- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- FlexFabric Firmware upgrade fail -> Dip switch?
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
09-08-2011 09:26 PM
09-08-2011 09:26 PM
FlexFabric Firmware upgrade fail -> Dip switch?
I tried upgrading my newest Flexfabric from 3.15 to 3.30 using VCSU and it fails. The error in the log is "Module state for Bay 2 is 0. Expected state is 4". Now if I try to upgrade again it says "Previous Firmware update was not completed".
I'm out of ideas but one thing I've noticed on the FF Managment webpage is a setting that says Dip Switch 0x0 but nowhere can I find out what this does or how to change it?
Bay 1 seems ok, only bay 2 has this error. The other issue is that I have stacking failure between Bay 1 and 2 whihc I assume is related (ie Bay 1 can't talk to bay 2 so can't sync firmware upgrade?
Any ideas?