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

<installdirectory>/bin/ibrix_event -c -y SNMP [-e ALERT|INFO|EVENTLIST]
-m TRAPSINK
For example, to associate all Alert events and two Info events with a trapsink at IP address
192.168.2.32, enter:
<installdirectory>/bin/ibrix_event -c -y SNMP -e ALERT,server.registered,
filesystem.created -m 192.168.2.32
Use the ibrix_event -d command to dissociate events and trapsinks:
<installdirectory>/bin/ibrix_event -d -y SNMP [-e ALERT|INFO|EVENTLIST] -m TRAPSINK
Defining views
A MIB view is a collection of paired OID subtrees and associated bitmasks that identify which
subidentifiers are significant to the view’s definition. Using the bitmasks, individual OID subtrees can
be included in or excluded from the view.
An instance of a managed object belongs to a view if:
• The OID of the instance has at least as many sub-identifiers as the OID subtree in the view.
• Each sub-identifier in the instance and the subtree match when the bitmask of the corresponding
sub-identifier is nonzero.
The management console automatically creates the excludeAll view that blocks access to all OIDs.
This view cannot be deleted; it is the default read and write view if one is not specified for a group
with the ibrix_snmpgroup command. The catch-all OID and mask are:
OID = .1
Mask = .1
Consider these examples, where instance .1.3.6.1.2.1.1 matches, instance .1.3.6.1.4.1 matches,
and instance .1.2.6.1.2.1 does not match.
OID = .1.3.6.1.4.1.18997
Mask = .1.1.1.1.1.1.1
OID = .1.3.6.1.2.1
Mask = .1.1.0.1.0.1
To add a pairing of an OID subtree value and a mask value to a new or existing view, use the
following format:
ibrix_snmpview -a -v VIEWNAME [-t {include|exclude}] -o OID_SUBTREE [-m MASK_BITS]
The subtree is added in the named view. For example, to add the X9000 Software private MIB to the
view named hp, enter:
ibrix_snmpview -a -v hp -o .1.3.6.1.4.1.18997 -m .1.1.1.1.1.1.1
Configuring groups and users
A group defines the access control policy on managed objects for one or more users. All users must
belong to a group. Groups and users exist only in SNMPv3. Groups are assigned a security level,
which enforces use of authentication and privacy, and specific read and write views to identify which
managed objects group members can read and write.
The command to create a group assigns its SNMPv3 security level, read and write views, and context
name. A context is a collection of managed objects that can be accessed by an SNMP entity. A
related option, -m, determines how the context is matched. The format follows:
X9720 Network Storage System Administrator Guide 47