NSE4_FGT-6.4 · Question #45
Which two statements are correct regarding FortiGate HA cluster virtual IP addresses? (Choose two.)
The correct answer is B. A change in the virtual IP address happens when a FortiGate device joins or leaves the cluster. C. Virtual IP addresses are used to distinguish between cluster members. HA heartbeat interface IP addresses The FGCP uses link-local IPv4 addresses (RFC 3927) in the 169.254.0.x range for HA heartbeat interface IP addresses and for inter-VDOM link interface IP addresses. When members join an HA cluster, each member's heartbeat interface (port_ha)…
Question
Which two statements are correct regarding FortiGate HA cluster virtual IP addresses? (Choose two.)
Options
- AHeartbeat interfaces have virtual IP addresses that are manually assigned.
- BA change in the virtual IP address happens when a FortiGate device joins or leaves the cluster.
- CVirtual IP addresses are used to distinguish between cluster members.
- DThe primary device in the clusteris always assigned IP address 169.254.0.1.
How the community answered
(32 responses)- A9% (3)
- B75% (24)
- D16% (5)
Explanation
HA heartbeat interface IP addresses The FGCP uses link-local IPv4 addresses (RFC 3927) in the 169.254.0.x range for HA heartbeat interface IP addresses and for inter-VDOM link interface IP addresses. When members join an HA cluster, each member's heartbeat interface (port_ha) is assigned an IP address from the range 169.254.0.1 - 169.254.0.63. HA inter-VDOM link interfaces are assigned IP address from the range 169.254.0.65 - 169.254.0.66. The IP address that is assigned to a heartbeat interface depends on the serial number priority of the member. Higher serial numbers have a higher priority, and therefore a serialno_prio number, # diagnose sys ha status FGVM08TM20002729: Secondary, serialno_prio=0, usr_priority=128, hostname=FGVM08TM20002729 FGVM08TM19003638: Primary, serialno_prio=1, usr_priority=128, hostname=FGVM08TM19003638 The member with serialno_prio=0 is assigned IP address 169.254.0.1, serialno_prio=1 is assigned 169.254.0.2, and so forth. The get system ha status command shows the HA heartbeat interface IP address of the primary # get system ha status vcluster 1: work 169.254.0.2 The diagnose ip address list command shows the device's assigned IP addresses: # diagnose ip address list IP=172.16.151.84->172.16.151.84/255.255.255.0 index=3 devname=port1 IP=192.168.2.204->192.168.2.204/255.255.255.0 index=6 devname=port2 IP=10.10.10.1->10.10.10.1/255.255.255.0 index=9 devname=port3 IP=127.0.0.1->127.0.0.1/255.0.0.0 index=13 devname=root IP=127.0.0.1->127.0.0.1/255.0.0.0 index=16 devname=vsys_ha IP=169.254.0.2->169.254.0.2/255.255.255.192 index=17 devname=port_ha IP=127.0.0.1->127.0.0.1/255.0.0.0 index=18 devname=vsys_fgfm IP=169.254.0.65->169.254.0.65/255.255.255.192 index=19 devname=havdlink0 IP=169.254.0.66->169.254.0.66/255.255.255.192 index=20 devname=havdlink1 You can also use the execute traceroute command from the subordinate unit CLI to display HA heartbeat IP addresses and the HA inter-VDOM link IP addresses.
Topics
Community Discussion
No community discussion yet for this question.