Verity VM Installation (VMware 7.0.3)🔗

Introduction🔗

The Verity management and orchestration system is comprised of two functional components, both of which are instantiated as Virtual Machines (VMs). This document describes the installation and configuration of these VMs within a VMWare ESXi server.

Resource Calculator🔗

Use the Verity VM Resource Calculator to determine system resources.

Virtual Machine Overview🔗

Verity’s two VM functional components:

Virtual Machine	Function
Virtual Network Commander (vNetC)	Orchestration logic, GUI hosting, northbound RESTful API, and databases.
Software Defined LAN Controller (SDLC)	The SDLC VM is comprised of a series of containers that map one-to-one to the managed switch devices. Network discovery, device provisioning, and network assurance. The SDLC serves as the abstraction layer between the managed switch and the vNetC by translating the native management protocols into the vNetC’s NETCONF interface and Yang model.

Virtual Machine Topology🔗

Below is the basic VM and hardware topology for reference:

Recommended Network Management Architecture

Each system requires a management subnet that can support 4 system IP addresses as well as 3 IP addresses per managed switch. The breakdown is as follows:

IP address Allocations for Management	Component	Allocation
Verity System components	vNETC LAN side, SDLC, ACS, GuiA	4 Static Addresses
Managed Switches	Verity Switch Controller	1 Dynamic Address per switch
Managed Switches	Switch in ZTP Process	1 Dynamic Address per switch
Managed Switches	Switch post ZTP Process	1 Static Address per switch

The orchestration platform (vNETC) is configured on the customer’s network with one static IP address to be accessed by users.

The following diagram shows the recommended management network architecture. Variations are possible based on individual customer’s network needs. A second diagram follows with a version showing only one connection to the vNETC.

Prerequisites🔗

vNetC
1. Resolvable, fully qualified domain name
2. Static IP address, gateway, DNS servers
3. Valid Verity license
SDLC
1. IP addressing per table above. NOTE: Must be routable to the vNetC
Controllers (within SDLC)
1. IP Addressing per table above. NOTE: The diagram above shows that the controllers are bridged to NIC 2 of the SDLC. The IP MUST be on the same VLAN/subnet as the SDLC.
ESXi
1. Compute resources meeting Verity requirements based on the number of switches being managed. See Resource documentation for computing CPU and memory needs.
2. Virtual Switch
  1. The vNetC and SDLC should be on the same virtual switch in ESXi or at minimum they must be routable.
  2. Your system requires promiscuous mode to be set to enabled.
Routable or switched network between Verity components and managed switching devices
1. If using a router or firewall between Verity and the switches, the following ports must be allowed to pass.
  1. Port 8080 for gNMI
  2. Port 80 - HTTP
  3. Port 443 - HTTPS
  4. Port 22 - SSH

Obtaining the vNetC and SDLC VM Images and Files🔗

Obtain the following files from BE Networks:

Description	Filename Example	File Type	Notes
vNetC VM Image	vNetC-x_x_x_x.ova	VMware OVA	Resources including vCPU and memory should be adjusted based on iVN resource needs documentation. Networking will need to be altered to the correct virtual switch names used in the server
vNetC “core” Upgrade	core-x_x_x_x- full.tar	tarball	vNetC needs to be updated via GUI SD-Admin immediately after configuration and boot
SDLC VM Image	SDLC-x_x_x_x.ova	VMware OVA	Resources including vCPU and memory should be adjusted based on iVN resource needs documentation. Networking will need to be altered to the correct virtual switch names used in the server
Firmware Upgrade Package	firmware-x_x_x_x.tar	Binary	SDLC should be upgraded via web page immediately after configuration and boot
License	license.cms or sitexxxxx.tar	License file	Is uploaded using GUI

Create the vNetC Virtual Machine🔗

