Three key advantages in your data center are built around architectural flexibility, operational simplicity, and end-to-end visibility. The Cisco NX-OS is designed for each of these three advantages, helping your network operations move at the same speed as your business operations. Today we'll focus on the configuration of this Cisco Software for your mission-critical data center environments.
Cisco NX-OS has added expansions to the Spanning Tree Protocol (STP) that make assembly increasingly proficient. Now and again, despite the fact that comparable usefulness might be fused into the IEEE 802.1w Rapid Spanning Tree Protocol (RSTP) standard, we prescribe utilizing these expansions. These expansions can be utilized with both RPVST+ and MST with available extensions including spanning-tree port types: Bridge Assurance, BPDU Guard, BPDU Filtering, Loop Guard, and Root Guard. Many of these features can be applied either globally or on specified interfaces.
Download the guide and refer back to it at any time!
Understanding STP Port Types
You can arrange a spreading over tree port as an edge port, a system port, or a typical port. A port can be in just one of these states at a given time. The default crossing tree port sort is typical. Contingent upon the kind of gadget to which the interface is associated, you can design spreading over tree port as one of these port sorts.
- STP Edge ports
- STP Networks ports
- STP Normal ports
Spanning Tree Edge Ports
Edge ports, which are connected to hosts, can be either an access port or a trunk port. The edge port interface immediately transitions to the forwarding state, without moving through the blocking or learning states.
Spanning Tree Network Ports
Network ports are connected only to switches or bridges. Bridge Assurance is enabled only on network ports.
Spanning Tree Normal Ports
Normal ports can be connected to either hosts, switches, or bridges. These ports function as normal spanning-tree ports.
STP Extensions Configuration Guidelines
When configuring STP extensions, follow these guidelines:
- Configure all access and trunk ports connected to hosts as edge ports.
- Bridge Assurance runs only on point-to-point spanning-tree network ports. You must configure each side of the link for this feature.
- Loop Guard does not run on spanning-tree edge ports.
- Enabling Loop Guard on ports that are not connected to a point-to-point link will not work.
- You cannot enable Loop Guard if Root Guard is enabled.
Before we get started with the specific configurations, ask yourself a couple of questions:
- Do I have the time to handle configurations?
- Do I have the bandwidth to configure my devices?
If you answered "No" to these questions, consider PivIT's SmartHands through EXTEND. Hire an engineer to take on these basic configurations and more. Click below to learn more about SmartHands.
Configuration of spanning-tree port type
| Command | Purpose | |
| Step 1 | PivIT-Global(Config)# configure terminal |
Enters configuration mode. |
| Step 2 | PivIT-Global(Config)# spanning-tree port type edge default |
Configures all interfaces as edge ports. It assumes all ports are connected to hosts/servers. |
PivIT-Global(Config)# spanning-tree port type network default |
Configures all interfaces as spanning-tree network ports. It assumes all ports are connected to switches and bridges. |
Configuration of spanning-tree port edge in the interface
Here will design the edge port at the interface level with the goal that the port comes up rapidly. It is prescribed to use in host conditions and it could be an access or trunk port. On this port we won't get BPDU so in this respect there will be no spanning circles can make. Design is hereunder
| Command | Purpose | |
| Step 1 | PivIT-Global# configure terminal |
Enters configuration mode. |
| Step 2 | PivIT-Global(Config)# interface type slot/port |
Specifies the interface to configure, and enters the interface configuration mode. |
| Step 3 | PivIT-Global(Config-if)spanning-tree port type edge |
Configures the specified access interfaces to be spanning edge ports. Edge ports immediately transition to the forwarding state without passing through the blocking or learning state at linkup. By default, spanning tree ports are normal port types. |
Configuration of the spanning-tree port network in the interface
| Command | Purpose | |
| Step 1 | PivIT-Global# configure terminal |
Enters configuration mode. |
| Step 2 | PivIT-Global(Config)# interface type slot/port |
Specifies the interface to configure, and enters the interface configuration mode. The interface can be a physical Ethernet port. |
| Step 3 | PivIT-Global(Config-if)spanning-tree port type network |
Configures the specified interfaces to be spanning network ports. If you enable Bridge Assurance, it automatically runs on network ports. By default, spanning tree ports are normal port types. |
Configuration of BPDU Guard in the interface
| Command | Purpose | |
| Step 1 | PivIT-Global# configure terminal |
Enters configuration mode. |
| Step 2 | PivIT-Global(Config)# interface type slot/port |
Specifies the interface to configure, and enters the interface configuration mode. |
| Step 3 | PivIT-Global(Config) # spanning-tree bpduguard { enable | disable } |
Configures the specified access interfaces to be spanning edge ports. Edge ports immediately transition to the forwarding state without passing through the blocking or learning state at linkup. By default, spanning tree ports are normal port types. |
About the Tech Corner
Leave a comment, question, or concern below. We created the Tech Corner to connect with you on Configuration Guides like today's, product discussions, product comparisons, and provide you with information about the industry! Subscribe to the Tech Corner today!