View source for Lab:Install and configure a (nested) vSphere SDDC

<div class="page-body">
In this lab I am working with the following software and versions:

{| class="wikitable simple-table"
|-
! Software
! Version
! Filename
|-
| VMware vCenter Server Appliance
| 7.00U3G
| VMware-VCSA-all-7.0.3-20150588.iso
|-
| VMware ESXi Server
| 7.00U3F
| VMware-VMvisor-Installer-7.0U3f-20036589.x86_64.iso
|}

# Deploy a vCenter server

<ol start="2" style="list-style-type: decimal;">
<li>Deploy 6 x ESXi hosts
<ol style="list-style-type: lower-alpha;">
<li>3 x Compute hosts</li></ol>

<ol start="2" style="list-style-type: lower-alpha;">
<li>3 x Edge hosts</li></ol>
</li></ol>

<ol start="3" style="list-style-type: decimal;">
<li>The vSphere environment has one Workload cluster and one Edge cluster that need to be configured.
<ol style="list-style-type: lower-alpha;">
<li>Prepare the full cluster for Compute with DRS and HA.</li></ol>

<ol start="2" style="list-style-type: lower-alpha;">
<li>Prepare another full cluster for Edge with DRS and HA.</li></ol>
</li></ol>

<ol start="4" style="list-style-type: decimal;">
<li>Create a VDS and Port Groups</li></ol>

<ol start="5" style="list-style-type: decimal;">
<li>Add the ESXi hosts to the vSphere Clusters</li></ol>

<ol start="6" style="list-style-type: decimal;">
<li>Configure VSAN</li></ol>

One of the prerequisites when you are installing NSX is a working SDDC based on vSphere.

