From: Carlos G Mendioroz (tron@xxxxxxxxxxx)
Date: Tue Jun 04 2002 - 11:58:52 GMT-3
I have the filling that this may be IOS version dependant...
In 12.1.13 and 11.3.11b, no frame inverse-arp does disable the sending
of inarp requests
but nothing else,i.e., responses are still sent if requests are
received.
Tricky thing here is that the remote arp request comes with address info
that will be used! (So even if you don't ask, you will use the
information
that was sent to you anyways, and you will still answer if queried).
If you disable both ends, then nobody will ask, and no information will
flow,
thus you would need static mappings.
I have been unable to determine what does "no arp frame" do, if
anything.
(inarp requests are still answered with no arp frame, and received
request info used...)
If someone does find out what does no arp frame do, please share the
light!
"GUGLER Jean-Luc (Consultas)" wrote:
>
> Dear all,
> on the Solie Book, the author write (693) :
>
> no frame-relay inverse-arp : disable the sending of inverse ARP
> requests. use this commande in conjunction with no arp fram-realy to
> prevent the dynamic mapping of PVC
>
> no arp frame-relay : Disable ARP responses. Use this in conjunction with
> the no frame-relay inverse-arp
>
> for me the arp frame-relay is an IP configuration and sould only be
> configured on an interface with IP addresse. This is not relevant for
> IPX,...
>
> The command no frame-relay inverse-arp could be apply to a dlci or a
> specific protocol (consult the commande reference)
>
> My question now is : sould we configure both on an ip interface to
> desactivate inverse arp or could we only configure no frame-relay
> inverse (which is more global to all prot.)
>
> Jean-Luc
> -----Message d'origine-----
> De : Erhan Kurt [mailto:kurt@superonline.net]
> Envoyi : mardi, 4. juin 2002 10:44
> @ : Joe Jia; ccielab@groupstudy.com
> Objet : RE: Frame-relay Inverse-arp
>
> Use "no fram inv" every FR interfaces except point-to-point. i.e. Do not
> rely on dynamic mappings even for IPX.
>
> Never Give Up,
> Erhan
>
> -----Original Message-----
> From: Joe Jia [mailto:ellenjjl@rogers.com]
> Sent: 09 May}s 2002 Per~embe 01:55
> To: ccielab@groupstudy.com
> Subject: Frame-relay Inverse-arp
>
> Hi,
>
> I have been confused by frame-relay inverse-arp and arp frame-relay.
> For
> example, suppose that Router R1, R2, R3, R4 fully messed to configure
> IP.
> Only R1 can use subinterfaces, say s0.1 point-to-point (to R4), s0.2
> multipoint (to R2 and R3). The requirement is that on R4 can not use
> subinterface and map. I also don't want to see R2,R3's IP address on R4,
> and
> on R2,R3 can't see R4's IP address. (Show Frame-relay map"
>
> With the following configuration, I reloaded the Routers, but still
> can't
> solve the problem.
>
> (1)on R4 cannot see R2, R3's IP address? Even though on R2, R3, I
> configured "no frame-relay inverse" and "no arp frame-relay".
>
> (2)On R4, whether or not put "no arp frame-relay", on R2,R3 can still
> see
> R4's IP address.
>
> R1:
>
> interface Serial0
>
> no ip address
>
> no ip directed-broadcast
>
> encapsulation frame-relay
>
> no ip mroute-cache
>
> no arp frame-relay
>
> no fair-queue
>
> clockrate 64000
>
> no frame-relay inverse-arp
>
> !
>
> interface Serial0.1 point-to-point
>
> ip address 137.20.100.2 255.255.255.0
>
> no ip directed-broadcast
>
> frame-relay interface-dlci 131
>
> !
>
> interface Serial0.2 multipoint
>
> ip address 137.20.101.1 255.255.255.0
>
> no ip directed-broadcast
>
> frame-relay map ip 137.20.101.3 132 broadcast
>
> frame-relay map ip 137.20.101.5 130 broadcast
>
> R4:
>
> interface Serial0
>
> ip address 137.20.100.1 255.255.255.0
>
> no ip directed-broadcast
>
> encapsulation frame-relay
>
> no ip mroute-cache
>
> no arp frame-relay
>
> no fair-queue
>
> clockrate 64000
>
> frame-relay interface-dlci 123
>
> R2:
>
> interface Serial0
>
> ip address 137.20.101.3 255.255.255.0
>
> no ip directed-broadcast
>
> encapsulation frame-relay
>
> no ip mroute-cache
>
> logging event subif-link-status
>
> logging event dlci-status-change
>
> no fair-queue
>
> clockrate 64000
>
> no arp frame-relay
>
> frame-relay map ip 137.20.101.1 231 broadcast
>
> no frame-relay inverse-arp
>
> R3:
>
> interface Serial0
>
> ip address 137.20.101.5 255.255.255.0
>
> no ip directed-broadcast
>
> encapsulation frame-relay
>
> no ip mroute-cache
>
> logging event subif-link-status
>
> logging event dlci-status-change
>
> no fair-queue
>
> clockrate 64000
>
> no arp frame-relay
>
> frame-relay map ip 137.20.101.1 230 broadcast
>
> no frame-relay inverse-arp
>
> Show Frame-relay map:
>
> R1:
>
> Serial0.2 (up): ip 137.20.101.3 dlci 132(0x84,0x2040), static,-`R2
>
> broadcast,
>
> CISCO, status defined, active
>
> Serial0.2 (up): ip 137.20.101.5 dlci 130(0x82,0x2020), static, `R3
>
> broadcast,
>
> CISCO, status defined, active
>
> Serial0.1 (up): point-to-point dlci, dlci 131(0x83,0x2030),
> broadcast`R4
>
> status defined, active
>
> R4:
>
> Rack01R2#sh fram map
>
> Serial0 (up): ip 137.20.100.2 dlci 123(0x7B,0x1CB0), dynamic,`R1
>
> broadcast,, status defined, active
>
> Serial0 (up): ip 137.20.101.3 dlci 400(0x190,0x6400), dynamic, --`R2
>
> broadcast,, status defined, active
>
> Serial0 (up): ip 137.20.101.5 dlci 200(0xC8,0x3080), dynamic,-`R3
>
> broadcast,, status defined, active
>
> R2:
>
> Serial0 (up): ip 137.20.100.1 dlci 400(0x190,0x6400), dynamic,`R4
>
> broadcast,, status defined, active
>
> Serial0 (up): ip 137.20.101.1 dlci 231(0xE7,0x3870), static, `R1
>
> broadcast,
>
> CISCO, status defined, active
>
> R3:
>
> Serial0 (up): ip 137.20.100.1 dlci 200(0xC8,0x3080), dynamic, `R4
>
> broadcast,, status defined, active
>
> Serial0 (up): ip 137.20.101.1 dlci 230(0xE6,0x3860), static,-`R1
>
> broadcast,
>
> CISCO, status defined, active
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:23 GMT-3