- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Firmware update of VC Flex-10 failed
BladeSystem - General
1748032
Members
5060
Online
108757
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
тАО05-04-2011 03:27 AM
тАО05-04-2011 03:27 AM
Firmware update of VC Flex-10 failed
When updating VC Flex10 modules firmware from 2.34 to 3.17 the process suddenly stopped during activation (5% complete). I've tried to reflash the modules, but support utility states that "Previous firmware update operation on one or more modules is not completed". I tried reseating module in bay 2, and it comes up and seems to be upgraded. The output of healthcheck scares me enough not to reseat bay 1:
-------------------------------------------------------------------------------
Onboard Administrator Information
-------------------------------------------------------------------------------
Version : 3.21
VLAN Tagging : Disabled
-------------------------------------------------------------------------------
Bay 1 : HP VC Flex-10 Enet Module
-------------------------------------------------------------------------------
Power : On
Health : Ok
IP Address : 10.255.34.134
IP Connectivity : Passed
Mode : Primary
Domain Configuration : Not In Sync
Module Configuration : In Sync
-------------------------------------------------------------------------------
Bay 2 : HP VC Flex-10 Enet Module
-------------------------------------------------------------------------------
Power : On
Health : Ok
IP Address : 10.255.34.135
IP Connectivity : Passed
Mode : Unintegrated
Module Configuration : Invalid
If I reseat bay 1 I guess I'll loose the configuration and get some downtime?
Is there a way to upload configuration to bay 2? Or how should I proceed my upgrade without noticable downtime?
What happens if I force an update on modules?
-------------------------------------------------------------------------------
Onboard Administrator Information
-------------------------------------------------------------------------------
Version : 3.21
VLAN Tagging : Disabled
-------------------------------------------------------------------------------
Bay 1 : HP VC Flex-10 Enet Module
-------------------------------------------------------------------------------
Power : On
Health : Ok
IP Address : 10.255.34.134
IP Connectivity : Passed
Mode : Primary
Domain Configuration : Not In Sync
Module Configuration : In Sync
-------------------------------------------------------------------------------
Bay 2 : HP VC Flex-10 Enet Module
-------------------------------------------------------------------------------
Power : On
Health : Ok
IP Address : 10.255.34.135
IP Connectivity : Passed
Mode : Unintegrated
Module Configuration : Invalid
If I reseat bay 1 I guess I'll loose the configuration and get some downtime?
Is there a way to upload configuration to bay 2? Or how should I proceed my upgrade without noticable downtime?
What happens if I force an update on modules?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-04-2011 07:11 AM
тАО05-04-2011 07:11 AM
Re: Firmware update of VC Flex-10 failed
What version of VCSU was used ? (use the 1.5.2 or newer).
Reset the standby module first and wait few minutes (check if the ne FW is activated). Then Reboot the active module. VCSU will take backup from domain config automatically. And if your teaming/bonding is set correctly, there should not be any major connectivity issues.
Reset the standby module first and wait few minutes (check if the ne FW is activated). Then Reboot the active module. VCSU will take backup from domain config automatically. And if your teaming/bonding is set correctly, there should not be any major connectivity issues.
Remember to give Kudos to answers! (click the KUDOS star)
You can find me from Twitter @JKytsi
You can find me from Twitter @JKytsi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-04-2011 10:59 PM
тАО05-04-2011 10:59 PM
Re: Firmware update of VC Flex-10 failed
I'm using VCSU v1.5.2. The problem is that VCSU will not continue reflashing as previous VC firmware is not completed. I guess if I reseat VC in bay 1, it will failover to bay 2 which apparently has no valid configuration or integrated... Will this lead to outage?
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