Wireless Access

after upgrading the os to 6.3.1.3 my 105 AP dose not flash SSID. My controller is 3600. My 135 AP's get SSID flashed. please help me

DId you see PAPI traffic to the AP105, flash the AP (Purge, sve, boot)?

the ap's are in down status list

Are your APs (105 and 135) installed at different patches? If yes did you provision them the same way?

Hi is there any update on this? I seem to be experiencing the same issue, we tried to upgrade to 6.3.1.3, after the controller went up our AP-105's just keeps on rebooting and won't come up. below is the logs for the "show ap image version ap-name <ap>"

AP Image Versions On
Controller
-------------------------------

6.3.1.3(p4build@port-royal)#42233 Tue Feb 11 11:29:58 PST 2014

Access Points Image Version

---------------------------

AP          
Running Image Version
String                               
Flash (Production) Image Version
String                    
Flash (Provisioning/Backup) Image Version String  Matches  Num
Matches  Num Mismatches  Bad Checksums  Bad Provisioning
Checksums  Image Load Status
--           ----------------------------                                ---------------------------------------                     ------------------------------------------------  -------  -----------  --------------  -------------  --------------------------  -----------------

10.27.0.242  6.0.1.3(p4build@cyprus)#28554 Tue May 31 12:37:22 PDT
2011  6.0.1.3(p4build@cyprus)#28554 Tue May 31 12:37:22 PDT
2011                                                   
No      
0           
1              
0             
0 

When we rebooted the controller back to the old version (6.0.1.3) the AP's went up automatically with no issues.

My question is is there an issue with ap-105 on this version?

Thank you.

Try typing "show log system 50" to see if there are any clues about this...

thanks cjoseph. will the logs when i booted to 6.3.1.3 stay when I do show log system all? If not i will have to schedule another maintenance downtime for it? anyway i will have to upgrade to 6.3.1.5 for the SSL thing.

i however remember that I managed to download the tar.logs, will post what i see later, it is with my customer.

Hi cjoseph,

I manage to pull out the system logs from the tar logs, see below:

Apr 11 21:41:00  nanny[764]: <303022> <WARN> |AP AP-L07-04@10.27.0.226 nanny|  Reboot Reason: AP rebooted Fri Dec 31 16:05:13 PST 1999: SAPD: Unable to contact switch. Called by sapd_ap_flashing_cb:3824

Apr 11 21:41:02  nanny[766]: <303022> <WARN> |AP AP-L11-03@10.27.0.237 nanny|  Reboot Reason: AP rebooted Fri Dec 31 16:04:26 PST 1999: SAPD: Unable to contact switch. Called by sapd_ap_flashing_cb:3824

Apr 11 21:41:44  nanny[538]: <303022> <WARN> |AP AP-L09-02@10.27.0.232 nanny|  Reboot Reason: AP rebooted Fri Dec 31 16:04:45 PST 1999: SAPD: Unable to contact switch. Called by sapd_ap_flashing_cb:3824

Apr 11 21:41:48  nanny[764]: <303022> <WARN> |AP AP-L11-04@10.27.0.217 nanny|  Reboot Reason: AP rebooted Fri Dec 31 16:04:47 PST 1999: SAPD: Unable to contact switch. Called by sapd_ap_flashing_cb:3824

Apr 11 21:41:56  nanny[764]: <303086> <ERRS> |AP AP-L11-05@10.27.0.239 nanny| Process Manager (nanny) shutting down - AP will reboot!

I just wonder why the AP's can't contact the controller in this version, but they can when we booted to 6.0.1.3.

 I also got some logs from the errorlog if it's relevant at all:

Apr 11 22:08:27  stm[1960]: PAPI RxPacket: Too small a packet of size 70 received.
Apr 11 22:08:27  stm[1960]: PAPI RxPacket: Should be >= 76
Apr 11 22:08:27  webui: LargeReplyTimeout: TIMEOUT
Apr 11 22:08:27  webui: PAPI_SendWaitForLargeReply: No response from 7f000001:8419

Anyway I will try out 6.3.1.5 and hopefully it works. But I hope there is an answer with what happened when we installed 6.3.1.3, as the customer is looking for answers.

Thank you.

Hi Richard

Apr 11 22:08:27  stm[1960]: PAPI RxPacket: Too small a packet of size 70 received.
Apr 11 22:08:27  stm[1960]: PAPI RxPacket: Should be >= 76
Apr 11 22:08:27  webui: LargeReplyTimeout: TIMEOUT
Apr 11 22:08:27  webui: PAPI_SendWaitForLargeReply: No response from 7f000001:8419

this is quite possibly due to a known bug with Airwave AMON vs. 6.3.1.3, it shouldnt be related to the AP issue.
Can you send me an email with the logs and customer name, i will add this part to the known bug

for the above error.

regards

-jeff

Richard,

My mistake in the last post since there is no airwave involved per your email. After reviewing the logs you forwarded, yes the log message like this:

Apr 11 22:00:45  stm[1960]: PAPI RxPacket: Too small a packet of size 69 received.
Apr 11 22:00:45  stm[1960]: PAPI RxPacket: Should be >= 76

is directly related to the system log you posted:

Apr 11 21:40:56  nanny[764]: <303022> <WARN> |AP AP-L10-03@10.27.0.221 nanny|  Reboot Reason: AP rebooted Fri Dec 31 16:04:19 PST 1999: SAPD: Unable to contact switch. Called by sapd_ap_flashing_cb:3824

the reason for this issue is as follows:

1. there was a bug fix done to add some additional bounds checking on PAPI messages being received by the controller
2. The additional checking missed a certain set of messages related to older software
3. As such, the controller drops these older messages as being "too small" - this happens for AP Flash and also AMON from Airwave as noted
4. The problem was introduced in 6.3.1.3, and fixed in 6.3.1.4

There are a few options to resolve/workaround

1. upgrade controller to 6.3.1.2, then after APs up, upgrade to 6.3.1.3
2. upgrade direct to 6.3.1.5
3. clear the os image on all APs and let them get 6.3.1.3 direct from the controller (not a good option but would resolve)

hope that clarifies, if you need exact bug numbers send me an email

regards

-jeff

Hi Jeff,

I'll take option #2. I will update this thread once succesful. Thank you.