Configure load balancing for the analytics cluster on the dedicated sfo01w01lb01 NSX Edge services gateway. The remote collector group does not require load balancing.

Procedure

  1. Log in to vCenter Server by using the vSphere Web Client.
    1. Open a Web browser and go to https://sfo01w01vc01.sfo01.rainpole.local/vsphere-client.
    2. Log in using the following credentials.

      Setting

      Value

      User name

      administrator@vsphere.local

      Password

      vsphere_admin_password

  2. From the Home menu, select Networking & Security

    The vSphere Web Client displays the NSX Home page.

  3. On the NSX Home page, click NSX Edges and select 172.16.11.66 from the NSX Manager drop-down menu at the top of the NSX Edges page.
  4. On the NSX Edges page, double-click the sfo01w01lb01 NSX edge.
  5. Configure the load balancing VIP address for analytics cluster.
    1. On the Manage tab, click the Settings tab and click Interfaces.
    2. Select the OneArmLB interface and click the Edit icon.
    3. In the Edit NSX Edge Interface dialog box, click the Edit icon and in the Secondary IP Addresses text box enter the 192.168.11.35 VIP address.
    4. Click OK to save the configuration.
  6. Create an application profile.
    1. On the Manage tab for the sfo01w01lb01 device, click the Load Balancer tab.
    2. Click Application Profiles, and click the Add icon.
    3. In the New Profile dialog box, configure the profile using the following configuration settings, and click OK.

      Setting

      Value

      Name

      vrops-https

      Type

      HTTPS

      Enable SSL Passthrough

      Selected

      Persistence

      Source IP

      Expires in (Seconds)

      1800

      Client Authentication

      Ignore

  7. Create a service monitoring entry.
    1. On the Load Balancer tab for the of the sfo01w01lb01 device, click Service Monitoring and click the Add icon.
    2. In the New Service Monitor dialog box, configure the health check parameters using the following configuration settings, and click OK.

      Setting

      Value

      Name

      vrops-443-monitor

      Interval

      3

      Timeout

      5

      Max Retries

      2

      Type

      HTTPS

      Method

      GET

      URL

      /suite-api/api/deployment/node/status

      Receive

      ONLINE (must be upper case)

  8. Add a server pool.
    1. On the Load Balancer tab of the sfo01w01lb01 device, select Pools, and click the Add icon. 
    2. In the New Pool dialog box, configure the load balancing profile using the following configuration settings. 

      Setting

      Value

      Name

      vrops-svr-443

      Algorithm

      LEASTCONN

      Monitors

      vrops-443-monitor

    3. Under Members, click the Add icon to add the pool members.
    4. In the New Member dialog box, add one member for each node of the analytics cluster and click OK.

      Setting

      Value

      Name

      vrops01svr01a

      IP Address

      192.168.11.31

      State

      Enable

      Port

      443

      Monitor Port

      443

      Weight

      1

      Max Connections

      8

      Min Connections

      8

    5. In the New Pool dialog box, click OK.
  9. Add a virtual server.
    1. On the Load Balancer tab of the sfo01w01lb01 device, select Virtual Servers and click the Add icon. 
    2. In the New Virtual Server dialog box, configure the settings of the virtual server for the analytics cluster and click OK.

      Setting

      Value

      Enable Virtual Server

      Selected

      Application Profile

      vrops_https

      Name

      vrops-svr-443

      Description

      vRealize Operations Manager Cluster

      IP Address

      192.168.11.35

      Click Select IP Address, select OneArmLB from the drop-down menu and select 192.168.11.35 IP for the virtual NIC.

      Protocol

      HTTPS

      Port

      443

      Default Pool

      vrops-svr-443

      Connection Limit

      0

      Connection Rate Limit

      0

      You can now connect to the analytics cluster using the public Virtual Server IP address over HTTPS at the https://vrops01svr01.rainpole.local address.

  10. Configure auto-redirect from HTTP to HTTPS requests.

    The NSX Edge can redirect users from HTTP to HTTPS without entering another URL in the browser. 

    1. On the Load Balancer  tab of the sfo01w01lb01 device, select Application Profiles and click the Add icon.
    2. In the New Profile dialog box, configure the application profile settings and click OK.

      Setting

      Value

      Name

      vrops-http-redirect

      Type

      HTTP

      HTTP Redirect URL

      https://vrops01svr01.rainpole.local/vcops-web-ent/login.action

      Persistence

      Source IP

      Expires in (Seconds)

      1800

    3. On the Load Balancer tab of the sfo01w01lb01 device, select Virtual Servers and click the Add icon.
    4. Configure the settings of the virtual server for HTTP redirects.

      Setting

      Value

      Enable Virtual Server

      Selected

      Application Profile

      vrops-http-redirect

      Name

      vrops-svr-80-redirect

      IP Address

      192.168.11.35

      Protocol

      HTTP

      Port

      80

      Default Pool

      NONE

      Connection Limit

      0

      Connection Rate Limit

      0

      You can connect to the analytics cluster at the public Virtual Server IP address over HTTP at the http://vrops01svr01.rainpole.local address.

  11. Verify the pool configuration by examining the pool statistics that reflect the status of the components behind the load balancer.
    1. Log out and log in again to the vSphere Web Client.
    2. From the Home menu, select Networking & Security.
    3. On the NSX Home page, click NSX Edges and select  172.16.11.66 from the NSX Manager drop-down menu at the top of the NSX Edges page.
    4. On the NSX Edges page, double-click the sfo01w01lb01 NSX edge.
    5. On the Manage tab, click the Load Balancer tab.
    6. Select Pools and click Show Pool Statistics.
    7. In the Pool and Member Status dialog box, select the vrops-svr-443 pool.
    8. Verify that the load balancer pool is up.