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. 32 bit INT OID issue

32 bit INT OID issue

Scheduled Pinned Locked Moved Support
5 Posts 3 Posters 31.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.
  • C
    C
    cserzs
    wrote on last edited by
    #1

    Hi,

    I have installed the v2.0-RC2 NetXMS system and I tried to integrate an SNMP device what uses 32 bit INT OIDs. I carried out the compilation process of corresponding MIB  files successfully but in DCI configuration/ Select MIB Object window when I tried to run an SNMP Walk process I found that the 32 bit INT OID components are not displayed properly (with negative sign). Please see the attached screenshot of this MIB Walk Results Window.


    netxms.JPG

    1 Reply Last reply
    0
    • T
      T
      tomaskir
      wrote on last edited by
      #2
      1. Use 2.0.3, RC2 is quite old.
      2. Use the Java Management console, not the legacy one.

      Let us know if the problem persists after those changes.

      1 Reply Last reply
      0
      • C
        C
        cserzs
        wrote on last edited by
        #3

        Hi,

        Thank you for your feedback.
        I have upgraded my NetXMS system to v2.0.3 but despite this the 32 bit INT OID issue still inadequate (remain the negative sign).

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

          Hi,

          it's actually a bug in libnxsnmp. I've fixed it in development branch. If you are building from source, you can fix it by changing file src/snmp/libnxsnmp/main.cpp line 34:

          from:
                size_t numChars = _sntprintf(&buffer[bufPos], bufferSize - bufPos, _T(".%d"), value[i]);

          to:
                size_t numChars = _sntprintf(&buffer[bufPos], bufferSize - bufPos, _T(".%u"), value[i]);

          Best regards,
          Victor

          1 Reply Last reply
          0
          • C
            C
            cserzs
            wrote on last edited by
            #5

            Hello Victor,

            Thank you very much for your support.
            I will wait for the official fixed version.

            BR, Zsolt

            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