rfc-2051

Definitions of Managed Objects for APPC using SMIv2

M. Allen, B. Clouston, Z. Kielczewski, W. Kwan, B. Moore
date1996-10 streamIETF areartg wgsnanau statusPROPOSED STANDARD pages124 canonicalhttps://www.rfc-editor.org/rfc/rfc2051 doi10.17487/RFC2051
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing the configuration, monitoring and controlling of network devices with APPC (Advanced Program-to-Program Communications) capabilities. This memo identifies managed objects for the SNA LU6.2 protocols. [STANDARDS-TRACK]

Extracted elements (25)

design-rationale §3.1

LU-related objects are split into Admin and Oper tables. Admin tables contain read-only default or expected configuration values; Oper tables contain current operational state such as negotiated parameters. Oper entries can outlive their Admin entries (e.g., a mode definition may be deleted while an active session still uses it), and Admin values may have changed since the Oper entry was created.

snmp

design-rationale §3

The MIB explicitly does not support: modifying APPC defaults, creating or deleting partner LUs/modes/TPs/CPI-C side info, activating or deactivating local or partner LUs, activating or deactivating conversations or TPs, activating sessions, or generating traps. This scope limitation keeps the MIB focused on monitoring and limited control rather than full configuration management.

snmp

design-rationale §3.1.3

There is no appcTpOperTable. Run-time information about Transaction Programs (TPs) tends to be product-specific (e.g., process ID), and much of the relevant information can be derived from the conversation tables instead.

snmp

interoperability-note §3

If an agent supports dependent LU 6.2 only, the SNA NAU MIB (RFC 1666) is used to represent those objects instead of this MIB. This MIB covers both dependent and independent LU 6.2 protocols.

snmp

interoperability-note §3

SNA names such as LU names, CP names, mode names, and COS names may be padded with insignificant trailing space characters in SNA wire formats (e.g., BIND RU), but agents must strip those trailing spaces before exposing the value in the MIB. The sole exception is the all-blank mode name, which is returned as exactly 8 space characters. When an SNA name serves as a table index, trailing spaces are treated as significant by the agent.

snmp

normative-requirement §3.1.1 MUST

All CNOS parameter objects (appcCnosMaxSessLimit, appcCnosMinCwinLimit, etc.) and the three target objects (appcCnosTargetLocLuName, appcCnosTargetParLuName, appcCnosTargetModeName) must be set to their desired values before setting appcCnosCommand to trigger execution of the CNOS verb.

snmp

normative-requirement §4 MUST NOT

Statistical entries are present in the appcSessStatsTable only when the value of appcCntrlOperStat is 'active'. When appcCntrlAdminStat is set to 'notActive', all entries are removed from the appcSessStatsTable.

snmp

protocol-element §4

appcCnosResponsible controls which LU (source or target) is responsible for selecting and deactivating sessions when a CHANGE_SESSION_LIMIT or RESET_SESSION_LIMIT reduces the session limit. The target LU may negotiate 'target' back to 'source', but the source LU cannot negotiate 'source' to 'target'.

snmp

protocol-element §4

appcDefaultTpOperation defines five TP startup modes: other (product-specific), queuedOperatorStarted (operator prompted on first attach, subsequent attaches queued), queuedOperatorPreloaded (attach rejected if TP not started; no operator message; subsequent attaches queued), queuedAmStarted (attach manager starts one instance; subsequent queued), and nonqueuedAmStarted (attach manager starts multiple concurrent instances).

snmp

protocol-element §4

appcLuPairAdminParaSessSup indicates whether multiple parallel sessions between a local and partner LU pair are permitted. When parallel sessions are supported, CNOS is used to negotiate session limits between the LUs.

snmp

protocol-element §4

appcLuPairAdminSecAccept specifies which access security types are accepted on ATTACH requests from a partner LU: none, conversation (user ID + password required), alreadyVerified, persistentVerification, or aVandpV (both already-verified and persistent verification accepted).

snmp, security

protocol-element §4

appcLuPairAdminSessSec specifies session-level security for incoming BIND requests: 'required' means the BIND must carry session-level verification; 'accepted' means it may carry verification and it will be checked; 'notAllowed' means the BIND must not carry session-level verification.

snmp, security

protocol-element §4

Compression negotiation for local LUs is controlled by appcLluAdminCompression (prohibited/required/negotiable) together with separate inbound and outbound compression level objects supporting: none, rle (run-length encoding), lz9, lz10, and lz12 (Lempel-Ziv-like with 9-, 10-, or 12-bit codes). An additional flag (appcLluAdminCompRleBeforeLZ) specifies whether RLE is applied before LZ compression. These values are used during SNA BIND negotiation.

