This Deployment for Region B document is updated with each release of the product or when necessary.

This table provides the update history of the Deployment for Region B document.

Revision

Description

26 SEP 2017

Added missing number in filename for the command to configure symbolic link between the UMDS and the PostgreSQL. See Configure PostgreSQL Database on Your Linux-Based Host Operating System for UMDS in Region B.

EN-002469-02

Added step 9, which instructs users to configure the MTU value on the vMotion VMkernel adapter to 9000. See Create a vSphere Distributed Switch for the Management Cluster in Region B.

Added step 9, which instructs users to configure the MTU value on the vMotion VMkernel adapter to 9000. See Create a vSphere Distributed Switch for the Shared Edge and Compute Cluster in Region B.

EN-002469-01

Step 4d incorrectly instructed you to use the fully qualified domain name (FQDN) lax01psc01.lax01.rainpole.local and a NSX Load Balancer name of LAX01PSC01. This error has been corrected such that the FQDN is lax01psc51.lax01.rainpole.local and the NSX Load Balancer name is LAX01PSC51. See Update the Platform Services Controller SSO Configuration and Endpoints in Region B.

Step 4d has been corrected to use the FQDN lax01psc51.lax01.rainpole.local. See Update the Platform Services Controller SSO Configuration and Endpoints in Region B

Step 6 has been corrected to use the name LAX01PSC51. The hostname has also been updated to lax01psc51.lax01.rainpole.local. See Deploy the Platform Services Controller NSX Load Balancer in Region B.

Step 8 incorrectly listed the datastore name as SFO01A-VSAN01-MGMT01. This has been corrected to read LAX01A-VSAN01-MGMT01. See Deploy the Platform Services Controller NSX Load Balancer in Region B.

Step 13c and 14c have been updated to LAX01PSC51. See Deploy the Platform Services Controller NSX Load Balancer in Region B.

Step 4 now states that you should double-click the NSX Edge labeled LAX01PSC51 to manage its settings. See Create Platform Services Controller Application Profiles in Region B.

Step 4 now states that you should double-click the NSX Edge labeled LAX01PSC51 to manage its settings. See Create Virtual Servers in Region B.

Step 4 now states that you should double-click the NSX Edge labeled LAX01PSC51 to manage its settings. See Create Platform Services Controller Server Pools in Region B.

Step 4 incorrectly instructed you to use the FQDN of lax01psc01.lax01.rainpole.local and a DNS record name of LAX01PSC01. This error has been corrected such that the FQDN is lax01psc51.lax01.rainpole.local and the DNS record name of LAX01PSC51. See Update DNS Records for the Platform Services Controller Load Balancer in Region B.

Step 10 incorrectly instructed you to save the vRealize Automation server pool. This has been corrected to save the Platform Services Controller server pools. See Create Platform Services Controller Server Pools in Region B.

The topic Configure Service Account Privileges on the Compute vCenter Server in Region B was incorrectly included twice in the previous version of this document. The extra occurrence has been removed.

The topic Configure the Service Account Privilege on the Compute Cluster NSX Instance in Region B was incorrectly included twice in the previous version of this document. The extra occurrence has been removed.

Steps 3b and 3c have been updated to make Bash your default command shell. See Replace the Platform Services Controller Certificates in Region B.

This topic incorrectly instructed you to use a fully qualified domain name (FQDN) of lax01psc01.lax01.rainpole.local and a NSX Load Balancer name of LAX01PSC01. This error has been corrected such that the FQDN is lax01psc51.lax01.rainpole.local and the NSX Load Balancer name is LAX01PSC51. See Replace the NSX Manager Certificates in Region B and Deploy the NSX Manager for the Shared Edge and Compute Cluster NSX Instance in Region B.

Step 4e incorrectly referred to lax01psc01.lax01.rainpole.local as the Platform Services Controller FQDN for the lookup service IP address. The correct FQDN is lax01psc51.lax01.rainpole.local. See Replace the NSX Manager Certificates in Region B.

Step 3h has been corrected to use the FQDN comp01nsxm51.lax01.rainpole.local. See Deploy the NSX Manager for the Shared Edge and Compute Cluster NSX Instance in Region B.

Step 4e has been corrected to use the Lookup Service FQDN lax01psc51.lax01.rainpole.local. See Deploy the NSX Manager for the Shared Edge and Compute Cluster NSX Instance in Region B.

Step 4h has been corrected to use the vCenter Server FQDN comp01vc51.lax01.rainpole.local. See Deploy the NSX Manager for the Shared Edge and Compute Cluster NSX Instance in Region B.

Step 2 has been corrected to use the vCenter FQDN mgmt01vc51.lax01.rainpole.local. See Configure a DRS Anti-Affinity Rule for vRealize Log Insight in Region B

The Platform Services Controller instances URLs in the "Appliance Management Interface URL" table have been corrected. Also, the vRealize Log Insight URL in Step 2a has been corrected. See Configure vCenter Server to Forward Log Events to vRealize Log Insight in Region B.

Step 4a has been updated to LAX01-Comp01 (comp01vc51.lax01.rainpole.local). See Create Reservations for the Compute Cluster in Region B.

Step 15 has been corrected to use mgmt01vc51.lax01.rainpole.local. See Deploy the vSphere Replication Appliance in Region B.

Steps 2 and 3 were duplicated, and this has been corrected. In addition, the vCenter FQDN in step 2 has been corrected, as has the host FQDN in step 4. See Configure Lockdown Mode on All ESXi Hosts in Region B

Step 3i incorrectly listed the default gateway IP address as 172.17.11 .1. The correct IP address is 172.17.11.253. See Deploy the External Platform Services Controllers for the vCenter Servers in Region B.

The step about powering on vSphere Replication in Region B now contains the correct host name mgmt01vc51.lax01.rainpole.local for the Management vCenter Server in Region B. See Deploy the vSphere Replication Appliance in Region B.

A step was added instructing you to power on vSphere Data Protection after appliance deployment. See Deploy the Virtual Appliance of vSphere Data Protection in Region B.

Use the UMDS Shared Repository as the Download Source in Update Manager in Region B now provides instructions about adding the repository of the Update Manager Download Service in Region B to the Update Manager on the Compute vCenter Server.

The vRealize Log Insight deployment documentation now contains the correct host names of the vCenter Server instances in Region B. See Configure vCenter Server to Forward Log Events to vRealize Log Insight in Region B and Configure the Log Insight Agent on vRealize Operations Manager to Forward Log Events to vRealize Log Insight in Region B.

EN-002469-00

Initial release.