Discovery: SNMP scan fails with " Unable to get the deviceinfo: TIMEOUT " after 30 minutes. The Discovery log has " credential failed: SNMP++: SNMP request timed out ".

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    BMC Discovery


    COMPONENT:

    BMC Discovery 11.2


    APPLIES TO:

    BMC Discovery



    PROBLEM:

    A scan fails with " Unable to get the deviceinfo: TIMEOUT " when using SNMP credentials, and the correct credential is at the bottom of the list.

    The tw_svc_discovery.log has the following information:

    139909580310272: 2017-10-20 13:41:07,720: discovery.servants: INFO: Main_i::getDevice() for 1.1.1.1
    ...
    139909580310272: 2017-10-20 13:41:07,723: discovery.heuristics.lastsnmp: DEBUG: Last SNMP Heuristic: 1.1.1.1: Last SNMP not available (no last_access_method)
    ...
    139909580310272: 2017-10-20 13:41:15,431: api.audit: DEBUG: 1.1.1.1: nmap.run(): Complete status = SUCCESS
    ...
    139909580310272: 2017-10-20 13:41:15,435: discovery.device: INFO: 1.1.1.1: Try snmp and wbem heuristic
    139909580310272: 2017-10-20 13:41:15,435: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Try SNMP Heuristic
    139909580310272: 2017-10-20 13:41:15,493: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: 14 credential(s) to try
    ...
    139909580310272: 2017-10-20 13:41:15,495: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Attempting identification using c9bb1135169ee73985f40a4a78461e90
    139909580310272: 2017-10-20 13:41:21,510: discovery.heuristics.snmp: DEBUG: identifyDevice: 1.1.1.1: credential failed: SNMP++: SNMP request timed out
    ...
    139909580310272: 2017-10-20 13:41:21,510: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Attempting identification using d3778c33ee6f65d220340a4a50982fdb
    139909580310272: 2017-10-20 13:41:21,584: discovery.heuristics.snmp: DEBUG: identifyDevice: 1.1.1.1: credential failed: SNMPv3: USM: Unknown SecurityName
    ...
    139909580310272: 2017-10-20 13:41:21,584: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Attempting identification using c5a2aa334d1bba3146dc0a4a5098442a
    139909580310272: 2017-10-20 13:41:27,598: discovery.heuristics.snmp: DEBUG: identifyDevice: 1.1.1.1: credential failed: SNMP++: SNMP request timed out
    ...
    139909580310272: 2017-10-20 13:41:27,599: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Attempting identification using f02fcc3373937cff86860a4a5098081e
    139909580310272: 2017-10-20 13:41:33,612: discovery.heuristics.snmp: DEBUG: identifyDevice: 1.1.1.1: credential failed: SNMP++: SNMP request timed out
    ...
    139909580310272: 2017-10-20 13:41:33,613: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Attempting identification using f02fcc3373944dc3039c0a4a5098081e
    139909580310272: 2017-10-20 13:41:39,627: discovery.heuristics.snmp: DEBUG: identifyDevice: 1.1.1.1: credential failed: SNMP++: SNMP request timed out
    ...
    139909580310272: 2017-10-20 13:41:39,627: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Attempting identification using 18e5a8317c05b4546c787f0000015ece
    139909580310272: 2017-10-20 13:41:45,640: discovery.heuristics.snmp: DEBUG: identifyDevice: 1.1.1.1: credential failed: SNMP++: SNMP request timed out
    ...
    139909580310272: 2017-10-20 13:41:45,641: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Attempting identification using 6c471132a38c008c0e8c7f00000155fe
    139909580310272: 2017-10-20 13:41:51,654: discovery.heuristics.snmp: DEBUG: identifyDevice: 1.1.1.1: credential failed: SNMP++: SNMP request timed out
    ...
    139909580310272: 2017-10-20 13:41:51,655: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Attempting identification using 6c471132a38d12e1c2047f00000155fe
    139909580310272: 2017-10-20 13:41:57,670: discovery.heuristics.snmp: DEBUG: identifyDevice: 1.1.1.1: credential failed: SNMP++: SNMP request timed out
    ...
    139909580310272: 2017-10-20 13:41:57,670: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Attempting identification using 77bc6932baefd95d6c027f0000010dcd
    139909580310272: 2017-10-20 13:42:03,685: discovery.heuristics.snmp: DEBUG: identifyDevice: 1.1.1.1: credential failed: SNMP++: SNMP request timed out
    ...
    139909580310272: 2017-10-20 13:42:03,685: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Attempting identification using 77bc6932baeff38310827f0000010dcd
    139909580310272: 2017-10-20 13:42:09,699: discovery.heuristics.snmp: DEBUG: identifyDevice: 1.1.1.1: credential failed: SNMP++: SNMP request timed out
    ...
    139909580310272: 2017-10-20 13:42:09,699: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Attempting identification using 77bc6932bb0643b31ad27f0000010dcd
    139909580310272: 2017-10-20 13:42:15,714: discovery.heuristics.snmp: DEBUG: identifyDevice: 1.1.1.1: credential failed: SNMP++: SNMP request timed out
    ...
    139909580310272: 2017-10-20 13:42:15,714: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Attempting identification using 434ab1334868023e65800a4a50981a39
    139909580310272: 2017-10-20 13:42:21,729: discovery.heuristics.snmp: DEBUG: identifyDevice: 1.1.1.1: credential failed: SNMP++: SNMP request timed out
    ...
    139909580310272: 2017-10-20 13:42:21,729: discovery.heuristics.snmp: DEBUG: SNMP Heuristic: 1.1.1.1: Attempting identification using b6c7a4337c564c71870a0a4a50983b4d

    In this case the following was observed:
    1. 14 SNMP credentials were a match for the IP
    2. The 13th SNMP credential did not timeout
    3. The 14th SNMP credential (not listed in the discovery log) is the correct one for the device and it was at the bottom of the credential list
    4. The error does not appear when the correct credential is at the top of the list
     


    CAUSE:

    The 13th credential (with uuid of b6c7a4337c564c71870a0a4a50983b4d) did not timeout.


    SOLUTION:

    To identify the 13th credential, the following was run:

    http://scanner/ui/Credential?uuid=b6c7a4337c564c71870a0a4a50983b4d
    -> replace scanner with the actual scanner hostname or IP address

    Looking at the credential, it was found that the timeout was set to 9000 seconds, which exceeds the default reasoning timeout of 30 minutes. 

    When the timeout on this credential was lowered to the default value, the scan succeeded.


    Article Number:

    000143976


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles