WCS to WLC SNMP stopped working

Unanswered Question
May 31st, 2010

I am using WCS and WLC, and SNMP just stopped working last Friday.  We had a situation where a user created several hundred ID's, in WCS, then deleted them and created similar ones again, and I think the database may have been corrupted somehow.  I have erased the invalid ID's directly on the WLC, and they stay in sync now for new ID's, but the overnight sync, and the config audit both fail with SNMP error messages.  SNMP exception while syncing with WLC from the Guest Account Sync task, and Failed for all devices from the config sync.  I found the error below in the log, bit I have no idea about how to fix it.

5/29/10 01:00:00.136 INFO[stspoll] [31] Configuration Sync for device started. 
5/29/10 01:00:09.387 ERROR[snmpmed] [31] SNMP Operation Error: Table too large for class  LocalNetUser
5/29/10 01:00:09.387 INFO[stspoll] [31] Configuration Sync for device failed with reason : MEDIATION-1,Table too large, possible agent loop,LocalNetUser
5/29/10 01:00:09.387 TRACE[com.aes] [31] [ThreadPoolCallbackImpl:onTaskException] THROW
com.cisco.server.common.errors.SnmpOperationException: MEDIATION-1,Table too large, possible agent loop,LocalNetUser

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Scott Fella Tue, 06/01/2010 - 06:13

Did you try to refresh the config from the WLC and did you delete the old entries or did you retain them.  this might be the reason you see these errors.  On WCs you can manually run an audit to see what differences you have between the two.


GENE MCTIERNAN Tue, 06/01/2010 - 07:18

Refreshing or running a manual audit results in the same errors.  I deleted the entries on both WCS and WLC.

GENE MCTIERNAN Tue, 06/01/2010 - 09:32

That looks promising, I will try this weekend (too many users to shut down during the week)

Lucien Avramov Tue, 06/01/2010 - 13:37

I dont advise you to start with the DB this is not DB related problem at first sight.

First of, your WLC version is too new to be supported for the WCS version you have as per release notes:


That WCS only supports WLC max.

For later WLC, you need to upgrade WCS.

Fix that first. You can upgrade WCS during production, it's not having an impact on the WLC.

Then FYI, for troubleshooting SNMP / WCS / WLC problems, look at my video. I also cover the upgrade steps for WCS:


or for bigger size:



Please support CSC Helps Haiti



Scott Fella Tue, 06/01/2010 - 15:33


Good to know... I was once told by TAC that as long as the WCS and WLC code train are on the same main version I should be fine.  Since it is based off the main code train and the upgrades are usually certain bug fixes or enhancements.  Seems like every new code the comes out on the WLC requires the WCS to be upgraded nowadays.  So even if the is ED, WCS is also ED, you would need to upgrade to WCS or would you suggest MD?


Lucien Avramov Tue, 06/01/2010 - 16:25

With newer WLC release, the mib do change and the WCS needs to be aware of those changes. Hence the WCS version needs to be released after the WLC code and not the other way around, so in your case, we need to upgrade WCS.

I do encourage you to run the latest and greatest WCS to support the WLC version you have.


This Discussion



Trending Topics - Security & Network