We recommend that you configure the IP address of the Cisco vManage server statically, in its configuration file. Configure this IP address on a non-tunnel interface in VPN 0. We recommend that you do not configure DHCP in VPN 512.

When you start Cisco vManage for the first time, the default IP address of the Cisco vManage server is shown as "localhost". Before you can add a new Cisco vManage server to a cluster, you must change localhost to an IP address:

1. In the Administration > Cluster Management > Service Configuration tab, click Add vManage. The Edit vManage screen opens.

2. From the vManage IP Address drop-down list, select an IP address to assign to the Cisco vManage server.

3. Specify a username and password for the Cisco vManage server.

4. Click Update.

The Cisco vManage server automatically reboots and displays the Cluster Management screen.

To add a new Cisco vManage to the cluster:

1. In the Administration > Cluster Management > Service Configuration tab, click Add vManage. The Add vManage screen opens.

2. From the Cisco vManage IP Address drop-down list, select an IP address to assign to the Cisco vManage server.

3. Specify a username and password for the Cisco vManage server.

4. Enter the IP address of the Cisco vManage you are adding to the cluster.

5. Specify the username and password for the new Cisco vManage server.

6. Select the services to run on the Cisco vManage server. You can select from the services listed below. Note that the Application Server field is not editable. The Cisco vManage Application Server is the local Cisco vManage HTTP web server.

   • Statistics Database—Stores all real-time statistics from all Cisco SD-WAN devices in the network.

   • Configuration Database—Stores all the device and feature templates and configurations for all Cisco SD-WAN devices in the network.

   • Messaging Server—Distributes messages and shares state among all Cisco vManage cluster members.

7. Click Add. The Cisco vManage that you just added then reboots before joining the cluster.

In a cluster, we recommend that you run at least three instances of each service.

View Statistics Database Space Usage

To view the amount of space available and utilized for the statistics database on the local Cisco vManage, in the Administration > Settings > Statistics Database Configuration and click View. The top of the screen shows the maximum space available for the database and the total amount of space currently being utilized. The table shows the disk space currently being utilized for each statistics type.

Configure Statistics Database

To configure the statistics database, which stores all real-time statistics from the local Cisco vManage:

1. In the Administration > Settings > Statistics Database Configuration screen, click Edit. The top of the screen specifies the maximum space available for the database.

2. For each Statistics Type field, assign the amount of storage to allocate, in gigabytes (GB). The total value of all fields cannot exceed the maximum available space.

3. Click Save.

Cisco vManage updates the storage allocations you have assigned once a day, at midnight.

To view detailed information about the services running on a Cisco vManage server:

1. In the Administration > Cluster Management > Service Configuration tab, click the hostname of the Cisco vManage server. The vManage Details screen opens. This screen displays the process IDs of all the Cisco vManage services that are enabled on Cisco vManage.

2. Click Cluster Management in the breadcrumb in the title bar to return to the Cluster Management screen.

View Devices Connected to Cisco vManage

To view a list of devices connected to Cisco vManage:

1. To view a detailed list of all devices connected to Cisco vManage, click the Managed Devices tab in Administration > Cluster Management > Service Configuration screen.

Alternatively:

1. In the Administration > Cluster Management > Service Configuration tab, for Cisco vManage, click the More Actions icon to the right of its row.

2. Click Device Connected.

   If a device is connected to Cisco vManage from a cluster, ensure that you do not configure the data stream hostname to the Cisco vManage system IP address. However, you can configure the management IP address on VPN 512 or internet public IP address on VPN 0. To know more about data stream troubleshooting tools, see Data Stream Troubleshooting Tools FAQ.

1. In the Administration > Cluster Management > Service Configuration tab, for a Cisco vManage, click the More Actions icon to the right of its row and click Edit. The Edit vManage screen opens.

2. Select an IP address to edit.

3. Enter the username and password, and edit the cluster services provided by that Cisco vManage.

4. Click Update.

Update Configuration Database Admin User Credentials

To update the default login credentials of configuration database, access Cisco vManage using a terminal and run the following commands:

Note	Don’t use the SSH terminal option in Cisco vManage to run these commands, because it leads to losing access to the Cisco vManage GUI.

