From: john matijevic (john.matijevic@gmail.com)
Date: Sun Jul 17 2005 - 10:55:59 GMT-3
Hello Jeremy,
If you understand the technologies, you should be able to visually spot
routing loop issues, however, you can also use the debug ip routing command
after configuring redistribution, to see if there is a routing loop.
Sincerely,
John
On 7/17/05, Jeremy <jeremy19@cox.net> wrote:
>
> In configuring redistribution, I am concerned about detecting routing
> loops.
> It appears that the ip route profile command allows you to track flapping
> routes (and possible routing loops?) Can anyone clarify how I would use
> this command, and its associated show commands to determine the source of
> a
> routing loop.
>
> I mayu be over-complicating this... Do I even need to worry about using
> this command, or can I find these purely by looking at the routing
> protocol
> diagram? I know that you can generally pick out potential routing loops
> just by looking at the redistribution points on the routing protocol
> diagram, and whether the protocols are link state vs. distance vector, but
> I
> tend to do this based on what I've seen in the past rather than sound
> logic.
> Does anyone have a more empirical way of locating potential routing loop
> problems visually?
>
> Doc-CD Link for "show ip profile"
>
>
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fipr
> rp_r/ind_r/1rfindp2.htm#wp1058095
>
>
> TIA!
>
> -Jeremy
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.9.0/50 - Release Date: 7/16/2005
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- John Matijevic, CCIE #13254 U.S. Installation Group Senior Network Engineer 954-969-7160 ext. 1147 (office) 305-321-6232 (cell)
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:30 GMT-3