Table of Contents · service providers to quickly implement and operationalize a hybrid WAN with...

Table of ContentsLab Overview - HOL-2039-01-NET - Building Managed Services with VMware SD-WAN byVeloCloud.......................................................................................................................... 2

Lab Guidance .......................................................................................................... 3Lab Objective .......................................................................................................... 9

Module 1 - VMware SD-WAN Technical Tour (15 minutes) ............................................... 11Introduction to VMware SD-WAN Technical Tour .................................................... 12Conclusion............................................................................................................. 20

Module 2- VMware SD-WAN Edge Install, Configure and Activate (30 minutes)..............21Lab Checklist Walk-Through .................................................................................. 22Installation, setup and verification steps of VMware SD-WAN...............................28Conclusion............................................................................................................. 56

Module 3- VMware SD-WAN Product Tour (iSIM) .............................................................. 57Introduction........................................................................................................... 58Hands-on Labs Interactive Simulation: Features and Product Tour........................59Conclusion............................................................................................................. 60

HOL-2039-01-NET

HOL-2039-01-NET

Lab Overview -HOL-2039-01-NET -Building Managed

Services with VMware SD-WAN by VeloCloud

HOL-2039-01-NET

HOL-2039-01-NET

Lab GuidanceNote: It will take more than 60 minutes to complete this lab. You shouldexpect to only finish 2-3 of the modules during your time. The modules areindependent of each other so you can start at the beginning of any moduleand proceed from there. You can use the Table of Contents to access anymodule of your choosing.

The Table of Contents can be accessed in the upper right-hand corner of theLab Manual.

VMware cloud-delivered SD-WAN by VeloCloud enables enterprises to securely supportapplication growth, network agility, and simplified branch and end-pointimplementations while delivering high-performance, reliable access to cloud services,private data centers, and SaaS-based enterprise applications.

With VMware cloud-delivered SD-WAN, service providers can increase revenue andservice innovation by delivering elastic transport, performance for cloud applicationsand a software-defined edge that can orchestrate multiple services to meet customerneeds.

This lab focuses on building up the SD-WAN infrastructure for SP, MSP and Enterprisecustomer.

Lab Module List:

• Module 1 - VMware SD-WAN Technical Tour (15 minutes) (15 minutes) (Basic)Introduction to SD-WAN Architecture, Components and Deployment Options

• Module 2 - VMware SD-WAN Edge Install, Configure and Activate (30 minutes)(Advanced) Pre-requisites, installation and configuration of SD-WAN.

• Module 3 - VMware SD-WAN Product Tour (30 minutes) (Intermediate) VMware SD-WAN Orchestrator Walk-Thru .

Lab Captains:

• Ramnath Shenai, Senior Technical Product Manager, United States• Rohan Naggi, Senior Technical Product Manager, United States

This lab manual can be downloaded from the Hands-on Labs Document site found here:

http://docs.hol.vmware.com

This lab may be available in other languages. To set your language preference and havea localized manual deployed with your lab, you may utilize this document to help guideyou through the process:

http://docs.hol.vmware.com/announcements/nee-default-language.pdf

HOL-2039-01-NET

HOL-2039-01-NET

http://docs.hol.vmware.com

http://docs.hol.vmware.com/announcements/nee-default-language.pdf

Location of the Main Console

1. The area in the RED box contains the Main Console. The Lab Manual is on the tabto the Right of the Main Console.

2. A particular lab may have additional consoles found on separate tabs in the upperleft. You will be directed to open another specific console if needed.

3. Your lab starts with 90 minutes on the timer. The lab can not be saved. All yourwork must be done during the lab session. But you can click the EXTEND toincrease your time. If you are at a VMware event, you can extend your lab timetwice, for up to 30 minutes. Each click gives you an additional 15 minutes.Outside of VMware events, you can extend your lab time up to 9 hours and 30

minutes. Each click gives you an additional hour.

Alternate Methods of Keyboard Data Entry

During this module, you will input text into the Main Console. Besides directly typing itin, there are two very helpful methods of entering data which make it easier to entercomplex data.

HOL-2039-01-NET

HOL-2039-01-NET

Click and Drag Lab Manual Content Into Console ActiveWindow

You can also click and drag text and Command Line Interface (CLI) commands directlyfrom the Lab Manual into the active window in the Main Console.

Accessing the Online International Keyboard

You can also use the Online International Keyboard found in the Main Console.

1. Click on the Keyboard Icon found on the Windows Quick Launch Task Bar.

<div class="player-unavailable"><h1 class="message">An error occurred.</h1><div class="submessage"><ahref="http://www.youtube.com/watch?v=xS07n6GzGuo" target="_blank">Try watching this video on www.youtube.com</a>, or enableJavaScript if it is disabled in your browser.</div></div>

HOL-2039-01-NET

HOL-2039-01-NET

Click once in active console window

In this example, you will use the Online Keyboard to enter the "@" sign used in emailaddresses. The "@" sign is Shift-2 on US keyboard layouts.

1. Click once in the active console window.2. Click on the Shift key.

Click on the @ key

1. Click on the "@ key".

Notice the @ sign entered in the active console window.

HOL-2039-01-NET

HOL-2039-01-NET

Activation Prompt or Watermark

When you first start your lab, you may notice a watermark on the desktop indicatingthat Windows is not activated.

