You use SNMP (Simple Network Management Protocol) to direct a process, called an agent, on the filer to perform network management tasks such as gathering status and diagnostic information. The information is sent to network management stations, which are client workstations on a network. The network management stations use third-party applications to process the information.
The information that is exchanged to perform these tasks is described in ASCII files called Management Information Bases (MIBs).
For diagnostic and other network management services, the filer supports the SNMP MIB-II specification. Based on SNMP version 1, this specification provides data about the following MIB-II groups:
SNMP commands enable users to specify up to eight communities and trap notifications for up to eight management stations.
To use SNMP, configure the SNMP agent using the snmp command. A typical set of SNMP commands in the /etc/rc file in the root volume is as follows:
snmp contact 'jdoe@abc.com 415-555-1212'
snmp location 'ABC corporation, engineering lab'
snmp community add ro private
snmp traphost add snmp-mgr1
snmp init
SNMP commands that Network Appliance supports are described in detail in the na_snmp(1) man page. The following paragraphs provide brief explanations of these commands:
Sets the email address and telephone number of the person responsible for the filer. You can include the person's full name, but an email address and a telephone number enable Network Appliance Technical Support to contact the right person after receiving an automatic email message through autosupport from your site concerning your filer status.
Sets the physical location of the filer. This value is returned by the SNMP agent.
Creates a read-only community called private. The SNMP manager uses the community name as a password to communicate with the filer's SNMP agent.
Makes the system snmp-mgr1 the recipient of all SNMP traps from the filer.
Initializes the SNMP daemon with the values specified with snmp commands. This command also sends the SNMP cold start and links up or down traps, as appropriate, to any trap hosts that were previously registered using the snmp traphost command. This command should be the last SNMP command in the filer's /etc/rc file.
Generates asynchronous notification of events, called traps.
The Network Appliance custom MIB provides detailed information about many aspects of filer operation. The current version of the Network Appliance custom MIB is 1.1.2 It contains objects that help you manage multivolume features.
You can obtain the custom MIB from the Data ONTAP CD, or from the NOW Web page at http://www.now.netapp.com. To locate the MIB on the CD, read the intro.txt file.
Install the MIB file on your network management workstation according to the installation procedure for your workstation, so that your workstation can obtain information from the filer about the objects that are part of the MIB.
Single-volume objects are deprecated, but you can use them for single-volume systems as before. If you are using a single-volume filer, you do not need to make changes to use the new MIB.
The descriptions of the deprecated single-volume objects contain the names of the corresponding new multivolume objects. For multivolume objects, use the new objects rather than the deprecated ones.
The top-level groups in the custom MIB and the information they contain are described in the following table
| Group name | Contents |
|---|---|
| cifs | Statistics like those displayed by the cifs stat command. |
| filesys | Information related to the file system, including the equivalent of the maxfiles and df commands, and some of the information from the snap list command. For more information about maxfiles, see "Increasing the maximum number of files." For more information about the df command, see "The df command." For more information about snapshots, see Chapter 11, "Snapshots." |
| nfs | Statistics like those displayed by the nfsstat command, including statistics for each client if per-client statistics are enabled. The per-client statistics are indexed by client IP addresses. |
| product | Product-level information, such as the software version string and the system id. |
| quota | Information related to disk quotas, including the output of the quota report command. To access quota information, quotas must be turned On. For more information about quotas, see "Restricting or tracking disk usage by using disk quotas." |
| raid | Information about raid equivalents to the sysconfig -r output. For more information about sysconfig, see Chapter 20, "System Information and Performance." |
| sysstat | System-level statistics, such as cpu uptime, idle time, and the number of kilobytes transmitted and received on all network interfaces. |
You use the snmp traps command to inspect the value of MIB variables periodically and send an SNMP trap to the machines on the traphost list whenever that value meets the conditions you specify. The traphost list specifies network management stations that receive trap information.
You use the SNMP third-party applications on your network management station to process the trap information. For example, you can set a trap to monitor the fans on a filer and have the SNMP application on your network management station put a flashing message on your console that tells you that a fan has ceased operating.
You can set traps on any numeric variable in the filer's MIB.
You define or change a user-specified trap using the following snmp traps command:
traps trapname.parameter value
trapname is the name of the trap.
value is the value that you assign to the definition.
parameter must be a parameter listed in the following table.
It is important to distinguish between the kind of user-specified traps you can set using the snmp traps command, and the built-in support for traps defined in RFC 1213, such as cold-start. Built-in traps such as cold start are automatically sent to the hosts on the traphosts list when some event (a reboot in the case of a cold start) occurs. User-specified traps only exist after they are defined by a series of snmp traps commands.
Traps are persistent. After you set a trap, it remains across reboots until you specifically remove it.
Refer to the following RFCs (Requests For Comments) for more information:
Copyright © 1999, Network Appliance, Inc. All rights reserved.
Part No. 210-02334
File: net2.htm
Last updated: 04/26/99 08:11:18