7.3 Agents and RILO Causing Pain

[Rich Harmer]

I have a 4.2 SP2 Server, And a several hundred servers running Insight Manager agents ranging from 5.x to 6.x to 7.x. Just recently we began to deploy 7.3 on DL360 G4s and since we DONT use the Lights Out features, the nic doesn't have link and therefore causes a "major" problem (Orange Triangle). I don't see anywhere in the software where I can clear or disable it, and I'd really rather not go through my G4s (100+) and go through the bios to disable ILO.

Help?

Thanks,

Rich

[David Claypool]

In the "HP Management Agents" applet in Control Panel, you can move the "Remote Insight" module to 'inactive' to resolve this.

One of the biggest reasons people purchase ProLiant servers is because of iLO. Can I ask why you're not using it?

[Rich Harmer]

Why we aren't using it... Before I arrived at my current post, Insight Manager wasn't deployed and agents weren't on many servers.

Remote access to servers has been a sore point with a hodge poge of ways to access servers -- but there is some light at the end of the tunnel as we are about to decide on a uniform method to do this. I will guess IP/KVM may win out in our current data center due to the number of network lines and switches it would require (600+).

That help? :)

Rich

[Rob Buxton]

David,
From my perspective here, ILO is not why we purchase Proliants. Reliability, Management tools (agents, HPSIM) etc. ILO comes a way down the list.

At our local site, having an additional 80 plus Network connections for ILO has some consequence.
We are located next to our computer room and use KVM switches to reduce the number of consoles.

As a note, it seems to be the firmware version, not the PSP that triggers whether the card reports as a failure.
At the local site, I've not bothered updating the ILO firmware as a result.

And yes, if you have then you can remove the Remote Lights Out using the HP Management Agents GUI.

[Rich Harmer]

I did go to the control panel and everything is better now.

I'm glad you talked about the RILO firmware update causing it because I do remember a while back doing the upgrade on a machine as part of my routine maintenance and it caused the same problem.

Thanks to you both - hopefully the issue is documented and will help someone down the road.

Rich