- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: On-Board Administrator Stops responding to Net...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2011 12:45 PM
тАО10-26-2011 12:45 PM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2011 12:49 PM
тАО10-26-2011 12:49 PM
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" !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-31-2011 02:12 PM
тАО10-31-2011 02:12 PM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2011 01:06 AM
тАО11-07-2011 01:06 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-16-2012 06:59 AM
тАО01-16-2012 06:59 AM