From the Cisco vManage menu, choose Monitor > Overview, to view the Hero Bar with five panes, which runs across the top of the dashboard screen that displays all the control connections from Cisco vManage to the vSmart controllers, vEdge routers, and vBond orchestrators in the overlay network. The pane also displays the status of the Cisco vManage in the network. Ensure that the connections for all the SD-WAN components are up.

Note	In Cisco vManage Release 20.6.x and earlier releases, the Device Pane is part of the Dashboard > Main Dashboard page.

1. From the Cisco vManage menu, choose Monitor > Overview.

   Cisco vManage Release 20.6.x and earlier: From the Cisco vManage menu, choose Dashboard > Main Dashboard.

2. To view device statistics, click on the number, to display a table with detailed information for each connection.

   

3. The table lists System IP, Site ID, Device Model, Software Version and more. For more device-specific information, click … at the end of each row. From here you can access Device Dashboard, Real Time data, or the SSH Terminal.

   

   The Device Dashboard displays the System Status of the device, the device Module Hardware Inventory information, CPU & Memory real time statistics.

   

   Real Time displays the basic system information of the device such as Site ID, Vbond, Hostname, Latitude, Longitude and more.

   

4. Additional information such as Control Connections over the interfaces of the WAN Edge device can be viewed from Cisco vManage. From the Cisco vManage menu, choose Monitor > Devices.Choose the device from the list and look for device information from the left-side panel.

   Note	In Cisco vManage Release 20.6.x and earlier releases, device information is available in the Monitor > Network page.

   

1. From the Cisco vManage menu, choose Tools > SSH Terminal.

   

2. Choose the WAN Edge from the Device Group.

   To verify if the WAN Edge device has established secure control connections with the SD-WAN controllers, enter the show control connections command.

   

1. From the Cisco vManage menu, choose Monitor > Devices.

   Cisco vManage Release 20.6.x and earlier: From the Cisco vManage menu, choose Monitor > Network.

2. Choose the WAN Edge device.

3. A list of deployed VMs for the device appears on screen. Click … next to the VM to start, stop or restart the device.

   

   The following examples show how to stop a VM and the change in status of the VM.

   

   Note	You can view the VM status by choosing Tools > Discover Network from the Cisco vManage menu. Choose the Device and click Rediscover to sync the latest status.

   

   You can also start, stop or restart the VM using the vmAction vmName Linux actionType STOP/START/REBOOT command. To view the status of the VMs, use the show system:system deployments or show vm_lifecycle deployments all command.

   
   Device# vmAction vmName Linux actionType STOP
   
   Device# show system:system deployments
   NAME   ID  STATE
   --------------------
   ASAv   1   running
   vEdge  2   running
   Linux  -   shut
   
   

This section covers the most common issues that could be encountered during the WAN Edge device onboarding process and recommended resolution to resolve the issues.

1. To verify the WAN Edge device has established a secure control connection with the SD-WAN controllers, enter the show control connections command.

   

2. To verify the device properties used to authenticate WAN Edge devices, enter the show control local-properties command.

   

   In the output, ensure that:

   

   

   • system parameters are configured to include organization-name and site-id

   • certificate-status and root-ca-chain-status are installed

   • certificate-validity is Valid

   • dns-name is pointing to vBond IP address/DNS

   • system-ip is configured and chassis-num/unique-id and serial-num/token is available on the device

   The above parameters must be available on the WAN Edge device to mutually authenticate with the SD-WAN controllers before establishing the connections.

3. To verify the reachability of the vBond controller from the WAN Edge device:

   

4. If a WAN Edge device fails to establish connection with the SD-WAN controllers, enter the show control connections-history command to view the reason for failure. View the LOCAL ERROR and REMOTE ERROR column to gather error details.

   

   Some of the reasons for the WAN Edge device failure to establish control connections with the SD-WAN controllers are listed below:

   CRTVERFL – the error state indicates the WAN Edge device authentication is failing because of a root-ca certificate mismatch between the WAN device and the SD-WAN controller. Use the show certificate root-ca-cert on vEdge devices or show sdwan certificate root-ca-cert on IOS-XE SD-WAN devices to confirm the same certificates are installed on the WAN Edge device and the SD-WAN controllers.

   CTORGNMMIS - the error state indicates the WAN Edge device authentication is failing because of a mismatch organization-name, compared with the organization-name configured on the SD-WAN controller. Use show sdwan control local-properties on vEdge devices and show sdwan control local-properties on IOS-XE SD-WAN devices to confirm all the SD-WAN components are configured with same organization-name across the SD-WAN environment.

   NOZTPEN – the error state indicates the onboarding vEdge device is not part of the authorized whitelist device on the ZTP server. Use show ztp entry on the on-prem ZTP server to verify the device whitelist.

   NOVMCFG – the error status indicates the WAN Edge device has not been attached with a device template in Cisco vManage. This status is seen when onboarding the device using automated deployment options, which is the PnP or ZTP process.

   VB_TMO, VM_TMO, VP_TMO, VS_TMO – the error indicates the WAN Edge device has lost reachability to the SD-WAN controllers.

5. Use the following show commands to verify control connections on the WAN Edge device:

   • show control connections

   • show control connections-history

   • show control connections-info

   • show control local-properties

   • show control statistics

   • show control summary

   • show control valid-vmanage-id

If the root-ca-chain certificates for the onboarding platform is missing, device authentication will fail. A failure in device authentication cannot establish control connection to the SD-WAN controller. The following steps shows how to install root-ca certificate on the device components:

Login into the device and view the root-ca-chain status from the show control local-properties command. The following example is a sample output that shows the root-ca-chain-status is in Not-Installed state.

show control local-properties
personality                      vedge
sp-organization-name             ENB-Solutions -21615
organization-name                ENB-Solutions -21615
root-ca-chain-status             Not-Installed

The following is an example of how to upload the root certificate in NFVIS:

nfvis# request root-cert-chain install scp://admin@10.28.13.168
Uploading root-ca-cert-chain via VPN 0
Enter directory of root CA certificate file : /ws/admin-sjc/
Enter root CA certificate file name (default: root-ca.crt) : TPMRootChain.pem
Copying ... admin@10.28.13.168:/ws/admin-sjc//TPMRootChain.pem via VPN 0
Warning: Permanently added '10.28.13.168' (ECDSA) to the list of known hosts.

WARNING!!!
READ THIS BEFORE ATTEMPTING TO LOGON

This System is for the use of authorized users only. Individuals
using this computer without authority, or in excess of their
authority, are subject to having all of their activities on this
system monitored and recorded by system personnel. In the course
of monitoring individuals improperly using this system, or in the
course of system maintenance, the activities of authorized users
may also be monitored. Anyone using this system expressly
consents to such monitoring and is advised that if such
monitoring reveals possible criminal activity, system personnel
may provide the evidence of such monitoring to law enforcement
officials.

Cisco Acceptable Use Policy:
http://wwwin.cisco.com/c/cec/organizations/security-trust/infosec/policies.html

admin@10.28.13.168's password:
TPMRootChain.pem 100% 7651 1.8MB/s 00:00
Updating the root certificate chain..
Successfully installed the root certificate chain
nfvis#