Wireless Access

Reply
Occasional Contributor II
Posts: 23
Registered: ‎06-16-2014

AP 224 not able to join the controller 6000 which has 6.4.2.5 version

Hi Experts ,

I have issue with getting AP 224 registered to controller 6000

 

I am getting below error :

 

<WARN> |AP @nanny|  Reboot Reason: AP rebooted SAPD: Reboot after image upgrade failed: 65280

when I gone through multiple cases in the same forum , I could see that , it was the issue with firmware limitation where AP220 would need 6.4 version .

Though we have 6.4.2.5 , we are getting same error in controller.

 

Can you please suggest me on this ?

 

Thanks

 

Valued Contributor II
Posts: 804
Registered: ‎12-01-2014

Re: AP 224 not able to join the controller 6000 which has 6.4.2.5 version

Hi ,

How about other APs terminating on the same 6000 Controller ? or this is the first AP you are trying to terminate ?

 

Please feel free for any further help on this.

 

Cheers,
Venu Puduchery,
[Is my post helped you ? Give Kudos :) ]
Occasional Contributor II
Posts: 23
Registered: ‎06-16-2014

Re: AP 224 not able to join the controller 6000 which has 6.4.2.5 version

Hi ,

 

Thanks for your reply...

 

I have nearly 160 AP's which are already registered . those models are 104 & 105 .

 

I am struggling only with AP224.

 

Occasional Contributor II
Posts: 23
Registered: ‎06-16-2014

Re: AP 224 not able to join the controller 6000 which has 6.4.2.5 version

Hi Experts ,

 

Can anybody suggest me on this please ??

 

Thanks in advance

Guru Elite
Posts: 20,761
Registered: ‎03-29-2007

Re: AP 224 not able to join the controller 6000 which has 6.4.2.5 version

You should type "show log system 50" on the command line of the controller to see if there are any clues as to why it is not booting up. You should also plug a console cable into the access point and see if that also can give you a clue why your problem is happening.

Ap224s will not broadcast until you provision them with antenna gains after it contains ts the controller.


Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II
Posts: 23
Registered: ‎06-16-2014

Re: AP 224 not able to join the controller 6000 which has 6.4.2.5 version

Hi Colin,

 

Thanks for your reply.

AP is not coming  in AP installation page to provision with Antenna gain . Do I need to provision the AP by taking console ? I mean is there any option to configure Antenna gain by taking console ?

 

I am getting multiple message  for AP 224 as below :

Jun 27 10:29:55  nanny[1658]: <303022> <WARN> |AP 94:b4:0f:c9:02:3a@x.x.x.x nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:01:11 PST 1969; SAPD: Reboot after image upgrade failed: 65280
Jun 27 10:31:13  nanny[1658]: <303022> <WARN> |AP 94:b4:0f:c9:02:3a@x.x.x.x nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:00:49 PST 1969; SAPD: Reboot after image upgrade failed: 65280
Jun 27 10:46:57  nanny[1681]: <303022> <WARN> |AP 94:b4:0f:c9:02:3a@x.x.x.x nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:00:49 PST 1969; SAPD: Reboot after image upgrade failed: 65280
Jun 27 10:48:14  nanny[1658]: <303022> <WARN> |AP 94:b4:0f:c9:02:3a@x.x.x.x nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:00:50 PST 1969; SAPD: Reboot after image upgrade failed: 65280
Jun 27 10:49:32  nanny[1681]: <303022> <WARN> |AP 94:b4:0f:c9:02:3a@x.x.x.x nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:00:49 PST 1969; SAPD: Reboot after image upgrade failed: 65280
Jun 27 10:50:51  nanny[1681]: <303022> <WARN> |AP 94:b4:0f:c9:02:3a@x.x.x.x nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:00:50 PST 1969; SAPD: Reboot after image upgrade failed: 65280
Jun 27 10:52:09  nanny[1681]: <303022> <WARN> |AP 94:b4:0f:c9:02:3a@x.x.x.x nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:00:50 PST 1969; SAPD: Reboot after image upgrade failed: 65280
Jun 27 10:53:28  nanny[1681]: <303022> <WARN> |AP 94:b4:0f:c9:02:3a@x.x.x.x nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:00:50 PST 1969; SAPD: Reboot after image upgrade failed: 65280
Jun 27 10:54:46  nanny[1681]: <303022> <WARN> |AP 94:b4:0f:c9:02:3a@x.x.x.x nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:00:50 PST 1969; SAPD: Reboot after image upgrade failed: 65280
Jun 27 10:56:26  nanny[2171]: <303022> <WARN> |AP 94:b4:0f:c9:02:3a@x.x.x.x nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:00:50 PST 1969; SAPD: Reboot after image upgrade failed: 65280
Jun 27 10:58:05  nanny[2148]: <303022> <WARN> |AP 94:b4:0f:c9:02:3a@x.x.x.x nanny|  Reboot Reason: AP rebooted Wed Dec 31 16:01:12 PST 1969; SAPD: Reboot after image upgrade failed: 65280

 

****************************************

show log system output is as below :

