RFC 1461 (rfc1461) - Page 3 of 21

SNMP MIB extension for Multiprotocol Interconnect over X

Alternative Format: Original Text Document
< Previous
Next >
RFC 1461        Multiprotocol Interconnect on X.25 MIB          May 1993


3.  Overview

3.1.  Scope

   Instances of the objects defined below provide management information
   for Multiprotocol Interconnect traffic on X.25 as defined in RFC 1356
   [9].  That RFC describes how X.25 can be used to exchange IP or
   network level protocols. The multiprotocol packets (IP, CLNP, ES-IS,
   or SNAP) are encapsulated in X.25 frames for transmission between
   nodes.  All nodes that implement RFC 1356 must implement this MIB.

   The objects in this MIB apply to the software in the node that
   manages X.25 connections and performs the protocol encapsulation.  A
   node in this usage maybe the end node source or destination host for
   the packet, or it may be a router or bridge responsible for
   forwarding the packet.  Since RFC 1356 requires X.25, nodes that
   implement RFC 1356 must also implement the X.25 MIB, RFC 1382.

   This MIB only applies to Multiprotocol Interconnect over X.25
   service. It does not apply to other software that may also use X.25
   (for example PAD).  Thus the presence, absence, or operation of such
   software will not directly affect any of these objects.  (However
   connections in use by that software will appear in the X.25 MIB).

3.2.  Structure of MIB objects

   The objects of this MIB are organized into three tables:  the
   mioxPleTable, the mioxPeerTable, and the mioxPeerEncTable.  All
   objects in all tables are mandatory for conformance with this MIB.

   The mioxPleTable defines information relative to an interface used to
   carry Multiprotocol Interconnect traffic over X.25.  Such interfaces
   are identified by an ifType object in the Internet-standard MIB [4]
   of ddn-x25 or rfc877-x25.  Interfaces of type ddn-x25 have a self
   contained algorithm for translating between IP addresses and X.121
   addresses.  Interfaces of type rfc877-x25 do not have such an
   algorithm.  Note that not all X.25 Interfaces will be used to carry
   Multiprotocol Interconnect traffic. Those interfaces not carrying
   such traffic will not have entries in the mioxPleTable.  The entries
   in the mioxPleTable are only for interfaces that do carry
   Multiprotocol Interconnect traffic over X.25.  Entries in the
   mioxPleTable are indexed by ifIndex to make it easy to find the
   mioxPleTable entry for an interface.

   The mioxPeerTable contains information needed to contact an X.25 Peer
   to exchange packets.  This includes information such as the X.121
   address of the peer and a pointer to the X.25 call parameters needed
   to place the call.  The instance identifiers used for the objects in



Throop
< Previous
Next >