To create a device template by entering a CLI text-style configuration directly on the Cisco vManage:

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device.

3. Click the Create Template drop-down list and select CLI Template.

4. From the Device Type drop-down list, select the type of device for which you wish to create the template.

5. In the Template Name field, enter a name for the device template.

   This field is mandatory and can contain only uppercase and lowercase letters, the digits 0 through 9, hyphens (–), and underscores (_). It cannot contain spaces or any other characters.

6. In the Description field, enter a description for the device template.

   This field is mandatory, and it can contain any characters and spaces.

7. In the CLI Configuration box, enter the configuration either by typing it, cutting and pasting it, or uploading a file.

8. To convert an actual configuration value to a variable, select the value and click Create Variable. Enter the variable name, and click Create Variable. You can also type the variable name directly, in the format {{variable-name}}; for example, {{hostname}}.

9. Click Add. The new device template is displayed in the Device Template table.

   The Feature Templates column shows the number of feature templates that are included in the device template, and the Type column shows "CLI" to indicate that the device template was created from CLI text.

Edit a Device Template

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates or Feature Templates, and select a template.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device, and Feature Templates is titled Feature.

3. Click …, and click Edit.

You cannot change the name of a device or feature template when that is attached to a device.

Note	You can edit templates simultaneously from one or more vManage servers. For simultaneous template edit operations, the following rules apply:

• You cannot edit the same device or feature template simultaneously.

• When you are editing a device template, all other feature templates attached to that device template are locked and you cannot perform any edit operations on them.

• When you are editing a feature template that is attached to a device template, that device template as well as all other feature templates attached to it are locked and you cannot perform any edit operations on them.

Delete a Template

Deleting a template does not remove the associated configuration from devices.

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates or Feature Templates, and select a template.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device, and Feature Templates is titled Feature.

3. Click …, and click Delete.

4. To confirm the deletion of the template, click OK.

Copy a Template

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates or Feature Templates, and select a template.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device, and Feature Templates is titled Feature.

3. Click …, and click Copy.

4. Enter a new template name and description.

5. Click Copy.

Edit a CLI Device Template

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates, and select a template.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device.

3. Click …, and click Edit.

4. Under Device CLI Template, edit the template.

5. Click Update.

An overlay network might have multiple devices of the same type that have nearly identical configurations. This situation most commonly occurs with routers when the routers that are located in multiple stores or branch locations provide identical services, but each individual router has its own hostname, IP address, GPS location, and other site-specific properties, such as BGP neighbors. This situation also occurs in a network with redundant controller devices, such as Cisco vSmart Controllers, which must all be configured with identical policies, and Cisco vManage systems. Again, each controller has its own individual parameters, such as hostname and IP address.

To simplify the configuration process for these devices, you can create a single configuration template that contains both static configuration values and variable values. The static values are common across all the devices, and the variable values apply only to an individual device. You provide the actual values for the variables when you attach the individual device to the device configuration template.

You can configure a variable value for a parameter in a feature configuration template in two ways:

• Select the parameter scope to be Device Specific—For an individual configuration parameter, select Device Specific to mark the parameter as a variable. Each variable must be identified by a unique text string, which is called a key. When you select Device Specific, an Enter Key box opens and displays the default key. You can use the default key, or you can change it by typing a new string and then moving the cursor out of the Enter Key box.

• Mark a group of related parameters as optional—For some features in some feature configuration templates, you can mark the entire feature as optional. To mark the feature in this way, click Mark as Optional Row in a section of a feature configuration template. The variable parameters are then dimmed, and you cannot configure values for them in the feature configuration template.

You enter the device-specific values for the variables when you attach the device to the configuration, in one of the following ways:

• From a file—When you are attaching a template to a device, you load a file to the vManage NMS. This is an Excel file in CSV format that lists all the variables and defines the variable's value for each device.

• Manually—When you attach a device template to a device, the Cisco vManage prompts you for the values for each of device-specific parameters, and you type in the value for each parameter.

Note	Cisco SD-WAN supports up to 500 variables in a template push operation.

