From: OhioHondo (ohiohondo@columbus.rr.com)
Date: Sat Jan 04 2003 - 21:10:23 GMT-3
Note -- be careful selecting a DLCI on an interface that has several DLCI's.
Let's say you have a sub-interface that allows the router to be the hub in a
hub and spoke and you use "frame maps" for the DLCI's associated with the
spokes. Using one of these DLCI's in a frame map, for the purpose of pinging
the local interface, is OK because the frame map has already disabled
Inverse ARP on those DLCI's.
You also have a sub-interface for a point to point connection -- and you
dynamically learn IP addresses on the point to point connection. Using this
DLCI for the purpose of pinging the local interface causes a problem that
will only be apparent when the router is reloaded. The "frame map" to this
DLCI disables Inverse ARP and when the router is next reloaded the IP
address of the remote side of the point to point will not be learned.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Jay Greenberg
Sent: Saturday, January 04, 2003 1:10 PM
To: ccielab@groupstudy.com
Subject: A Frame Relay router cannot ping itself?
Does anyone know how to allow a router with a frame-relay interface to
be able to ping it's own FR interface? This would make my ping tests
run a lot smoother.
.
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:41 GMT-3