Definitions of Managed Objects for APPN/HPR in IP Networks
Extracted elements (19)
The hprIpCnTable applies a single TOS Precedence mapping to a connection network regardless of which port is used, because the HPR/IP architecture provides no mechanism for per-port variation within a single connection network.
TOS Precedence settings in this MIB are noted to have been redefined in RFC 2474 as the first three bits of the differentiated services code point (DSCP). The MIB retains the TOS Precedence terminology for historical consistency with HPR/IP architecture.
A MIB conforming to SMIv1 can be produced by translating this SMIv2 MIB, but objects using Counter64 must be omitted as they have no SMIv1 equivalent. Machine-readable SMIv2 information becomes textual descriptions in SMIv1.
Deleting an entry from hprIpLsTable (RowStatus destroy(6)) causes the link station to revert to the default TOS Precedence mapping inherited from its port. Similarly, deleting from hprIpCnTable reverts the connection network to per-port defaults.
If hprIpActiveLsLsName has the same value as appnLsName in the APPN MIB, or hprIpAppnPortName equals appnPortName, they refer to the same APPN link station or port respectively, providing cross-MIB linkage.
appnPortSpecific and appnLsSpecific objects should return a RowPointer to the ifEntry in the agent's ifTable for the physical interface associated with the local IP address for the port.
The hprIpMonitoringGroup and hprIpConfigurationGroup are both mandatory for APPN implementations supporting HPR over IP; the configuration group may be implemented as read-only objects.
When an HPR/IP port or link station is identified by appnPortDlcType, appnLsDlcType, or appnLsStatusDlcType (syntax IANAifType), the value 126 ('IP for APPN HPR in IP networks') SHALL be returned.
When hprIpAppnPortTOSPrecedence, hprIpLsTOSPrecedence, or hprIpCnTOSPrecedence is changed via a Set operation, the new TOS Precedence setting takes effect immediately rather than waiting for reinitialization of the port or APPN node.
AppnTOSPrecedence textual convention is a 3-character DisplayString representing the three TOS Precedence bits in the IP Type of Service field. Default mapping: Network→110, High→100, Medium→010, Low→001, LLC commands→110.
AppnTrafficType textual convention defines five APPN traffic types: low(1), medium(2), high(3), network(4), and llcAndFnRoutedNlp(5). The first four correspond to APPN transmission priorities; the fifth covers LLC commands and function-routed NLPs.
hprIpActiveLsTable is indexed by link station name (DisplayString, SIZE 1..10) and AppnTrafficType, and contains hprIpActiveLsUdpPackets (Counter32) counting outgoing UDP packets per APPN traffic type per active HPR/IP link station.
hprIpAppnPortTable is indexed by APPN port name and AppnTrafficType, and contains hprIpAppnPortTOSPrecedence (read-write) representing the default TOS Precedence mapping for all link stations on that port.
hprIpCnTable is indexed by VRN name (SnaControlPointName) and AppnTrafficType, containing hprIpCnTOSPrecedence (read-create) and hprIpCnRowStatus. Connection network entries override port-level TOS Precedence settings for all ports through which the node can reach the connection network.
hprIpLsTable is indexed by link station name and AppnTrafficType, containing hprIpLsTOSPrecedence (read-create) and hprIpLsRowStatus (RowStatus). Entries override the port-level TOS Precedence mapping for individual link stations.
The HPR-IP-MIB module defines two groups: hprIpMonitoringGroup (counts UDP packets per APPN traffic type per link station) and hprIpConfigurationGroup (maps APPN traffic types to IP TOS Precedence bits at port, link station, and connection network levels).
This MIB module registers hprIp under hprObjects 5, hprIpCompliance under hprCompliances 2, hprIpMonitoringGroup under hprGroups 5, and hprIpConfigurationGroup under hprGroups 6, extending the HPR MIB OID subtree.
Authentication of received SNMP requests and controlled access to management information SHOULD be employed in sensitive network environments. SNMPv3 USM (RFC 2274) and VACM (RFC 2275) provide authentication and access control respectively.
The five writable objects (hprIpPortTOSPrecedence, hprIpLsTOSPrecedence, hprIpLsRowStatus, hprIpCnTOSPrecedence, hprIpCnRowStatus) can affect network operations; improper TOS mappings may cause delays or disruptions, including timeouts on control sessions that could cause network outages. SNMP access to these objects should be restricted.