Which NetScaler deployment mode is typically described as 'One-Arm'?

Which NetScaler deployment mode is typically described as 'One-Arm'?

• A. One-Arm Mode
• B. MAC-based Forwarding
• C. Two-Arm Mode
• D. Use Source IP(USIP)

Answer: (A)

One-Arm deployment refers to using a single network connection (one arm) to handle all traffic for the NetScaler, with traffic to and from the servers flowing through that same network path. In this setup the NetScaler sits on the same switch as the servers and often forwards requests to the real servers using MAC-based forwarding, effectively acting like a single-line gateway on that one arm. This is why this mode is described as One-Arm: there is one active network path into the system rather than separate, dedicated paths for clients and for servers. By contrast, a Two-Arm deployment uses separate interfaces or VLANs for client and server traffic. MAC-based Forwarding is a technique commonly used within One-Arm deployments to move traffic to back-end servers without requiring full routing between networks, and Use Source IP is about preserving the client’s original IP in backend communication, not about the deployment topology itself.

One-Arm deployment refers to using a single network connection (one arm) to handle all traffic for the NetScaler, with traffic to and from the servers flowing through that same network path. In this setup the NetScaler sits on the same switch as the servers and often forwards requests to the real servers using MAC-based forwarding, effectively acting like a single-line gateway on that one arm. This is why this mode is described as One-Arm: there is one active network path into the system rather than separate, dedicated paths for clients and for servers. By contrast, a Two-Arm deployment uses separate interfaces or VLANs for client and server traffic. MAC-based Forwarding is a technique commonly used within One-Arm deployments to move traffic to back-end servers without requiring full routing between networks, and Use Source IP is about preserving the client’s original IP in backend communication, not about the deployment topology itself.