I run LMS 2.6. I am having an issue with end devices on some 4503's not being discovered. My 4506's run the same IOS and the same configuration and are listing all end devices. I checked cdp in the switches and all see their neighbors, but in Device manager in LMS, the cdp neighbor is blank. I checked snmp etc. Everything else in LMS is populating for these switches, just not end devices. I've run Data Collection few times. Still nothing.
Any suggestions or help would be appreciaed.
As far as I can tell, all models of 4503 are supported in this version of Campus. Make sure that these switches have been Data Collected. Check that you do not have any Data Collection filters defined in Campus, then run a full Data Collection from the Campus Manager homepage.
When Data Collection finishes, check the topology map to see how these switches appear.
I ran Data Collection a few times. Checked the Data Collection filters, have none defined. Switches look fine in topology and in Cisco View.
In the Data Collection details, I have a few that are not showing any cdp neighbors. And those are the ones that will not show any end devices when I try to run a UT report. If I telnet into these switches and do a sh cdp neighbor, the neighbors are there.
Anything else I can check?
If they show up fine in Topology, then they should have neighbors. Post a screenshot showing one of these 4503s on the Topology Map.
Then that explains all the other problems. You can check the ani.log for errors pertaining to these devices. The most likely cause is bad SNMP community strings.
That seems to be the problem. The RW snmp is there and I did an edit device credentials, but when I do a credential verification report, under the Read Write Community column it comes up "No Value to test". RW configured on switch the same as the others that I'm not having any issues with, and in Ciscoworks the same.
BUT, another switch that I am having the same issue with, both Read and Read/Write Community when I do a Device Cred. verification come up "ok".
The read-write community string is not required for Data Collection. As long as you have a valid read-only string, Campus should be able to manage the device. Again, the ani.log may have more details if there is an error trying to communicate with these devices.
Go ahead and open a TAC service request for this. They will walk you through enabling debugging so that further analysis can be done.