Frame relay

From: Richard Dumoulin (richard.dumoulin@vanco.es)
Date: Mon Apr 12 2004 - 12:31:59 GMT-3


I still don't know after some years in the field now why when pinging the
local frame relay interface the packet delays are twice longer than when
pinging the remote router.
Is there any reason for this ?

Rack1R3#sh run int se 0/0
Building configuration...

Current configuration:
!
interface Serial0/0
 ip address 163.1.35.3 255.255.255.0
 no ip directed-broadcast
 encapsulation frame-relay
 no ip mroute-cache
 no fair-queue
 clockrate 64000
 frame-relay map ip 163.1.35.3 305
 frame-relay map ip 163.1.35.5 305 broadcast
 no frame-relay inverse-arp
end

Rack1R3#ping 163.1.35.5

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 163.1.35.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 144/144/145 ms
Rack1R3#ping 163.1.35.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 163.1.35.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 284/285/288 ms
Rack1R3#trace 163.1.35.5

Type escape sequence to abort.
Tracing the route to 163.1.35.5

  1 163.1.35.5 80 msec * 76 msec
Rack1R3#trace 163.1.35.3

Type escape sequence to abort.
Tracing the route to 163.1.35.3

  1 163.1.35.5 76 msec 81 msec 128 msec
  2 163.1.35.3 156 msec * 156 msec



This archive was generated by hypermail 2.1.4 : Mon May 03 2004 - 19:48:46 GMT-3