Major Health Status warning from a disconnected ILO port

[Mervin Cinq-Mars]

we do not use ILO so none of our sites have it connected. Can I tell the CMS to ignore this class of errors?

If not, I beleave that the practice is to inactivate the client agent so that the condition is not reported to the CMS. If this is true, then the problem I have is that the only active agent that I can see that MIGHT be correct is the NIC information agent. I do not want to ignore all NIC errors, merely ILO messages. What is the best way to acheive this?

[Rob Buxton]

There's an Agent "Remote Insight Information" move that to the Disabled Agents. The agent will need a restart.

[weik]

Hello Mervin
... also you can plug in a loopback connector (see picture), so you must not disable the agent.

kurt

[Dana Swanson]

Hi Mervin,

The loopbacks work great on 10/100 network ports.

If your ILOs have gigabit network ports you may only see a downgrade from Major to Minor health status if you use a loopback.

Loopbacks can get crosstalk on the wires and produce packet errors and these flag the agent as a alert still.

On these disabling the Remote Insight Information in the control panel like Rob mentioned is a easy way to fix it.

See ya,

Dana

[Mervin Cinq-Mars]

I have "fixed" this by removing the remote agent as suggested, thanks.