From: shiran guez (shiranp3@gmail.com)
Date: Fri Sep 28 2007 - 08:24:21 ART
R3-------
|-----R1
R2-------
R1 is used as FR Hub for R2 and R3
I am trying to set R1 as Bridge between R2 and R3
I used R1 /2/3 Point to Point Interface
R1
!
interface Serial1/0
no ip address
encapsulation frame-relay
no ip route-cache
serial restart-delay 0
!
interface Serial1/0.1 point-to-point
no ip route-cache
frame-relay interface-dlci 102
bridge-group 1
!
interface Serial1/0.2 point-to-point
no ip route-cache
frame-relay interface-dlci 103
bridge-group 1
no ip routing
bridge 1 protocol ieee
end
R1#sh bridge 1 group
Bridge Group 1 is running the IEEE compatible Spanning Tree protocol
Port 12 (Serial1/0.1 Frame Relay) of bridge group 1 is forwarding
Port 13 (Serial1/0.2 Frame Relay) of bridge group 1 is forwarding
R1#sh spanning-tree 1 brief
Bridge group 1
Spanning tree enabled protocol ieee
Root ID Priority 32768
Address 0000.0c45.dae8
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Bridge ID Priority 32768
Address 0000.0c45.dae8
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
Aging Time 300
Interface Designated
Name Port ID Prio Cost Sts Cost Bridge ID Port
ID
-------------------- ------- ---- ----- --- ----- --------------------
-------
Serial1/0.1 128.12 128 647 FWD 0 32768 0000.0c45.dae8
128.12
Serial1/0.2 128.13 128 647 FWD 0 32768 0000.0c45.dae8
128.13
R2
R2#sh run int ser1/0.1
Building configuration...
Current configuration : 119 bytes
!
interface Serial1/0.1 point-to-point
ip address 182.158.123.2 255.255.255.0
frame-relay interface-dlci 201
R3
R3#sh run int ser1/0.1
Building configuration...
Current configuration : 119 bytes
!
interface Serial1/0.1 point-to-point
ip address 182.158.123.3 255.255.255.0
frame-relay interface-dlci 301
but I do not understand why i cant ping between R2 to R3 as it look like the
bridge is FWD and working ok all the interface are point to point so there
should not be a encapsulation error of resolving layer 2 to 3 or layer 2 to
2 on the bridge
R2#debug ip packet detail
IP packet debugging is on (detailed)
R2#ping 182.158.123.3 re 1
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 182.158.123.3, timeout is 2 seconds:
*Mar 1 00:36:11.215: IP: tableid=0, s=182.158.123.2 (local), d=
182.158.123.3 (Serial1/0.1), routed via FIB
*Mar 1 00:36:11.219: IP: s=182.158.123.2 (local),
d=182.158.123.3(Serial1/0.1), len 100, sending
*Mar 1 00:36:11.219: ICMP type=8, code=0.
Success rate is 0 percent (0/1)
R3#debug ip packet detail
IP packet debugging is on (detailed)
R3#ping 182.158.123.2 re 1
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 182.158.123.2, timeout is 2 seconds:
*Mar 1 00:36:57.651: IP: tableid=0, s=182.158.123.3 (local), d=
182.158.123.2 (Serial1/0.1), routed via FIB
*Mar 1 00:36:57.655: IP: s=182.158.123.3 (local),
d=182.158.123.2(Serial1/0.1), len 100, sending
*Mar 1 00:36:57.655: ICMP type=8, code=0.
Success rate is 0 percent (0/1)
so you see there is no problem sending on both sides
also I am getting on the DLCI 0x4242 Spaning tree frames
R3#debug frame-relay packet
Frame Relay packet debugging is on
*Mar 1 00:40:34.571: Serial1/0(i): dlci 301(0x48D1), pkt type 0x4242,
datagramsize 39
R3#
*Mar 1 00:40:40.575: Serial1/0(i): dlci 301(0x48D1), pkt type 0x4242,
datagramsize 39
R3#
*Mar 1 00:40:42.571: Serial1/0(i): dlci 301(0x48D1), pkt type 0x4242,
datagramsize 39
R3#
I am missing here something stupid for sure
-- Shiran Guez MCSE CCNP NCE1 http://cciep3.blogspot.com
This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:16 ART