One of the major benefits of virtualization is that virtual machines can be moved andrun on any platform. The Hands-on Labs utilizes this benefit and we are able to run thelabs out of multiple datacenters. However, these datacenters may not have identicalprocessors, which triggers a Microsoft activation check through the Internet.

Rest assured, VMware and the Hands-on Labs are in full compliance with Microsoftlicensing requirements. The lab that you are using is a self-contained pod and does nothave full access to the Internet, which is required for Windows to verify the activation.Without full access to the Internet, this automated process fails and you see this

watermark.

This cosmetic issue has no effect on your lab.

Look at the lower right portion of the screen

HOL-2039-01-NET

HOL-2039-01-NET

Please check to see that your lab is finished all the startup routines and is ready for youto start. If you see anything other than "Ready", please wait a few minutes. If after 5minutes your lab has not changed to "Ready", please ask for assistance.

HOL-2039-01-NET

HOL-2039-01-NET

Lab ObjectiveObjective

Through this lab end user will go through the SD-WAN journey starting fromunderstanding the SD-WAN technology with a technology walk through and then ahands on lab task of installing an edge device. Topics covered are

1. Understand VMware SD-WAN solution2. What makes up the VMware SD-WAN?3. Technical Walk-Through4. How to bring up the infrastructure/components for VMware SD-WAN

For the hands on lab task, Install and Configure a VMware SD-WAN branch Edge devicein a VMware ESXi 6.5 environment. The management plane component - VMware SD-WAN Orchestrator (VCO) and control plane element - VMware SD-WAN gateway (VCG)are already installed in the lab.

In hosted environment, Orchestrator and Gateway are hosted and managed by VMware.In an Hybrid deployment model, Orchestrator is hosted/managed by VMware, Gateway'sare installed and configured by SP/MSP. In an fully On-premise deployment approach, allthe 3 components are hosted and managed by an enterprise.

For this lab, we can think of this as an hosted deployment approach, were in theorchestrator and gateway are installed/configured and now through this lab, enterpriseadministrator will go ahead with the install and configure of Edge device on Branch site.

VMware SD-WAN Edge Consumption Model (DeploymentOptions)

Before we dive into install and configure for edge device on branch site, lets understanddifferent consumption model for edge device.

VMware SD-WAN by VeloCloud provides multiple flexible options when it comes to edgedeployments. This allows VMware's SD-WAN solution to expand and work for multiplecustomer use-cases.

1. Pre-installed appliance : With this option; a customer buys an Edge appliancedirectly from VMware or Dell. The edge software would be installed bare-metal on theplatform.

2. Software Installation : Suitable for virtualization or NFV based environments;supported hypervisors include VMware ESXi and KVM. Customers would need to buy

HOL-2039-01-NET

HOL-2039-01-NET

their own hypervisor license. As part of this lab exercise; our focus would be toaddress this deployment option.

3. Market place : Suitable for deployments wherein customer's workloads are in publiccloud providers. Supported public cloud entities are Amazon's AWS and Microsoft'sAzure. VMware's SD-WAN edge images are available under both Amazon and Microsoft'smarketplace. The license required for compute resources for the cloud provider needs tobe purchased by the customer.

Intended Audience

This lab is geared towards understanding the infrastructure of VMware SD-WAN solution.The lab is a good candidate to be done by a Network Engineer/Designer/Architectmanaging their own Enterprise network or an MSP (Managed Service Provider), SP(Service Provider) engineer managing their customer's SD-WAN network.

Once the lab is complete, you would benefit from a holistic understanding of howVMware SD-WAN components are installed.

HOL-2039-01-NET

HOL-2039-01-NET

Module 1 - VMware SD-WAN Technical Tour (15

minutes)

HOL-2039-01-NET

HOL-2039-01-NET

Introduction to VMware SD-WANTechnical TourThis Module contains the following lessons:

• Introduction to VMware SD-WAN• VMware SD-WAN Architecture and Components• SDN Principles• Components• VMware SD-WAN Architecture• Enterprise Architecture (Over the Top)• Service Provider Architecture (SP)• VMware SD-WAN Infrastructure Deployment Options• Traffic flow

Introduction to VMware SD-WAN

In December 2017, VMware acquired VeloCloud, the market leader in cloud-deliveredSD-WAN that enables enterprises and service providers to deploy flexible, secure WANconnectivity. VeloCloud’s cloud-delivered SD-WAN enables enterprises to securelysupport application growth, network agility, and simplified branch and end-pointimplementations while delivering high-performance, reliable access to cloud services,private data centers and SaaS-based enterprise applications.

With VeloCloud cloud-delivered SD-WAN, service providers can increase revenue andservice innovation by delivering elastic transport, performance for cloud applicationsand a software-defined edge that can orchestrate multiple services to meet customerneeds. By acquiring VeloCloud, VMware will build on the success of the industry’sleading network virtualization platform – VMware NSX – and expand the company’snetworking portfolio to address end-to-end automation, application continuity, branchtransformation and security from the data center to cloud edge. This acquisition willfurther strengthen VMware’s position in leading the market transition to a software-defined future, and will enable enterprises to bring their businesses into the digital erawith networking that is ubiquitous, open, programmable and secure by default.

Service providers can continue to leverage their investment in their MPLS networks,while gradually and seamlessly integrating SD-WAN technology into their network. Themultitenant architecture and centralized management of the SD-WAN solution enablesservice providers to quickly implement and operationalize a hybrid WAN with MPLSservice. Service providers can quickly meet the customer demand and protect andaugment their existing MPLS revenue. SD-WAN also lays a foundation for the serviceprovider to transform their network to become an extensible, service-aware platformthat supports their customers’ adoption of cloud services and SaaS applications. Thebranch office WAN is in transition as SD-WAN improves the economics and quality of

