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

System

Use the System template for all Viptela devices.

To configure system-wide parameters using vManage templates:

  1. Create a System feature template to configure system parameters, as described in this article.
  2. Create an NTP feature template to configure NTP servers and authentication. See the NTP help topic.
  3. Configure the organization name and vBond orchestrator IP address on the vManage NMS. See the Settings help topic. These settings are appended to the device templates when the templates are pushed to devices.​

Navigate to the Template Screen

  1. In vManage NMS, select the Configuration ► Templates screen.
  2. In the Device tab, click Create Template.
  3. From the Create Template drop-down, select From Feature Template.
  4. From the Device Model drop-down, select the type of device for which you are creating the template.
  5. To create a custom template for System, select the Factory_Default_System_Template and click Create Template. The System template form is displayed. The top of the form contains fields for naming the template, and the bottom contains fields for defining System parameters. You may need to click a tab or the plus sign (+) to display additional fields.

When you first open a feature template, for each parameter that has a default value, the scope is set to Default (indicated by a check mark), and the default setting or value is shown. To change the default or to enter a value, click the scope drop-down to the left of the parameter field and select one of the following:

Parameter Scope

Scope Description

Device Specific (indicated by a host icon)

Use a device-specific value for the parameter. For device-specific parameters, you cannot enter a value in the feature template. You enter the value when you attach a Viptela device to a device template.

When you click Device Specific, the Enter Key box opens. This box displays a key, which is a unique string that identifies the parameter in a CSV file that you create. This file is an Excel spreadsheet that contains one column for each key. The header row contains the key names (one key per column), and each row after that corresponds to a device and defines the values of the keys for that device. You upload the CSV file when you attach a Viptela device to a device template. For more information, see Create a Template Variables Spreadsheet.

To change the default key, type a new string and move the cursor out of the Enter Key box.

Examples of device-specific parameters are system IP address, hostname, GPS location, and site ID.

Global (indicated by a globe icon)

Enter a value for the parameter, and apply that value to all devices.

Examples of parameters that you might apply globally to a group of devices are DNS server, syslog server, and interface MTUs.

Minimum System-Wide Configuration

The following parameters are required (unless otherwise indicated) to set up system-wide functionality on a Viptela device:

Step Parameter Field Procedure
 1. Template Name Enter a name for the template. It can be up to 128 characters and can contain only alphanumeric characters.
 2. Description (Template) Enter a description for the template. It can be up to 2048 characters and can contain only alphanumeric characters.
 3. Site ID Enter the identifier of the site in the Viptela overlay network domain in which the device resides, such as a branch, campus, or data center. All vEdge routers at the same site must have the same site ID
Range: 1 through 4294967295 (232 – 1)
 4. System IP Enter the system IP address for the Viptela device, in decimal four-part dotted notation. The system IP address provides a fixed location of the device in the overlay network and is a component of the device's TLOC address. It is used as the device's loopback address in the transport VPN (VPN 0). You cannot use this same address for another interface in VPN 0.
 5. Timezone Select the timezone to use on the device.
 6. Hostname (optional) Enter a name for the Viptela device. It can be up to 32 characters.
 7. Location (optional) Enter a description of the location of the device. It can be up to 128 characters.
 8. Device groups (optional) Enter the names of one or more groups to which the device belongs, separated by commas.
 9. Controller groups (optional, on vEdge routers only) List the vSmart controller groups to which the vEdge router belongs.
10. Description (optional) Enter any additional descriptive information about the device.
11. Console Baud Rate (vEdge routers only)

Select the baud rate of the console connection on the vEdge router.
Values: 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200 baud or bits per second (bps)
Default: 115200 bps

12. Maximum Controllers (optional, on vEdge routers only) Set the maximum number of vSmart controllers that the vEdge router is allows to connect to.
Range: 0 through 100
Default: Maximum number of OMP sessions configured in Max-OMP Sessions
13. Maximum OMP Sessions (optional, on vEdge routers only) Set the maximum number of OMP sessions that a vEdge router can establish to a vSmart controller.
Range: 0 through 100
Default: 2
14. Dedicated Core for TCP Optimization (optional, on vEdge 1000 and 2000 routers only) Click on to carve out a separate CPU core to use for performing TCP optimization.
14. GPS Location: Latitude and Longitude Enter the latitude and longitude of the device, in the format decimal-degrees. This location is used to place the device on the vManage NMS network map. Setting the location also allows the vManage NMS to send a notification if the device is moved to another location.
15. Local vBond (only on vEdge routers acting as vBond orchestrators) Click Advanced Options, and click On to configure the vEdge router to act as a vBond orchestrator. Then specify the DNS name for the vBond orchestrator or its IP address, in decimal four-part dotted notation.
16. Save Click Save to save the feature template.

