Forwarded to myasntesting...
> -----Original Message-----
> From: Arife Vural [mailto:arife@ripe.net]
> Sent: 17 December 2003 12:00
> To: Andreas Laudwein
> Cc: ris(a)ripe.net
> Subject: Re: MyASN - no alarms
>
>
>
> Hi Andreas,
>
> > I wrote a question to Maximo, he responded but that was on his last
> > working day for RIPE, so I'm now getting back to you with further
> > questions ;-)
>
> I try to answer your question as much I can :-)
>
> > >>We just had a look at MyASN, configured it and waited for alarms,
> > >>but we
> > >>did not receive any ... our AS number is 8560.
> > >>
> > >>We put in 5 prefixes in, but no more-specifics (we have one
> > >>more-specific announced). We put in two upstream
> providers and 'forgot'
> > >>one upstream to provoke upstream alarms.
> > >>
> > >>For some weird reason, we don't get any alarms. I
> crosschecked with
> > >>the
> > >>RIS query and when I compare it with our config, I should
> get a bunch of
> > >>alarms.
> > >
> > >The myASn send alarm notification in case something unexpected
> > >happen. In
> > >your case you have configured:
> > >the origin alarms:
> > >@ ORIGIN 217.160/16 300 3 14400
> > >@ ORIGIN 195.20.224/19 300 3 14400
> > >@ ORIGIN 212.227/16 300 3 14400
> > >@ ORIGIN 82.165/16 300 3 14400
> > >
> > >and the providers:
> > >@ PROVIDERS 3356 300 3 14400
> > >@ PROVIDERS 1239 300 3 14400
> > >
> > >you will only get alarm messages in case something unexpected
> > >happens. For
> > >example
> > >if AS2323 announces prefix 217.160/16 you will then get
> alarm messages. Or
> > >if someone announces any prefix and the ASPATH is NOT "x x
> x 3356 8569 x x
> > >x" OR
> > >"x x x 1239 8569 x x x¨ then you will get alarm messages.
> >
> > so with this setting we should get alarms: as I wrote I left out a
> > more
> > specific in the configuration and I left out another
> upstream, which is
> > AS12312.
> > If I query RIS directly, I e.g. see the announcement from
> AS12132 as
> > well as various announcements from other RIS peers who give
> you a full
> > feed and announce our route as their peer route.
> >
>
> myASN is using only data from RRC03. That's kind of
> misleading. You can
> get all BGP announcement from RIS queries but you can not see
> those in
> myASN. New version will run over all RRC data.
>
> It looks there is a bug in ASPATH matching. This would be
> fixed in the new version of myASN.
>
> > Can you please have a look at this issue ?
> >
> > We would be happy to integrate MyASN into our monitoring since it
> > gives
> > us a smart view on how the world's routers is see us.
>
> It's great to hear that! I suggest you to wait the new
> version will be
> online. We are planning to announce the new version late Jan.
>
> Kind regards,
>
> Arife
>
> > Thanks !
> >
> > Regards,
> > Andreas
> > --
> > Andreas Laudwein p: +49 721 91374 391
> > Network Operations f: +49 721 91374 212
> > Schlund+Partner AG http://www.schlund.net
> > --
> > "The shortest distance between two points is usually under repair"
> > -Anonymous
>
>