HOL-2039-01-NET

HOL-2039-01-NET

WAN connections and makes access to the cloud easier and better performing. Alongthese lines, the SD-WAN solution offers enterprise-grade performance, security,visibility, and control over both Internet and private networks, combining the reliabilityof MPLS private networks with the flexibility and cost savings of the Internet

VMware SD-WAN offers clear advantages for very large and multinational organizationswith thousands of existing branches, large annual numbers of new and decommissionedbranches, long-term contractual provider agreements, global reach and substantialinfrastructure investment.

VMware SD-WAN Architecture and Components

SDN Principles

The VMware SD-WAN solution employs a strictly segregated control and data plane,mirroring SDN principles.

This means that they can independently fail or be compromised without affecting theother plane. Should the control / Management plane partially fail, all Edges will continueto operate with their last known configuration and can still make independent steeringdecisions based on the last known policy. During this time, an administrator would notbe able to make configuration changes or monitor network performance. TheOrchestrator does provide the ability to back up its database and as such, restore thesystem to recover from a catastrophic failure. In addition, a Disaster Recovery functionis available that allows failover of the controller functions to a standby node, allowing tostandup a new Orchestrator.

HOL-2039-01-NET

HOL-2039-01-NET

Components

VMware SD-WAN by VeloCloud provides a complete Cloud-Delivered solution thatdramatically simplifies the WAN by delivering enterprise grade performance, visibilityand control over both Internet and private networks, combining the economy of theInternet with the flexibility of the cloud.

The Service is comprised of:

1. VMware SD-WAN Orchestrator2. VMware SD-WAN Gateway3. VMware SD-WAN Edge

VMware SD-WAN Orchestrator (VCO)

VMWare SD-WAN Orchestrator (VCO) is a cloud or on-premise based management portalthat provides centralized policy management, monitoring, and troubleshooting for theEdge devices and Gateways. All the SD-WAN Edge devices are managed and monitoredvia the Orchestrator portal.

Its multi-tenant architecture and role based access control ensures separation of rolesand responsibilities between various organizations within the operators as well asbetween different customers. Its API driven architecture also means that SP (ServiceProvider) can easily integrate the orchestrator into their operation.

VMware SD-WAN Gateway (VCG)

These gateways are deployed managed and maintained by VMware and aregeographically dispersed around North America & the World. They are designed to besecure, resilient and redundant. Each Edge CPE device, once activated, automatically

HOL-2039-01-NET

HOL-2039-01-NET

discovers its nearest VCG and also connects to any other VCG needed to establish VPNand cloud connectivity.

VMware Gateway (VCG) is a multi-tenant virtual appliance that is installed into the SPcore network. It terminates the overlay tunnels from the VMware Edge coming over bothprivate (MPLS) and public (Internet) paths. Its multi-tenant architecture provides costeffective, scalable SD-WAN headend sitting in the service provider core network. It alsoseamlessly integrates with existing MPLS VPN network by supporting VRF handoff to SPPE router.

VMware SD-WAN Edge Device (CPE Device)

A high performance branch CPE or Virtual vCPE designed to be very easy to deploy thatmonitors and reacts to link performance in a sub-second manner to ensure greatapplication experience while protecting critical applications from sub-optimalperformance of the underlying transport. The Edge is deployed at the branch and ismanaged centrally through a cloud orchestration portal (VCO). It can support 4 or moreWAN links and/or 4 USB based 3G/4G modems and it automatically measures thebandwidth available on all the WAN links connected (both upstream and downstreambandwidth). The Edge also features built in Wi-Fi (dual radios), Firewall, DHCP, 802.1Xauthentication, and 4-port GE switch with VLAN support.

VMware SD-WAN Architecture

The VMware SD-WAN by VeloCloud™ architecture originated in the cloud andis built on Software Defined Networking (SDN) principles.

VMware SD-WAN is the only SD-WAN solution delivered in the cloud with a separateorchestration plane, control plane and data plane using a secure and scalable cloudnetwork. Cloud-based service delivery, orchestration and analytics create a flexiblearchitecture designed to address the demands experienced by enterprise IT today withthe agility to meet unforeseen future requirements.

VMware SD-WAN support flexible architecture for Enterprise , SP and MSP.

Enterprise Architecture (Over the Top)

VMware SD-WAN provides a transport independent secure overlay enabling the use ofbroadband Internet with or without traditional MPLS, a cloud network for access to bothenterprise and cloud applications, and a business driven orchestration layer forautomation and virtual services insertion.

In an over-the-top architecture (OTT), edges are installed at the customer premises,while consuming control and data plane services residing in the cloud. The VMwareEdge (VCE) establishes an TSL 1.2 session to the VMware Orchestrator(Orchestrator)—mutually authenticating each other during session setup—to receivepolicy updates and upload statistics.

HOL-2039-01-NET

HOL-2039-01-NET

Once the edges are zero touch provisioned, next step is to do Geo-IP lookup for thenearest cloud Gateway and initiate SD-WAN overlay tunnels to these gateways. Edgescan build SD-WAN overlays over both public and private circuits to provide access toapplications and resources hosted in a corporate data center—whether physical, or avirtual data center implemented at an IaaS provider.

