Technical Documentation

Configuring SNMP Trap Groups

You can create and name a group of one or more types of SNMP traps and then define which systems receive the group of SNMP traps. The trap group must be configured for SNMP traps to be sent. To create an SNMP trap group, include the trap-group statement at the [edit snmp] hierarchy level:

[edit snmp]trap-group group-name {categories {category;}destination-port port-number;routing-instance instance;targets {address;}version (all | v1 | v2);}

The trap group name can be any string and is embedded in the community name field of the trap. To configure your own trap group port, include the destination-port statement. The default destination port is port 162.

For each trap group that you define, you must include the target statement to define at least one system as the recipient of the SNMP traps in the trap group. Specify the IPv4 or IPv6 address of each recipient, not its hostname.

Specify the types of traps the trap group can receive in the categories statement. For information about the category to which the traps belong, see the “Standard SNMP Traps Supported on Devices Running JUNOS Software” and “Juniper Networks Enterprise-Specific SNMP Traps” topics in the JUNOS Software SNMP MIBs and Traps Reference.

Specify the routing instance used by the trap group in the routing-instance statement. All targets configured in the trap group use this routing instance.

A trap group can receive the following categories:

  • authentication—Authentication failures
  • chassis—Chassis or environment notifications
  • configuration—Configuration notifications
  • link—Link-related notifications (up-down transitions, DS-3 and DS-1 line status change, IPv6 interface state change, and Passive Monitoring PIC overload)

    Note: To send Passive Monitoring PIC overload interface traps, select the link trap category.

  • remote-operations—Remote operation notifications
  • rmon-alarm—Alarm for RMON events
  • routing—Routing protocol notifications
  • sonet-alarms—SONET/SDH alarms

    Note: If you omit the SONET/SDH subcategories, all SONET/SDH trap alarm types are included in trap notifications.

    • loss-of-light—Loss of light alarm notification
    • pll-lock—PLL lock alarm notification
    • loss-of-frame—Loss of frame alarm notification
    • loss-of-signal—Loss of signal alarm notification
    • severely-errored-frame—Severely errored frame alarm notification
    • line-ais—Line alarm indication signal (AIS) alarm notification
    • path-ais—Path AIS alarm notification
    • loss-of-pointer—Loss of pointer alarm notification
    • ber-defect—SONET/SDH bit error rate alarm defect notification
    • ber-fault—SONET/SDH error rate alarm fault notification
    • line-remote-defect-indication—Line remote defect indication alarm notification
    • path-remote-defect-indication—Path remote defect indication alarm notification
    • remote-error-indication—Remote error indication alarm notification
    • unequipped—Unequipped alarm notification
    • path-mismatch—Path mismatch alarm notification
    • loss-of-cell—Loss of cell delineation alarm notification
    • vt-ais—Virtual tributary (VT) AIS alarm notification
    • vt-loss-of-pointer—VT loss of pointer alarm notification
    • vt-remote-defect-indication—VT remote defect indication alarm notification
    • vt-unequipped—VT unequipped alarm notification
    • vt-label-mismatch—VT label mismatch error notification
    • vt-loss-of-cell—VT loss of cell delineation notification
  • startup—System warm and cold starts
  • vrrp-events—Virtual Router Redundancy Protocol (VRRP) events such as new-master or authentication failures

If you include SONET/SDH subcategories, only those SONET/SDH trap alarm types are included in trap notifications.

The version statement allows you to specify the SNMP version of the traps sent to targets of the trap group. If you specify v1 only, SNMPv1 traps are sent. If you specify v2 only, SNMPv2 traps are sent. If you specify all, both an SNMPv1 and an SNMPv2 trap are sent for every trap condition. For more information about the version statement, see version.


Published: 2010-04-27