Re: Understanding debup output

From: ccie2be (ccie2be@nyc.rr.com)
Date: Tue Oct 12 2004 - 11:26:25 GMT-3

• Next message: Anand Singh: "RE: Forward all voip traffic to gateway"
• Previous message: Stan Zhang: "Re: OT: CCIE position in Atlanta"
• Maybe in reply to: ccie2be: "Understanding debup output"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Thanks, that makes alot of sense given the problem I was having - R6's rip
neighbor wasn't getting the routes I expected it to get.

I subsequently found out it was because my prefix-list had an error which
was blocking all routes.

----- Original Message -----
From: "Tim Fletcher" <groupstudy@fletchmail.net>
To: "ccie2be" <ccie2be@nyc.rr.com>; "Group Study" <ccielab@groupstudy.com>
Sent: Tuesday, October 12, 2004 9:46 AM
Subject: Re: Understanding debup output

> The "suppressing null update" means that there is nothing to advertise.
Not
> sure about the 0.0.0.0 without knowing more about your config.
>
> At 03:07 PM 10/11/2004, ccie2be wrote:
> >Hi guys,
> >
> >This is some output from deb ip rip.
> >
> >
> >*Oct 11 15:09:13.623: RIP: build update entries - suppressing null update
> >*Oct 11 15:09:13.623: RIP: sending v2 update to 224.0.0.9 via Loopback0
> >(150.3.6
> >.6)
> >*Oct 11 15:09:13.623: RIP: build update entries - suppressing null update
> >Rack1R6#
> >*Oct 11 15:09:22.347: RIP: received v2 update from 204.12.3.254 on
> >FastEthernet1
> >/0/0.263
> >*Oct 11 15:09:22.347: 30.0.0.0/16 via 0.0.0.0 in 1 hops
> >*Oct 11 15:09:22.347: 30.1.0.0/16 via 0.0.0.0 in 1 hops
> >*Oct 11 15:09:22.347: 30.2.0.0/16 via 0.0.0.0 in 1 hops
> >*Oct 11 15:09:22.347: 30.3.0.0/16 via 0.0.0.0 in 1 hops
> >*Oct 11 15:09:22.347: 31.0.0.0/16 via 0.0.0.0 in 1 hops
> >*Oct 11 15:09:22.351: 31.1.0.0/16 via 0.0.0.0 in 1 hops
> >*Oct 11 15:09:22.351: 31.2.0.0/16 via 0.0.0.0 in 1 hops
> >*Oct 11 15:09:22.351: 31.3.0.0/16 via 0.0.0.0 in 1 hops
> >
> >There are a couple of things I'm not that clear on from the output. I'm
> >hoping someone can shed some light.
> >
> >1) suppressing null update Why is this here and what does this really
mean?
> >
> >2) via 0.0.0.0 Why is 0.0.0.0 being used and not the actual source ip
address
> >shown right above, 204.12.3.254 ?
> >
> >Thanks, Tim
> >
> >_______________________________________________________________________
> >Subscription information may be found at:
> >http://www.groupstudy.com/list/CCIELab.html

• Next message: Anand Singh: "RE: Forward all voip traffic to gateway"
• Previous message: Stan Zhang: "Re: OT: CCIE position in Atlanta"
• Maybe in reply to: ccie2be: "Understanding debup output"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Sat Nov 06 2004 - 17:11:46 GMT-3