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

This table provides the update history of the Deployment for Region A 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 A.

EN-002468-03

Step 6 omitted the configuration values for the PSC-TCP server pool. The correct configuration values have been added to this step in the accompanying table. See Create Platform Services Controller Server Pools in Region A.

EN-002468-02

Extended the permissions that are required for integrating vRealize Operations Manager and vRealize Log Insight. See Configure User Privileges on vRealize Operations Manager for Integration with vRealize Log Insight in Region A

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 A.

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 A.

EN-002468-01

Step 1 incorrectly listed the FQDN as ending in .com. This has been corrected to read the sfo01psc01.sfo01.rainpole.local. See Update the Platform Services Controller SSO Configuration and Endpoints in Region A.

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

The default gateway IP address was incorrectly listed as 172.16.11.1. The correct IP address is 172.16.11.253. SeeDeploy the External Platform Services Controllers for the vCenter Servers in Region A.

Incorrectly instructed you to update host profile to the management cluster. It should instruct you to update the host profile for the Compute cluster. See Update the Host Profile for the Compute Cluster in Region A.

Step 5h incorrectly instructed you to configure the UDLR interface. The correct interface to configure is DLR. See Deploy NSX Edge Devices for North-South Routing in the Shared Edge and Compute Cluster in Region A.

Step 9m incorrectly stated that three neighbors were added to the Neighbors table. The correct number of neighbors added is four. See Enable and Configure Routing in the Shared Edge and Compute Cluster in Region A

The Distributed Firewall Rules have been updated to allow the administrator network access to vRealize Log Insight and vRealize Operations. See Create Distributed Firewall Rules, Create IP Sets for All Components of the Management Clusters in the SDDC, and Create Security Groups.

Step 10 incorrectly instructed you to save the vRealize Automation Server Pool. The correct pool member to save is the Platform Services Controller Pool. See Create Platform Services Controller Server Pools in Region A.

Steps 2 and 3 were duplicated. The duplicated step has been removed. See Configure Lockdown Mode on All ESXi Hosts in Region A.

Added a step to power on vSphere Data Protection after appliance deployment. See Deploy the vSphere Data Protection Virtual Appliance in Region A.

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

EN-002468-00

Initial release.