In a Global Server Load Balancing Active/Active environment, when the connection proxy is used as the site persistence method, what is used to source the traffic?

In a Global Server Load Balancing Active/Active environment, when the connection proxy is used as the site persistence method, what is used to source the traffic?

• A. LDNS IP Address
• B. Client source IP
• C. Virtual IP
• D. Subnet IP (SNIP)

Answer: (D)

In this GSLB setup, the persistence method that uses a connection proxy makes the appliance itself the source of the traffic to the remote site. The NetScaler uses its SNIP (Subnet IP) as the origin IP for outbound connections when proxying client sessions to another site. This ensures the remote site sees a consistent, routable source and that return traffic comes back to the same NetScaler for proper session persistence. The LDNS IP is only for DNS lookups, the client’s real IP is not used as the source in this proxy-based persistence, and the VIP is the front-end address the client hits—not the origin of the proxied traffic. Hence, the SNIP is the source of traffic in this scenario.

In this GSLB setup, the persistence method that uses a connection proxy makes the appliance itself the source of the traffic to the remote site. The NetScaler uses its SNIP (Subnet IP) as the origin IP for outbound connections when proxying client sessions to another site. This ensures the remote site sees a consistent, routable source and that return traffic comes back to the same NetScaler for proper session persistence. The LDNS IP is only for DNS lookups, the client’s real IP is not used as the source in this proxy-based persistence, and the VIP is the front-end address the client hits—not the origin of the proxied traffic. Hence, the SNIP is the source of traffic in this scenario.