[c-nsp] PBR and Redundancy

[Bruce Pinsky]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Steve Wright wrote:
> 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?
> 

Might help to know a little bit more about the environment here....

What is the interconnection between your L2TP gateways and the customer
routers?  Are there any routing protocols involved there?

What about between your gateways?  Any routing protocols?  How are they
connected?

Are the customer routers connected within their own network or are they
discontiguous?

What is policy routing be used for?  Do you need to make forwarding
decisions on anything other than the destination addresses in your
customer's network?

Thanks...

- --
=========
bep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)

iD8DBQFDRF2aE1XcgMgrtyYRAv6SAJ9Y4UzdADu4v9nJZWgrUd+oq+rkRQCgrc8D
c4TBU8QXiVAy5L1F3U3TsVM=
=Fdgw
-----END PGP SIGNATURE-----