Skip to content

Creating Additional Clusters in Amazon Elastic VMware Service

3 minute read
Content level: Advanced
0

This article will walk you through the process of creating additional VMware clusters in an Amazon EVS deployed VMware Cloud Foundation 5.2.x environment.

As you grow your Amazon EVS environment beyond the initial 4 nodes that get deployed, you may also look to create additional clusters in the environment. Here is a brief walk through on how to create these new clusters. Before you begin, log into the Amazon EVS section of the AWS console. Select the Amazon EVS environment you wish to add the cluster to, and under Networks and connectivity section of the environment, get the VLAN ID of the vTep network. You will need this in a later step.

Enter image description here

  1. Log into the SDDC Manager.

  2. Click on Workload Domains and then click the link for your domain.

Enter image description here

  1. Click Actions->Add Cluster.

Enter image description here

  1. Choose vSAN and select the Enable vSAN ESA checkbox and click Begin.

Enter image description here

  1. Enter a Cluster name and choose the Management-Domain-ESXi-Personality image from the image drop-down and click Next. If you have created another image in SDDC Manager with the Amazon EVS Custom Addon you could choose to use that image.

Enter image description here

  1. Leave vSAN HCI selected and leave the defaults for the vSAN Storage window and click Next.

Enter image description here

  1. Select a minimum of 3 hosts from the available hosts and click Next.

Enter image description here

  1. On the Switch Configuration screen, click Create Custom Switch Configuration.

Enter image description here

  1. Choose Default from the Copy from pre-configured profile drop-down.

Enter image description here

  1. You will see a message: VLAN ID is mandatory and has to be updated before proceeding. Click to Edit. Click Edit in the message.

Enter image description here

  1. Set the MTU to 8500 on the distributed switch.

Enter image description here

  1. Edit the Management, vMotion, and vSAN network settings and move uplink2 down to the Standby Uplinks.

Enter image description here

Enter image description here

  1. Scroll down to the NSX section, enter the VLAN ID you got at the beginning of the article and then click the Save VLAN ID link.

Enter image description here

  1. In the same section, now click Edit.

Enter image description here

  1. In the Overlay Network section, change the IP Allocation to Static IP Pool, choose Re-use an existing Pool and select the env-<your_environment_id>-tep01 IP pool. Then scroll down, set uplink2 to Standby Uplinks, and click Save Configuration. You can ignore the warning about IP pools with block subnets.

Enter image description here

Enter image description here

  1. Click Save Configuration again.

Enter image description here

  1. You will see another warning: VLAN ID is mandatory and has to be updated before proceeding. Click to Acknowledge. Click Acknowledge and then click Next.

Enter image description here

  1. Choose your license keys for vSphere and vSAN and click Next.

Enter image description here

  1. Review you settings and click Finish.

Enter image description here