From: Tim Fletcher (tim@fletchmail.net)
Date: Fri Mar 28 2003 - 13:29:12 GMT-3
Inverse arp is used to map destination IP to DLCI, and is only needed in
multipoint interfaces. On point to point, there is only one destination,
and can only be 1 DLCI. Hence there is no need for inverse arp.
-Tim Fletcher
At 08:30 AM 3/28/2003 -0500, Jonathan V Hays wrote:
>Hi Justin,
>
>Your problem is that you configured "no frame-relay inverse-arp" and
>also have the subinterfaces configured with dynamic mapping
>("frame-relay interface-dlci") which REQUIRES Inverse Arp to function.
>You should only enter "no frame-relay inverse-arp" when you are
>configuring a static map on the interface ("frame-relay map ip").
>
>HTH
>
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
> > Behalf Of Justin M. Ramsey
> > Sent: Thursday, March 27, 2003 10:06 PM
> > To: ccielab@groupstudy.com
> > Subject: Frame-relay / IP assistance
> >
>
><snip>
>
>
> > R1:
> > interface Serial0
> > no ip address
> > encapsulation frame-relay IETF
> > no frame-relay inverse-arp
> > frame-relay lmi-type ansi
> > !
> > interface Serial0.16 point-to-point
> > ip address 10.10.16.1 255.255.255.0
> > frame-relay interface-dlci 16
> > bridge-group 1
> >
> >
> > R3:
> > interface Serial0
> > bandwidth 64
> > no ip address
> > ip directed-broadcast
> > encapsulation frame-relay IETF
> > logging event subif-link-status
> > logging event dlci-status-change
> > no frame-relay inverse-arp
> > frame-relay lmi-type ansi
> > !
> > interface Serial0.16 point-to-point
> > bandwidth 56
> > ip address 10.10.16.2 255.255.255.0
> > no ip directed-broadcast
> > frame-relay interface-dlci 16
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:46 GMT-3