You are establishing a ClusterXL environment, with the following topology:
VIP internal cluster IP = 172.16.10.3; VIP external cluster IP = 192.168.10.3
Cluster Member 1: 4 NICs, 3 enableD. hme0: 192.168.10.1/24, hme1: 10.10.10.1/24, qfe2:
172.16.10.1/24
Cluster Member 2: 5 NICs, 3 enabled; hme3: 192.168.10.2/24, hme1: 10.10.10.2/24, hme2:
172.16.10.2/24
External interfaces 192.168.10.1 and 192.168.10.2 connect to a VLAN switch. The upstream
router connects to the same VLAN switch. Internal interfaces 172.16.10.1 and 172.16.10.2
connect to a hub. 10.10.10.0 is the synchronization network. The Security Management Server is
located on the internal network with IP 172.16.10.3. What is the problem with this configuration?
A.
The Cluster interface names must be identical across all cluster members.
B.
Cluster members cannot use the VLAN switch. They must use hubs.
C.
The Security Management Server must be in the dedicated synchronization network, not the
internal network.
D.
There is an IP address conflict.
For those that do not get why IP Address conflict is correct: The SMS would be assigned the same ip as the VIP internal Cluster IP (172.16.10.3)
Thx Chris!
From the description I don’t see any IP conflict between SMS and internal IPs, all are in 172.16.10.0/24
Look again, and you will see that the IP address 172.16.10.3 is mentioned twice, first as the internal VIP address, and then as the mgmt-server.
Look at it again
The vIP = SMS thus a conflict
D. There is an IP address conflict.