Hi, I assume that you have those peering on two different routers. Then it is not garanted that even one of them has full info from both peers. If both ASBR has common RR, then go to RR.
Anyway. from asian peer wyou will have active routes say 150, where 100 is unique to asian peer, and 50 are know from both peers, but aasian update is better. If you can affect your routing for the while, I suggest set LP to 255 on US peer. Then, if other policies do not alternate default BGP decision, all _active_ prefixes known form asian peer, are annouced only by this asian peer. If given prefix is known from asia and US, then US annoucement always win. If you can't alternate config for troubleshooting, You have to have router where all prefixes exist. This can be RR, but only if is common RR for both ASBR's. then display routes with as-path "AS2$", copy-past to txt file, and use external grep/awk/sed/perl. 2007/5/15, Amos Rosenboim <[EMAIL PROTECTED]>: > > Hello, > > What you can do is tag the coming from AS2 with 3 different > communities. One unique to the Asian peer, one unique to the US peer > and one shared to both. > This will give you the option to diff between the routes. > > Regards > > Amos > > On May 15, 2007, at 7:11 AM, wang yi wrote: > > > Greetings, j-nsp users. > > > > I manage AS1 and peering with AS2 at US and Asia. In US, I found > > that AS2 is > > giving us around 200 prefixes whereas in Aisa, it is giving us > > around 300. > > Is there anyway to compare and "diff" the prefixes received across > > different > > peering points of the same AS? > > > > Thank you very much. > > > > yi > > > > -- > > > > to be, or not to be > > _______________________________________________ > > juniper-nsp mailing list [email protected] > > https://puck.nether.net/mailman/listinfo/juniper-nsp > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > -- Rafał Szarecki JNCIE +48602418971 _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