Service Provider Architecture (SP)

VMware SD-WAN components can also be integrated into existing service providernetwork architectures . The solution offers a three tier, multi-tenant, role-basedorchestration portal for service providers to manage customers as well as partners.

Unlike OTT deployments, the VMware SD-WAN Orchestrator and Gateways are deployedinside the service provider network offering the SD-WAN service. This deployment modelterminates the overlay at the service provider edge network, allowing access to theMPLS core network. They also provide access to hosted services attached to thecustomer context of the core network.

HOL-2039-01-NET

HOL-2039-01-NET

VMware SD-WAN Infrastructure Deployment Options

VMware SD-WAN provides the flexibility for multiple deployment options based on thecustomer need.

The are three deployment options:

1. Hosted2. Hybrid3. On-Premise

1. Hosted Deployment Option: VMware SD-WAN components such as Orchestratorand Gateways are hosted and managed by VMware. Edge device can be deployed at thecustomer premise or in the public cloud infrastructure.

2. Hybrid Deployment Option: VMware SD-WAN components are jointly operated byVMware or SP/MSP.

For example, SD-WAN Orchestrator is managed and monitored by VMware as opposedto Gateways installed and managed by SP/MSP. In this case, both the SD-WANOrchestrator and Gateways can leverage the multi-tenant capabilities.

In this deployment option, Gateways are refereed to as Partner Gateway.

Edges are CPE devices installed at customer physical location or in public cloud.

HOL-2039-01-NET

HOL-2039-01-NET

3. On-Premise Deployment Option: All the VMware SD-WAN components are hostedand managed by the partner (SP/MSP). In this deployment option, Edges can either bephysical hardware, virtual software (VNF) or in public cloud.

Partner Gateway VS Cloud Gateway

In an hosted environment (OTT), Cloud Gateways are hosted and managed by VMware.They provide secure and optimized access to SaaS applications.

Partner Gateway are typically deployed in an on-premise or hybrid model. Thesegateways are controlled/operated by SP/MSP and provides peering to the SP MPLS Core.

Traffic flow

The VMware SDWAN by VeloCloud solution has a built-in Deep Application Recognition(DAR) engine, which identifies and classifies application traffic traversing the WAN links.The DAR engine is leveraged by the Business Policy framework to influence the priorityof each traffic type, the link steering and preference, rate limiting, and DSCP marking ofboth the inner and outer packet headers, as well as in the Application aware Firewall.

In addition to the DAR engine, traffic flows can also be classified based on traditional5-tuple information as well as the source VLAN, Operating System, Destination FQDN orsource MAC address.Top SaaS apps (TLS encrypted) are identified using public IP andport ranges. Other TLS traffic can be identified based on the certificate information.Example of supported applications are Business applications such as Office 365, Lync/Skype for Business, Salesforce, RTP/RTCP, or Recreational applications such as YouTube,Netflix, Spotify.

Application aware traffic redirection:

HOL-2039-01-NET

HOL-2039-01-NET

1. Low Priority Application traffic is sent over Internet. Edges at branch site will beable to recognize low priority application traffic based on DAR engine and willdirectly sent the application traffic over the WAN Interface without using the SD-WAN Overlay.

2. Traffic destined to Cloud is sent via VMware Cloud Gateway. As these cloudGateways are globally dispersed and strategically placed in close proximity toSaaS providers, these gateways provide secure and optimized access to SaaSapplications.

3. Traffic destined to enterprise on-premise applications are backhauled to regionaldatacenter utilizing the SD-WAN overlay tunnels. For this VMware SD-WAN DMPO(Dynamic Multi-Path Optimization) feature is leveraged.

VeloCloud Dynamic Multi-path Optimization (DMPO) enables application-awaredynamic per-packet steering, on-demand remediation and overlay Quality ofService; DMPO ensures optimal SD-WAN performance for the most demandingapplications over any transport (Internet or Hybrid) and any destination (On-Premises or Cloud).

HOL-2039-01-NET

HOL-2039-01-NET

ConclusionThis concludes our first chapter on the Overview of SD-WAN including areview of the architecture, Components and deployment options.

You have finished Module 1

Congratulations on completing Module 1.

If you are looking for additional information on VMware SD-WAN by VeloCloud, try one ofthese:

• Click on this link• Or VMware SD-WAN Solution Overview

Proceed to any module below which interests you most.



• Module 3 - VMware SD-WAN Product Tour (30 minutes) (Intermediate) . This willtake you through the product tour using the VMware SD-WAN Orchestrator.

How to End Lab

To end your lab click on the END button.

HOL-2039-01-NET

HOL-2039-01-NET

https://www.velocloud.com/products

https://www.velocloud.com/content/dam/digitalmarketing/velocloud/en/documents/brief-enterprise-wan-agility-simplicity-performance.pdf

Module 2- VMware SD-WAN Edge Install,

Configure and Activate(30 minutes)

HOL-2039-01-NET

HOL-2039-01-NET

Lab Checklist Walk-ThroughBefore we start with our lab exercises; let us walk-through Product Pre-requisite, somepreliminary checks and confirm the HOL environment is ready for us to begin.

We will check:

(A) Product Pre-requisite. What resources (CPU,Memory etc) are required to run theVirtual Edge on ESXi?

(B) Preliminary checks for the HOL lab envirnment:

• VMware SD-WAN Orchestrator is accessible by logging on to the Orchestrator• VMware vCenter is accessible• VMware SD-WAN VM's Orchestrator and Gateway are powered on and running.• VMware SD-WAN edge image is accessible.

