- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Onboard Administrator V3.31 issues
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
Forums
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
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
07-05-2011 07:12 AM
07-05-2011 07:12 AM
Onboard Administrator V3.31 issues
Mark was looking for info on a OA upgrade issue:
******************
Any information on the following issue?
1. EBIPA configuration lost after upgrading OA to 3.31
*****************
Monty replied:
*******************
You did not indicate the previous OA firmware version.
We did have issues with extended configuration info like EBIPA and certificates being lost on reboot of the OA or firmware update prior to OA v3.20.
This issue was fixed in OA v3.20 and documented in the OA Revision History as noted below.
Problems Fixed:
General
Fixed an issue where the enclosure configuration changes are not saved if the following error messages are in the OA Syslog after a settings change:
CONFIG: dhclient.leases has wrong file permissions
CONFIG: Wrong file permissions detected. Please reset to factory defaults.
- The workaround is: Save the OA configuration using GUI or CLI before updating the firmware, then restore the configuration after updating the firmware to ensure that the configuration changes are not lost.
**************
Anyone still having issues?? Please follow the procedure above and let us know if you are having troubles.