03-10-2015 01:00 AM - edited 07-05-2021 02:40 AM
WLC 5508 8.0.115 fails when add to prime 2.2: Unable to collect details neighbor device using Cisco Discovery Protocol. Posible cause :
SNMP request timed out. Verify device credentials and SNMP response speed from device. The SNMP credentials are corrects.
Capturing packets we see that the WLC responds snmp requests but prime does not know how interpret the responses and re-order them.
Solved! Go to Solution.
05-04-2015 03:00 AM
Hi,
please check this post
http://itsnotthefirewall.com/2014/08/07/cisco-wlc-not-adding-to-prime-infrastructure/
03-10-2015 05:48 AM
When you test and verify the credentials on PI 2.2, does both show as pass? The controller and PI seperate across the WAN or are the local to each other? Are you using smnp v3 by chance?
-Scott
03-11-2015 12:48 AM
The credentials pass always previous test, the controller and Prime are in a local network. I tried with snmp version 2c and 3.
03-12-2015 01:51 PM
Are you using both management and dynamic (an interface of WLC with an IP address on the same VLAN as Prime Infrastructure) ? If So due to asymmetric routing, it may happen PI will face issue in communicating.
03-17-2015 02:01 PM
Hi Josè,
have you solved your issue?
Now it is also mine:-)
It looks line a 8.0.115 or prime 2.2 bug.
03-27-2015 01:33 AM
Hello,
It worked for me with prime version 2.2 and controller version 7.6.130. If there is any dynamic interface in the controller with ip address from the same subnet as prime , then remove it and resync. It should work.
Thanks
Shabeeb
05-04-2015 03:00 AM
Hi,
please check this post
http://itsnotthefirewall.com/2014/08/07/cisco-wlc-not-adding-to-prime-infrastructure/
05-06-2015 04:18 AM
I Solved it , I changed "Maximum VarBinds per Get PDU" from 30 to 15 in Administration > Settings > System Settings > SNMP Settings
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide