Brocade TurboIron 24X Series Configuration Guide - Manual (Page 205)

Brocade TurboIron 24X Series Configuration Guide 171
53-100305301
SNMP version 3 traps
TurboIron(config)#snmp-server view Maynes system included
TurboIron(config)#snmp-server view Maynes system.2 excluded
TurboIron(config)#snmp-server view Maynes 2.3.*.6 included
TurboIron(config)#write mem
NOTE
The snmp-server view command supports the MIB objects as defined in RFC 1445.
Syntax: [no] snmp-server view <name> <mib_tree> included | excluded
The <name> parameter can be any alphanumeric name you choose to identify the view. The
names cannot contain spaces.
The <mib_tree> parameter is the name of the MIB object or family. MIB objects and MIB sub-trees
can be identified by a name or by the numbers called Object Identifiers (OIDs) that represent the
position of the object or sub-tree in the MIB hierarchy. You can use a wildcard (*) in the numbers to
specify a sub-tree family.
The included | excluded parameter specifies whether the MIB objects identified by the
<mib_family> parameter are included in the view or excluded from the view.
NOTE
All MIB objects are automatically excluded from any view unless they are explicitly included;
therefore, when creating views using the snmp-server view command, indicate which portion of the
MIB you want users to access.
For example, you may want to assign the view called “admin” a community string or user group. The
“admin” view will allow access to the Brocade MIBs objects that begin with the 1.3.6.1.4.1.1991
object identifier. Enter the following command.
TurboIron(config)#snmp-server view admin 1.3.6.1.4.1.1991 included
You can exclude portions of the MIB within an inclusion scope. For example, if you want to exclude
the snAgentSys objects, which begin with 1.3.6.1.4.1.1991.1.1.2 object identifier from the admin
view, enter a second command such as the following.
TurboIron(config)#snmp-server view admin 1.3.6.1.4.1.1991.1.1.2 excluded
NOTE
Note that the exclusion is within the scope of the inclusion.
To delete a view, use the no parameter before the command.
SNMP version 3 traps
Devices support SNMP notifications in SMIv2 format. This allows notifications to be encrypted and
sent to the target hosts in a secure manner.
Defining an SNMP group and specifying which
view is notified of traps
The SNMP group command allows configuration of a viewname for notification purpose, similar to
the read and write view. The default viewname is "all", which allows access to the entire MIB.