Discussion

Finally, configure which traps the NMS systems receive and the security used when
sending the traps:
[edit snmp v3]
aviva@router1# set target-parameters nms2-parameters notify-filter config-traps
aviva@router1# set target-parameters nms2-parameters parameters message-processingmodel
v3
aviva@router1# set target-parameters nms2-parameters parameters security-model usm
aviva@router1# set target-parameters nms2-parameters parameters security-level
privacy
aviva@router1# set target-parameters nms2-parameters parameters security-name nms2
Discussion
The configuration of SNMPv3 traps is much more involved than for SNMPv2, so
let’s look at each step of the process. The first part of this recipe sets up traps for the
objects related to the hardware chassis components.
First, configure a notification. SNMPv3 defines two types of notifications: informational
and trap. You want to set type trap. You’ll also want to name the notification
with the tag statement (here, chassis-trap-receivers) so that later in the configuration,
you can associate the trap type with the NMS system that will be receiving the
traps.
Second, create a filter that identifies which traps are sent to the NMS. Here, the filter
named chassis-traps sends all traps from the Juniper chassis MIB.
Next, define the NMS systems to receive the trap notifications in the target-address
statement hierarchy. Each target has a name, here nms1, which is the username of the
NMS (also referred to as the security name). Then set the NMS system’s address and
associate a tag list and security parameters with it. Here, we associate the chassistrap-receivers
tag and the nms1-parameters security parameters, which we define
next.
Finally, associate a trap notification filter with the target NMS system (here, the
chassis-traps filter) and define the security to use in all trap message exchanges.
SNMPv3 security has three components: the message-processing model, the security
model, and the security level. The processing model is SNMPv1, SNMPv2, or SNMPv3,
which corresponds to the v1, v2, and v3 options of the message-processing-model statement.
The security model is SNMPv1, SNMPv2, or USM, corresponding to the v1,
v2c, and usm options of the security-model statement. Finally, the security level can
be noAuthnoPriv, authNoPriv, orauthPriv, which match the none, authentication, and
privacy options of the security-level statement. Bundled in with defining the security
parameters is the username (security name) of the receiving NMS system. Here,
the security-name nms1 statement associates the security parameters with the system
we defined in the target-address nms1 statement hierarchy.
This is the Title of the Book, eMatter Edition
Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.
Setting Up SNMPv3 Traps | 159