Skip to main content
Viptela is now part of Cisco.
Support
Product Documentation
Viptela Documentation

Log In to Viptela Devices

This article describes how to log in to Viptela devices.

Log In to a Device for the First Time

When you first deploy a Viptela overlay network, log in to the vBond orchestrator, vManage NMS, and vSmart controller to manually create the device's initial configuration. For information, see the articles in the Viptela Overlay Network Bringup section that describe how to create the initial configurations for the vBond, vSmart, and vManage devices.

vEdge routers are shipped with a default factory configuration. If you choose to modify this configuration manually, log in through the router's console port, as described below.

Log In to the vManage Web Application Server

The vManage NMS runs as a web application server through which you log in to a running vManage NMS.

In an overlay network with a single vManage NMS, to log in to the NMS, use HTTPS and specify the IP address of the NMS. Enter a URL in the format https://ip-address:8443, where 8443 is the port number used by the vManage NMS. On the login page, enter a valid username and password, and then click Log In. You have five chances to enter the correct password. After the fifth incorrect attempt, you are locked out of the device, and you must wait 15 minutes before attempting to log in again.

In an overlay network that has a cluster of vManage NMSs, the cluster allows you to log in to one of the vManage NMSs that is operating in the role of a web application server. (For information about configuring roles in vManage clusters, see Create a vManage Cluster.) Use HTTPS, specifying the IP address of one of the vManage NMSs, in the format https://ip-address:8443. The cluster software load-balances login sessions among the individual vManage NMSs that are acting as web application servers. You cannot control which of the individual vManage NMSs you log in to.

With a vManage cluster, if you enter invalid login credentials, it might take some time for you to see an invalid login error message, and the amount of time increases as the size of the cluster increases. This delay happens because each vManage NMS attempts sequentially to validate the credentials. If none of the NMSs validates you, only then do you see an invalid login error message.

To determine which vManage NMS you are logged in to, look in the vManage toolbar, which is located at the top of the every screen, to the right of the Viptela logo. The penultimate button shows the name of the NMS you are logged in to. To display more information about this particular NMS server, enter the name of the NMS in the Search filter of the Monitor ► Network screen.

Establish an SSH Session to a Viptela Device

  1. In vManage NMS, select the Tools ► SSH Terminal screen.
  2. From the left pane, select the device on which to collect statistics:
    1. Select the device group to which the device belongs.
    2. If needed, sort the device list by its status, hostname, system IP, site ID, or device type.
    3. Click on the device to select it.
  3. Enter the username and password to log in to the device.

You can now issue CLI commands to monitor or configure the device.

You can also establish an SSH session directly to the Viptela device.

You have five chances to enter the correct password. After the fifth incorrect attempt, you are locked out of the device, and you must wait 15 minutes before attempting to log in again.

Log In to a vEdge Router through a Console Port

For hardware vEdge routers, you can connect the router to a management console through the router's console port. For information, see the planning and installation articles for your hardware router model.

Release Information

Introduced in vManage NMS in Release 15.2.

Additional Information

Viptela Overlay Network Bringup
See the vEdge Router Default Configuration article for your router model.

  • Was this article helpful?