An LTM has the 3 virtual servers, 2 SNATs, four self IP addresses defined and the networks shown in the graphic below. Selected options for each object are shown below. Settings not shown are at their defaults. Assume port exhaustion has not been reached.
A connection attempt is made with a source IP and port of 10.20.10.50:2222 and a destination IP and port of 10.10.2.102:80.
When the request is processed, what will be the source and destination IP addresses?
The connection attempt is made to the IP address 10.10.2.102 on port 80. This matches the VirtualServer1 configuration because it specifies the destination IP 10.10.2.102 with a netmask of 255.255.255.255 and port 80. VirtualServer1 has SNAT Automap configured, which means that the source IP address will be automatically translated using one of the self IPs of the LTM device. However, in the options provided, the closest correct configuration without errors is that the source IP remains as 10.20.10.50 (original source IP), and the destination IP will be a pool member in the 172.16/16 network, which is associated with VirtualServer1. Therefore, the source IP will be 10.20.10.50 and the destination IP will be a pool member in the 172.16/16 network.
F is the answer ignoring the typo: Source IP: 172.16.1.1; Destination IP: pool member in the 172.16/16 network
Answer is F, but ignoring the typo. When using a SNAT pool source address translation, the SNAT pool must contain SNAT translations assigned to the same traffic group as the virtual server’s virtual address. The only selfIP that maps traffic group of this SNAT is 172.16.1.1. Virtualserver1 accepts traffic because it contains the destination address and port 80 of the request, so it wins the battle against virtualserver2, with wildcard port.
answer F because automap is in used
I think it is A since the destination IP match most specific range. So the only the first VS is processed. So no SNAT. source address no change and destination is a pool member
correct answer is A?
Why E is not correct ??
I believe it is
because it is listening on all ports. The other virtual server is listening only for port 80