- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Re: 2910al stack members not managing properly in ...
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
10-26-2011 01:25 PM
10-26-2011 01:25 PM
2910al stack members not managing properly in stack when I upgrade from firmware w.14.38 to w.14.49
Background: Stack works fine with the w.14.38 firmware. Commander has an address on the primary vlan, members have no addresses but are set up with their trunk uplink ports to the commander as tagged in the primary vlan (stacking protocol apparently works across the primary VLAN). Their primary vlan ID is the same as the commander's. The primary vlan is no longer Default vlan ID 1. The Commander has an admin password set. I then upgraded the firmware on the members & set it as boot default image, ending with the upgrade of the commander. I have subsequently rebooted them all several times but the problem still occurs.
The problem: I can connect to the commander web interface fine, but when I switch the dropdown to a member switch, all I get is the HTML "page can't be displayed" message in the frame. I've checked the web agents on the members are enabled (plaintext not SSL). The 'show stack' option of the web interface shows all members as up.
If I connect over telnet to the Commander, and try to logon as admin it just hangs (perhaps because it would normally present an option just after logon to select the stack member I want to manage, but because stacking is messed up I think this is why it hangs here). If I logon as read-only and enable myself as Admin I can get in. When I view stacking (all) in the telnet menu system it says the members are up and connected. If I then view stacking (this switch) it hangs indefinately. If I then force disconnect the telnet session and go back in I can't then even run the menu utility 2nd time around (I just get the menu banner appear and no menu ... it just hangs there!
Has anyone encountered this before? (I've reverted to the older secondary image for now and it's running OK on that).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2012 12:23 AM
01-11-2012 12:23 AM
Re: 2910al stack members not managing properly in stack when I upgrade from firmware w.14.38 to w.14
Hi,
Did you ever resolve this issue? I'm having also the same problems with this firmware. Perhaps I need to roll back to version 14.38
Kind Regards,
Geert Reijnders
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2012 04:46 AM
01-26-2012 04:46 AM
Re: 2910al stack members not managing properly in stack when I upgrade from firmware w.14.38 to w.14
Hi guys
This is fixed in W.14.67. It's not available from the HPN website, but call support and you get the current W.14.69.
HTH,
Arimo
HPE Networking Engineer