Product Pre-requisite for VMware SD-WAN Virtual Edge

Before diving into details of VMware SD-WAN by VeloCloud, this section will reviewresource requirements. Specifically for activating an edge device on ESXi resourcerequirement for the VMware SD-WAN virtual Edge include:

• 2 x Intel vCPU's (minimum)• For 4x vCPUs and above, Intel DPDK functionality is recommended for optimizing

performance• CPU must support AES-NI, SSSE3 and RDTSC instruction sets• Hyper-threading disabled• CPU's at 2.0 Ghz or higher• 4 GB of memory• 8GB of storage

Supported Network I/O:

SR-IOV, VirtIO, VMXNET3

VMware SD-WAN Orchestrator is accessible

Open Google Chrome

HOL-2039-01-NET

HOL-2039-01-NET

1. Click on the "Google Chrome" icon located at the bottom of the screen.

Open VMware SD-WAN Orchestrator

1. There is a bookmark titled VeloCloud Orchestrator ; a browser would openconnecting to https://vco1.lab.velocloud.org

2. Login using credentials: Username: [email protected] Password:VMware1!

3. Click on Sign In

HOL-2039-01-NET

HOL-2039-01-NET

Confirm VMware SD-WAN Orchestrator is accessable

You will notice under "Monitor" > Edges and other tabs related to SD-WAN configuration.This step confirms that enterprise administrator is able to access the Orchestrator

The customer has already been created named "Global Retail Inc". Upon login, under"Monitor" >> "Edges"; you would notice "VeloCloud Edges have not been configured".This implies the customer Global Retail Inc has no active edges deployed.

VMware vCenter is accessible

HOL-2039-01-NET

HOL-2039-01-NET

Verify access to VMware's ESXi (vCenter). You will verify access to vCenter and VM's pre-configured are accessible too.

1. From the Google chrome browser, Open a new tab2. There is a bookmark titled Region A, click on the bookmark3. Click on RegionA vSphere Client (HTML)

1. A screen would open up "VMware vCenter Single Sign-On". Click on box Alwaysopen these types of links in the associated app

2. Open VMware cip launcher3. Click on the box to enable Use Windows authentication. To login; click Use

Windows Session authentication4. Click on Login

HOL-2039-01-NET

HOL-2039-01-NET

Confirm VM's Orchestrator and Gateway state

Once logged into the vCenter, make sure that the Orchestrator and Gateway VM arepowered on.

1. Once logged in; confirm esx-01a.corp.local host is seen and there are 2 SD-WAN VMs running - VCG-01, VCO-01 , and an single infrastructure VM "lnx-router".

VMware SD-WAN Orchestrator will be used to configure Branch site edge device.

lnx-router VM is the infrastructure VM providing routing and DHCP services to SD-WANcomponents (Edge Device WAN Side interface)

As part of this lab, VMware SD-WAN Orchestrator and Gateway VM's are pre-installedand configured for the end user. In the future labs, End user will have to deploy theseVM's too.

VMware SD-WAN Edge Image is pre-downloaded

1. Verify the necessary images are available. Click on the FileExplorer optionavailable at the bottom of the screen.

Full path for the image location is c:\users\administrator\downloads\images

HOL-2039-01-NET

HOL-2039-01-NET

Verify the necessary images are available.

1. Under the "Main Console", Navigate to Downloads and then Images.2. You will notice the necessary image required for the lab exercise.

Since we are going to do a VMware SD-WAN Edge (VCE) installation on ESXi host you willsee a OVA image.

In real world: you would have to download the image from VMware downloads page.

Now, that all the pre-requisite are checked, let us start executing the lab task.

HOL-2039-01-NET

HOL-2039-01-NET

Installation, setup and verificationsteps of VMware SD-WANSummary Steps

This module will take you through the following steps for configuring SD-WAN:

1. Download the OVA file from VMware downloads page2. From the VMware SD-WAN Orchestrator, Create a Site with Virtual Edge as

edge option - VMware SD-WAN Orchestrator acts as the single pane of glass forthe entire enterprise's SD-WAN network. Orchestrator is used to carrying outtasks for day-0 installation as well as day-1 to day-n monitoring and analyticsactivities.

3. From vCenter, Deploy the Virtual Edge using the OVA File - Since thedeployment is to be done on VMware's ESXi environment, using vCenter, edgeOVA file would be deployed.

4. From vCenter, Power on the Edge device and Verify the Activation of theSD-WAN Edge device.

5. From the VMware SD-WAN Orchestrator, Verify SD-WAN Overlay: Once theVMware SD-WAN edge is installed and brought up, SD-WAN overlays would beverified between the edge to the already installed gateway. The verification isdone again from the single pane of glass - VMware SD-WAN Orchestrator.

Download the OVA

Access the VMware SD-WAN Edge device software image. Typically available on theVMware download page. To save time, for this lab task, image has been pre-downloaded to the desktop "C:\download\image" folder edge-VC_VMDK-x86_64-3.2.2-16-R322-20190212-GA-updatable-ext4.ova

HOL-2039-01-NET

HOL-2039-01-NET

From the Windows task bar, click on the File explorer icon to access C:\download\images

From the File Explorer, access the images folder for Image file.

Create a Site from VMware SD-WAN Orchestrator

Access the VMware SD-WAN Orchestrator from the google chrome browser.Make sure you are logged in as [email protected], password=VMware1!

