-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, myASn has to detect an update from a RIS peer somewhere that 'conflicts' with your configuration. Check one of the 'bogus' prefixes in BGPlay for the time period that that alarm was configured. If you see activity there that you feel should have triggered an event, which you didn't see in 'pending events' on the 'Manage Alarms' page or 'view details' on the 'View Alarms' page, then we would have to dig deeper to see whether it's a bug. You can use one of the RIS routing beacon as a reference (originated from AS12654), just to make sure that the myASn system is actually doing something. The list of prefixes is available here: http://www.ripe.net/ris/beaconlist.html Please note that syslog will report conflicting 'events' rather than 'alarms', and that the feature is very experimental at this stage. Thanks for testing myASn! Kind regards, Matthew Williams
-----Original Message----- From: Hroi Sigurdsson [mailto:hroi@ngdc.net] Sent: 06 July 2004 19:51 To: risops@ripe.net Subject: Re: myASn Account Created
Thanks.
I created two bogus alarms just for testing, but I don't get alerts? Alarm 741 and 742 are bogus.
-----BEGIN PGP SIGNATURE----- Version: PGP 7.0.4 iQA/AwUBQOwS5cHkFbJe+GdoEQL6HACfQzS9znECa/P6rhU9KNQBVQynU/gAn2fJ CS2EKxjdAdQ+aa3LDJKyB0sx =yAQY -----END PGP SIGNATURE-----