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

4.  Managing Security

5.  Migrating From Other Agents

A.  Tools and Man Pages

Glossary

Index

Glossary

agent

A software program, typically run on a managed device, that implements the SNMP protocol. The program also services the requests of a manager. Agents can act as proxies for some non-SNMP manageable network nodes.

Agent Extensibility Protocol (AgentX)

A subagent protocol that can communicate with a master SNMP agent.

configuration token

Tokens can be identifiers, keywords, constants, punctuation, or white space.

context

A collection of managed objects that are accessible by an SNMP entity. The name for a subset of managed objects.

DAQ

Data acquisition.

DES

Data Encryption Standard

legacy subagent

See proxy agent.

Management Information Base (MIB)

A virtual information store for managed objects. MIBs define the properties of a managed object within the device to be managed.

manager

A client application that accesses data from a managed device or system.

master agent

An agent running on a designated port.

MD5

The message digest function defined in RFC 1321.

MIB II

The current standard definition of the virtual file store for objects that can be managed by SNMP.

mib2c

A utility that compiles MIBs and generates a syntax template for MIB implementation.

net-snmp

The Open Source version of the SMA. SMA uses net-snmp base functionality and supports SNMP protocol versions 1, 2, and 3.

Object Identifier (OID)

Every managed object, whether the object is a device or the characteristics of a device, has a name, a syntax, and an encoding. The name, an object identifier (OID), uniquely identifies the object. The OID is written as a sequence of integers separated by periods. For example, the sequence 1.3.6.1.2.1.1.1.0 specifies the system description within the system group of the management subtree.

PDU

Protocol Data Unit. This unit defines the type of SNMP message. A PDU contains control fields and an array of pairs. The control fields are dependent on the message type. The first element of each of the pairs in the array identifies management data. The second element of each of the pairs in the array specifies the value of this management data.

proxy agent

An agent that acts on behalf of a non-SNMP (foreign) network device. The management station contacts the proxy agent and indicates the identity of the foreign device. The proxy agent translates the protocol interactions it receives from the management station into the interactions supported by the foreign device.

SHA1

Secure Hash Algorithm - Version 1.0. SHA is a cryptographic message digest algorithm.

Structure of Management Information (SMI)

An industry-accepted method of organizing object names so that logical access can occur. The SMI states that each managed object must have a name, a syntax, and an encoding. The name, an object identifier (OID), uniquely identifies the object. The syntax defines the data type, such as an integer or a string of octets. The encoding describes how the information associated with the managed objects is serialized for transmission between machines.

subagent

An agent that interacts with a master agent.

System Management Agent (SMA)

An management agent based on open source Net-SNMP but carrying some Sun modifications and additional tools and wrappers.

trap

A message sent to a manager that describes exceptions that occurred on a managed device.

USM

User-based Security Model. A standard for providing SNMP message-level security, described in RFC 3414 at . This RFC document also includes a MIB for remotely monitoring and managing the configuration parameters for the User-based Security Model.

VACM

View-Based Access Control Mechanism. A standard for controlling access to management information, described in RFC 3415 at . This RFC document also includes a MIB for remotely managing the configuration parameters for the View-based Access Control Model.