Hi there,
I have a stub network comprising two Cisco 805 routers linked via a 64K serial link. The link is configured for HDLC encapsulation. AT one end is a remote site, the other links into the main LAN/WAN network. The link is setup as a bridge, the main LAN/WAN network is mainly routed but OSI traffic is bridged around the Core network. I can telnet into the 805 at the Core site and ping across the link. I can telnet into the remote router, however I am unable to get back past the Core site router onto the rest of the LAN/WAN. If I do a show span on the Core site I get:
Bridge group 80 is executing the IEEE compatible Spanning Tree protocol
The IEEE bridge domain for this group is 4
Bridge Identifier has priority 32768, address 0002.1763.bd93
Configured hello time 2, max age 20, forward delay 15
Current root has priority 0, address 0003.a00b.8000
Root port is 3 (Ethernet0), cost of root path is 1119
Port Number size is 9
Topology change flag set, detected flag not set
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0
bridge aging time 15
Port 2 (Serial0) of Bridge group 80 is disabled
Port path cost 15625, Port priority 128
Designated root has priority 0, address 0003.a00b.8000
Designated bridge has priority 32768, address 0002.1763.bd93
Designated port is 2, path cost 1119
Timers: message age 0, forward delay 0, hold 0
BPDU: sent 0, received 0
Port 3 (Ethernet0) of Bridge group 80 is blocking
Port path cost 100, Port priority 128
Designated root has priority 0, address 0003.a00b.8000
Designated bridge has priority 32768, address 00e0.4fc9.4400
Designated port is 193, path cost 1019
Timers: message age 19, forward delay 13, hold 0
BPDU: sent 165, received 2554
It appears that a Cisco device (0003.a00b.8000) is broadcasting itself as a Root Bridge with a priority of 0. I am unable to locate this device ( and I'm sure its not one of my routers! )
Anyone any ideas how I can stop this putting my ethernet port into blocking mode?
Regards,
Doug
I have a stub network comprising two Cisco 805 routers linked via a 64K serial link. The link is configured for HDLC encapsulation. AT one end is a remote site, the other links into the main LAN/WAN network. The link is setup as a bridge, the main LAN/WAN network is mainly routed but OSI traffic is bridged around the Core network. I can telnet into the 805 at the Core site and ping across the link. I can telnet into the remote router, however I am unable to get back past the Core site router onto the rest of the LAN/WAN. If I do a show span on the Core site I get:
Bridge group 80 is executing the IEEE compatible Spanning Tree protocol
The IEEE bridge domain for this group is 4
Bridge Identifier has priority 32768, address 0002.1763.bd93
Configured hello time 2, max age 20, forward delay 15
Current root has priority 0, address 0003.a00b.8000
Root port is 3 (Ethernet0), cost of root path is 1119
Port Number size is 9
Topology change flag set, detected flag not set
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0
bridge aging time 15
Port 2 (Serial0) of Bridge group 80 is disabled
Port path cost 15625, Port priority 128
Designated root has priority 0, address 0003.a00b.8000
Designated bridge has priority 32768, address 0002.1763.bd93
Designated port is 2, path cost 1119
Timers: message age 0, forward delay 0, hold 0
BPDU: sent 0, received 0
Port 3 (Ethernet0) of Bridge group 80 is blocking
Port path cost 100, Port priority 128
Designated root has priority 0, address 0003.a00b.8000
Designated bridge has priority 32768, address 00e0.4fc9.4400
Designated port is 193, path cost 1019
Timers: message age 19, forward delay 13, hold 0
BPDU: sent 165, received 2554
It appears that a Cisco device (0003.a00b.8000) is broadcasting itself as a Root Bridge with a priority of 0. I am unable to locate this device ( and I'm sure its not one of my routers! )
Anyone any ideas how I can stop this putting my ethernet port into blocking mode?
Regards,
Doug
