From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Tue Sep 06 2005 - 16:27:52 GMT-3
The "no arp frame-relay" command has no effect on Frame Relay
Inverse-ARP. The "no frame-relay inverse-arp" command stops the router
from requesting Inverse-ARP of the remote end. It does not stop the
router from replying to inverse-arp.
Configure this simple test on the command line and see what
happens:
R1--DLCI 102--Frame_Cloud--DLCI 201--R2
R1:
interface Serial0
ip address 10.0.0.1 255.0.0.0
encapsulation frame-relay
R2:
interface Serial0
ip address 10.0.0.1 255.0.0.0
encapsulation frame-relay
no frame-relay inverse-arp
Check connectivity along with the "show frame-relay map" output.
What do you see and why?
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> simon hart
> Sent: Sunday, March 13, 2005 2:05 PM
> To: ccie; ccielab@groupstudy.com
> Subject: RE: no arp frame-relay
>
> Kevin,
>
> You have disabled frame relay arp on the interface and not frame relay
> inverse arp. The debug output shows an inverse arp exchange and the
frame
> map shows the result of frame relay inverse arp.
>
> If you do not wish to resolve dynamic map from l3 to l2 then you have
to
> apply the command
>
> no frame-relay inverse-arp
>
> The command arp frame-relay resolves a known ip address to a hardware
> address (in the case of Frame Relay the DLCI).
>
> The command frame-relay inverse-arp resolves a known local DLCI to a
far
> end
> IP address.
>
> HTH
>
> Simon
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> ccie
> Sent: 13 March 2005 19:46
> To: ccielab@groupstudy.com
> Subject: no arp frame-relay
>
>
> I thought that "no arp frame-relay" disabled either arp requests or
arp
> responses.
> I did some testing see below and now I am totally confused ! With it
off
> on
> both router on each end of the same PVC it will still request and
still
> reply.
> Any pointers ?
>
>
> R1#clear fram in
> R1#
> R1#
> R1#
> R1#sh fram map
>
> R1#sh run int s 0/0
> Building configuration...
>
> Current configuration : 125 bytes
> !
> interface Serial0/0
> ip address 1.1.1.1 255.255.255.0
> encapsulation frame-relay
> clockrate 64000
> no arp frame-relay
> end
>
> R1#
> R1#
> *Mar 1 00:13:23.827: Serial0/0(i): dlci 102(0x1861), pkt encaps
0x0300
> 0x8000 0x0000 0x806 (ARP), datagramsize 34
> *Mar 1 00:13:23.827: Serial0/0: FR ARP input
> *Mar 1 00:13:23.827: datagramstart = 0x38DD3AE, datagramsize = 34
> *Mar 1 00:13:23.827: FR encap = 0x18610300
> *Mar 1 00:13:23.827: 80 00 00 00 08 06 00 0F 08 00 02 04 00 08 00 00
> *Mar 1 00:13:23.831: 01 01 01 02 30 91 00 00 00 00 01 02 00 00
> *Mar 1 00:13:23.831:
> *Mar 1 00:13:23.831: Serial0/0: frame relay INARP received
> *Mar 1 00:13:23.831: FR: Sending INARP Reply on interface Serial0/0
> dlci 102 for link 7(IP)
> R1#
> R1#sh fram map
> Serial0/0 (up): ip 1.1.1.2 dlci 102(0x66,0x1860), dynamic,
> broadcast,, status defined, active
> R1#
>
>
>
>
######################################R2################################
##
> ##
> ############
> R2#sh run int s 0/0
> Building configuration...
>
> Current configuration : 125 bytes
> !
> interface Serial0/0
> ip address 1.1.1.2 255.255.255.0
> encapsulation frame-relay
> clockrate 64000
> no arp frame-relay
> end
>
> R2#
> R2#
> R2#
> R2#clear fram in
> R2#
> R2#
> R2#
> R2#sh fram map
>
> R2#ping 1.1.1.255
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 1.1.1.255, timeout is 2 seconds:
>
> *Mar 1 00:13:08.031: Serial0/0: broadcast search
> *Mar 1 00:13:08.031: Serial0/0:encaps failed on broadcast for link
7(IP).
> *Mar 1 00:13:10.031: Serial0/0: broadcast search
> *Mar 1 00:13:10.031: Serial0/0:encaps failed on broadcast for link
7(IP).
> *Mar 1 00:13:12.031: Serial0/0: broadcast search
> *Mar 1 00:13:12.031: Serial0/0:encaps failed on broadcast for link
7(IP).
> *Mar 1 00:13:14.031: Serial0/0: broadcast search
> *Mar 1 00:13:14.031: Serial0/0:encaps failed on broadcast for link
7(IP).
> *Mar 1 00:13:16.031: Serial0/0: broadcast search
> *Mar 1 00:13:16.031: Serial0/0:encaps failed on broadcast for link
7(IP).
> R2#
> R2#
> R2#
> R2#
> R2#
> *Mar 1 00:13:26.583: Serial0/0(o): dlci 201(0x3091), pkt encaps
0x0300
> 0x8000 0x0000 0x806 (ARP), datagramsize 34
> *Mar 1 00:13:26.583: FR: Sending INARP Request on interface Serial0/0
> dlci 201 for link 7(IP)
> *Mar 1 00:13:26.603: broadcast dequeue
> *Mar 1 00:13:26.603: Serial0/0(o):Pkt sent on dlci 201(0x3091), pkt
> encaps 0x300 0x8000 0x0 0x806 (ARP), datagramsize 34
> *Mar 1 00:13:26.631: Serial0/0(i): dlci 201(0x3091), pkt encaps
0x0300
> 0x8000 0x0000 0x806 (ARP), datagramsize 34
> *Mar 1 00:13:26.631: Serial0/0: FR ARP input
> *Mar 1 00:13:26.631: datagramstart = 0x370070E, datagramsize = 34
> *Mar 1 00:13:26.631: FR encap = 0x30910300
> *Mar 1 00:13:26.631: 80 00 00 00 08 06 00 0F 08 00 02 04 00 09 00 00
> *Mar 1 00:13:26.635: 01 01 01 01 30 91 01 01 01 02 01 02 00 00
> *Mar 1 00:13:26.635:
> *Mar 1 00:13:26.635: Serial0/0: frame relay INARP received
> R2#
> R2#sh fram map
> Serial0/0 (up): ip 1.1.1.1 dlci 201(0xC9,0x3090), dynamic,
> broadcast,, status defined, active
> R2#
> R2#
>
> Regards,
> Kevin
>
>
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:14 GMT-3