cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1126
Views
0
Helpful
2
Replies

CSPC not discovering IP addresses

BDDavis
Level 1
Level 1

Using the Cisco Common Service Platform Collector 2.7 we are currently  receiving a successful connection to IP addresses only when we do SNMP scans for them individually. When we scan for a range of addresses it may only show one or few are discovered and the remaining failed (regardless of how large or small) , even when it had previously showed a connection during the individual search. We have been scanning using both SNMPv3 and SNMPv2 and have gotten the same results. Some of the missing devices are discoverable using Nmap but those results present less information than the successful SNMP scans.  In addition, no searches have returned serial numbers for their device. 

 

The credentials for SNMPv3, and other protocols we've added, have been verified as correct. 

Notice IP 10.13.0.20 in the below captures. 

2 Replies 2

BDDavis
Level 1
Level 1

What is happening is that the SNMPv3 EngineID is being automatically duplicated and preventing the management of devices during a large discovery, but this is not happening when only a single device is discovered. The current workaround is to manually set the EngineID or update the IOS version to the appropriate level. Currently searching for a better solution. 

Hello There,

When the CSPC is attempting to collect and discover these devices using SNMP v3, the devices will send its own msgAuthoritativeEngineID, msgAuthoritativeEngineBoots, and msgAuthoritativeEngineTime values to the agent to keep track of and use for secure purposes during snmp collection.  For each device, a unique EngineID must be returned back to the CSPC or discovery may fail.  This is also why we were able to see that running just a discovery or collection for a single device was working without any issues.

I was able to find a pre-existing bug for this version of IOS which had an issue during the auto-generation of the EngineIDs (CSCts87275). One workaround could be to manually set new unique EngineIDs on the devices which you have also mentioned.

Thank you,

Jarrett

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: