i've managed to get most of my WLCs into cCsco Prime, bar 1x. This one has been incredibly awkward and will not accept my SNMPv3 credentials - the exact same procedure worked for all my other WLC's. I set the AuthMode to HMAC-SHA & Privacy Type to CFB-AES-128 on both the WLC and Prime. Using Prime Infrastructure 3.2 device pack 4. Whenever I try to verify my credentials from the prime box i get: "Device unreachable for SNMP V3 credntials"- credentials entered are correct and the device is reachable from prime to wlc and wlc to prime. What could be wrong? possibly a bug ? I updated Prime to the latest. Has anyone experienced this issue before that could possibly help?
- Ok, you could , for instance, verify your snmpv3 configuation , with other tools besides cisco-prime ; google on 'snmpv3 test tool' or 'free snmp manager software' ; the latter could be used for mib-browsing on the controller over snmv3 (e.g.)
Thanks I tried and got the following error:
No response (check: firewalls, routing, snmp settings of device, IPs, SNMP version, community, passwords etc) (SNMP error # -2003) ( 0 seconds )
Odd that i can ping the controller IP and the controller is local and both prime & wlc are on the same subnet, no firewalls in the way. Beginning to think this could be a bug of some sorts with the controller.
- Begins to sound as a bug; check your current controller version, versus requirements linked to prime version installed (google on stuff as 'wireless compatibility matrix' and or 'cisco prime compatibility matrix'). Possibly try a next version on your controller, but stay compatible with Prime.
Facing similar situation, has it been resolved after upgrading?
We have 3 wlcs and I can successfully add 2 Wlcs into prime. The other one has issue. Just that the first 2 wlcs are in the same network as of the prime whereas the last one is not. However I have checked the connectivity and I am able to ping the wlc from the prime.