From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Fri Jun 30 2006 - 13:29:28 ART
The problem is that multicast and broadcast traffic may be
replicated out incorrect circuits if you leave the zero mappings there.
This means possible problems in OSPF, EIGRP, RIP, PIM, etc. Therefore
if your mappings are not correct don't wait until you have multicast
problems to fix it. Instead just fix it as you build it in the Frame
Relay section.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Russell Kelly (rukelly)
> Sent: Friday, June 30, 2006 10:23 AM
> To: Sidalo; Curt Gregg (cugregg)
> Cc: Cisco certification
> Subject: RE: Frame-Relay Static mapping couple Qs
>
> Those 0.0.0.0, if left, can adversely affect the core of the lab (OSPF
> Adj etc) - I would say best to sort 'em sooner rather than later ---
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Sidalo
> Sent: 30 June 2006 16:18
> To: Curt Gregg (cugregg)
> Cc: Cisco certification
> Subject: Re: Frame-Relay Static mapping couple Qs
>
> While in the lab do not waste time on a reboot just to clear this.
You
> should know that the config is correct and move on, and then make a
note
> of it.
> Just before lunch, save all configs (do this religiously anyway) and
> then reload the routers. Use the time for lunch as an advantage so
that
> all the routers are cycling and coming back up while you are not
there.
> When you get back from eating check the frame maps to make sure the
> reload took care of them.
> Also make sure all OSPF came back the way you would of thought it
would,
> and anything else that could be effected by a reboot.
>
>
> > > -----Original Message-----
> > > From: Curt Gregg (cugregg) [mailto:cugregg@cisco.com]
> > > Sent: Friday, June 30, 2006 7:12 AM
> > > To: Brian McGahan; Cisco certification
> > > Subject: RE: Frame-Relay Static mapping couple Qs
> > >
> > > So a reboot is the only way to clear these mappings.
> > >
> > > You know I have specifically shut down the interface before and
> > > reenabled it after my configuration was complete. With static
> > mappings
> > > I would still get 0.0.0.0 for my IP address:
> > >
> > >
> > > Frame-relay map ip 54.1.3.254 51
> > > --
> > > Serial0/0 (up): ip 0.0.0.0 dlci 51(0x33,0xC30), dynamic,
> > > broadcast,, status defined, active
> > >
> > > I have experienced the same issue when creating frame-relay
> > connections
> > > where I shutdown the interface and add my frame-relay
configuration
> > > including no frame-relay inverse-arp, enable the interface and I
> > > still
> >
> > > see more PVCs than I wanted to.
> > >
> > > I guess I'm wondering if its an IOS thing because I can remember
> > > times
> >
> > > when shutting down the interface adding frame-relay configs with
out
> > dyn
> > > mappings then enabling the interface would only allow the
configured
>
> > > PVCs and mappings to be shown and not others that might be
> > > configured
> > on
> > > the remote end.
> > >
> > > Thanks for the feedback,
> > >
> > >
> > > Curt
> > >
> > > -----Original Message-----
> > > From: Brian McGahan [mailto:bmcgahan@internetworkexpert.com]
> > > Sent: Thursday, June 29, 2006 7:47 PM
> > > To: Curt Gregg (cugregg); Cisco certification
> > > Subject: RE: Frame-Relay Static mapping couple Qs
> > >
> > > You have to reload to get rid of the 0.0.0.0 mappings. Next
> > time you
> > > configure Frame Relay make sure you "shutdown" the interface
before
> > > issuing the "encapsulation frame-relay" command. Then once all
the
> > > endpoints are configured the way you want them bring the
> > interfaces
> > > out of shutdown.
> > >
> > >
> > > HTH,
> > >
> > > Brian McGahan, CCIE #8593
> > > bmcgahan@internetworkexpert.com
> > >
> > > Internetwork Expert, Inc.
> > > http://www.InternetworkExpert.com
> > > Toll Free: 877-224-8987 x 705
> > > Outside US: 775-826-4344 x 705
> > > 24/7 Support: http://forum.internetworkexpert.com
> > > Live Chat: http://www.internetworkexpert.com/chat/
> > >
> > >
> > > > -----Original Message-----
> > > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
> > > > Behalf
> > > Of
> > > > Curt Gregg (cugregg)
> > > > Sent: Thursday, June 29, 2006 6:07 PM
> > > > To: Cisco certification
> > > > Subject: Frame-Relay Static mapping couple Qs
> > > >
> > > > When creating Frame-Relay static maps for example say R6 to BB3.
> > > >
> > > > BB3 is has 6 PVCs 100, 101, 201, 301, 401 and 51.
> > > >
> > > > You only want to use inverse-arp on DLCI 51 from R6 to BB3
> > > >
> > > > So options are :
> > > > R6
> > > > No frame-relay inverse-arp ip 100, 101, 201 etc..
> > > >
> > > > or can you use
> > > >
> > > > frame-relay inverse-arp ip 51
> > > > no frame-relay inverse-arp
> > > >
> > > > which one superseds?
> > > >
> > > > Next:
> > > > when showing frame map I see all the DLCI with blank ip address
> > > >
> > > > Serial0/0 (up): ip 0.0.0.0 dlci 51(0x33,0xC30), dynamic,
> > > > broadcast,, status defined, active
> > > >
> > > > Serial0/0 (up): ip 0.0.0.0 dlci 100(0x33,0xC30), dynamic,
> > > > broadcast,, status defined, active
> > > >
> > > > Serial0/0 (up): ip 0.0.0.0 dlci 101(0x33,0xC30), dynamic,
> > > > broadcast,, status defined, active
> > > >
> > > > Serial0/0 (up): ip 0.0.0.0 dlci 201(0x33,0xC30), dynamic,
> > > > broadcast,, status defined, active etc...
> > > >
> > > > is there a way to resolve this with out rebooting the router.. A
> > > reboot
> > > > show the correct results:
> > > >
> > > > Serial0/0 (up): ip 54.1.3.254 dlci 51(0x33,0xC30), dynamic,
> > > > broadcast,, status defined, active
> > > >
> > > > I have tried to the configuration with the interface shutdown
and
> > had
> > > > the same results.
> > > >
> > > > THX in ADV.
> > > >
> > > > Curt
> > > >
> > > >
> > >
> >
This archive was generated by hypermail 2.1.4 : Sat Jul 01 2006 - 07:57:34 ART