From: Jason Graun (jgraun@xxxxxxxxxx)
Date: Fri Nov 02 2001 - 18:22:26 GMT-3
Using "backbonefast" and "portfast" can help out. You could also modify
the priority of the switches so that is does not have to go through a
huge election process. The priority is the first variable STP looks at
and if you have a switch set with a better priority then it will be the
new root sooner.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Patel Kamlesh
Sent: Friday, November 02, 2001 2:59 PM
To: 'ccielab@groupstudy.com'
Subject: spanning-tree across four switches
I have Lab setup with four switches without stack mode.
SW1 --------------------Sw2
| |
| |
| |
Sw3-------------------- Sw4
Theses all switches (2924XL) are connected via Gbic Ethernet trunk
(ISL)
port, each switch has same 6 VLANs (VLAN: 100, 110, 120.....)
configured,
Switch 1 is a root for all spanning tree running in VLANs. What is
the
best way to minimize spanning tree recalculation in event of failure of
one
of the link. and also to avoid looping.
Switch :1 configured with :
spanning-tree vlan1 priority 0
spanning-tree vlan 100 priority 0
.........
........
Switch 2:
spanning-tree vlan1 priority 10
spanning-tree vlan 100 priority 10
..............
.............
Switch 3:
spanning-tree vlan1 priority 100
spanning-tree vlan 100 priority 100
.........
.........
Switch 4
spanning-tree vlan1 priority 100
spanning-tree vlan 100 priority 100
..............
............
When I tested for failure with one of the link, It takes time to
recalculate spanning tree. I tried to configure forward-delay 8 and
max-age
10 , but still wanted to know way to minimize down time less than 1-2
sec.
Thanks in advance
Kamlesh
This archive was generated by hypermail 2.1.4 : Fri Jun 21 2002 - 06:45:02 GMT-3