Hello, I am an IT intern for a ad agency and currently working on getting all the devices in my network inventoried on Spiceworks. This is my first time posting to this forum (though I browse around the community a lot to try and learn more) but I am running into a problem where one of our switches isn’t communicating with the Spicework network scan. Our other switch that is set up identically to the one giving us problems is pulling up information just fine; however, the other one isn’t being picked up in the network scan, despite having the using the same SNMP string. If I could ask for the community’s help in steering me the right way to addressing this problem, as far as things I could do, I would greatly appreciate it! Thank you.
4 Spice ups
Rod-IT
(Rod-IT)
2
Confirm that your switch SNMP settings do not require a list of allowed IPs, SNMP will be dropped if the SW scanners IP is not listed as allowed. (it might be listed as acl
I checked and we have the switch’s SNMP setting to allow it to be scanned from all IPs performing the scan.
A maybe pertinent piece of detail I forgot to add; we ping’d the switch just to make sure that it was active on the network, and it responded but it isn’t communicating with the spicework scan.
When looking at all the devices on the scan on the Spiceworks page, that particular switch just shows up as a grey rectangular box, whereas all the other switches that are being recognized in the scan are showing up green.
Rod-IT
(Rod-IT)
4
Which suggests something is blocking it.
Can you telnet port 161 from the SW server?
What does the switches log say?
2 Spice ups
dbeato
(dbeato)
5
Welcome to the community! What is the Switch model? and does the switch have the default gateway configured?
Thank you much for the welcome and the help! I look forward to be being more active in the community and learning more from everyone.
But we were able to telnet port 161 and it gave us this in the log:
Which gives me a great place to start to do some further research, I will look up what these errors mean and hopefully figure it out. If you guys have any other information and tips, I’m all ears 
Again, thank you guys much!
1 Spice up
They’re Cisco SG500-52P switches being used. I don’t quite understand the default gateway, we’ve been trying to communicate with it through a public SNMP community string. Sorry, I’m quite green so if you could elaborate on the gateway configuration; I can try to find out more detailed answers.
1 Spice up
dbeato
(dbeato)
8
It means that the address where the SNMP requests from Spiceworks have been denied, allow the connections from that IP address and you should be good.
Rod-IT
(Rod-IT)
9
Scan using public and not your own snmp string and see how that works, though unauthorized suggests the SW server is not allowed to query SNMP
1 Spice up
We initially had that switch configured to allow connections from all IP addresses, but changed that to allow it from a specific IP address from the device that we’re using to communicate with the switch. Coincidentally, as we were doing this, we noticed that the other switch that is set up identically had failed this morning’s scan. So we rescanned the two switches with only communication from our IP address allowed and the one that failed to communicate is now responding. But the other we’re having the initial problems with is still not responding. This was done while using the public string.
Rod-IT
(Rod-IT)
11
Disable your scan ranges (settings, inventory, device scanning) add in the IP of the failing switch and scan only this one.
What happens, what do the scan results look like and what does your device look like in the inventory after this?
I noticed too that while rescanning these two switches, after making those changes, the details of the scan states that its only scanning 1 of the switch (the non-problematic one), even though we input two IP addresses in the scan criteria.
Sort of like the network scan on Spiceworks isn’t even seeing the IP address for the switch with the issues.
Rod-IT
(Rod-IT)
14
Do as above please, then note the time, open your SW/logs folder and look in the production.log for the IP you just scanned, if it makes no sense you can paste some of it here, but cover your actual IPs and machine names with relevant fake details
Hello, sorry for the late reply.
When I run the scan on just that one IP address for the switch that’s currently exhibiting problems; it now finishes a scan with a red box saying that it has failed (before it just showed up as a grey box with no further information). Such as in the pic below:
And this was the results of the scan in the log:
21474815752017-Jul-10 09:47:28Informational%AAA-I-CONNECT: New http connection for user sraadmin, source 10.242.149.173 destination 10.242.148.24 ACCEPTED
21474815762017-Jul-10 09:47:05Informational%AAA-I-DISCONNECT: http connection for user sraadmin, source 10.242.148.179 destination 10.242.148.24 TERMINATED
21474815782017-Jul-10 09:46:47Informational%AAA-I-CONNECT: New http connection for user sraadmin, source 10.242.148.179 destination 10.242.148.24 ACCEPTED
Rod-IT
(Rod-IT)
16
It should not be using HTTP it should be using SNMP, if its not showing the port as open, look again at any SNMP settings on the switch
1 Spice up
I ran the scan again using SNMP, with a public string and it’s showing the same results. I checked the SNMP settings on the switch and they are identical to the other switch that is communicating, so I am at a lost as to why that one pulls up information but this one does not.
1 Spice up
dbeato
(dbeato)
18
Disable SNMP and re-enable on it on the switch.
Rod-IT
(Rod-IT)
19
From Spiceworks server, can you telnet the switch on port 161?
2 Spice ups
We tried to telnet the switch on port 161 from Spiceworks server, it failed and we initially thought that was the problem. But then we tried to telnet a known good switch with the same method and it failed too.
1 Spice up
