Wireless Access

Hello community, 

 

I've got a quick question, 

 

How often do you restart your controller? and your access points ?

 

After a lot of change, do you advise to do it?

 

Many thanks in advance.

 

+

Hi Michael,

 

I do it once a year, but I think it is recommended to do it a couple of times per year. It is also a good practice to check the resiliency :)

 

Regards

Borja

Thanks Borja for your answer.

 

me too, i think it's a good practice but I'm curious how often the community do it.

 

do you restart the controller and the AP ? or just the controller ?

 

Absolutely!

 

Only the controller. I only restart the AP's when I upgrade. 

 

 

Cheers

Borja

I recently logged on to a system that had been managed by another partner. The uptime of the controllers was roughly 2 years 1 month and nothing complained ;)

 

That said - unless you upgrade there shouldn't be a need to schedule a reboot of your controllers. If you have to do that - something is wrong - either in your design (ie. too high load) or the software version you're using has bugs.. 

 

I find it all depends on our customer, most of them are usually never over a year due to either planned maintenance or upgrades!

My personal lab controller is a different story, that gets rebooted almost every couple of days! :D

Hello Jsolb, 

 

Many thanks for your quick reply...

 

i'm going to upgrade the controller with the lastest version... i guess my version has some bugs because the ap reboot by itself ...

 

But it's a good thinks to get feedback !

 

The controller that you told to us, did he get a lot of change few weeks ago ?

 

my controller get a lot of changes ( number of channel changed, rates, etc... ) in order to improve the settings.... 

 

That why this question comes to my mind :)

 

have a good day

 

 

@zalion0

ahaha :) it's because you labbed a lot :)

When asked to do a healthcheck I start by checking software version and the dashboard to see status quo. Based on those findings I go through the config and document changes I want to do.

 

But - I always schedule upgrading/patching and do a new status quo before doing any major changes.

thanks is a very good things to do ! many thanks for your advice

 

here, on this setup i guess the "bug" version of the software cause ap tx restarting and cause clients disconnection...

 

i've got like some AP's with 240d of uptime and other 3h ... :/

 

I know that i need to upgrade the code... 

my question is most about the "routine maintenance"

you're are right !

 

i asked to do a Site Survey and to check all the swith port statut in case of duplex missmatch or fcs etc...

 

it's a whole audit of the infrastructure 

Have fun with that! I always enjoy going through a system and see how others do things. That is - when it's not in a critical troubleshooting scenario ;)

my guys like to do it as well :)

 

not a critical scenario... but critical application :)

 

thanks ! and yes it's nice or funny to try to get what the other did

Michael, 

 

What is your current version and the one your are planning to updagre that fixes the Ap reboots ?  for curiosity do you have a Bug number ?

 

We lost couple of lines on the config after saving the config and performing an upgrade from AOS 6.3.1.15 upgrading to .21

 

I'd advise to collect a backup before ( as I am sure you already planned to do ) and compare with the config after the upgrade to confirm everything is in place.

 

DSP

 

 

Hello, 

 

my code version is 6.4.2.13

 

did you have any feedback about upgrading from this version to the last one ?

 

have a good day.

 

++

Hello Michael-dc, 

 

 

Check Table 5: Known Issues in ArubaOS 6.4.2.18 RLN 

 

Nothing specific, if I am honest I haven't work with controllers on that specific versions. 

 

DSP

Thanks !

hello, 

 

first feedback after upgrading the controler to the lastest version : 6.5.1.4

 

everything seems to be fine except all my AP 275 won't come up after the upgrade...

 

Anyone get this issue ?

ok, thanks.

 

You recommanded to downgrade to 6.5.1.3 ?

the issue with the AP 275 on 6.5.1.3, the 6.5.1.4 should fix that, see the screenshot

my apologies you are correct the 6.5.1.4  fixed the issue with the 275s

Symptom: An AP failed to boot. The fix ensures that the AP boots successfully. Scenario: This issue occurred when an AP-275 access point was upgraded to ArubaOS 6.5.1.3.

 

what behavior are you currently experiencing with the AP275s ?

the AP's wont come up after the upgrade...

 

nothing more than "down" on the interface....

 

we are trying the " restart" the AP and probably reset them....

other idea ?

Do you have console access to the AP?

Run the following command on the controller :
Show log system all | include

yes we unmonted one of them...

 

but we are unable to get anything for the terminal ( we tested the cable before)

 

look like the AP is stuck....

You cant see the boot process ?

If the controller logs is not showing any errors related to the 275 not coming up or can't see any information when the AP is booting via the console i suggest you open a TAC case 

 

 

by resetting the AP it's works now....