Juniper JUNOSE 11.3, Configuration Manual

Page: 190 / 632

•
You can enable the traps listed in “Trap Categories” on page 157.
•
You can filter traps according to the trap severity levels described in Table 22 on page 158.
•
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.
snmp-server enable traps per-category-trapFilters
•
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.
NOTE: This command does not modify the severity level set for specific
hosts using the snmp-server host command.
•
If you configure global severity levels for different categories in succession, the last
global severity level you configure is applied to all categories.
•
Example 1—Configuring the per-category severity level without changing the global
severity level
1.
Configure the global severity level as critical for all enabled trap categories by
specifying the SONET trap category.
host1(config)# snmp-server enable traps sonet trapFilters critical
2.
Configure the global severity level as notice for all enabled trap categories by
specifying the BGP trap category.
host1(config)# snmp-server enable traps bgp trapFilters notice
3.
Configure the per-category severity level as debug for the SONET trap category.
host1(config)# snmp-server enable traps sonet per-category-trapFilters debug
In this example, although you configure the category-specific severity level as debug
for the SONET category in Step 3, the global severity level remains unchanged as
notice . This behavior occurs because only the category-specific severity level was
configured in the last operation.
•
Example 2—Overwriting the global severity level to the last-configured setting
Copyright © 2010, Juniper Networks, Inc. 160
JunosE 11.3.x System Basics Configuration Guide