RFC 2155 (rfc2155) - Page 2 of 124

Definitions of Managed Objects for APPN using SMIv2

RFC 2155        Definitions of Managed Objects for APPN        June 1997


   The Framework permits new objects to be defined for the purpose of
   experimentation and evaluation.

3.  Overview

   This document identifies a set of objects for monitoring the
   configuration and active characteristics of devices with APPN
   capabilities, and for controlling certain characteristics.  APPN is
   the aspect of Systems Network Architecture (SNA) that supports peer-
   to-peer networking.  These networks transport both independent and
   dependent LU session traffic.  See the SNANAU APPC MIB [7] and the
   SNA NAU MIB [8] for management of these sessions.  See also the DLUR
   MIB[9], and the HPR MIB[10] for management of extensions to the APPN
   architecture.  In this document, we describe APPN managed objects.

   An APPN network comprises various types of nodes, and transmission
   groups (TGs) that connect the nodes. Network nodes (NNs) provide
   directory and routing functions for session establishment.  NNs may
   be session end points or intermediate nodes in a session.  A border
   node is a type of network node that connects networks together for
   session establishment without fully merging them.  End nodes (ENs)
   are session end points that receive directory and routing functions
   from network nodes, over control-point to control-point (CP-CP)
   sessions.  Low-entry networking (LEN) nodes are also session end
   points, but do not support CP-CP sessions, and therefore need
   additional manual configuration definitions to establish sessions in
   an APPN network.  ENs and LEN nodes may have minimal directory and
   routing functions to establish control sessions (ENs) or to connect
   into the APPN network (LEN nodes).  Virtual routing nodes (VRNs) are
   not really nodes, but rather common definitions among actual nodes in
   a shared transport facility such as a local area network (LAN) that
   allow these actual nodes to temporarily establish a logical link with
   one another without defining each other's link-level addressing
   information.

   Ports and link stations are the node's interface to the data link
   control (DLC), which provides the physical transport, or to another
   protocol such as Data Link Switching (DLSw), which provides transport
   over an IP network.  See the SNADLC SDLC MIB[11], the SNADLC LLC
   MIB[12], and the DLSw MIB[13].  A link station uses a port to make a
   connection to another node.  This connection establishes a TG between
   the two nodes.









Clouston & Moore            Standards Track