BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
3/22/2024
Smart Assurance - SMARTS
No affected releases provided.
No fixed releases provided.
Some devices discovered by Smarts AM using SNMP v3 are added to the pending list with status UNDISCOVERED, but others are discovered correctly The following message is in the log file for Smarts AM:ADTM-N-AD_LOG-09-Apr-2009 13:03:36 CEST, at 'SeedResponse t@60', while discovering '10.244.247.1', add to pending, UNDISCOVERED 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
The above symptoms are related to the EngineID defined on the devices and is not caused by a Smarts issue.
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.