Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

MSTP - Been studying all night :) Did I get it?

psycho.chicken
Regular Advisor

MSTP - Been studying all night :) Did I get it?

So basically MSTP load balances your trunks via vlan id's...

I can send vlans 2,4,6 through oen way and tell 1,3,5 they can use this link IF there main link is down...

this is all providing that the switch has two paths...

does anyone have a sample config i can look at?


What is the root stuff though?
10 REPLIES
Mohieddin Kharnoub
Honored Contributor

Re: MSTP - Been studying all night :) Did I get it?

Hi

Say you have of the 5300 acting as Core switches, and we have 4 Vlans, so we will enable Core1 to be MSTP Root for Vlan1-2 and Backup for Vlan3-4.
Core2 will be MSTP Root for Vlan3-4 and Backup for Vlan1-2.

Core1:
spanning-tree
spanning-tree protocol-version MSTP
spanning-tree config-name "SPAN"
spanning-tree config-revision 8
spanning-tree instance 1 vlan 1 2
spanning-tree instance 1 priority 0
spanning-tree instance 2 vlan 3 4
spanning-tree instance 2 priority 1

Core2:
spanning-tree
spanning-tree protocol-version MSTP
spanning-tree B6 priority 0
spanning-tree config-name "SPAN"
spanning-tree config-revision 8
spanning-tree instance 1 vlan 1 2
spanning-tree instance 1 priority 1
spanning-tree instance 2 vlan 3 4
spanning-tree instance 2 priority 0


This is a Sample Configuration of how to do MSTP on the Core side.

Good Luck !!!
Science for Everyone
Mohieddin Kharnoub
Honored Contributor

Re: MSTP - Been studying all night :) Did I get it?

Just ignore the line :
spanning-tree B6 priority 0

Science for Everyone
psycho.chicken
Regular Advisor

Re: MSTP - Been studying all night :) Did I get it?

I think I got it...

But i'm trying to physically plan my layout...

I have:
5 - stacks of 4 2650 - workstations
2 2900 - servrs
2 - 5400's

I need to run vrrp between the 5400's for failover...
So i need to run trunks from each of the stacks to both the 5400's

So each stack of 4 2650's will have 2 cables (one trunk) to 5400_01 and 2 cables (one trunk) to 5400_02

Would I use MSTP to send all the traffic to 5400_01 or would i use MSTP to split the load between the 2 5400's...

I am under the impressionthat only 1 5400 can have routing enabled... correct?

I would do the same thing with the 2900's they will have a 10G link between them and 10G links to the 5400's... If only one of the 5400's is receiving all the traffic (MSTP routes all traffic to one) then I'd make the 2900's do the same, and route all traffic to the active 5400.

Is this correct?

I'm looking at it this way becuse if i split the traffic between the two 5400's, wouldnt i have to enable routinng on both of them? Or would VRRP enable this to be possible?

I need it completely redundant...

I'm trying to find visio so i can draw this up...
Matt Hobbs
Honored Contributor

Re: MSTP - Been studying all night :) Did I get it?

With your cores both will have 'ip routing' enabled and both need to run VRRP (assuming you have the premium edge license).

One of the core switches will be the VRRP Owner of say VLAN 10,20,30 - it will also be the MSTP Root for those same VLANs.

The other core switch will be the VRRP Owner for the other VLANS, 40,50,60. Once again it will be the MSTP Root for those VLANs.

The edge switches will simply be MSTP Enabled and will be running the same MSTP configuration.
psycho.chicken
Regular Advisor

Re: MSTP - Been studying all night :) Did I get it?

So...

With VRRP enabled then can both have IP Routing...

If VRRP were not enabled, IP Routing on both would be bad...

Yes we do have the premium license...

SO..
With VRRP and the Prem License, do i add both set of vlan IP's to both or does VRRP share the info?

Matt Hobbs
Honored Contributor

Re: MSTP - Been studying all night :) Did I get it?

Even without VRRP you could enable IP routing on both cores switches, they just wouldn't fail over the gateway address if a switch went down.

So with VRRP enabled, if Core1 is the VRRP "owner" of VLANs 10,20,30 you would give them the gateway address that your clients will be using, e.g. 10.10.10.1, 10.20.20.1.

On Core2, it will be a VRRP "backup" and on those same VLANs, 10,20,30, you will give it an IP address such as 10.10.10.2 and 10.20.20.2.

That way, if Core1 fails, Core2 will take ownership of the .1 address and your clients will go about their business without interruption.

In the MSTP example, you would make Core2 the VRRP "owner" for the other VLANs 40,50,60 and give them the .1 address. Core1 would be the VRRP backup and have the .2 address.
psycho.chicken
Regular Advisor

Re: MSTP - Been studying all night :) Did I get it?

Here's teh physical layout, and what makes sence to me.

I have one of the 5400's up and both 2900's

If someone can tell me what to enable where that would be great.

I learn better from seeing the correct way, before i do it 4 times the wrong way...
psycho.chicken
Regular Advisor

Re: MSTP - Been studying all night :) Did I get it?

attatched layout in jpeg.
Below are the three configs.

I need to still do VRRP and MSTP

I'm reading through both of these chaptes in the suggested reading from a few days ago.

If you can point me in the right direction it would be awsome!

WA_5400_01
______________


; J8697A Configuration Editor; Created on release #K.11.33

