Few SNMPv3 device discovery are added to the pending list with status UNDISCOVERED. Packet trace entries for problem devices reference 'Engine ID Conformance'.

Products

• VMware Smart Assurance
• VMware Telco Cloud Service Assurance

Issue/Introduction

Some devices discovered by Smarts AM using SNMPv3 are added to the pending list with status UNDISCOVERED, but others are discovered correctly.

The following message is observed in Smarts' domain log:

ADTM-N-AD_LOG-09-Apr-2009 13:03:36 CEST, at 'SeedResponse t@60', while
    discovering 'XX.XXX.XXX.X', add to pending, UNDISCOVERED

Where XX.XXX.XXX.X is an IP address

Packet trace captured the following entries in the packets for all the devices which are not being discovered correctly by Smarts AM:

Context Engine ID: <ID Number>
....... = Engine ID Conformance: RFC1910 (Non - SNMPv3)
Data not conforming to RFC1910

Environment

Smarts 10.1.x / 2.X

Cause

The above symptoms are related to the EngineID defined on the devices and is not caused by a Smarts issue.

Resolution

Smarts is working as designed. To resolve this issue, ensure that the correct EngineID is defined on the devices and the devices should discover correctly.