Skip to main content
Cisco SD-WAN
Support
Product Documentation
Viptela Documentation

Restore the vManage NMS

This article describes how to restore the vManage NMS in case the server on which the vManage NMS virtual machine (VM) is running fails. This article provides procedures for restoring a vManage NMS using two different VMware interfaces, vSphere Client and vSphere Web Client.

Note: If you are creating a new vManage NMS as part of an initial network bringup, see Bringup Sequence of Events and Create vManage NMS VM Instance.

The vManage NMS database is the repository for the overlay network device configurations, events, alarms, and monitoring information. The vManage NMS database is stored on a separate virtual hard disk on the vManage NMS server; specifically, it is stored on hard disk 2. Hard disk 1 contains the Viptela operating system software.

We recommend that you set up periodic crash-consistent backups of the vManage NMS database. (In a crash-consistent backup, all the VM's data are captured at exactly the same time.) Then, if the vManage NMS server fails, you simply create a new vManage NMS instance and attach the vManage NMS database backup to that instance.

The procedures in this article each encompass both of the following scenarios:

  • If you have a backup of the vManage NMS database, you create a new vManage NMS and attach the disk that contains your backup database.
  • If you do not have a backup of the vManage database, you create a new vManage NMS and create a new virtual hard disk for the database.

Restore vManage NMS Using vSphere Client

  1. Create a vManage VM instance. See Launch vSphere Client and Create a vManage VM Instance, in Create a vManage VM Instance.
  2. In the left navigation bar of the vSphere Client screen, select the vManage VM instance you just created, and click Edit virtual machine settings.
    G00033.pngThe vManage - Virtual Machine Properties screen is displayed.
  3. Click Add to add a new virtual disk, and click OK.
    G00072.pngThe Add Hardware window opens with the Select a Disk screen displayed. If you have a backup of the vManage NMS database, complete Step 4. If you do not have a backup database, skip to Step 5.
  1. If you have a backup of the vManage NMS database, complete the following steps:
    1. In the Select a disk screen, select Use an existing virtual disk, and click Next.
      G00039.pngThe Select Existing Disk screen is displayed.
    2. Click Browse.
      G00036.pngThe Browse Datastores window opens and displays the datastores on the server
    3. Navigate to the location of your backup database, and click OK.
      G00037.png
    4. In the Select Existing Disk screen, click Next.
      G00038.pngThe Advanced Options screen is displayed. Skip Step 5 and proceed to Step 6.
  2. If you do not have an existing vManage NMS database, you must create a new virtual disk for the vManage database:
    1. In the Select a Disk screen, select Create a new virtual disk and click Next.
      G00071.pngThe Create a Disk screen is displayed.
    1. Enter a disk capacity for the vManage database of 100 GB, and click Next.
      G00070.pngThe Advanced Options screen is displayed.
  3. In the Advanced Options screen, select IDE for the virtual device node, and click Next.
    G00035.pngThe Ready to Complete screen is displayed.
  4. Click Finish.
    G00034.png The data volume is added to the vManage NMS.
  5. To verify that the new disk has been created, in the vManage Virtual Machine Properties screen, select the Hardware tab. Hard disk 2—the virtual disk that stores the vManage database—is shown in the hardware list.
    G00054.png
  6. In the left navigation bar of the vSphere Client, select the vManage VM instance you just created, and click Power on the virtual machine.
    vSphere Client-vSmart-Demo.png

    The vManage​ virtual machine is powered on.

  7. Select the Console tab to connect to the vManage console. The vManage console is displayed.
    Console.png
  8. At the vManage login prompt, log in with the default username, which is admin, and the default password, which is admin. The system prompts you to select the storage device to use.
    G00057.png
  1. Select the appropriate storage device.
  2. In response to the question Would you like to format x?:
    • If you attached an existing disk with a backup of the vManage database, type n.
      G00059.png
    • If you created a new virtual disk for the vManage database, type y.
  3. Configure the vManage NMS. See vManage NMS Initial Configuration.
  4. Generate a certificate for the new vManage NMS. See Generate vManage Certificate.
  5. Add the serial number of the new vManage NMS to all the vBond orchestrators in the overlay network, as described later in this article.

Restore vManage NMS Using vSphere Web Client

  1. Create a vManage VM instance. See Launch vSphere Client and Create a vManage VM Instance, in Create a vManage VM Instance.
  2. Log in to the vSphere Web Client.
  3. Select the VM instance for your vManage NMS.
    G00049.png
  4. Click the Manage tab, and click Edit. The Edit Settings screen is displayed with the Virtual Hardware tab selected.
  5. If you have a backup of the vManage NMS database, attach it to the new vManage VM. If you do not have a backup database, skip to step 6 and create a new virtual disk for the database.
    1. In the New device field at the bottom of the screen, click Select. A pop-up menu opens.
      G00050.png
    2. From the pop-up menu, select Existing Hard Disk. The Select File window is displayed.
    3. In the Select File window, under Datastores, navigate to and select the appropriate .vmdk file, and click OK.
      G00051.png
  6. If you do not have an existing vManage NMS database, create a new virtual disk for the vManage NMS database:
    1. In the New device field at the bottom of the screen, click Select. A pop-up menu opens.
    2. From the pop-up menu, select New Hard Disk.
      G00068.png
    3. In the New Hard Disk field, enter a size for the new virtual disk of 100 GB.
      G00069.png
    4. Click OK.
  7. From the New Hard Disk section, under Virtual Device Node, select IDE 1, and click OK.

G00052.png

  1. From the vSphere Web Client Navigator, select the datacenter that is hosting the VM and then select Open Console from the menu. The vManage console is displayed.
  2. At the vManage login prompt, log in with the default username, which is admin, and the default password, which is admin. The system prompts you to select the storage device to use.
  3. Select the appropriate storage device:
    G00058.png
  1. In response to the question Would you like to format x?:
    • If you attached an existing disk with a backup of the vManage database, type n.
      G00060.png
    • If you created a new virtual disk for the vManage database, type y to reformat the disk.
  2. Configure the vManage NMS. See vManage NMS Initial Configuration.
  3. Generate a certificate for the new vManage NMS. See Generate vManage Certificate.
  4. Add the serial number of the new vManage NMS to all the vBond orchestrators in the overlay network, as described below.

Add vManage NMS Serial Number to vBond Orchestrators

When you generate a certificate for a new vManage NMS with a new database, the serial number from the certificate is automatically sent to the vBond orchestrators. However, when you create a new vManage NMS and attach an existing database, you must manually send the new serial number to each vBond orchestrator to overwrite the serial number of the previous vManage NMS.

If you have the management IP address for the vBond orchestrator, you can use vManage NMS to send the serial number to each vBond orchestrator. Otherwise, you must use the CLI.

If you have the management IP address for the vBond orchestrator:

  1. In vManage NMS, select the Configuration ► Devices screen.
  2. From the Devices title bar, select Controllers.
  3. Select the vBond orchestrator.
  4. Click the More Actions icon to the right of the row and select Edit.
  5. Enter the management IP address, username, and password for the vBond orchestrator.
  6. Click Save.
  7. Select the Configuration ► Certificates screen.
  8. From the Certificates title bar, select Controllers.
  9. Click Send to vBond to send the new vManage NMS certificate to the vBond orchestrator.

If you do not have the management IP address for the vBond orchestrator:

  1. Find the serial number for the new vManage NMS:
    1. In vManage NMS, select the Configuration ► Certificates screen.
    2. From the Certificates title bar, select Controllers.
    3. Select the vManage NMS and make a note of the serial number that is displayed in the Certificate Serial column.
  2. Select the Tools ► SSH Terminal screen.
  3. Select the vBond orchestrator.
  4. Enter the username and password for the vBond orchestrator and click Login.
  5. Enter the following command to send the certificate serial number for the new vManage NMS to the vBond orchestrator, where number is the serial number that you noted in Step 1:
    vBond# request vsmart add serial-num number
  • Was this article helpful?