Trap Severity Levels

The router provides a method of filtering traps according to severity. Table 23 describes the supported severity levels.

Table 23: Trap Severity Descriptions

You can set up one or more of the following types of trap filters:

• Global—Filters traps by type and severity level across all trap categories
• Per-category—Filters traps for a specific category by type and severity level
• Host-specific—Filters traps on a specific host by type and severity level

Trap filters work as follows:

1. An event is posted to the SNMP agent.
2. 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.
3. 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.

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

• 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 .
• You can filter traps according to the trap severity levels described in Table 23.
• 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 item, 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
  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

  Although you specify the type of SNMP trap category when you configure the global severity level, it takes effect for all enabled trap categories on the router. In this example, after you issue the second command, the global severity level is set as notice for all enabled trap categories.

• Example 3—Overriding the global severity level for a category with the per-category severity level
  1. Configure the global severity level as critical for the SONET trap category in the command.

     host1(config)#snmp-server enable traps sonet trapFilters critical

  2. Change the global severity level to notice for all enabled trap categories.

     host1(config)#snmp-server enable traps bgp trapFilters notice

  3. Configure the per-category severity level as debug for the SONET trap category. This setting overrides the notice trap severity level that was applicable for the SONET trap category.

     host1(config)#snmp-server enable traps sonet per-category-trapFilters debug

  The global severity level is configured as notice for all enabled trap categories except SONET, whose severity level is set as debug. This configuration occurs because the global severity level is overwritten to the last configured value and the per-category severity level takes precedence over the global severity level.

• There is no no version.
• See snmp-server enable traps.

snmp-server host

• Use to configure an SNMP trap host to refine the type and severity to traps that the host receives.
• A trap destination is the IP address of a client (network management station) that receives the SNMP traps.
• You can configure up to eight trap hosts on each virtual router.
• You can enable the traps listed in Trap Categories .
• You can filter traps according to the trap severity levels described in Table 23.
• Example

  host1(config)# snmp-server host 126.197.10.5 version 2c westford udp-port 162 snmp link trapfilters alert

• Use the no version to remove the specified host from the list of recipients.
• See snmp-server host.

snmp-server trap-source

• Use to specify the interface whose IP address is used as the source address for all SNMP traps.

  Note: When there are multiple IP addresses configured on the IP interface that is chosen as the SNMP trap source, the SNMP agent automatically uses the primary IP address of the interface as the SNMP source address on SNMP traps.

• Example

  host1(config)#snmp-server trap-source fastethernet 0/0

• Use the no version to remove the interface from the trap configuration.
• See snmp-server trap-source.

snmp trap ip link-status

• Use to enable link-status traps on an IP interface.
• Example

  host1(config-if)#snmp trap ip link-status

• Use the no version to disable link-status traps on an IP interface.
• See snmp trap ip link-status.

snmp trap ip link-status

• Use to configure the SNMP link-status traps on a particular interface.
• A link-up trap recognizes that a previously inactive link in the network has come up.
• A link-down trap recognizes a failure in one of the communication links represented in the server’s configuration.
• Example

  host1(config-controll)#snmp trap link-status

• Use the no version to disable these traps for the interface.

  Note: This command operates in Controller Configuration mode. It is supported only by the DS3, DS1, and FT1 interface layers.

• See snmp trap ip link-status.

traps

• Use to specify traps for OSPF.
• Example

  host1(config-router-rn)#traps all

• Use the no version to delete the specified trap, group of traps, or all traps.

  Note: For additional information about configuring OSPF-specific traps, see JUNOSe IP, IPv6, and IGP Configuration Guide.

• See traps.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.