Discovery: An SNMP v3 scan fails for some network devices, but the endpoint can be successfully discovered after restarting tideway services (EngineID)

Version 2
    Share This:

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


    BMC Discovery


    BMC Atrium Discovery and Dependency Mapping


    BMC Atrium Discovery and Dependency Mapping


    An SNMP v3 scan of a supported network device fails with “Skipped (Device is an unsupported device)”.

    The customer is able to do an snmpwalk from the discovery command line successfully.

    Other SNMP devices were discovered by the appliance using the same credentials.

    A credential test failed with "SNMP request timed out". Increasing the timeout to 100s did not help.

    After a restart of the tideway services, the device was discovered successfully


    This is a known defect: DRUD1-14790. Now known as: DRUD1-25505


    This is a known defect: DRUD1-14790

    Analysis indicates that the problem is related to when some network devices are operating in a master/slave mode where they both present the same EngineID, which is supposed to be unique. Discovery scans the first one successfully, but then the second one fails until the cache is flushed (by the service restart) - at which point a rescan of the first would fail, and so on. 

    UPDATE 2019:  DRUD1-14790 is closed and is replaced with a new jira DRUD1-25505

    DRUD1-25505 is scheduled (but not promised) for the next major release after 11.3 and 11.4.  11.4 is already releases and is known as Helix Discovery.




    Article Number:


    Article Type:

    Solutions to a Product Problem

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