07-01-2007 02:47 PM - edited 03-03-2019 05:41 PM
Hi all, I'm going through a FR lab and I am seeing some unexpected behavior. Namely, I have a FR hub router with 3 FR spokes, and when I ping from one spoke to another with "debug frame packet" on the hub router I see what appears to be packets smacking into that serial interface.
r1#
*Mar 1 01:43:12.943: Serial1/0(i): dlci 102(0x1861), pkt type 0x800, datagramsize 104
*Mar 1 01:43:12.947: Serial1/0(o): dlci 102(0x1861), pkt type 0x800(IP), datagramsize 60
*Mar 1 01:43:12.951: Serial1/0(o): dlci 103(0x1871), pkt type 0x800(IP), datagramsize 104
This would be fine, but I disabled inArp, and these packets aren't *always* showing up. I can't pin down the pattern. It isn't enough packets to be the interface accepting and then forwarding on the pings (pinging the hub router's int s1/0 results in 10 messages for 5 pings).
Does anyone know what these few packets are, or at least a show/debug combo that would help? I've gone through all the ones remotely logical already, but I'm not all that handy in the FR world.
Configs:
1 - HUB
interface Serial1/0
ip address 131.1.234.1 255.255.255.0
encapsulation frame-relay
serial restart-delay 0
no dce-terminal-timing-enable
frame-relay map ip 131.1.234.1 102
frame-relay map ip 131.1.234.2 102
frame-relay map ip 131.1.234.3 103
frame-relay map ip 131.1.234.4 104
no frame-relay inverse-arp
2 - SPOKE
interface Serial1/0
ip address 131.1.234.2 255.255.255.0
encapsulation frame-relay
serial restart-delay 0
no dce-terminal-timing-enable
frame-relay map ip 131.1.234.1 201
frame-relay map ip 131.1.234.2 201
frame-relay map ip 131.1.234.3 201
frame-relay map ip 131.1.234.4 201
no frame-relay inverse-arp
3 - SPOKE
interface Serial1/0
ip address 131.1.234.3 255.255.255.0
encapsulation frame-relay
serial restart-delay 0
no dce-terminal-timing-enable
frame-relay map ip 131.1.234.1 301
frame-relay map ip 131.1.234.2 301
frame-relay map ip 131.1.234.3 301
frame-relay map ip 131.1.234.4 301
no frame-relay inverse-arp
4 - SPOKE
interface Serial1/0
ip address 131.1.234.4 255.255.255.0
encapsulation frame-relay
serial restart-delay 0
no dce-terminal-timing-enable
frame-relay map ip 131.1.234.1 401
frame-relay map ip 131.1.234.2 401
frame-relay map ip 131.1.234.3 401
frame-relay map ip 131.1.234.4 401
no frame-relay inverse-arp
07-01-2007 03:02 PM
Hi,
do you have CDP or any routing protocol running ?
07-01-2007 03:09 PM
Not yet. I'm just doing basic frame and working through the idiosyncrasies.
07-01-2007 03:08 PM
Well I figured it out. It's working as expected, but for whatever reason, the Hub router's "debug frame packet" isn't picking up the packets most the time. I simply took out the static mapping for 131.1.234.3 on the Hub router and pings between R2 and R3 failed. I'm curious to know why the debug is being fussy, but at least I'm not crazy.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide