Kevin Dorrell Tue, 10/23/2007 - 11:21
User Badges:
  • Green, 3000 points or more

Hi Lisa,

Yes, the difference is fairly simple, but has interesting consequences.

no frame-relay inverse arp says that I shall not ask the other end what his IP address is.

no arp frame-relay means that if the other end asks me my IP address, I shall not answer him.

In a CCIE practice lab, they usually do no frame-relay inverse-arp, but the other on can be useful too.

Kevin Dorrell


ilya.varlashkin Tue, 10/23/2007 - 13:40
User Badges:
  • Silver, 250 points or more

no frame-relay inverse would also disable sending unsolicited announcement of router's own mapping, but nevertheless there's still remains one issue against neither of those commands protects - router will still happily accept unsolicited announcement from remote side and use them.

I've just checked this in the lab:

*Oct 23 14:15:51.181: Serial6/0:0(i): dlci 205(0x30D1), pkt encaps 0x0300 0x8000 0x0000 0x806 (ARP), datagramsize 34

*Oct 23 14:15:51.181: Serial6/0:0.1: frame relay INARP received

*Oct 23 14:15:51.181: FR-ADJ: dlci 205: adding adjacency

*Oct 23 14:15:51.181: FR: Sending INARP Reply on interface Serial6/0:0.1 dlci 205 for link 7(IP)

while interface config has both commands:

Current configuration : 275 bytes


interface Serial6/0:0.1 multipoint

ip address

ip ospf network broadcast

no arp frame-relay

no frame-relay inverse-arp


And here is the mapping:

Serial6/0:0.1 (up): ip dlci 205(0xCD,0x30D0), dynamic,


CISCO, status defined, active

Also looks like router was provoked to send InARP reply even if 'no arp fr' configured.

Did I miss something?

Edison Ortiz Tue, 10/23/2007 - 14:49
User Badges:
  • Super Bronze, 10000 points or more
  • Hall of Fame,

    Founding Member

It sounds like you configured that interface while active. When changing to no frame-relay inverse-arp, you need to shutdown the interface, then make the change.

Based on your frame map, your router is learning its mapping dynamically.

ilya.varlashkin Tue, 10/23/2007 - 22:25
User Badges:
  • Silver, 250 points or more

Indeed, the mapping is dynamic and that's what I wanted to show - that 'no frame-relay inv' and 'no arp fr' do not protect router from accepting dynamic mapping.

I've shut the interface, I tried to reboot the router. As long as the other side doesn't send anything, the router doesn't create dynamic mapping. But as soon as the router receives uncolicited InARP reply (note that it's not INARP request, but InARP reply) from the other side, the router creates dynamic mapping and send InARP reply.

It might be that commands were intended to block InARP completely, but during past 12 years I haven't seen any IOS release where it would have been working. Since workaround is rather simple, there's hardly any chance that such behaviour will be changed.


This Discussion