Things to check in this case are discovery filters under Campus Manager > Admin > Device Discovery > Discovery Settings and make sure you are not filtering out the missing devices.
Next, make sure that the SNMP settings are correct for all devices in your network under Campus Manager > Admin > Device Discovery > SNMP Settings.
Then, make sure CDP is enabled down to all of the devices in your network. If you have gaps in CDP, you will need to add multiple seed devices in each CDP region.
Finally, check the Discovery report by clicking on the number of devices discovered under Campus Manager > Home. Make sure all of the devices that were discovered were reachable. If not, you will need to figure out why those devices are not SNMP-reachable from the LMS server.
If you still can't figure out why Discovery is not finding all of your devices, enable devdiscovery debugging under Campus Manager > Admin > Device Discovery > Debugging Options, run a new Discovery, and look at the discovery.log for any errors.
* I have listed 9 upto major core seed devices (routers&switches) from our Toronto, Montreal and Calgary core infrastructure.
* I have specified our three major IP summarized IP ranges with asterisks for wildcards as follows
* CDP is enabled on at least 90% of our network gear. We estimate that our total netwok devices of routers/switches should be in the range of 1000 to 4000, and I am only seeing 571.
* I am using the same SNMP string that our other monitoring application is using. which is IND and that application see's the whole topology.
I will try the debugging and find out why some devices are unreachable.
Also, check to make sure you have enabled "Jump Router Boundaries" in your discovery settings. If you still can't figure it out, post the log and the NMSROOT/campus/etc/cwsi/DeviceDiscovery.properties file.
You can compress it down. Note, you will also need to provide one missing device, and how that device is connected into the discovered topology.
an example of one missing device would be
It is a router(3640) that is connected to the same vlan on our core switch.
Device 126.96.36.199 was discovered and it is on the same vlan as 188.8.131.52
I hope i provided the info you needed.
This device did get discovered as 172.29.96.5, then it was rejected since that was not in the valid range. You might want to try adding the following to DeviceDiscovery.properties, and see if that helps:
- I will change the seed ip range from 172.20.x.x & 172.21.x.x to 172.*.*.*
- I will go back and see what the loopback scheme is that is being used.
- if I wanted to ensure I grab every single device regardless of scheme..would you recommend *.*.*.* in device discovery?
what exactly does "Discovery.SkipExcludedLoopback=true" do?
If you want to grab every device, don't specify a discovery range.
SkipExcludedLoopback tells Discovery not to set a device's management IP to an address that is not in the allowed discovery range.