Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

WLAN Controller in Campus 5.0.3 (LMS 3.0.1)

The Campus 5.0.3 release notes state that the WLAN Controller 4400 series are supported. After installation of the 5.0.3 patch, the Controller is still a red icon (unknown) on the topology map.

The credentials are fine because I'm able to perform a SNMP MIB walk via CWLMS.

11 REPLIES
Cisco Employee

Re: WLAN Controller in Campus 5.0.3 (LMS 3.0.1)

Check the DCR credentials for this device. The fact that the icon is red has nothing to do with support; that means the device is unreachable via SNMP. You may also want to start a sniffer trace filtering on udp/161 traffic to this device, then run a new Campus Data Collection to see how Campus is querying the controller.

Community Member

Re: WLAN Controller in Campus 5.0.3 (LMS 3.0.1)

credentials are correct, I posted the ANI.log, one of the error messages is; Cannot normalize/resolve CDP port name Unit

This controller is connected via a multi-module channel. But other controllers are connected via a GEC on a single switch have the same problem

From the switch perspective I do see the controller as a neighbor.

Cisco Employee

Re: WLAN Controller in Campus 5.0.3 (LMS 3.0.1)

This looks like an SNMP timeout issue, or an issue reading the CISCO-CDP-MIB on the controllers. Can you post a sniffer trace filtering on udp/161 traffic to one of the affected controllers when running a Campus Data Collection?

Community Member

Re: WLAN Controller in Campus 5.0.3 (LMS 3.0.1)

the sniffer trace

Cisco Employee

Re: WLAN Controller in Campus 5.0.3 (LMS 3.0.1)

Campus is polling these controllers with the community string of "campus" and the controllers are responding with noSuchName for every object. This is causing your problem. This points to either an SNMP configuration error on the controller, or you have the wrong community strings configured in DCR.

Community Member

Re: WLAN Controller in Campus 5.0.3 (LMS 3.0.1)

FYI: The WLC4404 is not supported, only the WLC4402. However, the MIB implementation in the 4.2 firmware on the 4404 has a bug.

snmpwalk -v 2c -c public 1.2.3.4 .1.3.6.1.2.1.1.2.0 returns: SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.14179.1.1.4.3

So MIB walk reports that it's a 4402 but it's a 4404 ;-)

Cisco Employee

Re: WLAN Controller in Campus 5.0.3 (LMS 3.0.1)

That still wouldn't explain why you're seeing the noSuchName errors when Campus tries to poll this device. In fact, this bug should allow Campus to support the 4404.

Community Member

Re: WLAN Controller in Campus 5.0.3 (LMS 3.0.1)

FYI: I enabled debugging on the WLC4404 and discovered that datacollection was using SNMP v1 which is disabled on the controller by default.

For a workaround I've enabled SNMP v1 on the controller but Is there a way to force Campus (ANI) to use SNMP v2 instead??

Cisco Employee

Re: WLAN Controller in Campus 5.0.3 (LMS 3.0.1)

No. A bug was just filed for this, though, CSCsr63221.

Community Member

Re: WLAN Controller in Campus 5.0.3 (LMS 3.0.1)

I would not expect a device to respond to

SNMPv1 requests when that version is

explicitely disabled. But the WLCs sends

an "End of MIB" answer.

Maybe this contributes to the problem?

Cisco Employee

Re: WLAN Controller in Campus 5.0.3 (LMS 3.0.1)

Not really. If the device didn't respond at all, the symptoms in Campus would be the same: the device would be unreachable.

187
Views
0
Helpful
11
Replies
CreatePlease to create content