Not sure if right place here and followed notification procedure to
stat(a)ripe.net [ticket #1140111]...
I've found some *missing prefix/asn* returned from query to COUNTRY
RESOURCE
https://stat.ripe.net/data/country-resource-list/data.json?resource=it
It seems that response list is missing all those ipv4 resource lines that
before were returned as RANGE instead of CIDR, and obviously related asn.
For example 151.3.0.0/16 is related to country IT (
https://stat.ripe.net/data/whois/data.json?resource=151.3.0.0/16) but* this
prefix and its ASN is missing in response country resource list* of above
query.
Earlier ,sure at 13 JUL 2014, this prefix was in response as contained in
range 151.3.0.0-151.84.255.255.
Regards,
We've begun advertising a new subnet to our Level3 transit and were required to setup a route object for our prefix which is now in place.
route: 37.0.5.0/24<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=37.0.5.0/24AS19…>
descr: Workday Limited
origin: AS198993<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=AS198993&type=a…>
mnt-by: MNT-WORKD-EU<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=MNT-WORKD-EU&ty…>
changed: amanda.galligan(a)workday.com<mailto:amanda.galligan@workday.com> 20141001
source: RIPE
We have a pre-existing as-set object that is being used by Level3 import policy to update their filters with our advertised routes
as-set: AS-Workday-AMS-L3peer<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=AS-Workday-AMS-…>
descr: Workday Limited
members: AS198993<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=AS198993&type=a…>
tech-c: VAZ28-RIPE<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=VAZ28-RIPE&type…>
admin-c: VAZ28-RIPE<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=VAZ28-RIPE&type…>
mnt-by: mnt-workd-eu<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=mnt-workd-eu&ty…>
source: RIPE # Filtered
When we use the following whois check we only see our existing subnet 37.0.4.0/24 listed and not 37.0.5.0/24
bash-4.1$ whois -h filtergen.level3.net RIPE::AS-Workday-AMS-L3peer
Prefix list for policy RIPE::AS-Workday-AMS-L3peer =
RIPE::AS198993
37.0.4.0/24
However this prefix is clearly available below.
arg@$ whois AS-Workday-AMS-L3peer | grep members |awk '{print $2}' | xargs whois -i origin | grep route
route: 37.0.4.0/24
route: 37.0.5.0/24
arg@Ubuntu02:~/code/tools$
Level3 are saying that we need to associate 37.0.5.0/24 with AS198993 which is already in place an wait two days for update but its been over two days and this still hasn't been updated.
Upon contacting Level3 they informed us that we need to do following but I'm not clear on what they are actually looking for us to do here?
***************************************************
[CUSTOMER UPDATE] EMEA Technical Service Centre
[SUMMARY OF WORK]
To update the prefix-list, you need to update your RIPE::AS-Workday-AMS-L3peer import policy RIPE::AS-Workday-AMS-L3peer with all the prefixes you are advertising. Once done, our prefix-list will be automatically updated from RIPE (this process takes up to 48 hours).
Please do keep your import policy up to date for more flexibility and allow up to 48 hours to our automatic process to complete once your routing registry is updated.
Any advise on where I'm going wrong here greatly appreciated.. I've done this previously for 37.0.4.0/24 and didn't need to do anything additional to what I've already done above.
Amanda