snmp

protocol-element §3.1

The APPC MIB module (appcMIB, OID snanauMIB 3) is organized into six object groups: appcGlobal (global defaults, controls, CNOS commands), appcLu (local LU, partner LU, mode tables), appcTp (transaction program tables), appcSession (active, stats, history, HPR session tables), appcConversation (active and historical conversation tables), and appcCPIC (CPI-C side information tables).

snmp

protocol-element §3.1.1

The appcCnosControl group supports three CNOS commands via appcCnosCommand: initSesslimit (INITIALIZE_SESSION_LIMIT), changeSesslimit (CHANGE_SESSION_LIMIT), and resetSesslimit (RESET_SESSION_LIMIT). Each command requires specific parameter objects (appcCnosMaxSessLimit, appcCnosMinCwinLimit, appcCnosMinClosLimit, appcCnosResponsible, appcCnosDrainPart, appcCnosForce) to be set before writing appcCnosCommand, along with target LU and mode name objects.

snmp

protocol-element §3.1.1

The appcCntrlAdminGroup and appcCntrlOperGroup objects allow management stations to activate and deactivate APPC session statistics collection (appcCntrlAdminStat/OperStat), RSCV collection (appcCntrlAdminRscv/OperRscv), and tracing (appcCntrlAdminTrace/OperTrace). Admin objects hold desired state; Oper objects reflect actual current state. These objects are conditionally mandatory.

snmp

protocol-element §3.1.5

The appcConversation group contains appcActiveConvTable (active conversations with state and type, created on conversation start and removed on end) and appcHistConvTable (abnormally terminated conversations with sense data and log data; number of entries and retention period are implementation-dependent).

snmp

protocol-element §3.1.6

The appcCPIC group contains appcCpicAdminTable and appcCpicOperTable, both indexed by (LocalLuName, SymbolicDestinationName). They hold CPI-C side information including the symbolic destination name and partner LU name. '*ALL' may be used for LocalLuName to indicate that the CPI-C definition applies to all local LUs.

snmp

protocol-element §3.1.2

The appcLuPairAdminTable is indexed by (appcLuPairAdminLocLuName, appcLuPairAdminParLuName). The reserved value '*ALL' for the local LU name indicates the partner LU definition applies to all local LUs. The table captures session limit, session-level security type (required/accepted/notAllowed), access security acceptance level, an InstancePointer to the associated link, and parallel session support.

snmp, security

protocol-element §3.1.2

The appcModeAdminTable is indexed by (LocalLuName, ParLuName, ModeName). It captures mode configuration including COS name, maximum session limit, minimum contention-winner and contention-loser limits, pacing window sizes, preferred and bounded RU sizes, compression settings, sync level, and cryptography support. Reserved '*ALL' values allow mode definitions to apply broadly across all local or partner LUs.

snmp

protocol-element §3.1.4

The appcSession group contains four tables: appcActSessTable (active sessions with PCID and pacing counts), appcSessStatsTable (byte and RU send/receive counters, present only when stats collection is active), appcHistSessTable (abnormally terminated sessions with unbind type and sense data), and appcSessRtpTable (sessions transported by APPN High Performance Routing, with NCEID and TCID).

snmp

security-consideration §7

The MIB contains read-write objects (appcCntrlAdmin*, appcCnos*) that allow a management station to alter APPC operational parameters, issue CNOS commands, and start or stop statistics and tracing. Unauthorized access to these objects could disrupt APPC session management. Implementors should apply appropriate SNMP access control (e.g., SNMPv2 party-based or SNMPv3 VACM) to restrict write access.

snmp, security

state-machine §4

appcLuPairOperState models the state of a local/partner LU pair: 'inactive' (no active or pending session exists) and 'active' (an active or pending session exists between the LUs). A row in appcLuPairOperTable is created as soon as there is an active session; two entries are present when both LUs in a pair are local.

snmp

wire-format §4

SnaSenseData is a textual convention encoded as a DisplayString of SIZE(8). Eight '0' characters indicates no sense data identifying an SNA error condition is available; any other 8-character value represents an SNA sense data code.

snmp

wire-format §4

The appcLluAdminLocalAddress field is a single-byte OCTET STRING (SIZE 1). For dependent LUs the value ranges from 1 to 254; for independent LUs the value is always 0.

snmp