- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- 3810 stack member reboot, port down problem
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-05-2016 10:53 AM
10-05-2016 10:53 AM
3810 stack member reboot, port down problem
Hello, we have two 3810's connected with stacking modules. One member is prio 255, the other 200. When we reboot one of the two members, a strange behaviour is observed.
When the switch boots, and is almost joined back to the stack, the ports on the switch go online. However the port status in 'show int bri' has Status of 'down'. It takes about 15 seconds before the switch gives status 'Up' to the ports.
ESXi hosts connected to the switch see an link up and starts to put VM traffic on the link, but because traffic isn't yet forwarded on the switch we get isolated VM's. This again resolves after about 15 seconds, when the switch gives port status 'Up'.
We have disabled spannign tree to test, but same result.
Is this normal behaviour of a stacking switch coming back online?
Kind Regards,
Bastiaan