Skip to main content

MST - Best Practices for Core and Access Switch Configurations

In this post, we will configure Multiple Spanning Tree (MST), a protocol designed to optimize spanning tree instances by mapping multiple VLANs to fewer instances. This reduces overhead on network devices, enhances scalability, and speeds up convergence. We'll configure MST on both core/root switches and access switches, ensuring that only the required VLANs are active on each switch. The configuration will focus on assigning VLANs to specific MST instances, defining root priorities, and controlling VLAN availability on trunk links between switches.

This setup ensures efficient traffic flow, minimizes network downtime, and improves overall stability. We'll also define MST regions and revision numbers to maintain consistency across the network. By following this guide, you'll optimize spanning tree operations while maintaining flexibility in VLAN creation and deployment across your infrastructure.


Configuration for Core-SW1 (Primary Root for Instance 1)

! Define MST region and name it "MSTRegion1" with revision number 1

core-sw1(config)# spanning-tree mode mst

core-sw1(config)# spanning-tree mst configuration

core-sw1(config-mst)# name MSTRegion1

core-sw1(config-mst)# revision 1

core-sw1(config-mst)# instance 1 vlan 2-50

core-sw1(config-mst)# instance 2 vlan 51-100

core-sw1(config-mst)# exit

 

! Set priorities to define the root for MST instances

core-sw1(config)# spanning-tree mst 1 priority 4096  ! Primary root for instance 1

core-sw1(config)# spanning-tree mst 2 priority 8192  ! Secondary root for instance 2

 

! Save the configuration

core-sw1# write memory


Configuration for Core-SW2 (Primary Root for Instance 2)

! Define MST region and name it "MSTRegion1" with revision number 1

core-sw2(config)# spanning-tree mode mst

core-sw2(config)# spanning-tree mst configuration

core-sw2(config-mst)# name MSTRegion1

core-sw2(config-mst)# revision 1

core-sw2(config-mst)# instance 1 vlan 2-50

core-sw2(config-mst)# instance 2 vlan 51-100

core-sw2(config-mst)# exit

 

! Set priorities to define the root for MST instances

core-sw2(config)# spanning-tree mst 1 priority 8192  ! Secondary root for instance 1

core-sw2(config)# spanning-tree mst 2 priority 4096  ! Primary root for instance 2

 

! Save the configuration

core-sw2# write memory


Configuration for Access Switches

! Define MST region to match the core switches

access-sw(config)# spanning-tree mode mst

access-sw(config)# spanning-tree mst configuration

access-sw(config-mst)# name MSTRegion1

access-sw(config-mst)# revision 1

access-sw(config-mst)# instance 1 vlan 2-50

access-sw(config-mst)# instance 2 vlan 51-100

access-sw(config-mst)# exit

 

! Configure trunk to Core-SW1

access-sw(config)# interface g1/0/1

access-sw(config-if)# switchport mode trunk

access-sw(config-if)# switchport trunk allowed vlan 2-50,51-100

access-sw(config-if)# exit

 

! Configure trunk to Core-SW2

access-sw(config)# interface g1/0/2

access-sw(config-if)# switchport mode trunk

access-sw(config-if)# switchport trunk allowed vlan 2-50,51-100

access-sw(config-if)# exit

 

! Enable PortFast and BPDU Guard on access ports

access-sw(config)# interface range g0/1-24

access-sw(config-if-range)# spanning-tree portfast

access-sw(config-if-range)# spanning-tree bpduguard enable

access-sw(config-if-range)# exit

 

! Example: Allow VLAN 10 on specific access ports

access-sw(config)# interface range g0/5-8

access-sw(config-if-range)# switchport access vlan 10

access-sw(config-if-range)# spanning-tree portfast

access-sw(config-if-range)# exit

 

! Verify MST configuration

access-sw# show spanning-tree mst configuration

! Verify spanning tree status

access-sw# show spanning-tree mst

! Verify trunk status

access-sw# show interface trunk


Labels:

Comments

Post a Comment

Popular posts from this blog

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.
1 comment
Read more

BGP Soft Reconfiguration vs. Route Refresh: Key Differences and Best Practices

In BGP (Border Gateway Protocol), managing route updates and reapplying new policies can sometimes be challenging, especially if you want to avoid resetting the BGP session. Two methods allow you to update routing policies without tearing down the session: BGP Soft Reconfiguration and BGP Route Refresh . While both methods serve the same purpose, they work differently and have distinct impacts on your router's resources. This post explains the key differences between Soft Reconfiguration and Route Refresh , when to use each, and why Route Refresh is preferred in most modern networks. 1. What is BGP Soft Reconfiguration? BGP Soft Reconfiguration is an older method of applying new policies (like route maps, filters, or prefix lists) without resetting the BGP session. It works by storing a local copy of all the routes received from a BGP neighbor before applying inbound policies. This local route copy allows the router to reprocess the routes when a policy change occurs. How So...
Post a Comment
Read more

BGP Local Preference Controlling Outbound Traffic in BGP

In BGP, Local Preference is used to control the outbound traffic path. It helps you decide which egress point (exit point) should be used when you have multiple connections to external networks, such as ISPs. Local Preference is an attribute that is local to your AS and is shared with all iBGP peers but not with eBGP neighbors. Higher Local Preference = More preferred outbound path. Example Scenario : You have two external links: ISP1 (via CE1) and ISP2 (via CE2). You want traffic to prefer ISP1 for all outbound traffic. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP2): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE1 (Higher Local Preference) : Create a route map to set the local preference to 200 for routes learned from CE1: route-map SET_LOCAL_PREF permit 10 set local-preference 200 In the BGP configuration for CE1, apply this route map to the neighbor: router bgp 65001 ne...
Post a Comment
Read more