From: Dmitry Volkov (dmitry.volkov@rogers.com)
Date: Tue Jan 20 2004 - 15:18:13 GMT-3
Hi,
the following config (for lab/test/curiosity purposes):
r6#
interface ATM0
ip address 192.168.1.6 255.255.255.0
ip ospf network point-to-point
pvc 2/114
protocol ip 192.168.1.9 broadcast <-------
broadcast
protocol ip inarp <--------
!
no atm ilmi-keepalive
r9#
interface ATM0
ip address 192.168.1.9 255.255.255.0
ip ospf network point-to-point
pvc 0/113
broadcast
!
no atm ilmi-keepalive
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fwan
_c/wcfatm.htm#1001268
"Inverse ARP is enabled by default when you create a PVC using the pvc
command. Once configured, a protocol mapping between an ATM PVC and a
network address is learned dynamically as a result of the exchange of ATM
Inverse ARP packets.
Inverse ARP is supported on PVCs running IP or IPX and no static map is
configured. If a static map is configured, Inverse ARP will be DISABLED."
In the above config despite I enabled inarp explicitly - it's actually
doesn't work -
I mean inarping (debug shows that r9 does inarp request, r6 doesn't answer).
I understand that it's probably meaningless to have static map and inarp
together. However IOS allows config them under the same pvc.
Question is: Is it expectable/normal that inarp still disabled in the above
config despite "protocol ip inarp" is configured ?
Thanks,
Dmitry
This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:48 GMT-3