Event Receiving, Forwarding, and Notifications
Cisco EPN Manager processes syslogs and SNMPv1, v2, and v3 traps that it receives from devices. The server automatically listens for these events on UDP port 162. You do not have to perform any event listening configuration on the server, but you do have to configure devices to forward traps and syslogs to Cisco EPN Manager on the appropriate port.
Notifications are forwarded in SNMPv2 or SNMPv3 format. They are also forwarded to email recipients when you setup corresponding Notification Policies. If you are adding a notification receiver with the notification type UDP, the receiver you add should be listening to UDP on the same port on which it is configured. Only INFO level events are processed for the selected category and alarms are processed with critical, major, minor and warning levels.
Cisco EPN Manager can forward alarms and events that are generated by the processing of received syslogs, traps, and TL/1 alarms to northbound notification receiver. Alarms of any severity can be forwarded, but only events with INFO severity can be forwarded. Information can be forwarded in :
-
E-Mail format. See Configure Default Settings for E-Mail Notifications
-
SNMP trap format. See Forward Alarms and Events as SNMP Trap Notifications
You can also use the SNMP trap notification mechanism to forward SNMP traps that indicate server problems.
Alerts and events are sent as SNMPv2.
User Roles and Access Permissions for Configuring Alarm Notification Settings
This table describes the user roles and access permissions for configuring notification destination and creating customized notification policies.
Note |
Ensure that you enable the following Task Permissions for any user roles to view, create, and edit notification destination and notification policy:
For more information, see View and Change the Tasks a User Can Perform. |
User Role |
Access Permission |
---|---|
Root user with root domain |
View, create, delete and edit notification destination and notification policy. |
Root user with non-root domain |
View notification destination and notification policy. |
Admin user with root domain |
View, create, delete and edit notification destination and notification policy. |
Super user with root domain |
View, create, delete and edit notification destination and alarm notification policy. |
System monitoring user with root domain |
View notification destination and notification policy. |
Config manager with root domain |
View notification destination and notification policy. |
Admin user with non-root domain |
View notification destination and notification policy created under their respective virtual domain. |
Super user with non-root domain |
View notification destination and notification policy created under their respective virtual domain. |
System monitoring user with non-root domain |
View notification destination and notification policy created under their respective virtual domain. |
Config manager with non-root domain |
View notification destination and notification policy created under their respective virtual domain. |
Points to Remember While Adding a New Notification Policy
The following table lists few points you must remember when adding a new notification policy.
Category selected under Notification Policy Page |
Points to Remember |
---|---|
|
|
Trap Receiver |
|
Notification Policy |
|
Configure Alarms Notification Destination
You can configure the email notification and Northbound trap receiver settings to notify the alarms generated by Cisco EPN Manager.
Procedure
Step 1 |
Choose . |
Step 2 |
Click the Add icon to create a new notification destination. |
Step 3 |
To configure Email Destination, do the following: |
Step 4 |
To configure a Northbound trap receiver using IP Address, do the following:
|
Step 5 |
To configure a Northbound trap receiver using DNS, do the following:
|
Note |
|
Customize Alarm Notification Policies
You can add a new alarm notification policy or edit an existing alarm notification policy to send notifications on specific alarms of interest that are generated on particular device groups, to specific recipients: either email recipients or northbound trap receivers or both.
Procedure
Step 1 |
Choose Administration > Settings > System Settings > Alarms and Events> Alarm Notification Policies. To add a new alarm notification policy, do the following: |
Step 2 |
To edit an alarm notification policy, do the following: |
Convert Old Email and Trap Notification Data to New Alarm Notification Policy
The email and trap notification data created in previous Cisco EPN Manager releases is converted in to new alarm notification policies while upgrading or migrating Cisco EPN Manager from previous release to the latest version.
The migrated alarm notification policies can be viewed in the Alarms and Events Notification Policies pages.
The following Alarm categories are supported in Cisco EPN Manager Release 4.0:
-
Change Audit
-
Generic
-
System
-
Application Performance
-
Compute Servers
-
Nexus VPC switch
-
Switches and Routers
-
AP
-
Adhoc Rogue
-
Clients
-
Context Aware Notifications
-
Controller
-
Coverage Hole
-
Mesh Links
-
Mobility Service
-
Performance
-
RRM
-
Rogue AP
-
SE Detected Interferers
-
Security
-
Third Party AP
-
Third Party Controller
The following Alarm categories are not supported in Cisco EPN Manager Release 4.0:
-
Autonomous AP
-
Cisco UCS Series
-
Routers
-
Switches and Hubs
-
Wireless Controller
To edit the migrated alarm notification polices, see Customize Alarm Notification Policies.
Forward Alarms and Events as SNMP Trap Notifications
Cisco EPN Manager can forward alarms and events in EPM-NOTIFICATION-MIB format as an SNMPv2c and SNPv3 trap notifications. You can specify:
-
A specific alarm or event category, such as System for internal server SNMP traps.
-
Alarms of a specific severity. Only INFO events are forwarded; you cannot specify other severities for events.
See Configure Alarms Notification Destination for more information.
Configure Default Settings for E-Mail Notifications
If you have not configured the mail server, perform the instructions in Set Up the SMTP E-Mail Server. Otherwise notifications will not be sent.
You can configure certain default settings that are applied across all alarm and event e-mail notifications. These settings can be overwritten when users configure individual notifications and receivers.
By default, the email subject line will include the alarm severity and category. The following settings are also available but are disabled by default.
-
Subject line—Include the prior alarm severity or add custom text. Alternatively you can replace all of the subject line with custom text.
-
Body of the email—Include custom text, the alarm condition, and a link to the alarm detail page.
-
Secure message mode—Enabling this mode masks the IP address and controller name.
To enable, disable, or adjust these settings, choose Alarm Email Options area.
, then . Make your changes in the