How to Access the VMware SD-WAN Orchestrator?

HOL-2039-01-NET

HOL-2039-01-NET

Follow the steps mentioned in Module 2: Lab Checklist Walk-Through"(B) Preliminary checks for the HOL lab environment"

If you have skipped the Lab Pre-requisite section, then use the steps here to login toorchestrator.

Click on the "Google Chrome" icon located at the bottom of the screen.

There is a bookmark titled "VeloCloud Orchestrator"; a browser would open connectingto "https://vco1.lab.velocloud.org"

Login using credentials:

Username: [email protected]

Password: VMware1!

Note: The customer has already been created named "Global Retail Inc". Upon login,under "Monitor" >> "Edges", you would notice "VeloCloud Edges have not beenconfigured". This implies the customer Global Retail Inc has no active edges deployedtoday.

Create a New Branch Site: (BR1-VCE-01)

1. Under the VMware SD-WAN Orchestrator screen; click on "Configure"

HOL-2039-01-NET

HOL-2039-01-NET

◦ Navigate to "Edges"; since there are no active edges installed for customer"Global Retail Inc" no edges would show up here.

2. Click on "New Edge"; a new dialogue box will open up.

3. Provision the new Edge - Branch-VCE-01, Under the new dialogue titled"Provision New Edge":

◦ Type in Name "Branch-VCE-01";◦ Model "Virtual Edge";◦ Profile "QuickStartProfile"

Do not change any other parameters. The same screen can be used if edges need to beinstalled in High Availability mode for redundancy.

4. Click on "Create"

Branch site name specified at the Orchestrator level can be different than what isconfigured at the Instance level (vCenter Virtual edge deployment).

HOL-2039-01-NET

HOL-2039-01-NET

For example, at Orchestrator level, end user might use "Branch-VCE-01" and at Instancelevel they can use BR1-VCE-01. There is no relation between the naming convention.

5. Create Site will generate an unique Activation Key. End user will see astatement "The edge has been provisioned with activation key xxxx-xxxx-xxxx-xxxx".

6. End user will also notice that the edge status is Pending.

This activation key will be unique per edge, per customer.

Make sure to note down this activation key since this value would be needed later forcopy paste.

You can copy the activation key to the notepad.

Deploy the Virtual SD-WAN Edge using the OVA

Accessing vCenter

HOL-2039-01-NET

HOL-2039-01-NET

The first step involves; accessing the vCenter client.

1. Make sure that there is a separate browser tab with vCenter already opened. Ifnot then refer to the Pre-Requisite Lab on how to access vCenter.

2. Make sure VCO-01 , VCG-01 and Lnx-Router VM are powered on and running

There are 3 VM's running:1. lnx-router2. VCG-013. VCO-01

For this lab, lnx-router VM is providing the routing functionality between differentVMware SD-WAN components. It is also acting as a DHCP Server for WAN Side interface.

Deploy OVF template for Virtual SD-WAN Edge

Read through all the detailed steps before deploying the Virtual edge using thetemplate.

There have been instances were an end user has taken more then 15 minutes to deploythe template and got the error message "Operation failed , Unable to deploy thetemplate".

HOL-2039-01-NET

HOL-2039-01-NET

This is because the OVF template dialog box has timed out. If you encounter this issue,start deploying a new OVF template and it will work.

1. Deploy OVA: Right-click on the host "esx-01a.corp.local"; you will see a drop-down with multiple options. Click on "Deploy OVF Template"; a new dialoguewill open up.

Select the OVF File

HOL-2039-01-NET

HOL-2039-01-NET

1. Choose the OVA file: End user will need to input the OVF File for the VMwareSD-WAN edge device. Select the option "Local File" and click on "Choose Files".

2. Browse to "Downloads > Images". Select the OVA file.3. Click Next

HOL-2039-01-NET

HOL-2039-01-NET

Give a name to the VM

1. Select the location for virtual machine - "RegionA01" , Type in the Virtualmachine name as "Branch-VCE-01"

2. Click "Next".

HOL-2039-01-NET

HOL-2039-01-NET

Select the Computer Resource

1. As a next step, select the compute resource "esx-01a.corp.local".2. Click Next. Validation could take several seconds.

HOL-2039-01-NET

HOL-2039-01-NET

"Review Details" screen will show up, Click Next

HOL-2039-01-NET

HOL-2039-01-NET

Configure Storage

1. Under "Select Storage" for "Select virtual disk format" - select "Thin Provision".Notice VM Storage Policy. Confirm "RegionA01-esxi-01a-Local" is selected.

2. click "Next"

Configure Networking

Before configuring Networking, let us understand how these components are interactingwith each other:

1. All the VMware SD-WAN Components are running Release 3.2.2 GA2. SD-WAN components (VCO,VCG and VCE) are running on their own network. Each

component has their own subnet (for ex: Orchestrator is on 30.30.30.x, Gatewayis 40.40.40.x)

3. Routing between subnets is handled by router: in this lab it is lnx-router VM. VCO,VCG and VCE default gateway points to lnx-router VM. For example: VCO gatewayIP address 30.30.30.1 is configured on lnx-router VM.

4. Additional role for the lnx-router VM is assigning DHCP based IP addresses to theEdge device WAN interfaces.

HOL-2039-01-NET

HOL-2039-01-NET

5. All the SD-WAN components are also configured with Management IP address forSSH Access (out of band management). Management subnet is 192.168.110.x/24.

