From: glmorris (glmorris48@xxxxxxxxxxx)
Date: Sun Apr 14 2002 - 16:52:24 GMT-3
Trace route is really the best tool to help locate loops. You should never
see a hop destination more than once in any route. If you are worried about
routes appearing and disappearing, turn on logging buffered and check the
output periodically. In the case of IGRP it is probably a split-horizon
mismatch. If other routing protocols have their routes disappear, it is
probably because their administrative distance was lower than another
protocol that is routing similar networks.
The key to avoiding route loops is to make sure you filter correctly during
redistribution.
----- Original Message -----
From: <Dennis.D.Adekola@britishairways.com>
To: <ccielab@groupstudy.com>
Sent: Sunday, April 14, 2002 8:59 AM
Subject: Routing Loops
> Hello all,
>
> I have been trying to practice how to take care of routing loops
> My problem is , i am not very clear on how to detect you have a loop in
> your network.
>
> What are the command that would help you
> Debug ip routing ?
> Debug ip packet ?
> What do i need to look out for in these debugs ?
>
> also in the routing table what will tell me.
> IGRP saying "Possibly down" and then okay.
> How difficult will it be looking out for routes that disapper and
> reapper periodically in the tables.
>
> Tried to check the archives but couldn't find anything concrete
>
> Imputs are much appreciated
>
>
> D
>
> --------------------------------------------------------------------------
-----------------------
>
> Save time by using an eTicket and our Self-Service Check-in Kiosks. For
> more information go to http://www.britishairways.com/eservice1
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:07 GMT-3