ISSUE: Spectrum is unable to AutoDiscover SNMPv2 devices when SNMPv3 community strings are first in the list in the SNMP Information field of the Discovery Profile:
During the modeling process, the following is seen in the Modeling Status panel in the Discovery Modeling tab:
** Failed creation for device at IP 220.127.116.11 **
If AutoDiscovery debug is enabled, the following is seen in the discovery debug file where Spectrum is trying to discover an SNMPv2 device using an SNMPv3 profile even though the SNMPv2 device is not configured with SNMPv3.
11:15:12 IP Discovery 18.104.22.168: mtype identification failed at community name #v3/P:authpass:privpass/UserID and SNMP port 161 with error: 1
CAUSE: The community strings listed in the SNMP Information field of the Discovery Configuration are tested in order of appearance from top to bottom. So in thsi case, Spectrum will attempt to contact the device using the SNMPv3 profile. When this occurs, the device will respond with an authentication failure. However, Spectrum is misinterpreting the authentication failure from the device as a valid response to the SNMPv3 request and attempts to model the device using the SNMPv3 profile.
RESOLUTION: As a work-around, the order of the community strings listed in the SNMP Information field of the Discovery Configuration can be changed.
There is no fix for this issue in Spectrum 9.4.3. Please use the work-around.
This issue is fixed in Spectrum 10 by the 10.00.00.PTF_10.0.012a patch. Please contact CA Spectrum Support for a copy of this patch.
This issue is also resolved in Spectrum 10.01.00.00.
This issue is scheduled to be addressed in Spectrum 09.04.04.00.