Wireless Access

This problem popped up on several controllers that were deployed last week.

620 controller, running 5.0.3.3

AP93

The following shows up in the log on the local controllers:

Aug 27 12:39:39 :399803:  <ERRS> |AP d8:c7:c8:cf:63:46@10.1.14.109 sapd|  An internal system error has occurred at file sapd_cfg.c function sapd_read_cached_info line 483 error apfc_read failed: Cache uninitialized.
Aug 27 12:39:39 :303022:  <WARN> |AP d8:c7:c8:cf:63:46@10.1.14.109 nanny|  Reboot Reason: No reboot message found.

These are new APs and I'm beginning to think there is something wrong with this batch.  All of the affected APs have a MAC that starts with "d8:c7:c8:cf"  

Is there a way to make sure these are AP93 with the 802.11b/g/n radio and not 802.11a/n?

I currently have 5 controllers/APs deployed that will not provision and not sure where else to start looking.

AP90s require the following minimum code rev on the controllers:

ArubaOS 5.0.4.2, 6.0.2.1, 6.1.2.0

-Mike

Is this new?  I've been using AP93s with 5.0.2.0 and 5.0.3.3 for almost 2 years.

I'm not having a problem with the other 310 AP93s that I have deployed on my network......just these 5 from the latest batch.  They all have a manufacturer date of 3/18/12.

I also have another batch from 3/11/11 that may also be giving me problems.....edit:  these appear to work fine.

Looks like the other AP93s deployed on my network were manufactured on 8/18/10.

Please contact support so that they can provide clarity to your specific situation.

Thanks, but I'm not sure I have the required time to devote to a support call - plus I'm not on-site with controllers/APs that are having the issue.

However, I think mnarine might be on to something.  The AP-92 & 93 product page does say:

Minimum AOS Version

5.0.4.2, 6.0.2.1, 6.1.2.0

The APs from 2011 don't seem to be an issue, so I may just be able to swap out those 5 newer APs and be okay for a while. 

An upgrade to 6.x has been discussed for quite some time and this may be the issue to helps move it up the project list.

Not that it matters, but here is the result of "show log system 50":

Aug 27 18:49:27 :399803:  <ERRS> |AP d8:c7:c8:cf:64:52@10.1.17.105 sapd|  An internal system error has occurred at file sapd_msg.c function sapd_mesh_erase_domain_prof line 1776 error apfc_read failed: Cache uninitialized.
Aug 27 18:49:28 :311002:  <WARN> |AP d8:c7:c8:cf:64:52@10.1.17.105 sapd|  Rebooting: SAPD: Rebooting after provisioning
Aug 27 18:49:28 :303086:  <ERRS> |AP d8:c7:c8:cf:64:52@10.1.17.105 nanny| Process Manager (nanny) shutting down - AP will reboot!
Aug 27 18:50:30 :399803:  <ERRS> |AP d8:c7:c8:cf:64:52@10.1.17.105 sapd|  An internal system error has occurred at file sapd_cfg.c function sapd_read_cached_info line 483 error apfc_read failed: Cache uninitialized.
Aug 27 18:50:30 :303022:  <WARN> |AP d8:c7:c8:cf:64:52@10.1.17.105 nanny|  Reboot Reason: No reboot message found.

COLE1

- A bird just told me:

The newer AP9x with increased memory is probably the one you have.  It is supported from 5.0.4.2 and forwards.  You can substitute like you mentioned or upgrade to 5.0.4.2 to support those new APs.

Thank you.....and mnarine!   

All of those deployments were done last week while I was on vacation, so I came back to some worry and confusion.