From: Luca Hall (lhall@setnine.com)
Date: Tue Apr 15 2008 - 11:23:04 ART
r4 and r5 connected to the frame-relay switch:
r4(s0/0) -- fr-sw -- (s0/0)r5
r4 uses fr encapsulation of cisco:
r4#sh int s0/0 | in Encap
Encapsulation FRAME-RELAY, loopback not set
r4#sh run int s0/0
interface Serial0/0
ip address 45.1.1.4 255.255.255.0
encapsulation frame-relay
no ip route-cache cef
no ip route-cache
ip ospf network non-broadcast
ip ospf priority 0
frame-relay map ip 45.1.1.5 405
no frame-relay inverse-arp
end
r4#sh ip int brie | i up
Serial0/0 45.1.1.4 YES manual up up
r5 uses frame-relay encapsulation of ietf:
r5#sh int s0/0 | in Encap
Encapsulation FRAME-RELAY IETF, loopback not set
r5#sh run int s0/0
interface Serial0/0
ip address 45.1.1.5 255.255.255.0
encapsulation frame-relay IETF
no ip route-cache cef
no ip route-cache
ip ospf network non-broadcast
frame-relay map ip 45.1.1.4 504 IETF
no frame-relay inverse-arp
end
r5#sh ip int brief | in up
Serial0/0 45.1.1.5 YES manual up up
From everything I have ever read these two shouldn't be able to talk
as encapsulation must match between cpe's, but they can:
r4#ping 45.1.1.5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 45.1.1.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/60/64 ms
I have shut the interfaces in every way I can think of and then saved and
reloaded them both and I still have the same result. I cant figure out why
they can still talk.
Also anyone know a command similar to `debug ip packet dump` for frame
so you could put the frame into a analyzer?
Thanks
Pass the CCIE in six weeks, Guaranteed!
http://www.certscience.com/CCIE
This archive was generated by hypermail 2.1.4 : Thu May 01 2008 - 08:25:51 ART