Stopping and Restarting Processes

What Happens When Processes are Stopped

When the shutdownNAC command is run on the appliance in control, the following occurs:

• If Primary Server(s) are in control, the management process sets the secondary state to “Idle.” This prevents a failover from occurring.

• The loaders are stopped on the appliance in control.

• FortiNAC does not switch VLANs, serve Captive Portal pages or respond to RADIUS requests.

• In L2 HA configurations, the Virtual IP address stops responding.

• Primary and Secondary Server eth0 IP addresses are still reachable via normal means (e.g. ICMP, SSH, etc).

The shutdownNAC -kill command stops the Management Process on the appliance the command is run from.

Important: Running shutdownNAC -kill on the primary without running shutdownNAC first will cause a failover.

Restart Processes without Causing Failover

Used for routine maintenance and quick restart.

Important: For L2 HA configurations, do not use the Virtual IP for connecting to CLI.

1. 1. SSH as root to the Primary Server and type

   execute enter-shell

   shutdownNAC 

2. Type

   jps 

   (use the jps command until you no longer see any "Yams" process running; this could take 10 - 30 seconds)

3. Start back up the loaders. Type

   startupNAC 

   Note: The startup could take 5-10 minutes to complete. Please wait at least 10 minutes before attempting to access the Administrative UI.

Stopping All Processes

Stop processes in order to:

• Restart management processes

• Reboot or power down appliances

Important: For L2 HA configurations, do not use the Virtual IP for connecting to CLI.

1. SSH as root to the Primary Server and type

   shutdownNAC

2. Type

   jps

   (use the jps command until you no longer see any "Yams" process running; this could take 10 - 30

   seconds)

3. Type

   shutdownNAC -kill

4. SSH as root to the Secondary Server and type

   shutdownNAC -kill

Option 1: Restart Management Processes

1. In the Primary Server CLI type

   startupNAC

2. Wait until the Primary Server is up and running (by confirming you have Administration UI access).

   Note: The startup could take 5-10 minutes to complete. Please wait at least 10 minutes before attempting to access the Administrative UI.

3. Once the Primary Server is running, in the Secondary Server CLI type

   startupNAC

Note: The Administration UI will display “Processes are Down” unless the appliance is in control.

Option 2: Reboot Appliances

1. In the Primary Server CLI type

   reboot

2. Wait until the Primary Server is up and running (by confirming you have SSH access and Administration UI access).

   Note: The startup could take 5-10 minutes to complete. Please wait at least 10 minutes before attempting to access the Administration UI.

3. Once the Primary Server is running, in the Secondary Server CLI type

   reboot

Option 3: Power Down Appliances

1. Shut down and halt the system. In both the Primary and Secondary Server CLIs type

   shutdown -h now

2. Power down the appliance.

   • Virtual machines: select the server from the list and click the Power Off button. This process may take 30 seconds.

   • Physical appliances: push the power button.