JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Solaris System Management Agent Administration Guide
search filter icon
search icon

Document Information

Preface

1.  Introduction to the System Management Agent

2.  Configuring the System Management Agent

3.  Working with the System Management Agent

Starting and Stopping the System Management Agent

To Start the System Management Agent

To Restart the System Management Agent

To Stop the System Management Agent

Common Operations With the System Management Agent

To Check Whether Another Process Is Running on the SMA Port

To View the Status of the Agent

To See Which MIBs Are Initialized

To Check the Disk Space on a Local or Remote Machine

The snmpnetstat command

Resource Usage

JDMK Interoperability

Configuration and Proxying With JDMK

4.  Managing Security

5.  Migrating From Other Agents

A.  Tools and Man Pages

Glossary

Index

Starting and Stopping the System Management Agent

Start or stop the SMA by starting or stopping the snmpd daemon. Numerous options are available for starting or stopping the daemon, but several of these options override the snmpd.conf and snmp.conf files. The recommended way to start and stop the System Management Agent is to use the svcadm command as described in this section. Further information on the snmpd daemon can be found in the snmpd(1M) man page.


Note - As a standard SNMP agent, the System Management Agent must run on port 161. If another process is running on port 161, the System Management Agent does not start.


To Start the System Management Agent

Once the svcadm command has launched the System Management Agent on your system, the snmpd daemon always starts at boot time during the Solaris system boot. If you are using other agents, you might want to prevent the snmpd daemon from starting at boot time, which initializes the System Management Agent. If you want to prevent the snmpd daemon from starting at boot time, see To Prevent The System Management Agent Initializing at Boot Time.

  1. As root, start the SMA service.
    # svcadm enable svc:/application/management/sma:default
  2. Check whether errors occurred in attempting to start the System Management Agent by examining the /var/log/snmpd.log file.

    If the log file reports that the port 161 is occupied, follow the procedure described in To Check Whether Another Process Is Running on the SMA Port.

To Restart the System Management Agent

To enable changes made to the main SMA configuration file, /etc/sma/snmp/snmpd.conf, a signal must be sent to the SMA daemon, snmpd. This signal reads the changes to snmpd.conf and restarts the System Management Agent.

To Stop the System Management Agent