[c-nsp] Selecting an eBGP destination based on the source network.
Bruce Pinsky
bep at whack.org
Thu Dec 14 18:25:56 EST 2006
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rick Ernst wrote:
> It's a forwarding decision.
>
> "Customer class A" would prefer high-speed/high-quality outbound links and
> fall back to low-speed/low-cost links in case of failure, while "Customer
> class B" would prefer the low-speed/low-cost links and fall back to the
> high-speed/high-quality links.
>
> The key would be determining the destination based on source network, and
> my initial thought was doing something with next-hop, but that raises a
> possible reachability problem if the next-hop isn't available.
>
You can specify multiple next-hops that will be tried, in order, if not
available.
Depending on your design/topology, there may be some ways to use VRF-Lite
to segregate the different customer classes and create different routing
policies for each of those classes.
If you can share some more info about your network (privately if
necessary), I might be able to offer up a couple of different options.
- --
=========
bep
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFgd2EE1XcgMgrtyYRAuJcAKCGKqcV2Jndgni1e+4ZV15idVI8FwCghwIu
VJvXslUM7OROUfe9HOJ/OBQ=
=5x9M
-----END PGP SIGNATURE-----
More information about the cisco-nsp
mailing list