DX NetOps

  • Private Community
 View Only

  • 1.  Is there a way to find which circumstances cause an alarm to be open?

    Posted Oct 19, 2016 01:12 PM

    We are sometimes confused why an alarm is opened in Spectrum and in most of those cases it stems from vague descriptions in the alarm (loaded by developers). I can find the alarm in the event configuration tool and I can find the cause code. Is there a way to find out what triggers that cause code without hunting and pecking through suspected MIBs?

     

    The best our SE can come up with is to manually look through all the txt files for the cause code.



  • 2.  Re: Is there a way to find which circumstances cause an alarm to be open?

    Broadcom Employee
    Posted Oct 20, 2016 09:27 AM
      |   view attached

    Hi Stuart,

      I apologize but I think I’m not quite sure exactly what you are looking for.  It sounds like you are using the Event Configuration GUI and have the “Cause Code” column showing but are wondering how that is generated?  Are you trying to correlate that alarm cause code to the trap that generated the event (that generated that alarm)?  If so, unfortunately the only way to see the oid is to search through the AlertMap files…

    If I’m misunderstanding please let me know.

    Cheers

    Jay



  • 3.  Re: Is there a way to find which circumstances cause an alarm to be open?

    Posted Oct 20, 2016 10:58 AM

    That's exactly what i mean. I have the alarm and i want to know what caused it. I got as far as the cause code in the event, but couldn't tie that to a particular trap.

     

    Searching through the AlertMap files seems to be the only way, which is unfortunate. That should be much easier.



  • 4.  Re: Is there a way to find which circumstances cause an alarm to be open?
    Best Answer

    Posted Oct 20, 2016 11:35 AM

    A couple of things that may help. When viewing the Event Configuration tool, display the Generated By and Trap Event columns. If the Generated By field is populated, then the event is generated by an Event Rule. When you select the event specified in the Generated By column and click on the Event Rules tab, you will see the details of the Event Rule that generates the event.

     

     

    The Trap Event field is populated if the event is generated from a trap. To find the AlertMap file entry that generates the trap, I use the following find command executed from the $SPECROOT/SS/CsVendor directory to quickly find the AlertMap file(s):

     

    find . -name AlertMap -exec grep 0x00010013 {} \; -print
    0.0 0x00010013 1.3.6.1.2.1.1.3(1,0)\
    ./Ctron_CAT/HubCat29xx/AlertMap
    0.0 0x00010013 1.3.6.1.2.1.1.3(1,0)\
    ./Ctron_CAT/SwCat35xx/AlertMap
    0.0 0x00010013 1.3.6.1.2.1.1.3(1,0)\
    ./Ctron_CAT/SwCat85xx/AlertMap
    0.0 0x00010013 1.3.6.1.2.1.1.3(1,0)\
    ./Ctron_CAT/SwCat45xx/AlertMap
    0.0 0x00010013 1.3.6.1.2.1.1.3(1,0)\
    ./Cisco_Router/Rtr_Cisco/AlertMap
    0.0 0x00010013 1.3.6.1.2.1.1.3(1,0)\
    ./Cisco_Router/Cisco6400_DSL/AlertMap
    0.0 0x00010013 1.3.6.1.2.1.1.3(1,0)\
    ./Cisco_Router/UBR72xxCMTS/AlertMap
    0.0 0x00010013 1.3.6.1.2.1.1.3(1,0)\
    ./Cisco_Router/Cisco_12000/AlertMap
    0.0 0x00010013 1.3.6.1.2.1.1.3(1,0)\
    ./Cisco_Router/SwCiscoIOS/AlertMap
    0.0 0x00010013 1.3.6.1.2.1.1.3(1,0)\
    ./Cisco_MC3810/Cisco_MC3810/AlertMap
    0.0 0x00010013 1.3.6.1.2.1.1.3(1,0)\
    ./CiscoPIX/CisPIXDev/AlertMap
    0.0 0x00010013 1.3.6.1.2.1.1.3(1,0)\
    ./Cisco_AS5X/AS5x00/AlertMap

     

    Joe