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

Discovery Tool - SNMP scan fails if SNMP credentials are dedicated to the Scan Setting

XMLWordPrintable

      Issue Summary

      This is reproducible on Data Center: (yes) 

      Using a dedicated Scan Setting, to indicate a range of IP address of Network devices, such as switches - Discovery will not attempt the dedicated Credentials, and the result will be an Unknown / Basic Host with a Rejected Status

      Steps to Reproduce

      1. Configure the Discovery Tool with 2 Scan settings: Scan setting 00001 for Hosts (e.g. windows or linux), Scan setting 00002 for SNMP Network devices (e.g. Switches)
      2. Save credentials for the Hosts and make the Credentials set to Scan Setting 00001
      3. Save credentials for  SNMP Devices (SNMP2) and make the Credentials set to Scan Setting 00002
      4. Execute a scan (any type of scan - single IP, Scan Settings or complete)

      Expected Results

      The SNMP Devices are logged into using the saved SNMP Credentials, and included in the Scan Results.

      Actual Results

      No Credentials available, and SNMP devices show as Unknown Hosts (imported with Rejected Status)

      ...

      Workaround

      Set the SNMP credentials to ALL Scan Settings

          Form Name

            [JSDSERVER-12003] Discovery Tool - SNMP scan fails if SNMP credentials are dedicated to the Scan Setting

            Rasmus Breidahl added a comment - - edited

            Hi, I got this info in my snmp logs
            Hostname Unknown, but its getting the "Device information: Nexus-2" name of the device
            Why is Hostname Unknown, when this is listed

            Change the SNMP account for all scan target and still get this

            6/26/2023 1:01:42 PM : Start Scan Thread: 00011 IP: x.x.x.x TaskID: 0000000034
            6/26/2023 1:01:42 PM : Start Scan: x.x.x.x
            6/26/2023 1:01:42 PM : Ping x.x.x.x --> Success ResponseTime=0ms TTL=255
            6/26/2023 1:01:42 PM : No working credential for x.x.x.x
            6/26/2023 1:01:42 PM : Try getting basic information for x.x.x.x
            6/26/2023 1:01:49 PM : Getting Hostname: Unknown Host
            6/26/2023 1:01:49 PM : Finish scan for x.x.x.x
            6/26/2023 1:01:49 PM : Connected to x.x.x.x with Device-Credential: xxx
            6/26/2023 1:01:49 PM : Using pattern: SNMP_Deviceinfo_Default.pat (v3.3.0)
            6/26/2023 1:01:50 PM : pattern executed in 0.8047148 seconds
            6/26/2023 1:01:50 PM : Getting Device information: Nexus-2
            6/26/2023 1:01:50 PM : Using pattern: SNMP_Deviceinfo_Network.pat (v3.1.0)
            6/26/2023 1:01:54 PM : pattern executed in 3.7575306 seconds
            6/26/2023 1:01:54 PM : Connected to x.x.x.x with Device-Credential: xxx
            6/26/2023 1:01:54 PM : Finished Scan Thread: 00011 IP: x.x.x.x TaskID: 0000000034

            Rasmus Breidahl added a comment - - edited Hi, I got this info in my snmp logs Hostname Unknown, but its getting the "Device information: Nexus-2" name of the device Why is Hostname Unknown, when this is listed Change the SNMP account for all scan target and still get this 6/26/2023 1:01:42 PM : Start Scan Thread: 00011 IP: x.x.x.x TaskID: 0000000034 6/26/2023 1:01:42 PM : Start Scan: x.x.x.x 6/26/2023 1:01:42 PM : Ping x.x.x.x --> Success ResponseTime=0ms TTL=255 6/26/2023 1:01:42 PM : No working credential for x.x.x.x 6/26/2023 1:01:42 PM : Try getting basic information for x.x.x.x 6/26/2023 1:01:49 PM : Getting Hostname: Unknown Host 6/26/2023 1:01:49 PM : Finish scan for x.x.x.x 6/26/2023 1:01:49 PM : Connected to x.x.x.x with Device-Credential: xxx 6/26/2023 1:01:49 PM : Using pattern: SNMP_Deviceinfo_Default.pat (v3.3.0) 6/26/2023 1:01:50 PM : pattern executed in 0.8047148 seconds 6/26/2023 1:01:50 PM : Getting Device information: Nexus-2 6/26/2023 1:01:50 PM : Using pattern: SNMP_Deviceinfo_Network.pat (v3.1.0) 6/26/2023 1:01:54 PM : pattern executed in 3.7575306 seconds 6/26/2023 1:01:54 PM : Connected to x.x.x.x with Device-Credential: xxx 6/26/2023 1:01:54 PM : Finished Scan Thread: 00011 IP: x.x.x.x TaskID: 0000000034

              21ad8969f413 Viktor Kryvoruchko (Inactive)
              8cdc82c96fd5 Yinon Negev
              Affected customers:
              3 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: