- Introduction to Administering Cisco Prime Infrastructure
- Administrator Setup Tasks
- Prime Infrastructure Server Settings
- Maintaining Prime Infrastructure Server Health
- Backing Up and Restoring Prime Infrastructure
- Maintaining Network Health
- Managing Data and Collection Retention
- Configuring Controller and AP Settings
- Configuring High Availability
- Configuring Wireless Redundancy
- Controlling User Access
- Advanced Monitoring
- Managing Licenses
- Managing Traffic Metrics
- Planning Network Capacity Changes
- Appendix A: Prime Infrastructure Internal SNMP Trap Generation
- Appendix B: Best Practices: Server Security Hardening
- Appendix C: Configuring the Plug and Play High Availability Feature
Cisco Prime Infrastructure 2.2 Administrator Guide
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Updated:
- February 9, 2018
Chapter: Appendix A: Prime Infrastructure Internal SNMP Trap Generation
- About Internal Trap Generation
- Prime Infrastructure SNMP Trap Types
- Generic SNMP Trap Format
- Prime Infrastructure SNMP Trap Reference
- Working With Prime Infrastructure Traps
- Configuring Notifications
- Configuring Notification Receivers
- Port Used To Send Traps
- Configuring Email Notifications for SNMP Traps
- Configuring Email Server Settings
- Viewing Events and Alarms for SNMP Traps
- Filtering Events and Alarms for SNMP Traps
- Purging Alarms for SNMP Traps
- Troubleshooting Prime Infrastructure SNMP Traps
Internal SNMP Trap Generation
Revised: September 24, 2015, OL-32123-01
When properly configured, Prime Infrastructure will send SNMP traps to notification receivers to notify them of the following events occurring within the Prime Infrastructure system itself:
- Any crash or failure of an internal software process on the Prime Infrastructure server
- High Availability (HA) state changes, including Registration, Failover, and Failback.
- High CPU, memory or disk utilization
- CPU, disk, fan, or power supply unit (PSU) failures
This appendix provides reference information on these internal SNMP traps and how to use them to manage Prime Infrastructure.
About Internal Trap Generation
You can edit the severity associated with each of these internal SNMP traps. You can also change the threshold limits on high CPU, memory and disk utilization traps (these SNMP traps are sent when the system hardware exceeds the configured thresholds).
For other events (such as CPU, disk, fan, and PSU failures, or HA state changes), an SNMP trap is sent as soon as the failure or HA state-change is detected.
SNMP traps are generated based on customized threshold and severities for the following:
- Server Process Failures
- High Availability Operations
- CPU Utilization
- Memory Utilization
- Disk Utilization
- Disk Failure
- Fan Failure
- PSU Failure
Prime Infrastructure does not send SNMPv2 Inform or SNMPv3 notifications.
Prime Infrastructure SNMP Trap Types
The following table lists the SNMP traps that Prime Infrastructure generates for its own functions. The listing is by trap type. The table describes the circumstances under which each trap is generated as well as suggested operational responses (where applicable).
Generic SNMP Trap Format
The following shows the syntax of SNMP trap notifications for Prime Infrastructure:
Component
: Component Name,
Server
: Primary, Secondary or Standalone,
Type
: Process, Sync, Activity, etc.,
Service
: Service Name,
When
: Phase in the Prime Infrastructure Lifecycle,
State
: HA and HM state of the server,
Result
: Warning, Failure, Success, Information, Exception,
MSG
: Free-form text of the message for a given SNMP Trap
The following table describes possible values for each of the generic trap format attributes
Prime Infrastructure SNMP Trap Reference
The following tables provide details for each class of SNMP trap notification generated in Prime Infrastructure. The mapped OID for the WCS northbound notification MIB is 1.3.6.1.4.1.9.9.712.1.1.2.1.12. This OID is referenced by Prime Infrastructure's software- and hardware-related traps.The trap OID for the northbound MIB will always be 1.3.6.1.4.1.9.9.712.0.1. For details, consult the listing for CISCO-WIRELESS-NOTIFICATION-MIB .
Working With Prime Infrastructure Traps
The following sections explain how to configure and use Prime Infrastructure trap notifications.
Configuring Notifications
For Prime Infrastructure to send northbound SNMP trap notifications, you must configure the correct settings on both the Prime Infrastructure Event Notification and Notification Receivers pages. Once configured, traps will be generated based on values associated with the Threshold and Severity for the following SNMP Events:
You can edit the threshold and severity associated with each event, and enable or disable trap generation for the associated event.
Step 1 Log in to Prime Infrastructure using a user ID with administrator privileges.
Step 2 Select Administration > System Settings > PI Event Notification .
Step 3 For each SNMP event you want to configure:
a. Click on the row for that event.
b. Set the Event Severity level to Critical, Major, or Minor, as needed.
c. For the CPU, disk, and memory utilization traps: Enter the Threshold percentage (from 1-99). These events will send the associated SNMP traps when the utilization exceeds the threshold limit. You cannot set thresholds for events for which the threshold setting is shown as NA. These events send traps whenever the associated failure is detected.
d. Set the SNMP Event Status to Enabled or Disabled. If set to Enabled, the corresponding trap will be generated for this event.
Step 4 When you are finished, click Save to save your changes.
Configuring Notification Receivers
Once you have enabled trap notifications and customized their severities and thresholds, you must configure one or more Notification Receivers to receive the traps.
When you add a Notification Receiver, remember to select the System checkbox as one of the Criteria and, set the Severity to the highest severity set under the severity level configured for each trap on the Event Notifications page (see Configuring Notifications).
Step 1 Log in to Prime Infrastructure with a user ID that has administrator privileges.
Step 2 Select Administration > System Settings > Notification Receivers.
Step 3 In the Select a command box, select Add Notification Receiver , then click Go .
Step 4 Complete at least the following fields:
a. IP Address : Enter the IPv4 or IPv6 address of the server on which the receiver will run.
b. Server Name : Enter the host name of the server on which the receiver will run.
c. Under Category , select at least the System checkbox.
d. Under Severity , select the highest Severity Level that you set when you configured the trap notifications themselves.
For example: If you selected “Critical” as the Event Severity for a PSU failure, select “Critical” as the value in this field.
Alternatively: Select All to receive all traps, regardless of severity.
Step 5 When you are finished, click Save.
Port Used To Send Traps
Prime Infrastructure sends traps to notification receivers on port 162. This port cannot be customized at present. The northbound management system has to register itself through the Notification Receiver web page (see Configuring Notification Receivers).
Configuring Email Notifications for SNMP Traps
You can configure Prime Infrastructure to send email notification for alarms and events generated in response to SNMP traps. All of these alarms and events are considered part of the System event category. You can also customize the severity level for which such notifications will be sent.
Note that, for these email notifications to be sent, a Prime Infrastructure administrator must configure at least a primary SMTP email server (see Configuring Email Server Settings).
Step 1 Log in to Prime Infrastructure.
Step 2 Select Monitor > Alarms and Events
Step 3 Click Email Notification . Prime Infrastructure displays the first Email Notification Settings page.
Step 4 In the Alarm Category column, click on the System category's name. Prime Infrastructure displays a second Email Notification Settings page.
Step 5 Under Send email for the following severity levels , select all of the severity levels for which you want Prime Infrastructure to send email notifications.
Step 6 In To , enter the email address to which you want Prime Infrastructure to send email notifications. If you have multiple email addresses, enter them as a comma-separated list.
Step 7 Click Save . Prime Infrastructure displays the first Email Notification Settings page.
Step 8 In the Enable column, make sure System is selected, then click Save .
Configuring Email Server Settings
To enable Prime Infrastructure to send email notifications, the system administrator must configure a primary SMTP email server (and, preferably, a secondary email server).
Step 1 Log in to Prime Infrastructure using a user ID with administrator privileges.
Step 2 Select Administration > Settings > System Settings > Mail Server Configuration .
Step 3 Under Primary SMTP Server , complete the Hostname/IP , User Nam e, Password and Confirm Password fields as appropriate for the email server you want Prime Infrastructure to use.
Step 4 (Optional) Complete the same fields under Secondary SMTP Server .
Step 5 Under Sender and Receivers , enter a legitimate email address for the Prime Infrastructure server.
Step 6 When you are finished, click Save .
Viewing Events and Alarms for SNMP Traps
Events and Alarms for all of Prime Infrastructure’s internal SNMP traps fall under the System category. You can view them in the Prime Infrastructure Alarms and Events dashboard.
Step 1 Log in to Prime Infrastructure.
Step 2 Select Monitor > Alarms and Events .
Filtering Events and Alarms for SNMP Traps
You can use the Prime Infrastructure Filter feature to narrow the display of alarms to just those in the System category, or use a combination of criteria and operators to focus the list on very specific alarms. The following sections explain how to do this.
Filtering for SNMP Traps Using Quick Filters
Prime Infrastructure's Quick Filters allow you to quickly focus the data inside a table by applying a filter for a specific table column or columns.
Step 1 Log in to Prime Infrastructure.
Step 2 Select Monitor > Alarms and Events .
Step 3 In the Show box, select Quick Filter from the drop-down list. Prime Infrastructure displays a table header listing fields on which you can perform a quick filter, including Severity , Message , and Category .
Step 4 In the Category field, enter System . Prime Infrastructure displays only System alarms.
Step 5 To clear the Quick Filter, click the funnel icon shown next to the Show box.
Filtering for SNMP Traps Using Advanced Filters
Prime Infrastructure's Advanced Filter allows you to narrow down the data in a table by applying a filter combining multiple types of data with logical operators (such as “Does not contain”, “Does not equal”, “Ends with”, and so on). For example, you can choose to filter the table of alarms based on the Category, then further reduce the data by filtering on Severity (as shown in the steps below). You can also save an Advanced Filter for later re-use.
Step 1 Log in to Prime Infrastructure.
Step 2 Select Monitor > Alarms and Events .
Step 3 In the Show box, select Advanced Filter from the drop-down list. Prime Infrastructure displays a table header showing criteria for the first rule in the filter.
Step 4 Complete the first rule as follows:
a. In the first field, select Category from the drop-down list.
b. In the second field, select Contains from the drop-down list.
c. In the third rule field, enter System .
d. Click Go . Prime Infrastructure displays only System alarms.
Step 5 Click the plus sign icon to add another rule, then complete the second rule as follows:
a. In the first field, select Severity from the drop down list
b. In the second field, select Is exactly (or equals) from the drop-down list.
c. In the third rule field, select Major from the drop-down list.
d. Click Go . Prime Infrastructure displays only System alarms with Major Severity.
Step 6 To save the Advanced filter, click the Save icon and supply a name for the filter.
Step 7 To clear the Advanced Filter, click Clear Filter.
Purging Alarms for SNMP Traps
You can remove an alarm from the list of alarms by changing its status to Acknowledged or Cleared. No e-mails will be generated for these alarms.
Step 1 Log in to Prime Infrastructure.
Step 2 Select Monitor > Alarms and Events .
Step 3 Select an alarm, then choose Change Status > Acknowledge or Change Status > Clear .
Troubleshooting Prime Infrastructure SNMP Traps
If you are having trouble with Prime Infrastructure's internal traps and related notifications, check the following:
Step 1 Ping the notification receiver from the Prime Infrastructure server, to ensure that there is connectivity between Prime Infrastructure and your management application.
Step 2 Check if any firewall ACL settings are blocking port 162, and open communications on that port if needed.
Step 3 Log in to Prime Infrastructure with a user ID that has administrator privileges. Select Administration > Logging and download the log files. Then compare the activity recorded in these log files with the activity you are seeing in your management application:
- ncs_nb.log: This is the log of all the northbound SNMP trap messages Prime Infrastructure has sent. Check for messages you have not received.
- ncs- # - # .log: This is the log of most other recent Prime Infrastructure activity. Check for hardware trap messages you have not received.
- hm- # - # .log: This is the log of all Health Monitor activity. Check for recent messages about High Availability state-changes and application-process failures that you have not received.
The messages you see in these logs should match the activity you see in your management application. If you find major differences, open a support case with Cisco Technical Assistance Center (TAC) and attach the suspect log files with your case.
Feedback