Solved: Not Reachable past Core switch?

Jason Fraioli · ‎10-23-2008

This is a fresh install of LMS 3.1/CM5.0. For some reason I can't get CM to reach past my Core switch. Any idea why?

I tried using SNMPv3 authentication, but for some reason couldn't get that to work at all. I enabled an SNMPv2c community string and was able to get this far.

Thanks for any help you can provide.

Type OID IP Address Host Name Neighbors Status

1. 172.20.5.48 172.20.5.48 UnReachable

2. 172.20.5.52 172.20.5.52 UnReachable

3. 172.20.5.220 172.20.5.220 UnReachable

4. 172.20.5.25 172.20.5.25 UnReachable

5. 172.20.5.30 172.20.5.30 UnReachable

6. 172.20.5.36 172.20.5.36 UnReachable

7. 172.20.5.72 172.20.5.72 UnReachable

8. 172.20.5.24 172.20.5.24 UnReachable

9. 172.20.5.71 172.20.5.71 UnReachable

10. 172.20.5.74 172.20.5.74 UnReachable

11. C6509-IOS .1.3.6.1.4.1.9.1.283 172.20.5.1 172.20.5.1 172.20.5.220, 172.20.5.71, 172.20.5.69, 172.20.5.20, 172.20.5.23, 172.20.5.24, 172.20.5.25, 172.20.5.10, 172.20.5.15, 172.20.5.29, 172.20.5.30, 172.20.5.32, 172.20.5.52, 172.20.5.48, 172.20.5.223, 172.20.5.72, 172.20.5.36, 172.20.5.74, 172.20.5.40, 172.20.5.62, 172.20.5.54 Reachable

12. 172.20.5.69 172.20.5.69 UnReachable

13. 172.20.5.40 172.20.5.40 UnReachable

14. 172.20.5.32 172.20.5.32 UnReachable

15. 172.20.5.223 172.20.5.223 UnReachable

16. 172.20.5.10 172.20.5.10 UnReachable

17. 172.20.5.23 172.20.5.23 UnReachable

18. 172.20.5.20 172.20.5.20 UnReachable

19. 172.20.5.62 172.20.5.62 UnReachable

20. 172.20.5.54 172.20.5.54 UnReachable

Joe Clarke · ‎10-23-2008

Unreachable implies the SNMP community strings in your Discovery settings are not correct. Make sure you don't have the v3 strings still configured with an overlapping range. That is, if you have SNMPv2c strings configured for *.*.*.* and you also have v3 credentials for *.*.*.*, only the v3 credentials will be tried.

If you still can't figure it out, start a sniffer trace filtering on UDP port 161 to one of these unreachable devices. Start a new Discovery, and see what credentials are being used to access the device.

View solution in original post

Joe Clarke · ‎10-23-2008

Unreachable implies the SNMP community strings in your Discovery settings are not correct. Make sure you don't have the v3 strings still configured with an overlapping range. That is, if you have SNMPv2c strings configured for *.*.*.* and you also have v3 credentials for *.*.*.*, only the v3 credentials will be tried.

If you still can't figure it out, start a sniffer trace filtering on UDP port 161 to one of these unreachable devices. Start a new Discovery, and see what credentials are being used to access the device.

Jason Fraioli · ‎10-23-2008

Jclarke, that was it. For some reason the wildcard did not work the first time, but did the second time around.