>I want to run a pair of BGP sessions to a Private AS via two ATM links.
>I'm holding back prefixes and the CPE is using default routes to send
>traffic back. The LAN
>interfaces on the CPE's run HSRP to give the customer a single gateway, but
>HSRP can only
>track Interface states. I cannot put a link between the CPE's as they are
>sometimes on
>different sites miles apart. The link state change is imperitave for any
>type of failure to ensure
>the HSRP session fails over. Any thoughts?
If you are trying to spot the odd failures how about the following:
1)Run a tunnel between the routers to simulate a crossover cable.
Run the tunnel within the CPE network ;-). Make sure you have
lots of CPU on the routers and also you have plenty of BW
with the CPE network.
2) Make sure you have OAM running on the ATM pvcs so if there
is a failure within the ATM cloud you will get a link change
3) Advertise via an IGP a route something like
router ospf 100 ! or you favourite IGP
redistribute static
ip route 0.0.0.0 0.0.0.0 <some supernet within your AS>
ip route 0.0.0.0 0.0.0.0 <ip address of the other rtrs lan side>
This means if you lose BGP to router the second route will kick in.
Why not just redistribute an default from BGP into the IGP. I like this
idea more as you way still get a advert for the 0/0 even if half you AS
is dead in many cases. If you choose a "good" supernet this is less
"likely" to happen.
They are just different thoughts for you to try or play with.
Regards,
Kevin
>Jon..
>
>-----Original Message-----
>From: Gert Doering [mailto:gert@greenie.muc.de]
>Sent: 27 April 2001 13:20
>To: Desmarais, Jonathan; 'cisco-nsp@puck.nether.net'
>Subject: Re: [nsp] Config Options.
>
>
>hi,
>
>On Fri, Apr 27, 2001 at 11:38:41AM +0100, Desmarais, Jonathan wrote:
> > There are two ways to configure a PVC on an ATM interface.
> >
> > "atm pvc" or just "pvc". WHat is the diffence.
> > I have found that using just "pvc" to define the circuit and then
> > configuring oam etc, the interface link state changes correctly.
> > When I use the atm pvc command and add oam to the end the
>link state does
> > not change. Do I need to configure oam on the physical interface too.
> > Or is this just the way it is?
>
>This seems to be the way it is.
>
>But while we're on it: I use ATM subinterfaces, with "pvc" style syntax:
>
>interface ATM2/0.32 point-to-point
> bandwidth 2000000
> ip unnumbered Loopback0
> pvc sp1 15/32
> ubr 2000
> oam-pvc manage
> encapsulation aal5mux ip
>
>and nearly everything works nicely, that is:
>
> - everything in order -> line is "up/up".
> - line is broken, remote end disconnected -> OAM fails -> line
>is "down/down"
>
>what I would like to see is:
>
> - line is looped back -> OAM detects loop -> line is "up/up (looped)"
>
>but that doesn't happen right now, the loopback condition is not
>recognized and the Interface just stays "up/up", which is bad for
>dial-backup etc.
>
>Does this ring a bell for anyone? Is there a workaround, or is it
>"bug your sales droid"...?
>
>gert
>--
>USENET is *not* the non-clickable part of WWW!
>
>//www.muc.de/~gert/
>Gert Doering - Munich, Germany
>gert@greenie.muc.de
>fax: +49-89-35655025
>gert.doering@physik.tu-muenchen.de
>
>
>**********************************************************************
>COLT Telecommunications
>Registered in England No. 2452736
>Registered Office: Bishopsgate Court, 4 Norton Folgate, London E1 6DQ
>Tel. 020 7390 3900
>
>This message is subject to and does not create or vary any contractual
>relationship between COLT Telecommunications, its subsidiaries or
>affiliates ("COLT") and you. Internet communications are not secure
>and therefore COLT does not accept legal responsibility for the
>contents of this message. Any view or opinions expressed are those of
>the author. The message is intended for the addressee only and its
>contents and any attached files are strictly confidential. If you have
>received it in error, please telephone the number above. Thank you.
>
>
>**********************************************************************
*********************************IMPORTANT NOTICE******************************
All e-mails for technical support must be cc'd to support@lancomms.ie. This
ensures that the call is logged with the support desk and the case is actively
tracked which speeds up the response you will receive. If you have an urgent
problem you _must_ contact the support desk directly on 01-4093030.
*****************************************************************************************
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:36 EDT