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. snmp v3

snmp v3

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 23.6k 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.
  • M
    M
    MarcusH
    wrote on last edited by
    #1

    Hi,

    Any known issues with connecting to snmp v3 agents?
    Have odd issue where some nodes work and some don't with the exact same auth configuration.

    The node that netxms can't connect to agent with v3 is verified that the agent is running and v3 auth information works in other snmp explorer software.

    The node can connect with v2c if enabled, just v3 having issues.

    Tried debug logs but since it is the server very hard with spammed debug log, set snmp.discovery to level 6 and it shows SnmpCheckV3CommSettings trying then fail.

    When i do full config poll on a node that V3 works on there is no SnmpCheckV3CommSettings in logs it just connects and polls.

    The nodes that V3 work on and the nodes that does not have exact same config no question since the snmp is set with nxshell script on all nodes in the container.

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

      Yes, debug log on level 6 would be beneficial. Couple of options
       - use some netxms agent in proxy mode and take the log of it

      • use some test installation of netxms server that has just a couple of SNMP nodes (it's also worth to unmanage the node that represents server itself to minimize logged stuff)
      1 Reply Last reply
      0
      • M
        M
        MarcusH
        wrote on last edited by
        #3

        Tried clean test server install with just the node that do not work and it works on test server.
        Tried renaming and then recreate the node that does not work and now snmp v3 works on the new node on production server.
        Odd issue that only snmp v3 is not working on some old nodes.

        I will recreate all nodes to be safe.

        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