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

Logging

You can use the Logging template for all Vipela devices.

To configure logging to either the local hard drive or a remote host:

  1. Create a Logging feature template to configure logging parameters, as described in this article.
  2. Create a device template that incorporates the Logging feature template. See the Configuration ► Templates help topic.​

Navigate to the Template Screen

  1. In vManage NMS, select the Configuration ► Templates screen.
  2. From the Templates title bar, select Feature.
  3. Click Add Template.
  4. In the left pane, select one or more devices. The right pane displays the available templates for the selected devices.
  5. Select the Logging template.

The right pane displays the Logging template form:

  • The top of the form contains fields for naming the template.
  • The bottom contains fields for defining parameters applicable to that template.
  • A drop-down menu to the left of each parameter field defines the scope of the parameter. When you first open a feature template form, for each parameter that has a default value, the scope is set to Default. To edit a parameter field, change the scope to Global or Device Specific. Note that if a parameter's scope is Device Specific, you cannot enter a value for it in the feature template. Instead, you enter a value when you attach the template to a device.
  • A plus sign (+) is displayed to the right when you can add multiple entries for the same parameter.

Minimum Logging Configuration

The following logging parameters are configured by default on all Viptela devices:

  • Log event notification system log (syslog) messages are logged to a file on the local device's hard disk, at a priority level of "information."
  • Log files are placed in the directory /var/log on the local device.
  • Log files are readable by the "admin" user.

Configure Logging To the Local Disk

You can configure logging of event notification system log messages to the local device's hard disk:

Parameter Name Description
Template Name Enter the template name. It can be up to 128 characters and can contain only alphanumeric characters.
Description (Template) Enter a description of the template. It can be up to 2048 characters and can contain only alphanumeric characters.
Enable disk Click On to allow syslog messages to be saved in a file on the local hard disk, or click Off to disallow it. By default, logging to a local disk file is enabled on all Viptela devices.
Maximum file size Enter the maximum size of syslog files. Syslog files are rotated on an hourly basis based on the file's size. When the file size exceeds configured value, the file is rotated and the syslogd process is notified.
Range: 1 through 20 MB
Default: 10 MB
Rotations

Enter the number of syslog files to create before discarding the oldest files.
Range: 1 through 10
Default: 10

Priority Select the priority level of the syslog message to save to the log files. The severity indicates the seriousness of the event that generated the message. The default priority value is "informational", so, by default, all syslog messages are recorded.
The priority level can be one of the following (in order of decreasing severity):
• Emergency—System is unusable (corresponds to syslog severity 0).
• Alert— Action must be taken immediately (corresponds to syslog severity 1).
• Critical—Critical: A serious condition (corresponds to syslog severity 2).
• Error—An error condition that does not fully impair system usability (corresponds to syslog severity 3).
• Warning—A minor error condition (corresponds to syslog severity 4).
• Notice—A normal, but significant condition (corresponds to syslog severity 5).
• Informational—Routine condition (the default) (corresponds to syslog severity 6).

CLI equivalent:

system 
  logging
  ​  disk  
      enable
      file
        rotate number
        size megabytes      
      priority priority

 

Configure Logging To Remote Severs

To configure logging of event notification system log messages to a remote server, click the plus sign (+):

Parameter Name Description
Hostname/IP Address

Enter the DNS name, hostname, or IP address of the system on which to store syslog messages.

To add another syslog server, click the plus sign (+). To delete a syslog server, click the trash icon to the right of the entry.

VPN Enter the VPN in which the syslog server is located or through which the syslog server can be reached.
Range: 0 through 65530
Source Interface Enter the specific interface to use for outgoing system log messages. The interface must be located in the same VPN as the syslog server. Otherwise, the configuration is ignored. If you configure multiple syslog servers, the source interface must be the same for all of them.
Priority Select the severity of the syslog message to save. The severity indicates the seriousness of the event that generated the message. priority can be one of the following:
• Emergency—System is unusable (corresponds to syslog severity 0).
• Alert— Action must be taken immediately (corresponds to syslog severity 1).
• Critical—Critical: A serious condition (corresponds to syslog severity 2).
• Error—An error condition that does not fully impair system usability (corresponds to syslog severity 3).
• Warning—A minor error condition (corresponds to syslog severity 4).
• Notice—A normal, but significant condition (corresponds to syslog severity 5).
• Informational—Routine condition (the default) (corresponds to syslog severity 6).

To remove a logging server, click the trash icon to the right of the entry.

CLI equivalent:

system 
  logging 
    ​server (dns-name | hostname | ip-address)
      priority priority
      source-interface interface-name
      vpn vpn-id

Release Information

Introduced in vManage NMS in Release 15.2.

  • Was this article helpful?