On 21 Mar 2016, at 16:28, Paul Thornton wrote:
Hi,
On 21/03/2016 16:16, Gareth Bryan wrote:
Hi All,
Just looking for output from a 3356 session in Manchester for any of
our prefixes (e.g 62.121.0.0/19)
A customer of mine has 3356 transit in Manchester, but is default-only
so table contents aren't really that valid.
I can help in the other direction though. How do you see
217.9.192.0/20 ?
L3 build all their import filters from RADB/RIPE-DB so you must have all
your route and as-set objects in good order.
I would guess that your announcement is being filtered on receipt by L3,
and you need to fix your data.
It’s been a while since I was a L3 customer, but IIRC they rebuild
their filters every 24 hours. You can request a manual update via
support, but it’ll be overwritten by the next automatic update.
62.121.0.0/19 has origins 16034 and 8607 in the ripe database.
AS3356 at whois.radb.net shows an import AS-KEME from AS16034 but
nothing from AS8607
My view of the table has:
er1#sh ip bgp 62.121.0.0
BGP routing table entry for 62.121.0.0/19, version 72392
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
30740 8607
82.219.48.254 from 82.219.48.254 (82.219.0.92)
Origin IGP, localpref 50, valid, external, best
Community: 29474:62110 29474:65003
AS8607 object in the RIPE DB has no mention of 3356
Assuming your adjacency is 3356<->16034, you need AS-KEME to include
AS8607 (or AS-ATLAS) .. but it doesn’t appear to.
d.
