- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Spanning Tree Topology Change Notification on CISC...
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
03-04-2011 12:03 PM
03-04-2011 12:03 PM
Spanning Tree Topology Change Notification on CISCO 3120x StackWise Port
Mitch had a customer experiencing Cisco 3120x issues:
****************
Hello,
I have a customer with several C7000 enclosures. Each has two CISCO 3120X switches and four Cisco 3020g switches. The switches are stacked together with the StackWise ports. When the customer has a bare metal blade in the enclosure (no OS loaded yet), they get a Spanning Tree Topology Change Notification from the StackWise port when the bare metal server is powered-on. The notification goes away once they power off the bare metal blade.
Anyone have an idea of why this is occurring? They’re seeing this on all of their enclosures.
*************
From Hongjun:
Do they have “portfast” feature enabled on 3120/3020 downlinks facing blades? It should be design best practice to enable it when connecting to servers.
TCN generation has nothing to do with server OS. 3120/3020 has no idea which kind of os is running on blade. If you don’t have portfast configured for downlink ports, anytime you power off/on servers which causes interfaces up/down on the switch, it’ll generate TCN for SPT.
Reply from Mitch:
Thank you for the response. I spoke to the customer today and he confirmed that he does have portfast enabled on the downlinks and also on the uplinks going from the 3120x switches up to their core. The customer does trunk downlinks on some of the CISCO switches in their enclosures. He was wondering if by using trunked downlinks he may be overriding portfast.
From Carlos:
PortFast is not override when the uplinks are trunked. A Cisco Trunk (dot1q) means multiple VLANs going across the uplinks. This configuration does not affect anything on the downlinks ports. Now what I do find an issue is PortFast enabled on the Uplinks connected to their core. Portfast is to be enabled only on ports that connect end stations to switches. If PortFast is enabled on ports connecting two switches then Spanning-Tree loops can occur.
Here is a good Cisco document on PortFast, BPDU Filters and BPDU Guard:
**********************
Any other comments or input for Mitch??