SNMP timeout catalyst

[Moudar]

Hi

i have tested eveything i know but it still shows snmp timeout

.\SnmpWalk.exe -r:172.23.3.250 -c:private -v:2c -os:.1.3.6.1.2.1.1.1.0
SnmpWalk v1.01 - Copyright (C) 2009 SnmpSoft Company
[ More useful network tools on http://www.snmpsoft.com ]

OID=.1.3.6.1.2.1.1.2.0, Type=OID, Value=1.3.6.1.4.1.9.1.2427
OID=.1.3.6.1.2.1.1.3.0, Type=TimeTicks, Value=112 days, 5:47:41.00
OID=.1.3.6.1.2.1.1.4.0, Type=OctetString, Value=Tietoevry Network Offshore
OID=.1.3.6.1.2.1.1.5.0, Type=OctetString, Value=wlc-112-0039-250
OID=.1.3.6.1.2.1.1.6.0, Type=OctetString, Value=FABRIKKVEIEN 84, 4323 SANDNES
OID=.1.3.6.1.2.1.1.7.0, Type=Integer, Value=2
OID=.1.3.6.1.2.1.2.1.0, Type=Integer, Value=6
OID=.1.3.6.1.2.1.2.2.1.1.1, Type=Integer, Value=1
OID=.1.3.6.1.2.1.2.2.1.1.2, Type=Integer, Value=2

as you can see above snmp works fine on WLC

so the problem is CCC

i have added CLI user and snmp V2C correct but still snmp timeout
WLC shows reachable on CCC but AP are unreachable

WLC is 3504 running 8.5.131, it worked before!!

so i think snmp is the key

done resync many times but still there

[balaji.bandi]

Does the WLC have any ACL configured, and is the DNAC (Cat C) IP allowed to snmp?

You can see the logs on WLC. Why was this failing?

above you doing only read community, is the write community same ? if not remove and test it.

[pieterh]

the AP's are accessible through the WLC, and so a problem with accessing the WLC also has effect on the AP's

in the same window as you attached for credentials, there is also a button to "test credentials" 
what result gives this test ?
does it give a different result with "select global credential" and "se;lect device specific credentials" for snmp?

>>> WLC is 3504 running 8.5.131, it worked before!! <<<
has CCC been upgraded ? -> check version compatibility

[Moudar]

as you can see validation is green

but still snmp timeout

does deleting wlc and adding it again a possible solution, would that affect the wifi by any means?

[pieterh]

it could be the WLC needs too much time to response to th snmp query for it's configuration
High CPU or memory usage on switches/routers can cause SNMP requests to time out.

some things you can modify/check
Adjust SNMP Settings: Navigate to System > Settings > Device Settings > SNMP to adjust the Timeout (default 5s, valid 1-300s) and Retries (default 3, valid 1-3).
Verify Connectivity: Ensure network latency between Catalyst Center and network devices is ideally under 100 ms RTT, with a maximum of 200 ms RTT.

if you did not configure the WLC using templates in CCC then deleting and rediscover should not impact the WIFi operation

[Moudar]

as you can see i have tested discovery  and it works fine

but still managed: sync timeout

i have tested 5 and 60 for timeouts same problem

what if i delete it and add it again how risky is that?

[Moudar]

I did delete the WLC and waited 10 mins and then added it again with same problem😑 with no AP at all, 

[pieterh]

you did not answer the question about software version?

https://www.cisco.com/c/dam/en/us/td/docs/Website/enterprise/catalyst_center_compatibility_matrix/index.html

Device	Device Series	Device Model	Recommended Release	Compatible Release	Cisco DNA Essentials License	Cisco DNA Advantage License
Cisco 3504 Wireless Controller	AIR-CT3504	AireOS 8.10.196.0	AireOS 8.10.196.0	Y	Y

[Moudar]

version is 8.2.166 and WLC 5508 this is another one

i know maybe that is not supported on catalyst 

but it worked yesterday and we did not upgrade anything 

[pieterh]

if the wlc AND Catalyst Center have not changed then it must be something in between?
-> maybe traffic between Catalyst Center and WLC has something changed?
snmp is UDP -> "best effort" ; packets may be dropped in favor of other trafic, when traffic load gets too high

- is this a HA setup? -> you may be running on the backup WLC ?

[Moudar]

*RRM-DCLNT-5_0: Mar 06 09:44:58.906: [SA] detect AP lradMacAddr: 00:78:88:DE:F9:90 lradSlotId:1,neighbor mac: 58:AC:78:29:1E:DF neighborChannel:64, neighborRssi:-72 .

*snmp_trap_msg_task: Mar 06 09:45:00.409: [SA] Succeeded Sending ciscoLwappDot11ClientMovedToRunState trap                       for client 56:40:b2:bc:9d:d9
*snmp_trap_msg_task: Mar 06 09:45:00.409: [SA] AP Name: AP-11, MAC: 00:78:88:xx:xx:xx, radId: 166
*snmp_trap_msg_task: Mar 06 09:45:00.409: [SA] getApName rc: 0
*snmp_trap_msg_task: Mar 06 09:45:00.410: [SA] Succeeded Sending ciscoLwappDot11ClientSessionTrap trap                       for client 56:40:b2:bc:9d:d9
*RRM-DCLNT-2_4: Mar 06 09:45:00.493: [SA] detect AP lradMacAddr: CC:16:7E:42:29:70 lradSlotId:0,neighbor mac: 00:81:C4:59:E6:80 neighborChannel:1, neighborRssi:-53 .

on WLC if i run debug i can see the above logs and more

but CCC still shows only WLC as reachable with no AP

!!!

[pieterh]

That is to be expected!

You need to get the communication between CCC and WLC in order first.

If CCC cant't query the WLC correctly, then it cannot retrieve the AP information either.

added: by the way, did you check if expired (3y or 5y subscription) DNA licenses  are involved?