hostname "WA_5400_PRI"
snmp-server contact "Systems"
max-vlans 25
module 1 type J8702A
module 2 type J8702A
trunk A1,B1 Trk1 Trunk
trunk A2,B2 Trk2 Trunk
ip routing
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged A4-A24,B3-B24
ip address 10.3.100.1 255.255.255.0
tagged Trk1-Trk2
no untagged A3
exit
vlan 10
name "vlan10-d"
ip helper-address 10.3.0.70
ip address 10.3.10.1 255.255.255.0
tagged Trk1-Trk2
exit
vlan 20
name "vlan20-d"
ip helper-address 10.3.0.70
ip address 10.3.20.1 255.255.255.0
tagged Trk1-Trk2
exit
vlan 30
name "vlan30-d"
ip helper-address 10.3.0.70
ip address 10.3.30.1 255.255.255.0
tagged Trk1-Trk2
exit
vlan 40
name "vlan40-d"
ip helper-address 10.3.0.70
ip address 10.3.40.1 255.255.255.0
tagged Trk1-Trk2
exit
vlan 50
name "vlan50-d"
ip helper-address 10.3.0.70
ip address 10.3.50.1 255.255.255.0
tagged Trk1-Trk2
exit
vlan 90
name "vlan90-d"
untagged A3
ip helper-address 10.3.0.70
ip address 10.3.0.200 255.255.255.0
tagged Trk1-Trk2
exit
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
password manager


_______________________________________


WA_2900_01

hostname "WA_2900_01-0"
snmp-server contact "Systems"
max-vlans 20
module 3 type J90XXA
trunk 1-2 Trk1 Trunk
trunk 3-4 Trk2 Trunk
ip default-gateway 10.3.100.1
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
ip address 10.3.100.91 255.255.255.0
tagged A1-A4,Trk1-Trk2
no untagged 5-48
exit
vlan 10
name "vlan10-d"
ip helper-address 10.3.0.70
tagged A1-A4,Trk1-Trk2
no ip address
exit
vlan 20
name "vlan20-d"
ip helper-address 10.3.0.70
tagged A1-A4,Trk1-Trk2
no ip address
exit
vlan 30
name "vlan30-d"
ip helper-address 10.3.0.70
tagged A1-A4,Trk1-Trk2
no ip address
exit
vlan 40
name "vlan40-d"
ip helper-address 10.3.0.70
tagged A1-A4,Trk1-Trk2
no ip address
exit
vlan 50
name "vlan50-d"
ip helper-address 10.3.0.70
tagged A1-A4,Trk1-Trk2
no ip address
exit
vlan 90
name "vlan90-d"
untagged 5-48
ip helper-address 10.3.0.70
tagged A1-A4,Trk1-Trk2
no ip address
exit
stack commander "WA_2900_01"
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
password manager

___________________________________

; J9050A Configuration Editor; Created on release #T.11.12

hostname "WA_2900_02"
snmp-server contact "Systems"
module 3 type J90XXA
trunk 1-2 Trk1 Trunk
trunk 3-4 Trk2 Trunk
ip default-gateway 10.3.100.1
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
ip address 10.3.100.92 255.255.255.0
tagged A1-A4,Trk1-Trk2
no untagged 5-48
exit
vlan 10
name "vlan10-d"
ip helper-address 10.3.0.70
tagged A1-A4,Trk1-Trk2
no ip address
exit
vlan 20
name "vlan20-d"
ip helper-address 10.3.0.70
tagged A1-A4,Trk1-Trk2
no ip address
exit
vlan 30
name "vlan30-d"
ip helper-address 10.3.0.70
tagged A1-A4,Trk1-Trk2
no ip address
exit
vlan 40
name "vlan40-d"
ip helper-address 10.3.0.70
tagged A1-A4,Trk1-Trk2
no ip address
exit
vlan 50
name "vlan50-d"
ip helper-address 10.3.0.70
tagged A1-A4,Trk1-Trk2
no ip address
exit
vlan 90
name "vlan90-d"
untagged 5-48
ip helper-address 10.3.0.70
tagged A1-A4,Trk1-Trk2
no ip address
exit
stack commander "WA_2900_02"
spanning-tree
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
password manager
psycho.chicken
Regular Advisor

Re: MSTP - Been studying all night :) Did I get it?

I just finished reading through the MSTP stuff... again... all 40 pages...

I dont understand teh difference between the regions, instances, ist and cist.

How do i tell one of the switch stacks on teh bottom of my diagram to use one trunk over teh other, unless it is down...?
Matt Hobbs
Honored Contributor

Re: MSTP - Been studying all night :) Did I get it?

Using Mohieddin's examples for the Core's which were posted above, you would use this for all of the other switches:

spanning-tree
spanning-tree protocol-version MSTP
spanning-tree config-name "SPAN"
spanning-tree config-revision 8
spanning-tree instance 1 vlan 1 2
spanning-tree instance 2 vlan 3 4

You only need 2 instances, just specify your VLANs instead of 1,2,3,4.

The config-name and revision are up to you, as long as it's the same on all switches.

The spanning-tree priority which has been set on the Core switches will determine automatically the best path to take. There is no need to force it to go through certain links. In the event of a switch or link failure, it will automatically take another path.

If for whatever reason you must ensure traffic goes one way and not another then you need to understand spanning-tree from the ground up. I would strongly recommend you attend the AEF course which will give you the answers to just about everything you've asked so far: http://www.hp.com/rnd/training/technical/AEF.htm