Create NSX-T Cloud Connector object on the NSX Advanced Load Balancer Controller cluster. Choose the Cloud Connector model based on the Models for configuring an NSX-T Cloud Connector on the Advanced Load Balancing for VMware Cloud Foundation section.

Prerequisites

  • Create User Credential objects for NSX-T Data Center and vCenter Server on the Controller cluster.

  • Create a content library for hosting the Service Engine images on each of the vCenter Server(s) that are managed by NSX-T Data Center.

  • If using overlay-backed NSX segments for load balancing, create a Tier-1 router and dedicated a Tier-1 connected Logical Segment for the Service Engine data networks (vNICS).

  • If using an overlay-backed NSX segments for Service Engine management, create at least one overlay-backed NSX segments connected to a Tier-1 router (Applicable to NSX-T Cloud Connector of type overlay).

  • If using a VLAN network for the Service Engine management, create at least one VLAN-backed NSX segments (Applicable to NSX-T Cloud Connector of type overlay and/or VLAN).

  • If using VLAN networks for load balancing, create at least one VLAN-backed NSX segments for the Service Engine data networks (vNICS).

Procedure

  1. Create a new NSX-T Cloud Connector on the Controller cluster.

    1. In a web browser, log in to the Controller cluster VIP by using https://sfo-m01-avic01.sfo.rainpole.io/.

    2. Navigate to Infrastructure > Clouds.

    3. Click on CREATE and select NSX-T Cloud.

    4. To configure the Cloud, specify the following general settings:

      Setting

      Value

      Name

      NSX-T-<ID>

      Recommendation: Use VI workload domain name as the <ID>.

      Use the VI workload domain name if NSX-T Data Center manages VI workload domains.

      DHCP

      Select (If using DHCP for the Service Engine data networks).

      Object Name Prefix

      <prefix>

      This prefix will be used for all objects created by this NSX-T Cloud Connector.

      Recommendation: Use an easy identifier like ‘avise-<ID>’, where <ID> is the same ID used for the cloud name.

  2. Attach the Cloud Connector to an NSX Manager cluster.

    1. Click CHANGE CREDENTIALS under NSX-T credentials and specify the following information:

      Setting

      Value

      NSX-T Manager Address

      FQDN of the NSX Manager cluster that is managing this VI workload domain.

      NSX-T Manager Credentials

      NSX-T-<ID>

      Name of the NSX-T Data Center user credential object that was configured on the Controller cluster.

    2. Click on CONNECT.

  3. Configure the management network for the Service Engines.

    1. Under the Management Network section, select a Transport Zone.

    2. If a VLAN Transport Zone is selected, select a VLAN Segment.

    3. If an overlay Transport Zone is selected, select a Tier1 Logical Router and then an Overlay Segment.

  4. Configure the data network(s) for the Service Engines.

    1. Under the Data Networks section, select a Transport Zone.

    2. If a VLAN Transport Zone is selected, select a VLAN Segment.

    3. If an overlay Transport Zone is selected, select a Tier1 Logical Router and then an Overlay Segment.

    4. Repeat to add multiple data networks as required.

      Note:

      1. All data networks should belong to the same Transport Zone. Therefore all data networks are either VLAN-backed NSX segments or Tier-1 router attached overlay-backed NSX segments.

      2. Only one overlay-backed NSX segment can be added per Tier-1 router.

      3. Each Tier-1 router requiring load balancing services will be added as a new data network in the Cloud Connector configuration.

  5. Configure the vCenter Server(s).

    1. Click on ADD to add a new vCenter Server and specify the following information:

      Setting

      Value

      Name

      <name>

      Recommendation: Use VI workload domain name as an easy identifier

      Credentials

      vCenter Address

      Specify

      The vCenter Server FQDN/IP

      vCenter Credentials

      vCenter-<ID>

      Name of the vCenter Server user credential object that was configured on the Controller cluster.

    2. Click on CONNECT.

    3. From the Content Library drop-down, select the content library configured to host the Service Engine images.

    4. Click on DONE.

    5. Repeat to add multiple vCenter Server(s) as required.

    6. Click on SAVE.