SNMP Scanning Issue

kimboaticus · 2013-09-06T13:54:42.000Z

Hi Folks,

I have an odd SNMP scanning issue with some Cisco Switches and Routers. I have had a standardized SNMP community setup on my Cisco gear and the appropriate info is setup in Spiceworks to allow these devices to be queried. All of them work except for a couple which I only noticed yesterday after I upgraded to SW 7. These devices show up as having scanning issues and I go through the troubleshooter to correct these and when I give it the community name required, SW says it doesn’t work. However, if I run the Paessler SNMP tester from the Spiceworks server against these devices, it works no problem. I have tried setting Spiceworks to use SNMP and SNMP v2c but neither work. Very odd. Anyone have any ideas?

scottalanmiller · 2013-09-06T13:57:33.000Z

Maybe some MIBs have gone missing in the update?

kimboaticus · 2013-09-12T14:24:31.000Z

Might be something like that. Switches that were being scanned before SW 7.0 are no longer being scanned so perhaps something was removed?

Ben-B-Spiceworks · 2013-09-12T15:32:30.000Z

Do you have Spiceworks configured with multiple SNMP community strings (Settings > Network Scan), or does everything use “public”?

kimboaticus · 2013-09-12T15:36:40.000Z

I am using a custom SNMP community rather than public, but its just the one.

Ben-B-Spiceworks · 2013-09-12T15:46:04.000Z

I wonder if its the same issue I saw here: http://community.spiceworks.com/topic/post/2522032

Could you send in your scan logs, after enabling “Verbose scan logging” in Settings > Network Scan > Show Additional Settings, and letting a fresh scan run on those devices?

Here’s how to send the logs:

http://community.spiceworks.com/help/Contact_Support#Log

kimboaticus · 2013-09-12T16:18:07.000Z

Ok, I will let it run tonight and send the logs tomorrow.

kimboaticus · 2013-09-16T12:30:27.000Z

Tried to email the logs but its 177 MB in size and is being rejected. Do you have another option for sending the logs?

Ben-B-Spiceworks · 2013-09-17T01:11:06.000Z

No problem - shoot us the email without them and we can reply with instructions on uploading them instead.

cegait0711 · 2013-10-02T13:25:05.000Z

we are having a similar problem with V7 not being able to connect to snmp on my Axis IP Cameras - despite the correct community string being passed.

cegait0711 · 2013-10-02T14:15:23.000Z

Looks like this is also being discussed here:-

http://community.spiceworks.com/topic/380567-v7-introduced-snmp-scan-credentials-error

Ben-B-Spiceworks · 2013-10-03T02:01:11.000Z

Hi CEGA IT, if you find one of your devices in the Inventory and test SNMP credentials, does the test pass? If so, when the device is rescanned does the scan error return?

cegait0711 · 2013-10-03T11:16:22.000Z

@Ben, this shows up as an unknown device, and when I select the snmp method and enter the string, it fails.

Ben-B-Spiceworks · 2013-10-03T15:31:21.000Z

Could you test out resetting the community string to “public” or some other simple community string (on the device), and then test again in Spiceworks?

We had some problems with special characters in Windows passwords, and I’m wondering if this might be a similar issue (if your community string has non-alphanumeric characters outside [A-Z] and [0-9]).

cegait0711 · 2013-10-04T06:03:08.000Z

it is public!

jbell · 2013-10-24T14:31:12.000Z

I’m having a similar issue with a Switchvox server (at least, working through many scan errors now). snmpwalk to the machine with v1 and public works just fine.

Ben-B-Spiceworks · 2013-10-24T23:08:56.000Z

Hi guys, if the scans are failing when using the correct credentials, could you test out changing or adding a new community string on one of the devices?

Does the new community string allow Spiceworks to scan the device?

ruivieira · 2013-10-30T12:21:44.000Z

I also have problems (even with update 7.0.01308) with cisco router and switches.

The switches are detected ok, but sw7 insists on authentication with SSH (We couldn’t connect to this device due to the following error: SSH authentication error when attempting to backup the configuration of this device.) and i don’t want/need SSH open.

The router isn’t detect at all, using the “fix” option with snmp it tells me its good, but after the scan stays the same. Ive deleted the device several times.

ruivieira · 2013-10-30T12:24:27.000Z

Is this the official fix ?!

http://community.spiceworks.com/topic/319630-snmp-scan-not-picking-up-but-test-passed

ruivieira · 2013-10-31T13:29:59.000Z

Well, i deleted the device(router) and did a rescan using the “fix” above, now the router isnt detect at the discovery :S

I[14:23:46.21 2ff800] Found custom SNMP support using Snmp::CiscoSwitchSupport for 10.37.110.254
I[14:23:46.52 2ff800] Found Finder::SnmpTypes::SnmpDevice - 10.37.110.254, uid - FCZ103872FR, message - snmp addressable device
I[14:23:46.54 2ff800] Device gra0578_rt_01 supports Configuration Backup.
I[14:23:46.54 2ff800] Classifier-0: 10.37.110.254(10.37.110.254) supports sip 5060…
I[14:23:46.54 2ff800] Found Finder::OtherTypes::VoipDevice - 10.37.110.254, uid - 192F05E3F8, message - a VoIP device
W[14:23:46.54 2ff800] failed to find matching scenario for computer w/ 2 candidates
I[14:23:46.54 2ff800] Classifier-0: 10.37.110.254(10.37.110.254) is a resolvable yet unknown or offline device
I[14:23:46.54 2ff800] Found Finder::OtherTypes::Unknown - 10.37.110.254, uid - 192F05E3F8, message - network device with no known services
I[14:23:46.54 2ff800] Found Finder::OtherTypes::Unknown - 10.37.110.254, uid - 192F05E3F8, message - network device with no known services
I[14:23:46.54 2ff800] Classifier-0: 10.37.110.254(10.37.110.254) is a resolvable yet unknown device with no open service ports
I[14:23:46.54 2ff800] Classifier-0: completed classifying 10.37.110.254, ip 10.37.110.254 in 3.67 seconds
I[14:23:46.54 2ff800] Classifier-0: finished.