Configure a virtual IP (VIP) subnet for the Data Network. You can configure the VIP range to use when a virtual service is placed on the specific VIP network. You can configure DHCP for the Service Engines. Optionally, if DHCP is unavailable, you can configure a pool of IP addresses which will get assigned to the Service Engine interface on that network. vSphere with Tanzu supports only a single VIP network.

Procedure

  1. In the NSX Advanced Load Balancer Controller dashboard, Infrastructure > Networks > .
  2. Select the cloud from the list.
    For example, select Default-Cloud.
  3. Enter a name for the network.
    For example, Data Nework.
  4. Keep DHCP Enabled selected if DHCP is available on the Data Network.
    Deselect this option if DHCP is not available.
  5. Select Enable IPv6 Auto Configuration.
    The NSX Advanced Load Balancer Controller discovers the network CIDR automatically if a VM is running on the network and it appears with type Discovered.
  6. If the Controller discovers the IP subnet automatically, configure the IP range for the subnet.
    1. Edit settings.
    2. Enter a Subnet Prefix.
    3. If DHCP is available for the Service Engine IP address, deselect Use Static IP Address for VIPs and SE.
    4. Enter one or more IP addresses or IP address ranges.
      For example, 10.202.35.1-10.202.35.254.
      Note: You can enter an IP address that ends with 0. For example, 192.168.0.0 and ignore any warning that appears.
    5. Click Save.
  7. If the Controller does not discover an IP subnet and its type, perform the following steps:
    1. Click Add.
    2. Enter a Subnet Prefix.
    3. Click ADD.
    4. If DHCP is available for the Service Engine IP address, deselect Use Static IP Address for VIPs and SE.
    5. In IP Address, enter the CIDR of the network that provides the virtual IP addresses.
      For example, 10.202.35.0/22
    6. Enter one or more IP addresses or IP address ranges.
      The range must be a subset of the network CIDR in IP Subnet. For example, 10.202.35.1-10.202.35.254.
      Note: You can enter an IP address that ends with 0. For example, 192.168.0.0 and ignore any warning that appears.
    7. Click Save to save the subnet configuration.
    The Edit Network Settings page lists the IP Subnet with type Configured and an IP address pool.
  8. Click Save to save the network settings.

Results

The Network page lists the configured networks.

Example

The Primary Workload Network network displays the discovered network as 10.202.32.0/22 and configured subnets as 10.202.32.0/22 [254/254]. This indicates that 254 virtual IP addresses come from 10.202.32.0/22. Note that the summary view does not list the IP range 10.202.35.1-10.202.35.254.