Go to Virtual Machines.
Click Create/Register VM.
In the window that appears select Deploy a virtual machine from an OVF or OVA file.
Click Next.
Enter a name for the VM and upload the vNetC VM Image OVA file via the prompt that says Click to Select file or drag/drop.
Click Next.
Select the desired data store options. Click Next.
Set the Deployment options – Network mappings to the correct Port Group.
This Port Group must be set to promiscuous mode.
Click Next.
Review the settings and if they are correct, click Finish.
The VM creation process will start. When the process completes the progress bar in Recent tasks at the bottom of the screen will say Completed Successfully.

Configure the vNetC from the Console🔗

This step requires you to configure the vNetC with an IP address and Fully Qualified Domain Name (FQDN). To do so, you need to open the VM console.

Select your VM under the Virtual Machine column and click Console/Open browser console.
The VM console appears. The vNetc initialization may take several minutes. While waiting you can press Enter and wait for login prompt.
Login to the vNetC with username root and password vnc1234.
Enter a new password if prompted (new password = vnc1234). If not prompted for the password, you can continue to use the default password or change it with the passwd command.
Run the administration application from the shell by typing ns_admin and pressing Enter.
You are prompted to enter a web user interface admin account password (ex. admin). Document the password you choose as it will be required for GUI authentication later in the process. It is very important that you remember the password!
Press Enter when complete.
In the Admin Menu, select Network Configuration.
Press Enter.
Select FQDN (Fully Qualified Domain Name). Press Enter and set to the desired Fully Qualified Domain Name. If the field is prepopulated, it is required that you replace the default text with your own FQDN.
Verify that WAN IP DHCP is disabled. If WAN IP DHCP is enabled, disable it using the menu.
Select WAN Static IP Settings, press enter.
Enter the following information:
1. IPv4 Address and subnet in CIDR format (x.x.x.x/#)
2. Default Route (Gateway)
3. DNS Server 1 & DNS Server 2 (optional)
Return to the network configuration menu.
Save Settings.
Follow the prompt and the VM will reboot with the new settings configured.

Install the License (required) and Upgrade to the Latest vNetC Core Software🔗

Upgrade the vNetC Core software via the vNetC Web Administration.
Use Chrome Web Browser to access the vNetC IP address that was just configured.
At the login prompt enter username admin and the administration password configured in the menu during installation. These are the credentials you entered in step 3 of Configure the vNetC from the Console.
From the Admin web page, select the Software Packages and Licensing section by double clicking and zooming in.
Select License.
When the window appears, record the information on the Licensing tied to line. Provide this information to BE Networks to obtain your license file.
After you obtain your license.cms file you are required to upload it to the application. Use the drag and drop palette to upload the file or browse for the file. The license file may also be embedded in a \<filename>.tar file and this can also be directly imported and the system will extract the license.cms file.
After you upload the file make sure a success message is presented.
After you upload the license, a tab titled Verity appears at the upper right of the screen (refresh the page if you do not see the tab).
Click Verity and let the screen populate.
After the Verity window has fully completed populating select the Admin tab.
Select Software Packages and Licensing and click vNetC Packages.
Using the Browse Files (or drag and drop) field, import the vNetC Core Upgrade file provided by BE Networks.
When the process is complete you are presented with a success message.
Click the Deploy button.
When prompted to continue, click Yes. The software updates.

Temporary Error Message

You may see an error titled Fatal Error WebSocket Error: Connection lost -2 appear, this is normal. The browser may temporarily say that the site cannot be reached. When the process is done the landing page will render.

Return to the SD ADMIN Menu on the console (If you are logged out, log back in and use the ns_admin menu command).
Select 3 - SD-LAN Features.
Select 8 – Place system in Data Center mode. Check that the field is set to ENABLED.
Select 9 - >>> SAVE SETTINGS <<< to Save Settings.
Select 10 - Return to VNetC Administration Menu menu
Exit from ns_admin by selecting 9 exit but do not logout.
In Chrome, select the Verity button and verify that the system is in Data Center Mode. You may get a prompt saying to upgrade versions. Click the accept button. Also click the tan GUIA Alert growl to clear. Display should look like the following:
Go back to the VNC Console in VMware and type poweroff in the CLI. This will cleanly shutdown the VNC.

Congratulations

You have now successfully installed the VNetC VM.

Create the SDLC Virtual Machine🔗

Go to Virtual Machines. Click Create/Register VM.
In the window that appears select Deploy a virtual machine from an OVF or OVA file.
Click Next.
Enter a name for the VM and upload the SDLC VM Image OVA file via the prompt that says Click to Select file or drag/drop. Click Next.
Select the desired data store options. Click Next.
Set the deployment options. Click Next.
Review the settings and if they are correct, click Finish.
The VM creation process will start. Wait until you see the message Completed Successfully.

Configure the SDLC from the Console🔗

The SDLC must be configured with a Static IP address and the vNetC FQDN.

Select the SDLC from the VMWARE ESXi interface and click the Console tab.
Select Open browser console.
The console appears.

DHCP Error Messages

During the following process DHCP errors may appear. These can be ignored.
Press Enter to get the login prompt, enter username: admin and password: admin.
At the command line interface (CLI) press Enter to see a list of options.
Select Admin and press Enter.

Type Wizard and press Enter.

Prompt	Answer
Do you want to modify hostname	Yes
hostname	Type SDLC (uppercase)
hostname	This is to confirm to change the hostname. Yes
Advertise the Site Management Vlan?	No
Use DHCP for management uplink configuration	No
MGMT IP	Enter management IPIf vNetC and SDLC (GuiA, ACS and DHCP) are on different subnets, it is recommended to have three consecutive static IP addresses on the same subnet for GuiA, ACS and DHCP. However, if vNetC is on the same subnet as GuiA, ACS and DHCP, it is recommended to use four sequential IP addresses.
Default Gateway in CIDR format	Enter the default gateway IP address
ACS IP	Yes
GuiA IP	Yes
DNS server	Enter DNS server IP
Comma Separated NTP Server(s)	Enter vNetC’s IP address
vNetC FQDN or IP	The vNetC IP address
ACS connection path as URL	No
ACS FQDN or IP	Press Enter
ACS connection protocol	choose http or https
ACS connection port number	Press Enter
VCF connection path URL	No
VCF FQDN or IP	Press Enter
DHCP on management VLAN	No
Save the configuration?	Yes

Reboot is required for any changes to take effect. In the console, type reboot and press Enter.

Power On the vNetC🔗

In the VMware ESXi interface power on the vNetC. This takes a few minutes.
Open the GUI and select Admin.
Select the Settings palette.
Set up the Management VLAN used to access the Management network. This field is required even if your management switches are using untagged connections.
For Permissible IP Address Ranges on Managed Devices enter the relevant IP address range (IP address and Mask).

Permissible IP Range Requirement

The range entered MUST include SDLC components.
Click the Save button to save your settings. ().
Go to the Verity tab. If a beige notification box appears in the lower right, click it to close it.
Wait until the process is finished. The application landing page resembles the image below when all processes have been completed.

Update SDLC🔗

Double click the Admin tab.
Double click Software Packages and Licensing.
Double click Firmware Packages.
Select and place the SDLC Binary Firmware Upgrade firmware file on the Drag & Drop area or use the Browse Files button to select the file.
When uploaded, you are prompted with a green success message.
Deploy the firmware by clicking the Deploy button.
A validation message appears. Click Yes.
Wait while the package is applied.
Click the Verity tab.
Double click the VNFs window.
Double click the SDLC section.
Double click the box with the title of SW Version.
Set the Target Package field to the Firmware version and uncheck the box titled Disable Upgrades.
Click the Save button ().
Click Yes to the validation message.
In the window that appears titled GuiA Disconnected, click the icon to refresh.
Let the process complete.
When the window appears the initial state of System Applications are offline. This is expressed by their red LED icons.
When the System Applications come online their LED icons render green. This may take up to 5 minutes.

Site Certificate🔗

In order to avoid having to accept the self signed certificate delivered with the system you will need to add a server.pem file to the system. This will need to be obtained from your internet domain administrator.

Click on the Admin tab.
Select Certificate Management box.
Click on vNetC Server Certificate box.
Drag and drop the server.pem file.

Congratulations

Verity has been successfully installed. Treat yourself to an iced coffee!