Fortinet black logo
7.2.0

Monitoring server communication

Monitoring server communication

The Secondary Server polls the status of the Primary Server every 30 seconds to determine whether the primary is still in control. If the secondary does not receive a response from a poll, it will re-attempt to communicate 5 additional times (every 30 seconds) by default.

The messaging in the output.processManager is similar to the entries below, where “Ping retval = null” indicates the Primary Server did not respond to the poll.

sendPacket() <Primary Server IP> verb Ping retval = Running - In Control
sendPacket() <Primary Server IP> verb Ping retval = Running - In Control
sendPacket() <Primary Server IP> verb Ping retval = Running - In Control
sendPacket() <Primary Server IP> verb Ping retval = null
**** Failed to talk to Primary **** PingRetryCnt = 1 pingRetries = 5
**** Failed to talk to Primary **** PingRetryCnt = 2 pingRetries = 5
**** Failed to talk to Primary **** PingRetryCnt = 3 pingRetries = 5
**** Failed to talk to Primary **** PingRetryCnt = 4 pingRetries = 5
**** Failed to talk to Primary **** PingRetryCnt = 5 pingRetries = 5
**** Failed to talk to Primary **** PingRetryCnt exceeded!

If the secondary does not receive a response, the secondary pings the “Secondary Appliance Gateway IP Address” configured in the High Availability Tab. See section Primary And Secondary Server Configuration.

  • If the gateway is reachable, the secondary takes control, since the primary is assumed to be isolated from the network. If, however, the Secondary Server’s Management Process has been running for less than 10 minutes, the secondary waits 10 minutes for any further communication from the primary. If still no response, the secondary takes control.

  • If the gateway is not reachable, the secondary will not take control since the secondary is assumed to be isolated from the network and the primary could be functioning properly.

Important: If the secondary is Idle, it does not take control. For example, the secondary can be set to Idle when Reboot and Shutdown commands are run on the primary.

The number of ping retries can be modified from the default of 5 attempts. For details, see Modify Ping Retry Count in the Appendix.

Monitoring server communication

The Secondary Server polls the status of the Primary Server every 30 seconds to determine whether the primary is still in control. If the secondary does not receive a response from a poll, it will re-attempt to communicate 5 additional times (every 30 seconds) by default.

The messaging in the output.processManager is similar to the entries below, where “Ping retval = null” indicates the Primary Server did not respond to the poll.

sendPacket() <Primary Server IP> verb Ping retval = Running - In Control
sendPacket() <Primary Server IP> verb Ping retval = Running - In Control
sendPacket() <Primary Server IP> verb Ping retval = Running - In Control
sendPacket() <Primary Server IP> verb Ping retval = null
**** Failed to talk to Primary **** PingRetryCnt = 1 pingRetries = 5
**** Failed to talk to Primary **** PingRetryCnt = 2 pingRetries = 5
**** Failed to talk to Primary **** PingRetryCnt = 3 pingRetries = 5
**** Failed to talk to Primary **** PingRetryCnt = 4 pingRetries = 5
**** Failed to talk to Primary **** PingRetryCnt = 5 pingRetries = 5
**** Failed to talk to Primary **** PingRetryCnt exceeded!

If the secondary does not receive a response, the secondary pings the “Secondary Appliance Gateway IP Address” configured in the High Availability Tab. See section Primary And Secondary Server Configuration.

  • If the gateway is reachable, the secondary takes control, since the primary is assumed to be isolated from the network. If, however, the Secondary Server’s Management Process has been running for less than 10 minutes, the secondary waits 10 minutes for any further communication from the primary. If still no response, the secondary takes control.

  • If the gateway is not reachable, the secondary will not take control since the secondary is assumed to be isolated from the network and the primary could be functioning properly.

Important: If the secondary is Idle, it does not take control. For example, the secondary can be set to Idle when Reboot and Shutdown commands are run on the primary.

The number of ping retries can be modified from the default of 5 attempts. For details, see Modify Ping Retry Count in the Appendix.