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.
You use monitoring templates to enable Prime Infrastructure to monitor network device metrics such as CPU and memory utilization statistics and alert you of changing conditions before any issues can impact operation.
Table 5-1 describes the process for creating and deploying monitoring templates.
|
|
---|---|
1. |
Under the Design menu, choose which type of template to create. |
2. |
After you have created the template, click the Publish icon to publish the template and make it available to be deployed. |
3. |
Under the Deploy menu, choose which template to deploy. See Designing Monitoring Configurations for more information. |
4. |
Choose Tools > Task Manager > Jobs Dashboard to verify the status of the template deployment. |
Prime Infrastructure provides the following types of monitoring templates:
•Device Health—See Creating Health Monitoring Templates.
•Interface Health—See Creating Health Monitoring Templates.
•Threshold—See Defining Thresholds.
•SNMP Polling—See Designing Custom SNMP Monitoring Templates
You use health monitoring templates to enable Prime Infrastructure to monitor network device metrics such as CPU and memory utilization statistics and alert you of changing conditions before the issues impact their operation.
To create a template to monitor overall device health:
Step 1 Choose Design > Monitoring Templates.
Step 2 Expand Features, then Metrics, then click Device Health or Interface Health.
Step 3 Enter the basic template information.
Step 4 Under Template Content, choose the parameters to monitor. To change a parameter, click the parameter name, description, or polling frequency value and change the field.
Step 5 Click Save.
Step 6 Click Save As New Template.
Step 7 Navigate to the My Templates folder and choose the template you just saved.
Step 8 Click the Go to Deployment icon at the top-right corner.
Step 9 Select the template you created, then click Deploy.
Step 10 Choose the devices or device groups on which to deploy the template, then click Submit.
You use monitoring templates to define thresholds. When the thresholds you specify are reached, Prime Infrastructure issues an alarm.
To define thresholds:
Step 1 Choose Design > Monitoring Templates.
Step 2 Under Features, choose Threshold.
Step 3 Complete the basic template fields.
Step 4 Under Feature Category, choose one of the following metrics:
•Device Health—Allows you to change threshold values for CPU utilization, memory pool utilization, and environment temperature
•Interface Health—Allows you to change threshold values for the number of outbound packets that are discarded.
Step 5 Under Metric Parameters, choose the threshold setting you want to change, then click Edit Threshold Setting.
Step 6 Enter a new value and choose the alarm severity for the threshold.
Step 7 Click Done.
Step 8 Click Save as New Template.
Step 9 Under the My Templates folder, navigate to the template you created and select it.
Step 10 Click Go to Deployment.
Step 11 Select the template you created, then click Deploy.
Prime Infrastructure allows you to design custom SNMP polling templates to monitor third-party devices and device groups. You can also use these templates for Cisco devices and device groups. You can upload the SNMP MIB for the device type, then choose devices and attributes to poll and the polling frequency. You can upload one MIB, or a package of MIBs in a ZIP file. You publish and deploy the custom SNMP polling template the same way as other monitoring templates, and you can display the results in the form of a line chart or a table. This feature enables you to easily repeat polling for the same devices and attributes, and can be used to customize the way Cisco devices are polled using SNMP.
To create a custom SNMP polling template:
Step 1 Choose Tools > Custom SNMP Template.
Step 2 On the Basic tab, make entries for the following:
•Name—Name of the custom SNMP template.
•MIBs—Select a MIB from the list. If you want to use a new MIB, click UploadMIB to browse for the MIB file you want to use. You can upload a single MIB file, or a group of MIBs with their dependencies as a zip file. Specify a filename extension only if you are uploading a zip file.
•Tables—Choose the table you want to poll from the list of tables supported in the MIB you selected. A list of attributes is displayed, based on the table type you selected. Choose the parameters that you want for your template.
Step 3 If you want to edit the generated configuration file, click the Advanced tab and make your changes. It is usually useful to change the Display name and Description for the attributes. Be aware that the configuration file must remain a valid XML file after your changes.
Step 4 Click Save.
Step 5 On the Monitoring Template page, choose Features > Custom SNMP and select your new custom SNMP template.
Step 6 Under Template Basics, make entries for the following:
•Name—Name of the design instance of your custom SNMP template.
•Description.
•Author Contact.
Step 7 Under Template Content, select a polling frequency from the Select Polling Frequency drop-down menu.
Step 8 Click Save As New Template.
Related Topics
•Deploying Custom SNMP Polling Templates,
•Viewing Custom SNMP Polling Results, page
The most common reasons that a template might not be deployed are:
•One or more devices are unreachable.
•A device CLI returned an error because the CLI was incorrect.
Need to add information about how to test, say, a threshold template to make sure it's set up right, so it's not, say, generating flapping alarms because the tolerances are set to tight. We can also give advice on Admin stuff like setting the monitoring threshold in Administration and take that out of Administration.