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

Alarms

Use the Alarms screen to display detailed information about alarms generated by controllers and routers in the overlay network.

Screen Elements

  • Top bar—On the left are the menu icon, for expanding and collapsing the vManage menu, and the vManage product name. On the right are a number of icons and the user profile drop-down.
  • Title bar—Includes the title of the screen, Alarms.
    • Email Notifications—Send email notifications when the vManage server generates alarms.
  • Filter bar—Includes the Filter drop-down and time periods. Click the Filter icon to display a drop-down menu to add filters for searching alarms. Click a predefined or custom time period for which to display data.
  • Alarms Histogram—Displays a graphical representation of all alarms in order of severity: Critical, Major, Medium, Minor. To hide the alarms histogram, click the Alarms Histogram title or the down angle bracket to the right of it.
  • Search box—Includes the Search Options drop-down, for a Contains or Match string.
  • Refresh icon—Click to refresh data in the alarms table with the most current data.
  • Export icon—Click to download all data to a file, in CSV format.
  • Show Table Fields icon—Click to display or hide columns from the alarms table. By default, all columns are displayed.
  • Table of alarms—To re-arrange the columns, drag the column title to the desired position.

g00430.png

Set Alarm Filters

To set filters for searching alarms generated by one or more Viptela devices:

  1. Click the Filter drop-down menu.
  2. In the Severity drop-down, select the alarm severity level. You can specify more than one severity level.
  3. In the Active drop-down, select active, cleared, or both types of alarm. Active alarms are alarms that are currently on the device but have not been acknowledged.
  4. CIick the Alarm Name drop-down, select the name of the alarm. You can specify more than one alarm name.
  5. Click Search to search for alarms that match the filter.

vManage NMS displays the alarms both in table and graphical format.

Export Alarm Data in CSV Format

To export data for all alarms 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 Search box below the Alarms Histogram.

vManage NMS downloads all data from the alarms table to an Excel file in CSV format. The file is downloaded to your browser's default download location and is named viptela_download.csv.

View Alarm Details

To view detailed information about any alarm:

  1. Select the alarm row from the table.
  2. Click the More Actions icon to the right of the row and click Alarm Details.

The Alarms Details window opens, displaying the possible cause of the alarm, impacted entities, and other details.

Send Alarm Notifications

To send email notifications when alarms occur:

  1. In the vManage Administration ► Settings screen, ensure that Email Notifications is enabled.
  2. In the Monitor ► Alarms screen, click Email Notifications. A list of configured notifications is displayed in the email notifications table.
  3. Click Add Email Notification.
  4. In the Name field, enter a name for the email notification. The name can be up to 128 characters and can contain only alphanumeric characters.
  5. In the Severity drop-down, select one or more alarm severity levels, from Critical, Major, Medium, and Minor.
  6. In the Alarm Name drop-down, select one or more alarms. The alarms generated for each severity level are listed in the section Alarms Generated on vManage NMS, below.
  7. In Account Details, enter the email addresses to receive email notifications:
    1. Click Add New Email List.
    2. In the Email List popup, click Add Email.
    3. Enter the email address of a user.
    4. Add additional email addresses as desired.
    5. Click Save.
  8. In the Email Threshold field, set the maximum number of emails to be sent per minute. The number can be a value from 1 through 30. The default is 5.
  9. Click the Webhook box to trigger an HTTP callback when an alarm notification event occurs:
    1. Enter the username and password to authenticate the webhook server.
    2. Enter the URL of the webhook server.
  10. Select the routers to which the alarm notification applies, either All Devices or a custom list. If you select Custom, a device list is displayed:
    1. In the Available Devices table on the left, select one or more devices.
    2. Click the right-point arrow to move the devices to the Selected Devices table on the right.
  11. Click Add.

View an Email Notification

  1. Click Email Notifications.
  2. For the desired email notification, click the View icon to the right of the row.
  3. When you are done viewing the notification, click OK.

Edit an Email Notification

  1. Click Email Notifications.
  2. For the desired email notification, click the Pencil icon to the right of the row.
  3. When you are done editing the notification, click Update.

Delete an Email Notification

  1. Click Email Notifications.
  2. For the desired email notification, click the Trash Bin icon to the right of the row.
  3. In the confirmation popup, click OK.

Alarms Generated on vManage NMS

The table below lists the alarms that the vManage NMS software generates. The software generates alarms when a state or condition changes, such as when a software component starts, transitions from down to up, or transitions from up to down. The severity indicates the seriousness of the alarm. When you you create email notifications, the severity that you configure in the notification determines which alarms you can receive email notifications about.

Alarm Name Severity Description
AAA Admin Password Change Critical The password for the AAA user admin changed on a router or controller.
BFD Between Sites Down Critical All BFD sessions on all routers between two sites are in the Down state. This means that no data traffic can be sent to or transmitted between those two routers.
BFD Between Sites Up Medium A BFD session on a router between two sites transitioned to the Up state.
BFD Node Down Critical All BFD sessions for a router are in the Down state. This means that no data traffic can be sent to or transmitted from that router.
BFD Node Up Medium A BFD session for a router transitioned to the Up state.
BFD Site Down Critical All BFD sessions on all vEdge routers in a site are in the Down state. This means that no data traffic can be sent to or transmitted from that site.
BFD Site Up Medium A BFD session on a router in a site transitioned to the Up state.
BFD TLOC Down Major All BFD sessions for a TLOC (transport tunnel identified by a color) are in the Down state. This means that no data traffic can be sent to or transmitted from that transport tunnel.
BFD TLOC Up Medium A BFD session for a TLOC transitioned to the Up state.
BGP Router Down Critical All BGP sessions on a router are in the Down state.
BGP Router Up Medium A BGP session on a router transitioned to the Up state.
Clear Installed Certificate Critical All certificates on a controller or device, including the public and private keys and the root certificate, have been cleared, and the device has returned to the factory-default state.
Cloned vEdge Detected Critical A duplicate router that has the same chassis and serial numbers and the same system IP address has been detected.
Cloud onRamp Major The Cloud onRamp service was started on a router.
Control All vSmarts Down Critical All control connections from all vSmart controllers in the overlay network are in the Down state. This means that the overlay network cannot function.
Control Node Down Critical All control connections for a vEdge router are in the Down state.
Control Node Up Medium At least one control connection for a vEdge router transitioned to the Up State.
Control Site Down Critical

