From: Long Kwok (lkwok@ccieunix.com)
Date: Sun May 15 2005 - 14:47:35 GMT-3
Hi,
In IE's lab 2 / 6.14 it is pushing towards a method so that AS 400 is
not a transit provider for prefixes originating in AS 254 from AS 400's
directly connected AS 54 , solution shows to filter all routes /
prefixes from AS 254 and not advertise them onto its directly connected
EBGP peer AS 54 , this works , but if you look at the next hop to reach
the prefixes which are also being advertised via BB1 to BB3 you will see
next hop is sw1 which is in AS 400 so this solution doesn't actually
meet the requirements as far as I can see ? Anyone else have that issue
??
TIA , Long
This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:11:58 GMT-3