From: Jonathan V Hays (jhays@jtan.com)
Date: Fri Mar 28 2003 - 15:00:33 GMT-3
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/
wan_r/wrdfrely.htm#1019514
"This implementation of Inverse ARP is based on RFC 1293. It allows a
router or access server running Frame Relay to discover the protocol
address of a device associated with the virtual circuit.
In Frame Relay, permanent virtual circuits (PVCs) are identified by a
DLCI, which is the equivalent of a hardware address. By exchanging
signaling messages, a network announces a new virtual circuit, and with
Inverse ARP, the protocol address at the other side of the circuit can
be discovered.
The show frame-relay map command displays the word "dynamic" to flag
virtual circuits that are created dynamically by Inverse ARP."
---If you plan to communicate via IP with the router on the other side of the frame circuit you should either allow Inverse ARP to map the remote IP or do it yourself with "frame-relay map ip."
If you have configured "no frame-relay inverse-arp" you have effectively removed the map and you should configure a static "frame-relay map ip" statement. Using dynamic mapping entails leaving Inverse ARP on (as it is by default) and entering "frame-relay interface-dlci."
If you want to bridge across the interface, you'll need "frame-relay map bridge." Since you are in troubleshooting mode, I'd suggest keeping it simple and getting rid of the bridge commands for now.
> -----Original Message----- > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On > Behalf Of Justin M. Ramsey > Sent: Friday, March 28, 2003 8:43 AM > To: Jonathan V Hays; ccielab@groupstudy.com > Subject: RE: Frame-relay / IP assistance > > > I was under the impression that "no frame-relay inverse-arp" > command was to keep the dlci maps from being dynamically > assigned, rather then matching them with an IP. I must be wrong here? > > Justin Ramsey
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:46 GMT-3