Event Receiving, Forwarding, and Notifications
Prime Infrastructure 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 Prime Infrastructure 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 destination with the notification type UDP, the destination 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.
Prime Infrastructure can forward alarms and events that are generated by the processing of received syslogs, traps, and TL/1 alarms to northbound notification destination. Information can be forwarded in email format or SNMP trap format, See Configure Alarm Notification Destination.
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
Note |
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, create, edit and delete notification destination and notification policy created under their respective virtual domain. |
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, create, edit and delete notification destination and notification policy created under their respective virtual domain. |
Super user with non-root domain |
View, create, edit and delete 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 explains you some points you must remember while 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 Prime Infrastructure.
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: |
Note |
Notifications will not be sent to email recipient for North Bound trap receiver, if you change the severity of an alarm type from Monitor > Monitoring Tools > Alarm Policies. |
Convert Old Email and Trap Notification Data to New Alarm Notification Policy
The email and trap notification data created in previous Prime Infrastructure releases is converted in to new alarm notification policies while upgrading or migrating Prime Infrastructure from previous release to the latest version.
The migrated alarm notification policies can be viewed in the Alarms and Events Notification Policies pages.
- 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
- Autonomous AP
- Cisco UCS Series
- Routers
- Switches and Hubs
- Wireless Controller
To edit the migrated alarm notification polices, see Customize Alarm Notification Policies.