Sun Microsystems Netscape Enterprise Server, Руководство администратора

Страница: 214 / 532

Enabling and Starting the SNMP Master Agent
214 Netscape Enterprise Server Administrator’s Guide
Starting the SNMP Master Agent
Once you have installed the SNMP master agent, you can start it manually or by
using Enterprise Server.
Note
After you have installed and enabled the master agent and the subagent, if the
master agent terminates, the subagent does not terminate with the master agent.
Instead, the subagent consumes the CPU usage and cause the server to dump
core. If you notice such unusual behavior, make sure that the master agent is
running.
Manually Starting the SNMP Master Agent
To start the master agent manually, enter the following at the command
prompt:
# magt CONFIG INIT&
The
INIT
file is a nonvolatile file that contains information from the MIB-II
system group, including system location and contact information. If
INIT
doesn’t already exist, starting the master agent for the first time will create it. An
invalid manager name in the
CONFIG
file will cause the master agent start-up to
fail.
To start a master agent on a nonstandard port, use one of two methods:
Method one: In the
CONFIG
file, specify a transport mapping for each
interface over which the master agent listens for SNMP requests from managers.
Transport mappings allow the master agent to accept connections at the
standard port and at a nonstandard port. The master agent can also accept
SNMP traffic at a nonstandard port. The maximum number of concurrent SNMP
is limited by your target system’s limits on the number of open sockets or file
descriptors per process. Here is an example of a transport mapping entry:
TRANSPORT extraordinary SNMP
OVER UDP SOCKET
AT PORT 11161
After editing the
CONFIG
file manually, you should start the master agent
manually by typing the following at the command prompt:
# magt CONFIG INIT&