[afnog] AS Path transparency on Route Server

Mark Tinka mark.tinka at seacom.mu
Mon Jun 10 12:56:15 UTC 2013


On Monday, June 10, 2013 02:24:13 PM Joe Abley wrote:

> It is frequently handy for debugging (I find) to be able
> to identify quickly whether a route was learnt from a
> route server or learnt in some other way.

I prefer the route server's AS_PATH to be elided from the 
the BGP updates I receive from it.

If I need to troubleshoot by just looking at BGP attribute 
data, I can look for the Loopback address that sourced the 
update (ORIGINATOR_ID attribute).

But that's just me...

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://afnog.org/pipermail/afnog/attachments/20130610/7e296df8/attachment.sig>


More information about the afnog mailing list