Lucent Technologies Stinger, Administration Manual

Page: 165 / 374

Administering the SNMP Agent
Securing the SNMP agent
Stinger® Administration Guide 7-7
Privacy—Protects messages from being copied and interpreted by unauthorized
listeners on the network. “Generating privacy keys” on page 7-9.
Timeliness—Protects against message delay or replay.
Discovery—Allows an SNMP manager to obtain sufficient information about the
Stinger units’ SNMP agent to establish communication between an SNMP
manager station and the Stinger units.
GetBulkRequest—Added from SNMPv2 to allow the SNMPv3 manager to
minimize the number of protocol exchanges required to retrieve a large amount
of management information. The GetBulkRequest protocol data unit (PDU)
allows an SNMPv3 manager to request as large a response as possible.
Enabling SNMPv3 USM privacy
The security-level parameter in the snmp profile specifies the security level of the
SNMP agent when SNMPv3 is in use.
When configuring SNMPv3 USM privacy support, set the security-level parameter
in the snmp profile to auth-priv , as the shown in the following example:
admin> read snmp
SNMP read
admin> set security-level = auth=priv
admin> write
With this setting, the system rejects all user transmissions with a security level of none
or auth-nopriv by sending the error message Unsupported Security Level .
Using the
snmpv3-usm-user
profile
The snmpv3-usm-user profile contains the parameters that support SNMPv3 USM
privacy. You create and edit user profiles in the snmpv3-usm-user profile. The
following example lists the contents of the snmp-usm-user profile, shown with default
settings:
[in SNMPV3-USM-USER/groupz]
name* =groupz
password = feow4873re
active-enabled = no
read-write-access = no
auth-protocol = md5-auth
priv-protocol = no-priv