Users Guide

40 Setup and Administration
Configuring the SNMP Agent on Systems Running Supported SUSE Linux
Enterprise Server Operating Systems
Server Administrator uses the SNMP services provided by the ucd-snmp or
net-snmp agent. You can configure the SNMP agent to enable SNMP access
from remote hosts, change the community name, enable Set operations, and
send traps to a management station. To configure your SNMP agent for
proper interaction with systems management applications such as
IT Assistant, perform the procedures described in the following sections.
NOTE: On SUSE Linux Enterprise Server (version 10), the SNMP agent
configuration file is located at /etc/snmp/snmpd.conf.
NOTE: See your operating system documentation for additional details about
SNMP configuration.
Sever Administrator SNMP Install Actions
Server Administrator SNMP communicates with the SNMP agent using the
SNMP Multiplexing (SMUX) protocol. When Server Administrator SNMP
connects to the SNMP agent, it sends an object identifier to the SNMP agent
to identify itself as a SMUX peer. Since the object identifier must be
configured with the SNMP agent, Server Administrator adds the following
line to the SNMP agent configuration file, /etc/snmpd.conf or
/etc/snmp/snmpd.conf, during installation if it does not exist:
smuxpeer .1.3.6.1.4.1.674.10892.1
Enabling SNMP Access From Remote Hosts
The default SNMP agent configuration on SUSE Linux Enterprise Server
operating systems gives read-only access to the entire MIB tree for the public
community from the local host only. This configuration does not allow SNMP
management applications such as IT Assistant running on other hosts to
discover and manage Server Administrator systems properly. If Server
Administrator detects this configuration during installation, it logs a message
to the operating system log file, /var/log/messages, to indicate that SNMP
access is restricted to the local host. You must configure the SNMP agent to
enable SNMP access from remote hosts if you plan to manage the system by
using SNMP management applications from remote hosts.
NOTE: For security reasons, it is advisable to restrict SNMP access to specific
remote hosts if possible.