One note about discovery of ESXi 5.0 servers with Dell OpenManage EssentialsPosted: October 31, 2012 Filed under: Dell, VMware | Tags: dell, dell esxi unknown, dell ome, esxi open manage, esxi openmanage, esxi unknown, ome, ome unknown, omsa, omsa 7.1, omsa 7.1 vib, omsa vib, open manage essentials, openmanage, unknown, vib 7 Comments
Even though we’re using the Dell Management Plug-in for vCenter, we use Dell’s OpenManage Essentials (OME) for physical boxes. I want to be able to view ESXi server info from OME, as well, though. After initial configuration, my ESXi servers were showing up as “Unknown” even though they were correctly categorized as “VMware ESX Servers” in OME. This irritated me because I had finally configured my physical servers to show nice green check marks to show all was well but I couldn’t get my ESXi boxes to play nicely. As the ESXi boxes sat as unknown, they also did not have detailed hardware inventories available.
Now, I’ve been unimpressed by Dell’s hardware management platform so far even though the idea of it promises to be a big time saver and monitoring tool. When I have it configured, not only will I get SNMP hardware monitoring, but I should be able to upgrade firmwares and BIOSs remotely. Mostly, I’ve been dissatisfied by the lack of clear and organized configuration steps for, what I consider to be, a pretty standard data center: mostly virtualized with a few physical servers scattered about. As a note, I haven’t yet configured Dell’s management and monitoring stack to keep track of our remote office hardware, but it’s on the list of things to do.
Real quick, let me show you what I’ve come up with.
Dell Management Plug-in with DNS AliasesPosted: October 3, 2012 Filed under: Dell, VMware | Tags: dell, dell management, dell management plug-in, dell management plugin, dell plug-in, dell plugin, management, plug-in, plugin, vcenter plug-in, vcenter plugin Leave a comment
A tricky configuration piece of the Dell Management Plug-in that I discovered the hard way was that you must log in to vCenter via the vSphere Client with the same name or IP address with which you used to register vCenter with the Dell Management Plug-in Virtual Appliance. And I mean *exactly* the same, perhaps even with an FQDN. You can’t register vCenter in the Dell virtual appliance with an IP address and then turn around and log in to the vSphere Client with your usual server name or, in my case, a DNS alias or CNAME.
As you can see above, I’ve created a CNAME record for the first of my vCenters that are in a Linked-Mode group. I’ve named it vCenter. This is how I log into the vSphere Client – by just typing vCenter in the Name/IP address field. When I first registered the Dell plug-in via the virtual appliance, I registered the first vCenter server by its FQDN – let’s call it, myvcenter.company.net. Going to the Dell plug-in in the vSphere Client you get a nice error stating that the Dell Management Plug-in cannot access vCenter. Showing details gives you nothing, but don’t despair quite yet.