From: Chad Patterson (cpatterson@summithealth.org)
Date: Fri Jan 13 2006 - 07:53:09 GMT-3
After I have redistributed all desired routes and attained universal
connectivity, I enable debug ip routing.
Last week I would have said,
If I see routes being added / deleted, that indicates there is a
problem.
I am expecting to see no output from the debug ip routing command,
unless I actually do something to cause a route to be added or deleted.
There seems to be an exception to this rule, or I need some
clarification concerning my debug output,
In some versions of code, when you have a default route, debug ip
routing will give you a message like the one below every 60 seconds.
R1#
*Mar 1 00:38:19.063: RT: NET-RED 0.0.0.0/0
*Mar 1 00:38:19.063: RT: NET-RED queued, Queue size 1
Since I don't see this affecting traffic, I am assuming it is
informational and would like to move on.
If this is the sign of a real problem, I would like to understand what
is causing the problem and fix it.
My initial assumption was that if everything is stable, I will not see
anything when I enable debug ip routing.
Is this an exception, and is anyone aware of other exceptions?
Regards,
Chad
>>> loke <loke14@gmail.com> 1/12/2006 9:36 PM >>>
R1 is receiving the default route because of the nssa area type you
configured. The reason you are seeing that output the route add, is
because
you have debug ip routing turned on.
Nick
On 1/12/06, Chad Patterson <cpatterson@summithealth.org> wrote:
>
> I found someone else having this same problem when I searched the
group
> study archives.
> Unfortunately, this was after two hours of troubleshooting, and
writing
> this email.
> So here is the email, and a link to the groupstudy string.
>
> I would welcome an actual explanation of "why" this problem happens,
> but I am just glad some else has seen it.
>
>
> Here is my original problem,
>
> R1 is receiving 0.0.0.0/0 from R4
>
> I have enabled debug ip routing on R1,
> I get this message every minute,
>
> R1#
> *Mar 1 00:38:19.063: RT: NET-RED 0.0.0.0/0
> *Mar 1 00:38:19.063: RT: NET-RED queued, Queue size 1
>
> I have tried every debug I can think of,
> I do not have any (noticable) reachability issues.
> I have reloaded all routers.
> I am unable to determine the exact meaning of, RT: NET-RED
0.0.0.0/0
> I can't see the route leaving the routing table. I never see RT: add
/
> delete
> I have tried different combinations of the area nssa command.
> I shut down all other interfaces,
> I disabled cdp on all routers, ODR is not running,
>
> Is there any chance RT: NET-RED 0.0.0.0/0, is not a bad thing?
>
>
> R1
> router ospf 40
> area 25 nssa
> network 172.16.241.1 0.0.0.0 area 25
> !
>
> R4
> router ospf 40
> area 25 nssa no-redistribution no-summary
> network 172.16.241.4 0.0.0.0 area 25
>
>
> R1#u all
> All possible debugging has been turned off
> R1#
> R1#debu ip routin
> R1#debu ip routing
> IP routing debugging is on
> R1#
> *Mar 1 00:38:19.063: RT: NET-RED 0.0.0.0/0
> *Mar 1 00:38:19.063: RT: NET-RED queued, Queue size 1
> R1#
> *Mar 1 00:39:19.063: RT: NET-RED 0.0.0.0/0
> *Mar 1 00:39:19.063: RT: NET-RED queued, Queue size 1
> R1#
> *Mar 1 00:40:19.063: RT: NET-RED 0.0.0.0/0
> *Mar 1 00:40:19.063: RT: NET-RED queued, Queue size 1
> R1#
>
> R1#sho ip ospf database <Text Ommitted>
> Summary Net Link States (Area 25)
> Link ID ADV Router Age Seq# Checksum
> 0.0.0.0 172.16.104.1 1272 0x80000002 0x00C34B
> R1#
>
>
> R1#sho ip route
> O*IA 0.0.0.0/0 [110/65] via 172.16.241.4, 00:46:44, Serial0/0.1
>
>
>
>
> This seems to be related to the default route itself?
> R4 sends the route,
> I see no debug ip routing messages from R4
>
> Both R1 and R2 at different IOS versions see this every minute,
>
> R1 ver-12.2(15)T
> R1#
> *Mar 1 00:40:19.063: RT: NET-RED 0.0.0.0/0
> *Mar 1 00:40:19.063: RT: NET-RED queued, Queue size 1
>
> R2 ver-12.4(5)
> R2#
> *Apr 24 08:54:48.459: RT: NET-RED 0.0.0.0/0
>
>
>
> Here is what I found in the Archives,
>
> http://shop.groupstudy.com/archives/ccielab/200507/msg01062.html
>
> RE: NET-RED every 60 seconds posted 07/22/2005
>
> Crazy or not, after removing a static default route pointing to
remote
>
> ISDN, it stopped (I previously removed ospf and bgp, but no change).
>
> Then I tested other static routes. Just default route causes it.
> Pointing
> to ISDN or remote serial IP, it causes the 60 second message. It is
> 12.2T
> - precisely C2600-J1S3-M, Version 12.2(15)T5.
>
> I tought it was some instability on the IGP/BGP. But now there is no
> routing protocol, just a defaut static route, confirming that this
> cause
> the behavior. I reloaded the router, and it is still there.
>
> Thanks
>
> Gladston
>
>
This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:48 GMT-3