- db-help - mailman.ripe.net

Updating import policy Level3 issues
by Amanda Galligan 02 Oct '14

02 Oct '14

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

1 0

Disputes in the Internet peering.
by Kshitiz Verma 30 Mar '14

30 Mar '14

Hi, I am Kshitiz Verma, a Ph.D. student in Madrid, Spain, working in the area of studies on the Internet ecosystem. We are conducting a survey on the Internet disputes, not limited to, but mainly focusing on de-peering. We will appreciate responses from the community that help us build our data on such incidences. We did an initial search ( https://docs.google.com/spreadsheet/ccc?key=0Ajn7QWBNzSlLdGo3UzFDVkNvdGVwYn…), but unfortunately the results we obtained were mostly limited to well known disputes in North America. We believe there should be more of them but are hard to find, 1. if they occur outside the Tier 1 regime. 2. if outside USA. 3. because the local news may not always be in English. 4. they may not last long or may not have as big an impact and find place in news. We are posting We are also looking for instances like Youtube hijacking by Pakistan Telecom is not a dispute between any two ASes but still for repairing purposes, connectivity between Pakistan Telecom and PCCW (AS 3491), Hong Kong was disrupted. At the same time, we are not looking for disruption of the Internet connectivity due to an accident like Taiwan earthquake in December 2006. As claimed in http://www.cs.columbia.edu/~misra/news/CD070113.pdf , 500 to 1000 de-peering happens on a daily basis today. We are curious to know how this number has evolved since its inception (starting from post commercialization of NSFNET is already very good but before that is excellent :-) ). Please fill in the following form if you have some information that you may want to share with us. Also, as there are so many de-peerings happening, there is a high possibility that most of these don't become International News, so to get information on these disputes we expanded our search to local and regional News but unfortunately this has not added significant information. Once the results are processed and filtered, we intend to share them publicly. Form: https://docs.google.com/forms/d/1X6msZeK0_3SIaIK8IxZaO2-Vrl1MPh_8dTSpbG0oGz… Many thanks in advance :-)

1 0

Allocations in the test database
by Vornanen Harri 27 Mar '14

27 Mar '14

Hello, Is it possible to create allocations in the test database yet? It would be helpful for test purposes, br,Harri

1 0

Database crash
by ripe＠foobar.dk 03 Mar '14

03 Mar '14

Mojn guys I had a server crash last week, and when I got it up and running again, the database was not able to receive updates - the whois-server core dumped. I've been there before, so I kept the old pseudo defect database running and rebuild a new DB during the night (downloading latest ripe.db.gz and RIPE.CURRENTSERIAL) Rebuilding ended up with an error. I can't remember seeing this before, but my first thought was that it something to do with the already running database. *** ERROR: Loader failure [139]. Exiting\n ************** ERROR *************** *** 04:56:54 Error loading database=WHOISDB for source=RIPE, /usr/local/whoisserver/bin/make_db exiting ************************************ I've started NRTM through the console, and everything looks fine, but apparently my current serial is 0 (zero) and not 28071882(+) as I would expect. 20140227 14:31:32 whois_rip-25050/2356136848 INFO connecting to NRTM server [whois.ripe.net:4444] (current serial=0) 20140227 14:31:32 whois_rip-25050/2356136848 INFO ******** report ********** 20140227 14:31:32 whois_rip-25050/2356136848 INFO 0 objects OK ( 0.0000 obj/s) 20140227 14:31:32 whois_rip-25050/2356136848 INFO 0 objects failed 20140227 14:31:32 whois_rip-25050/2356136848 INFO average processing time 0.0000 obj/s ( 0.00 obj/min) 20140227 14:31:32 whois_rip-25050/2356136848 INFO forwarded to serial:0 The old database (table serials) contains some 5051203 rows ending with serial=28072454 The new database (table serials) is pretty empty: mysql> desc serials; +-------------+---------------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +-------------+---------------------+------+-----+---------+----------------+ | thread_id | int(10) unsigned | NO | MUL | 0 | | | serial_id | int(11) | NO | PRI | NULL | auto_increment | | object_id | int(10) unsigned | NO | MUL | 0 | | | sequence_id | int(10) unsigned | NO | | 0 | | | atlast | tinyint(4) unsigned | NO | | 0 | | | operation | tinyint(4) unsigned | NO | | 0 | | +-------------+---------------------+------+-----+---------+----------------+ 6 rows in set (0.00 sec) mysql> select serial_id from serials; Empty set (0.00 sec) Digging deeper into the the problem I found this - this is the actual error when it crashed during make_db the first night: WARNING - 'Feb 27 04:56:54 snowblind kernel: [67641.487347] loader[22291]: segfault at 0 ip 00000000 sp bfb7fddc error 4 in loader[8048000+1a6000]' (1 matches for 'WARNING,[Ww]arning,ERROR,[Ee]rror') found in '/var/log/messages' I wonder if the ripe.db.gz is broken ("ip 00000000") ? So, I ran another make_db - but with the same result. Then I recovered an mysqldump from the start of the week, and it started up OK. Then I activated NRTM and updates started to roll in ... Happy I was for some hours; the server crash again saturday night :-( Today even startup of whois-server fails completely with core dumps, so I've picked another mysql backup and it's curently recovering. It seems me like one of the updates are causing problems - it's just a feeling - not a solid "Hey, here's the culprit!" fact. I've attached the error log (from today - core dumping (crash recovery mode + roll back)) Anyone ? Best Regards, Peter Landbo

1 0

Route object creating problem
by Pavel Korsakov 21 Nov '13

21 Nov '13

Hi, I can create routing object and I don't understand why. I got an error: ***Error: Authorisation for [route] 93.179.92.0/24AS49505 failed using "mnt-by:" The following object(s) were found to have ERRORS: --- Create FAILED: [route] 93.179.92.0/24AS49505 route: 93.179.92.0/24 descr: Selectel PI origin: AS49505 mnt-by: MNT-SELECTEL changed: korsakov(a)selectel.ru 20131121 source: RIPE ***Error: Authorisation for [route] 93.179.92.0/24AS49505 failed using "mnt-by:" not authenticated by: MNT-SELECTEL ***Error: Authorisation for [aut-num] AS49505 failed using "mnt-routes:" not authenticated by: MNT-SELECTEL ***Error: Authorisation for [inetnum] 93.179.92.0 - 93.179.92.255 failed using "mnt-routes:" not authenticated by: RU-TOP-MNT, MNT-SELECTEL But all seems to be fine: inetnum: 93.179.92.0 - 93.179.92.255 netname: TOP-NET descr: TOP LLC. country: RU admin-c: UD426-RIPE tech-c: UD426-RIPE org: ORG-TL279-RIPE status: ASSIGNED PA mnt-by: TRANSITTELECOM-MNT mnt-routes: RU-TOP-MNT mnt-routes: MNT-SELECTEL mnt-domains: RU-TOP-MNT source: RIPE # Filtered organisation: ORG-TL279-RIPE org-name: TOP LLC. org-type: OTHER address: 188544, Leningrad Region, Sosnovy Bor, Komsomolskaya, 8 mnt-ref: RU-TOP-MNT mnt-by: RU-TOP-MNT source: RIPE # Filtered person: Udimov Dmitry address: 188544, Leningrad Region, Sosnovy Bor, Komsomolskaya, 8 phone: +7 812 9977989 nic-hdl: UD426-RIPE mnt-by: RU-TOP-MNT source: RIPE # Filtered

2 2

Re: Problem in creating a domain
by Kadir Dogan // ExactHost 21 Oct '13

21 Oct '13

Hi, We are trying to create a domain for reverse dns with the following information: domain: 179.182.46.in-addr nserver: ns1.exactnet4.nl nserver: ns2.exactnet.nl descr: Reverse delegation for ExactHost admin-c: KD1483-RIPE tech-c: KD1483-RIPE zone-c: KD1483-RIPE mnt-by: Kadir-Dogan changed: hostmaster(a)exacthost.nl 20131018 source: RIPE But it fails with error code: ***Error: Syntax error in 179.182.46.in-addr Do you have any idea how to fix this? Wij vertrouwen erop u hierbij voldoende te hebben geïnformeerd. Indien u nog vragen heeft dan vernemen wij dat uiteraard graag van u. Met vriendelijke groet, Kadir Dogan --------------------------------- ExactHost Nederland BV Zichtenburglaan 16 2544 EB Den Haag * 070 - 388 77 11 Ê 070 - 388 82 23 * K.Dogan(a)exacthost.nl<mailto:K.Dogan@exacthost.nl> * http://www.exacthost.nl<http://www.exacthost.nl/> [Beschrijving: http://exacthost.grafia.nl/images/logo.gif]

2 1

Fwd: Re: [gii-people] Fwd: FW: FAILED: reverse
by Iñigo Ortiz de Urbina Cazenave 07 Oct '13

07 Oct '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Dear Reihaneh, Please find attached our reply to your question. Regards, > -------- Original Message -------- Subject: FW: FAILED: reverse > Date: Sun, 6 Oct 2013 14:14:23 +0330 From: javidi <ripe(a)dci.ir> To: > <db-help(a)ripe.net> > > > Dear Sir/Madam > > I sent the form below to define reverse DNS for a customer. But > these errors appear. Please inform me to tell him how to fix these > errors. > > My next question is about reverse delegation for assignments </24. > I've read page 111 Lir HAND BOOK.but I can't define reverse dns for > less than /24. > > > Best Regards Reihaneh Javidi. > > -----Original Message----- From: RIPE Database Administration local > [mailto:unread@ripe.net] Sent: Sunday, October 06, 2013 1:45 PM To: > ripe(a)dci.ir Subject: FAILED: reverse > >> From: javidi <ripe(a)dci.ir> Subject: reverse Date: >> Sun, 06 Oct 2013 12:14:03 +0200 Reply-To: javidi <ripe(a)dci.ir> >> Message-ID: <00d401cec27c$9c8e7c80$d5ab7580$@ir> > > SUMMARY OF UPDATE: > > Number of objects found: 1 Number of objects > processed successfully: 0 Create: 0 Modify: 0 > Delete: 0 No Operation: 0 Number of objects processed > with errors: 1 Create: 1 Modify: 0 Delete: > 0 > > DETAILED EXPLANATION: > > ***Warning: Invalid keyword(s) found: reverse ***Warning: All > keywords were ignored > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following > object(s) were found to have ERRORS: > > --- Create FAILED: [domain] 140.38.78.in-addr.arpa > > domain: 140.38.78.in-addr.arpa descr: Reverse > Delegation for ikk.ir IP range. admin-c: MT7308-RIPE tech-c: > MT7308-RIPE zone-c: MT7308-RIPE nserver: > ns1.parsdata.com nserver: ns2.parsdata.com mnt-by: > AS12880-MNT notify: javadshoaei(a)yahoo.com changed: > ripe(a)dci.ir 20131006 source: RIPE > > ***Error: Superfluous name server listed at parent: > ns1.parsdata.com > > A name server listed at the parent, but not at the child, was > found. This is most likely an administrative error. You should > update the parent to match the name servers at the child as soon > as possible. > > ***Error: Superfluous name server listed at parent: > ns2.parsdata.com > > A name server listed at the parent, but not at the child, was > found. This is most likely an administrative error. You should > update the parent to match the name servers at the child as soon > as possible. 11:04:21-iortiz~$ dig ns 140.38.78.in-addr.arpa @ns1.parsdata.com +short parsdata-helm. 11:05:58-iortiz~$ dig ns 140.38.78.in-addr.arpa @ns2.parsdata.com +short 11:06:01-iortiz~$ ns2.parsdata.com returns NXDOMAIN. ns1.parsdata.com returns invalid answers (see below). > ***Error: Total parent/child glue mismatch. > > The parent lists name servers that the child doesn't know about; > see details in advanced. This configuration could actually work > but breaks very easily if one of these zones changes slightly. 10:58:26-iortiz~$ dig @ns24.parsweb.com ns1.parsdata.com +short 217.66.216.70 10:58:29-iortiz~$ dig @ns24.parsweb.com ns2.parsdata.com +short 217.66.216.80 10:58:32-iortiz~$ dig @ns25.parsweb.com ns1.parsdata.com ; <<>> DiG 9.8.3-P1 <<>> @ns25.parsweb.com ns1.parsdata.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached 10:58:58-iortiz~$ dig @ns25.parsweb.com ns2.parsdata.com ; <<>> DiG 9.8.3-P1 <<>> @ns25.parsweb.com ns2.parsdata.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached ns25.parsweb.com seems to be unavailable. > ***Error: No address found for parsdata-helm. > > No IPv4 or IPv6 address was found for the host name. Explained next. > ***Error: Host name or address error for parsdata-helm. > > The specified host name is not a valid host name or the host name > points to an invalid IP address, e.g. a private or reserved IP > address. The MNAME of the SOA record in the zone file defined on their auth servers (ns[12].parsdata.com) must be the valid hostname of the master server (unless a hidden master setup is in use, which is not the case most surely) > ***Error: Invalid SOA RNAME syntax for 140.38.78.in-addr.arpa: > hostmaster > > The email address specified in SOA RNAME is specified incorrectly. > A common error is to use @ in the address field - an address like > hostmaster(a)example.com must be specified as > hostmaster.example.com. The RNAME of the SOA record in the zone file defined on their auth servers must have the correct syntax, outlined above. > ***Warning: Error while checking SOA MNAME for > 140.38.78.in-addr.arpa (parsdata-helm). > > The SOA MNAME is not a valid host name. > Ditto > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > The RIPE Database is subject to Terms and Conditions: > http://www.ripe.net/db/support/db-terms-conditions.pdf > > For assistance or clarification please contact: RIPE Database > Administration <ripe-dbm(a)ripe.net> > > Generated by RIPE WHOIS Update version 1.69 on WHOIS4 Handled > email update (RIPE, 2013-10-06 12:14:40) > In summary, all the issues reported above must be fixed before he can re-attempt to delegate or we help them further - should he still get the errors. -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) Comment: GPGTools - http://gpgtools.org iQEcBAEBCgAGBQJSUolOAAoJELPfvrguw2h1hP0H/R6RGB+gBFXqI7yrNCerE/bm Hln00OVOwtRj6JNe7F/aM5xfxXq7vFbVBAU7PEAjQyUQxlF4RPYowiv44d/5fsed FPdVZ0/0MvCMro8lFN9ag2/bRGXxi+vLUCfFf+VNxOGOfnCtIvCw8XLkWoqnA3lY /b/xgR2wRW6oGcewStndolinTRkSS8x1pHKPX6xmL+Ee9ok/BxNebFteqJ/XNoyJ +b+yryLp1shd7o5qJ/xRrYn0MX47yj6TAQd7XJY/ArhCJytvjn7tKFs/dL9+9xbU jmR6+gS8XLzagVglVNqoGUYv8NN7baY4bLuKANJ+5j0tt1OLtjYvmEhdwmsLLVc= =LU6+ -----END PGP SIGNATURE-----

1 0

FW: FAILED: reverse
by javidi 06 Oct '13

06 Oct '13

Dear Sir/Madam I sent the form below to define reverse DNS for a customer. But these errors appear. Please inform me to tell him how to fix these errors. My next question is about reverse delegation for assignments </24. I've read page 111 Lir HAND BOOK.but I can't define reverse dns for less than /24. Best Regards Reihaneh Javidi. -----Original Message----- From: RIPE Database Administration local [mailto:unread@ripe.net] Sent: Sunday, October 06, 2013 1:45 PM To: ripe(a)dci.ir Subject: FAILED: reverse > From: javidi <ripe(a)dci.ir> > Subject: reverse > Date: Sun, 06 Oct 2013 12:14:03 +0200 > Reply-To: javidi <ripe(a)dci.ir> > Message-ID: <00d401cec27c$9c8e7c80$d5ab7580$@ir> SUMMARY OF UPDATE: Number of objects found: 1 Number of objects processed successfully: 0 Create: 0 Modify: 0 Delete: 0 No Operation: 0 Number of objects processed with errors: 1 Create: 1 Modify: 0 Delete: 0 DETAILED EXPLANATION: ***Warning: Invalid keyword(s) found: reverse ***Warning: All keywords were ignored ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following object(s) were found to have ERRORS: --- Create FAILED: [domain] 140.38.78.in-addr.arpa domain: 140.38.78.in-addr.arpa descr: Reverse Delegation for ikk.ir IP range. admin-c: MT7308-RIPE tech-c: MT7308-RIPE zone-c: MT7308-RIPE nserver: ns1.parsdata.com nserver: ns2.parsdata.com mnt-by: AS12880-MNT notify: javadshoaei(a)yahoo.com changed: ripe(a)dci.ir 20131006 source: RIPE ***Error: Superfluous name server listed at parent: ns1.parsdata.com A name server listed at the parent, but not at the child, was found. This is most likely an administrative error. You should update the parent to match the name servers at the child as soon as possible. ***Error: Superfluous name server listed at parent: ns2.parsdata.com A name server listed at the parent, but not at the child, was found. This is most likely an administrative error. You should update the parent to match the name servers at the child as soon as possible. ***Error: Total parent/child glue mismatch. The parent lists name servers that the child doesn't know about; see details in advanced. This configuration could actually work but breaks very easily if one of these zones changes slightly. ***Error: No address found for parsdata-helm. No IPv4 or IPv6 address was found for the host name. ***Error: Host name or address error for parsdata-helm. The specified host name is not a valid host name or the host name points to an invalid IP address, e.g. a private or reserved IP address. ***Error: Invalid SOA RNAME syntax for 140.38.78.in-addr.arpa: hostmaster The email address specified in SOA RNAME is specified incorrectly. A common error is to use @ in the address field - an address like hostmaster(a)example.com must be specified as hostmaster.example.com. ***Warning: Error while checking SOA MNAME for 140.38.78.in-addr.arpa (parsdata-helm). The SOA MNAME is not a valid host name. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The RIPE Database is subject to Terms and Conditions: http://www.ripe.net/db/support/db-terms-conditions.pdf For assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> Generated by RIPE WHOIS Update version 1.69 on WHOIS4 Handled email update (RIPE, 2013-10-06 12:14:40)

1 0

Override authentication failed (via lirportal)
by David Freedman 21 Mar '13

21 Mar '13

Hi all, I'm trying to update my ORG objects via lirportal this morning and getting "Override authentication failed" , I know this isn't the lirportal support hotline but could somebody tell me if this is to be expected? or could they take a look? Dave.

2 2

Error: There is no parent object while creating inetnum
by Moritz Lenz 14 Jan '13

14 Jan '13

Hi, I'm having trouble generating some assignments: Error while creating object through syncupdates API: - From-Host: 62.128.1.62 - Date/Time: Fri Jan 11 15:36:54 2013 SUMMARY OF UPDATE: Number of objects found: 1 Number of objects processed successfully: 0 Create: 0 Modify: 0 Delete: 0 No Operation: 0 Number of objects processed with errors: 1 Create: 1 Modify: 0 Delete: 0 Syntax Errors: 0 DETAILED EXPLANATION: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following object(s) were found to have ERRORS: --- Create FAILED: [inetnum] 62.128.31.128 - 62.128.31.131 ***Error: Authorisation failed ***Info: Syntax check passed inetnum: 62.128.31.128 - 62.128.31.131 netname: testblubb2 country: DE descr: noris network AG admin-c: ML1-TEST tech-c: ML1-TEST status: ASSIGNED PA notify: guardian(a)noris.net mnt-by: NORIS-MNT source: TEST changed: moritz.lenz(a)noris.de ***Warning: Date '20130111' added to changed: attribute 'moritz.lenz(a)noris.de' ***Error: There is no parent object ***Info: Authorisation for [inetnum] 62.128.31.128 - 62.128.31.131 using mnt-by: authenticated by: NORIS-MNT ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The RIPE Database is subject to Terms and Conditions: http://www.ripe.net/db/support/db-terms-conditions.pdf For assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> Generated by RIPE WHOIS Update version 1.50.2 on WHOIS2 Handled sync update (TEST, LGC, 2013-01-11 15:36:54) at /home/mlenz/src/kunde/kunde/add/kunde_ipaddr line 339 I'm kinda guessing that the 'parent object' that the error message talks about is meant to be the allocation -- but that exists: $ whois -h whois-test.ripe.net 62.128.31.128 % This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See http://www.ripe.net/db/support/db-terms-conditions.pdf % Information related to '62.128.0.0 - 62.128.31.255' inetnum: 62.128.0.0 - 62.128.31.255 netname: DE-NORIS-990421 descr: noris network AG org: ORG-TT1-TEST country: DE admin-c: ML98-TEST tech-c: ML98-TEST status: ALLOCATED PA mnt-by: TEST-NCC-HM-MNT mnt-lower: NORIS-MNT mnt-routes: NORIS-MNT source: TEST changed: nobody(a)example.com 20130111 and has the correct mnt-lowerk afaict. So, what's the problem here? Cheers, Moritz

2 2