I'm currently working on a new VMware ESX5.0i update 2 cluster. After the install of ESX5.0i, I set about to get OMSA on my hosts for health monitoring through OpenManage Server Essentials.
My initial efforts yielded me errors on the attempt to install. I was getting 'Could not find a trusted signer.' Googling this error led me here: http://charlieferreira.blogspot.com/2013/05/update-dell-openmanage-72-on-esxi5.html where they recommended adding the --no-sig-check flag.
That just changed my error. The install was then failing:
[VIBDownloadError]
Failed to download VIB.
url = vmware-fdm-5.0.0-623373
localfile = Unable to download VIB from any of the URLs
Please refer to the log file for more details.
/var/log/vmware # Unable to download VIB from any of the URLs
~sh: Unable: not found
At that point, I decided to get on the phone with Dell.
The verdict? OMSA doesn't have a version that supports 5.0 update 2. As this was released December 2012, and we're almost in July 2013, that was disappointing. I have to say I've been really unhappy with the poor health monitoring on ESX5i via Dell. I've had to implement service restarts automated on my hosts to keep the Dell software quasi-running (I still get bogus OMSE alerts that I have issues on the hosts that are not true).
Luckily for me, I have an enterprise iDRAC on the host that I can monitor over the OMSA software. If you didn't have that, I guess you'd be out of luck.
Showing posts with label OMSA. Show all posts
Showing posts with label OMSA. Show all posts
Wednesday, June 26, 2013
Thursday, February 7, 2013
Dell Servers, clearing the amber light
I run an environment consisting of Dell servers. I'm quite happy with them. They have some good management and monitoring utilities, and they've greatly improved applying things like firmware updates over the years.
This one was easy, but Googling didn't get me the answer, so I figured it warranted a post.
I had dealt with a nasty disk issue previously. In the end, I recovered the server to health, but my original RAID1 running in drives 0 and 1 had to reconfigured to run from drive 1 and drive 7 as a global hot spare. It seemed that there was a hardware problem in slot 0, and as the server is nearing retirement, it was easier just to leave drive 0 empty.
Some weeks later, someone else pointed out the "amber light." I monitor my systems through OMSE (Open Manage Server Essentials) which relies on OMSA (Open Manage Server Administrator), and the server showed healthy.
Physical examination yielded "PowerEdge 2950 E1812 HDD 0 Removed." Well, that was true, but I didn't need to see an amber light for it.
Going online netted me results like "Clear SEL" without telling me how to do that.
The quick and easy solution: clearing the hardware log.
From the OMSA web interface, from System, select Logs, and then Hardware. Then Clear Log.
Voila. Healthy blue display screen, no amber light.
This one was easy, but Googling didn't get me the answer, so I figured it warranted a post.
I had dealt with a nasty disk issue previously. In the end, I recovered the server to health, but my original RAID1 running in drives 0 and 1 had to reconfigured to run from drive 1 and drive 7 as a global hot spare. It seemed that there was a hardware problem in slot 0, and as the server is nearing retirement, it was easier just to leave drive 0 empty.
Some weeks later, someone else pointed out the "amber light." I monitor my systems through OMSE (Open Manage Server Essentials) which relies on OMSA (Open Manage Server Administrator), and the server showed healthy.
Physical examination yielded "PowerEdge 2950 E1812 HDD 0 Removed." Well, that was true, but I didn't need to see an amber light for it.
Going online netted me results like "Clear SEL" without telling me how to do that.
The quick and easy solution: clearing the hardware log.
From the OMSA web interface, from System, select Logs, and then Hardware. Then Clear Log.
Voila. Healthy blue display screen, no amber light.
Subscribe to:
Posts (Atom)