Re: On-Board Administrator Stops responding to Network Communication (1748 Views)
Reply
Occasional Visitor
Ryan Hoopp
Posts: 1
Registered: ‎01-10-2011
Message 1 of 5 (1,893 Views)

On-Board Administrator Stops responding to Network Communication

Hi,

 

I have an On-Board Admin for my C7000 with a backup OA as well.  At some point yesterday it stopped responding to network communication.  I can no longer ping the OA, or the iLo's of any of the servers I have attached to the C7000 Enclosure.  I am using 3.30 version of the firmware.

 

What are the risks to my environment, if I pull our and re-seed the OnBoard Admin modules to try and reset the environment to regain connectivity?  would it affect my Virtual Connect modules? (that are also not responding to ping)  Do I have any risk that my blades will lost their network connectivity?  Their SAN connectivity? or will the only thing affected be the On-Board admin cards themselves.?

 

Thanks

Ryan

Honored Contributor
Bart_Heungens
Posts: 687
Registered: ‎10-26-2005
Message 2 of 5 (1,890 Views)

Re: On-Board Administrator Stops responding to Network Communication

Hi,

 

Besides the fact why this happens (never had it myself, U should start with checking the logs), but yes you can remote the OA board from the enclosure... It will have no impact on the server or network operations...

 

ILO will not work anymore and the fans will go full speed but no production impact...

 

 

Kr,

Bart

--------------------------------------------------------------------------------
If my post was useful, clik on my KUDOS! "White Star" !
My blog: http://blog.bitcon.be
Occasional Visitor
Reddogg99
Posts: 1
Registered: ‎10-31-2011
Message 3 of 5 (1,872 Views)

Re: On-Board Administrator Stops responding to Network Communication

Hi,

 

I've run into the same problem on several enclosures.   Enclosures are  at 3.31, ilo2 2.06, ilo3 1.20. Here are the logs I get:

 

(Standby OA failed completely )

Oct 29 08:54:21 Enclosure Oct 29 08:54:21 10.62.43.59 OA: Internal System Firmware Error. Rebooting.
Oct 29 08:54:21 Enclosure Oct 29 08:54:21 10.62.43.59 OA: Function callback 0x00000000 0x3052505c 0x30525038 0x100053f8 0x1000f11c 0x100079f4 0x304f42d8 0x10002afc 
Oct 29 08:54:21 Enclosure Oct 29 08:54:21 10.62.43.59 OA: /usr/sbin/redund (pid=746) SEGV at 0x305250b8. Address accessed 0x00000000. Link reg 0x305250a0

 

(Standby OA came back up after several reboots)

Oct 24 11:29:23 Enclosure2 Oct 24 11:29:23 10.62.43.24 Redundancy: Onboard Administrator redundancy restored.
Oct 24 11:10:53 Enclosure2 Oct 24 11:10:53 10.62.43.24 Redundancy: Error communicating via ethernet with the other Onboard Administrator (heartbeat).

Oct 22 01:08:02 Enclosure2 Oct 22 01:08:01 10.62.43.24 OA: Onboard Administrator booted successfully
Oct 22 01:08:00 Enclosure2  Oct 22 01:08:00 10.62.43.24 OA: Redundant Onboard Administrator detected.

 

(Standby OA came back up after several reboots)

Oct 19 21:11:33 Enclosure3  Oct 19 21:11:34 10.62.44.74 OA: Onboard Administrator is rebooting
Oct 19 21:11:33 Enclosure3 Oct 19 21:11:33 10.62.44.74 OA: Internal System Firmware Error. Rebooting.
9:11:32.000 PM  Oct 19 21:11:32 Enclosure3 Oct 19 21:11:32 10.62.44.74 OA: Function callback 0x00000000 0x3052505c 0x30525038 0x100053f8 0x1000f11c 0x100079f4 0x304f42d8 0x10002afc 
 Oct 19 21:11:32 Enclosure3 Oct 19 21:11:32 10.62.44.74 OA: /usr/sbin/redund (pid=1324) SEGV at 0x305250b8. Address accessed 0x00000000. Link reg 0x305250a0

 

Last call with HP Support recommended updating ilo2 to 2.06.  It did not help.

 

Thanks

 

Occasional Collector
Leverfever
Posts: 1
Registered: ‎11-04-2011
Message 4 of 5 (1,850 Views)

Re: On-Board Administrator Stops responding to Network Communication

We're having the same problem with our c7000 enclosures. We installed firmware version 3.32 at first, but the OAs wouldn't establish a redundant link at all until we installed the firmware on each OA individually. We did this by removing one OA, installing the firmware on the live OA, then vice versa. Even after this they seemed unstable, often being unavailable for several minutes at a time.

 

We rolled back to 3.31, which seemed to be an improvement, in that we could see both OAs for several minutes at any one time, but we get the same errors as above in our syslog, example:

 

Nov  6 01:39:25  OA: /usr/sbin/redund (pid=697) SEGV at 0x305250b8. Address accessed 0x00000000. Link reg 0x305250a0  
Nov  6 01:39:25  OA: Function callback 0x00000000 0x3052505c 0x30525038 0x10005190 0x10003fc8 0x10004330 0x10004d88 0x10005c14
Nov  6 01:39:25  OA: Internal System Firmware Error. Rebooting.

 

On some OAs this will occur perhaps once or twice per day, on others the error appears repeatedly several times per hour.

Occasional Advisor
WilliamCH
Posts: 9
Registered: ‎03-11-2010
Message 5 of 5 (1,748 Views)

Re: On-Board Administrator Stops responding to Network Communication

I had same issues here. I have three c7000 chassis. Two have 3.21 firmware and one has 3.30 firmware. OA reboots itself pretty much twice a day and lost redundancy with standby OA. Jan 12 12:55:27 OA: /usr/sbin/redund (pid=1011) SEGV at 0x305230b8. Address accessed 0x00000000. Link reg 0x305230a0 Jan 12 12:55:27 OA: Function callback 0x00000000 0x3052305c 0x30523038 0x1000592c 0x100088fc 0x304f22d8 0x10002b1c Jan 12 12:55:29 OA: Internal System Firmware Error. Rebooting. anybody has any ideas? thanks,
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.