From: Montiean (noktes@bellsouth.net)
Date: Mon Jan 02 2006 - 11:25:58 GMT-3
Try to think about the concept that if your primary path has gone, how many
ways you can reach the destination through the secondary path or other ways
around? DDR, static route, associate isdn to ospf routing domain, backup
interface? Once you see this then apply to the ospf domain in your network
and ensure that this backup will completely stable, not causing blackhole or
missing some destination by using what ever like ospf demand-circuit, "no
peer neighbor", no cdp or how's about setup ospf cost to make isdn quite
when topology changed. Is there some traffic making isdn flap?
The main idea is try to understand what you want to accomplish before
thinking about the command. I don't think there's only one specific command
or one solution to accomplish this. Also when you see that picture, you can
also apply to other contingency plan in your network that doesn't have ISDN
in the environment. Does this make sense??
Montiean
----- Original Message -----
From: "Young-Soo Basler" <charly@basler.net>
To: <ccielab@groupstudy.com>
Sent: Monday, January 02, 2006 7:49 AM
Subject: contigency cmd
> hi, i don't have a clou about a contigency command in a ospf isdn backup
> enviroment. anyone a idea?
>
> i't
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Wed Feb 01 2006 - 07:45:47 GMT-3