Hi Sherwin, Inbound traffic can also be altered on the basis of prefix-advertisement. If you are advertising more specific prefix i.e. /22 or /24 (though not recommended with tier1 service providers) your inbound traffic will always take the desired path.
and yes as-path prepend is also an option. Regards, Aftab A. Siddiqui On Wed, Feb 10, 2010 at 8:23 AM, Jon Lewis <[email protected]> wrote: > On Wed, 10 Feb 2010, Sherwin Torres wrote: > > 1. AS1 - AS200 - AS30 >> 2. AS1 - AS300 - AS30 >> 3. AS1 - AS400 - AS20 - AS30 >> >> In the above scenario, I am using AS30 and I need to access AS1. The >> outbound traffic can be force using the localpref to prefer which >> path I can use for the outbound however, my dilemma is the inbound >> traffic. Since sample 1 and 2 has lesser path from AS1 going to AS30, >> this might be the best in returned path while sample 3 is the least >> priority due to longer path. Is there a way can I manipulate the inbound >> and outbound via sample 3 without contacting AS1? >> > > The short answer is as-path prepending of your announced routes to as200 > and as300. > > ---------------------------------------------------------------------- > Jon Lewis | I route > Senior Network Engineer | therefore you are > Atlantic Net | > _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________ > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
