cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Welcome to the Smart Net Total Care Community!

Our community includes Cisco experts to answer your questions about the Smart Net Total Care (SNTC) portal and CSP-Collector.
Click the navigation links below to access materials for using our service and supported collectors.

148
Views
0
Helpful
3
Replies
Highlighted
Beginner

Discovery using subnet scanning not working correctly after upgrade to v2.8

I have upgraded y collector to v2.8.01 and when I run discovery scans using subnets, it runs through some of the IP's and then the logs stop. The scan job is still running but nothing new is in the logs so it looks like the job is stuck. How can I fix this as that is how we have done our scans to make sure we can include any devices we aren't sure that are on the network?

 

Here is the output of the log and it is stuck at this for a couple of hours now.

 

Message

"Starting Ip Address Scan based discovery.."

"      ->10.22.0.0-10.22.255.255"

"Device Discovered with protocol snmpv2c:10.22.0.8"

"10.22.0.8 is managed."

"Device Discovered with protocol snmpv2c:10.22.0.10"

"10.22.0.10 is managed."

"Device Discovered with protocol snmpv2c:10.22.0.11"

"10.22.0.11 is managed."

"Device Discovered with protocol snmpv2c:10.22.0.101"

"10.22.0.101 is managed."

"Device Discovered with protocol snmpv2c:10.22.0.251"

"10.22.0.251 is managed."

"Device Discovered with protocol snmpv2c:10.22.0.252"

"10.22.0.252 is managed."

"Device Discovered with protocol snmpv2c:10.22.0.253"

"10.22.0.253 is managed."

Everyone's tags (1)
3 REPLIES 3
Cisco Employee

Re: Discovery using subnet scanning not working correctly after upgrade to v2.8

Hello,

 

Could you attempt to run a TCP dump on port 161 to see if the collector is running any SNMP traffic during the discovery job? This will need to be executed at the collectorlogin or root level.

 

Additionally, please provide the output of the below commands:

 

#du -h

#ls -larts /var/log

 

 Edit - Corrected DU command

Beginner

Re: Discovery using subnet scanning not working correctly after upgrade to v2.8

It looks like it is scanning when I use the tcpdump command to show the network traffic. That is much easier to follow than the logs.

 

dh -h doesn't work, it says "no such command" I tried using the admin and root accounts.

 

[root@it-ciscosn-p-01 collectorlogin]# ls -larts /var/log
total 6504
4 drwxr-xr-x. 18 root root 4096 Mar 12 2017 ..
8 drwx------+ 2 root root 4096 Mar 22 2017 aide
8 -rw-r-----+ 1 root utmp 172 Oct 5 2017 btmp-20171005.gz
8 -rw-r-----+ 1 root root 162 Oct 26 2017 secure-20171026.gz
8 -rw-r-----+ 1 root root 674 Oct 26 2017 maillog-20171026.gz
8 -rw-r-----+ 1 root root 918 Oct 26 2017 cron-20171026.gz
8 -rw-r-----+ 1 root root 20 Oct 26 2017 spooler-20171026.gz
8 -rw-r-----+ 1 root root 20 Oct 26 2017 daemon.log-20171026.gz
8 -rw-r-----+ 1 root root 20 Oct 26 2017 boot.log-20171026.gz
8 -rw-r-----+ 1 root root 20 Oct 26 2017 unused.log-20171026.gz
8 -rw-r-----+ 1 root root 440 Oct 26 2017 syslog-20171026.gz
8 drwxr-xr-x+ 2 ntp ntp 4096 Oct 26 2017 ntpstats
16 -rw-r-----+ 1 root root 10587 Oct 26 2017 yum.log-20180101
20 -rw-r-----+ 1 root root 13383 Oct 1 22:37 dracut.log-20171026.gz
20 -rw-r-----+ 1 root root 14469 Oct 2 17:21 yum.log-20181112
8 -rw-r-x---+ 1 root utmp 1536 Nov 5 10:12 btmp-20181112
40 -rw-rw-r--+ 1 root utmp 30336 Nov 12 21:49 wtmp-20181112
20 -rw-r-----+ 1 root root 13344 Nov 12 22:32 dracut.log-20181001.gz
396 -rw-r-----+ 1 root root 397851 Nov 12 22:32 dracut.log-20181112
4 -rw-r-x---+ 1 root utmp 0 Nov 12 22:32 btmp
8 drwx------+ 3 root root 4096 Nov 12 22:36 samba
200 -rw-r-----+ 1 root root 200499 Nov 12 22:38 dracut.log
16 -rw-r-x---+ 1 root root 10754 Nov 12 22:44 yum.log
4 -rw-r-----+ 1 root root 0 Nov 15 03:32 spooler-20181116
4 -rw-r-----+ 1 root root 0 Nov 15 03:32 unused.log-20181116
76 -rw-r--r--+ 1 root root 71494 Nov 15 18:19 dmesg.old
8 -rw-r-----+ 1 root root 1372 Nov 15 18:20 daemon.log-20181116
12 -rw-r--r--+ 1 root root 5834 Nov 15 18:22 boot.log-20181116
12 -rw-r-----+ 1 root root 4776 Nov 16 02:00 maillog-20181116
124 -rw-r-----+ 1 root root 115897 Nov 16 03:24 secure-20181116
16 -rw-r-----+ 1 root root 9244 Nov 16 03:27 cron-20181116
60 -rw-r-----+ 1 root root 56914 Nov 16 03:27 kern.log-20181116.gz
380 -rw-r-x---+ 1 root root 383076 Nov 16 03:27 messages-20181116.gz
4 -rw-r-----+ 1 root root 0 Nov 16 03:27 spooler
4 -rw-r-----+ 1 root root 0 Nov 16 03:27 unused.log
20 -rw-r-----+ 1 root root 14546 Nov 16 03:27 syslog-20181116
8 drwxr-x---+ 2 root casusers 4096 Nov 16 04:25 audit
76 -rw-r--r--+ 1 root root 71494 Nov 16 10:05 dmesg
8 drwxr-xr-x+ 6 root root 4096 Nov 16 10:05 .
68 -rw-r-----+ 1 root root 60578 Nov 16 10:05 vmware-vmsvc.log
32 -rw-r-----+ 1 root root 21529 Nov 16 10:05 vmware-vgauthsvc.log.0
8 -rw-r-----+ 1 root root 491 Nov 16 10:05 daemon.log
12 -rw-r--r--+ 2 root root 5834 Nov 16 10:08 boot.log
8 -rw-r-----+ 1 root root 2563 Nov 16 10:08 syslog
12 -rw-r-----+ 1 root root 4258 Nov 16 15:01 cron
160 -rw-r-----+ 1 root root 158058 Nov 16 15:50 secure.old
8 -rw-r-----+ 1 root root 2978 Nov 16 15:50 maillog
16 -rw-r-----+ 1 root root 1294848 Nov 16 15:55 tallylog
168 -rw-r-----+ 1 root root 161065 Nov 16 15:55 secure
20 -rw-rw-r--+ 1 root utmp 13056 Nov 16 15:55 wtmp
16 -rw-r--r--+ 1 root root 5908036 Nov 16 15:55 lastlog
184 -rw-r-----+ 1 root root 176964 Nov 16 15:56 kern.log
4136 -rw-r-x---+ 1 root root 4224465 Nov 16 15:56 messages

Beginner

Re: Discovery using subnet scanning not working correctly after upgrade to v2.8

[root@it-ciscosn-p-01 collectorlogin]# du -h
2.1G

CreatePlease to create content
Right-rail
Navigation
Be sure to bookmark these support pages and use them in the future to find all the self-help information.
Helpful Links