3 Replies Latest reply on Apr 1, 2014 7:56 AM by patrick

    SNMP Traps

    telegrideng New Member

      Hi -

       

      I am testing an Adtran Atlas 890 for SNMP integration into a local NMS.  I am writing a test procedure and trying to generate some traps.  I am referencing the MIBS and using the telnet utility to make system changes that should generate SNMP traps.  However, I don't get any traps other than a cold start when the device is rebooted.  For example, according to the MIBs switching a module to online or offline will generate a trap but I never see one.  Is there something I am doing wrong?  All the thresholds are set to MINOR.  Is that correct?

       

      I can't find any help in the user manual and I am hoping someone here can help.

       

      Thanks!

      Beth

        • Re: SNMP Traps
          patrick Employee

          Hello Beth, and thank you for using the ADTRAN Support Community Forums.

           

          The thresholds (under SYSTEM CONFIG and EVENT LOGGING) are for the ATLAS' EVENT LOG (under SYSTEM STATUS). Those do not effect the SNMP traps.

          The module status (online or offline) can be found through SNMP polling, but there is not a trap sent when that status changes. Alarm conditions typically cause a trap to be sent.

           

          The "att1.mib" shows traps for a RED alarm condition (as well as other conditions):

           

          adATLAST1RedAlarmActive  TRAP-TYPE

                  ENTERPRISE     adATLASmg

                  VARIABLES {

                          ifIndex,

                          adATLASUnitSlotAddress,

                          adATLASUnitPortAddress,

                          adATLASModuleInfoFPStatus,

                          adATLASUnitFPStatus,

                          dsx1LineStatus

           

                  }

                  DESCRIPTION

                          "This trap indicates a red alarm is active."

                  --#TYPE       "Error - RED Alarm"

                  --#SUMMARY    "ATLAS 15400904: Red alarm is active for "

                  --#SUMMARY    "Line %d, Slot %d, Port %d, Module Status %d, "

                  --#SUMMARY    "Box Status %d, Line Status %d"

                  --#ARGUMENTS  {0,1,2,3,4,5}

                  --#SEVERITY   MAJOR

                  --#GENERIC    6

                  --#CATEGORY   "Error Events"

                  --#SOURCE_ID  "A"

                  --#TIMEINDEX  0

                  ::= 15400904

           

          adATLAST1RedAlarmInActive  TRAP-TYPE

                  ENTERPRISE     adATLASmg

                  VARIABLES {

                          ifIndex,

                          adATLASUnitSlotAddress,

                          adATLASUnitPortAddress,

                          adATLASModuleInfoFPStatus,

                          adATLASUnitFPStatus,

                          dsx1LineStatus

           

                  }

                  DESCRIPTION

                          "This trap indicates a red alarm is inactive."

                  --#TYPE       "Error - RED Alarm"

                  --#SUMMARY    "ATLAS 15400905: Red alarm is inactive for "

                  --#SUMMARY    "Line %d, Slot %d, Port %d, Module Status %d, "

                  --#SUMMARY    "Box Status %d, Line Status %d"

                  --#ARGUMENTS  {0,1,2,3,4,5}

                  --#SEVERITY   MAJOR

                  --#GENERIC    6

                  --#CATEGORY   "Error Events"

                  --#SOURCE_ID  "A"

                  --#TIMEINDEX  0

                  ::= 15400905

           

          This only sends a trap if the T1 port is configured in either the DIAL PLAN or in the DEDICATED MAP. You can put the T1 port into alarm if there is a T1 circuit connected to it, and you change the FORMAT under the module configuration. (If there is no alarm when it is running ESF, you can change the FORMAT to D4 and the T1 port should go into RED alarm.) If you do not have a T1 circuit, you can use a T1 loopback plug on one port configured in the DIAL PLAN (which should not have an alarm when in loopback), and then unplug the loopback to cause the port to go into LOS/RED.

          You can also use a T1 cross-over cable to connect 2 T1/PRI ports together, and either map the two ports together in the DEDICATED MAP or configure them in the DIAL PLAN. You can then cause an alarm by changing the FORMAT on one of the ports.

           

          Hope this helps,

          Patrick