All control connections from all Viptela devices in a site are in the Down state.This means that no control or data traffic can be sent to or transmitted from that site.

Control Site Up Medium A control connection from the vManage NMS and the vBond orchestrator in the site transitioned to the Up state.
Control vBond State Change Critical
Major
A control connection on a vBond orchestrator transitioned to the Down state (Critical) or the Up state (Major).
Control TLOC Down Major All control connections for a TLOC are in the Down state.
Control TLOC Up Medium A control connection for a TLOC is in the Up state.
Control vManage Down Critical All control connections from a vManage NMS are in the Down state.
Control vManage Up Medium A control connection from a vManage NMS transitioned to the Up state.
Control vSmart Down Critical All control connections from a vSmart controller in the overlay network are in the Down state.
Control vSmart Up Medium A control connection from a vSmart controller in the overlay network transitioned to the Up state.
Control vSmarts Up Medium Control connection from all vSmart controllers in the overlay network transition to the Up state.
CPU Load Critical
Medium
The CPU load on a controller or device has reached a critical level that could impair or shut down functionality, or a medium level that could impair functionality.
Default App List Update Major The default application and application family lists, which are used in application-aware routing policy, have changed.
Device Activation Failed Critical Activation of a software image on a controller or device failed.
Device Upgrade Failed Critical The software upgrade on a router failed.
DHCP Server State Change Major The state of a DHCP server changed.
Disk Usage Critical
Major
The disk usage load on a controller or device has reached a critical level that could impair or shut down functionality, or a medium level that could impair functionality.
Domain ID Change Critical A domain identifier in the overlay network changed.
Interface Admin State Change Critical
Medium
The administrative status of an interface in a controller or router changed from up to down (Critical) or down to up (Medium).
Interface State Change Medium The administrative or operational status of an interface changed.
Memory Usage Critical
Medium
The memory usage on a controller or device has reached a critical level that could impair or shut down functionality, or a medium level that could impair functionality.
New CSR Generated Critical A controller or router generated a certificate signing request (CSR).
OMP All vSmarts Down Critical All OMP connections from all vSmart controllers in the overlay network are in the Down state. This means that the overlay network cannot function.
OMP vSmarts Up   At least one OMP connection from all vSmart controllers in the overlay network is in the Up state.
OMP Node Down   All OMP connections for a vEdge router are in the Down state.
OMP Node Up Medium At least one OMP connection for a vEdge router is in the Up state.
OMP Site Down Critical

All OMP connections to vSmart controllers from all nodes in the a are in the Down state. This means that that site cannot participate in the overlay network.

OMP Site Up Medium At least one OMP connection to vSmart controllers from all nodes in the site is in the Up state.
OMP State Change Critical
Medium
The administration or operational state of an OMP session between a vSmart controller and a vEdge router has changed, from Up to Down (Critical) or Down to Up (Medium).
OMP vSmarts Up Medium OMP connection from all vSmart controllers in the overlay network transition to the Up state.
Org Name Change Critical The organization name used in the certificates for all overlay network devices changed.
OSPF Router Down Critical All OSPF connections on a router are in the Down state.
OSPF Router Up Medium An OSPF connection on a router transitioned to the Up state.
PIM Interface State Change Major The state of a PIM interface changed.
Process Restart Critical A process (daemon) on a controller or router restarted.
Pseudo Commit Status Minor The vManage NMS has started pushing a device configuration template to a controller or router. The NMS pushes a tentative configuration (called the pseudo commit) to the device and starts the rollback timer. If , with the new configuration, the control connections between the device and the vManage NMS come up, the tentative configuration becomes permanent. If the control connections do not come up, the tentative configuration is removed, and the device's configuration is rolled back to the previous configuration (that is, to the last known working).
Root Cert Chain Installed Critical The file containing the root certificate key chain was installed on a controller or router.
Root Cert Chain Uninstalled Critical The file containing the root certificate key chain was removed from a controller or router.
Site ID Change Critical A site identifier in the overlay network changed.
System IP Change Critical The system IP address on a controller or router changed.
System IP Reuse Critical The same system IP address is being used by more than one device in the overlay network.
System Reboot Issued Critical
Medium
A device rebooted, either initiated by the device (Critical) or by a user (Medium).
Template Rollback Critical The attaching of a device configuration template to a router did not succeed in the configured rollback time, and as a result, the configuration on the device was not updated, but instead was rolled back to the previous configuration.
Unsupported SFP Detected Critical The software detected an unsupported transceiver in a hardware router.
vEdge Serial File Uploaded Critical The WAN Edge serial number file was uploaded to the vManage server.
vSmart/vManage Serial File Uploaded Critical A vManage NMS uploaded the file containing certificate serial numbers for the vManage NMSs and vSmart controllers in the overlay network.
ZTP Upgrade Failed Critical A software upgrade using ZTP failed on a controller or router.

Additional Information

Monitor Alarms and Events

  • Was this article helpful?