[nsp] How to do flexible route selection

From: Phillip Vandry (vandry@Mlink.NET)
Date: Fri Feb 27 1998 - 16:34:26 EST


I have the following problem. I'm seeking advice on how to handle it.
Surely someone else has been presented with this situation!

                       AS X <----------> AS Y
                        | |
                        | |
                        | |
                       AS Z AS W

AS Z and AS W are transit providers and are backbones or have connections
to backbones (not shown). AS X and AS Y are interconnected to each other
to that AS X has the benefit of using AS W for transit and vice versa.

The idea is that AS X and AS Y pool together to buy 2 links, and they
use each other's link.

Problem:

AS X is likely to have a general tendancy to use AS Z too often because
every AS path from AS W has an extra Y prepended to it, so it's probably
longer.

Conversely, AS Y is more likely to select AS W for the same reason.

AS X could prepend once to paths from AS Z. That was the paths are
longer by 1 whether they come from Z or W, so it will probably make a
better selection. But this simply makes the problem worse for AS Y
which is now going to receive paths from Z which are longer by 2.

Is there a way in IOS to prepend an AS to an AS path, or otherwise
influence the route selection process, for the local router or AS
only, but send the original path received to external peers?

Any other suggestions?

Thanks.

-Phil



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:15 EDT