Status reported as Minor but nothing is wrong

[Kevin Everts_1]

I have a ML310 G3 that is being reported as having a 'Minor' health status for the server and ilo card. When I go to the System Management Homepage on the server, it doesn't show anything as being wrong. There aren't any failed or degraded items. The only thing different with the server compared to the rest of them is that the NIC and ilo are in different networks.

Anyhow, why would SIM think that the status is minor?

[Igor Karasik]

Kevin,
ILO card connected to network ?

[Ivan Daniel]

You may want to try checking the Integrated logs. The events in the logs may have been fixed but the log entries need to be cleared or deleted

[Ferry Steenvoorde]

Another one: is the external trafo for the ILO-board not connected?

[Kevin Everts_1]

The ilo card is connected. It is on a different network than the server's network card though.

I checked the logs, there isn't anything that needs to be cleared.

What is the external trafo? The server is in a remote location and I haven't actually seen it yet so I don't know what is connected.

[Craig McK]

Does the status stay at minor after re-identifying the server, or deleting & re-discovering?

[Kevin Everts_1]

Yeah. I've deleted it from SIM, restarted the agents, etc and it keeps showing up as Minor.

[Ferry Steenvoorde]

I do not know what kind of ILO-board an ML310 has, but the ML370 has a "Remote Insight Lights Out Edition" ILO-board. It's got an (external) auxiliary power unit.
Check the SMH, Remote Insight Board, Power, Auxiliary Power. It may show yellow.

[Kevin Everts_1]

There isn't any external power, at least not that I see.

[Terence Burton]

Hi Kevin,
I don't know if this will help, but there are two things you could try:

1. Run a hardware status polling from SIM (Make sure the job includes the problem server), this will update the minor warning.

or

2. I have iLo cards enabled, but not in use, so to stop errors appearing on SIM, from the problem server, go to control panel, load HP Management Agents, then from the services tab, highlight and remove "Remote Insight Information"

I hope this helps.

[Wim Panhorst]

I have the same problem with a DL320 G4. None of the proposed solutions seem to help.

[Kevin Everts_1]

I'm still having this issue. I've finally decided to give up and watch that server closely.

[HP Systems Insight]

Two thoughts - One is that I believe the ILO status is just a reflection of the server status (I'm not 100% sure on this)

Second, when we've had this issue the most common cause has been communication failure with the UPS and the only way we could verify was to RDP in console mode (if w2k3 use mstsc /console) or for our 2K we use dameware to get to the console and then outside of the agents we could see the UPS error.

MJ

[dospavlos]

I've seen this with the ilo as the culprit. If you go to the smh, all components looks green including ilo. If you drill down in the smh to the management processor / integrated lights-out, I've seen one of the self test results components (usually nvram) in a degraded status. Clicking the 'reset ilo' button and waiting around 10 minutes will fix it. I get this everytime I do a firmware update on ilo's.

[James Kennedy_4]

Yes, this usually is often the ILO or RILOE II card that is the issue.

Funny enough, if you are running Compaq Insight Manager 5.5, you actually get the yellow indicator on Recovery icon and the RILO board. For some reason the SMH shows everything as green.

[Kevin Everts_1]

I tried resetting the ilo card but it didn't fix it.

[Goonboon]

I had the same problem on an old GL580. After reading this post and the hints that it could be related to the iLO, I went through the SMH and checked out the iLO. Found that the External Power showed green but had a "Disconnected" error message. I reseated the External Power and removed the system from SIM. After resetting the iLO and adding the server back into SIM it seemed to have fixed my problem.

Server now shows green.

Hope this helps

Chris

[komaxRos]

Hello Kevin

I have extactly the same problem with my new Proliant ML310G3 and HP SIM, I have contacted HP support using the carepack contract. At this time HP is not able to fix the problem, something is wrong arround ILO2 power supply. Problem can be on Agent or on HP SIM, HP as repported the problem to developpers, as soon I have a response I will forward it to the post

Regards
KomaxRos

[Brian Hahne]

We have the exact same issue, nothing is wrong on the System Management Homepage, but SIM 5.0 SP5 is still reporting all of our DL320 G4's in a minor state.

I applied ILO Fw 1.22 (just released) to the servers, and that didn't fix it.

Has anyone found a solution to this?

[Brian Hahne]

Still no fixes. PSP 7.60 and firmware is out, anyone know if this has been resolved?
All my DL320 G4's running W2K3 are showing as minor.

[Kevin Everts_1]

I now have 3 servers that are doing this. They are a DL380 G2, a ML370 G1 and the original ML310 G3.

[Brian Hahne]

I take back my earlier post.
PSP 7.60 definitely fixed this issue.
I just installed it, and the servers all now report properly.

[Brian Hahne]

You shouldn't have a DL380 G2 doing this though..
Even the ML310 G3 should be ok.

Does your server SNMP settings allow read and create for the sim server? That needs to be set. Did you maybe configure the agents improperly where they are going for certificates or something?
The DL320 G4 was definitely an issue.
DL380 G2 shouldn't be though.

[Kevin Everts_1]

Everything is set correctly. The ML370 and DL380 G2 started doing this after I installed the 7.60A support pack. Prior to the installation, the two servers reported correctly.

[Brian Hahne]

That's very strange.
I just noticed that my new DL380 G5, and 2 new DL360 G5's were doing this. I installed 7.60 and it's fixed. So that was definitely linked to the ILO2 i think.

Not sure why you'd see this on a DL380 G2. That doesn't make any sense to me. I have 400 servers all reporting fine now.
The only things I can think: snmp set wrong on client or sim host, certificates not working if using them for trusted communication, maybe in the snmp properties you aren't checking physical/datalink/etc.. and just a few? i think you should check them all.