04-02-2014 06:18 AM - last edited on 05-13-2014 09:04 AM by /chiefAirhead/
How to restart processes on an Aruba controller
Here is a list of commands that we will use and what we can look for:
- “show processes” – if you used linux then you will love the output. Please check the other parameters of the command in order to see the process that uses more CPU or Memory.
- PROCESS STATE CODES
- R running or runnable (on run queue)
- D incorruptible sleep (usually IO)
- S interruptible sleep (waiting for an event to complete)
- Z defunct/zombie, terminated but not reaped by its parent
- T stopped, either by a job control signal or because it is being traced
- “show process monitor statistics” – will display a list of current processes running under watchdog.
- “process restart <process name>” – will restart the process and in order to see if it has re-initialized you would need to use one of the previous commands.
I would recommend to have an Aruba support engineer with you on the phone when doing this on production and only if the engineer requests you to do so.
04-07-2014 07:13 AM - edited 04-07-2014 07:17 AM
Thank you for that information.
Under what circumstances would a user want to or need to restart a process?
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
04-07-2014 07:55 AM - edited 04-07-2014 07:56 AM
For example now in my company we use it in order to clear the station table - because the "aaa user delete all" would not do it properly and we get to max out our user license on the controllers.
We are working with Aruba support to get the issue fixed but in order for us not to restart the controller we restart the "auth" process and that clears the station-table.
04-07-2014 07:56 PM
Some additional thoughts for your document
- If you restart a process without the "core" CLI flag, it is unlikely any root cause can ever be found
- Using the core flag will increase the time it takes to recover the process (as core has to be dumped and compressed etc)
- Many processes (stm, auth), if restarted, will cause all clients to be disassociated
- During process restart related CLI commands will be unavilable (i.e. if you restart stm, show ap <> will become unavailable)
- If you restart a process with core flag that has high CPU, it may not provide sufficient info - you should request TAC to "strace" the process before someone restarts it.
I definitely concur with the comment "I would recommend to have an Aruba support engineer with you on the phone when doing this on production and only if the engineer requests you to do so." as restarting processes randomly is likely to cause some sort of outage.