Important Note – I was updating this for v3 of the OM tool, and I cannot make it work with vCenter 5.5 U3a. I do not see U3 or U3a in their compatibility list so that may explain it. Much of the article has in fact been updated but it has not been finished due to this issue. I will keep an eye on it, and try and make it work, and will update this as I learn. Update – version 3, 3.1 of OM works with U3 and 6.0.
This is a wonderful tool that I last used as a plug-in for the vSphere Client. This is the first time using it in the vSphere Web Client and of course I am impressed. I have talked to a number of people who have worked for Dell and while they know of it, they have not seen it. So I figured it is a good idea to have an install / configure post on getting this great tool working. The prices on it have dropped seriously as well – I paid around 450 US$ for a 3 year subscription for four hosts. But I thought before the install / configure I would talk about why.
Installing OpenManage for vCenter
Things to gather before you start
- If you are using 12th Generation servers (like R720) you do not have to install the OpenManage VIB first as it will be install automatically. If you are using 11th Gen servers like the R710, or older you can use OpenManage (OM) to install the VIB I am told. Not sure how however – although this may help. Update – using the VUM depot and VIB mentioned in that article allowed me to connect to older generation servers – but not all of them. Still investigating that.
- Make sure your iDRAC are all configured and you have the credentials for them.
- You need an IP address and DNS entry. Do the DNS entry before installing as I think it saves on watching a few error messages.
- Service account for vC connectivity. It should be a member of Domain Users, and a vC admin level account.
- It looks like for 5 hosts or less there is no license or license file. This was confusing for me as I found a bunch of conflicting information on this subject and finally had to install to confirm! Update: not right, maybe 1 or 2 free. Confusing. Update: nothing free but 90 day trial.
- The documentation for 3.1 is here (3.0 is here 2.1 here and for 2.3 here).
- You do need the bits – which you will normally download via a link in the email after your purchase but you can download from here too. Note – when I bought the license info email was sent to someone else in the company that bought something from Dell a long time ago. When you get the bits you will need to extract them to find the .ovf / .vmdk files. See below what you are extracting down to. BTW, the Dell_OpenManage_Integration.exe file – seen below – needs to be run to extract everything you see below. It extracts to the same folder it executes in.
- Here is a link to a central point of info on OpenManage. This is a major useful link and is very useful! Documentation, bits, and videos. Plus more.
You would deploy the appliance as per normal. However be aware that you do not set password or network info during the deployment. I was so surprised, I did it twice! The documentation was not always exactly what I needed! After you have deployed the VM you access the VM console and set the password and network info – see below for the main screen you see after logging in (as admin on console with no password) and changing the password for the admin account.
Once you have finished with Time Zone, network, and likely Hostname too you should log out. You will be told to access a particular URL but ignore that. If you forget to do DNS, you will have troubles registering your vCenter. The error will be about not being able to contact, or certificate errors. After you add DNS info, you will need to reboot the appliance.
Once logged in at HTTPS://FQDN you will need to do a couple of things. When you log in the first time you will see something like below.
- The first thing we will do is to configure the OM to vC connection. Use the Register New vCenter Server button to start this process.
- You will see a dialog like below you will need to fill in. My service account is svcom but use whatever yours is. Update: as of later versions you need to do domain\user_name.
Once this is done, and the Register process works, you should see something like below.
Notice at the bottom of the screen where you can see my license info? That is with no license applied. I add my license (you can see the Upload License in the screenshot), and after a day or two, and after my inventory is being scanned by OM, this screen looks a little different.
Now you can see that my four hosts are using up licenses.
We need to configure NTP now so select Appliance Management in the list in the top left corner of the screen – it is likely already done, but just in case you can do it here. After you do that, and scroll down the new screen you will see NTP Settings and will be able to configure it. You may have done this in the console already.
BTW, at the top of the Appliance Management screen you can do pretty easy upgrades. I have pointed at the Update version info, and the update button in the screenshot below. I will do an article about upgrades the next time I do an upgrade (here it is).
The next section is Alert Management and normally I do not make any changes there until after I have had things running for a while and actually know why I would make a change.
We do need to make changes in Backup and Restore. I do suggest you setup a CIFS share that the appliance can access and do a backup too. I use the same service account I use to connect to vC to secure the folder that the appliance will backup to. See what the configuration looks like when it is done (Note: I had troubles with the URL for my backup location below when I used a capital D for Dell. When I changed it both in Windows and the URL to a small d it worked fine.)
You can see I setup the schedule backups too. This is particularly important as you use OM more and have more and more configuration that you don’t want to lose. Also note that I tested things? Important to do that. BTW, the location where you specify the backups to be written too will look like below once you have some backups. One very nice improvement I appreciate, which I think came out in 3.0 is the ability to do a manual backup but use the settings that you have configured and not have to type them in again!
The appliance is now configured and we are ready to move forward!
Configuration in vSphere Web Client
We have some interesting things to do in the Web Client now. Lets get started!
- Log out of your vSphere Web Client and log back in.
- When you log back in you should see a new icon in the Home page.
See it in the bottom row on the right? You need to click on it now and you will see a popup about the initial setup.
This starts a wizard to help you get things configured.
The first screen is just a welcome screen but I suggest you also check and enable the Do Not show the Configuration Wizard again as that will be irritating and you can always start it again.
After you press Next you will see the next screen.
You should see your vC already selected. After Next you will see an informational screen which is followed by a Connection Profile screen. When it is filled in it will look something like below.
There is some important things to understand on this form. Note in the iDRAC Credential section I am not using AD but I have a blank user name and yet a password defined? That password is for the root account in my iDRACs.
Update: while the above was true for the version of Dell used in this article, in a later version – 184.108.40.206 you need to put root in the account info above.
As well, the Host Root section is similar. See below for that example.
For the root account on the hosts you need the password as well. On the next screen you select your Dell hosts. In my case my whole Gold cluster is Dell hosts.
Update: as of – I believe 220.127.116.11 there was an additional screen added to the wizard. This screen allows you to test the credentials before you continue. You can see below in the screenshot the screen and the button to use to test.
The next screen just confirms information. On the next screen however you need to enable and configure Inventory Data retrieval. This is important. Check out what mine looks like.
The next screen is about configuring Warranty Data retrieval. I do not think it needs to be done often at all. See how I configured mine below.
The next screen is Events and Alarms and I do not make any changes there at this time. I do later on after I am more familiar with how things work with this product.
When you are finished with this wizard you will see something like below.
The configuration is now finished! We need to wait until the Inventory and Warranty details are retrieved but at least things are ready now.
So some time has passed, enough so my Inventory retrieval has run. Lets go look. You should see something at the Cluster level, and on Monitor / Dell Cluster Information. Like below.
Or if you change to the Firmware option you will see something like below.
There you have it. Things are good. You now have OM installed and can see a lot more info on your Dell servers and you can now start doing other things like firmware updates without an outage – which I will show you how in a new article soon.
Have a great day – and don’t forget questions or comments are welcome!
- 8/17/16 – updated this after testing the referenced article in supporting older hardware. It worked on one but not the other. So curious!
- 8/11/16 – update for using this with 3.1, updated links for 3.1, making some of the screenshots bigger and misc cleanup.
- 11/4/15 – started to updated and got a lot done before I discovered that it appears vSphere vCenter 5.5 U3 or U3a is not supported. Cannot make OM visible in the vSphere Web Client. And who would NOT use U3a with that amazing CIP fix in it!? Will update as I learn.
- 5/13/15 1714 – more on 2.3 – just making things more clear.
- 4/2/15 1019 – more on the 2.30 release. Nothing major but just cleaning it up.
- 4/1/15 1628 – updated for the 2.30 release.
- 3/31/15 1925 – found this handy link for things OMVV.
- 1/27/15 – added a note about that even as current as 18.104.22.168 you will not see your day or time when you set a schedule to do a BU but it will work.
- 1/27/15 – added a note that as of 22.214.171.124 you need to specify the root account in the connection profile and not leave it blank.
- 1/27/15 – added a screenshot to cover off credential testing in the initial config wizard that was added in – I think – 126.96.36.199.
=== END ===