FW: transit alarms with a single-element AS-PATH
I'm receiving some events (for alarm 545) with only my own ASN in the path. If I understand correctly what is happening, the RRC box we peer with is receiving the prefix directly from us without our transit provider ASN prepended, so myasn is flagging it as a leak.
Looks like a bug. Are you coming into the office soon? Cheers, Matthew
-----Original Message----- From: Marco d'Itri [mailto:md@Linux.IT] Sent: 23 June 2004 18:38 To: ris@ripe.net Subject: transit alarms with a single-element AS-PATH
I'm receiving some events (for alarm 545) with only my own ASN in the path. If I understand correctly what is happening, the RRC box we peer with is receiving the prefix directly from us without our transit provider ASN prepended, so myasn is flagging it as a leak.
BTW, I think that it would be useful to sort by default on last seen date in show_alarmevents.html.
-- ciao, | Marco | [6886 cov/HgvPKMXiU]
Once Matthew Williams wrote:
Looks like a bug. Are you coming into the office soon?
Yes, possibly today? Alexis
HU and I have to attend a meeting between 15-16. Please time it before or shortly after :) Cheers, Matthew
-----Original Message----- From: ris-int-admin@ripe.net [mailto:ris-int-admin@ripe.net] On Behalf Of Alexis Yushin Sent: 25 June 2004 12:50 To: Matthew Williams Cc: 'Alexis Yushin'; ris-int@ripe.net Subject: [ris-int] Re: FW: transit alarms with a single-element AS-PATH
Once Matthew Williams wrote:
Looks like a bug. Are you coming into the office soon?
Yes, possibly today?
Alexis
participants (2)
-
Alexis Yushin -
Matthew Williams