The section explains the steps required to deploy the SE OVA.
- In vCenter, click File in the top menu and choose Deploy OVF Template.
- Follow the Deploy OVA Template wizard instructions:
- Select Thick Provision Lazy Zeroed for disk format.
- Select the port groups for the SE network connections. The SE has ten vNICs. Connect the first vNIC to the management network. Connect the other vNICs to the data network.
- For the management connection, choose a port group that will allow the SEs to communicate with the Controller. The SE can be connected to up to nine data networks. Choose a port group in the destination networks for each source network, where you can host the virtual services and pools. The Controller expects the SE’s data vNICs to be connected to virtual service and pool networks.
- Specify the Controller IP address.
- Navigate to to copy the authentication token.
- Specify the management IP address and default gateway. In the case of DHCP, leave this field empty.
- The field for the Controller cluster UUID must be left blank.
- In In the VM properties menu, connect the SE data vNICs that are required to reach a virtual service network and pool network to the port groups. Leave the unused vNICs disconnected.
- Note down the following information: MAC address of the vNICsIP subnet of the port group. This information will be used to identify the SE interfaces, as the Controller does not have access to vCenter and so cannot associate the SE’s interface names with VMware’s interface names.
- MAC address of the vNICs
- IP subnet of the port group
- MAC address of the vNICsIP subnet of the port group.
What to do next
Repeat the above steps for at least one more Service Engine. By default, two NSX Advanced Load Balancer SEs are required for deploying a virtual service.