From: Jung, Jin (jin.jung@lmco.com)
Date: Wed Oct 23 2002 - 11:30:31 GMT-3
Hi Hunt,,
First ,, This is advise I have received, -
"nail it down as much as you can"
Which means, if you can use map to control the frame-relay map, why would
you want to take a chance with dynamic inverse-arp,
Second, there are many option to configure frame-relay - ptp, ptm,
interface-dlci, inverse-arp, ....
And this could get some what confusing, so once again,, nail it down,
Third, don't forget the rule of frame-relay for inverse-arp.
I can recall exect words but,,
It goes something like, inverse-arp is disabled for the dlci if you use map
statement per that protocol, I guess I need to go back and read this again,,
---------Original Message----- From: Hunt Lee [mailto:ciscoforme3@yahoo.com.au] Sent: Wednesday, October 23, 2002 9:42 AM To: ccielab@groupstudy.com Subject: Please help urgently!!!
Hello,
I have to subj fo clarification:
In a hub & spoke environment, I have read on many books & other resources stating to use "frame-relay map ip <x.x.x.x> <DLCI no> to map the appropriate IP address to its corresponding DLCI on the FR routers.
While I understand that this is a MUST for Spoke routers (since the Inverse ARP only works on directly connected links)
e.g. On Spoke routers,
interface Serial0 ip address 172.16.2.2 255.255.255.0 encapsulation frame-relay ip ospf priority 0 no fair-queue clockrate 64000 frame-relay map ip 172.16.2.3 600 broadcast frame-relay map ip 172.16.2.4 600 broadcast frame-relay map ip 172.16.2.1 600 broadcast no frame-relay inverse-arp
... but on the Hub, wouldn't it make more sense just to stay with Inverse ARP by "frame-relay inverse-arp" , since the Hub will need to have physical direct connections to all the Spokes anyway??
e.g. On Hub,
interface Serial0 ip address 172.16.2.1 255.255.255.0 encapsulation frame-relay frame-relay inverse-arp
Please add something or disprove if i'm wrong.
Thank You,
L.
http://careers.yahoo.com.au - Yahoo! Careers - 1,000's of jobs waiting online for you!
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:54 GMT-3