Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

PSC 6.7 High Availability with NSX-T Load Balancer (65030)

Last Updated: 12/20/2018Categories: InformationalTotal Views: 3678Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Purpose

This article provides information on Platform Services Controller 6.7 High Availability with NSX-T Load Balancer.

Resolution

Overview

The load balancer distributes incoming service requests among multiple servers in such a way that the load distribution is transparent to users. Load balancing helps achieve optimal resource utilization, maximizing throughput, minimizing response time, and avoiding overload. NSX-T provides load balancing services through the edge nodes, which enables users to deploy their own load balancer instances.

Scope

The primary focus of this document is to provide steps for installation and configuration of NSX-T Load Balancer for PSC’s.
In the upcoming sections, this document provides an overview of the specific solution requirements, a high-level design, implementation and verification steps.

Product versions

Product

Version

General Availability

vSphere (ESXi and vCenter Server)

6.7 U1

10/04/2018

NSX-T

2.3

09/06/2018

Prerequisites

NSX-T 2.3 is deployed and configured the NSX-T logical components.

Deployed NSX-T Edge nodes (recommended two) and configured Edge transport nodes.

Configure Edge Cluster with Edge node(s).

VLAN Backed NSX-T switch and assigned with VLAN ID for the subnet where the PSC’s are running.

Topology

Implemented the above topology with NSX-T Tier-1 router and Edge node.

High Level Summary

Configure NSX-T Load Balancer.
a)    Create and configure Tier-1 Router
b)    Add Centralized Port for the Tier-1 Logical Router
c)    Create and Configure Load Balancer
d)    Attach the newly created load balancer to a Tier-1 logical router
e)    Create a Health Monitor
f)     Add a Server Pool for Load Balancing
g)    Configure Virtual Server
h)    Attach Virtual Server to Load Balancer

Deploy the primary external Platform Services Controller node.

Deploy the secondary SSO node as a replication partner to the primary Platform Service Controller node.

Configuring vSphere 6.7 Platform Service Controllers for High availability.

Deploy vCenter server and point to PSC Load Balancer VIP FQDN.

1. Configure NSX-T Load Balancer

Create and configure Tier-1 Router

In the NSX Manager UI, Select Routing from the navigation panel.

Click Add and select Tier-1 Router.

Assign a name for the logical router.

(Optional) Select a tier-0 logical router to connect to this tier-1 logical router, you can leave this field blank for now.

Select an edge cluster to connect to this tier-1 logical router.

Select Edge Cluster Member from drop-down menu.

Click Save.

Add Centralized Port for the Tier-1 Logical Router

Click the Tier-1 logical router link to create ports.

Click the Configuration > Router Ports tab.

Click Add under the Logical Router Ports section.

Assign a name for the logical router port.

Select Type as “Centralized”.

Select the Logical switch (VLAN) from drop-down menu.

Enter the router port IP address in CIDR notation.

Keep the remaining default settings.

Click Save.

Create and Configure Load Balancer

From your browser, log in to an NSX Manager.

Select Load Balancer > Add.

Enter a name and a description for the load balancer.

Select the load balancer virtual server size and click “OK”.

Attach the newly created load balancer to a Tier-1 logical router

Select the load balancer and click Actions > Attach to a Logical Router.

Select Tier-1 logical router which created in previous steps from the drop-down menu.

Click OK.

Create a Health Monitor

Navigate to Load Balancing > Server Pools > Active Health Monitors.

Click “+ADD” to create a health monitor.

Monitor Properties

> Provide Name: “TCP”, select “LbTcpMonitor”.
> Health check protocol: “LbTcpMonitor”.
> Monitor Port: 443.

Click next and then finish.

Add a Server Pool for Load Balancing

Navigate to Load Balancing > Server Pools > Server Pools > Click on “ADD”.

General Properties > Provide the Pool Name and select “ROUND_ROBIN” for Load Balancing Algorithm and click Next.

SNAT Translation > Translation Mode as “Auto Map” and click Next.

Pool Members > Select Membership Type as “Static”.

Under Static Membership > Click “ADD” to add the pool members (PSC’s).
> provide Member “name” and the “IP of PSC-1”. Make sure the state is set to “Enabled”.

Click “ADD” again to add the second member.
> provide Member “name” and the “IP of PSC-2”. Make sure the state is set to “Enabled”.

Click Next and select “TCP-VCD” created in previous step for Active Health Monitor.

Click Finish.

Configure Virtual Server

From your browser, log in to an NSX Manager.

Navigate to Load Balancing > Virtual Servers > Virtual Servers and click on “ADD”.

General Properties:

> Provide Name for Virtual server.
> Application Type: Select Layer 4 and then select “TCP” from drop-down menu.
> Application Profile: select “nsx-default-lb-fast-tcp-profile”.

Click Next.

Virtual Server Identifiers: Provide the below details.

> IP Address: provide the IP address for Virtual server. (Provide T-1 router Centralized port IP)
> Port: 443, 389, 636, 2012, 2014, 2020.

Click Next.

Server Pool: Select the Server Pool which is created in previous step.

Load Balancing Profiles: select “nsx-default-source-ip-persistence-profile” for Source IP.

Click Finish.

Attach Virtual Server to Load Balancer

From your browser, log in to an NSX Manager.

Navigate to Load Balancing > Virtual Servers > Virtual Servers,

Select the Virtual Server created in previous Step and then click on “Actions” > Attach to a Load Balancer,

Select Load Balancer which created in previous steps.

Click “OK”.

2. Deploy the primary external Platform Services Controller node.

For more information, see Getting Started with Platform Services Controller.

3. Deploy the secondary SSO node as a replication partner to the primary Platform Service Controller node.

For more information, see Getting Started with Platform Services Controller.

4. Configuring vSphere 6.7 Platform Service Controllers for High availability

a.    Configuring certificates for PSC for High Availability : Link here.
b.    Configuring PSC Appliance for High Availability: Link here.

5. Verify the Load Balancer is presenting the same certificate.

From: Platform Services Controller Appliance:
# openssl s_client -connect <LB VIP FQDN>:443

6. Deploy vCenter server and point to PSC Load Balancer VIP FQDN.

Refer to VMware Official documentation for vCenter deployment with External PSC’s and Load Balancer. Link here.
Note: Ensure to provide the PSC Load Balancer VIP FQDN in Stage-2 deployment phase.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T

Take Our Survey

Support Assistant