RFC 2742 (rfc2742) - Page 3 of 20
Definitions of Managed Objects for Extensible SNMP Agents
Alternative Format: Original Text Document
RFC 2742 Agent X MIB January 2000
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
2. Introduction
The SNMP Agent Extensibility Protocol (AgentX) is a protocol used to
distribute the implementation of an SNMP agent amongst a single
"master agent" and multiple "subagents". See [17] for details about
the AgentX protocol.
The goals of the AgentX MIB are:
- List the set of subagent connections that currently have logical
sessions open with the master agent.
- Identify each subagent connection transport address and type.
- Identify each subagent session vendor, AgentX protocol version,
and other characteristics.
- Identify the set of MIB objects each session implements, the
context in which the objects are registered, and the priority of
the registration.
- Determine protocol operational parameters such as the timeout
interval for responses from a session and the priority at which a
session registers a particular MIB region.
- Allow (but do not require) managers to explicitly close subagent
sessions with the master agent.
3. AgentX MIB Overview
This MIB is organized into four groups. The agentxGeneral group
provides information describing the master agent's AgentX support,
including the protocol version supported. The agentxConnection group
provides information describing the current set of connections
capable of carrying AgentX sessions. The agentxSession group
provides information describing the current set of AgentX sessions.
The agentxRegistration group provides information describing the
current set of registrations.
Three tables form the heart of this mib. These are the connection,
session, and registration tables.
Heintz, et al. Standards Track