View a Template

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates or Feature Templates, and select a template you wish to view.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device, and Feature Templates is titled Feature.

3. Click …, and then click View.

View Device Templates Attached to a Feature Template

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Feature Templates, and select a template you wish to view.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Feature Templates is titled Feature.

3. Click …, and click Show Attached Device Templates.

   Device Templates dailog box opens, displaying the names of the device templates to which the feature template is attached.

View Devices Attached to a Device Template

For a device template that you created from feature templates:

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates, and select a template you wish to view.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device.

3. Click …, and click Attach Devices.

4. From Attach Devices, click Attached Devices.

For a device template that you created from a CLI template:

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates, and select a template you wish to view.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device.

3. Click …, and then click Show Attached Devices.

To configure a device on the network, you attach a device template to the device. You can attach only one device template to a device, so the template—whether you created it by consolidating individual feature templates or by entering a CLI text-style configuration—must contain the complete configuration for the device. You cannot mix and match feature templates and CLI-style configurations.

On Cisco Cisco vEdge devices in the overlay network, you can perform the same operations, in parallel, from one or more vManage servers. You can perform the following template operations in parallel:

• Attach a device template to devices

• Detach a device template from a device

• Change the variable values for a device template that has devices attached to it

For template operations, the following rules apply:

• When a device template is already attached to a device, you can modify one of its feature templates. Then when you click Update > Configure Devices, all other template operations—including attach devices, detach devices, and edit device values—are locked on all vManage servers until the update operation completes. This means that a user on another vManage server cannot perform any template operations until the update completes.

• You can perform the attach and detach device template operations on different devices, from one or more vManage servers, at the same time. However, if any one of these operations is in progress on one vManage server, you cannot edit any feature templates on any of the servers until the attach or detach operation completes.

Note	You need to recreate the feature templates as the templates created prior to Cisco vManage Release 20.5 fails when attached to the device.

If the device being configured is present and operational on the network, the configuration is sent to the device immediately and takes effect immediately. If the device has not yet joined the network, the pushing of the configuration to the device is scheduled. When the device joins the network, Cisco vManage pushes the configuration immediately after it learns that the device is present in the network.

Attach a Device Template to Devices

You can attach the same templates to multiple devices, and you can do so simultaneously, in a single operation.

To attach a device template to one or more devices:

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates and select the desired template.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device.

3. Click …, and click Attach Devices. The Attach Devices dialog box opens with the Select Devices tab selected

4. In the Available Devices column on the left, select a group and search for one or more devices, select a device from the list, or click Select All.

5. Click the arrow pointing right to move the device to the Selected Devices column on the right.

6. Click Attach.

7. If the template contains variables, enter the missing variable values for each device you selected in one of the following ways:

   • Enter the values manually for each device either in the table column or by clicking ... and Edit Device Template. When you are using optional rows, if you do not want to include the parameter for the specific device, do not specify a value.

   • Click Import File to upload a CSV file that lists all the variables and defines each variable's value for each device.

8. Click Update

9. Click Next.

   If any devices have the same system IP address, a dialog box appears or an error message is displayed when you click Next. Modify the system IP addresses so that there are no duplicates, and click Save. Then click Next again.

10. In the left pane, select the device, to preview the configuration that is ready to be pushed to the device. The right pane displays the device's configuration and the Config Preview tab is selected. Click the Config Diff tab to view the differences between this configuration and the configuration currently running on the device, if applicable. Click the Back button to edit the variable values entered in the previous screen.

11. If you are attaching a Cisco vEdge device, click Configure Device Rollback Timer to configure the time interval at which the device rolls back to its previous configuration if the router loses its control connection to the overlay network. The Configure Device Rollback Time dialog box is displayed.

    1. From the Devices drop-down list, select a device.

    2. To enable the rollback timer, in the Set Rollback slider, drag the slider to the left to enable the rollback timer. When you do this, the slider changes in color from gray to green.

    3. To disable the rollback timer, click the Enable Rollback slider. When you disable the timer, the Password field dialog box opens. Enter the password that you used to log in to the vManage NMS.

    4. In the Device Rollback Time slider, drag the slider to the desired value. The default time is 5 minutes. You can configure a time from 6 to 15 minutes.

    5. To exclude a device from the rollback timer setting, click Add Exception and select the devices to exclude.

    6. The table at the bottom of the Configure Device Rollback Time dialog box lists all the devices to which you are attaching the template and their rollback time. To delete a configured rollback time, click the Trash icon from the device name.

    7. Click Save.

12. Click Configure Devices to push the configuration to the devices. The Status column displays whether the configuration was successfully pushed. Click the right angle bracket to display details of the push operation.

Export a Variables Spreadsheet in CSV Format for a Template

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates and select the desired template.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device.

3. Click …, and click Export CSV.

When you attach a template to a device using the screen, the device might reject the template. One reason that this may occur is because the device template contains incorrect variable values. When a device rejects a template, it reverts to the previous configuration.

To determine why the device rejected the template:

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device.

3. Locate the device. The Template Status column indicates why the device rejected the template.

By default, when you attach a Cisco vEdge device to a configuration template, if the router is unable to successfully start after 5 minutes, it returns to, or rolls back to, the previous configuration. For a configuration that you have created from the CLI, you can change the device's rollback timer:

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates, and choose a device template.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device.

3. Click …, and click Change Device Values.

   The right pane displays the device's configuration, and the Config Preview tab is selected.

4. In the left pane, click the name of a device.

5. Click Configure Device Rollback Timer. The Configure Device Rollback Time pop up page is displayed.

6. From the Devices drop-down list, select a device.

7. To enable the rollback timer, in the Set Rollback slider drag the slider to the left to enable the rollback timer. When you do this, the slider changes in color from gray to green.

8. To disable the rollback timer, click Enable Rollback slider. When you disable the timer, the Password field dialog box appears. Enter the password that you used to log in to the vManage NMS.

9. In the Device Rollback Time slider, drag the slider to the desired value. The default time is 5 minutes. You can configure a time from 6 to 15 minutes.

10. To exclude a device from the rollback timer setting, click Add Exception and select the devices to exclude.

11. The table of the Configure Device Rollback Time dialog box lists all the devices to which you are attaching the template and their rollback time. To delete a configured rollback time, click the Trash icon of the device name.

12. Click Save.

13. Click Configure Devices to push the configuration to the devices. The Status column displays whether the configuration was successfully pushed. Click (+) to display details of the push operation.

For a configuration that you have created from the CLI:

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates, and choose the desired device template.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device.

3. Click ..., and click Change Device Values.

   The right pane displays the device's configuration, and Config Preview is selected.

4. Click the name of a device.

5. Click Config Diff to view the differences between this configuration and the configuration currently running on the device, if applicable. Click Back to edit the variable values entered in the previous screen.

6. Click Configure Devices to push the configuration to the devices. The Status column displays whether the configuration was successfully pushed. Click the right angle bracket to display details of the push operation.

For a configuration that you have created from device configuration templates, if the templates contain variables, the vManage NMS can automatically populate the variables with actual values when you attach the templates to the devices. To do this, you create an Excel file that lists the variable values for each device and save the file in CSV format. You can also enter values for these variables manually.

After you have pushed the configuration to a device, you can change the value assigned to any variable:

1. From the Cisco vManage menu, choose Configuration > Templates.

2. Click Device Templates, and choose the desired device template.

   Note	In Cisco vManage Release 20.7.x and earlier releases, Device Templates is titled Device.

3. Click ..., and click Change Device Values.

   The screen displays a table of all the devices that are attached to that device template.

4. For the desired device, click ..., and click Edit Device Template.

5. In the Update Device Template dialog box, enter values for the items in the variable list.

6. Click Update.

7. Click Next.

8. Click Configure Devices to push the configuration to the device. The Status column displays if the configuration was successfully pushed or not. Click the right angle bracket to display the details of the push operation.

A device can be in either of these configuration modes:

• vManage mode–A template is attached to the device and you cannot change the configuration on the device by using the CLI.

• CLI mode – No template is attached to the device and the device can be configured locally by using the CLI.

When you attach a template to a device from vManage, it puts the device in vManage mode. You can change the device back to CLI mode if needed to make local changes to its configuration.

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

2. Click WAN Edge List, and select a device.

3. Click the Change Mode drop-down list and select CLI mode.

Note	Starting from Cisco IOS XE SD-WAN Release 17.11.1a, click the ... icon adjacent to the device that you want to change from the vManage mode to the CLI mode and click Config Lock (Provision Device). You can use the Config Lock (Provision Device) only if a template is attached to a device.

An SSH window opens. To log in to the device, enter a username and password. You can then issue CLI commands to configure or monitor the device.

To toggle a controller device from vManage mode to CLI mode:

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

2. Click Controllers, and select a device.

3. Click the Change Mode drop-down list.

4. Select CLI mode and then select the device type. The Change Mode - CLI window opens.

5. From the vManage mode pane, select the device and click the right arrow to move the device to the CLI mode pane.

6. Click Update to CLI Mode.

An SSH window opens. To log in to the device, enter a username and password. You can then issue CLI commands to configure or monitor the device.

Note	Starting from Cisco IOS XE SD-WAN Release 17.11.1a, click the ... icon adjacent to the device that you want to change from the vManage mode to the CLI mode and click Config Lock (Provision Device). You can use the Config Lock (Provision Device) only if a template is attached to a device.

The WAN eEdge router authorized serial number file contains the chassis number and the certificate serial numbers of all valid Cisco vEdge devices in the overlay network. You retrieve a serial number file from the Cisco Plug-and-Play (PnP) portal and upload it to Cisco vManage. (For more information abou Cisco PnP, see Cisco Plug and Play Support Guide for Cisco SD-WAN Products.) From Cisco vManage, you send the file to the controllers in the network. This file is required to allow the Cisco SD-WAN overlay network components to validate and authenticate each other and to allow the overlay network to become operational.

To upload the WAN edge router authorized serial number file to Cisco vManage and then download it to controllers in the network:

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

2. Click WAN Edge List, and click Upload WAN Edge List.

3. Under Upload WAN Edge List screen:

   1. Click Choose File and select the WAN edge router authorized serial number file you received from Cisco PnP.

   2. To automatically validate the routers and send their chassis and serial numbers to the controllers, ensure that the Validate the uploaded vEdge List and send to controllers check box is selected. If you do not select this option, you must individually validate each router in Configuration > Certificates > WAN Edge List.

   3. Click Upload.

A list of routers in the network is displayed in the router table, with details about each router.

Starting from Cisco vManage Release 20.9.2, you can monitor the newly added WAN Edge devices in the Monitor > Devices page.

To allow Cisco SD-WAN overlay network components to validate and authenticate each other and to allow the overlay network to become operational, Cisco SD-WAN requires chassis numbers of all valid Cisco vEdge devices in the overlay network.

In addition, certificate serial numbers, are required for all devices.

To upload the WAN edge router authorized serial numbers from a Cisco Smart account to the vManage NMS and then download it to all the controllers in the overlay network:

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

2. Click WAN Edge List, and click Sync Smart Account.

3. In the Sync Smart Account window:

   1. Enter the Username and Password for your Smart account.

   2. To automatically validate the routers and send their chassis and serial numbers to the controllers, check the Validate the Uploaded WAN Edge List and Send to Controllers check box. If you do not select this option, you must individually validate each router in Configuration > Certificates > WAN Edge List.

   3. Click Sync.

A list of routers in the network is displayed in the router table, with details about each router.

Starting from Cisco vManage Release 20.9.2, you can monitor the newly added WAN Edge devices in the Monitor > Devices page.

For vEdge Cloud routers, you need to generate a bootstrap configuration file that you use when you create vEdge cloud VM instances.

To generate and download a bootstrap configuration for one or more vEdge Cloud routers:

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

2. Click WAN Edge List, and click Export Bootstrap Configuration.

3. In the Export Bootstrap Configuration window, in the Bootstrap Configuration field, click Cloud-Init or Encoded String, depending the Hypervisor you are using to bring up the vEdge Cloud router.

4. Select the devices to configure from the Available Devices pane, or click Select All to select all devices.

5. Click the right arrow to move the devices to the Selected Devices pane.

6. Click Generate Configuration. The configurations are downloaded to the vManage NMS.

7. Provision the vEdge Cloud router instance in AWS, KVM, or ESXi with the boostrap configuration. By default, ge0/0 is the device's tunnel interface and is a DHCP client. To use an interface other than ge0/0 as the tunnel interface or to use a static IP as the IP address, reconfigure the device through the CLI. For more information about configuring interfaces, see Configure Network Interfaces.

After you provision the vEdge Cloud router instance, vManage NMS installs a certificate on the device and the device's token changes to a serial number. After the device's control connections to vManage NMS come up, any templates attached to the device are automatically pushed to the device.

In an overlay network, you might have multiple devices of the same type that have identical or effectively identical configurations. For example, in a network with redundant Cisco vSmart Controllers, each controller must be configured with identical policies. Another example is a network with Cisco vEdge devices at multiple sites, where each Cisco vEdge device is providing identical services at each site.

Because the configurations for these devices are essentially identical, you can create one set of feature templates, which you then consolidate into one device template that you use to configure all the devices. You can create an Excel file in CSV format that lists the variables and defines each device specific variable value for each device. Then you can load the file when you attach a device template to a device.

To export data for all devices to a file in CSV format, click the Export icon. This icon, which is a downward-pointing arrow, is located to the right of the filter criteria both in the WAN Edge List and in the Controllers tab.

vManage NMS downloads all data from the device table to an Excel file in CSV format.

View a Device's Running Configuration

Running configuration is configuration information that vManage obtains from the memory of a device. This information can be useful for troubleshooting.

To view a device's running configuration:

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

2. Click WAN Edge List or Controllers, and select the device.

3. Click …, and click Running Configuration.

View a Device's Local Configuration

Local configuration is configuration that vManage has stored for a device. This information can be useful for troubleshooting or for determining how to access a device if, for example, a device is not reachable from vManage.

To view a device's local configuration created using Configuration ► Templates:

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

2. Click WAN Edge List or Controllers, and select the device.

3. Click …, and click Local Configuration.

Copy Router Configuration

When you are replacing one router at a site with another router, you copy the old router's configuration to the new router. Then you remove the old router from the network and add the new one.

To copy the configuration from the old router to the new router:

1. From the Cisco vManage menu, choose Configuration > Certificates.

2. Mark the new Cisco vEdge device as invalid.

3. From the Cisco vManage menu, choose Configuration > Devices.

4. Under WAN Edge List, select the old router.

5. Click …, and click Copy Configuration.

6. In the Copy Configuration window, select the new router.

7. To confirm the copy of the configuration, click Update.

After you have copied the configuration to the new router, you can add the new router to the network. First, delete the old router from the network, as described below. Then add the new router to the network:

1. From the Cisco vManage menu, choose Configuration > Certificates.

2. Mark the new router as valid.

3. Click Send to Controller.

Delete a router if you need to remove it from your deployment. Doing so removes from the WAN edge router serial number list any of the following items that are stored for the router:

• Chassis number

• Certificate serial number

• Subject SUDI serial number

Note	Deleting a router also permanently removes the router configuration from the vManage NMS.

To delete a router:

1. From the Cisco vManage menu, choose Configuration > Certificates.

2. Mark the WAN Edge router as invalid.

3. From the Cisco vManage menu, choose Configuration > Devices.

4. Click WAN Edge List, and select the router.

5. Click ..., and click Delete WAN Edge.

6. To confirm deletion of the device, click OK.

7. From the Cisco vManage menu, choose Configuration > Certificates.

8. Click Send to Controller.

Decommissioning a cloud router (such as a vEdge Cloud router ) removes the device's serial number from Cisco vManage and generates a new token for the device. To do so:

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

2. Click WAN Edge List, and select a cloud router.

3. Click …, and click Decommission WAN Edge.

4. To confirm the decommissioning of the router, click OK.

View Log of Template Activities

A log of template activities contains information that relates to creating, editing, and deleting configuration templates, and the status of attaching configuration templates to devices. This information can be useful for troubleshooting.

To view a log of template activities:

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

2. Click WAN Edge List or Controllers, and select the device.

3. Click …, and click Template Log.

View Status of Device Bringup

You can view the status of the operations involved in bringing a router or controller up in the overlay network. This information can help you monitor these operations.

To view the status of a device bringup:

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

2. Click WAN Edge List or Controllers, and select the device.

3. Click …, and click Device Bring Up.

A Cisco vBond Orchestrator automatically orchestrates connectivity between Cisco vEdge devices and vManage controllers. If any Cisco vEdge device or Cisco vSmart Controller is behind a NAT, the Cisco vBond Orchestrator also serves as an initial NAT-traversal orchestrator. To add a Cisco vBond Orchestrator:

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

2. Click Controllers.

3. Click Add Controller drop-down list, and select vBond.

4. In the Add vBond window:

   1. Enter vBond Management IP Address of the vBond controller.

   2. Enter the Username and Password to access the vBond orchestrator.

   3. To allow the certificate-generation process to occur automatically, check the Generate CSR check box.

   4. Click Add.

5. Repeat Steps 2, 3 and 4 to add additional Cisco vBond Orchestrators.

The new Cisco vBond Orchestrator is added to the list of controllers in the Controllers screen.

Add a vSmart Controller

After the Cisco vBond Orchestrator authenticates Cisco vEdge devices, the Cisco vBond Orchestrator provides Cisco vEdge devices information that they need to connect to the Cisco vSmart Controller. A Cisco vSmart Controller controls the flow of data traffic throughout the network via data and app-route policies. To configure Cisco vSmart Controllers:

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

2. Click Controllers.

3. Click the Add Controller drop-down list and select vSmart.

4. In the Add vSmart window:

   1. Enter the system IP address of the Cisco vSmart Controller.

   2. Enter the username and password to access the Cisco vSmart Controller.

   3. Select the protocol to use for control-plane connections. The default is DTLS. The DTLS (Datagram Transport Layer Security) protocol is designed to provide security for UDP communications.

   4. If you select TLS, enter the port number to use for TLS connections. The default is 23456.

      The TLS (Transport Socket Layer) protocol that provides communications security over a network.

   5. Check the Generate CSR check box to allow the certificate-generation process to occur automatically.

   6. Click Add.

5. Repeat Steps 2, 3 and 4 to add additional Cisco vSmart Controllers. The vManage NMS can support up to 20 Cisco vSmart Controllers in the network.

The new Cisco vSmart Controller is added to the list of controllers in the Controllers screen.

Edit Controller Details

Editing controller details lets you update the IP address and login credentials of a controller device. To edit controller details:

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

2. Click Controllers, and select the controller.

3. Click …, and click Edit.

4. In the Edit window, edit the IP address and the login credentials.

5. Click Save.

Delete a Controller

Deleting a controller removes it from the overlay. Delete a controller it if you are replacing it or if you no longer need it in your network.

To delete a controller:

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

2. Click Controllers, and select the controller.

3. Click …, and click Invalidate.

4. To confirm the removal of the device and all its control connections, click OK.

Configure Reverse Proxy on Controllers

To configure reverse proxy on an individual vManage NMS and Cisco vSmart Controller:

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

2. Click Controllers, and select the controller.

3. Click …, and click Add Reverse Proxy.

   The Add Reverse Proxy dialog box is displayed.

4. Click Add Reverse Proxy.

5. Configure the private IP address and port number for the device. The private IP address is the IP address of the transport interface in VPN 0. The default port number is 12346. This is the port used to establish the connections that handle control and traffic in the overlay network.

6. Configure the proxy IP address and port number for the device, to create the mapping between the private and public IP addresses and port numbers.

7. If the Cisco vManage NMS or Cisco vSmart Controller has multiple cores, repeat Steps 5 and 6 for each core.

8. Click Add.

To enable reverse proxy in the overlay network, from the Cisco vManage menu, choose Administration > Settings. Then from the Reverse Proxy bar, click Edit. Click Enabled, and click Save.