Managing SNMP
8-18
Express5800/
ftServer
: System Administrator’s Guide for the Linux Operating System
Verifying Traps
You can easily verify traps using
snmptrapd
on a remote Linux system with
Net-SNMP installed.
1. On the remote Linux system, set up Net-SNMP to autostart, and verify it using the
chkconfig
command, or manually start Net-SNMP.
2. On the ftServer system with the Linux operating system,
Express Builder
, Net-SNMP,
and
ftlSNMP installed, configure
/etc/opt/ft/snmp/snmpd.conf
with trapsink
entries that point to the IP address of a remote management system running
snmptrapd
, by adding lines as follows:
trapcommunity
public
trapsink
ip_address
public
trap2sink
ip_address
public
In this example,
ip_address
is the IP address of the remote management
system.
3. Start (or restart) SNMP using the
/etc/opt/ft/snmp/scripts/start_snmp
(or
/etc/opt/ft/snmp/scripts/restart_snmp
) command for changes to
take effect.
4. From the remote management system, you can view the traps as they are
generated, by tailing /
var/log/messages
(or wherever the remote management
system is configured to log
snmptrapd
messages):
tail -f /var/log/messages
Pulling CPU-I/O enclosures and/or pulling Ethernet cables on the ftServer system will
generate traps, as will exercising the system using the
ftsmaint
command.
Managing SNMP
The following sections discuss how to manage SNMP on your system:
•
‘‘Testing Your SNMP Configuration
”
•
‘‘Managing ftServer Hardware Components”
•
‘‘Testing Ethernet Ports
”
N O T E
The sample command lines in the remainder of this
chapter are for general guidance only. Some of the
command-line details and command output shown—for
