HPR-MIB: View SNMP OID List / Download MIB

This is the MIB module for objects used to manage network devices with HPR capabilities.

Administratively assigned network name for the APPN node where this HPR implementation resides. If this object has the same value as the appnNodeCpName object in the APPN MIB, then the two objects are referring to the same APPN node.

This object indicates an implementation's level of support for an operator-requested path switch. notSupported(1) - the agent does not support operator-requested path switches switchTriggerSupported(2) - the agent supports a 'switch path now' command from an operator, but not a command to switch to a specified path switchToPathSupported(3) - the agent supports both a 'switch path now' command and a command to switch to a specified path. Note that the latter command is not available via this MIB; a system that supports it must do so via other means, such as a local operator interface. Enumeration: 'switchToPathSupported': 3, 'notSupported': 1, 'switchTriggerSupported': 2.

The count of ANR labels assigned by this node since it was last re-initialized. A Management Station can detect discontinuities in this counter by monitoring the appnNodeCounterDisconTime object in the APPN MIB.

This object is used for a network management station to turn on/off the counting of ANR packets in the hprAnrRoutingTable. The initial value of this object is an implementation choice. notActive(1) - the counter hprAnrPacketsReceived returns no meaningful value active(2) - the counter hprAnrPacketsReceived is being incremented and is returning meaningful values Enumeration: 'notActive': 1, 'active': 2.

The time when the hprAnrCounterState object last changed its value. The initial value returned by this object is the time at which the APPN node instrumented with this MIB was last brought up.

The ANR Routing table provides a means of correlating an incoming ANR label (i.e., one assigned by this node) with the TG over which a packet containing the label will be forwarded. When the ANR label identifies a local NCE, the hprAnrOutTgDest and hprAnrOutTgNum objects have no meaning. The table also contains an object to count the number of packets received with a given ANR label.

The ANR label is used to index this table.

The first ANR label in an incoming packet.

An object indicating whether an ANR label assigned by this node identifies a local NCE or a TG on which outgoing packets are forwarded. nce(1) - the ANR label identifies a local NCE. In this case the hprAnrOutTgDest and hprAnrOutTgNum objects have no meaning. tg(2) - the ANR label identifies a TG. Enumeration: 'tg': 2, 'nce': 1.

Destination node for the TG over which packets with this ANR label are forwarded. This is the fully qualified name of an APPN network node or end node, formatted according to the SnaControlPointName textual convention. If the ANR label identifies a local NCE, then this object returns a zero-length string. This object corresponds to the appnLocalTgDest object in the APPN MIB.

Number of the TG over which packets with this ANR label are forwarded. If the ANR label identifies a local NCE, then this object returns the value 0, since 0 is not a valid TG number for a TG that supports HPR. This object corresponds to the appnLocalTgNum object in the APPN MIB.

The count of packets received with this ANR label as their first label. A Management Station can detect discontinuities in this counter by monitoring the hprAnrCounterDisconTime object in the same row.

The value of the sysUpTime object when the hprAnrPacketsReceived counter for this ANR label last experienced a discontinuity. This will be the more recent of two times: the time at which the ANR label was associated with either an outgoing TG or a local NCE, or the time at which the ANR counters were last turned on or off.

The Network Connection Endpoint (NCE) table.

The NCE ID is used to index this table.

The Network Connection Endpoint (NCE) ID. NCEs identify Control Points (Cp), Logical Units (Lu), HPR Boundary Functions (Bf) and Route Setup (Rs) Functions. A value for this object can be retrieved from any of the following objects in the APPN MIB: - appnLsCpCpNceId - appnLsRouteNceId - appnLsBfNceId - appnIsInRtpNceId - appnIsRtpNceId In each case this value identifies a row in this table containing information related to that in the APPN MIB.

A bit string identifying the function types provided by this Network Connection Endpoint (NCE).

A bit string identifying the function types for which this Network Connection Endpoint (NCE) is the default NCE. While default NCEs are not explicitly defined in the architecture, some implementations provide them; for such implementations, it is useful to make this information available to a Management Station.