CLI equivalent:

system
  clock
    timezone timezone
  console-baud-rate rate
  controller-group-list numbers 
  description text 
  device-groups group-name
  gps-location (latitude decimal-degrees | longitude decimal-degrees)
  host-name string
  location string
  max-control-connections number
  max-omp-sessions number
  site-id site-id  
  system-ip ip-address
  tcp-optimization-enabled
  vbond (dns-name | ip-address) local

To configure the DNS name or IP address of the vBond orchestrator in your overlay network, go to the Administration ► Settings screen and click vBond.

Configure Advanced Options

To configure additional system parameters, click Advanced Options:

Parameter Name Description
Control Session Policer Rate

Specify a maximum rate of DTLS control session traffic, to police the flow of control traffic.
Range: 1 through 65535 pps
Default: 300 pps

MTU of DTLS Tunnel

Specify the MTU size to use on the DTLS tunnels that send control traffic between Viptela devices.
Range: 500 through 2000 bytes
Default: 1024 bytes

Port Hopping

Click On to enable port hopping, or click Off to disable it. When a Viptela device is behind a NAT, port hopping rotates through a pool of preselected OMP port numbers (called base ports) to establish DTLS connections with other Viptela devices when a connection attempt is unsuccessful. The default base ports are 12346, 12366, 12386, 12406, and 12426. To modify the base ports, set a port offset value.
Default: Enabled

Port Offset Enter a number by which to offset the base port number. Configure this option when multiple Viptela devices are behind a single NAT device, to ensure that each device uses a unique base port for DTLS connections.
Values: 0 through 19
DNS Cache Timeout

Specify when to time out the vBond orchestrator addresses that have been cached by the device.
Range: 1 through 30 minutes
Default: 30 minutes

Track Transport

Click On to regularly check whether the DTLS connection between the device and a vBond orchestrator is up. Click Off to disable checking. By default, transport checking is enabled

Local vBond (only on vEdge routers acting as vBond orchestrators)

Click On to configure the vEdge router to act as a vBond orchestrator. Then specify the DNS name for the vBond orchestrator or its IP address, in decimal four-part dotted notation.

Track Interface (on vEdge routers only) Set the tag string to include in routes associated with a network that is connected to a non-operational interface.
Range: 1 through 4294967295
Multicast Buffer (on vEdge routers only) Specify the percentage of interface bandwidth that multicast traffic can use.
Range: 5% through 100%
Default: 20%
USB Controller (on vEdge 1000 and 2000 series routers only)

Click On to enable or click Off to disable the USB controller, which drives the external USB ports. If you enable the USB controller, the vEdge router reboots when you attach the device template to the device.
Default: Disabled

Gateway Tracking

Click On to enable or click Off to Disable tracking of default gateway. Gateway tracking determines, for static routes, whether the next hop is reachable before adding that route to the device's route table.
Default: Enabled

Host Policer (on vEdge routers only)

Specify the maximum rate at which a policer delivers packets to the control plane.
Range: 1000 through 20000 pps
Default: 5000 pps

ICMP Error (on vEdge routers only) Specify how many ICMP error messages a policer can generate or receive.
Range: 1 through 200 pps
Default: 100 pps
Allow Same-Site Tunnel (vEdge routers only) Click On to allow tunnels to be formed between vEdge routers in the same site. Note that no BFD sessions are established between the two collocated vEdge routers.
Default: Off
Route Consistency Check (on vEdge routers only) Click On to check whether the IPv4 routes in the device's route and forwarding table are consistent.

CLI equivalent:

system
  allow-same-site-tunnels (on vEdge routers only)
  control-session-pps rate 
  host-policer-pps rate (on vEdge routers only)
  icmp-error-pps rate (on vEdge routers only)
  multicast-buffer-percent percentage (on vEdge routers only)
  port-hop​
  port-offset number
  route-consistency-check (on vEdge routers only)
  system-tunnel-mtu bytes
  timer
    dns-cache-timeout minutes 
  track-default-gateway
  track-interface-tag number (on vEdge routers only)
  track-transport 
  upgrade-confirm minutes
  [no] usb-controller (vEdge 1000 and 2000 routers only)
  vbond (dns-name | ip-address) local (on vEdge routers acting as vBond controllers)

Release Information

Introduced in vManage NMS in Release 15.2.
In Releases 15.3.8 and 15.4.3, add Track Interface field.
In Release 17.1.0, add Route Consistency Check field.

  • Was this article helpful?