Package org.snmp4j.agent


package org.snmp4j.agent
  • Class
    Description
    The AgentConfigManager is the main component of a SNMP4J-Agent.
    The BaseAgent abstract class defines a framework for writing SNMP agents using the SNMP4J-Agent API.
    The CommandProcessor is the central glue code that puts together the various sub-systems of a SNMP agent.
    The ContextEvent object describes an event that added or removed a context to/from a system.
    A ContextListener can be informed about new contexts or when a context is removed from a system.
    The DefaultMOContextScope is the default implementation of a MOContextScope representing an OID scope that distinguishes between different contexts.
    The DefaultMOQuery class is the default implementation of a managed object query.
    The DefaultMOScope is the default MOScope and MutableMOScope implementation.
    The default MO server implementation uses a sorted map for the managed object registry.
    A DuplicateRegistrationException is thrown when a managed object registration attempt conflicts with an existing registration because their scope's overlap.
    The ManagedObject interface defines the basic operations for all SNMP(4J) manageable objects.
    The ManagedObjectValueAccess interface provides direct access to instance values of a ManagedObject.
    The MOAccess interface defines means to determine the maximum access supported by a managed object.
    The MOContextScope extends the MOScope by applying a scope to a context.
    The MOException is the base class for all exceptions thrown while managing ManagedObjects.
    A MOGroup instance is a group of ManagedObjects.
    A managed object query is used to lookup managed objects, for example in a MOServer repository.
    The MOQueryWithSource class is the implementation of a managed object query for a Request.
    A managed object scope defines a continuous region within the global OID space.
    The MOScopeComparator compares two scopes with each other.
    The managed object server interface defines the services that a repository of managed objects needs to provide for a command responder.
    A MOServerLookupEvent describes a lookup of a managed object within a MOServer repository.
    An object that is interested in callback notifications of lookup events on a MOServer instance has to implement the MOServerLookupListener interface.
    The MutableMOScope interface describes a mutable scope as needed for query processing.
    The NotificationOriginator specifies the interface for classes providing notification sending.
    The NotificationTask is a Runnable that sends a notifcation or a series of notifications/traps/informs - depending on the configuration associated with the supplied NotificationOriginator.
    The ProxyForwarder class represents a proxy forwarder instance as defined by RFC 3413.
    To (proxy) forward a request or notification to a target, the original command responder event, the context engine ID, and context are required information.
    The ProxyMap maps context engine IDs in conjunction with a proxy usage type to a ProxyForwarder instance.
    A registered ManagedObject has an unique OID that has been registered world-wide by a MIB module.
    A request handler is able to process a request on behalf of the managed object repository represented by a MOServer.
    The SerializableManagedObject interface is implemented by ManagedObjects whose (data) content can be serialized using MOInput and MOOutput.
    The UpdatableManagedObject interface defines the basic operations for all SNMP(4J) manageable objects that need to be updated to reflect the up-to-date state of the managed object.
    The UpdatableMOSupport class provides support for update UpdatableManagedObjects.
    An UpdateStrategy defines how UpdatableManagedObjects are updated on behalf of server queries to a MOServer.