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. Specify community in CreateSNMPTransport function

Specify community in CreateSNMPTransport function

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 14.0k 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
    mmarin11
    wrote on last edited by
    #1

    Dear NetXMS community.

    I'm trying to integrate Ekinops transport gear into NetXMS and this equipment requires the use of multiple snmp communities in order to get the data for specific slots. For example if we are trying to get interface data of card in slot #3 we have to append the slot number to the snmp community, if the snmp is public, we need to set the community as public3. Is there a way to specify the community in the CreateSNMPTransport NSXL function as an argument in order to use multiple snmp communities for the same node?

    Thanks

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

      Currently CreateSNMP transport does not support this. I've created an issue, also there's no particular plan when this could be implemented https://track.radensolutions.com/issue/NX-2062

      Meanwhile you can try creating multiple nodes with the same IP address, setting checkbox "Communication through external gateway" (this is needed so that system ignores same IP address for these nodes). Each node would have specific community string set. To consolidate all monitored values onto one node you can configure "push" DCIs on that one node and use PushDCIData() from transformation script in DCIs of the additional nodes.

      If your device returns list of interfaces for all of these community strings, then interfaces with same IP address would be created. This should not cause much troubles, but you can handle this in Hook::CreateInterface to avoid interface creation for the additional nodes.

      1 Reply Last reply
      0
      • M
        M
        mmarin11
        wrote on last edited by
        #3

        Thanks Filipp!

        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