Webauth stops redirecting after some time: CSCtx00942

We hit this bug a few weeks ago. I love the work around -- Reboot your controller for another week or so. I understand Cisco is working on this bug. As a side note. Software will have bugs and I appreciate the fact Cisco will publish these in a timley fashion and not hide their issues like some "other" vendors I know. Webauth stops redirecting after some time
Symptom: It is seen on 7.0.220 4404 WLC that users in the webauth SSID are not redirected to the login page anymore after 1 week or so. This message appears : sshglue.c:7009 WebAuth HTTP Redirect rule creation failed for peer 192.168.1.8 Conditions: webauth, 4404 running 7.0.116/220 Workaround: A reboot solves the problem for another week or so	Status Open Severity 2 - severe Last Modified In Last 3 Days Product Cisco 5500 Series Wireless Controllers Technology 1st Found-In 7.0(116.0) 7.0(220.0)
Interpreting This Bug Bug Toolkit provides access to the latest raw bug data so you have the earliest possible knowledge of bugs that may affect your network, avoiding un-necessary downtime or inconvenience. Because you are viewing a live database, sometimes the information provided is not yet complete or adequately documented. To help you interpret this bug data, we suggest the following: This bug has a Severe severity level 2 designation. Important functions are unusable but the router's other functions and the rest of the network is operating normally. Severity levels are designated by the engineering teams working on the bug. Severity is not an indication of customer priority which is another value used by engineering teams to determine overall customer impact. Bug documentation often assumes intermediate to advanced troubleshooting and diagnosis knowledge. Novice users are encouraged to seek fully documented support documents and/or utilize other support options available.

Comments

[Taylor]

Upgrade to 7.2!

[George]

Well then we would have to upgrade ALL our controllers. We have over 40 WLCs (Wisms)

[Simmo]

Heh, nice! Combine that with the recent security advisory that states move all previous 7.0 to 7.0.220.0 and you have a bit of a pickle. 7.0.220.0 is supposed to be MD....

[Wakomo]

Well we have a anchor controller solution and we notice that the DNS server nic needed to be bounced. 7.0.116.0 code is what we are on. We use a godaddy cert to 1.1.1.1. Sometimes the dns just stop showing the authencation page.