I'm trying to determine if there's a way to achieve the following:   An 802.1x client authenticates onto the network.   By virtue of the credentials we leverage the WLC's AAA override feature and redirect that client to a specified interface on the WLC.  That interface effectively generates a splash page (provided by the WLC) that says something along the lines of "Your credentials work" but dead ends the client at that point - not giving it network access.   Is there such a methodology?     Thanks!     ... View more

While looking at client information from a pair of controllers on our NCS (version 1.3.0.20) I see what amounts to 53 different "Unknown" vendors listed among the clients.  My question - Is there any way to update the OUI Vendor data in NCS to reflect the current IEEE registered OUIs?  Considering that approximately 75% of the Unknown vendors I see are Apple devices it would help to have reports reflect vendor reality. ... View more

As we transition buildings to our lightweight infrastructure we're installing new autonomous 1142 APs to fill in gaps and swapping out older 1242s with autonomous 1142s.  What we're seeing is that some of these APs, running the latest IOS code available, are shutting down their 2.4 GHz radios.  The only thing in the logs is: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down The only residual elements that are found (most times) is on the client association page where we'll see what amounts to stale client sessions.  There are two flavors of such stale sessions.  Associations to open networks show clients with IP addresses of 0.0.0.0, the MAC addresses are still listed, and the state is "Associated".  For 802.1x based associations clients show their assigned IP addresses, MAC addresses, and the state appears as "EAP-Associated". I was looking at some of the open caveats with IOS release 12.4(21a)JY to see if anything matched up with the problem I’m seeing.  In the bug toolkit, bug CSCtg09159 (might be related to our problem?) is stated as being “Fixed-in” release 12.4(21a)JHB.  Anyone seen the problem we're seeing?  Anyone know when 12.4(21a)JHB is scheduled for release? ... View more

My WLC has detected (via 15 detecting radios) a rogue AP with a client connected to it. The infrastructure has not determined that the AP is plugged into the local network. I'm trying to contain the AP - I classify it as "Malicious", update its status to "Contain" & assign 2 APs (though the number of APs don't matter here) to contain the rogue. Everything looks right, as the WLC shows that the rogue AP is in a "Contained" status. However, after about a minute the WLC shows the rogue having been reverted to an "Alert" status. I've contain other rogues before but have yet to see one not have the "Contained" status stick. Anyone seen this? Or know why it's happening? Thanks! ... View more

We have a pair of 'legacy' 1310 bridges that serve as a backup radio link to our primary 1400 bridges. I updated the IOS on both root and remote bridges to 12.3(2)JA4. Subsequently, I see that the G radio interfaces of both bridges are down. Through the GUI I see the log states "No SSID with VLAN configured. Dot11Radio0 not started." Upon further investigation I find that through the GUI none of the running/startup configuration is in place - No VLANs defined, No SSID, etc. However, through the CLI the configuration is all in tact. Anyone see this before? ... View more