[c-nsp] PBR and Redundancy

[Luan Nguyen]

If I understand your question right..., I would summerize Cust netblock and
advertise to endusers so that rtr2 link fails won't trigger a route
withdrawn.  Then just build a GRE tunnel between gw2 and gw1.

-luan


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Steve Wright
Sent: Wednesday, October 05, 2005 9:35 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] PBR and Redundancy

Hi all,

We are just looking into the following configuration for a client to enable
us to offer them certain services such as L2TP termination on our kit, but
to hand the traffic off to them to deal with.

     EndUsers
   /         \
l2tp-gw1----l2tp-gw2
   |           |
Cust-rtr1   Cust-rtr2


Now, I understand how to do the policy map to set the traffic for the range
of IP's to go via 'Cust-rtr1' and 'Cust-rtr2' by setting the next hop.
However, should a link failure be experienced between 'l2tp-gw2' and
'Cust-rtr2' for example, I would still want to hand the traffic off to them.
However, this would have to be done via the interconnect between 'l2tp-gw2'
and  'l2tp-gw1' and then to 'Cust-rtr1'.

Can anyone advise on the ways to achieve this?

Thanks,



This message has been scanned for viruses by MailController -
www.MailController.altohiway.com
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/