[https://www.notion.so/Compute-Storage-and-vSphere-Infrastructure-71c1d504273242bf98f3f948e7eea491?pvs=21 There are different designs available when it comes to the deployment of your vSphere Infrastructure].

In this section I will tell you how to deploy/configure a vCenter Server with some ESXi hosts so that you can use this environment as a starting point to Install and configure NSX.

As I am doing a nested deployment and one can loose track on what is happening where I have created the figure below for better understanding.

<div id="3da76001-a906-4dff-87af-0fa1392d0c47" class="figure image">
'''Figure 1:'''
https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled.png

</div>
⚠️ In this article I am building the nested lab as per Figure 1.

When I add NSX later in this nested setup Figure 2 would look something like this:

<div id="75e7fd01-3b59-43ee-9ac4-0279e307417c" class="figure image">
'''Figure 2:'''
https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%201.png

</div>
When I would deploy this in a non-nested environment Figure 3 would look like this:

<div id="ad307f1f-4425-42b5-b00e-d76e71578526" class="figure image">
'''Figure 3:'''
https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%202.png

</div>
<span id="2742a719-6d0c-4b5c-8852-63bde1f2c7c6"></span>
= The Steps =

When you have [https://www.notion.so/Lab-Install-and-configure-a-DNS-Server-using-BIND-e561f226941745e087a49ddc9650a214?pvs=21 DNS] working, the next step is to deploy your vSphere infrastructure.

<ul>
<li>
<span class="far fa-regular fa-square">STEP 1: Deploy a vCenter Server (Appliance)</span></li>
<li>
<span class="far fa-regular fa-square">STEP 2: Configure vCenter Server</span></li>
<li>
<span class="far fa-regular fa-square">STEP 3: Deploy the ESXi </span>
</li>
<li>
<span class="far fa-regular fa-square">STEP 4: Add the ESXi Servers to a vSphere Cluster and configure VSAN</span>
</li>
<li>
<span class="far fa-regular fa-square">STEP 5: Install the Licences for the vCenter Server, ESXi Servers and VSAN</span>
</li></ul>

<span id="1756d5fc-c543-4308-a225-13a674b19491"></span>
== STEP 1: Deploy a vCenter Server (Appliance) ==

The vCenter Server is deployed on another vSphere environment (nested) and this requires a different installation approach using two stages. You will need to deploy the vCenter Server using the .ova file. The .ova file can be retrieved from the vCenter Server ISO file that you can download from the VMware website.

⚠️ There are multiple ways to deploy a vCenter Server, for example using the VCSA deploy tool with the JSON file as input. This method will not be used in this article.

<span id="06ecdbee-27da-42d8-80a8-696c6325812d"></span>
=== STAGE 1 Deployment ===

Create a new Virtual Machine:

<div id="5d0e7120-97cc-4bdc-8752-baf8399b7216" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%203.png

</div>
Select: Deploy from template:

<div id="51dbac67-9236-45f1-9e83-43dc86894e1b" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%204.png

</div>
Choose the OVA/OVF Template you want to deploy from:

<div id="f0f87a28-e7d2-4cd5-9af2-9b91d03a826a" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%205.png

</div>
Provide a Virtual Machine name:

<div id="168bbbb7-41af-40bf-8354-6cc1c3c7633d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%206.png

</div>
Select the correct Resource Pool (the one with your name on it):

<div id="4e8f57b9-3d31-409b-973b-2a68a3e3a37e" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%207.png

</div>
Review the details:

<div id="e3935ba2-651c-4111-81dc-f0d23e7ec155" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%208.png

</div>
Accept the licence agreement:

<div id="5935e694-f061-4e57-be10-24bfa270a102" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%209.png

</div>
Select the Storage:

<div id="e212ade6-9c23-4521-bc77-69d4a1393469" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2010.png

</div>
Select the destination network:

<div id="7dbb28eb-a4b5-4040-9901-c98408b7fedf" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2011.png

</div>
Specify the template specific properties like passwords, IP address, DNS, default gateway settings, etc.:

<div id="d3df6778-52be-4d57-b088-f097ca5985d1" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2012.png

</div>
<div id="de1350ff-629b-46cf-9b34-f3f0a4dbb277" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2013.png

</div>
<div id="9222230d-0e76-481e-80a2-5e7ab639ff2a" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2014.png

</div>
<div id="00ca2ade-31f3-4192-96eb-c592d08a013e" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2015.png

</div>
<div id="6b5aa78b-6be0-4585-8010-9581589159e3" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2016.png

</div>
Review the Summary before you start the actual deploy:

<div id="6bdab151-553e-4357-ab54-e9a4ba027b66" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2017.png

</div>
Power on the Virtual Machine:

<div id="1c183976-27b4-4ad1-b877-2a841a27ceef" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2018.png

</div>
<span id="c616b18d-7222-4735-8345-cc82593d5034"></span>
=== STAGE 2 Deployment ===

When you powered on the Virtual machine, you have only completed the STAGE 1 vCenter Server deployment, and we still need to complete the STAGE 2 deployment.

To do this, you need to browse from the Stepstone to [https://10.203.100.5:5480/ https://10.203.100.5:5480] (the vCenter Server Management IP address) Log in to the vCenter Server to complete the STAGE 2 deployment.

<div id="05e5b3d4-d099-4b94-a6ef-c89e6324700f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2019.png

</div>
Click next:

<div id="2585ca02-985b-4d7f-8708-65700597a4e4" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2020.png

</div>
Verify all the parameters, and select to synchronise your NTP with a selected NTP server.

<div id="b0390726-f89c-4269-a448-8e05600f4169" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2021.png

</div>
Specify the SSO configuration details:

<div id="e040db44-d03b-4f3e-abad-62401b18baf4" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2022.png

</div>
Configure CEIP (or not):

<div id="09beecf3-7ade-4523-904e-a654c9149179" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2023.png

</div>
Review the final STAGE 2 configuration details and click finish to start the STAGE 2 deployment:

<div id="c7318a46-cbab-42f6-b093-08a45ce3c649" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2024.png

</div>
<div id="3a83ffbb-4b16-4a00-a923-48b1d37e85b9" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2025.png

</div>
Watch the progress screen until it finishes.

When STAGE 2 deployment is finished sometimes, you will get a screen that is finalised, and sometimes it does not do the auto-refresh properly, and it times out. The STAGE 2 deployment takes around 20 minutes, and after the deployment, you can refresh the screen and log in again and look at the vCenter Server Appliance summary screen:

<div id="6ebad63f-224b-480e-a075-230ae7ac7294" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2026.png

</div>
Now you are ready to log into the vCenter Server GUI:

<div id="d91b046e-8c5d-4732-a4b1-edafa93a44f1" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2027.png

</div>
<span id="10fc48bf-ef8e-4553-9172-e27d177427a9"></span>
== STEP 2: Configure vCenter Server ==

<span id="6d28365f-2913-4b84-9e32-458037ca3edd"></span>
=== Create (virtual) Data Center with vSphere Clusters ===

After the Data Center and vSphere Cluster objects are created this looks something like the screenshot below.

<div id="a9fd54a2-552e-49dc-9f52-b86e31b20242" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2028.png

</div>
<span id="02b7cbbb-3b41-4bc3-bc5b-cf7fd126349f"></span>
=== Configure DRS on the vSphere Clusters ===

Verify if DRS is enabled and set to “Fully Automated” and if not set it to the below settings.

Verify this on the Compute Cluster.

<div id="1fa4803b-edcd-4bf2-a609-7c373f3b79ab" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2029.png

</div>
Verify this on the Edge Cluster.

<div id="eee4cab5-caf3-466c-b516-11568f32352f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2030.png

</div>
<span id="5d80462b-0c06-4398-9d22-1a08698b8a94"></span>
=== Create VDS and VDS Port Groups ===

Browse to the Networking tab and right-click on the Data Center object and select '''Distributed Switch → New Distributed Switch''' to create a new Distributed Switch.

<div id="7c25f79f-7cee-4c6e-821b-59ef298c8f98" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2031.png

</div>
Provide a name for the new Distributed Switch:

<div id="2f79bb35-5c3f-4f98-a99e-a9b2ee249336" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2032.png

</div>
Select a Distributed Switch version:

<div id="060ad150-7088-490e-b593-608c641fe4fb" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2033.png

</div>
Set the number of uplinks:

<div id="cc947a6e-7d72-4cff-b4c4-3762c6e06bef" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2034.png

</div>
Review the details and click on finish:

<div id="ebdf3710-e047-4ecb-b55f-50c6ba2fc8bf" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2035.png

</div>
Verify if the Distributed Switch has been created successfully:

<div id="21d723e1-2fbb-44d4-b0c8-220cfc37c888" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2036.png

</div>
Now that the Distributed Switch is created it is time to create some Port Groups. the details can be found in the table below:

<div id="40d8d9d3-18d2-4a5b-b1d9-ef21be347111" class="collection-content">

<span id="section"></span>
====  ====

{| class="wikitable collection-content"
|-
! Port Group Name
! VLAN Type
! VLAN ID/trunk range
|-
| [https://www.notion.so/Management-9ad619900edd452798a48164f5e647a0?pvs=21 Management]
| VLAN
| 100
|-
| [https://www.notion.so/NSXEdgeUplink1-2c89e82bea304a668b57088e730bde53?pvs=21 NSXEdgeUplink1]
| VLAN Trunk
| 114, 116, 118
|-
| [https://www.notion.so/NSXEdgeUplink2-ff4142f5afa54d0a9e0241400cd0355d?pvs=21 NSXEdgeUplink2]
| VLAN Trunk
| 114, 117, 118
|-
| [https://www.notion.so/vMotion-6479378f6c0c41b98591eee2df4e365d?pvs=21 vMotion]
| VLAN
| 111
|-
| [https://www.notion.so/vSAN-150f1b097dbd44b7a9b5de51efcaf869?pvs=21 vSAN]
| VLAN
| 112
|}




</div>
⚠️ The NSXEdgeUplink Port Groups will be created now, and will be used for the Virtual NSX Edge Transport Nodes.

Right-click on the Distributed Switch and select '''Distributed Port Group → New Distributed Port Group.'''

<div id="a70fad4c-dcb9-4159-9be8-89ebf19b6890" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2037.png

</div>
Provide a name for the new Distributed Port Group:

<div id="381ae028-9371-4d1e-ae1d-76947c0970a1" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2038.png

</div>
Set the VLAN Type to be VLAN and specify the VLAN id as provided in the table:

<div id="78a4821f-2bec-418d-bdd6-af162335b037" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2039.png

</div>
Review the details and click on finish:

<div id="6aba1d34-80a3-467d-858e-60ce76f8b999" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2040.png

</div>
Verify if the Distributed Port Group has been created successfully:

<div id="643c9222-7f80-4b6a-9982-630e8fee3f2d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2041.png

</div>
⚠️ Repeat the same steps to create the vMotion and VSAN Distributed Port Groups.

The Distributed Port Groups that are going to be used for the Virtual Edge Transport Nodes are slightly different.

Provide a name for the new Distributed Port Group:

<div id="436abf1f-a8f1-4a91-be0a-8a25f41d8b41" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2042.png

</div>
Set the VLAN Type to be VLAN Trunking and specify the VLAN trunk range as provided in the table:

The VLANS that are trunked are the BGP Uplink VLANs, the TEP and RTEP VLANs.

<div id="6027af05-110b-4aaa-a6a2-394a616048ae" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2043.png

</div>
Review the details and click on finish:

<div id="021be3e9-abac-4087-8d87-3df2079449a4" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2044.png

</div>
Verify if the Distributed Port Group has been created successfully:

<div id="7c7f7df7-97c3-4270-a878-9c3884ba51c9" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2045.png

</div>
⚠️ Repeat the same steps to create the second NSXEdgeUplink2 Distributed Port Group.

When all the required Distributed Port Groups are created it should look like this:

<div id="9bc87857-f12d-49ef-aefd-3c71c05a233d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2046.png

</div>
<span id="6efdbf24-493a-47fc-bfad-740d99979c6a"></span>
== STEP 3: Deploy the ESXi ==

Now that your vCenter Server is up and running and reachable the next step is to deploy the (nested) ESXi Compute and Edge hosts. Per Pod I am deploying in total six (nested) ESXi hosts (as per the diagrams in the diagrams section above) For Pod 100 the details for the (nested) ESXi hosts to deploy are found in the table below:

<div id="e1977fa9-85f2-4e34-b269-206a21305bfd" class="collection-content">

<span id="section-1"></span>
====  ====

{| class="wikitable collection-content"
|-
! ESXi Hostname
! VM Name
! vmk0 IP address
! Purpose
|-
| [https://www.notion.so/Pod-100-ESXi-31-f8e5f66bb3564e8f8d2b251ec75ce63a?pvs=21 Pod-100-ESXi-31]
| IH-Pod-100-ESXi-31
| 10.203.100.31/24
| Compute Host
|-
| [https://www.notion.so/Pod-100-ESXi-32-12465a97a36d40de8c8231d6284fb55f?pvs=21 Pod-100-ESXi-32]
| IH-Pod-100-ESXi-32
| 10.203.100.32/24
| Compute Host
|-
| [https://www.notion.so/Pod-100-ESXi-33-dd19b05cb95246ac9044fd6caec038a5?pvs=21 Pod-100-ESXi-33]
| IH-Pod-100-ESXi-33
| 10.203.100.33/24
| Compute Host
|-
| [https://www.notion.so/Pod-100-ESXi-91-c5b2f02bc93b43c7851e74e1b51062ff?pvs=21 Pod-100-ESXi-91]
| IH-Pod-100-ESXi-91
| 10.203.100.91/24
| Edge Host
|-
| [https://www.notion.so/Pod-100-ESXi-92-c122288222094974a854f0065b3bf377?pvs=21 Pod-100-ESXi-92]
| IH-Pod-100-ESXi-92
| 10.203.100.92/24
| Edge Host
|-
| [https://www.notion.so/Pod-100-ESXi-93-2f4d6589fd524644b43cf63bc8605341?pvs=21 Pod-100-ESXi-93]
| IH-Pod-100-ESXi-93
| 10.203.100.93/24
| Edge Host
|}




</div>
⚠️ In this article I am only deploying Compute and Edge Hosts, but the same steps below can also be used to deploy your Management hosts ([https://www.notion.so/Lab-Install-and-configure-a-nested-vSphere-SDDC-fc60530328db4b978f996c049a693621?pvs=21 Figure 2]). It all depends on the amount of available resources you have.

I am using an ova template (Nested_ESXi7.0_Appliance_Template_v1.0)that has been [https://williamlam.com/nested-virtualization/nested-esxi-virtual-appliance provided by William Lam].

<div id="165fd33c-409d-4ed8-8108-1a65c7436f37" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2047.png

</div>
Create a new Virtual Machine:

<div id="352d5be0-92d5-43ed-b738-0df6df89ec73" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2048.png

</div>
Select: Deploy from template:

<div id="1f86bac6-76ac-42c1-8519-41cb65709b10" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2049.png

</div>
Choose the OVA/OVF Template you want to deploy from:

<div id="ede6c2f4-a0b9-4d43-88fc-9b2dad2fb8b0" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2050.png

</div>
Provide a Virtual Machine name:

<div id="b9dc74a4-3926-4a7e-a349-64d31b612893" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2051.png

</div>
Select the correct Resource Pool (the one with your name on it):

<div id="a02c4c41-0d4c-4488-bc29-f2ef44f61f0a" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2052.png

</div>
Review the details:

<div id="7e561817-33df-40bc-a1d4-37b66446bd09" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2053.png

</div>
Accept the licence agreement:

<div id="d78a2136-513d-45b8-8c3f-ef4f3db81ba3" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2054.png

</div>
Select the Storage:

<div id="fc895575-f970-4603-aed1-f8114d6b1644" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2055.png

</div>
Select the destination network:

<div id="d8227e71-9c5d-4cb1-99e1-72be60a06179" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2056.png

</div>
Specify the template specific properties like passwords, IP address, DNS, default gateway settings, etc.:

<div id="f8050128-a07e-4f00-af1f-de4d6dc017cf" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2057.png

</div>
<div id="7aabd53d-8ce9-430c-912d-baf333d159b7" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2058.png

</div>
<div id="31f480ef-1172-400b-b231-1b23cc3d2f5a" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2059.png

</div>
Review the Summary before you start the actual deploy:

<div id="ac81280d-288b-4cfc-a298-27a45747c992" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2060.png

</div>
Now that the first (nested) ESXi host is deployed, we need to add an additional Virtual Network adapter and change the CPU, RAM, and Hard Disk settings. Let's edit the settings the newly created (nested) ESXi host:

<div id="1977de1f-a1f3-45e7-bd41-d51e8503d46f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2061.png

</div>
Add Network Adapter so we can use the first NIC dedicated for management.

<div id="d878c64e-5882-4b79-b972-cb208f231b2d" class="collection-content">

<span id="section-2"></span>
====  ====

{| class="wikitable collection-content"
|-
! vNIC#
! Port Group
|-
| [https://www.notion.so/Network-Adaptor-1-112b7ce0c88e44969ca9105cb887f27d?pvs=21 Network Adaptor 1]
| Pod-100-Mgmt
|-
| [https://www.notion.so/Network-Adaptor-2-d72833a0533e483eb71b739094ac0731?pvs=21 Network Adaptor 2]
| Pod-100-Trunk
|-
| [https://www.notion.so/Network-Adaptor-3-1e2fcf97579e4db49f507a077bde01da?pvs=21 Network Adaptor 3]
| Pod-100-Trunk
|}




</div>
Change the CPU, RAM, and Hard Disk settings:

<div id="785ca217-46b9-4e1f-be16-5311f68b7104" class="collection-content">

<span id="section-3"></span>
====  ====

{| class="wikitable collection-content"
|-
! Property
! 
|-
| [https://www.notion.so/vCPU-5908376c855944beb13251bf09dc363c?pvs=21 vCPU]
| 8
|-
| [https://www.notion.so/RAM-0d6b6af42c4c4a30b557091d9ebb35dc?pvs=21 RAM]
| 16 GB
|-
| [https://www.notion.so/Hard-Disk-1-3fb7c5aaf9894cac9a782c9a24781fb8?pvs=21 Hard Disk 1]
| 8 GB
|-
| [https://www.notion.so/Hard-Disk-2-d21626689891497388a2001fd22051df?pvs=21 Hard Disk 2]
| 20 GB
|-
| [https://www.notion.so/Hard-Disk-3-ce0d1b63ee604715af1969d7aefb2cb0?pvs=21 Hard Disk 3]
| 180 GB
|}




</div>
Edit the VM settings:

<div id="86b99c05-1505-42a2-890d-b5f2e53b5c10" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2062.png

</div>
Now that you have just change the settings, you can use this Virtual Machine and clone this five times and specify the (nested) ESXi host-specific parameters during the clone wizard. Clone the Virtual Machine:

<div id="f5d71e10-c792-423e-b135-c007de2f400c" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2063.png

</div>
Provide a Virtual Machine name:

<div id="09558dcc-c68a-4dee-b788-f891e4b26ac4" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2064.png

</div>
Select the correct Resource Pool (the one with your name on it):

<div id="3f1e7ca1-83c0-4b4c-818f-58af2473c2fb" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2065.png

</div>
Select the Storage:

<div id="db13eba1-a5ed-4a20-907f-137ee0a1d5b7" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2066.png

</div>
As you are cloning, this exact VM and the Virtual Machines will be identical, you don't need any OS or hardware modification, and you can choose for yourself if you want to power the VM on after deployment. I prefer powering them up all at the same time.

<div id="afb81459-8917-4d7e-8790-a327740d2e04" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2067.png

</div>
Specify the template specific properties like passwords, IP address, DNS, default gateway settings, etc. Most of the details are already predefined, the only thing you need to change is the hostname and the management IP address:

<div id="2329ac90-ad40-4803-b5fa-9ffa6ba036f5" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2068.png

</div>
<div id="e64b4795-d0a8-4ec4-a4cf-d63240a74d78" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2069.png

</div>
Now you have ESXI-31 and ESXI-32; repeat the cloning steps for all the (nested) ESXi hosts you required in your SDDC lab / Pod. I deployed everything according to the diagram in Figure 1.

<span id="8bacc7cc-6648-4d29-906a-04839f01fea5"></span>
== STEP 4: Add the ESXi Servers to a vSphere Cluster and configure VSAN ==

<span id="18e70d96-36c2-42c3-88fc-be09bbf0f91c"></span>
=== Add ESXi hosts to vSphere Clusters ===

<div id="6b4f3325-c54b-4d68-8255-857d3024aaf4" class="collection-content">

<span id="section-4"></span>
====  ====

{| class="wikitable collection-content"
|-
! ESXi hostname
! Username
! Password
|-
| [https://www.notion.so/pod-100-computea-1-sddc-lab-c2e985f586704274b7b6335db85244ba?pvs=21 pod-100-computea-1.sddc.lab]
| root
| VMware1!
|-
| [https://www.notion.so/pod-100-computea-2-sddc-lab-9ed5ad7dcd8148809d94f89e732795dc?pvs=21 pod-100-computea-2.sddc.lab]
| root
| VMware1!
|-
| [https://www.notion.so/pod-100-computea-3-sddc-lab-2c227446992c458984a4cb534a2fdd8b?pvs=21 pod-100-computea-3.sddc.lab]
| root
| VMware1!
|-
| [https://www.notion.so/pod-100-edge-1-sddc-lab-63ad8cf8472243b9b0ee80731c027cc0?pvs=21 pod-100-edge-1.sddc.lab]
| root
| VMware1!
|-
| [https://www.notion.so/pod-100-edge-2-sddc-lab-2098287f236a44aaaeb65e83feed0949?pvs=21 pod-100-edge-2.sddc.lab]
| root
| VMware1!
|-
| [https://www.notion.so/pod-100-edge-3-sddc-lab-efdfb10fd37247b1bb599f1243092f78?pvs=21 pod-100-edge-3.sddc.lab]
| root
| VMware1!
|}




</div>
Right-click on the Compute Cluster and select '''Add Hosts'''.

<div id="7722f076-6b4d-449d-927b-88911748370d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2070.png

</div>
Specify the FQDNs for all the hosts you need to add and if the credentials are the same you can check the box and only specify the credentials of the first host you are adding.

<div id="668d4648-58d2-4640-a72e-81f1ea5a33a8" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2071.png

</div>
Accept the SHA1 thumbprints/certificates:

<div id="f9d7fa9b-5363-425c-b9ec-3fa1a033aee7" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2072.png

</div>
Look at the summary:

<div id="a1a6994c-7372-466c-a5fa-9e4b3f897981" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2073.png

</div>
Review the Summary and Finish.

<div id="931f429a-b8f5-44b4-80e7-8e2d49b7b724" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2074.png

</div>
Verify if the hosts are added successfully:

<div id="be25d88d-11e5-434d-866a-e6531f9ae06e" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2075.png

</div>
⚠️ Repeat the same steps to add the ESXi Edge hosts to the vSphere Edge Cluster.

When all the hosts are added to the clusters this should look something like this:

<div id="737ffa85-2075-47aa-8988-68e00c236ac5" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2076.png

</div>
<span id="ed362718-a6f6-49a1-99c1-4e3d5714cda3"></span>
=== Add hosts to VDS and move vmk0 to VDS (Port Group) ===

Now that the VDS is created and the Port Groups are in place and the ESXi hosts are added to the cluster, you can now add the hosts to the VDS and migrate the vmk0 management port to the VDS (Port Group).

Go to the Networking tab and right-click on the VDS and select '''Add and Manage Hosts'''.

<div id="f5bd35a6-fc5b-4587-ad01-2b791f679be9" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2077.png

</div>
Select “Add hosts”:

<div id="70a93d89-72a5-45bc-b41e-a550d6e1194f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2078.png

</div>
Select all the hosts you want to the VDS:

<div id="dc0041c3-9efb-46d4-857f-ab83ba1e6699" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2079.png

</div>
Assign the pNICs (vmnics) to the VDS Uplinks.

In my case I have 5 pNICs available on my ESXi hosts, and I will use vmnic1 and vmnic2 as shown below:

<div id="4e9c85a5-fdf2-4778-87d9-843ffabdc694" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2080.png

</div>
Move the vmk0 from the VSS to the VDS (Management Port Group). Click on “Assign”:

<div id="486ae549-73c4-4022-9d2d-088e00eaa5e4" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2081.png

</div>
Select the Management Port Group and click on “assign” again:

<div id="855f0116-ef08-42eb-b585-075dffcd4069" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2082.png

</div>
You do not have any (Compute) Virtual Machines so there is nothing to migrate:

<div id="998bdcfe-d399-44fc-8671-9d29a8a71af0" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2083.png

</div>
Review the Summary and Finish.

<div id="742e4c9f-8267-4ef6-b74e-ca535ecb8572" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2084.png

</div>
Verify if all the hosts has been added to the VDS correctly:

<div id="fa71601f-40df-4791-8a06-45d1e689b6d4" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2085.png

</div>
<span id="2f471e5f-50da-432e-8f2c-7ab6da7dc275"></span>
=== Create vMotion vmk interface on ESXi hosts ===

To allow Virtual vMotion is is good practice to use a dedicated vmk interface and VLAN for that. The table below will show the IP addresses that I am using per host for the vMotion vmk interfaces.

<div id="22e3d990-f18c-466d-8cf9-aa3d7651e412" class="collection-content">

<span id="section-5"></span>
====  ====

{| class="wikitable collection-content"
|-
! ESXi hostname
! vMotion IP address
! VDS Portgroup
! Subnetmask
! Gateway
|-
| [https://www.notion.so/pod-100-computea-1-sddc-lab-f8c8c6f646b64ffa88ab8bf5cf07c84c?pvs=21 pod-100-computea-1.sddc.lab]
| 10.203.101.111
| vMotion
| 255.255.255.0
| 10.203.101.1
|-
| [https://www.notion.so/pod-100-computea-2-sddc-lab-661ddbc78bec4dcda88d2ebdce082ef3?pvs=21 pod-100-computea-2.sddc.lab]
| 10.203.101.112
| vMotion
| 255.255.255.0
| 10.203.101.1
|-
| [https://www.notion.so/pod-100-computea-3-sddc-lab-d57697f13df240f4a412a985a18455e3?pvs=21 pod-100-computea-3.sddc.lab]
| 10.203.101.113
| vMotion
| 255.255.255.0
| 10.203.101.1
|-
| [https://www.notion.so/pod-100-edge-1-sddc-lab-538951fd3aac46e29e031c9f65d5c906?pvs=21 pod-100-edge-1.sddc.lab]
| 10.203.101.191
| vMotion
| 255.255.255.0
| 10.203.101.1
|-
| [https://www.notion.so/pod-100-edge-2-sddc-lab-c23fdabe38a2425bb76e88bfca10b408?pvs=21 pod-100-edge-2.sddc.lab]
| 10.203.101.192
| vMotion
| 255.255.255.0
| 10.203.101.1
|-
| [https://www.notion.so/pod-100-edge-3-sddc-lab-f82f7ca30f714ababfec15bb7fd6485c?pvs=21 pod-100-edge-3.sddc.lab]
| 10.203.101.193
| vMotion
| 255.255.255.0
| 10.203.101.1
|}




</div>
When you go to the Networking tab and the Distributed Port Groups sub-tab you can right-click on the vMotion Port Group and “Add VMkernel Adapters.

<div id="77c75773-cdba-453c-bbc3-fd2d1ac72636" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2086.png

</div>
Click on “+Attached hosts”:

<div id="158e6346-be1c-4dfc-9e36-864f935ce428" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2087.png

</div>
Select all the hosts you want to add a vMotion vmk interface:

<div id="08a4693f-106e-43f6-b7ec-152411b69b82" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2088.png

</div>
Enable the vMotion service by checking the checkbox:

<div id="4b091654-6a8a-4774-9715-3e4dc3a8633c" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2089.png

</div>
Use static IPv4 settings, and use the IP address settings provided in the table:

<div id="77234512-48b8-4ff9-ae4f-e9c3dc03b895" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2090.png

</div>
Review the Summary and Finish.

<div id="ab07ff0d-4519-439c-b14b-ecd6fa83eae6" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2091.png

</div>
Verify if the vmk vMotion interfaces have a virtual switch port assigned:

<div id="8933e27c-bd88-490f-8905-12ecff47d35d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2092.png

</div>
<span id="0794cd36-9d6f-4803-8386-c74f59a8e88e"></span>
=== Configure vSAN ===

Before you can configure vSAN you need to add a vmk interface dedicated for vSAN. This is similar to the steps you just followed for the vMotion vmk, but now with a different Port Group and VLAN.

<div id="9479c53b-6bb3-4b84-9f21-ea8971e42321" class="collection-content">

<span id="section-6"></span>
====  ====

{| class="wikitable collection-content"
|-
! ESXi hostname
! vSAN IP address
! VDS Portgroup
! Subnetmask
! Gateway
|-
| [https://www.notion.so/pod-100-computea-1-sddc-lab-69fa2c96302444799acfffd7fd6ca38e?pvs=21 pod-100-computea-1.sddc.lab]
| 10.203.102.111
| vSAN
| 255.255.255.0
| 10.203.102.1
|-
| [https://www.notion.so/pod-100-computea-2-sddc-lab-7b75033509384360abadaf5cbe349ebe?pvs=21 pod-100-computea-2.sddc.lab]
| 10.203.102.112
| vSAN
| 255.255.255.0
| 10.203.102.1
|-
| [https://www.notion.so/pod-100-computea-3-sddc-lab-32310ac7d3c9477dace25a3696119411?pvs=21 pod-100-computea-3.sddc.lab]
| 10.203.102.113
| vSAN
| 255.255.255.0
| 10.203.102.1
|-
| [https://www.notion.so/pod-100-edge-1-sddc-lab-bb846e16825941b28f5b4dcb38e5af55?pvs=21 pod-100-edge-1.sddc.lab]
| 10.203.102.191
| vSAN
| 255.255.255.0
| 10.203.102.1
|-
| [https://www.notion.so/pod-100-edge-2-sddc-lab-0e57ff0e02e843e3a0ee84ede262f05b?pvs=21 pod-100-edge-2.sddc.lab]
| 10.203.102.192
| vSAN
| 255.255.255.0
| 10.203.102.1
|-
| [https://www.notion.so/pod-100-edge-3-sddc-lab-f4bc7ec97c10464bb0f4179bea2f5509?pvs=21 pod-100-edge-3.sddc.lab]
| 10.203.102.193
| vSAN
| 255.255.255.0
| 10.203.102.1
|}




</div>
When you go to the Networking tab and the Distributed Port Groups sub-tab you can right-click on the vSAN Port Group and “Add VMkernel Adapters.

<div id="72ac1f34-a367-4c3b-b7c7-8a7eb5c94a2c" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2093.png

</div>
Select all the hosts you want to add a vSAN vmk interface:

<div id="4694d2c0-1dce-49f6-9e1a-4b6c18cd60d8" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2094.png

</div>
Select all the hosts you want to add a vSAN vmk interface:

<div id="51541f6f-252c-4669-ba8d-1466968344f8" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2095.png

</div>
Verify the selected hosts (again):

<div id="b1c06bf0-a0fa-43b2-8d6b-a8c81834abe3" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2096.png

</div>
Enable the vSAN service by checking the checkbox:

<div id="71f153b6-6dbf-474f-940b-d16c3db95b0b" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2097.png

</div>
Use static IPv4 settings, and use the IP address settings provided in the table:

<div id="2ba5a5ab-4609-4a27-aebc-bf2c09938cea" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2098.png

</div>
Review the Summary and Finish.

Verify if the vmk vSAN interfaces have a virtual switch port assigned:

<div id="9f3f20ae-5fb4-4248-ae24-6f1be48dbd91" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%2099.png

</div>
Now that the vSAN vmk is in place you can start to configure vSAN.

Each host has three Disks.

# 1 x 10 GB (ESXi boot disk)

<ol start="2" style="list-style-type: decimal;">
<li>1 x 20 GB (vSAN cache disk)</li></ol>

<ol start="3" style="list-style-type: decimal;">
<li>1 x 180 GB (vSAN capacity disk)</li></ol>

When you look at the Storage Devices on the ESXi hosts it looks something like this:

<div id="827633b2-c1a5-4602-8ca9-87e83ae44fbe" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20100.png

</div>
To enable vSAN select the vSphere Cluster object, and in the configure tab select Services in the vSAN section. Click on “Configure vSAN” to open the wizard.

<div id="e53813f6-1d86-4f9b-99b7-709450c32462" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20101.png

</div>
Select “Single site cluster”:

<div id="4f6f2b4b-a346-43c9-ac83-80a6af708c5e" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20102.png

</div>
Leave all the services settings default:

<div id="68e9f0d1-147c-4879-93f8-6a7a1d8b3f8c" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20103.png

</div>
The wizard will detect what disk is the caching and capacity disk. Just make sure this is correct and change this if required:

<div id="4449c152-d8e1-4b33-a21c-099d63a39bd2" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20104.png

</div>
Review the Summary and Finish.

<div id="f2f39cdb-4bbe-4d0b-83f6-75a9f877ecd0" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20105.png

</div>
Verify if the vSAN datastore is created:

<div id="c63edd28-bccc-4fab-bd69-ae218ff039d4" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20106.png

</div>
You can also verify what hosts are part of this vSAN datastore.

<div id="21642eff-298e-4e3b-99e5-4d1812ccc0a7" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20107.png

</div>
Rename the name of the vSAN datastore.

<div id="f9951f00-33f9-49cb-bed4-559f26f51280" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20108.png

</div>
Name it to something that is related to the cluster name:

<div id="e178a9f3-7880-41ce-888c-0277046149b7" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20109.png

</div>
Verify if the name has been changed:

<div id="66314e09-a197-4da3-95a1-d91236f63479" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20110.png

</div>
⚠️ Repeat the same steps to enable vSAN on the vSphere Edge Cluster.

When you enabled vSAN on the Compute and Edge vSphere clusters your datastores view will look something like this:

<div id="121d2c59-e94f-47ba-b09b-c05b3d9a0c39" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20111.png

</div>
<span id="b8a47ba8-8085-4821-9f8b-326d30fdac54"></span>
== STEP 5: Install the Licenses for the vCenter Server, ESXi Servers and VSAN ==

You must have noticed the message in the orange bar on the top related to Licenses.

<div id="6f30a90d-6f02-4e9d-bf64-90e258f3516a" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20112.png

</div>
For the products above I will need to have three licences:

<div id="c5674e3b-0233-428c-b868-073e80f58ce0" class="collection-content">

<span id="section-7"></span>
====  ====

{| class="wikitable collection-content"
|-
! Product
! License key
|-
| [https://www.notion.so/vCenter-Server-License-4bbe188fe0a24aa2a193bd272e212d3e?pvs=21 vCenter Server License]
| <code>K42HJ-XXXXX-XXXXX-XXXXX-XXXXX</code>
|-
| [https://www.notion.so/ESXi-Server-License-13314cae12484b4e818554e0a8bb9fba?pvs=21 ESXi Server License]
| <code>1J4T3-XXXXX-XXXXX-XXXXX-XXXXX</code>
|-
| [https://www.notion.so/VSAN-License-735788f24a9c47fd92b7239d2aa7ad2d?pvs=21 VSAN License]
| <code>X02TH-XXXXX-XXXXX-XXXXX-XXXXX</code>
|}




</div>
You can add new licenses by either clicking on the button on the top bar, or you can do trough the menu and when you click on “Administration”:

<div id="1448a352-ebc5-48d2-84ff-8a147fbcc712" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20113.png

</div>
Click on “Licenses”:

<div id="ac14a7dc-c2bf-4b6b-b163-0cdfc1a494cf" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20114.png

</div>
Copy/Paste all the license keys:

<div id="22ab95b8-04b8-4196-afd9-bc25a1da5920" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20115.png

</div>
Provide a recognisable license name:

<div id="8f84c357-b1ca-4eae-9cde-636c4652bd28" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20116.png

</div>
Review the Summary and Finish.

<div id="cd3a125a-8da1-47a0-bb50-846325356d6f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20117.png

</div>
Verify if all the licenses has been added correctly:

<div id="93f575bc-8f77-4348-8f48-b0193ea3ea01" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20118.png

</div>
<span id="5d624f16-4a1a-440b-a5bc-0d891c0c3255"></span>
=== vCenter Server ===

Assign the vCenter Server license:

<div id="350f05e9-83df-41d1-8c16-8f7ea92e0af0" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20119.png

</div>
Assign the vCenter Server license:

<div id="0dddea95-3019-4c7a-a675-318753c61c36" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20120.png

</div>
Verify if the vCenter Server license is assigned:

<div id="c67426d4-b038-4edc-a1b0-dcaeb4e6092f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20121.png

</div>
<span id="031916e1-a2ca-4474-9506-c0fdb30806af"></span>
=== ESXi Server(s) ===

Assign the ESXi Server licenses:

<div id="1888a4f3-fb69-4ab8-a890-503fe6d7cf18" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20122.png

</div>
Click yes:

<div id="008f4758-a526-4a97-a7f7-87ed33b28c62" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20123.png

</div>
Assign the ESXi Server licenses:

<div id="eeae9b62-7aba-477f-baad-4bd3fa19b813" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20124.png

</div>
Verify if the ESXi Server licenses are assigned:

<div id="fff8dbdf-f15c-41ff-82e5-7ac3e6bb75f3" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20125.png

</div>
<span id="b44eee28-5008-4750-8f1c-c0e06bb48b32"></span>
=== vSAN ===

Assign the vSAN Server licenses:

<div id="ce8ac87d-480e-4f15-9fb6-8b89b3ede329" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20126.png

</div>
Click yes:

<div id="e5e750bc-a070-4dc6-96fa-41a20299490a" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20127.png

</div>
Assign the vSAN Server licenses:

<div id="ba4681ae-b6d0-45b4-a53b-b158497ae46e" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20128.png

</div>
Verify if the vSAN Server licenses are assigned:

<div id="e2c2eaa6-1872-4f18-89c4-13b8c17fb07a" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20129.png

</div>
Refresh the screen and notice that the orange bar is gone.

<div id="b3bb6408-3ef5-484a-85da-94eb3bec1bb4" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/5/Untitled%20130.png

</div>

'''Continue with >>''' [[Lab: NSX Manager deployment (Single site)]]

[[Category:NSX]]
[[Category:Networking]]
[[Category:VMware]]
[[Category:NSX Academy]]