12-31-2010 03:54 AM - edited 07-03-2021 07:36 PM
I've hit uppon a problem and I think its due to a change in the code between 6.0.x and 7.0.x versions of code.
We've got a large campus which is a mixture of hospital buildings and university buildings, the university buildings have a separate wireless infrastructure with which they broadcast (amongst others) the ssid eduroam.
As the hospitals on campus are teaching hospitals we also broadcast eduroam in addition to our own ssids.
When we had our WLAN infrastructure replaced this year with cisco kit we started on the first release of 6.x code and after all the work was complete and all the required ssids were available including eduroam I setup a rogue rule. The rogue rule says that all university ssids are friendly.
This worked well even though it sometimes picks up one of our own APs broadcasting eduroam.
Between then and now we've upgraded to 7.0.98.0 code.
Last week we discovered that 2 of our 10 wisms had developed a fault so needed replacing. The new ones arrived yesterday so I got them upgraded to 7.0.98.0 then restored the config. The rogue rule didn't properly restore so I deleted and recreated it with all the university ssids and clicked apply.
The attached file shows the error message I get.
I don't see this mentioned in the release notes for 7.0.98.0
Anyone come accross this?
Solved! Go to Solution.
12-31-2010 05:38 AM
Hi Martin,
The behavior in 7.0 has been in fact changed.
The previous design was in fact considered as wrong: in order to classify Friendly rogue APs for an SSID that we have configured in the WLC, we should refer to the condition "Managed SSID" only.
As a further consequence of this, if now we first define a rogue condition for an SSID and we then try to create a WLAN for that specific SSID, we should be prompted with the error "Cannot create a WLAN whose SSID is configured as part of user defined rogue rules".
Regards,
Fede
--
If this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it.
12-31-2010 05:38 AM
Hi Martin,
The behavior in 7.0 has been in fact changed.
The previous design was in fact considered as wrong: in order to classify Friendly rogue APs for an SSID that we have configured in the WLC, we should refer to the condition "Managed SSID" only.
As a further consequence of this, if now we first define a rogue condition for an SSID and we then try to create a WLAN for that specific SSID, we should be prompted with the error "Cannot create a WLAN whose SSID is configured as part of user defined rogue rules".
Regards,
Fede
--
If this helps you and/or answers your question please mark the question as "answered" and/or rate it, so other users can easily find it.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide