Your web browser doesn't support some required capabilities.
This interactive simulation works best with the latest version of Chrome, Firefox, or Safari.
An error occurred. Please visit Hands-on Labs Support to get help or report this issue.
Unable to initialize the simulation player:
Please visit Hands-on Labs Support to get help or report this issue.
Drive it with your mouse, your finger, or just use the arrow keys.
Use Learn mode to learn the demo. The orange boxes show where to click.
Use Present mode to hide the orange boxes and notes.
Click a Shortcut to jump to a specific part of the demo.
This part of the lab is presented as a Hands-on Labs Interactive Simulation. This will allow you to experience steps which are too time-consuming or resource intensive to do live in the lab environment. In this simulation, you can use the software interface as if you are interacting with a live environment.
The orange boxes show where to click, and the left and right arrow keys can also be used to move through the simulation in either direction.
You should now be back at the vSphere Web Client tab in Chrome.
This takes you to the NSX Manager Installation and Upgrade page, which contains five tabs:
Within the Management tab of Installation and Upgrade, there are two additional tabs available:
We now need to configure the appropriate settings for the NSX Controller:
The first controller should start deploying and would typically take approximately 5 - 10 minutes to complete in an actual environment. This wait is skipped for the simulation.
Once the first controller has successfully deployed and the status shows Connected, you can deploy the two additional controllers required for a production NSX environment.
Add a third controller by clicking the "+ ADD" button and entering the following information:
Once all three controllers have been deployed, verify that they are all connected to the NSX Manager instance and the status shows Connected. During deployment you may see the existing Controllers' peer status temporarily change to red. This is a normal part of the deployment process as the Controllers establish synchronization, and should return to green within 1 - 2 minutes.
NSX components are deployed to hosts on a per-cluster basis. You cannot prepare a single host within a cluster.
The VMware Infrastructure Bundles (vibs) are now being pushed down to all ESXi hosts in the cluster. This should only take a few minutes to complete. The prepared hosts do not require a reboot.
Verify that the NSX Installation has completed successfully and shows the version of NSX that you are currently deploying. The Firewall column should also show a status of Enabled. Communication Channels will remain UNKNOWN until setup has been completed.
Next, install the NSX components on the RegionA01-MGMT01 cluster.
As mentioned above, although kernel modules have been pushed and the hosts in these clusters have been prepared for NSX, they are not yet configured for VXLAN. This requires the setup of VXLAN Tunnel End Point (VTEP) vmkNIC ports on each host participating in Logical Networking.
To verify that the VTEPs have configured IP addresses, either via DHCP or an IP Pool:
Finally, let's assign a pool of Segment IDs to be used by NSX when provisioning Logical Switches.
The Segment ID Pool specifies a range of available VXLAN Network Identifiers (VNIs) for use when creating Logical Network segments.
Viewing the Dashboard provides a view of the overall health of the NSX environment. The Dashboard alerts us to any potential issues with the NSX Manager, Controllers, Hosts, Firewall and Logical Switches.
To return to the lab, click the link in the top right corner or close this browser tab.