The bug ID CSCvd91152 Journey
Is there any release this bug doesn’t affect?
This is the journey regarding the above cisco bug, for those not accustomed to this bug, here it is taken from cisco’s Bug Search Tool (Word for word)
Symptom:
An access point may unexpectedly reload. In the AP's crashfile, shortly before the crash, errors similar to the following are logged:
*Jun 25 11:18:35.579: Rx radio stop 1
*Jun 25 11:18:35.579: %DOT11-2-RADIO_RX_BUF: Corrupt buf:1E4A16C0 rcv:46F0ABA2/F255FD27 prog:099AF990/099AF990 pak:09004104 clns_flags:FACD1010
*Jun 25 11:18:35.579: %DOT11-2-RADIO_RX_BUF2: Ring in/out:28430911/28430656 ProgID:28430657 Last:1E529568 Errs:0/0/0
*Jun 25 11:18:35.579: %SOAP_BUF-2-PAK: pak:09004104, pool:Wlan Pool, pool size:2704
Conditions:
802.11k and PMF (802.11w) are enabled (possibly on different WLANs).
AP 2702 or 3702.
Seen with APs in Local, FlexConnect or autonomous mode.
Workaround:
Disable PMF.
Alerts from Prime regarding affected AP’s read
1. Alarm Condition: AP disassociated from controller
Message: AP XXXXXXX disassociated from Controller XXXXXXXX
Failure Source: a8:9d:21:89:cc:c0:XXXXXXXX
Application Category Data: AP_DISASSOCIATED
When the AP re-associates another alert is received
1. Alarm Condition: AP disassociated from controller
Message: Access Point XXXXXXXX associated to controller XXXXXXX Reason for association 'AP Crashed Due To Software Failure'.
Failure Source: a8:9d:21:89:cc:c0:XXXXXXXX
Application Category Data: LRAD_REBOOTREASON
Can I add at this point, we were on the 8.3 train, cisco TAC also advised me to disable 802.11k and 802/11v as well as PMF.
Not a problem I hear you say, and then wait for it…... upgrade our firmware to the 8.5 train.
Here the problems come into play as we have 474 AP’s on site and upgrading the firmware (even with the predownload command applied and the default AP boot image changed) left me in a mini sweat!
When advised to migrate to the 8.5 train this bug was supposed to be eliminated, and with the predownload command applied and the default AP boot image being changed, this was supposed to be a relatively straight forward piece of early morning work.
I do remember, when I upgraded our WLC to the 8.3 train. I had the predownload command applied and the default AP boot image changed I ran into issues with some AP’s fizzling out and doing the AP version of the “Blue Screen of Death”. So, I thought, no worries just make sure I have some replacements, it can’t be that bad!.......
Once the predownload was done, I could tell from the show ap image all command there were some AP’s that had problems and reported this to TAC.
I was assured that once we had rebooted the WLC this would not be a problem as they would come alive with the 8.5 firmware.
Remember the reason for the upgrade was cisco bug ID CSCvd91152.
Once the WLC was rebooted 802.11k, 802.11v and PMF were all re-enabled. Cisco bug ID CSCvd91152 was still in effect, and the worse thing of all, we had nearly eight percent of our AP’s 'fried' for want of a better phrase.
The Bug is the Bug, I have faith that Cisco TAC will find a resolution.
My question to the forum is does anyone have a fool proof way of saving the AP’s during a firmware upgrade without having spares, very helpful helpdesk staff, and Facilities on hand to facilitate?
I have decided to turn off all WLAN’s and disable the A and B Networks on the WLC as a first port of call. And I’ve just read a post from Darren Stobbs that mentions a Wlanpoller tool which I’m just about to evaluate.
Thanks Darren, I wonder why TAC didn’t mention this tool prior to the upgrade advice?
Regards
Mak
Francis Crick Institute
########################################################################
To unsubscribe from the WIRELESS-ADMIN list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=WIRELESS-ADMIN&A=1
|
