config link-load-balance : config link-load-balance health-check
 
config link-load-balance health-check
Use this command to configure health checks.
Link health checks test routes to the specified destination. When the link health check option is enabled for a gateway link, the system periodically sends an ICMP ECHO probe (ping) to a beacon—an IP address that must be reachable in order for the link to be deemed available. A beacon can be any IP address, such as a main office, core router, or virtual server at another data center.
Before you begin:
• You must have knowledge of a destination IP address that can function as a beacon for the health check.
• You must have read-write permission for link load balancing settings.
After you have configured a health check, you can select it in the gateway link configuration.
Syntax
config link-load-balance health-check
edit <name>
set interval <integer>
set retry <integer>
set source-addr <class_ip>
set timeout <integer>
set type icmpv4
config check_member
edit <name>
set ip <class_ip>
set source-sddr <class_ip>
next
end
next
end
interval
The default is 5. The default is recommended in most cases.
retry
The default is 3. The default is recommended in most cases.
source-addr
Source IP address specified in the health check packet header.
You do not necessarily need to configure the source address of the health check or its individual probes unless you want it to differ from the network interface IP address, or differ from the source IP used by other probes in the health check.
The probe’s source IP address is configurable at multiple levels. The system uses the most specific source address that you configure for each probe:
• If a source IP address is configured for the health check member, the system uses that source address as the SRC field in the packet’s IP header.
• If source IP address for the health check member remains at its default value (0.0.0.0) but you have configured an health check group source IP address, the system uses that address.
• If both group and member settings are not configured (remaining at their default value of 0.0.0.0), the system uses the IP address of the network interface from which the packet is sent.
The default is 0.0.0.0.
timeout
The default is 3. The default is recommended in most cases.
type
Only ICMPv4 is supported.
config check_member
ip
You must specify a destination IP address.
When the link health check option is enabled within an active link group, the system periodically sends an ICMP ECHO probe (ping) to a beacon—an IP address that must be reachable in order for the link to be deemed available. A beacon can be any IP address, such as a main office, core router, or virtual server at another data center.
source-addr
Source IP address specified in the health check packet header.
You do not necessarily need to configure the source address of the health check or its individual probes unless you want it to differ from the network interface IP address, or differ from the source IP used by other probes in the health check.
The probe’s source IP address is configurable at multiple levels. The system uses the most specific source address that you configure for each probe:
• If a source IP address is configured for the health check member, the system uses that source address as the SRC field in the packet’s IP header.
• If source IP address for the health check member remains at its default value (0.0.0.0) but you have configured an health check group source IP address, the system uses that address.
• If both group and member settings are not configured (remaining at their default value of 0.0.0.0), the system uses the IP address of the network interface from which the packet is sent.
The default is 0.0.0.0.
Example
FortiADC-VM # config link-load-balance health-check
FortiADC-VM (health-check) # edit llb-hc-1
Add new entry 'llb-hc-1' for node 1801
 
FortiADC-VM (llb-hc-1) # get
type : icmpv4
interval : 5
retry : 3
timeout : 3
source-addr : 0.0.0.0
 
FortiADC-VM (llb-hc-1) # config check_member
FortiADC-VM (check_member) # edit 1
Add new entry '1' for node 1803
FortiADC-VM (1) # set ip 198.51.100.10
FortiADC-VM (1) # end
FortiADC-VM (llb-hc-1) # end