MyASN FAQs

1. How do I log on to MyASN?
2. How do I log out of MyASN?
3. How do I add new users for my AS Number?
4. What are active and inactive alarm events?
5. How are alarm events generated by MyASN?
6. When are alarm events removed from the alarm database by MyASN?
7. What happens to the MyASN alarm database when I change the alarm configuration?
8. Who do I contact for MyASN support?

How do I log on to MyASN?

Logging On

1. Goto the MyASN start page
2. Enter your user name and Autonomous System Number (ASN), separated by an 'at-sign', e.g. harold@1066, and then your password in the field below
3. Click 'OK'
4. You should now see the MyASN main page

You can ask for more MyASN user accounts by filling in the MyASN account creation form.

How do I log out of MyASN?

Quoted from Apache's Authentication FAQ:

"How do I log out?

Since browsers first started implementing basic authentication, website administrators have wanted to know how to let the user log out. Since the browser caches the username and password with the authentication realm, as described earlier in this tutorial, this is not a function of the server configuration, but is a question of getting the browser to forget the credential information, so that the next time the resource is requested, the username and password must be supplied again. There are numerous situations in which this is desirable, such as when using a browser in a public location, and not wishing to leave the browser logged in, so that the next person can get into your bank account. However, although this is perhaps the most frequently asked question about basic authentication, thus far none of the major browser manufacturers have seen this as being a desirable feature to put into their products."

How do I add new users for my AS Number?

Fill in the MyASN account creation form.

All users of the same ASN will have access to the same MyASN account.

All registered MyASN users are added to the myasntesting mailing list.

What are active and inactive alarm events?

• Active Alarm Events correspond to BGP routing information from RIS peers that conflict with the expected values as specified on the alarm configuration page. Manipulation of "Holddown Time" and "Holddown Events" will affect when an alarm message is sent to a user's e-mail account.
  
  
• Inactive Alarm Events are active events that have been reset by MyASN following the detection of a BGP withdrawal message from the same RIS peer that caused the event. An e-mail notification will be triggered and sent to the specified users as soon as an active alarm event becomes inactive.

Active events are displayed on the current alarms page in red and inactive events in black.

How are alarm events generated by MyASN?

This principle is illustrated below with an example.
Suppose that, hypothetically, you have set an "Origin Alarm" with the following configuration in your MyASN account for AS(A).

When AS(B) inadvertently announced the same prefix on June 17th, 2003, several alarm events were detected by MyASN from RIS peers and listed on the current alarms page in account AS(A):

• Peer(1) triggered an alarm event on 17 June 2003, at 00:44:06. After the first occurrence, MyASN detected three more BGP announcements where the prefix originated from AS(B) instead of AS(A). In total, there are four alarm events.
  
  
• Peer(2) triggered only one alarm event at 00:47:00 on the same day.
  
  
• Peer(3) triggered six events. The first occurrence happened on 17 June 2003, at 00:50:16 and was followed by another five.

Please observe that each row relates to three different peers.

The "Time to Live" value in seconds determines when the entries should be deleted from the current alarm page. In this case, peer(1)'s entry would be removed at 04:44:06, 14,400 seconds after the first occurrence, peer(2)'s entry at 04:47:00 and peer(3)'s entry at 04:50:16.

When are alarm events removed from the alarm database by MyASN?

All alarm events, active and inactive, are removed from the alarm database when the "Time to Live" expires. By default this happens after four hours (14,400 seconds).

What happens to the MyASN alarm database and the alarm event entries in the user interface when I change the alarm configuration?

When the "Time to Live" value expires, the alarm database cleans out old entries. The new configuration then becomes active and will be used the next time MyASN scans RIS peers for conflicting BGP routing information, usually within the hour.

Who do I contact for MyASN support?

For any extra information, please contact the RIS project team.