Wireless Access

Reply
Contributor II
Posts: 73
Registered: ‎03-07-2011

25+ RAPs fail to register after unexpected reboot controller

On of our controllers reboot due to a power failure, as a result 25+ RAPs fail to connect. The following error message is in the log:

 

Apr 28 15:37:17 sapd[822]: <311020> <ERRS> |AP GDF-RAP37-G16B@192.168.114.122 sapd| An internal system error has occurred at file sapd_msg.c function sapd_hello_cb line 6529 error Unexpected result code (null).
Apr 28 15:37:17 sapd[822]: <311020> <ERRS> |AP GDF-RAP37-G16B@192.168.114.122 sapd| An internal system error has occurred at file sapd_msg.c function sapd_hello_cb line 6529 error Unexpected result code (null).

 

We run a 3600XM with the latest software;

Aruba Operating System Software.
ArubaOS (MODEL: Aruba3600), Version 6.4.3.7

 

Some suggestions about how to troubleshoot would be much appreciated.

Guru Elite
Posts: 21,512
Registered: ‎03-29-2007

Re: 25+ RAPs fail to register after unexpected reboot controller

I would open a TAC case, because they would probably need much more information than that to find out what is happening.



Colin Joseph
Aruba Customer Engineering

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

Contributor II
Posts: 73
Registered: ‎03-07-2011

Re: 25+ RAPs fail to register after unexpected reboot controller

I created a TAC case but unfortunately our contact ended a few weeks ago, and the order for the new contact is somewhere in the process of being accepted and processed. I hope they will accept this and give support anyway, we will see.

 

 

Contributor II
Posts: 73
Registered: ‎03-07-2011

Re: 25+ RAPs fail to register after unexpected reboot controller

[ Edited ]

I am troubeshooting this myself, untill I can get a hold on a valid contract.

 

I see rather strange behaviour, the RAPs don't connect with the controller. Somehow the RAP nats all traffic to his WAN ip and drops it on our LAN. Is this by design? I have not noticed this before.

 

PS we use RAPs on our LAN to tunnel guest and contractor traffic on production sites.

MVP
Posts: 428
Registered: ‎07-26-2011

Re: 25+ RAPs fail to register after unexpected reboot controller

Any chance you can provide some further information which might help us diagnose the issue? If you run the following via the CLI

 

#show ap database long

- Is there any flags next to the RAP's? 

 

#show datapath session | include xxxxx 

- Where XXXX is the outer IP of the RAP.

 

#show log all | include xxxx

- Where XXXX is the name of a RAP

 

#show control-plane-security 

- Is control plane security enabled?

ACMA, ACMP
If my post addresses your query, give kudos:)
Contributor II
Posts: 73
Registered: ‎03-07-2011

Re: 25+ RAPs fail to register after unexpected reboot controller

Thank you for your reply.

 

I found this in the logs

Apr 29 10:06:35  stm[1953]: <305059> <WARN> |stm|  Version 6.4.3.7 is not compatible with AP GDF-RAP37-G16B with type RAP-5WN, mac 00:0b:86:69:54:c2

 

Seems like the software version on the controller is not compatible with the RAPs.

I guess I will have to figure out to update the software running on the RAPs.

MVP
Posts: 428
Registered: ‎07-26-2011

Re: 25+ RAPs fail to register after unexpected reboot controller

The latest supported OS for a RAP5-WN is ArubaOS 6.3, so the code you are running isn't supported.

 
You can see this from the EOL doc below : 

 

http://www.arubanetworks.com/support-services/end-of-life/

 

Is it possible one of the image paritions has been upgraded on the controller but not activated? When the controller rebooted it may have booted into the parition with the later firmware? You can check this with

 

#show image version

- Will display the software versions running on each parition

 

# boot system partition X

- Will inform the controller to boot into partition X (as seen in the above command) on the next reboot.

 

ACMA, ACMP
If my post addresses your query, give kudos:)
Contributor II
Posts: 73
Registered: ‎03-07-2011

Re: 25+ RAPs fail to register after unexpected reboot controller

That should be it! I will downgrade to the latest 6.3 release.

Thanks for your insight :)

 

(DHARUBA02) #show image version
----------------------------------
Partition : 0:0 (/dev/hda1)
Software Version : ArubaOS 6.3.1.21 (Digitally Signed - Production Build)
Build number : 54002
Label : 54002
Built on : Mon Feb 29 00:04:58 PST 2016
----------------------------------
Partition : 0:1 (/dev/hda2) **Default boot**
Software Version : ArubaOS 6.4.3.7 (Digitally Signed - Production Build)
Build number : 53990
Label : 53990
Built on : Sat Feb 27 13:11:21 PST 2016

 

 

MVP
Posts: 428
Registered: ‎07-26-2011

Re: 25+ RAPs fail to register after unexpected reboot controller

Great stuff, glad to hear it :D

ACMA, ACMP
If my post addresses your query, give kudos:)
Contributor II
Posts: 73
Registered: ‎03-07-2011

Re: 25+ RAPs fail to register after unexpected reboot controller

Pretty sloppy of me tbh, I was convinced the RAPs were already working on a prior 6.4 release.

 

Thanks again!

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