IP Address Information for VMware SD-WAN Components

VMWare SD-WAN Orchestrator (VCO) Details:

• vAPP name = VM-Network-Velo-InfraLab-VCO• Subnet = 30.30.30.200/24, Gateway = 30.30.30.1

VMWare SD-WAN Gateway (VCG) Details:

• vAPP name = VM-Network-Velo-InfraLab-VCG• Subnet = 40.40.40.100/24, Gateway = 40.40.40.1

VMWare SD-WAN Edge Details (VCE):

VCE (Edge devices) has 2 interfaces: LAN Side and WAN Side. WAN Side interfaces areDHCP-based and lnx-router is providing the IP addresses.

• vAPP Name = VM-Network-Velo-BR1-VCE-LAN• Subnet= 192.168.6.x/24, Gateway = 192.168.6.1

Branch Edge device has 2 WAN interfaces, WAN-1 and WAN-2

• VCE WAN-1 vAPP Name= VM-Network-Velo-BR1-VCE-WAN-1• VCE WAN-2 vAPP Name= VM-Network-Velo-BR1-VCE-WAN-2

Now that we understand the network layout, let us start configuring the networking forthe VMware SD-WAN Virtual edge device.

Next step is Network configuration.

HOL-2039-01-NET

HOL-2039-01-NET

Configure Network

In this step, define the LAN and WAN Interface for the SD-WAN edge device.

1. For this lab task, end user will select:◦ GE1 = LAN Interface=VM Network-Velo-BR1-VCE-LAN◦ GE3 = VM Network-Velo-BR1-WAN-1◦ GE2 = LAN Interface=VM Network-Velo-BR1-VCE-LAN◦ GE4 = VM Network-Velo-BR1-WAN-2

Click Next to move to the next step.

Customize Template

Next is to Customize the template by specifying the following:

In customize template, End user will configure:

• Instance ID = BR1-VCE-01• Orchestrator Address = 30.30.30.200• Activation code = copy paste the activation code from Orchestrator or notepad

HOL-2039-01-NET

HOL-2039-01-NET

• Checkbox for Ignore certificate error = check box enable• Password information = VMware1!• DNS1 information = 192.168.110.10• Edge WAN IP addresses = Select as DHCP

1. Unique Instance name = BR1-VCE-012. Velocloud Orchestrator address = 30.30.30.2003. Activation Key = Enter the activation code from the VMware SD-WAN Orchestrator

(VCO) UI by using Paste operation.4. Scroll down and select Checkbox "ignore VCO certificate"

Branch site name specified at the Orchestrator level can be different than what isconfigured at the Instance level (vCenter Virtual edge deployment).

For example, at Orchestrator level, end user might use "Branch-VCE-01" and at Instancelevel they can use BR1-VCE-01. There is no relation between the namingconvention.

Screen capture showing earlier copy / paste operation for Activation key. Access theOrchestrator UI, select and copy the Activation key. Return to vCenter and paste fromnotepad to VCE activation code section of "Customize Template".

HOL-2039-01-NET

HOL-2039-01-NET

If you have copied the activation key to the notepad, paste from the notepad.

After the activation code is entered and checkbox "ignore VCO certificate" is selected,scroll down the Customize template to enter Password, DNS and WAN IP addressinformation.

Enter the password. This password is used to access the Virtual edge from CLI. For thislab, use the password VMware1!

Confirm the password before you proceed to DNS information.

HOL-2039-01-NET

HOL-2039-01-NET

Enter the DNS information. In this case, end user will add DNS1 and leave the DNS2 asis.

Scroll down to get to the DNS1 IP address setting:

1. Enter 192.168.110.10. This is the lab environment DNS server.2. Leave the DNS2 IP address as is (8.8.4.4)

WAN Interface as DHCP

After the DNS information is entered, scroll down and start entering the WAN IPaddresses for the edge device. WAN interfaces are GE3 and GE4.

Make sure WAN Interfaces GE3 and GE4 are configured as DHCP. These interfaceswill get IP address from the Lnx-router and through these interfaces will have access tothe orchestrator.

HOL-2039-01-NET

HOL-2039-01-NET

For successful activation a single WAN interface is enough.

Scroll down and click next to move to "Final Template Summary" view page.

HOL-2039-01-NET

HOL-2039-01-NET

Final Template summary

1. Confirm final configuration as follows:

2. Click on Finish

If the end user has spent more then 15 minutes for deploying the template, there hasbeen cases were in the template deployment fails because of the dialog box time out.You might see an error message

"Operation failed : Unable to deploy template"

HOL-2039-01-NET

HOL-2039-01-NET

Resolution is to start from step 1 and try to click on finish within 15 minutes. This willhelp deploy the SD-WAN template successfully.

VM Status

Check the Status for VMware SD-WAN Virtual Edge device from the vCenter before theVM is powered on.

HOL-2039-01-NET

HOL-2039-01-NET

Select the VM "Branch-VCE-01" in the navigation pane to view its status.

Switch back to the Velocloud Orchestrator UI. If still showing "Configure" details select"Monitor" to view status.

Before powering on the Branch VM, Check the status of the Branch Site from theVMware SD-WAN Orchestrator UI.

Status shown is "Pending Activation" (mouse hover). After the VM is powered on,Edge device will use the Zero touch provisioning and if successful, Virtual edge devicewill be activated.

Power On the Virtual SD-WAN Edge device and Verify theActivation of Edge device

