From: Kevin Baumgartner (kbaumgar@xxxxxxxxx)
Date: Thu Aug 31 2000 - 20:32:36 GMT-3
No problem. Good luck on the lab tomorrow.
- Kevin
At 10:14 AM 9/1/00 +1100, you wrote:
>I've really got to try and keep calm - this was a panic problem...
>
>Here's the post-mortem :
>
>Unlike in rip where it understands a 0.0.0.0, IGRP does not. (I knew this
>but couldn't see the wood for the trees!!)
>
>Even if you flag a network as default on a IGRP boundary, if the flagged
>network is not running IGRP it won't advertise it.
>
>IGRP will, by default, advertise default information - it can be filtered to
>say which and when etc, but the default network has to be flagged as such
>and running IGRP - or redistributing into IGRP (via static or connected
>etc).
>
>What I was doing wrong was
>
>int lo0
>ip add 47.47.47.47/24
>
>ip default-net 47.47.47.0
>
>is all very well, but because "netw 47.0.0.0" was not in IGRP (and no
>redistr) I was still expecting IGRP to advertise a default of 0.0.0.0 which
>it never will...
>
>
>Thanks Kevin, I think I need a cup of tea and a lie down now!!
>
>
>Simon
>
>
>-----Original Message-----
>From: Kevin Baumgartner [mailto:kbaumgar@cisco.com]
>Sent: Friday, September 01, 2000 8:58 AM
>To: Simon Baxter
>Subject: RE: LAST DAY...HELP!!!
>
>
>The reason you are getting this wierd route is because it trying to
>summarize the 47.47.47.0 network to a classful route of 47.0.0.0.
>
> I would then try changing the configuration to
>
>int lo0
>ip add 47.47.47.47 255.0.0.0
>
>ip default-network 47.0.0.0
>
> This should work, might have to add
>router igrp
>network 47.0.0.0
>
>Let me know if this works. It seems like it should.
>
> Kevin
>
>
>At 09:38 AM 9/1/00 +1100, you wrote:
> >I'll try the first thing.
> >
> >with
> >int lo0
> >ip add 47.47.47.47/24
> >
> >and
> >
> >ip default-net 47.47.47.0
> >
> >the command doesn't appear in the running config but is replaced with
> >ip route 47.0.0.0 255.0.0.0 47.47.47.0
> >
> >and if you try to do a
> >no ip route 47.0.0.0 255.0.0.0 47.47.47.0
> >
> >it reports :
> >%No matching route to delete
> >
> >and won't remove until reload.....
> >
> >
> >I'm sure it's a class thing...but feel really frustrated so close to the
>lab
> >date - and my Cisco mentor in Sydney isn't answering his phone!! (you
>don't
> >work in Chatswood in Sydney do you??)
> >
> >
> >Thanks,
> >
> >Simon
> >
> >
> >-----Original Message-----
> >From: Kevin Baumgartner [mailto:kbaumgar@cisco.com]
> >Sent: Friday, September 01, 2000 8:41 AM
> >To: Simon Baxter
> >Subject: Re: LAST DAY...HELP!!!
> >
> >
> >Might want to try changing the mask to /8
> >ie
> >int lo0
> >ip add 47.47.47.47/8
> >
> > IGRP will only put a classful route as the default-network.
> >And plus you are defining the IP default-network to use
> >47.0.0.0.
> >
> > If this doesn't work try changing the
> >IP default-network to 47.47.47.0
> >with 24 bit mask for int lo0.
> >
> > But I think the first way as the what should work.
> >
> > - Kevin
> >
> >
> >At 09:11 AM 9/1/00 +1100, you wrote:
> > >IGRP.
> > >
> > >this is what I have :
> > >
> > >int lo0
> > >ip add 47.47.47.47/24
> > >
> > >int s1/0
> > >ip add 2.2.2.1
> > >
> > >router igrp 1
> > >netw 2.0.0.0
> > >pass s1/0
> > >neigh 2.2.2.2
> > >
> > >ip default-network 47.0.0.0
> > >
> > >
> > >the show ip protocols says :
> > >Routing Protocol is "igrp 1"
> > > Sending updates every 90 seconds, next due in 75 seconds
> > > Invalid after 270 seconds, hold down 0, flushed after 630
> > > Outgoing update filter list for all interfaces is
> > > Incoming update filter list for all interfaces is
> > >
> > > Default networks flagged in outgoing updates <------------shouldn't
> >this
> > >do it?
> > >
> > > Default networks accepted from incoming updates
> > > IGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
> > > IGRP maximum hopcount 100
> > > IGRP maximum metric variance 1
> > > Redistributing: igrp 1
> > > Neighbor(s):
> > > 2.2.2.2
> > > Routing for Networks:
> > > 1.0.0.0
> > > 2.0.0.0
> > > Passive Interface(s):
> > > Serial1/0
> > > Routing Information Sources:
> > > Gateway Distance Last Update
> > > 2.2.2.2 100 00:00:18
> > > Distance: (default is 100)
> > >
> > >
> > >Why won't my neighbor 2.2.2.2 get the default route?
> > >
> > >It's not because of the unicast updates, if I put a more specific ip
> > >default-network statement in it creates a static route which can only be
> > >removed with a reload.
> > >
> > >
> > >
> > >PLEEEASE someone be awake in the southern hemisphere!!
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:24:34 GMT-3