1. Use request nms application-server stop to stop application servers on all Cisco vManage servers.

2. Use one of the following commands to reset the user name and password for the configuration database:

   • For Cisco SD-WAN Release 20.1.1 and earlier:

     request nms configuration-db update-admin-user username username password password newusername newadminuser newpassword newpassword

   • For releases beginning with Cisco SD-WAN Release 20.1.2:

     request nms configuration-db update-admin-user

     When prompted, enter your current user name and password, and your new user name and password.

   Note	When you execute one of the commands described above, Cisco vManage restarts the application server.

   Note	If you do not know the default credentials of config DB, contact Cisco TAC to retrieve the credentials. You cannot use an older user name. Password can only be a mix of characters A to Z ( upper or lowercase), digits 0-9, and special characters @#*.

   Example

   • For Cisco SD-WAN Release 20.1.1 and earlier:

     request nms configuration-db update-admin-user username neo4j password ******** newusername myusername newpassword mypassword

   • For releases beginning with Cisco SD-WAN Release 20.1.2:

     request nms configuration-db update-admin-user

     Enter current user name:neo47

     Enter current user password:123

     Enter new user name:myusername

     Enter new user password:mypassword

After configuration database admin user update, if you are unable to view a specific Cisco vManage instance, use the request nms application-server restart command to restart the application server on that Cisco vManage instance again.

Upgrade Cisco vManage instances in a Cluster

In Cisco vManage, use the Tools > SSH Terminal screen to establish an SSH session with Cisco vManage. From an SSH session, use the following commands to upgrade Cisco vManage instances in a cluster. For information on SSH terminal, see SSH Terminal.

1. Take a snapshots of all vManage servers. Take a backup of the configuration database and save it to location outside of the Cisco vManage server using the following command:

   request nms configuration-db backup path </home/admin/backup_file_name>

2. Ensure that Cisco vManage release 18.3 or later is installed.

3. Copy the Cisco vManage Release 20.3.1 image on each Cisco vManage server in the cluster and install the image on each Cisco vManage server. Do not activate the image at this time.

   request software install <path>

4. Stop NMS services on all Cisco vManage instances in the cluster using the following command on each Cisco vManage instance:

   request nms all stop

5. Activate the Cisco vManage Release 20.3.1 or later image on each Cisco vManage server using the following command. All servers reboot simultaneously.

   request software activate now <version>

6. When each Cisco vManage server is active, confirm the upgrade using the following commands:

   request software upgrade-confirm

   This step is essential to prevent the software from reverting to the previous image version.

7. Use the following command to upgrade the configuration database on any one node in the cluster:

   request nms configuration-db upgrade

   • Enter login credentials, if prompted. Login credentials are prompted if all vManage server establish control connection with each other. After a successful upgrade, all configuration-db services are UP across the cluster and the application-server is started.

   Note

   If you are upgrading a cluster that utilizes Cisco vManage signed certificates and contains Cisco CSR100vs, Cisco ISRv (ENCS), Cisco ASR 1002-X, or any other Cisco IOS XE SD-WAN cloud-based devices, please contact Cisco SD-WAN TAC Support after upgrading the cluster and before upgrading any of these devices to 17.3.x or higher.

Note	If you are upgrading a Cisco vManage cluster setup from Cisco vManage Release 20.3.1 and Cisco vManage Release 20.4.1 to Cisco vManage Release 20.5.1 or higher, you must do it through CLI.

Note	You can check the database upgrade logs at the following location: <vmanage-server>/var/log/nms/neo4j-upgrade.log

For information on how to upgrade Cisco vManage clusters through Cisco vManage GUI, refer to Upgrade the Software Image on a Device

1. In the Administration > Cluster Management > Service Configuration tab, click the More Actions icon to the right of its row and click Remove. The Remove vManage dialog box opens.

2. Enter the username and password to confirm removal of the device from the network.

3. Click Remove.

The Cisco vManage instance is removed from the cluster, the device is invalidated, and the certificates for that device are deleted. The remaining members in the cluster rebalance the network management services.

Note	You can only remove n - 2 Cisco vManage instances from a cluster of n instances. You must retain at least two Cisco vManage instances in a cluster.