RFC 2051 (rfc2051) - Page 2 of 124
Definitions of Managed Objects for APPC using SMIv2
Alternative Format: Original Text Document
RFC 2051 SNANAU APPC MIB using SMIv2 October 1996 purpose of management. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. 3. Overview This document identifies the proposed set of objects for managing the configuration, monitoring and controlling devices with APPC capabilities. APPC is the aspect of SNA which supports peer-to-peer communication, and provides the interface for applications to communicate. In this document, we will describe LU6.2 protocol- specific managed objects. This document describes both dependent and independent LU 6.2 protocols. A dependent LU requires assistance from an SSCP in order to activate an LU 6.2 session. An independent LU is able to activate an LU 6.2 session without assistance from the SSCP. If the agent supports dependent LU 6.2 only, the SNA NAU MIB, RFC 1666 [7] is used instead to represent those objects. Local LUs and partner LUs connect with each other using sessions. Multiple different sessions can be established between LUs with characteristics defined by Modes. Session limits within a defined Mode are negotiated between the local and partner LUs using a protocol called CNOS (Change Number of Sessions). Transaction Programs (TPs) are applications that use sessions to communicate with each other. Multiple TPs can use the same session, but not at the same time. A single usage of a session is called a conversation. While a session can stay active for a long time, a conversation can come up and down based on usage by the TPs. Common Programming Interface - Communications (CPI-C) is a standard API (Application Programming Interface) for APPC and OSI TP that is used by TPs for accessing conversations. Although, many of the CPI-C objects in this MIB are relevant to both APPC and OSI TP, the intention is for managing APPC products only. SNA names such as LU names, CP names, mode names, and COS names can be padded with space characters in SNA formats. These space characters are insignificant. For example, in a BIND RU a mode name of "#INTER" with a length of 6 is identical to a mode name of "#INTER " with a length of 8. However, in this MIB, insignificant space characters are not included by the agent. Using the mode name from the previous example, an agent would return a length of 6 and the Allen, et. al. Standards Track
