You are the MegaCorp Security Administrator. This company uses a firewall cluster, consisting of
two cluster members. The cluster generally works well but one day you find that the cluster is
behaving strangely. You assume that there is a connectivity problem with the cluster
synchronization link (cross-over cable). Which of the following commands is the BEST for testing
the connectivity of the crossover cable?
A.
ifconfig -a
B.
arping <IP address of the synchronization interface on the other cluster member>
C.
telnet <IP address of the synchronization interface on the other cluster member>
D.
ping <IP address of the synchronization interface on the other cluster member>
B
sk92483
https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92483
How to send a Gratuitous ARP Request manually from cluster member
In Check Point ClusterXL, cluster members are sending Gratuitous ARP Request packets to notify the networking devices about which MAC address is associated with Virtual IP address.
This is crucial, for example, in High Availability cluster during fail-over – new Active member must update the network that a new MAC address is now associated with Virtual IP address.
In some scenarios (e.g., networking device does not process correctly the Gratuitous ARP Request packets from ClusterXL members), a network administrator might want to send such Gratuitous ARP Request from ClusterXL members to networking devices, so they update their ARP cache tables.
The Synchronization Network is used to transfer synchronization information about connections and other Security Gateway states between cluster members.
So do arping on synchronization link has no sense.
I think the answer is D
I forgot : sk92483
Example 1 – Send Gratuitous ARP Request packets from ClusterXL member to networking devices about member’s physical interface
Example:
Members’ interface name – eth5
Members’ interface MAC address – 00:A0:8E:B4:A7:5D
Members’ interface IP address – 192.10.10.10
Procedure:
[Expert@HostName]# arping -c 4 -A -I eth5 192.10.10.10
Traffic capture on neighboring devices would show:
11:06:31 arp reply 192.10.10.10 is-at 00:a0:8e:b4:a7:5d
11:06:32 arp reply 192.10.10.10 is-at 00:a0:8e:b4:a7:5d
11:06:33 arp reply 192.10.10.10 is-at 00:a0:8e:b4:a7:5d
11:06:34 arp reply 192.10.10.10 is-at 00:a0:8e:b4:a7:5d
B. arping