AAA, NAC, Guest Access & BYOD

How do I perform a graceful reboot on an NAC appliance configured in High Availability or Hot Standby?
Product and Software: This article applies to all ECS product and software versions.

If at any point the need to reboot any of the NAC appliances in a High Availability configuration arises, a graceful reboot is mandatory. Improperly rebooting an appliance may cause the system to go into a fail-over state.

This solution describes the proper way to reboot NAC appliances that are set up in a High-Availability or Hot Standby configuration. Different procedures are followed based on which appliance needs to be rebooted.

Important: Do not power off your NAC appliance by pulling the plug or pressing the Power Off switch. This action could jeopardize the database on the NAC appliance. Performing a graceful reboot provides the safest way to reset the appliance and avoid corrupting the database.

In general, you will be rebooting the primary server(s) first, then wait for them to become fully functional before rebooting the secondary server(s).

Requirements
  • PuTTY or other ssh software
  • Admin or greater access privileges
Procedure #1 (Rebooting either of the primary NAC appliances)
1) Connect to the primary NAC Control Server or NAC Server appliance CLI using ssh.

2) Log in as admin.

3) Run the following command to shut down the NAC product and database:
shutdownCampusMgr
4) Wait 15-20 seconds.

5)  Connect to each (secondary) NAC Appliance's CLI using ssh  and view the current 'processManager' log file (example: 'ssh <hostname secondary>').

6) If you have a 1U appliance:
a. Type:
cd /bsc/logs/processManager
b. Type:
tail –f output.processManager.<most current file date>
If you have a 2U/4U appliance:
a. Type:
 cd /bsc/campusMgr
b. Type:
 tail –f output.masterProcess.<most current file date>
7) Verify that the secondary appliance is in Idle(true) mode. Look for the line of text that looks like this:
(Slave) Master In Control Idle(true)
If you find that the secondary NAC appliance is not in Idle mode, go back to the primary NAC Control Server and reissue the command:
shutdownCampusMgr
8) Once Idle mode has been verified, continue.

Do the following step if you have a NAC Application Server; otherwise, skip the next step.

9) In a console window, connected to the primary NAC application server and run one of the following commands to reboot:
sudo reboot
or
sudo init 6
10) In a console window, connect to the primary NAC Control Server of the NAC Server and  run one of the following commands to reboot:
sudo reboot
or
sudo init 6
11) Verify proper operation of the primary servers before moving on to reboot the secondary servers.

Procedure #2 (Rebooting Either of the Secondary NAC Appliances)

1) Verify proper operation of the primary servers before moving on to reboot the secondary servers.

2) Connect to the secondary  NAC Control Server or NAC Server appliance that is to be rebooted using ssh.

3) Run one of the following commands to reboot:
sudo reboot
or
sudo init 6
4) Repeat the process for each secondary NAC appliance that needs rebooting.

Validation
1) Access the NAC GUI and log in.

2) Access different functions to verify that the device is working correctly.

3) Visit the Events page to review if any errors have been encountered upon reboot.

 

Version History
Revision #:
1 of 1
Last update:
‎06-30-2014 05:52 PM
Updated by:
 
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.