nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

2 11-20
----------------------------------------------------------
---------------------
Egypt(config-mst)# abort
Aborting and exiting region configuration mode
Egypt(config)# spanning-tree mst configuration
Egypt(config-mst)# spanning-tree mst configuration
Egypt(config-mst)# name AGG1
Egypt(config-mst)# revision 10
Egypt(config-mst)# instance 1 vlan 1-10
Egypt(config-mst)# instance 2 vlan 11-20
Egypt(config-mst)# show pending
Pending MST Configuration
Name [AGG1]
Revision 10 Instances configured 3
Instance Vlans mapped
-------- ------------------------------------------------
---------------------
0 21-4094
1 1-10
2 11-20
----------------------------------------------------------
---------------------
Egypt(config-mst)# exit
Egypt(config)#
Because the instance 1 VLAN mapping was input incorrectly, the pending changes were
aborted and reconfigured correctly before exiting/committing.
If PVLANs are used within the environment, it is required that all secondary VLANs share
the same MST instance as their associated primary VLAN. MST provides a mechanism to
automatically enforce this.
Example 2-33 shows VLAN synchronization for MST.
Example 2-33. Private VLAN Synchronization
Click here to view code image
Congo(config)# spanning-tree mst configuration
Congo(config-mst)#private-vlan synchronize
Example 2-34 shows how to verify the spanning tree configuration with the show runningconfig
spanning tree command.
Example 2-34. Verifying MST Configuration