Updating Dell iDRAC ISM

I was working on installing iDRAC for an ESX host, and ran into a little trouble. Here's a small guide for the steps to do it. Googling it leads you to this article:
https://www.dell.com/support/manuals/us/en/04/idrac-service-module-v3.1/ism_3.1_users_guide/using-the-vsphere-cli?guid=guid-1606fa9a-19ad-4394-a65f-72fb0312a2c7&lang=en-us
I didn't think this was clear enough, so here's some pictures too


When you are inside of iDRAC, you will see this:

Download the iSM installer.

Next:

Create a Folder inside a datastore


Upload the ZIP you downloaded from iDRAC

Enable SSH and ESXCLI inside the host

SSH into the host

CD to the directory

Actual command I ran:

esxcli software vib install -d /vmfs/volumes/5d135ad3-ff5e8e7c-6d02-e4434b77b398/ISOs/ISM-Dell-Web-3.4.0-VIB-ESX6i-Live.zip

Even though it says you don't need to restart, you will need to get iDRAC to recognize it.

Comments

Post a Comment

Popular posts from this blog

Outlook VBA Macros for Journal Entries

I recently discovered how amazing the Journal function is in Outlook. Primarily, it's great because it has a timer on it that you can use to track your time. It also allows you to categorize each Journal Entry with a type, as well as the categories already in Outlook. I like using this for if someone calls me, there's an entry type for "Phone Call". I'll record what the conversation was about. It automatically creates a new entry at the day and time you create it. If I'm working on a script, there's a Entry Type for "Scripting". I'll record notes on what I'm working on, and my findings/issues I run into. If I'm doing a task, there's one for "Task". All of these are great but I wanted to add a little more automation to it all. I didn't like that I couldn't easily start a new Journal Entry from the E-Mail Home Screen. I had to open the Journal, create a new Entry and then start the timer. Too much to do when so...
Read more

SCCM PXE Boot Issues - No Advertisements Found

Image
I've been battling with a pervasive issue with SCCM where the computer fails to install the SCCM task sequence on the first try, it won't ever boot again. It will constantly just present you with a "failed to boot" message, or something of that regard. Then when you attempt to boot it again, in the SMSPXE.log, it will give you an error that says "no advertisements found". You can see a sample of that log below This is by design of the SCCM system. It won't attempt to rerun a required deployment to the same MAC address. Resolution: I had only set up a deployment to unknown computers as required. The workaround I came up with is to also deploy an "Available" deployment to unknown computers. This will cause the task sequence to be offered as an optional deployment, and give you the chance to re-run the task sequence.
Read more