Definitions of Managed Objects for APPN
obsoletes
- rfc-2155 — Definitions of Managed Objects for APPN using SMIv2
Extracted elements (29)
Branch network nodes are treated as a distinct third node type in this MIB (parallel to NN and EN) despite being technically network nodes in the base APPN architecture, because the distinction increases clarity for management applications—BrNNs omit appnNnTopo objects but implement appnSessIntermediate and two appnEnUniqueCaps objects.
DLC addresses are exposed as ASCII display strings (DisplayableDlcAddress, 0-64 chars) rather than raw binary because the encoding is DLC-type-specific; the authoritative binary address is available in the appropriate DLC-specific MIB referenced via RowPointer.
The appnNnTopology tables are indexed first by the FRSN (flow-reduction sequence number) so that a management station can poll for incremental topology updates rather than fetching the entire database each time, since agents update the FRSN only on new or changed resources.
RFC 2455 obsoletes RFC 2155, adding multi-link TG objects (appnLsMltgMember, appnNnTgFRMltgLinkType, appnLocalTgMltgLinkType), branch network node objects (appnNodeBrNn, appnNnNodeFRBranchAwareness, appnNnTgFRBranchTg, appnLocalTgBranchLinkType), appnNodeLsCounterType, and deprecating appnNodeMibVersion.
This MIB is specified in SMIv2 and can be translated to SMIv1 with semantic equivalence, except that Counter64 objects must be omitted (no SMIv1 equivalent exists) and some machine-readable SMIv2 information is degraded to textual descriptions.
A branch network node SHALL return endNode(2) as the value of appnNodeType. A management application distinguishes a BrNN from a true end node by retrieving the appnNodeBrNn object.
Agents MUST NOT include nonsignificant trailing blanks in SNA name values returned by MIB objects. The sole exception is the all-blank mode name, which is returned as exactly 8 blank characters.
Management stations SHOULD accept '#', '@', and '$' in SNA NetIds and CpNames for backward compatibility with earlier SNA versions, even though their use has been retired from the current APPN architecture.
When an SNA name is used as a table index, agents treat trailing blanks as significant: a GetNext request for index '#INTER ' does not match the row indexed '#INTER'. This allows management stations to position GetNext traversal within a table.
appnDirTable lists LUs known to the node along with the owning node's CP name and its serving NN. appnDirPerf objects expose directory database statistics and search performance counters.
appnLsStatusTable records exceptional conditions during connection activation, XID exchange, and termination; no entries are created for normal processing. It is an implementation option when entries are removed from this table.
appnLsTable provides comprehensive link station information: operational state, HPR support level, forward/reverse ANR labels (0-8 bytes each), CP-CP/Route/BF NCE IDs, echo-probe delay measurements (current, min, max in ms with timestamp), XID counters, and appnLsMltgMember (multi-link TG membership).
appnNodeHprSupport reports the node's HPR capability level: noHprSupport(1), hprBaseOnly(2/option-set 1400), rtpTower(3/option-set 1401), or controlFlowsOverRtpTower(4/option-set 1402); corresponds to cv4580 byte 9 bits 3-4.
appnNodeLsCounterType indicates which ANR traffic the node counts in link station byte/frame statistics: other(1), noAnr(2), anrForLocalNces(3) (only locally terminating RTP connections), or allAnr(4). ISR traffic is always counted regardless of this setting.
appnNodeType identifies the node as networkNode(1), endNode(2), or t21len(4). A branch network node (BrNN) reports endNode(2) here and must be further distinguished via the appnNodeBrNn boolean object.
appnPortTable describes APPN port configuration and status, indexed by port name (1-10 chars), including DLC type (IANAifType), port type (leased/switched/sharedAccessFacilities), BTU size (99-32767 bytes), I-frame window, XID counters, and a RowPointer to the DLC-specific MIB.
appnSessIntermediate group includes appnIsInGlobal (control of RSCV and counter collection), appnIsInTable (active intermediate sessions), and appnIsRtpTable (intermediate sessions carried on HPR RTP connections).
One APPN notification is defined corresponding to SNA/MS Alert conditions; it carries an Alert ID and, where possible, the affected resource OID. Implementation of this trap is optional.
The APPN-MIB module (appnMIB) is rooted at { snanauMIB 4 } (mib-2 34) and organizes managed objects into six groups: appnNode, appnNn, appnLocalTopology, appnDir, appnCos, and appnSessIntermediate, plus one optional SNA/MS Alert trap.
The appnCos group contains four tables: appnCosModeTable (mode-to-COS mapping), appnCosNameTable (transmission priority per COS), appnCosNodeRowTable (per-COS node routing weights), and appnCosTGRowTable (per-COS TG routing weights).
The appnNnTopology tables (appnNn group) represent the APPN network topology database—NNs, VRNs, and TGs between them—indexed first by the flow-reduction sequence number (FRSN) so a management station can retrieve only incremental updates.
Section 5 addresses security for the APPN MIB. The MIB includes read-write objects—appnPortCommand and appnLsCommand (activate, deactivate, recycle) and appnNodeNnSafeStoreFreq—that can disrupt network operations; unauthorized SET access to these objects must be controlled via SNMP access control mechanisms.
appnLsOperState defines 11 link station states: inactive(1); five pending-active states (sentConnectOut, pendXidExch, sendActAs, sendSetMode, otherPendingActive); active(7); and four pending-inactive states (sentDeactAsOrd, sentDiscOrd, sentDiscImmed, otherPendingInact). Transitions are triggered by appnLsCommand.
appnPortOperState defines four port states: inactive(1), pendactive(2), active(3), and pendinact(4). Transitions are driven by writing activate(2), deactivate(1), or recycle(3) to the appnPortCommand read-write object.
AppnTgDelay is a 1-byte OCTET STRING encoding propagation delay in microseconds using the same floating-point scheme as cv47, with named values including negligible(384/X'4C'), terrestrial(9216/X'71'), packet(147456/X'91'), and maximum(2013265920/X'FF').
AppnTgEffectiveCapacity is a 1-byte floating-point OCTET STRING encoded identically to byte 7 of SNA cv47, representing TG bandwidth in units of 300 bits per second.
AppnTgSecurity is an INTEGER representing TG physical security level with seven values: nonsecure(1/X'01'), publicSwitchedNetwork(32/X'20'), undergroundCable(64/X'40'), secureConduit(96/X'60'), guardedConduit(128/X'80'), encrypted(160/X'A0'), and guardedRadiation(192/X'C0').
SnaControlPointName is an OCTET STRING (SIZE 3..17) encoding a fully-qualified SNA CP name as NetId.CpName, where each part is 1-8 uppercase alphanumeric ASCII characters starting with a letter; trailing blanks are not allowed.
SnaNodeIdentification is an OCTET STRING (SIZE 8) encoding the SNA Node ID as 8 ASCII hexadecimal characters: a 3-digit block number (product identifier) followed by a 5-digit administratively-assigned ID, matching bytes 2-5 of the XID.