- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Upgrading 2920 stack with P IMC
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
11-08-2015 05:16 AM
11-08-2015 05:16 AM
Upgrading 2920 stack with P IMC
Hi,
I'm currently in the process of upgrading our 2920's from WB.15.12.0015 to WB.15.17.0007 and I'm having quite some issues with the 3+ switches stacks.
I'm using IMC 7.0 to deploy the firmware and it has worked just find for standalone switches as well as a 2 switch stacks.
I'm not upgrading my second 3 switches stack and while I thought the first time was some sort of glitch, I encountered the same behavior now.
From my understanding, the master should upgrade and then the rest of the stack should upgrade one switch by one.
The behavior I see is;
Deploy software via IMC - Member 3 upgrades - Member 3 is kicked out of the stack - Upgrade stops
Now I can push the software again so that;
Member 2 upgrades - Member 2 is kicked out of the stack - Upgrade stops
Now I can push the software again so that;
Member 1 upgrades - it reboots - after a few minutes the stacks is operationnal again.
Is that normal? I got a burned a bit on the second stack I upgraded since my uplinks are on member 2 and 3 - I expected the Master to be upgrade last since it was the case on the first stack I upgraded but in my case (master was member 2), it really seems to upgrade from last member to first.
I'd like to be able to upgrade my stacks with a bit more confidence and without having to push the software 3 times.
Thanks to anyone who could shed some light on the process !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2015 07:13 AM
11-11-2015 07:13 AM
Re: Upgrading 2920 stack with P IMC
Hello. I was able to successfully upgrade a 3 member 2920 stack from WB.15.12.0015 to WB.15.17 via IMC 7.1. The process should be:
- Software uploaded to commander
- Commader sync to standby
- Standy sync to other members
No member should be "kicked out" of the stack unless there was some kind of error. Does the log say anything during the upgrade? I also used a fairly basic config. If you want to post your config I can try an upgrade with that.
I 01/01/90 00:35:52 00179 mgr: ST1-CMDR: SME TELNET from 128.44.120.35 - MANAGER Mode
(several logins from IMC)
I 01/01/90 00:40:44 00163 update: ST1-CMDR: Firmware image contains valid signature.
I 01/01/90 00:41:16 00179 mgr: ST1-CMDR: SME TELNET from 128.44.120.35 - MANAGER Mode
I 01/01/90 00:41:34 00537 stacking: ST1-CMDR: Syncing primary OS to standby started
I 01/01/90 00:41:35 00150 update: ST1-CMDR: Primary Image updated.
I 01/01/90 00:42:06 00179 mgr: ST1-CMDR: SME TELNET from 128.44.120.35 - MANAGER
I 01/01/90 00:42:11 00537 stacking: ST1-CMDR: Syncing primary OS to standby complete
I 01/01/90 00:42:13 00179 mgr: ST1-CMDR: SME TELNET from 128.44.120.35 - MANAGER Mode
W 01/01/90 00:42:35 03257 stacking: ST1-CMDR: Reboot of a0b3cc-aaea00 Successful
W 01/01/90 00:42:35 03257 stacking: ST1-CMDR: Reboot of 2c59e5-0bfbc0 Successful