July 2004 - myasntesting - mailman.ripe.net

Re: myASn Account Created
by Hroi Sigurdsson 12 Jul '04

12 Jul '04

Matthew Williams wrote: > Hi there, > > >>morning from the one bogus entry and from the transit alarms, >>triggered >>by peer propagation. > > > Great :) > > I really appreciate that you're investing the time to investigate our system. Please feel free to suggest some features that you > think are missing in the current implementation. You're welcome. It is a useful tool. A cool feature would be auto-configuration (even auto-updating?) of alerts from info in aut-num objects. Another nice feature would be detection of leaks, ie. "only this set of prefixes may have my AS in the path". Comparative checks: "These prefixes must have identical paths" etc. (might be too noisy). Bug? Customer alerts contain empty AS fields: Customer alarm 742 (Default), 217.145.48.0/20 (exceptions not shown), MyASn: , Their ASn: , HDT: 60, HDE: 1, TTL: 3600 .=------+-----------------+--------------+--------------------------+-------------------------=. | RRC | Prefix | Peer | First Seen | Last Seen | |=------+-----------------+--------------+--------------------------+-------------------------=| | rrc10 | 217.145.48.0/20 | 217.29.66.65 | Wed Jul 7 02:02:01 2004 | Wed Jul 7 02:02:01 2004 | '=------+-----------------+--------------+--------------------------+-------------------------=' -- Hroi Sigurdsson · NetGroup DataCenter A/S St. Kongensgade 40H · DK-1264 Copenhagen K, Denmark Phone: +45 3370 1544 · Fax: +45 7025 2687

2 1

NOTIFICATION: myASn inaccessable from 4pm, CET, today (09.07.2004) , until 10am, CET, on Monday (12.07.2004)
by Matthew Williams 09 Jul '04

09 Jul '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear All, Due to a code update of the myASn beta, users will not be able to access the system over the weekend. We also expect that notifications during the maintenance window may be unreliable, and probably better ignored. The update and the following testing will commence at 4pm, CET, today (09.07.2004) and be completed by 10am, CET, on Monday (12.07.2004). Apologies for the short notice. Kind regards, Matthew Williams --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.4 iQA/AwUBQO6Z5sHkFbJe+GdoEQKomgCgtuNeg3IHx3TEyIUilZgq0qMQc7wAn0Ex eFOtVISez4CTTvb2zuPhNvQW =1COI -----END PGP SIGNATURE-----

1 0

RE: myASn Account Created
by Matthew Williams 07 Jul '04

07 Jul '04

-----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(a)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-----

1 0

NOTIFICATION: Old myASn Prototype Deprecated
by Matthew Williams 05 Jul '04

05 Jul '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear All, We will be turning off the old prototype at URL: http://www.ris.ripe.net/cgi-bin/myas/index.cgi on Friday, the 9th of July, 2004. The current beta is available here: http://www.ris.ripe.net/myasn.html. Just type in your old account information from the previous myASn prototype in the following format (without apostrophes): U: 'user@asn' PW: 'old password' There is a tool in this newer version of myASn, which allows you to import origin alarms into the configuration. Alas, the other alarm types could not be included due to design changes. Thanks for testing myASn. Your comments are more than welcome. Kind regards, The RIS Team --- > Matthew Williams (MW243-RIPE) > Customer Liaison Engineer > RIPE NCC - http://www.ripe.net/np/ -----BEGIN PGP SIGNATURE----- Version: PGP 7.0.4 iQA/AwUBQOkedcHkFbJe+GdoEQK79gCeOxN/AbisyC88LpUD+FisVcwkRrUAoOqZ jNHaLfm32jpAyrUDc75ZkCyG =aJvw -----END PGP SIGNATURE-----

1 0