You can configure SNMP by completing
the following procedure.
About this task
The
IBM® Tivoli® Storage Manager SNMP set
up procedure is illustrated by
Figure 1:
Figure 1. IBM Tivoli Storage Manager SNMP Set
Up
To set up
Tivoli Storage
Manager monitoring
through SNMP, do the following:
Procedure
- Modify
the server options file to specify the SNMP communication
method. Figure 2 displays an
example of a SNMP communication method setting in the server options
file.
You must specify the COMMMETHOD
and SNMPSUBAGENT options. The SNMPSUBAGENT option must specify a host
that is an AIX® system with a
DPI-enabled SNMP agent, such as the SystemView® agent.
Figure 2. Example of SNMP communication method options commmethod snmp
snmpsubagent hostname jimbo communityname public timeout 600
snmpsubagentport 1521
snmpheartbeatinterval 5
snmpmessagecategory severity
For
details about server options, see the server options section
in Administrator's Reference.
- Install, configure, and
start the SNMP agent as described
in the documentation for that agent. The SNMP agent must support
the DPI Version 2.0 standard. Tivoli Storage
Manager supports
the SNMP agent that is built into the AIX operating system.
Configure the AIX SNMP agent by customizing the
SNMP
file; the SNMP, V1 file is named:
/etc/snmpd.conf, the SNMP,
V3 file is named:
/etc/snmpdv3.conf. A default configuration
for SNMP, V1 might look like this:
logging file=/var/snmp/snmpd.log enabled
logging size=0 level=0
community public
community private 127.0.0.1 255.255.255.255 readWrite
community system 127.0.0.1 255.255.255.255 readWrite 1.17.2
view 1.17.2 system enterprises view
trap public <snmp_manager_ip_adr> 1.2.3 fe
snmpd maxpacket=16000 smuxtimeout=60
smux 1.3.6.1.4.1.2.3.1.2.2.1.1.2 public
where is
the IP address of the system running the SNMP management application.
Attention: The trap statement also defines
the
system to which the AIX SNMP
agent forwards traps that it receives.
Before starting the
agent, ensure that the
dpid2 and
snmpd subsystems have
been started.
Important: The dpid2 subsystem is started
automatically through the snmpd subsystem in SNMP, V3. The dpid2
subsystem must be manually started independently of the snmpd subsystem
with SNMP, V1.
The snmpd and dpid2 subsystem
status can be reviewed by issuing the following commands:
lssrc -s snmpd
lssrc -s dpid2
The subsystems can be started by issuing
the following commands:
startsrc -s dpid2
startsrc -s snmpd
- Start the Tivoli Storage
Manager SNMP subagent
by running the dsmsnmp executable.
- Start the Tivoli Storage
Manager server to
begin communication through the configured TCP/IP port with the subagent.
- Begin event logging for the SNMP receiver, and enable
events
to be reported to SNMP. For example, issue the following commands:
begin eventlogging snmp
enable event snmp all
- Define the Tivoli Storage
Manager SNMP MIB
values for the SNMP manager to help format and display the Tivoli Storage
Manager SNMP MIB
variables and messages. The adsmserv.mib file ships with the Tivoli Storage
Manager server and
must be loaded by the SNMP manager. This file is in the installation
directory of the server. For example, when you run NetView® for Windows as
an SNMP manager, the adsmserv.mib file is copied to the \netview_path\SNMP_MIB directory
and then loaded through the following command:
[C:\] loadmib -load adsmserv.mib