CPI WLC Unreachable

[adam.gray]

Hi,

I have inherited a system that was working, and I'm a bit new to this gear.  The other day I noticed that the controller has become unreachable and along with it no data.  It was not set up by me and it was working.  Can anyone give me a few pointers as to how to diagnose what the issue might be.  I have been through the setup and that looks fine,  and checked the blogs but I can't see my exact problem.  So before I start fiddling with a possible working configuration, can anyone suggest any diagnostic procedures.

Thanks

Adam

CPI 2.0

WLC 2504 SW 7.6.100.0

Reachability Status: Unreachable

Inventory Collection: Managed and Synchronise (red)

Audit Status: Not available

Network audit: enabled

Controller SNMP v2c, v3c enabled,  SNMP port 161,  Trap Port 162

[Rasika Nayanajith · Accepted solution]

I would check first WLC has rechability to CPI (ping & see)

Then I would remove WLC from PI & readd

Refer below post, if you are doing it using SNMPv3.

https://mrncciew.com/2014/05/03/cisco-prime-device-mgt-using-snmpv3/

HTH

Rasika

*** Pls rate all useful responses ***

[adam.gray]

Thanks for your help Rasika,

I just got back to work and after documenting as much as the setup as possible,

The device would ping etc.

I removed the WLC and re-added it.  Now it is reachable but the Inventory collection status failed with the details of

"CLI Failure: Connection to the device failed."  Removed and reinstalled it several times removing all authentication.  Still the same result.  Any ideas from here?

Thanks

[adam.gray]

Hi Rasika,

Finally got it but not to sure what the issue was.  I saved and rebooted the controller, no joy , removed and re-added the controller from prime and it worked.  Might be an earlier version of software that requires a reboot.

A few thinks were apparent before this.

1:SNMP 3 not connecting

 had to remove the authentication from SNMP v3 ... this got the best result of CLI not working

2:CLI issue

Enabled telnet instead of SSH, but I got an error of not all information was being picked up.

My best guess is

1: That any changes to the controllers SNMP config required a reboot

2: There might be something wrong with the SNMP v3 authentication

3: The controller needed to be removed not just updated, however updates did show an improvement

Diagnosis

I did test SSH and telnet manually,  I think this is a good idea to help give confidence.

I would recommend removing all security authentication and protocols to get it working then re-add later.

I would suspect I also need to update the firmware,  but as it was in production and was working, then I would rather prove it failed with minimum change.

Thanks for your help.  The links were most helpful.

Adam

[Rasika Nayanajith]

Hi Adam,

Glad to see you get it working & thanks for detailed update.

If our response was helpful you can mark this thread as "answered"

Rasika