Juniper SYSTEM BASICS - CONFIGURATION GUIDE V 11.1.X Configuration Manual page 200

JUNOSe 11.1.x System Basics Configuration Guide
Trap filters work as follows:
1.
2.
3.
To set up global severity filters, use the snmp-server enable traps command. To
specify the trap severity level for a particular category, use the snmp-server enable
traps per-category-trapFilters command. To set up a severity filter for a specific
host, use the snmp-server host command.
snmp-server enable traps
snmp-server enable traps per-category-trapFilters
170
Configuring Traps
An event is posted to the SNMP agent.
The system determines whether the corresponding trap category is globally
enabled and whether the trap meets the minimum severity level for the trap
category. If the per-category filter is not defined for this trap, the global trap
severity applies.
If the trap does not meet these criteria, the system discards the trap.
If the trap does meet these criteria, the trap goes to the trap host processor.
The trap host processor determines whether the trap category is enabled on the
host and whether the trap meets the minimum severity level set for the host.
If the trap does not meet these criteria, the system discards the trap.
If the trap does meet these criteria, the trap is sent to the trap recipient.
Use to enable and configure SNMP trap generation on a global basis.
Traps are unsolicited messages sent from an SNMP server (agent) to an SNMP
client (manager).
You can enable the traps listed in "Trap Categories" on page 168.
You can filter traps according to the trap severity levels described in Table 22
on page 169.
If you do not specify a trap option, all options are enabled or disabled for the
trap type.
Example
host1(config)#snmp-server enable traps atmPing trapfilters critical
Use the no version to disable SNMP trap generation.
See snmp-server enable traps.
Use to specify the trap severity level for a particular category without overwriting
the existing global severity level, which applies to all enabled categories configured
on the router.
If you change the global trap severity level (which applies to all enabled categories)
after you set the per-category trap severity level, the global severity level takes
precedence over the per-category severity level.
If you do not configure the per-category severity level, the global trap severity
level (which applies to all enabled categories) takes effect for that category.