- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Firmware 2.60 to 3.10 causes lost of OA
BladeSystem - General
1753974
Members
7161
Online
108811
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО06-26-2010 01:01 AM
тАО06-26-2010 01:01 AM
Firmware 2.60 to 3.10 causes lost of OA
Hi,
I've just started to update our C7000s but stopped after the first one after uploading and restting the standby OA, I received a message saying the SB OA couldn't recognise the f/w image and the update failed.
Now I have a working active OA on 2.60 f/w and the SB OA is pinging but unknown to the active OA and is unusable.
I updated locally via the HTTP interface if it matters.
I'll now stop the updates and log a call with HP to perhaps replace the SB OA if a physical reset on Monday doesn't fix it.
Anyone else seen this behaviour?
I've just started to update our C7000s but stopped after the first one after uploading and restting the standby OA, I received a message saying the SB OA couldn't recognise the f/w image and the update failed.
Now I have a working active OA on 2.60 f/w and the SB OA is pinging but unknown to the active OA and is unusable.
I updated locally via the HTTP interface if it matters.
I'll now stop the updates and log a call with HP to perhaps replace the SB OA if a physical reset on Monday doesn't fix it.
Anyone else seen this behaviour?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2010 11:15 PM
тАО06-26-2010 11:15 PM
Re: Firmware 2.60 to 3.10 causes lost of OA
Seen similar things going 2.60 to 3.00.
I hate saying this, but most likely fix may be to pop the sb module (wait a few mins) and replace.
A fix when i had a firmware mismatch (which caused a similar issue) was to repeat the firmware upgrade.
What does the log file of the active OA say? Also might be worth running a 'show oa info all' from the command line.
I hate saying this, but most likely fix may be to pop the sb module (wait a few mins) and replace.
A fix when i had a firmware mismatch (which caused a similar issue) was to repeat the firmware upgrade.
What does the log file of the active OA say? Also might be worth running a 'show oa info all' from the command line.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-28-2010 10:02 PM
тАО06-28-2010 10:02 PM
Re: Firmware 2.60 to 3.10 causes lost of OA
Yep, same issue. We followed HP support advice and pulled both OAs, and their sleeve.
Can't help feeling like you don't have the redundancy you thought you did after you've had to do that :(
Certainly fixed the problem with no actual downtime though.
Can't help feeling like you don't have the redundancy you thought you did after you've had to do that :(
Certainly fixed the problem with no actual downtime though.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2010 08:58 AM
тАО07-05-2010 08:58 AM
Re: Firmware 2.60 to 3.10 causes lost of OA
Thanks. Re-seating the OA didn't help but resolved it by a physical connection.
I started an ftp and DHCP service on my laptop, so the secondary OA was able to obtain an IP address, I then followed the instructions from the OA
Lost Password or Flash Recovery requested
Press L for Lost Password Recovery
Press F for Flash Recovery
Press any other key to reset
Flash Recovery Mode
Obtaining DHCP Address...ENET Speed is 10 Mbps - HALF duplex connection
BOOTP broadcast 1
DHCP client bound to address 192.168.4.193
Done
Please enter the IP address of the tftp server at the next prompt.
Please enter 'serverip':192.168.4.195
Please enter the filename of the ROM image at the next prompt.
Please enter 'bootfile':hpoa310.bin
The Onboard Administrator will keep trying to download the image until it succeeds.
If this does not complete, you may press to restart Flash Recovery Mode.
Downloading the ROM...Done!
Verifying ROM image....Done!
Flashing your Onboard Administrator. This will take several minutes.
Do not power off or reset until the process completes
Flashing...
..
..
..Done!
Flash procedure succeeded.
Restarting the Onboard Administrator.
I started an ftp and DHCP service on my laptop, so the secondary OA was able to obtain an IP address, I then followed the instructions from the OA
Lost Password or Flash Recovery requested
Press L for Lost Password Recovery
Press F for Flash Recovery
Press any other key to reset
Flash Recovery Mode
Obtaining DHCP Address...ENET Speed is 10 Mbps - HALF duplex connection
BOOTP broadcast 1
DHCP client bound to address 192.168.4.193
Done
Please enter the IP address of the tftp server at the next prompt.
Please enter 'serverip':192.168.4.195
Please enter the filename of the ROM image at the next prompt.
Please enter 'bootfile':hpoa310.bin
The Onboard Administrator will keep trying to download the image until it succeeds.
If this does not complete, you may press
Downloading the ROM...Done!
Verifying ROM image....Done!
Flashing your Onboard Administrator. This will take several minutes.
Do not power off or reset until the process completes
Flashing...
..
..
..Done!
Flash procedure succeeded.
Restarting the Onboard Administrator.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP