Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Leo, I have 150 9130s from a cancelled project 4 years ago and all loop on our new WLCs. I was fixing the issue with a port ACL forcing the AP to a 5520, but those are now decomm'd. I never thought of the RMA option. I don't think we have a contract ...
I appreciate your willingness to assist, but please read the entire thread, as I explained both the constant "CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN" WLC logs, and also the constant up/down switchport logs.
Thanks. Since my Splunk report found numerous "bricked" APs already deployed in restricted areas, I really needed to find a method to do this without touching the APs. I didn't have to bother TAC with this, as I had access to code versions all the wa...
Thanks. I agree with most of your points, but you are incorrect on the option to resolve this with a 5520. As I mentioned earlier, I have fixed dozens of these 9130s with this issue utilizing a 5520 on 8...183 code. ONLY xxx.183 works however.
All, Thanks so much for your input. Here is an update for my issue… There are numerous related Bug IDs, but this one is the most obvious for my situation. https://bst.cisco.com/quickview/bug/CSCwb46295 UPDATE:My 5520s on the previously mentioned code...
I had a few IDs when I first discovered the issue but cannot find them now. From what I remember, the Flash was full. They are seen on the WLC for a few seconds. This is the current log, then a reboot, then loop... Mar 23 14:02:22 10.71.1.196 1106970...
