Monitor your ping / connection statistics to ensure everything looks fine. Press “Y” to confirm and reboot the slave. Enter the following command to reboot the slave: execute rebootġ0. You should notice your command line change to reflect the name of the newly selected HA member.ĩ. This will change your management console to this particular firewall unit. Where “x” is the number noted down in step number 7. Next enter the following command: execute ha manage x In the above example the Slave unit has the number “0”. Look for the number right at the end and note this down. This will show which firewall is master and slave in the cluster e.g. Type the following command to bring up your HA cluster details: get system ha statusħ. (Optionally, you could also just SSH in if you have this enabled).Ħ. Click in the “CLI Console” black window area to get to your console. Return to the “Status” home page of your firewall GUI. Click “View HA statistics” near the top right if you would like to view each unit’s CPU/Memory usage and other statistics.ĥ. This step is optional and just gives you a nice overview of how things are looking at the moment. This will give you an overview of your HA cluster – you can view which unit is the Master and which is the slave. It should show as “Active-passive” if this is the mode your HA cluster is in. For details, see the FortiWeb CLI Reference. If you want to adjust the behavior of execute ping, first use the execute ping options command. Login and look for “HA status” under the status area – this should be the default page that loads. Log in to the CLI via either SSH, Telnet, or You can ping from the FortiWeb appliance in the CLI Console widget of the web UI. Specify a custom port number if you have the management GUI on a custom port for example 3. Start by logging in to the web interface of your firewall cluster.
When the slave restarts you can watch your ping statistics or other connections just to ensure everything stays up whilst it reboots.ġ. The slave is merely there to take over should things go pear shaped on the master unit. Restarting the slave unit should not have any effect on these connections in theory as your master unit is the one handling all the work. I have only tested this on a cluster of FG60 units, but am quite sure the steps would be similar for a cluster of FG100s, FG310s etc…įirst of all you may or may not want to set up some monitoring going to your various WAN connections on the HA cluster. Here’s a quick how-to on restarting a specific member of a High Availability FortiGate hardware firewall cluster.
0 kommentar(er)
