Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. No SNMP Trap processing after upgrading from 4.4.4 to 5.1.2

No SNMP Trap processing after upgrading from 4.4.4 to 5.1.2

Scheduled Pinned Locked Moved Support
3 Posts 3 Posters 33.1k Views
  • 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.
  • G
    G
    GTM
    wrote on last edited by
    #1

    Hello! It's been a long time since I've posted here. Regardless....I just upgraded from 4.4.4 to 5.1.2 and now SNMP traps are no longer processed.

    I was running 4.4.4 in a Debian container on Proxmox. I created a new Debian container and did a fresh install of 5.1.2. I upgraded the database via the nxdbmgr and updated my scripts with the new OID syntax. My SNMP polling of devices is working correctly, however, NetXMS is not processing the SNMP traps. 

    1. I verified via packet capture that the server is receiving the traps
    2. netstat -an shows that NetXMS is listening on port 162
    3. The firewall was temporarily set to "allow all"
    4. I verified that my server configuration variables had not changed
    5. The SNMP trap monitor in the client doesn't display any of the incoming traps, and the event monitor doesn't show anything either.

    I haven't tried any other 5.x versions as I was wanting to update to the latest and greatest.

    Any ideas?

    1 Reply Last reply
    0
    • F
      F
      Filipp Sudanov
      wrote on last edited by
      #2

      Hi,

      I did a quick check - looks that it works in 5.1.1 and does not in 5.1.2. Will check with developers.

      1 Reply Last reply
      0
      • V
        V
        Victor Kirhenshtein
        wrote on last edited by
        #3

        Hi,

        there was a bug introduced in 5.1.2. We fixed it in patch release 5.1.3 which was just published.

        Best regards,
        Victor

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups