You create and store configurations for all devices in the Viptela overlay network—the vManage NMSs themselves, vSmart controllers, vBond orchestrators, and the vEdge routers—on the vManage NMS. When the devices start up, they contact the vManage NMS, and the NMS then downloads the device's configuration to the device. (A device that is starting up first contacts the vBond orchestrator, which validates the device and then sends it the IP address of the vManage NMS.)
The general procedure for creating configuration for all Viptela devices is the same. This article provides a high-level description of the configuration procedure. It also describes the prerequisite steps that must be performed before you can create configurations and configure devices in the overlay network.
High-Level View of Configuration Procedure
All Viptela devices in the overlay network that are managed by the vManage NMS must be configured from the NMS. The basic configuration procedure is straightforward:
- Create feature templates.
Configuration ► Templates ► Feature ► Add Template
- Create device templates.
Configuration ► Templates ► Device ► Create Template
- Attach device templates to individual devices.
Configuration ► Templates ► Device ► Select the template ► Select Attach Devices from the More Actions icon to the right of the row.
Feature templates are the building blocks of a device's complete configuration. For each feature that you can enable on a Viptela device, the vManage NMS provides a template form that you fill out. The form allows you to set the values for all configurable parameters for that feature.
Because device configurations vary for different Viptela device types and the different types of vEdge routers, feature templates are specific to the type of Viptela device.
Some features are mandatory for device operation, so creating templates for these features is required. Also for the same feature, you can can create multiple templates for the same device type.
Device templates contain a device's complete operational configuration. You create device templates by consolidating together individual feature templates.
Each device template is specific for a type of device. For each device type, if multiple devices have the same configuration, you can use the same device template for them. For example, many of the vEdge routers in the overlay network might have the same basic configuration, so you can configure them with the same templates. (You specify the differences in the templates using configuration variables, which are discussed below.) If the configurations for the same type of devices are different, you create separate device templates.
You can also create a device template by entering a CLI text-style configuration directly on the vManage NMS. Typically, you upload a text file containing the configuration text (or cut the configuration text from a text file and paste it into the vManage NMS). You can also directly type the configuration text into the vManage NMS.
Attach Templates To Devices
To configure a device on the overlay 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 device's complete configuration. You cannot mix and match feature templates and CLI-style configurations.
You can attach the same templates to multiple devices, and you can do so simultaneously, in a single operation.
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, the vManage NMS pushes the configuration immediately after it learns that the device is present in the network.
Within a feature template, some configuration commands and command options are identical across all device types. Others—such as a device's system IP address, its geographic latitude and longitude, the timezone, and the overlay network site identifier—are variable, changing from device to device. When you attach the device template to a device, you are prompted to enter actual values for these command variables. You can do this either manually, by typing the values for each variable and for each device, or you can upload an Excel file in CSV format that contains the values for each device.
Before you can configure any device in the Viptela overlay network, that device must be validated and authenticated so that the vManage NMSs, vSmart controllers, and vBond orchestrators recognize it as being allowed in the overlay network.
To validate and authenticate the controllers in the overlay network—the vManage NMSs, vSmart controllers, and vBond orchestrators—a signed certificate must be installed on these devices, as described in the article Generate a Certificate.
To validate and authenticate the vEdge routers, you receive a vEdge authorized serial number file from Viptela, which lists the serial and chassis numbers for all the vEdge routers allowed in your network. Then, you upload the vEdge serial number file to the vManage NMS.
The feature templates that you create will most likely contain variables. To have the vManage NMS populate the variables with actual values when you attach a device template to a device, create an Excel file that lists the variable values for each device and save the file in CSV format.
In the spreadsheet, the header row contains the variable name and each row after that corresponds to a device, defining the values of the variables. The first three columns in the spreadsheet must be (in the order listed below):
- csv-deviceId—Serial number of the device (used to uniquely identify the device). For vEdge routers, you receive the serial numbers in the vEdge authorized serial number file sent to you from Viptela. For other devices, the serial number is included in the signed certificate you receive from Symantec or from your root CA.
- csv-deviceIP—System IP address of the device (used to populate the system ip address command).
- csv-host-name—Hostname of the device (used to populate the system hostname command).
You can create a single spreadsheet for all devices in the overlay network—vSmart controllers, vBond orchestrators, and vEdge routers. You do not need to specify values for all variables for all devices.
Introduced in vManage NMS in Release 15.3.