rfc-2232

Definitions of Managed Objects for DLUR using SMIv2

B. Clouston (Editor), B. Moore (Editor)
date1997-11 streamIETF areartg wgsnanau statusPROPOSED STANDARD pages21 canonicalhttps://www.rfc-editor.org/rfc/rfc2232 doi10.17487/RFC2232
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 monitoring and controlling network devices with DLUR (Dependent LU Requester) capabilities. This memo identifies managed objects for the DLUR protocol. [STANDARDS-TRACK]

Extracted elements (20)

design-rationale §5

CPSVRMGR pipe status is presented as a single combined value rather than exposing two separate contention-winner and contention-loser session states, because the meaningful operational state for management purposes is the aggregate pipe status. A matrix in the MIB description documents how individual session states map to the combined value.

snmp

design-rationale §4

DLUR/S was introduced because the base APPN architecture only transported data between independent LUs, yet customers had large investments in dependent LU type applications. DLUR encapsulates SSCP-PU and SSCP-LU session flows on LU 6.2 sessions (CPSVRMGR pipes) between DLUS and DLUR nodes, enabling dependent LU support in APPN networks without changing the base architecture.

snmp

design-rationale §4

The DLUR MIB deliberately omits management of DLUS nodes, DLUR configuration, changing control session state, displaying dependent LUs, and traps. Traps for DLUR resources are handled via the existing APPN MIB alertTrap mechanism using a VariablePointer into the DLUR MIB.

snmp

interoperability-note §4.1

dlurNodeCpName has the same value as appnNodeCpName in the APPN MIB when both refer to the same APPN node. Similarly, dlurPuLsName equals appnLsName in the APPN MIB when identifying the same link station, and dlurPuDefBackupDlusPuName equals dlurPuName when identifying the same PU.

snmp

normative-requirement §5 REQUIRED

The dlurCompliance MODULE-COMPLIANCE statement declares dlurConfGroup as unconditionally mandatory for all SNMPv2 entities implementing the DLUR MIB. All 18 objects in dlurConfGroup must be supported.

snmp

protocol-element §5

dlurAnsSupport (dlurNodeCapabilities 3) indicates Automatic Network Shutdown capability: 'continueOrStop(1)' means DLUR supports either ANS value as specified by the DLUS per ACTPU; 'stopOnly(2)' means only ANS=stop is supported. ANS=continue keeps LU-LU sessions active if SSCP control sessions are interrupted.

snmp

protocol-element §5

dlurDefaultDefBackupDlusTable (dlurNodeInfo 2) is an ordered list of default backup DLUSs for all PUs served by this DLUR, indexed by dlurDefaultDefBackupDlusIndex (Unsigned32 1..4294967295), with entries ordered from most to least preferred backup DLUS.

snmp

protocol-element §5

dlurDlusTable (dlurDlusInfo 1) contains information about active CPSVRMGR pipes to DLUSs, indexed by dlurDlusName (SnaControlPointName). Each entry records only the DLUS name and the combined contention-winner/contention-loser session status.

snmp

protocol-element §5

dlurMultiSubnetSupport (dlurNodeCapabilities 4) is a TruthValue indicating whether the DLUR implementation can support CPSVRMGR sessions that cross NetId boundaries. Read-only.

snmp

protocol-element §5

dlurNetworkNameForwardingSupport (dlurNodeCapabilities 6) indicates whether the DLUR forwards Network Name control vectors on ACTPUs and ACTLUs to DLUR-served PUs and their LUs. This corresponds to byte 9, bit 3 of CV51.

snmp

protocol-element §5

dlurNodeCpName (dlurNodeCapabilities 1) is the administratively assigned SNA network name for the APPN node hosting DLUR; it has the same value as appnNodeCpName in the APPN MIB when referring to the same node. Syntax: SnaControlPointName, read-only.

snmp

protocol-element §5

dlurNondisDlusDlurSessDeactSup (dlurNodeCapabilities 7) indicates support for nondisruptive DLUR-DLUS session deactivation. When the DLUR receives an UNBIND for the CPSVRMGR pipe with sense data X'08A0 000B', it immediately attempts to activate a CPSVRMGR pipe with a different DLUS. Corresponds to byte 9, bit 4 of CV51.

snmp

protocol-element §5

dlurPuActiveDlusName (dlurPuEntry 8) is the SNA name of the currently active DLUS for a PU. A zero-length string indicates no active DLUS. When non-empty it follows the SnaControlPointName textual convention (DisplayString SIZE 0..17).

snmp

protocol-element §5

dlurPuDefBackupDlusTable (dlurPuInfo 2) provides per-PU ordered backup DLUS lists, indexed by dlurPuDefBackupDlusPuName and dlurPuDefBackupDlusIndex. PUs without entries in this table fall back to dlurDefaultDefBackupDlusTable for backup DLUS selection.

snmp

protocol-element §5

dlurPuTable (dlurPuInfo 1) contains one entry per PU supported via DLUR, indexed by dlurPuName (DisplayString SIZE 1..17). Each entry includes SSCP-supplied name, PU status, ANS support, location, link station name, DLUS session status, active DLUS name, and defined primary DLUS name.

snmp

protocol-element §5

dlurReleaseLevel (dlurNodeCapabilities 2) carries the DLUR release level as encoded in CV 51 of the DLUR/DLUS Capabilities. The one-byte value is represented as a two-character displayable hex string (e.g., X'01' becomes '01'). Syntax: DisplayString SIZE(2), read-only.

snmp

protocol-element §5

The APPN-DLUR-MIB module is registered at snanauMIB 5 (mib-2 34 subtree). It defines objects for monitoring APPN nodes with Dependent LU Requester (DLUR) capabilities, organized into three groups: dlurNodeInfo, dlurPuInfo, and dlurDlusInfo.

snmp, yang

security-consideration §8

The DLUR MIB contains no read-write objects and no read-only objects that expose passwords or user data. Enterprises treating network topology and performance data as sensitive corporate assets may wish to restrict SNMP access to MIB objects via SNMP security mechanisms.

security, snmp

state-machine §5

dlurPuDlusSessnStatus and dlurDlusSessnStatus both use a four-state model for CPSVRMGR pipe status: reset(1), pendingActive(2), active(3), pendingInactive(4). The combined status is derived from a matrix of contention-winner and contention-loser session states; active(3) requires both sessions active, and pendingActive(2) takes precedence over pendingInactive(4).

snmp

state-machine §5

dlurPuStatus defines nine states for a DLUR-supported PU: reset(1), pendReqActpuRsp(2), pendActpu(3), pendActpuRsp(4), active(5), pendLinkact(6), pendDactpuRsp(7), pendInop(8), pendInopActpu(9). The pendInop state captures the CPSVRMGR pipe becoming inoperative while awaiting a PU ACTPU response; pendInopActpu captures receipt of a new ACTPU on a newly active pipe before the prior ACTPU response arrives.

snmp