SNMPv3 Scanning of Cisco Devices

[Frazier]

We are unable to scan Cisco devices using SNMPv3. We were previously able to successfully scan our Cisco devices using SNMPv3 about 5 months ago. Solarwinds is installed on the same server with Lansweeper. Solarwinds is able to successfully scan the same Cisco devices using SNMPv3 (same server and same IP address). When viewing the debug log, after conducting a scan of one of the Cisco devices using Batch Scanning, we don't see that Lansweeper is attempting to use SNMPv3. Please see log below, where x.x.x.x is the target scanned Cisco switch IP address:

INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGSNMP DEBUG Object OID could not be retrieved.
2019-10-21 13:30:58,683 [SCAN_x.x.x.x] INFO LOGSNMP DEBUG Scanning Ver2 for x.x.x.x with Global (SNMP Community String): failed
2019-10-21 13:30:58,683 [SCAN_x.x.x.x] INFO LOGSNMP DEBUG Scanning Ver1 for x.x.x.x with Global (SNMP Community String)
2019-10-21 13:31:43,995 [iwtg\IWTG-N-2TF9S52\1] INFO DEBUG Update DataTable - consecutive scan for table:rstevents The INSERT statement conflicted with the FOREIGN KEY constraint "FK_tblntlog_tblntlogmessage". The conflict occurred in database "lansweeperdb", table "dbo.tblNtlogMessage", column 'MessageID'.
The statement has been terminated.
at System.Data.Common.DbDataAdapter.UpdatedRowStatusErrors(RowUpdatedEventArgs rowUpdatedEvent, BatchCommandInfo[] batchCommands, Int32 commandCount)
at System.Data.Common.DbDataAdapter.UpdatedRowStatus(RowUpdatedEventArgs rowUpdatedEvent, BatchCommandInfo[] batchCommands, Int32 commandCount)
at System.Data.Common.DbDataAdapter.Update(DataRow[] dataRows, DataTableMapping tableMapping)
at System.Data.Common.DbDataAdapter.UpdateFromDataTable(DataTable dataTable, DataTableMapping tableMapping)
at System.Data.Common.DbDataAdapter.Update(DataTable dataTable)
2019-10-21 13:32:06,261 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGSNMP DEBUG Object OID could not be retrieved.
2019-10-21 13:32:06,261 [SCAN_x.x.x.x] INFO LOGSNMP DEBUG Scanning Ver1 for x.x.x.x with Global (SNMP Community String): failed
2019-10-21 13:32:06,261 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Checking existing duplicate
2019-10-21 13:32:06,276 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Starting various scans
2019-10-21 13:32:07,323 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPPORTSCANNING DEBUG No FTP
2019-10-21 13:32:07,323 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPPORTSCANNING DEBUG No SMTP
2019-10-21 13:32:08,386 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Starting SSH scan
2019-10-21 13:32:09,026 [SCAN_x.x.x.x] INFO LOGSSH DEBUG Skipping SSH scan for x.x.x.x: detected Cisco network device
2019-10-21 13:32:09,026 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Starting manufacturer scan
2019-10-21 13:32:09,042 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Starting DnsSd scan
2019-10-21 13:32:11,558 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Asset type is now Unknown
2019-10-21 13:32:11,558 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Starting UPNP scan
2019-10-21 13:32:15,058 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Asset type is now Unknown
2019-10-21 13:32:15,058 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Starting SSDP scan
2019-10-21 13:32:15,058 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Asset type is now Unknown
2019-10-21 13:32:15,058 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Starting hardware scan
2019-10-21 13:32:20,604 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Asset type is now Unknown
2019-10-21 13:32:20,604 [SCAN_x.x.x.x] INFO IP__x.x.x.x x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Starting final checks
2019-10-21 13:32:20,620 [SCAN_x.x.x.x] INFO x.x.x.x\1 x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Starting update
2019-10-21 13:32:20,636 [SCAN_x.x.x.x] INFO x.x.x.x\1 x.x.x.x BatchScanning x.x.x.x LOGDEVICEUPDATE DEBUG Starting update checks
2019-10-21 13:32:20,667 [SCAN_x.x.x.x] INFO x.x.x.x\1 x.x.x.x BatchScanning x.x.x.x LOGDEVICEDUPLICATES DEBUG Starting duplicate check for asset with MAC addresses
2019-10-21 13:32:20,683 [SCAN_x.x.x.x] INFO x.x.x.x\1 x.x.x.x BatchScanning x.x.x.x LOGDEVICEDUPLICATES DEBUG Found possible duplicate with assetID: 5880, unique: x.x.x.x\1, 0 MAC addresses and no OID
2019-10-21 13:32:20,683 [SCAN_x.x.x.x] INFO x.x.x.x\1 x.x.x.x BatchScanning x.x.x.x LOGDEVICEDUPLICATES DEBUG Best match for x.x.x.x: id 5880 and unique x.x.x.x\1
2019-10-21 13:32:20,683 [SCAN_x.x.x.x] INFO x.x.x.x\1 x.x.x.x BatchScanning x.x.x.x LOGDEVICEUPDATE DEBUG Updating existing asset
2019-10-21 13:32:20,698 [SCAN_x.x.x.x] INFO LOGDEVICEDUPLICATES DEBUG Editing existing asset 5880 with IP x.x.x.x, unique x.x.x.x\1 and type Linux
2019-10-21 13:32:20,761 [SCAN_x.x.x.x] INFO x.x.x.x\1 5880 x.x.x.x BatchScanning x.x.x.x LOGDEVICEUPDATE DEBUG Adding error: EnableSnmp - Enable SNMP to scan Cisco devices
2019-10-21 13:32:20,761 [SCAN_x.x.x.x] INFO x.x.x.x\1 5880 x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Starting SNMP scan
2019-10-21 13:32:20,761 [SCAN_x.x.x.x] INFO LOGSNMP DEBUG Scanning SNMP for x.x.x.x
2019-10-21 13:32:20,761 [SCAN_x.x.x.x] INFO LOGSNMP DEBUG Scanning Ver2 for x.x.x.x with Global (SNMP Community String)
2019-10-21 13:32:21,089 [SCAN_x.x.x.x] INFO LOGSNMP DEBUG Scanning Ver2 for x.x.x.x with Global (SNMP Community String): success
2019-10-21 13:32:21,089 [SCAN_x.x.x.x] INFO x.x.x.x\1 5880 x.x.x.x BatchScanning x.x.x.x LOGIPMAIN DEBUG Ending IP scan
2019-10-21 13:32:21,089 [SCAN_x.x.x.x] INFO x.x.x.x\1 5880 x.x.x.x BatchScanning x.x.x.x LOGSCANS DEBUG Ending IP scan

It looks as if only SNMPv1 and SNMPv2 are being attempted. Any ideas?

[Bruce_B]

If you're certain there's no SNMPv3 credential even being tried, the issue must lie with your credential mappings, make sure the SNMPv3 credential you want to use is mapped to the appropriate IP ranges under Scanning\Scanning Credentials, in the credential mappings section. Also make sure the credential itself is correct and isn't throwing any password hash errors.

If the credential is actually being tried but failing, make sure FIPS compliance isn't enabled on your scanning server.