This document describes how to configure and send email notifications via vManage for events that take place in the network.
Cisco recommends that you have knowledge of vManage and ensure that it should be 18.3.0 and above.
This document is not restricted to specific software and hardware versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
These steps need to be configured in order to enable email notifications.
1. Edit the Email Notifications from Administration > Settings.
2. Configure the Email Notifications from Monitor > Alarms.
For Step 1., from vManage Dashboard, navigate to Administration > Settings > Email Notifications > Edit and configure the Enable Email Notifications section. Here is an example screenshot.
You can select the From address as per your choice, however, the domain name should match the mail server. As an example, <..username..>@cisco.com and the reply address will be firstname.lastname@example.org. Because, if there will be a reply, vManage will not capture. This scenario is similar to the auto-generated emails that come with a no-reply address.
For Step 2., this includes sub-steps like Severity, Alarm Name, Email-list, and WebHook URL.
Webhooks are used by an external system in order to notify the local system about a certain event or update. They are like API calls
in the opposite direction. HTTP POST can be sent from vManage to any service who is listening for this. For example, when you set up a webhook in vManage that hits a "serverless" piece of code in AWS, it fires off an event to page a bunch of people in the organization. There are several online services that you can connect to do these things. Refer to https://testwebhooks.com/.
There is a threshold field in the Email Notifications page. Navigate to Monitor> Alarms> Email Notifications.
This field indicates how many emails you want to receive per minute. By default, a maximum of 5 emails per minute. When the emails go beyond that threshold, you will receive the message as shown in the image. The emails will not be sent for 5 minutes and then the threshold will start fresh.
The rest of the document captures the usage of "Email Alerts."
Check the vManage logs: /var/log/nms/vmanage-server.log
Verify via vManage-Dashboard. Navigate to Monitor > Audit Log as shown in the image.
This section provides information you can use in order to troubleshoot your configuration.
Currently, there is an issue where vManage Audit-Log might say that email might have been sent, but in fact, the email is not received. You can verify this through the in/var/log/nms/vmanage-server.log file as shown in the image.
VIP-42227 is opened to track this issue. There is no plan to fix.
Not all email alerts get generated consistently:
Firstly, it depends on how many alarms are generated for the set of events. vManage tries to combine events to one alarm if they are related. If not, it will generate multiple alarms at the same time. For each alarm generated and rule, there will be an email. Email notification is tied to alarms, not events.
Secondly, if in the first rule, you see that there are multiple alarms, there is only 1 email sent for that rule match. If a customer wants multiple emails for the individual event, the individual rule needs to be defined.
"Username and Password not accepted" in vmanage-server.logs:
As seen in the screenshot, you might see the error "Username and Password not accepted. Learn more at
Email notifications should then be received on the email account specified.
Failure to send email Notification(s):
In some cases, you might see that the generated email is denied by the mail server. This could be if the already provided account configuration might be incorrect or access is not granted. In the logs, you can see this message: SendAsDeniedException.
03-Dec-2018 15:46:37,177 CST ERROR [ts_vManage][EmailNotiUtil] (default task-84) |default| Sending email notification failed: 554 5.2.0 STOREDRV.Submission.Exception:SendAsDeniedException.MapiExceptionSendAsDenied; Failed to process message due to a permanent exception with message Cannot submit message.
Another use case is that the number of email messages users can send per day varies from SMTP Server to Server. You might see this log message in vManage: