Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-11029

Discovery SNMP pattern retrieves "location" parameter as HEX instead of ASCII

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • None
    • Discovery 3.1.0
    • Assets Discovery
    • None

      Issue Summary

      Using Insight Discovery, when scanning SNMP network devices using our default patterns, SNMP_Deviceinfo_Default.pat, the “location” parameter is not being returned as HEX instead of ASCII

      Steps to Reproduce

      1. Set up an SNMP Device on the network
      2. Ensure through a SNMP tester tool or by running an SNMP walk, with numeric OIDs 1.3.6.1.2.1.1.6.0 that "Location" value is correctly set on the device.
      3. On the Discovery Tool, "Credentials" tab, set up "SNMP_V3" type as well as user and password.
      4. Run the Discovery Scan

      Expected Results

      Location value from the device should return correctly if found.
      In the following example, Location value should return: BE_304

      Actual Results

      SNMP_Deviceinfo_Default.pat returns the value in HEX (42455F333034) instead of ASCII (BE_304)

      The below can be seen in the discovery-xxxxx.log file:

      17.01.2022 14:14:55 : Using pattern: SNMP_Deviceinfo_Default.pat (v3.3.0)
17.01.2022 14:14:55 : Sending message request...
17.01.2022 14:14:55 : Processing 5 SNMP results.
17.01.2022 14:14:56 : Command: 
    1.3.6.1.2.1.1.3.0;1.3.6.1.2.1.1.4.0;1.3.6.1.2.1.1.5.0;1.3.6.1.2.1.1.6.0;1.3.6.1.4.1.2021.4.5.0
    
17.01.2022 14:14:56 : Result: 

1.3.6.1.2.1.1.3.0: 76d 3h 48m
1.3.6.1.2.1.1.4.0: +111111111, username@email.com
1.3.6.1.2.1.1.5.0: hostname
1.3.6.1.2.1.1.6.0: 42455F333034

      Workaround

      Until the current pattern is adjusted to fix that, you can converting Hex value to Ascii

        1. SNMP Tester.png
          SNMP Tester.png
          387 kB

            [JSDSERVER-11029] Discovery SNMP pattern retrieves "location" parameter as HEX instead of ASCII

            Vitek Urban added a comment -

            Hi,

            the issue sometimes occurs on all possible OIDs called by any SNMP script. I hope you are not going to fix it only on SNMP script bundled with Discovery. We need a system fix with valid return values for every OID (both in out-of-the-box script and custom). Thanks a lot.

            Br,

            Vitek

            Vitek Urban added a comment - Hi, the issue sometimes occurs on all possible OIDs called by any SNMP script. I hope you are not going to fix it only on SNMP script bundled with Discovery. We need a system fix with valid return values for every OID (both in out-of-the-box script and custom). Thanks a lot. Br, Vitek

              b4eb96ad59e5 Kostiantyn Onyshchenko (Inactive)
              9f03f4114502 Pablo Bartolome
              Affected customers:
              2 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: