From: taashour - Digital-X, Inc. at Cisco ("Tamer)
Date: Mon Mar 30 2009 - 18:10:51 ART
Please ignore Problem Solved !!
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Tamer Ashour -X (taashour - Digital-X, Inc. at Cisco)
Sent: Monday, March 30, 2009 1:54 PM
To: ccielab@groupstudy.com
Subject: Bridging over FR
Hi,
Here is the scenario
R2----------SW2---------BB2
.
.
R5----------SW1
Basically the FE on BB2 is 192.10.1.254/24
SW2 has two I/F F0/24 towards BB2 and F0/2 towards R2`s F0/0, both are
in Vlan 100
R2 is connected to R5 through a FR cloud
SW1 F0/5 has ip 192.10.1.7/24 towards R5`s F0/0
Objective is to ping BB2 from SW1 while enabling Bridging on R2 and R5
R2:
interface FastEthernet0/0
no ip address
duplex auto
speed auto
bridge-group 1
!
interface Serial0/0
no ip address
encapsulation frame-relay
frame-relay map bridge 205 broadcast
bridge-group 1
!
bridge 1 protocol ieee
R5:
interface FastEthernet0/0
no ip address
duplex auto
speed auto
bridge-group 1
!
interface Serial0/0
no ip address
encapsulation frame-relay
frame-relay map bridge 502 broadcast
bridge-group 1
!
bridge 1 protocol ieee
SW3560-1#ping 192.10.1.254 repeat 1
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 192.10.1.254, timeout is 2 seconds:
*Mar 1 02:44:10.666: IP: s=192.10.1.7 (local), d=192.10.1.254, len 100,
local feature, Redirection Cli(6), rtype 0, forus FALSE, sendself FALSE,
mtu 0
*Mar 1 02:44:10.666: IP: s=192.10.1.7 (local), d=192.10.1.254, len 100,
local feature, Clustering(7), rtype 0, forus FALSE, sendself FALSE, mtu
0
*Mar 1 02:44:10.666: IP: tableid=0, s=192.10.1.7 (local),
d=192.10.1.254 (FastEthernet0/5), routed via FIB
*Mar 1 02:44:10.666: IP: s=192.10.1.7 (local), d=192.10.1.254
(FastEthernet0/5), len 100, sending
*Mar 1 02:44:10.666: IP: s=192.10.1.7 (local), d=192.10.1.254
(FastEthernet0/5), len 100, output feature, Check hwidb(63), rtype 1,
forus FALSE, sendself FALSE, mtu 0
*Mar 1 02:44:10.666: IP: s=192.10.1.7 (local), d=192.10.1.254
(FastEthernet0/5), len 100, encapsulation failed.
Success rate is 0 percent (0/1)
R2610-2#sh spanning-tree 1
Bridge group 1 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, address 000d.edc8.3460
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 2 last change occurred 01:38:10 ago
from FastEthernet0/0
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 4 (FastEthernet0/0) of Bridge group 1 is forwarding
Port path cost 19, Port priority 128, Port Identifier 128.4.
Designated root has priority 32768, address 000d.edc8.3460
Designated bridge has priority 32768, address 000d.edc8.3460
Designated port id is 128.4, designated path cost 0
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
BPDU: sent 3218, received 13
Port 5 (Serial0/0) of Bridge group 1 is forwarding
Port path cost 647, Port priority 128, Port Identifier 128.5.
Designated root has priority 32768, address 000d.edc8.3460
Designated bridge has priority 32768, address 000d.edc8.3460
Designated port id is 128.5, designated path cost 0
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
BPDU: sent 3208, received 0
R2610-5#sh spanning-tree 1
Bridge group 1 is executing the ieee compatible Spanning Tree protocol
Bridge Identifier has priority 32768, address 0013.1aa8.de80
Configured hello time 2, max age 20, forward delay 15
Current root has priority 32768, address 000d.edc8.3460
Root port is 5 (Serial0/0), cost of root path is 647
Topology change flag not set, detected flag not set
Number of topology changes 1 last change occurred 01:48:25 ago
from Serial0/0
Times: hold 1, topology change 35, notification 2
hello 2, max age 20, forward delay 15
Timers: hello 0, topology change 0, notification 0, aging 300
Port 4 (FastEthernet0/0) of Bridge group 1 is forwarding
Port path cost 19, Port priority 128, Port Identifier 128.4.
Designated root has priority 32768, address 000d.edc8.3460
Designated bridge has priority 32768, address 0013.1aa8.de80
Designated port id is 128.4, designated path cost 647
Timers: message age 0, forward delay 0, hold 0
Number of transitions to forwarding state: 1
BPDU: sent 3252, received 0
Port 5 (Serial0/0) of Bridge group 1 is forwarding
Port path cost 647, Port priority 128, Port Identifier 128.5.
Designated root has priority 32768, address 000d.edc8.3460
Designated bridge has priority 32768, address 000d.edc8.3460
Designated port id is 128.5, designated path cost 0
Timers: message age 1, forward delay 0, hold 0
Number of transitions to forwarding state: 1
BPDU: sent 151, received 3104
I looked up Cisco Doc and the configuration seems fine so it should be
working
I suspect that there are two problems one on R2 as it is sending on the
S0/0 but no receiving any BPDU at all whereas on R5 it is sending and
receiving normally but not receiving on the F0/0, which is the second
problem . When I convert SW2 F0/5 to a switchport the BPDU between R5
and SW1 pass through when I convert it back to a routing port BPDU stop
. So the question is how does a port on a switch differ than that on a
router I mean shouldn't the same happen with BB2 ?
My problem is I don't know how to further troubleshoot, I am quite sure
the path from R2 to BB2 is okay I put an IP and pinged successfully from
R2 . I need guidance on how to further troubleshoot , what debug can I
use ?
Tamer
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Apr 06 2009 - 06:44:08 ART