Peeringdb: IXP membership entries keep disappearing for AS43369 (MINAP RRs)

[netravnen]

Useraccount "md _at_ seeweb _dot_ it" complains about the MINAP RRs in ticket 20503 _disappearing_ from the MINAP Internet Exchange.

Looking in the backend at ASN 43369 (MINAP RRs). I can deduce what $USER is experiencing. But I am unable to go any level deeper and deduce what (automated?) action caused this to be the case. ($USER writes they initially had "Allow IXP Update" enabled for 43369. But have disabled it now. And yes. The MINAP RRs is included in the IX-F feed)

I assume a server and/or application log file may be able to reveal more details than what is available in the Admin Dashboard?

Could $OPERATOR go a level deeper and maybe provide more details about the above issue?

[arnoldnipper]

Just look at https://peeringdb.com/cp/peeringdb_server/ixlanixfmemberimportlog/ to dive deeper into the issue. When looking there I see that the addresses where deleted as they are already in use somewhere else

[netravnen]

Is it possible to deduce from where the duplicate address conflicts
originates from?

/Netravnen

On Wed, 8 Aug 2018 at 19:37, Arnold Nipper [e-mail] wrote:

Just look at
https://peeringdb.com/cp/peeringdb_server/ixlanixfmemberimportlog/ to
dive deeper into the issue. When looking there I see that the addresses
where deleted as they are already in use somewhere else
[image: change ixf import log peeringdb]
https://user-images.githubusercontent.com/16888757/43854210-80a4cb1a-9b42-11e8-9e32-3637f0527a04.png

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/peeringdb/peeringdb/issues/357#issuecomment-411490186,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2T1Qb8GJVaT9YbAyKkAMTxf2NGCdYwks5uOyHlgaJpZM4VzxWp
.

[arnoldnipper]

curl -sG https://peeringdb.com/api/netixlan --data-urlencode ipaddr4__in=185.1.114.252,185.1.114.253 | jq '.data[] | [ .ix_id, .name ]'

should do the trick. But that query currently returns nothing

[arnoldnipper]

I've rolled back tonight's changes

[grizz]

I can take a look later, has anyone contacted them? We have seen similar before and it was a problem with the IX's export script.

[arnoldnipper]

Yes, we are in contact with them. For more info see first line of this issue ;-)

[grizz]

@arnoldnipper I don't see any communication with MINAP there, am I missing it?

[rfc1036]

"Them" would be me: feel free to ask here if needed.

[grizz]

@rfc1036 Oh, hi :) You've monitored your output and it's stable / consistent? Is that coming from IXP Manager or a custom script?

I'll be able to take a closer look from our side in a few hours.

[arnoldnipper]

@grizz ... https://peeringdb.deskpro.com/agent/#app.tickets,filter:24,t.o:20503,vis:5

[grizz]

@rfc1036 The route servers in your JSON dump are listed as AS64725 but on PDB they are AS43369 -- that wouldn't work, which is it supposed to be?

[rfc1036]

They were recently renumbered, looks like I had missed updating the IXP manager entry, thank you. Hopefully this should solve the issue.

[grizz]

Good deal, let us know if you still see any problems.

[arnoldnipper]

Thanks, Mr. Eagle Eye