What is required for a virtual server to support clients whose traffic arrives on the internal VLAN and pool members whose traffic arrives on the external VLAN?

Load balancers are specifically designed to segment client and server traffic across different VLANs, making it a standard and supported configuration.

While technically possible, enabling a virtual server on both VLANs is typically not necessary; its primary role is to listen for client connections, which are on the internal VLAN.

A virtual server acts as the client-facing endpoint for connections, so it must be explicitly enabled or configured to listen on the internal VLAN where client traffic is expected to arrive. The load balancer's routing capabilities then handle forwarding traffic to pool members on the external VLAN.

Enabling the virtual server only on the external VLAN would prevent clients on the internal VLAN from being able to establish a connection with the virtual server.