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 [ categories ];
destination-port <port-number>;
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.
Each trap group you define must have a name and one or more targets, which are the systems that receive the SNMP traps. Specify the targets by IPv4 or IPv6 address, not by hostname.
Specify the types of traps the trap group can receive in the categories statement. For information about which category traps belong to, see Standard SNMP Traps and Juniper Networks Enterprise-Specific SNMP Traps.
A trap group can receive the following categories:
-
authentication—Authentication failures -
chassis—Chassis/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
linktrap category.
-
remote-operations—Remote operation notifications -
rmon-alarm—Alarm for RMON events -
routing—Routing protocol notifications -
sonet-alarms—SONET/SDH alarms
-
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 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—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—VRRP events such as new-master or authentication failures
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 on the version statement, see version.
Example: Configuring SNMP Trap Groups
Set up a trap notification list named urgent-dispatcher for link and startup traps. This list is used to identify the network management hosts (1.2.3.4 and fe80::1:2:3:4) to which traps generated by the local router should be sent. The name specified for a trap group is used as the SNMP community string when the agent sends traps to the listed targets.
[edit]
snmp {
trap-group "urgent-dispatcher" {
version v2;
categories link startup;
targets {
1.2.3.4;
fe80::1:2:3:4;
}
}
}