Differences

This shows you the differences between two versions of the page.

--- arista:switch:stp_commands [2020/11/11 01:02] – created hvillanueva
+++ arista:switch:stp_commands [2020/11/11 01:32] – hvillanueva
@@ Line 208: / Line 208: @@
 When loop protection is disabled (at the VLAN or interface level), the computed state of the interface is forgotten and packets queued to be sent are dropped. If an interface is err-disabled by loop protection, disabling loop protection removes the err-disable.
+{{:arista:switch:stp_arista_20_-_hvillanueva.png?800|}}
+==== monitor loop-protection ====
+The monitor loop-protection command places the switch in loop-protection configuration mode.
+{{:arista:switch:stp_arista_21_-_hvillanueva.png?800|}}
+==== protect vlan ====
+The protect vlan command specifies which VLANs will participate in loop protection. The no protect vlan and default protect vlan commands remove loop protection from the specified VLANs.
+{{:arista:switch:stp_arista_22_-_hvillanueva.png?800|}}
+==== rate-limit ====
+The rate-limit command sets the maximum number of loop detection frames which can be sent by the switch per second. The no rate-limit and default rate-limit commands return the rate limit to the default value of 1000.
+{{:arista:switch:stp_arista_23_-_hvillanueva.png?800|}}
+==== shutdown (Loop-protection) ====
+The shutdown (Loop-protection) command disables loop protection globally. The feature is disabled by default, and is enabled by using the no shutdown (Loop-protection) command.
+**Note:** To function, loop protection must also be enabled on a per-VLAN basis using the protect vlan command.
+{{:arista:switch:stp_arista_24_-_hvillanueva.png?800|}}
+==== transmit-interval ====
+The transmit-interval command sets the interval at which loop detection packets are transmitted. The no transmit-interval and default transmit-interval commands restore the transmission interval to the default of 5 seconds.
+{{:arista:switch:stp_arista_25_-_hvillanueva.png?800|}}
+===== Spanning Tree Commands: Interface Configuration Mode =====
+==== spanning-tree bpdufilter ====
+The spanning-tree bpdufilter command controls bridge protocol data unit (BPDU) filtering on the configuration mode interface. BPDU filtering is disabled by default.
+•spanning-tree bpdufilter enabled enables BPDU filtering.
+•spanning-tree bpdufilter disabled disables BPDU filtering by removing the spanning-tree bpdufilter command from running-config.
+The BPDU filter default setting for portfast ports is configured by the spanning-tree edge-port bpdufilter default command; BPDU filter is disabled by default on all non-portfast ports.
+The no spanning-tree bpdufilter and default spanning-tree bpdufilter commands restore the global BPDU filter setting on the configuration mode interface by removing the corresponding spanning-tree bpdufilter command from running-config.
+{{:arista:switch:stp_arista_26_-_hvillanueva.png?800|}}
+==== spanning-tree bpduguard ====
+The spanning-tree bpduguard command controls BPDU guard on the configuration mode interface. A BPDU guard-enabled port is disabled when it receives a BPDU packet.
+The BPDU guard default setting for portfast ports is configured by the spanning-tree edge-port bpduguard default command; BPDU guard is disabled by default on all non-portfast ports.
+The no spanning-tree bpduguard and default spanning-tree bpduguard commands restore the global BPDU guard setting on the configuration mode interface by removing the corresponding spanning-tree bpduguard command from running-config.
+{{:arista:switch:stp_arista_27_-_hvillanueva.png?800|}}
+==== spanning-tree bpduguard rate-limit count (interface) ====
+The spanning-tree bpduguard rate-limit count command configures the maximum BPDU reception rate for the configuration mode interface. The default rate limit is specified by the spanning-tree bpduguard rate-limit count (global) command.
+BPDU rate limiting restricts the number of BPDUs that ports with BPDU guard or BPDU filter disabled can process during a specified interval. Ports discard BPDUs it receives in excess of the specified limit. BPDU rate limiting is enabled or disabled by spanning-tree bpduguard rate-limit enable / disable commands.
+The no spanning-tree bpduguard rate-limit count and default spanning-tree bpduguard rate-limit count commands restore the interface value to the global setting by removing the corresponding spanning-tree bpduguard rate-limit count command from running-config.
+{{:arista:switch:stp_arista_28_-_hvillanueva.png?800|}}
+==== spanning-tree bpduguard rate-limit enable / disable ====
+These commands enable and disable BPDU rate limiting on the configuration mode interface:
+•spanning-tree bpduguard rate-limit enable enables BPDU rate limiting.
+•spanning-tree bpduguard rate-limit disable disables BPDU rate limiting.
+The spanning-tree bpduguard rate-limit default command enables BPDU rate limiting on all ports not configured with a spanning-tree bpduguard rate-limit command.
+BPDU rate limiting restricts the number of BPDUs that ports with BPDU guard or BPDU filter disabled can process during a specified interval. Ports discard BPDUs it receives in excess of the specified limit. BPDU rate limits are established by spanning-tree bpduguard rate-limit count (interface) commands.
+The no spanning-tree bpduguard rate-limit and default spanning-tree bpduguard rate-limit commands restore the global rate limit setting on the configuration mode interface by removing the corresponding spanning-tree bpduguard rate-limit command from running-config.
+{{:arista:switch:stp_arista_29_-_hvillanueva.png?800|}}
+==== spanning-tree cost ====
+The spanning-tree cost command configures the path cost of the configuration mode interface. Cost values range from 1 to 200000000 (200 million). The default cost depends on the interface speed:
+•1 gigabit interface: cost = 20000
+•10 gigabit interface: cost = 2000
+The spanning-tree cost command provides a mode option:
+•RST instance cost is configured by not including a mode.
+•MST instance 0 cost is configured by not including a mode or with the mst mode option.
+•MST instance cost is configured with the mst mode option.
+•Rapid-PVST VLAN cost is configured with the vlan mode option.
+The no spanning-tree cost and default spanning-tree cost commands restore the default cost on the configuration mode interface by removing the corresponding spanning-tree cost command from running-config.
+{{:arista:switch:stp_arista_30_-_hvillanueva.png?800|}}
+==== spanning-tree guard ====
+The spanning-tree guard command enables root guard or loop guard on the configuration mode interface. The spanning-tree guard loop default command configures the global loop guard setting.
+•Root guard prevents a port from becoming a root or blocked port. A root guard port that receives a superior BPDU transitions to the root-inconsistent (blocked) state.
+•Loop guard protects against loops resulting from unidirectional link failures on point-to-point links by preventing non-designated ports from becoming designated ports. When loop guard is enabled, a root or blocked port transitions to loop-inconsistent (blocked) state if it stops receiving BPDUs from its designated port. The port returns to its prior state when it receives a BPDU.
+The no spanning-tree guard and default spanning-tree guard commands sets the configuration mode interface to the global loop guard mode by removing the spanning-tree guard statement from running-config. The spanning-tree guard none command disables loop guard and root guard on the interface, overriding the global setting.
+{{:arista:switch:stp_arista_31_-_hvillanueva.png?800|}}
+==== spanning-tree link-type ====
+The spanning-tree link-type command specifies the configuration mode interface’s link type, which is normally derived from the port’s duplex setting. The default setting depends on a port’s duplex mode:
+•full-duplex ports are point-to-point.
+•half-duplex ports are shared.
+The no spanning-tree link-type and default spanning-tree link-type commands restore the default link type on the configuration mode interface by removing the corresponding spanning-tree link-type command from running-config.
+{{:arista:switch:stp_arista_32_-_hvillanueva.png?800|}}
+==== spanning-tree port-priority ====
+The spanning-tree port-priority command specifies the configuration mode interface’s port-priority number. The switch uses this number to determine which interface it places into forwarding mode when resolving a loop. Valid settings are all multiples of 16 between 0 and 240. Default value is 128. Ports with lower numerical priority values are selected over other ports.
+The no spanning-tree port-priority and default spanning-tree port-priority commands restore the default of 128 for the configuration mode interface by removing the spanning-tree port-priority command from running-config.
+The spanning-tree port-priority command provides a mode option:
+•RST instance port-priority is configured by not including a mode.
+•MST instance 0 port-priority is configured by not including a mode or with the mst mode option.
+•MST instance port-priority is configured with the mst mode option.
+•Rapid-PVST VLAN port-priority is configured with the vlan mode option.
+{{:arista:switch:stp_arista_33_-_hvillanueva.png?800|}}
+==== spanning-tree portfast ====
+The spanning-tree portfast command programs configuration mode ports to immediately enter forwarding state when they establish a link. PortFast ports are included in spanning tree topology calculations and can enter discarding state. This command overrides the spanning-tree portfast auto command.
+The no spanning-tree portfast and default spanning-tree portfast commands remove the corresponding spanning-tree portfast command from running-config.
+{{:arista:switch:stp_arista_34_-_hvillanueva.png?800|}}
+==== spanning-tree portfast auto ====
+The spanning-tree portfast auto command enables auto-edge detection on the configuration mode interface. When auto-edge detection is enabled, the port is configured as an edge port if it does not receive a new BPDU before the current BPDU expires. Auto-edge detection is enabled by default. The spanning-tree portfast command, when configured, has priority over this command.
+The no spanning-tree portfast auto command disables auto-edge port detection. This command is removed from running-config with the spanning-tree portfast auto and default spanning-tree portfast auto commands.
+{{:arista:switch:stp_arista_35_-_hvillanueva.png?800|}}
+==== spanning-tree portfast <port type> ====
+The spanning-tree portfast <port-type> command specifies the STP port mode for the configuration mode interface. Default port mode is normal.
+Port modes include:
+•Edge: Edge ports connect to hosts and transition to the forwarding state when the link is established. An edge port that receives a BPDU becomes a normal port.
+•Network: Network ports connect only to switches or bridges and support bridge assurance. Network ports that connect to hosts or other edge devices transition to the discarding state.
+•Normal: Normal ports function as normal STP ports and can connect to any type of device.
+The no spanning-tree portfast <port-type> and default spanning-tree portfast <port-type> commands restore the default port mode of normal by removing the corresponding spanning-tree portfast <port-type> command from running-config.
+{{:arista:switch:stp_arista_36_-_hvillanueva.png?800|}}
+==== switchport backup-link ====
+The switchport backup-link command establishes a primary-backup configuration for forwarding VLAN traffic between the command mode interface and a specified interface. The show interfaces switchport backup-link command displays
+the state of backup interface pairs on the switch:
+•the primary interface is the command mode interface.
+•the backup interface is the interface specified in the command.
+The following guidelines apply to primary and backup interfaces.
+•Ethernet and Port Channels can be primary interfaces.
+•Ethernet, Port Channel, Management, Loopback, and VLANs can be backup interfaces.
+•The primary and backup interfaces can be different interface types.
+•Interface pairs should be similarly configured to ensure consistent behavior.
+•An interface can be associated with a maximum of one backup interface.
+•An interface can back up a maximum of one interface.
+•Any Ethernet interface configured in an interface pair cannot be a port channel member.
+•The STP mode is backup.
+•Static MAC addresses should be configured after primary-backup pairs are established.
+When load balancing is not enabled, the primary and backup interfaces cannot simultaneously forward VLAN traffic. When the primary interface is forwarding VLAN traffic, the backup interface drops all traffic. If the primary interface fails, the backup interface forwards VLAN traffic until the primary interface is functional.
+The prefer vlan option balances the load across the primary and backup interfaces. When the command includes the prefer vlan option, each interface is the primary for a subset of the vlans carried by the pair. When both interfaces are up, prefer option vlans are forwarded on the backup interface and all other configured vlans are carried by the primary interface.
+The no switchport backup-link and default switchport backup-link commands remove the primary-backup configuration for the configuration mode interface.
+{{:arista:switch:stp_arista_37_-_hvillanueva.png?800|}}