HOL-2039-01-NET

HOL-2039-01-NET

Power on the VM

Notice a new VM "BR1-VCE-01" under the esx host.

1. Either Right-click on VM and select "Power On" OR use the Green Power button.

Check the Activation Status

After the VM is powered on, the Edge device will start communicating to theOrchestrator as part of the Activation process.

HOL-2039-01-NET

HOL-2039-01-NET

Activation status can be checked from VM Console (CLI) and also from the VMware SD-WAN Orchestrator UI

1. Check the VM Console CLI for the activation process by clicking on the "LaunchWeb Console"

When launching the web console, you might get pop up error. Allow pop ups to viewthe console

From the VM console cli, check for the "Successfully activated .." message. Thismessage indicates that the Edge has been able to establish connection to theorchestrator (30.30.30.200) and activation has been successful.

HOL-2039-01-NET

HOL-2039-01-NET

Check the VCO UI (Orchestrator UI)

HOL-2039-01-NET

HOL-2039-01-NET

1. From the VeloCloud Orchestrator UI (VCO), Monitor>Edges

Click Monitor>Edges to get the current status. Or you in general Refresh canbe used.

HOL-2039-01-NET

HOL-2039-01-NET

Branch Virtual edge SD-WAN device is activated now. Also, it has auto-discovered 2 WANlinks. The same can also be verified from Monitor>Events.

HOL-2039-01-NET

HOL-2039-01-NET

Verify VMware SD-WAN Overlay

After the activation, Edge device will do geo-ip lookup and will create SD-WAN overlaytunnel from WAN links to the VMware SD-WAN gateway.

Next step is to verify SD-WAN overlay tunnel from Edge device to VMware SD-WANgateway.

1. From the Orchestrator UI > Click on Test and Troubleshoot2. Click on the Branch Edge device

3. Scroll down to "List Paths"4. Click on Run

HOL-2039-01-NET

HOL-2039-01-NET

Expected result should be two SD-WAN overlay tunnels from the Edge WAN interfacesto VMware SD-WAN gateway (40.40.40.100/24).

HOL-2039-01-NET

HOL-2039-01-NET

ConclusionThis concludes our module 2 on installing, configuring and verifying anVMware SD-WAN Virtual Edge device on ESxi.

You have finished Module 2

Congratulations on completing Module 2.

If you are looking for additional information on VMware SD-WAN, try this:

• Click on this link

If you are looking for addition information on VMware SD-WAN Edge device datasheet

• Click on this data sheet link




• Module 3 - VMware SD-WAN Product Tour (30 minutes) (Intermediate) Thisproduct tour uses the VMware SD-WAN orchestrator to walk through differentproduct features .

How to End Lab


HOL-2039-01-NET

HOL-2039-01-NET

https://www.velocloud.com/products

https://images.nsx.techzone.vmware.com/sites/default/files/VMware%20SD-WAN%20by%20VeloCloud%20Edge%20Data%20Sheet.pdf%C2%A0

Module 3- VMware SD-WAN Product Tour (iSIM)

HOL-2039-01-NET

HOL-2039-01-NET

IntroductionIn this module, we will take product tour and check-out some of the most useful featuresof the VMware SD-WAN Orchestrator.

HOL-2039-01-NET

HOL-2039-01-NET

Hands-on Labs Interactive Simulation:Features and Product TourThis part of the lab is presented as a Hands-on Labs Interactive Simulation. This willallow you to experience steps which are too time-consuming or resource intensive to dolive in the lab environment. In this simulation, you can use the software interface as ifyou are interacting with a live environment.

1. Click here to open the interactive simulation. It will open in a new browserwindow or tab.

2. When finished, click the “Return to the lab” link to continue with this lab.

The lab continues to run in the background. If the lab goes into standby mode, you canresume it after completing the module.

HOL-2039-01-NET

HOL-2039-01-NET

http://docs.hol.vmware.com/hol-isim/hol-2020/hol-2039-01-nsxsdwan.htm

ConclusionIn this module, we took a look at the SD-WAN Orchestrator and witnessedvarious capabilities and options. Within the VMware SD-WAN Orchestrator(VCO) we are able to deploy a virtual edge on ESXi environment.

You have finished Module 3!

Congratulations on completing Module 3!

If you are looking for additional information on VMware SD-WAN by VeloCloud, try one ofthese:

• Click on this link• Or go to https://tinyurl.com/yd7q2xs7



• Module 2 - VMware SD-WAN Edge Install, Configure and Activate (30 minutes)(Basic) Pre-requisites, installation and configuration of SD-WAN.

• Module 3 - VMware SD-WAN Product Tour (30 minutes) (Intermediate) This willtake you through the product tour using the VMware SD-WAN Orchestrator.

How to End Lab


HOL-2039-01-NET

HOL-2039-01-NET

https://www.vmware.com/products/nsx-sd-wan-by-velocloud.html

https://tinyurl.com/yd7q2xs7

ConclusionThank you for participating in the VMware Hands-on Labs. Be sure to visithttp://hol.vmware.com/ to continue your lab experience online.

Lab SKU: HOL-2039-01-NET

Version: 20191021-184002

HOL-2039-01-NET

HOL-2039-01-NET

http://hol.vmware.com/

Table of Contents · service providers to quickly implement and operationalize a hybrid WAN with...

Documents

Transcript of Table of Contents · service providers to quickly implement and operationalize a hybrid WAN with...