From: James Ramsay (JRamsay@xxxxxxxxxxx)
Date: Mon Oct 11 1999 - 00:42:02 GMT-3
Hi Manjeet - just built this one to try it out and I get some interesting
results
One of my spokes has ONLY the static map (this has v11.2.4 code and v10 Boot
ROM's) just like Bruce Caslow says
The other has both the static map and the dynamic entry to the HUb(this has
v11.2.14 and v11 Boot Roms)
I am guessing this has something to do with revision of BOOT ROMs
I am using 2500 hundreds which load up their boot ROM images before the
Flash Image and so I would guest that this is the origin of the difference.
I would guess that older boxes like one of mine (and Mr Caslows!) does not
have Inverse ARP support in the boot ROM, where as the new one does. When
newer boxes boot they Inverse ARP (from BOOT code) before reading the NVRAM
- leading to the dynamic entry - and then install the static maps when the
config file is read.
AN ASIDE: Older Boot ROMs DEFINATELY had a more limited support for Frame as
the failure of earlier BOOT code to support inverse arp meant that
techniques such as Autoinstall did not work for routers going onto Frame
networks.
Manjeet - what version Boot ROMs are you using (sh version)
Regards
James
> -----Original Message-----
> From: Manjeet Chawla [SMTP:mchawla@asanet.com]
> Sent: Monday, 11 October 1999 14:47
> To: ccielab@groupstudy.com
> Subject: Frame Map /Inverse arp
>
> Hi everyone !
>
> I have a frame relay map/inverse arp question. As per Caslow, page 118
> under "A Word of Caution...." paragaph-1; it says:
>
> If a router is reload, inverse arp will be disabled for any DLCI that is
> used with any frame relay map statements....
>
>
> I have three routers (plus a router as FR Switch):
>
> Routers Spoke-1 and Spoke-2 connect to Hub router (via FR switch).
>
> Spoke-1 and 2 cannot ping each other as no map exists. If I am
> understanding it right, If I use FR map on Spoke-1 and 2 and reload the
> spokes, the inverse arp will be disabled on the spokes and under "show
> FR map" I should see only the static map (and no dynamic). Well, I see
> both static (to other spoke) and dynamic (to the hub).
> Am I mis-interpretting the book ?
>
> My configs and FR MAP outputs are as below:
>
>
> Thanks all for your helo in advance.
> Manjeet Chawla
>
>
>
>
> SWITCH:
> interface Serial0
> no ip address
> encapsulation frame-relay
> no fair-queue
> frame-relay intf-type dce
> frame-relay route 102 interface Serial1 201
> frame-relay route 103 interface Serial2 301
> !
> interface Serial1
> no ip address
> encapsulation frame-relay
> frame-relay intf-type dce
> frame-relay route 201 interface Serial0 102
> !
> interface Serial2
> no ip address
> encapsulation frame-relay
> frame-relay intf-type dce
> frame-relay route 301 interface Serial0 103
> !
> end
>
>
> HUB:
> interface Serial0
> ip address 172.16.3.3 255.255.255.0
> encapsulation frame-relay
> no fair-queue
> clockrate 2000000
>
> Hub#sh fr map
> Serial0 (up): ip 172.16.3.1 dlci 102(0x66,0x1860), dynamic,
> broadcast,, status defined, active
> Serial0 (up): ip 172.16.3.2 dlci 103(0x67,0x1870), dynamic,
> broadcast,, status defined, active
> Hub#
>
>
> SPOKE-1:
> interface Serial0
> ip address 172.16.3.1 255.255.255.0
> encapsulation frame-relay
> no ip mroute-cache
> no fair-queue
> clockrate 2000000
> frame-relay map ip 172.16.3.2 201
> !
> end
>
> Sh frame map
> Serial0 (up): ip 172.16.3.2 dlci 201(0xC9,0x3090), static,
> <------------------------
> CISCO, status defined, active
> Serial0 (up): ip 172.16.3.3 dlci 201(0xC9,0x3090), dynamic,
> <--------------------
> broadcast,, status defined, active
>
>
>
> SPOKE-2
> interface Serial0
> ip address 172.16.3.2 255.255.255.0
> encapsulation frame-relay
> no fair-queue
> clockrate 2000000
> frame-relay map ip 172.16.3.1 301
> !
>
> spoke-2#sh fr map
> Serial0 (up): ip 172.16.3.1 dlci 301(0x12D,0x48D0), static,
> <---------------------
> CISCO, status defined, active
> Serial0 (up): ip 172.16.3.3 dlci 301(0x12D,0x48D0), dynamic,
> <----------------
> broadcast,, status defined, active
> spoke-2#
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:52 GMT-3