DX NetOps

  • 1.  Event message codes

    Posted Mar 15, 2017 02:23 PM

    So I have what very well may be a ridiculous question, but I'm going to ask it anyway.  When looking at an event message in the Event Configuration tool, how do we know which values are which?  For example, here's the message for event 0x00220007:

    A(n) {t} device, named {m}, has received over 15 Communication Link Up and Down Trap pairs in the last 5 minutes. An alarm will be created on the device.

    ifIndex = {I 1}
    ifDescr = {S 3}
    ifType = {S 4}
    ifAdminStatus = {T ifAdminStatus 5}
    ifOperStatus = {T ifOperStatus 6}

     

    In the Spectrum documentation I have found references to the {t} and {m} variables, among others.  How do we know the attribute associated with the string variable numbers?  For example, the {S 3} variable for ifDescr rarely provides any data in an event.  I'd rather change that to the ifAlias value so the event contains the interface's configured description, but how do I know which number to substitute there?  Or is that even possible?



  • 2.  Re: Event message codes
    Best Answer

    Posted Mar 15, 2017 02:49 PM

    Josh,

    The number is referred to an an Event Variable. They are most commonly populated in one of three ways:

     

    1. Internally in the code. When Spectrum creates an event from an inference handler, the developer can create an event and populate the Event Variable with data.

     

    2. Using an Event Procedure, the user can tell Spectrum to take the value of a model attribute and save it to an Event Variable. Or they can take an existing Event Variable, apply a regular expression to extract a piece of information out of the existing Event Variable and save it to a new Event Variable.

     

    3. From a trap varbind. In the AlertMap file, the user can tell Spectrum to save the value of a varbind to an Event Variable.

     

    In any case, after the value is saved to an Event Variable, the Event Format files tell Spectrum how to display the saved value. For example, if a value was saved to Event Variable 5, depending on the data type of the value, it can be displayed as follows: (See  the "Variable Descriptions and Syntax" section of the documentation for a complete list)

    For text - {S 5}

    For integer - {I 5}

    For an octet string - {O 5}

    For an enumerated table - {T (table name) 5}

     

    For your question about ifDescr, I believe the 0x00220007 event is based on a trap and ifDescr is sent as a varbind with the trap.

     

    Joe