Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

Radix IoT Website Mango 3 Documentation Website Mango 4 Documentation Website

Navigation

    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Popular

    Handling Unknown SNMP Traps

    User help
    2
    5
    3725
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      narenblr last edited by

      Is there a provision to handle unknown SNMP Traps.

      We have to configure all the known SNMP OID's in Mango to receive traps. What I have observed is that at times we receive trap OID's which are not configured in Mango. These traps are not logged any where and they are discarded. It will be good if the unknown traps received are alerted/captured. This will help us to identify as well as configure them immediately in mango. Something like a space holder for unknown traps.

      Regards,
      Naren

      1 Reply Last reply Reply Quote 0
      • M
        mlohbihler last edited by

        Check the log files. There should be a warning in there that starts with "Trap not handled:".

        Best regards,
        Matthew

        1 Reply Last reply Reply Quote 0
        • N
          narenblr last edited by

          Thanks.
          I can see the unknown traps in the logs
          "/mango/apache-tomcat-6.0.20/logs/catalina.out:WARN 2009-10-08 09:31:24,070 (com.serotonin.mango.rt.dataSource.snmp.SnmpDataSourceRT.receivedTrap:236) - Trap not handled: 1.3.1.4.1.2854.2.2 = 200
          /mango/apache-tomcat-6.0.20/logs/mango.log:WARN 2009-10-08 09:31:24,070 (com.serotonin.mango.rt.dataSource.snmp.SnmpDataSourceRT.receivedTrap:236) - Trap not handled: 1.3.1.4.1.2854.2.2 = 200

          This justs makes me to think how can we proactively identify the unnown traps?

          Should there be a log file data source to monitor specific strings?

          Regards,
          Naren

          1 Reply Last reply Reply Quote 0
          • M
            mlohbihler last edited by

            A system event would probably be simpler.

            Best regards,
            Matthew

            1 Reply Last reply Reply Quote 0
            • First post
              Last post