- How vPath Works
- Step 1: Configuring vPath on a NetScaler
- Step 2: Configuring Load Balancing of Backend Servers
- Step 3: Binding Backend Servers to a Port Profile
- Behavioral Aspects of NetScaler with vPath
All data transmitted between the NetScaler virtual appliance and the server is vPath encapsulated. By default, vPath is disabled on the NetScaler virtual appliance. Therefore, to configure vPath on a NetScaler, you must first enable vPath, and then configure a SNIP address as the source of the vPath packet when the packet is forwarded to the switch.
If, in the return flow, the vPath packet is received at an IP address other than the specified SNIP address, the appliance drops the packet.
At the command prompt, do the following:
enable ns feature vPath
set vPathParam -srcIP <ip_addr> -offload <ENABLED | DISABLED>
When the offload parameter is enabled, the NetScaler adds an extra 24 bytes to the vPath header.
By default, the NetScaler IP (NSIP) address is configured as the vPath source IP address. However, the show vPathParam command shows the source IP address as 0.0.0.0.
add vpath <name> (<destIP> [<netmask>] [<gateway>]) -encapMode L3
save ns config