This is an interactive simulation
Drive it with your mouse... or your finger
The blue boxes show you where to click
You can also use the arrow keys to step forward or backward
Shortcuts jump to different parts of the simulation
This portion of the lab is presented as a Hands-on Labs Interactive Simulation. This simulation will enable you to navigate the software interface as if you are interacting with a live environment.
The orange boxes show where to click, and you can also use the left and right arrow keys to move through the simulation in either direction.
We will start by viewing the Status of the NSX Controller nodes, and Software Version of the NSX Manager. We will also check our NSX Controllers are all connected. Next, we will view the Logical Switch, and Hosts and Clusters deployments for the environment.
Note: that Network adapter 1 is connected to the Logical Switch vxw-dvs-virtualwire-3-sid-5002-db, and the IP Address is 172.16.10.11
Now we will check the IP configuration of vm1 that is sitting on an NSX Logical Switch.
Note: this displays the IP Address of vm1, 172.16.10.11, sitting on a Logical Switch.
Now we will check the IP configuration of the server VM that is sitting a VLAN-backed port group, and communication to vm1 on a Logical Switch.
Note: this displays the IP Address of the server VM, 172.16.10.12, sitting on a VLAN in the Arista network.
Note: the 100% packet loss between the VMs that are located on the same network segment. This is to show that there is currently no communication between vm1 and server.
Now we will test communication from vm1 to the server VM.
Note: the 100% packet loss between the VMs that are located to the same network segment. This is to show that there is currently no communication between server and vm1.
Now we will configure the Arista switch for the CloudVision and VXLAN services.
Note: typing conf t ( or config terminal) takes the switch into the global configuration mode, where we can change global settings.
Once the CloudVision is enabled, the VXLAN Control service should be enabled.
This step and the following 3 configuration steps are necessary on each TOR switch that needs to connect to the VXLAN Control Service running on CloudVision.
Next we will configure the VXLAN interface.
The Hardware Switch Controller (HSC) provides an integration point between the NSX controllers and the VCS, which provides a means for software and hardware switches to exchange state. Now we will connect the HSC service to an NSX Controller. There are typically several redundant NSX Controllers; but only one of them needs to be specified and the others will be automatically discovered.
Now we must gather the SSL certificate generated by the CVXs OVSDB instance. The SSL certificate generated by the HSC service is used to register CVX with an NSX controller.
----END CERTIFICATE----- HW-GW(config)#
Note: in a real world environment, we would highlight all of the text from the -----BEGIN CERTIFICATE----- to the bottom line, including ----END CERTIFICATE-----, and then right click and copy the text to a notepad or text file.
Having configured the hardware VTEP, the NSX controller needs to be configured to communicate with CloudVision and obtain VTEP information for its inventory of hardware switches. The registration of Arista CloudVision in the NSX UI is relatively straightforward in vCenter.
Our first step to registering our hardware gateway is to add our hosts to the Replication Cluster. The Replication Cluster is the set of Hypervisors that will act as RSNs (Replication Service Nodes).
This completes the registering of a Hardware Gateway to NSX, and our new Hardware Gateway, HW-GW should show up as Up.
Note: that BFD (Bidirectional Forwarding Detection) is enabled by default, meaning the Arista switches will establish BFD sessions to the RSNs. This is critical for protecting against the silent failure of an RSN and VMware will only support configurations running BFD.
Once Arista CloudVision is added to NSX, a Logical Switch can be mapped programmatically to any physical port/VLAN advertised by this gateway. These next few steps will illustrate the mapping of a logical switch to a particular port using NSX UI.
Three columns are available:
Switch: Arista CloudVision will control several hardware switches, so this selection is necessary to identify which one is effected by this configuration.
Port: the HSC provides a list of physical ports available for binding on the physical switch.
VLAN: specify which VLAN tag will be used on the particular port selected. A VLAN value of 0 represents an access port, where the extended Logical Switch traffic will be sent untagged on the port.
Once this selection is done, the Logical Switch is extended to the physical world at Layer 2 on the physical switch/physical port/VLAN specified.
Note: that several bindings can be achieved for a particular Logical Switch
We have now successfully registered an Arista CloudVision hardware switch VTEP to NSX, mapped a Logical Switch to a VLAN port in the Arista CloudVision switch environment, and tested communication between VMs on each side of the virtual and physical networks.
This completes the Hands-on Lab Interactive Simulation of Hardware VTEP with Arista integration.
To return to the lab, click the link in the top right corner or close this browser tab.