Product Documentation

Step 3: Binding Backend Servers to a Port Profile

Oct 06, 2014

After performing the vPath configurations on the NetScaler and then configuring the load balancing virtual server, you must define the NetScaler as a Virtual Service Node (VSN) and associate it with a port profile. The port profile, which is defined on the Virtual Supervisor Module (VSM), specifies that all traffic reaching the virtual port of the server must be redirected to the NetScaler virtual appliance. On the vCenter Server, you must then bind the port profile to the virtual port that is associated with the virtual machine.

Note: Every virtual NIC of a virtual machine has a corresponding virtual port on the Nexus virtual switch. Each virtual port must be associated with a port profile that specifies the properties of the device.

To bind backend servers to a port profile

On the Nexus Virtual Supervisor Module (VSM), do the following

  1. Configure the NetScaler virtual appliance as a VSN. Example: Create a VSN named "NS1" for a NetScaler with IP address 10.102.38.220.
    # vservice node NS1 type adc 
       ip address 10.102.38.220 
       adjacency l3 
       fail-mode open
  2. Create a port profile for the NetScaler virtual appliance. Example: Create a port profile named "LB-ON-L3" to be used for the NetScaler services.
    # port-profile type vethernet LB-ON-L3 
       vmware port-group 
       switchport mode access 
       switchport access vlan 1 
       vservice node NS1 
       no shutdown 
       system vlan 1 
       state enabled
  3. On the vCenter Server, bind the port profile to the virtual machine as shown in the following image:
    Note: Repeat this step to bind the required servers to the port profile.