The NCE instance identifier (NCEII) identifying the current instance of this NCE. An NCEII is used to denote different instances (IPLs) of an NCE component. Each time an NCE is activated (IPL'd), it acquires a different, unique NCEII.

The count of RTP connection setups in which this node has participated, as either sender or receiver, since it was last re-initialized. Retries of a setup attempt do not cause the counter to be incremented. A Management Station can detect discontinuities in this counter by monitoring the appnNodeCounterDisconTime object in the APPN MIB.

This object allows a network management station to turn the counters in the hprRtpTable on and off. The initial value of this object is an implementation choice. notActive(1) - the counters in the hprRtpTable are returning no meaningful values active(2) - the counters in the hprRtpTable are being incremented and are returning meaningful values Enumeration: 'notActive': 1, 'active': 2.

The time when the value of the hprRtpGlobeCtrState object last changed. The initial value returned by this object is the time at which the APPN node instrumented with this MIB was last brought up.

The RTP Connection table

The local NCE ID and local TCID are used to index this table.

The local Network Connection Endpoint (NCE) ID of this RTP connection. NCEs identify CPs, LUs, Boundary Functions (BFs), and Route Setup (RS) components. A value for this object can be retrieved from any of the following objects in the APPN MIB: - appnLsCpCpNceId - appnLsRouteNceId - appnLsBfNceId - appnIsInRtpNceId - appnIsRtpNceId In each case this value identifies a row in this table containing information related to that in the APPN MIB.

The local TCID of this RTP connection. A value for this object can be retrieved from either the appnIsInRtpTcid object or the appnIsRtpTcid object the APPN MIB; in each case this value identifies a row in this table containing information related to that in the APPN MIB.

Administratively assigned network name for the remote node of this RTP connection.

The remote Network Connection Endpoint (NCE) of this RTP connection. NCEs identify CPs, LUs, Boundary Functions (BFs), and Route Setup (RS) components.

The remote TCID of this RTP connection.

Object by which a Management Station can trigger an operator- requested path switch, by setting the value to switchPathNow(2). Setting this object to switchPathNow(2) triggers a path switch even if its previous value was already switchPathNow(2). The value ready(1) is returned on GET operations until a SET has been processed; after that the value received on the most recent SET is returned. This MIB module provides no support for an operator-requested switch to a specified path. Enumeration: 'ready': 1, 'switchPathNow': 2.

The forward Route Selection Control Vector for this RTP connection. The format of this vector is described in SNA Formats. The value returned in this object during a path switch is implementation-dependent: it may be the old path, the new path, a zero-length string, or some other valid RSCV string.

The topic for this RTP connection. This is used to indicate the Class of Service.

The state of the RTP connection, from the perspective of the local RTP protocol machine: rtpListening - connection open; waiting for other end to call in rtpCalling - connection opened, attempting to call out, have not yet received any data from other end rtpConnected - connection is active; responded to a call-in or received other end's TCID from a call-out attempt rtpPathSwitching - the path switch timer is running; attempting to find a new path for this connection. rtpDisconnecting - no sessions are using this connection; in process of bringing it down other - the connection is not in any of the states listed above. Enumeration: 'rtpConnected': 3, 'rtpListening': 1, 'rtpPathSwitching': 4, 'other': 99, 'rtpCalling': 2, 'rtpDisconnecting': 5.

The length of time the RTP connection has been up, measured in 1/100ths of a second.

The value of the liveness (ALIVE) timer of this RTP connection, in units of 1/100th of a second. When this timer expires and no packet has arrived from the partner since it was last set, packets with Status Request indicators will be sent to see if the RTP connection is still alive.

The value of the RTP SHORT-REQ timer, in units of 1/100 of a second. This timer represents the maximum time that a sender waits for a reply from a receiver.

The length of time that RTP should attempt a path switch for a connection, in units of 1/100th of a second.

The count of liveness timeouts for this RTP connection.

The count of short request timeouts for this RTP connection.

The high-water mark for this RTP connection's send rate, in units of bytes per second. This is the high-water mark for the entire life of the connection, not just the high-water mark for the connection's current path. For more details on this and other parameters related to HPR, see the High Performance Routing Architecture Reference.

The low-water mark for this RTP connection's send rate, in units of bytes per second. This is the low-water mark for the entire life of the connection, not just the low-water mark for the connection's current path. For more details on this and other parameters related to HPR, see the High Performance Routing Architecture Reference.

The current send rate for this RTP connection, in units of bytes per second. For more details on this and other parameters related to HPR, see the High Performance Routing Architecture Reference.

The smoothed round trip delay for this RTP connection, in units of 1/1000th of a second (ms). For more details on this and other parameters related to HPR, see the High Performance Routing Architecture Reference.

The count of packets successfully sent on this RTP connection.

The count of packets received on this RTP connection. The counter is incremented only once if duplicate copies of a packet are received.

The count of bytes sent on this RTP connection. Both RTP Transport Header (THDR) bytes and data bytes are included in this count.

The count of bytes received on this RTP connection. Both RTP Transport Header (THDR) bytes and data bytes are included in this count.

The count of packets retransmitted on this RTP connection.

The count of packets received on this RTP connection and then discarded. A packet may be discarded because it is determined to be a duplicate, or for other reasons.

The count of gaps detected on this RTP connection.

The count of Rate Requests sent on this RTP connection.

The count of successful path switch attempts for this RTP connection due to errors.

The count of unsuccessful path switches for this RTP connection due to errors.

The count of successful path switches for this RTP connection due to operator requests.

The count of unsuccessful path switches for this RTP connection due to operator requests. This counter is not incremented by an implementation that does not support operator-requested path switches, even if a Management Station requests such a path switch by setting the hprRtpPathSwitchTrigger object.

The value of the sysUpTime object when the counters for this RTP connection last experienced a discontinuity. This will be the more recent of two times: the time at which the connection was established or the time at which the HPR counters were last turned on or off.

RTP Connection Status Table: This table contains historical information on RTP connections. An entry is created in this table when a path switch is completed, either successfully or unsuccessfully.

This table is indexed by local NCE ID, local TCID, and an integer hprRtpStatusIndex. Thus the primary grouping of table rows is by RTP connection, with the multiple entries for a given RTP connection ordered by time.

The local Network Connection Endpoint (NCE) of this RTP connection. NCEs identify CPs, LUs, Boundary Functions (BFs), and Route Setup (RS) components.

The local TCID of this RTP connection.

Table index. This value begins at one and is incremented when a new entry is added to the table. It is an implementation choice whether to run a single counter for all entries in the table, or to run a separate counter for the entries for each RTP connection. In the unlikely event of a wrap, it is assumed that Management Stations will have the ability to order table entries correctly.

The time when the path switch began.

The time when the path switch was ended, either successfully or unsuccessfully.

Administratively assigned network name for the remote node of this RTP connection.

The remote Network Connection Endpoint (NCE) of this RTP connection. NCEs identify CPs, LUs, Boundary Functions (BFs), and Route Setup (RS) components.

The remote TCID of this RTP connection.

The new Route Selection Control Vector for this RTP connection. A zero-length string indicates that no value is available, perhaps because the implementation does not save RSCVs.

The old Route Selection Control Vector for this RTP connection. A zero-length string indicates that no value is available, perhaps because the implementation does not save RSCVs.

The reason for the path switch: other(1) - Reason other than those listed below, rtpConnFail(2) - RTP connection failure detected, locLinkFail(3) - Local link failure, remLinkFail(4) - Remote link failure (learned from TDUs), operRequest(5) - Operator requested path switch. Enumeration: 'locLinkFail': 3, 'remLinkFail': 4, 'other': 1, 'operRequest': 5, 'rtpConnFail': 2.

The result of the last completed path switch attempt. If the path switch is aborted in the middle of a path switch attempt because the path switch timer expires, the result of the previous path switch attempt is reported. The values are defined as follows: successful(1) - The final path switch attempt was successful. initiatorMoving(2) - The final path switch attempt failed because the initiator is mobile, and there was no active link out of this node. directorySearchFailed(3) - The final path switch attempt failed because a directory search for the destination node's CP name failed. rscvCalculationFailed(4) - The final path switch attempt failed because an RSCV to the node containing the remote RTP endpoint could not be calculated. negativeRouteSetupReply(5) - The final path switch attempt failed because route setup failed for the new path. backoutRouteSetupReply(6) - The final path switch attempt failed because the remote RTP endpoint refused to continue the RTP connection. timeoutDuringFirstAttempt(7) - The path switch timer expired during the first path switch attempt. otherUnsuccessful(8) - The final path switch attempt failed for a reason other than those listed above. Enumeration: 'successful': 1, 'timeoutDuringFirstAttempt': 7, 'directorySearchFailed': 3, 'negativeRouteSetupReply': 5, 'backoutRouteSetupReply': 6, 'otherUnsuccessful': 8, 'initiatorMoving': 2, 'rscvCalculationFailed': 4.

The compliance statement for the SNMPv2 entities that implement the HPR MIB.

A collection of objects providing the instrumentation of HPR general information and capabilities.

A collection of objects providing instrumentation for the node's ANR routing.

A collection of objects providing information on the users of the HPR transport known to the node.

A collection of objects providing the instrumentation for RTP connection end points.