On Tue, 28 Feb 2006, David T. Perkins wrote:

HI Peder Chr. Norgaard,

I believe we pretty are much in agreement that what was done
in many of the access routines and event reporing routines
in NET-SNMP can and should be updated.

The note was to help other readers with understanding that
the change was not to add any new capabilities to NET-SNMP,
but to change the mechanism used to report link up and
link down events.

Note, on terminology, I really wish there was a good
reference, since I believe that in telco speak there
are two types of alarms - one for "standing conditions"
and one for (I forgot the actual term) "instance events"
(for example, a failed login attempt). If you have
a good reference, please send me a citation.

Well, yes, I do have a reference for terminology - but you probably know about that yourself. It is X.733 and X.734 (also known as ISO/IEC 10164-4 and 10164-5). This is where the concepts of events and alarms are defined; the short story is that an "alarm" in this context is a specialized "event" which has to be reset by another special "event".

A purist will of course point out that the ifUp/ifDown pair is not a true alarm in this context, and I will have to agree; I used the term only because the pair shares the high-level functional goal with a real X.733 alarm: to mirror a binary status of a node to a management station.

Regards,
/david t. perkins


best regards

--
Peder Chr. Nørgaard             Senior System Developer, M. Sc.
Ericsson Denmark A/S, Telebit Division
Skanderborgvej 232              tel: +45 30 91 84 31
DK-8260 Viby J, Denmark         fax: +45 89 38 51 01
        e-mail: [EMAIL PROTECTED]
(old e-mail 2000-2003: [EMAIL PROTECTED])
         (old e-mail 1992-2000: [EMAIL PROTECTED])
----------------------------------------------------------------
This communication is confidential and intended solely for the
addressee(s). Any unauthorized review, use, disclosure or distribution
is prohibited. If you believe this message has been sent to you in
error, please notify the sender by replying to this transmission and
delete the message without disclosing it. Thank you.

E-mail including attachments is susceptible to data corruption,
interruption, unauthorized amendment, tampering and viruses, and we
only send and receive e-mails on the basis that we are not liable for
any such corruption, interception, amendment, tampering or viruses or
any consequences thereof.

Reply via email to