Just wanted to drop by and say that I still have this same issue with multiple platforms.
currently working for a client which is experiencing this issue for:
-3 flexconnect-controllers (7510's)
So it's widely affecting the WLC's.
Only solution TAC has been provided for this is to "wait for the next release".
This problem has been existing since 3.0 with all patches, tech-packs and device-packs.
Now we're on 3.1.1 and issue is still not gone ;).
But 3.1.1 fixed a lot of issues with the controllers that are managed by PI, so it was worth the upgrade.
We're still using 2.2 that don't have any similar issues and it was just until recently we feel that PI 3.x is actually working good enough to shutdown the 2.2 system.
... View more
Again i hit undocumented features in CPI - lost track on how many we're up to now.
Hopefully someone else have seen this syslog message before?
Event Dispatcher was flooded with events and some were lost total:1 since last congestion notification:1
Its severity: critical
I have managed to dig up this information that it has to do with the Health Monitor but here the documentation stops how to troubleshoot further.
Since it says that Severity critical is a Database error i am assuming that the Database somehow caused this issue.
Any suggestions of where to look?
Ps - if cisco reads this PLEASE update your documentation because it's HORRIBLE for anyone to administer this tool!
... View more
Hopefully someone can help me understanding how this tool works, as it's completely undocumented by Cisco.
Here's the scenario.
You go go "Inventory->Device Management->Network Devices-> Wireless Controller.
Then you sort them on "Audit status mismatch".
Select any controller device and click "configure->audit now".
After the audit is done, you get these options that are really undocumented what they do:
Now the problem is that in this case, since the system has been down for a couple of days, engineers have been doing changes on the WLC's themselves not on any templates or from Prime. So the logic is to NOT push down values from prime to the controllers.
What I want to achieve is the reverse, to pull the configurations from the Controllers and have Prime audit them as "the valid working configuration".
So this is the information you get when you click "refresh config from controller" and it's extremely unclear what this warning message means:
This operation will Retain template associations from configuration objects in the database, and retain templates for this controller from associated config groups.
Configuration objects in the database are automatically refreshed. After refresh you might see a mismatch between the template and the controller configuration.
What exactly does that mean?
Does it update the templates or just downloads the configuration from the WLC?
For now, no engineers are allowed to use prime until this has been sorted out. Since in 2.2 it used to update the templates and told prime to actually use the configuration pulled from the WLC's themselves. I am not sure about this message at all!
Thanks in advance.
... View more