Jun 27 09:34:31  KERNEL(AP_AP11-1_D1@x.x.x.121): RESTARTING ALL TX
Jun 27 09:38:21  KERNEL(AP_AP1-2_9D@x.x.x.31): RESTARTING ALL TX
Jun 27 09:38:49  KERNEL(AP_AP9-2_CD@x.x.x.131): RESTARTING ALL TX
Jun 27 09:41:06  KERNEL(AP_AP13-6_52@x.x.x.120): RESTARTING ALL TX
Jun 27 09:42:28  KERNEL(AP_AP14-7_BA@x.x.x.141): RESTARTING ALL TX
Jun 27 09:43:52  KERNEL(AP_AP9-22_d9af@x.x.x.199): RESTARTING ALL TX
Jun 27 09:45:15  KERNEL(AP_AP2-5_61@x.x.x.43): RESTARTING ALL TX
Jun 27 09:45:55  KERNEL(AP_AP1-7_A1@x.x.x.35): RESTARTING ALL TX
Jun 27 09:47:00  KERNEL(AP_AP14-9_E288@x.x.x.135): RESTARTING ALL TX
Jun 27 09:48:51  KERNEL(AP_AP9-2_CD@x.x.x.131): RESTARTING ALL TX
Jun 27 09:50:18  KERNEL(AP_AP1-7_A1@x.x.x.35): RESTARTING ALL TX
Jun 27 09:50:19  KERNEL(AP_AP13-6_52@x.x.x.120): RESTARTING ALL TX
Jun 27 09:52:17  KERNEL(AP_AP8-6_67@x.x.x.80): RESTARTING ALL TX
Jun 27 09:54:15  KERNEL(AP_AP11-1_D1@x.x.x.121): RESTARTING ALL TX
Jun 27 09:56:19  KERNEL(AP_AP5-8_EA0C@x.x.x.54): RESTARTING ALL TX
Jun 27 09:57:17  KERNEL(AP_AP1-12_50@x.x.x.39): RESTARTING ALL TX
Jun 27 09:59:56  KERNEL(AP_AP14-7_BA@x.x.x.141): RESTARTING ALL TX
Jun 27 10:01:45  KERNEL(AP_AP8-3_6A@x.x.x.78): RESTARTING ALL TX
Jun 27 10:01:51  KERNEL(AP_AP9-22_d9af@x.x.x.199): RESTARTING ALL TX
Jun 27 10:02:36  KERNEL(AP_AP1-12_50@x.x.x.39): RESTARTING ALL TX
Jun 27 10:06:14  KERNEL(AP_AP9-22_d9af@x.x.x.199): RESTARTING ALL TX
Jun 27 10:06:44  KERNEL(AP_AP14-7_BA@x.x.x.141): RESTARTING ALL TX

 

 

 

 

Guru Elite
Posts: 20,761
Registered: ‎03-29-2007

Re: AP 224 not able to join the controller 6000 which has 6.4.2.5 version

You should try resetting the AP by using the button on the back:

 

- power down the AP

- hold a paper clip in the hole on the back of the AP, pressing the button

- Power up the AP

- after 15 seconds release the paper clip and allow the AP to come up.

IMG_20150627_101005.jpg



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Occasional Contributor II
Posts: 23
Registered: ‎06-16-2014

Re: AP 224 not able to join the controller 6000 which has 6.4.2.5 version

Hi Team,

 

we have been working with TAC for almost 2 weeks , unfortunately there is no solution yet for this issue.

 

partially there is a success , meaning we could AP registered to default group where we do not have any VAP configured however when we provision those AP's , it goes into DOWN state and never comes up.

 

so only the the respective AP-group where AP should get provisioned , AP224 is not working with. TAC understanding is profile is corrupted however he tried to remove some VAP in that group but still no luck.

 

We tried disabling HT-profile on respective VAP's where AP should get provisioned however no luck. Afterword , there was one more observation that , we have static WEP which is been configured on one of our SSID and thats limitation since this devices are old and do not support for WPA and WPA2 with AES , AP224 is not getting registered due to this as well.

 

more confusion is , other AP's 104 & 105 is working fine in this ap-group , only AP224 is not working with this ap-profile.

 

did anybody come across this kind of issue ?

 

 

Frequent Contributor II
Posts: 109
Registered: ‎11-11-2008

Re: AP 224 not able to join the controller 6000 which has 6.4.2.5 version

Hi

 

I have myself seen strange things happen to controllers in my lab running 6.4.2.4 and 6.4.2.5.

VLAN's not working, DHCP no working and a bunch of other strange things.

Running 6.4.2.5, i could add several DHCP scopes, just to find out that the scope that was present when upgrading to 6.4.2.5 was the one working.

As soon as downgraded and upgraded beyond 6.4.2.5 i got it to work again.

I ended up switch back to the version in the other bank on the controller, only to upgrade to 6.4.2.7 or 6.4.2.8.

I'm not sure if this is an issue, but i have seen problems with 6.4.2.5 on 2 controllers in my lab, so i try to avoid 6.4.2.5.

 

Roar Fossen

Guru Elite
Posts: 20,761
Registered: ‎03-29-2007

Re: AP 224 not able to join the controller 6000 which has 6.4.2.5 version

[ Edited ]

Mosher,

 

If you see strange things please report them so they can be replicated and fixed.

 

There are  people new to Aruba who struggle because they are not familiar with the technology.  For the people who are experienced we need them to open a Tac case when they see issues so it is fixed for everyone.

 



Colin Joseph
Aruba Customer Engineering

Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base

Search Airheads
Showing results for 
Search instead for 
Did you mean: