Routing diff report, Rancid for BGP
Just like many you, I use rancid to track changes in configurations of our routers and switches. This week BGPmon.net released a new feature called ‘routing report’, you can think of this as a Rancid for your BGP routing table. Every day BGPmon compares the announcements by your ASN with those of the day before. Any differences in announcements or reachability will be sent to you in an email.
I’ve been using this feature for a few weeks now and found it very useful.
The things it will report on is differences in announced prefixes, including a breakdown of which prefixes are reachable via which upstream / peer AS. This will help you detect if a prefix is no longer reachable via one or all peers or upstreams.
The routing report will also report on upstream and downstream ASns. At the end of this blog post you’ll find an example report. Please note that each report also contains a summary report of your AS, comparable to the cidr report.
This routing report feature can be enabled/disabled on a per AS basis in the ‘my ASn’ page.
Update January 12, 2010
The routing report feature is disabled by default. If you would like to use this feature you will need to enable it.
New Prefix alert (code60)
If you recently started to announce a new prefix, then you most likely received a BGPmon email with a New Prefix (code60) alert. These notifications are send out as soon as your AS starts to originate a new prefix.
This feature could only be enabled / disabled globally via the settings menu. If you’re using BGPmon.net for multiple ASns chances are that for some ASns you would like to have this feature enabled and for some disabled. As of this week this is possible and you should now be able to configure this on a per ASn basis.
Adding your AS to My ASn
All the ASns your are currently monitoring should have been added to ‘My ASn’ automatically. If you add a new prefix and ASn to my prefixes, remember to also add your AS to ‘My ASn’. Otherwise the ‘routing report’ and ‘New Prefix alert’ will not work, as your ASn needs to be added manually.
As always if you have any questions please leave a comment on this blog or send me an email.
From: BGPmon Alert < info@bgpmon.net > To: you@gmail.com Subject: BGPmon Routing report Date: Sun, 10 Jan 2010 02:53:27 +0100 (CET) Your routing table report for AS271 (BCNET-AS - BCnet) ================================== Changes: ==================================== RIB file used: RRC01 -- LINX, London RRC03 -- AMS-IX / NL-IX / GN-IX, Amsterdam RRC11 -- NYIIX, New York RRC12 -- DE-CIX, Frankfurt RRC13 -- MSK-IX, Moscow RRC15 -- PTTMetro, Sao Paulo ------ AS Adjacency report ------ New Downstream / Customer AS: + AS25689 (NRCNET-AS - National Research Council of Canada) ------ Prefixes report ------ Lost prefixes for AS271 - 207.23.245.0/24 (Sky Research Inc.) - 209.87.17.0/24 (UBC Commercial Client) ------ Prefixes reachable via peers report ------ + 134.87.113.0/24 via AS6939 (BCNET IPv6 awareness day) now reachable via HURRICANE - Hurricane Electric, Inc. + 2607:f8f0:690::/48 via AS6939 (No valid route object!) now reachable via HURRICANE - Hurricane Electric, Inc. - 209.87.17.0/24 via AS6509 (UBC Commercial Client) no longer reachable via CANARIE-NTN - Canarie Inc - 207.23.245.0/24 via AS6509 (Sky Research Inc.) no longer reachable via CANARIE-NTN - Canarie Inc - 209.87.17.0/24 via AS6939 (UBC Commercial Client) no longer reachable via HURRICANE - Hurricane Electric, Inc. - 207.23.245.0/24 via AS6939 (Sky Research Inc.) no longer reachable via HURRICANE - Hurricane Electric, Inc. ================ AS271 Summary report 01/09/10 23:59:58: ==================== Upstream Adjacent AS list: *AS852 ASN852 - Telus Advanced Communications) *AS6327 SHAW - Shaw Communications Inc.) *AS6509 CANARIE-NTN - Canarie Inc) *AS6939 HURRICANE - Hurricane Electric, Inc.) *AS13768 PEER1 - Peer 1 Network Inc.) Downstream Adjacent AS list: *AS3633 BC-SYSTEMS - Province of British Columbia) *AS11105 SFU-AS - Simon Fraser University) *AS16462 UVIC-AS - University of Victoria) *AS25689 NRCNET-AS - National Research Council of Canada) *AS25722 GATEWAY-OPERATIONS - Payment Processing Inc.) *AS32956 ZED-RADIO3 - Canadian Broadcasting Corporation) *AS36000 NHA-ASN1 - Northern Health Authority) *AS36391 TRIUMF - TRIUMF (Tri-University Meson Facility)) *AS25689 NRCNET-AS - National Research Council of Canada Announced IPv6 prefixes: *2607:f8f0:670::/48 (No valid route object!) *2607:f8f0:680::/48 (No valid route object!) *2607:f8f0:690::/48 (No valid route object!) *2607:f8f0::/32 (No valid route object!) Announced IPv4 prefixes: *128.189.0.0/16 (BCNet Class B network) *128.189.0.0/17 (BCNet network) *128.189.128.0/18 (UBC RESnet network) *128.189.192.0/18 (UBC wireless network) *128.189.4.0/24 (No valid route object!) *128.189.64.0/19 (No valid route object!) *128.189.96.0/19 (No valid route object!) *134.87.0.0/16 (BCNET-2) *134.87.112.0/24 (BCnet gigapop servers - News,DNS) *134.87.113.0/24 (BCNET IPv6 awareness day) *134.87.114.0/23 (BCNET conference 2009 (DUAL stack)) *134.87.2.0/24 (BCnet gigapop C3 interconnect links) *134.87.3.0/24 (UBC_TRU DR project) *134.87.4.0/24 (BC Genome Sequence Centre) *134.87.58.0/24 (BCnet gigapop C3 interconnect links) *137.82.0.0/16 (UBC) *142.103.0.0/16 (University of British Columbia (UBC1)) *142.207.0.0/16 (NET-UNBC) *142.231.0.0/16 (BCNET3) *142.231.1.0/24 (BCnet gigapop C3 interconnect links) *142.231.110.0/24 (BCNET VANTX interconnects) *142.231.112.0/24 (BCnet gigapop servers - News,IRR) *142.231.113.0/24 (BCnet gigapop servers - RealServer, Video Server) *142.231.142.0/24 (BCnet gigapop connections) *142.231.2.0/24 (No valid route object!) *142.231.20.0/24 (UBC MedSchool AV Network) *142.231.3.0/24 (BCIT Internet Engineering Lab) *142.231.4.0/24 (UBC MedSchool AV Network) *142.231.5.0/24 (UBC MedSchool AV Network) *142.231.64.0/19 (University of British Columbia (UBC) Okanagan) *142.232.0.0/16 (BCITNET2) *142.90.0.0/16 (TRIUMF) *192.139.193.0/24 (DPIC) *192.146.156.0/24 (Thompson Rivers University) *192.219.32.0/19 (Open Learning Agency) *192.68.67.0/24 (British Coulmbia Institute of Technology (NET-192-68-67-0-2)) *192.68.68.0/24 (British Coulmbia Institute of Technology (NET-192-68-68-0-1)) *192.68.69.0/24 (British Coulmbia Institute of Technology (NET-192-68-69-0-1)) *192.68.72.0/24 (British Columbia Institute of Technology (BCIT)) *192.68.73.0/24 (BCIT Internet Engineering Lab) *192.73.5.0/24 (University of British Columbia (CDNnet)) *198.162.20.0/22 (BCNET-AGG-13) *198.162.32.0/19 (University of British Columbia (UBC-CS)) *198.162.67.0/24 (Forintek) *199.175.163.0/24 (SPINNAKER) *199.60.119.0/24 (Emily Carr Institute of Art and Design) *199.60.120.0/24 (Emily Carr Institute of Art and Design) *199.60.226.0/23 (Emily Carr Institute of Art and Design) *204.239.83.0/24 (NETBLK-UNBC-DMZ) *206.12.0.0/16 (NETBLK-BR-COL-6) *206.12.0.0/24 (BCNET ORAN interconnect links) *206.12.10.0/24 (Great Northen Way Digital Arts) *206.12.104.0/22 (University of British Columbia (UBC) Vancouver BCWARN BC Amateur Radio Network) *206.12.11.0/24 (E-Learning Conference) *206.12.12.0/24 (UBC Commercial Clients) *206.12.14.0/24 (CANFOR) *206.12.18.0/24 (UBC Commercial Clients) *206.12.19.0/24 (UBC Commercial Clients Debian Project) *206.12.2.0/24 (No valid route object!) *206.12.24.0/22 (WestGrid project) *206.12.24.0/24 (WestGrid) *206.12.28.0/24 (UBC Commercial) *206.12.52.0/22 (UBC eduroam wireless) *206.12.8.0/24 (WestGrid project inter-router links) *206.123.160.0/19 (Thompson Rivers University) *206.87.0.0/16 (BCNET (Non-portable address space)) *206.87.0.0/18 (University of British Columbia (UBC) Okanagan) *206.87.128.0/19 (University of British Columbia (UBC) Vancouver wireless) *206.87.96.0/19 (University of British Columbia (UBC) Vancouver wireless) *207.23.0.0/16 (BR-COL-8) *207.23.128.0/19 (BC Childrens and Womens Hospital) *207.23.240.0/24 (BCnet gigapop interconnects (BCNET-4)) *207.23.241.0/24 (BCNET VICTX interconnects) *207.23.242.0/24 (BCNET PGTX interconnects) *207.23.243.0/24 (BC Research - UBC Commercial Client) *207.23.249.0/24 (UBC Commercial Client) *207.23.252.0/24 (UBC Commercial Client) *207.23.254.0/24 (BCNET KELTX interconnects) *207.23.255.0/24 (BCNET KAMTX interconnects) *207.23.78.0/24 (UBC Research Enterprises Inc.) *207.23.8.0/21 (University College of the Cariboo) *207.23.94.0/24 (BCnet gigapop C3 interconnect links) *207.23.95.0/24 (BCnet gigapop C3 interconnect links) *207.23.96.0/20 (Royal Roads University (RRU)) *209.87.0.0/18 (BCNET-5) *209.87.18.0/24 (Prince George Public Library) *65.39.232.0/22 (Farleigh Dickinson University Vancouver campus) * The upstream / downstream categorisation in this report is strictly a description relative topology, and should not be confused with provider / customer / peer inter-AS relationships.
3 comments
What does “(No valid route object!)” mean after an announced prefix? All of my routes are reachable so I’m not understanding this one.
Thanks so much for this site/tools. It has been a huge help for me.
Hi Adam,
Good to hear that you find this tool useful.
“(No valid route object!)” means that no route object was found for the announced prefix. It’s good practice to have route objects for all your prefixes in one the IRR’s.
With valid we mean: an Exact match, ie, same prefix and same prefix length and same origin AS.
This would be a valid route object for 145.88.0.0/15 announced by AS1103
whois -h whois.radb.net 145.88.0.0/15route: 145.88.0.0/15
descr: LUMC-NET HVUNET
origin: AS1103
notify: info@surfnet.nl
mnt-by: AS1103-MNT
changed: peter.vons@sara.nl 20020227
source: RIPE
Hope that answers your question.
Thanks for your help. That answers the question perfectly.