Related Documentation
- M, MX, PTX, T Series
- Understanding SNMP Implementation in Junos OS
- Configuring SNMP on Devices Running Junos OS
- Monitoring SNMP Activity and Tracking Problems That Affect SNMP Performance on a Device Running Junos OS
- Optimizing the Network Management System Configuration for the Best Results
- Configuring Options on Managed Devices for Better SNMP Response Time
- M, MX, QFX, T Series
- Using the Enterprise-Specific Utility MIB to Enhance SNMP Coverage
Managing Traps and Informs
The following sections contain a few tips on managing SNMP notifications:
Generating Traps Based on SysLog Events
Event policies can include an action that raises traps for events based on system log messages. This feature enables notification of an SNMP trap-based application when an important system log message occurs. You can convert any system log message,for which there is no corresponding trap, into a trap. If you are using network management system traps rather than system log messages to monitor your network, you can use this feature to ensure that you are notified of all the major events.
To configure a policy that raises a trap on receipt of an event, include the following statements at the [edit event-options policy policy-name] hierarchy level:
The following example shows the sample configuration for raising a trap for the event ui_mgd_terminate:
Generating Traps Based on SysLog Events
Filtering Traps Based on the Trap Category
SNMP traps are categorized into many categories. The Junos OS provides a configuration option, categories at the [edit snmp trap-group trap-group] hierarchy level, that enables you to specify categories of traps that you want to receive on a particular host. You can use this option when you want to monitor only specific modules of the Junos OS.
The following example shows a sample configuration for receiving only link, vrrp-events, services, and otn-alarms traps:
Filtering Traps Based on the Object Identifier
The Junos OS also provides a more advanced filter option that enables you to filter out specific traps based on their object identifiers. You can use the notify-filter option to filter out a specific trap or a group of traps.
The following example shows the sample configuration for excluding Juniper Networks enterprise-specific configuration management traps (note that the SNMPv3 configuration also supports filtering of SNMPv1 and SNMPv2 traps as is shown in the following example):
Related Documentation
- M, MX, PTX, T Series
- Understanding SNMP Implementation in Junos OS
- Configuring SNMP on Devices Running Junos OS
- Monitoring SNMP Activity and Tracking Problems That Affect SNMP Performance on a Device Running Junos OS
- Optimizing the Network Management System Configuration for the Best Results
- Configuring Options on Managed Devices for Better SNMP Response Time
- M, MX, QFX, T Series
- Using the Enterprise-Specific Utility MIB to Enhance SNMP Coverage
Published: 2012-12-08
Related Documentation
- M, MX, PTX, T Series
- Understanding SNMP Implementation in Junos OS
- Configuring SNMP on Devices Running Junos OS
- Monitoring SNMP Activity and Tracking Problems That Affect SNMP Performance on a Device Running Junos OS
- Optimizing the Network Management System Configuration for the Best Results
- Configuring Options on Managed Devices for Better SNMP Response Time
- M, MX, QFX, T Series
- Using the Enterprise-Specific Utility MIB to Enhance SNMP Coverage
