From: Don (seadon@attbi.com)
Date: Mon Dec 16 2002 - 15:11:59 GMT-3
Make sure you do not have 3550's with the spanning tree bug. Cisco shipped
about 6000 of them on which spanning tree did not work correctly. Upgrading
to the latest image does fix these defective units, however. The test is to
connect two access ports on the same vlan on the same switch back to back
with a reverse cable and see if one goes into blocking, which can be seen by
the front panel port status lights. If both go green and stay green after
60 seconds, you have a defective unit. If one is yellow after 60 seconds,
your unit is ok.
Don
----- Original Message -----
From: "chrisa" <chris_atkins@blueyonder.co.uk>
To: <ccielab@groupstudy.com>
Sent: Monday, December 16, 2002 9:09 AM
Subject: Re: spanning tree help please
> Sorry diagram did not come out.
>
> sw1 ------------------- :sw2
>
>
>
> sw1--------------------sw2
>
>
> isl trunk vlan 1 &100 on both connections.
>
>
> ----- Original Message -----
> From: "chrisa" <chris_atkins@blueyonder.co.uk>
> To: <ccielab@groupstudy.com>
> Sent: Monday, December 16, 2002 4:53 PM
> Subject: spanning tree help please.
>
>
> > Hi
> > I am going mad I have the following set up.
> >
> >
> >
> >
> > =20
> >
> > =20
> >
> > =20
> > =20
> > =20
> >
> > =20
> >
> > =20
> >
> >
> >
> >
> > Isl
> >
> > =20
> >
> > =20
> > Switch2=20
> > =20
> > =20
> > =20
> >
> >
> > =20
> >
> >
> >
> > =20
> > =20
> > =20
> >
> > =20
> >
> > =20
> >
> >
> >
> > There is a ISL trunk on both links but spanning =
> > tree is not working on any vlan.
> >
> > Both 3550 are set up as below (identical results )
> >
> > On eiher switch you do not receive BPDU but do send so both become =
> > roots.
> >
> > Am I missing something here should not one of the ports go into =
> > blocking mode for vlan 100????
> >
> >
> >
> >
> >
> > version 12.1
> > no service pad
> > service timestamps debug uptime
> > service timestamps log uptime
> > no service password-encryption
> > !
> > hostname switch1
> > !
> > !
> > ip subnet-zero
> > !
> > spanning-tree extend system-id
> > !
> > !
> > !
> > interface GigabitEthernet0/1
> > switchport trunk encapsulation isl
> > switchport mode trunk
> > no ip address
> > !
> > interface GigabitEthernet0/2
> > switchport trunk encapsulation isl
> > switchport mode trunk
> >
> >
> >
> > switch1#sh spanning-tree vlan 100=20
> >
> > VLAN100 is executing the ieee compatible Spanning Tree protocol
> > Bridge Identifier has priority 32768, sysid 100, address =
> > 000a.410b.ce80
> > Configured hello time 2, max age 20, forward delay 15
> > We are the root of the spanning tree
> > Topology change flag not set, detected flag not set
> > Number of topology changes 1 last change occurred 00:01:51 ago
> > from GigabitEthernet0/1
> > Times: hold 1, topology change 35, notification 2
> > hello 2, max age 20, forward delay 15=20
> > Timers: hello 1, topology change 0, notification 0, aging 300
> >
> > Port 1 (GigabitEthernet0/1) of VLAN100 is forwarding
> > Port path cost 4, Port priority 128, Port Identifier 128.1.
> > Designated root has priority 32868, address 000a.410b.ce80
> > Designated bridge has priority 32868, address 000a.410b.ce80
> > Designated port id is 128.1, designated path cost 0
> > Timers: message age 0, forward delay 0, hold 0
> > Number of transitions to forwarding state: 1
> > BPDU: sent 70, received 0
> >
> > Port 2 (GigabitEthernet0/2) of VLAN100 is forwarding
> > Port path cost 4, Port priority 128, Port Identifier 128.2.
> > Designated root has priority 32868, address 000a.410b.ce80
> > Designated bridge has priority 32868, address 000a.410b.ce80
> > Designated port id is 128.2, designated path cost 0
> > Timers: message age 0, forward delay 0, hold 0
> > Number of transitions to forwarding state: 1
> > BPDU: sent 70, received 0version 12.1
> >
> >
> >
> >
> >
> >
> >
> >
> > no service pad
> > service timestamps debug uptime
> > service timestamps log uptime
> > no service password-encryption
> > !
> > hostname switch2
> > !
> > !
> > ip subnet-zero
> > !
> > spanning-tree extend system-id
> > !
> > !
> > !
> > interface GigabitEthernet0/1
> > switchport trunk encapsulation isl
> > switchport mode trunk
> > no ip address
> > !
> > interface GigabitEthernet0/2
> > switchport trunk encapsulation isl
> > switchport mode trunk
> > no ip address
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > VLAN100 is executing the ieee compatible Spanning Tree protocol
> > Bridge Identifier has priority 32768, sysid 100, address =
> > 000a.410b.d200
> > Configured hello time 2, max age 20, forward delay 15
> > We are the root of the spanning tree
> > Topology change flag not set, detected flag not set
> > Number of topology changes 1 last change occurred 00:06:29 ago
> > from GigabitEthernet0/1
> > Times: hold 1, topology change 35, notification 2
> > hello 2, max age 20, forward delay 15=20
> > Timers: hello 1, topology change 0, notification 0, aging 300
> > =20
> > Port 1 (GigabitEthernet0/1) of VLAN100 is forwarding
> > Port path cost 4, Port priority 128, Port Identifier 128.1.
> > Designated root has priority 32868, address 000a.410b.d200
> > Designated bridge has priority 32868, address 000a.410b.d200
> > Designated port id is 128.1, designated path cost 0
> > Timers: message age 0, forward delay 0, hold 0
> > Number of transitions to forwarding state: 1
> > BPDU: sent 209, received 0
> > =20
> > Port 2 (GigabitEthernet0/2) of VLAN100 is forwarding
> > Port path cost 4, Port priority 128, Port Identifier 128.2.
> > Designated root has priority 32868, address 000a.410b.d200
> > Designated bridge has priority 32868, address 000a.410b.d200
> > Designated port id is 128.2, designated path cost 0
> > Timers: message age 0, forward delay 0, hold 0
> > Number of transitions to forwarding state: 1
> > BPDU: sent 209, received 0
> >
> >
> >
> > =20
> >
> > =20
> >
> > [GroupStudy.com removed an attachment of type image/gif which had a name
> of clip_image001.gif]
> > .
> .
.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:46 GMT-3