As a side note, "no arp frame-relay" does not work.
Here is the explanation from Brian McGahan:
A common misconception is that the "no arp frame-relay" command stops the
responses to Frame Relay inverse-arp requests. This is not true. The "no arp
frame-relay" command actually does not relate to frame relay inverse-arp at
all. Type it in and do a "show frame-relay map". You can see by the dynamic
mappings that it does not disable the processing of inverse-arp.
Frame Relay inarp can be disabled in the following manners:
1. "no frame-relay inverse-arp"
disables inarp for all protocols and all dlci's on that interface
2. "no frame-relay inverse-arp [protocol] [dlci]"
disables inarp for a specific protocol and dlci pair
3. "frame-relay map [protocol] [dlci]"
disables inarp for a specific protocol and dlci pair
On Sat, Aug 14, 2010 at 12:57 PM, Edward John <edwardjohn2020_at_googlemail.com
> wrote:
> Thanks to everyone. I will check this again in real routers and verify..
> I used to always no shut the interface, only after configuring
> "encapsulation frame-relay", "no arp frame-relay" and "no frame-relay
> inverse-arp"..
> I think I also should try in reverse...
>
> Thanks,
> John
Blogs and organic groups at http://www.ccie.net
Received on Sat Aug 14 2010 - 13:22:22 ART
This archive was generated by hypermail 2.2.0 : Wed Sep 01 2010 - 11:20:52 ART