5.5 HP StorageWorks X9720 Network Storage System Administrator Guide (AW549-96026, March 2011)

The update command for SNMPv1 and v2 uses optional community names. By convention, the default
READCOMMUNITY name used for read-only access and assigned to the agent is public. No default
WRITECOMMUNITY name is set for read-write access (although the name private is often used).
The following command updates a v2 agent with the write community name private, the agent’s
system name, and that system’s physical location:
ibrix_snmpagent -u –v 2 -w private -n agenthost.domain.com -o DevLab-B3-U6
The SNMPv3 format adds an optional engine id that overrides the default value of the agent’s host
name. The format also provides the -y and -z options, which determine whether a v3 agent can
process v1/v2 read and write requests from the management station. The format is:
ibrix_snmpagent -u –v 3 [-e engineId] [-p PORT] [-r READCOMMUNITY]
[-w WRITECOMMUNITY] [-t SYSCONTACT] [-n SYSNAME] [-o SYSLOCATION]
[-y {yes|no}] [-z {yes|no}] [-c {yes|no}] [-s {on|off}]
Configuring trapsink settings
A trapsink is the host destination where agents send traps, which are asynchronous notifications sent
by the agent to the management station. A trapsink is specified either by name or IP address. X9000
Software supports multiple trapsinks; you can define any number of trapsinks of any SNMP version,
but you can define only one trapsink per host, regardless of the version.
At a minimum, trapsink configuration requires a destination host and SNMP version. All other
parameters are optional and many assume the default value if no value is specified. Trapsink
configuration for SNMPv3 is more detailed than for earlier versions. The main differences involve the
additional security parameters added by SNMPv3.
The format for creating a v1/v2 trapsink is:
ibrix_snmptrap -c -h HOSTNAME -v {1|2} [-p PORT] [-m COMMUNITY] [-s {on|off}]
If a port is not specified, the command defaults to port 162. If a community is not specified, the
command defaults to the community name public. The -s option toggles agent trap transmission
on and off. The default is on. For example, to create a v2 trapsink with a new community name, enter:
ibrix_snmptrap -c -h lab13-116 -v 2 -m private
For a v3 trapsink, additional options define security settings. USERNAME is a v3 user defined on the
trapsink host and is required. The security level associated with the trap message depends on which
passwords are specified—the authentication password, both the authentication and privacy passwords,
or no passwords. The CONTEXT_NAME is required if the trap receiver has defined subsets of managed
objects. The format is:
ibrix_snmptrap -c -h HOSTNAME -v 3 [-p PORT] -n USERNAME [-j {MD5|SHA}]
[-k AUTHORIZATION_PASSWORD] [-y {DES|AES}] [-z PRIVACY_PASSWORD]
[-x CONTEXT_NAME] [-s {on|off}]
The following command creates a v3 trapsink with a named user and specifies the passwords to be
applied to the default algorithms. If specified, passwords must contain at least eight characters.
ibrix_snmptrap -c -h lab13-114 -v 3 -n trapsender -k auth-passwd -z priv-passwd
Associating events and trapsinks
Associating events with trapsinks is similar to associating events with email recipients, except that you
specify the host name or IP address of the trapsink instead of an email address.
Use the ibrix_event command to associate SNMP events with trapsinks. The format is:
Configuring cluster event notification46