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. MIB Browser only returning "Hex-STRING" (since 2.1-M2?)

MIB Browser only returning "Hex-STRING" (since 2.1-M2?)

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

    Hi,

    I did not need to use the MIB Browser in a while as most our templates just chugging along nicely.
    The other day I had a new device type to add and when I tried to use the MIB Browser the result was that every single OID in a full SNMP walk returned "Hex-STRING".
    I then went and tried walking other devices which have working templates and SNMP DCIs applied to them: same result.

    From what I read, Hex-STRING is what NetXMS shows when there are non-printable characters in the result.
    Considering I used the MIB Browser extensively in the past to create templates and now none of the dozen devices I tested are returning anything but Hex-STRING - in the MIB Browser only. DCIs happily return correct data.

    I would have last used the MIB Browser while running M2.1-M1, so I am guessing this to be related to 2.1-M2.
    This happens in the console as well as the web interface.
    Has anyone else seen the same issue?

    Cheers,
    Tursiops


    Hex-STRING.jpg

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

      Hi,

      yes, that's a bug in 2.1-M2. Should be fixed in 2.1-M3.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • T
        T
        Tursiops
        wrote on last edited by
        #3

        Hi Victor,

        Just installed 2.1-M3. While the MIB Browser no longer shows Hex-STRING in M3, it now shows INTEGER, COUNTER, etc., i.e. the type, but not but not the actual values.

        It looks like there's a column (header) missing. It shows the OID, then the "human readable" version of the OID (which shows under the header "Type") followed by the actual type in the column "Value". The value itself is not in the list at all.

        Cheers,
        Tursiops

        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