- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Problem with OA - Onbord Administrator 2.31 , Enc...
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
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
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
08-19-2016 02:25 AM
08-19-2016 02:25 AM
Problem with OA - Onbord Administrator 2.31 , Enclosure info - BladeSystem c3000 ?
Hi guys,
I have got the same problem from 2 - 3 days with my Onbord Administrator (OA).
It's happened twice morning, when I come to work in our server room is too noisily. When I login in OA I seeing my blade servers with Critical errors : Management Processor : Error - lost communication with ILO , and their fans spins on 98%.
The reboot it is not decision, but when I pull out OA module from the chassis and back it again, everything is OK
That from below is OA System Logs from when I have problem with my OA:
Aug 17 04:07:54 OA: Management Processor on Blade 1 appears unresponsive.
Aug 17 04:08:04 OA: Management Processor on Blade 2 appears unresponsive.
Aug 17 04:08:14 OA: Management Processor on Blade 3 appears unresponsive.
Aug 17 07:38:28 OA: Authentication failure for user admin from 192.168.11.203, requesting web service
Aug 17 07:38:46 OA: admin logged into the Onboard Administrator from 192.168.11.203
Aug 17 08:29:45 OA: Blade removed from bay 3
Aug 17 08:29:45 OA: Blade inserted in bay 3
Aug 17 08:29:45 OA: Blade in bay #3 status changed to OK
Aug 17 08:29:45 OA: Management Processor on Blade 3 appears unresponsive.
Aug 17 08:31:45 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 08:33:45 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 08:44:19 OA: Blade removed from bay 3
Aug 17 08:44:19 OA: Blade inserted in bay 3
Aug 17 08:44:19 OA: Blade in bay #3 status changed to OK
Aug 17 08:46:19 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 08:47:37 OA: Management Processor on Blade 3 appears unresponsive.
Aug 17 08:48:19 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 09:31:39 OA: Blade removed from bay 3
Aug 17 09:31:40 OA: Blade inserted in bay 4
Aug 17 09:31:40 OA: Blade in bay #4 status changed to OK
Aug 17 09:33:40 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 09:35:04 OA: Management Processor on Blade 4 appears unresponsive.
Aug 17 09:35:40 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 09:44:11 OA: Blade removed from bay 4
Aug 17 09:44:11 OA: Blade inserted in bay 4
Aug 17 09:44:11 OA: Blade in bay #4 status changed to OK
Aug 17 09:46:11 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 09:47:35 OA: Management Processor on Blade 4 appears unresponsive.
Aug 17 09:48:11 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 10:37:36 OA: PowerDelay server settings have been changed.
Aug 17 10:39:57 OA: Blade removed from bay 4
Aug 17 10:39:57 OA: Blade inserted in bay 4
Aug 17 10:39:57 OA: Blade in bay #4 status changed to OK
Aug 17 10:41:58 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 10:43:21 OA: Management Processor on Blade 4 appears unresponsive.
Aug 17 10:43:58 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 10:44:54 OA: PowerDelay server settings have been changed.
Aug 17 10:57:36 OA: Onboard Administrator is rebooting
Aug 17 10:58:16 Kernel: Network link is up at 100Mbps - Full Duplex
Aug 17 10:58:17 OA: Time zone changed to GMT+2
Aug 17 10:58:19 OA: LCD Status is: OK.
Aug 17 10:58:21 Enclosure-Link: Service started
Aug 17 10:58:22 OA: Onboard Administrator booted successfully
Aug 17 10:58:31 Enclosure-Link: Initial topology scan completed successfully
Aug 17 10:59:48 OA: admin logged into the Onboard Administrator from 192.168.11.203
Aug 17 11:00:32 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 11:01:24 OA: Management Processor on Blade 1 appears unresponsive.
Aug 17 11:01:30 OA: Management Processor on Blade 2 appears unresponsive.
Aug 17 11:01:42 OA: Management Processor on Blade 4 appears unresponsive.
Aug 17 11:02:56 OA: Blade removed from bay 4
Aug 17 11:03:13 OA: Blade inserted in bay 3
Aug 17 11:03:13 OA: Blade in bay #3 status changed to OK
Aug 17 11:04:56 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 11:06:31 OA: Management Processor on Blade 3 appears unresponsive.
Aug 17 11:06:56 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 11:12:51 Kernel: Network link is up at 100Mbps - Full Duplex
Aug 17 11:12:53 OA: Time zone changed to GMT+2
Aug 17 11:12:54 OA: Server Power Reduction Mode - Enabled
Aug 17 11:12:55 OA: LCD Status is: OK.
Aug 17 11:12:56 Enclosure-Link: Service started
Aug 17 11:12:58 OA: Onboard Administrator booted successfully
Aug 17 11:13:06 Enclosure-Link: Could not acquire bottom enclosure's UUID. Cannot set RUID.
Aug 17 11:13:06 Enclosure-Link: Initial topology scan completed successfully
Aug 17 11:13:08 OA: Blade 3 is reporting nominal health status.
Aug 17 11:13:08 OA: Blade in bay #3 status changed to OK
Aug 17 11:13:13 Enclosure-Link: RUID recovered: 09CZC9027XJ3
Aug 17 11:13:28 OA: Blade 1 is reporting nominal health status.
Aug 17 11:13:28 OA: Blade in bay #1 status changed to OK
Aug 17 11:13:32 OA: Blade 2 is reporting nominal health status.
Aug 17 11:13:32 OA: Blade in bay #2 status changed to OK
Aug 17 11:13:36 OA: Server Power Reduction - Deactivated
Aug 17 11:13:36 OA: Server Power Reduction Mode - Disabled
Aug 17 11:13:40 OA: Server blade in bay 3 has been powered on
Aug 17 11:13:40 OA: Blade 3 is properly cooled.
Aug 17 11:14:09 OA: Blade in bay #3 status changed to OK
Aug 17 11:14:25 OA: admin logged into the Onboard Administrator from 192.168.11.203
Aug 17 11:14:29 OA: Blade in bay #1 status changed to OK
Aug 17 11:14:33 OA: Blade in bay #2 status changed to OK
Aug 17 11:15:08 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 11:15:08 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 17 11:17:08 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 18 15:35:48 Kernel: Network packet flooding detected.
Aug 18 15:35:50 Kernel: Network packet flooding detected.
Aug 18 15:35:55 Kernel: Network packet flooding detected.
Aug 18 15:36:02 Kernel: Network packet flooding detected.
Aug 18 20:28:34 OA: Management Processor on Blade 1 appears unresponsive.
Aug 18 20:28:44 OA: Management Processor on Blade 2 appears unresponsive.
Aug 18 20:28:54 OA: Management Processor on Blade 3 appears unresponsive.
Aug 19 07:43:16 OA: admin logged into the Onboard Administrator from 192.168.11.203
Aug 19 07:51:20 OA: Onboard Administrator is rebooting
Aug 19 07:52:00 Kernel: Network link is up at 100Mbps - Full Duplex
Aug 19 07:52:00 OA: Time zone changed to GMT+2
Aug 19 07:52:01 OA: LCD Status is: OK.
Aug 19 07:52:03 Enclosure-Link: Service started
Aug 19 07:52:04 OA: Onboard Administrator booted successfully
Aug 19 07:52:13 Enclosure-Link: Initial topology scan completed successfully
Aug 19 07:53:13 OA: admin logged into the Onboard Administrator from 192.168.11.203
Aug 19 07:54:14 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 19 07:55:07 OA: Management Processor on Blade 1 appears unresponsive.
Aug 19 07:55:13 OA: Management Processor on Blade 2 appears unresponsive.
Aug 19 07:55:19 OA: Management Processor on Blade 3 appears unresponsive.
Aug 19 08:15:31 Kernel: Network link is up at 100Mbps - Full Duplex
Aug 19 08:15:32 OA: Time zone changed to GMT+2
Aug 19 08:15:34 OA: Server Power Reduction Mode - Enabled
Aug 19 08:15:36 OA: LCD Status is: OK.
Aug 19 08:15:38 Enclosure-Link: Service started
Aug 19 08:15:41 OA: Onboard Administrator booted successfully
Aug 19 08:15:47 Enclosure-Link: Initial topology scan completed successfully
Aug 19 08:15:47 OA: admin logged into the Onboard Administrator from 192.168.11.203
Aug 19 08:16:10 OA: Blade 1 is reporting nominal health status.
Aug 19 08:16:10 OA: Blade in bay #1 status changed to OK
Aug 19 08:16:15 OA: Blade 2 is reporting nominal health status.
Aug 19 08:16:15 OA: Blade in bay #2 status changed to OK
Aug 19 08:16:16 OA: Server Power Reduction - Deactivated
Aug 19 08:16:16 OA: Server Power Reduction Mode - Disabled
Aug 19 08:16:20 OA: Blade 3 is reporting nominal health status.
Aug 19 08:16:20 OA: Blade in bay #3 status changed to OK
Aug 19 08:17:10 OA: Blade in bay #1 status changed to OK
Aug 19 08:17:15 OA: Blade in bay #2 status changed to OK
Aug 19 08:17:20 OA: Blade in bay #3 status changed to OK
Aug 19 08:17:48 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
Aug 19 08:18:08 Alertmail: Failed to send AlertMail to kiro@elkabel.bg
If someone has experience with similar errors please let me share what have to done.
Thank you in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-19-2016 04:29 AM - edited 08-19-2016 04:40 AM
08-19-2016 04:29 AM - edited 08-19-2016 04:40 AM
Re: Problem with OA - Onbord Administrator 2.31 , Enclosure info - BladeSystem c3000 ?
Onbord Administrator 2.31 ???
The oldest version I still have on my disk is 2.60 from early year 2010.
Now we are at version 4.50.
Same age for ILO and BIOS?
So you probably missed 1000+1 fixes ...
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-19-2016 05:23 AM
08-19-2016 05:23 AM
Re: Problem with OA - Onbord Administrator 2.31 , Enclosure info - BladeSystem c3000 ?
Hi,
My blade system ILO2:
Model iLO2 Firmware Version 1.61 Aug 31 2008 ROM Version I15 11/02/2008
OA:
Device Name BladeSystem c3000 Onboard Administrator Manufacturer HP Firmware Version 2.31 Hardware Version 0J
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2016 11:16 PM
08-21-2016 11:16 PM
Re: Problem with OA - Onbord Administrator 2.31 , Enclosure info - BladeSystem c3000 ?
Is it problem on firmware versions !?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2016 12:43 AM
08-22-2016 12:43 AM
Re: Problem with OA - Onbord Administrator 2.31 , Enclosure info - BladeSystem c3000 ?
>>
My blade system ILO2:
Model iLO2 Firmware Version 1.61 Aug 31 2008 ROM Version I15 11/02/2008
This is not helpful without knowing the blade model.
>> Is it problem on firmware versions !?
Maybe.
Here is the list of all OA updates and fixes, have a look.
(consider an update!)
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2016 01:13 AM
08-23-2016 01:13 AM
Re: Problem with OA - Onbord Administrator 2.31 , Enclosure info - BladeSystem c3000 ?
I saw this, but we have not HP support, and we afraid to execute these operations.
Who will assume a responsibility if happens something badly, unless we.
What will you advise me !?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2016 01:20 AM
08-23-2016 01:20 AM
Re: Problem with OA - Onbord Administrator 2.31 , Enclosure info - BladeSystem c3000 ?
Separately, from where I can download new firmwares