This happens to me in frame-relay lab. Apparently the inverse arp does not
function the way it should in lab. Right now I always do 'copy run start',
then 'reload' on all lab routers to make sure that the inverse arp and
what-not work as it should.

In a recent actual frame relay implementation between two sites, we had to
config the lmi type at one site in order to bring up frame-relay connection.
We were using 1720 with v. 12.1(1) at both sites.


"Nigel Taylor" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> All,=20
>         I made another weird discovery this morning in one of my =
> practice labs. The lab equipment in use;
>
> AGS+ : 11.0(22) Frame-relay cloud
> R1 2501   : 12.0.9(15)  Hub  sub-interface(s0.1 P-t-P1.1.1.1), and =
> (s0.2, ip 2.2.2.1) Multipoint
> R2 2502   : 11.3.(11a)T1  Spoke - Physical interface, ip 1.1.1.2
> R3 2502   : 11.3.(11a)T1  Spoke - Physical interface, ip 2.2.2.2
> R4 2520   : 11.3.(11a)T1  Spoke - Physical interface, ip 2.2.2.3
>
> After setting the frame circuit and the Hub and spoke routers the HUB =
> specific local DLCI's come up and go active on the frame switch, the =
> spoke DLCI's go active the inactive, then deleted.  I looked at every =
> thing that made sense,=20
>
> 1)Is the HUB - is the interface-dlci command using the correct dlci's , =
> Yes!  =20
> 2) At the spokes is the encapsulation type(frame relay) configured, Yes!
> 3) Is the ip (L3) configured on all devices, Yes!
>
> Ok, a "clear frame inverse-arp"  and a good sign I get an arp for R2 on =
> the hub!  A second look shows R2 has no mappings and the pvc is =
> inactive.  No matter what I did nothing.
>
> No this is really weird...  Before I started this lab I did a "wr erase" =
> on all the routers.  I proceeded to do a "wr mem" for the first time =
> since entering all my commands for my frame relay setup on the HUB, and =
> out of nowhere all the Spoke DLCI's go active and everything works like =
> it's suppose too.
>
> No, in everything things I've read it says that the commands go active =
> as they're entered, however here it seemed to require me to wr mem for =
> the circuit to come up. Has anyone seen this or have it happen in the =
> past.
>
> Thanks
>
> Nigel.
>
>
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>


_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to