Unsolved
This post is more than 5 years old
9 Posts
0
152580
February 4th, 2016 05:00
OME shows servers with warnings
HI all,
I have some strange problem with some of the servers. Currently we have 6 PowerEdge Server but different versions T and R series. 3 of the servers are standalone ESX servers. On T430 there is no problem but on T420 and R320 there is warning by Data Sources and Global Status. There are 4 lines:
- Server Administrator - green
- Server Administrator (Storage Management) - yellow
- iDRAC7 - question mark
- VMware ESXi 5.5.0 build-2068190 - yellow
All 3 servers are using the same version of ESXi server. By T420 and R320 I made a mistake becuase I've installed first the package for ESXi 5.1 but I've successfully updated it later with the version for 5.5. I've tried also removing the servers from inventory and adding them again but without success.
Anyone has an idea what else I could do to fix the problem? Thanks in advance.
brastedd
2 Intern
•
336 Posts
0
February 4th, 2016 06:00
Is CSIOR (Collect System Inventory On Restart) turned on for those servers? If it is, have you rebooted them lately? If it isn't, I'd suggest turning it on and rebooting (if you can) so that OME has the latest data.
Can you view the iDRAC7 GUI? Does it show any errors in there?
BorislavVitanov
9 Posts
0
February 4th, 2016 07:00
Hi brastedd,
I've checked on both server the iDRAC and on both at system summary everything is green. I've checked also Logs - everything seems to be ok. I've restarted both server last week when I've updated the package for ESXi. Sorry for the question but where is the option for CSIOR? Usually the discovery and inventory task is scheduled and executed everyday. I've also perform it manually.
brastedd
2 Intern
•
336 Posts
0
February 4th, 2016 12:00
SSH into your iDRAC7s and run the following:
racadm get LifecycleController.LCAttributes.CollectSystemInventoryOnRestart
It will tell you whether CSIOR's enabled. If it isn't you can enable it using:
racadm set LifecycleController.LCAttributes.CollectSystemInventoryOnRestart Enabled
You'll need to reboot the server to force it to take a new inventory.
BorislavVitanov
9 Posts
0
February 5th, 2016 00:00
Hi brastedd,
I've just check and on both servers it is enabled.
brastedd
2 Intern
•
336 Posts
0
February 5th, 2016 06:00
At this point I would suggest calling Dell tech support and opening a case with them. They'll probably need to dig into the OME database and such to see what's going on.
DELL-Pupul M
2 Intern
•
1K Posts
0
February 8th, 2016 06:00
The warning ICON that you see for storage management may be due to the firmware of a storage module. It contributes to the health status of storage and storage management shows it as warning. Upgrading the firmware to latest should sort this problem if you are seeing green everywhere else.
BorislavVitanov
9 Posts
0
February 9th, 2016 05:00
Hi Dell-Pupul,
you mean to update firmware for PERC H710P Adapter? I think that I have to remove the vib installation, reboot and install it again. I hoped that this won't be need it. About the warnings - see my first post. Is it possible to make a check for updates using iDRAC. There everything is green and looks ok.
DELL-Pupul M
2 Intern
•
1K Posts
0
February 9th, 2016 07:00
Not sure if you would have to remove the vib installation. Might not be needed. You should be able to just update the PERC firmware on this server via iDRAC update method if the iDRAC is discovered using WSMAN protocol. Another way to confirm this would be use the latest catalog in OME and then verify if this system shows PERC adapter as one of the components which is non-compliant.
Have you discovered the ESXi host also using WSMAN?
BorislavVitanov
9 Posts
0
February 14th, 2016 01:00
yes, it was discovered with WSMAN the same way like on the other ESX servers with the same settings. The "warnings" are by Server administrator (storage management) and VMware ESXi. By iDRAC7 is only question mark. I've tried to search in OME anywhere about explanation about these indications but so far without luck. I thought that when such warnings or problems appear there should be kind of explanation somewhere what an administrator should do and exactly is the problem.
DELL-Pupul M
2 Intern
•
1K Posts
0
March 1st, 2016 09:00
Hi,
Thanks for clarifying. OME does provide an option to launch OMSA and verify what is wrong on the server. Unfortunately for ESXi hosts, you need to setup a distributed web server setup to launch OMSA. If you are able to launch OMSA of ESXi server, you should be able to find the problem. In worst case, please try to download the latest catalog and check if this server is listed as non-compliant with storage firmware needing update.
BorislavVitanov
9 Posts
0
March 31st, 2016 07:00
hi Dell-Pupil
sorry for the delay of my answer. I've downloaded the latest catalog and check the compliancy of the computers. The results are interesting. We have 6 servers - 3 of them are with ESXi but only 2 are with warnings by health - Server 1 and Server 2. In the same time the compliance is showing that all ESXi servers have issues. And here comes the strange part:
Reason: System Update is not support on ESXi systems that are discovered using WSMAN
Recommendation: Discover the iDRAC of ESXi using WSMAN for out of band updates.
Do you have any suggestions? Thanks in advance
BorislavVitanov
9 Posts
0
April 14th, 2016 06:00
Dell-Pupil any ideas?
DELL-Pupul M
2 Intern
•
1K Posts
0
April 14th, 2016 08:00
Hi,
Like you see in the resolution, it is needed to have the iDRAC of the server also discovered to perform Out of band system update on these servers(iDRAC update method). If the server is shown non-compliant with PERC controller as a package, then most likely that is the reason for warning health state.
The reason to why health is warning can be best figured out by launching OMSA for that ESXi host.