As per Relevance of the word definition, we have this rfc below:
Network Working Group B. Clouston,
Request for Comments: 2238 Cisco
Category: Standards Track B. Moore,
IBM
November 1997
Definitions of Managed
for HPR using SMIv
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1997). All Rights Reserved
Table of
1. Status of this Memo ..................................... 1
2. Introduction ............................................ 1
3. The SNMP Network Management Framework ................... 2
4. Overview ................................................ 2
4.1 HPR MIB structure ...................................... 3
5. Definitions ............................................. 5
6. Acknowledgments ........................................ 33
7. References ............................................. 33
8. Security Considerations ................................ 33
9. Authors' Addresses ..................................... 34
10. Full Copyright Statement ................................ 35
2.
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
network devices with HPR (High Performance Routing) capabilities
This memo identifies managed objects for the HPR protocol
Clouston & Moore Standards Track [Page 1]
RFC 2238 Definitions of Managed Objects for HPR November 1997
3. The SNMP Network Management
The SNMP Network Management Framework consists of several components
For the purpose of this specification, the applicable components
the Framework are the SMI and related documents [1, 2, 3],
define the mechanisms used for describing and naming objects for
purpose of management
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
4.
This document identifies objects for monitoring the configuration
active characteristics of devices with HPR capabilities. HPR is
enhancement to the Advanced Peer-to-Peer Network (APPN)
that provides fast data routing and improved session reliability
APPN is one of the protocols that can use the HPR
mechanism. See the SNANAU APPN MIB [4] for management of APPN
APPN use of the HPR transport
The HPR terms and overall architecture [5] are available
http://www.networking.ibm.com/app/aiwdoc/aiwsrc.htm
Automatic Network Routing (ANR) is a fast low-level
technique. Each node assigns a unique (within that node) ANR
for each out-bound link as it is activated. The label size
defined by the ANR node, and nodes only need to know how to
their own labels. The ANR string is a group of ANR labels encoded
a header in front of the message being sent. At each hop the
strips off its own ANR label and forwards the message onto the
with that label. The last label in the string is the
Connection Endpoint (NCE), which identifies the component within
destination node that is to receive the message
Rapid Transport Protocol (RTP) is an end-to-end full duplex
connection (pipe). It provides for high-speed transport of
using ANR. RTP is connection-oriented, and delivers data in
order reliably. Error recovery is done efficiently with
retransmission of data. An RTP path can be switched
disrupting the sessions using it. An RTP path switch may be
automatically if a link in the path fails and another RTP path
available, or on demand to attempt to restore the optimal path
RTP performs flow/congestion control with the Adaptive Rate-
(ARB) algorithm, described in [5]. ARB is done only at the
of the RTP pipe, so intermediate hops are not involved
Clouston & Moore Standards Track [Page 2]
RFC 2238 Definitions of Managed Objects for HPR November 1997
ARB regulates the flow of data over an RTP connection by
changing the sender's rate based on feedback on the receiver's rate
It is designed to prevent congestion rather than react to it
In this document, we describe HPR managed objects
Highlights of the management functions supported by the HPR
module include the following
o Identifying network connection endpoints (NCEs).
o Identifying how incoming packets are routed based on ANR labels
o Monitoring the RTP connections between nodes
o Ability to trigger an RTP path switch. The MIB only supports
path switch with no specified path. Some implementations
have a product-specific option to specify a new path.
hprOperatorPathSwitchSupport object identifies this support
o Historical information about RTP path switch attempts
This MIB module does not support
o Configuration of HPR nodes
o Protocol-specific uses of HPR (such as APPN).
o Traps. The APPN MIB contains a trap for Alert conditions
may affect HPR resources. The value for the
object contained in the alertTrap is determined by
implementation. It may contain a VariablePointer from the
MIB. The APPN/HPR Alerts are defined in [6].
4.1. HPR MIB
Although HPR is an extension to APPN, the HPR MIB relies very
upon the APPN MIB. The appnNodeCounterDisconTime object in the
MIB is used to detect discontinuities in HPR MIB counters.
hprNodeCpName object in this MIB has the same value as
appnNodeCpName object in the APPN MIB
The HPR MIB module contains the following collections of objects
o hprGlobal - general HPR objects
o hprAnrRouting - objects related to the ANR routing table
Clouston & Moore Standards Track [Page 3]
RFC 2238 Definitions of Managed Objects for HPR November 1997
o hprTransportUser - objects related to users of the
transport
o hprRtp - objects related to the HPR Transport Tower
These are described below in more detail
4.1.1. hprGlobal
The hprGlobal group consists of general objects such as the APPN
(control point) name of the HPR node and the level of support
operator-requested path switches
4.1.2. hprAnrRouting
The hprAnrRouting group consists objects to monitor and control
counting of ANR packets received and the following table
The hprAnrRoutingTable correlates incoming ANR labels to the
transmission group (TG) or local NCE to which incoming packet will
forwarded. An entry defines the label type as identifying a
NCE or a TG, identifies the NCE or TG, and counts the number
packets received with the entry's ANR label
4.1.3. hprTransportUser
The hprTransportUser group consists of the following table
The hprNceTable identifies network connection endpoints and
function types. The function type can be any combination of a CP
logical unit (LU), boundary function, and route setup
4.1.4. hprRtp
The hprRtp group consists of the following objects and tables
1)
These objects contain information about the number of RTP
setups, and control of RTP counters
2)
This table contains one entry for each RTP connection.
information includes local and remote NCE IDs and TCIDs (
connection identifiers), timers, send rates, and statistics. A
switch can be triggered by the hprRptPathSwitchTrigger object if
agent node supports it; however, a new path cannot be specified
Clouston & Moore Standards Track [Page 4]
RFC 2238 Definitions of Managed Objects for HPR November 1997
3)
This table contains statistics and historical information for
path switches attempts, including old and new ANR strings and
Selection Control Vectors (RSCVs), why the path switch was initiated
and the result (successful or reason for failure).
5.
HPR-MIB DEFINITIONS ::=
DisplayString, DateAndTime, TimeStamp, TEXTUAL-
FROM SNMPv2-
Counter32, Gauge32, Unsigned32, TimeTicks
OBJECT-TYPE, MODULE-
FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-
FROM SNMPv2-
FROM SNA-NAU-
FROM APPN-MIB
hprMIB MODULE-
LAST-UPDATED "970514000000Z
ORGANIZATION "AIW APPN / HPR MIB SIG
CONTACT-
"
Bob
Cisco
7025 Kit Creek
P.O. Box 14987
Research Triangle Park, NC 27709,
Tel: 1 919 472 2333
E-mail: clouston@cisco.
Bob
IBM
800 Park Offices
RHJA/664
P.O. Box 12195
Clouston & Moore Standards Track [Page 5]
RFC 2238 Definitions of Managed Objects for HPR November 1997
Research Triangle Park, NC 27709,
Tel: 1 919 254 4436
E-mail: remoore@ralvm6.vnet.ibm.
"
"This is the MIB module for objects used
manage network devices with HPR capabilities."
::= { snanauMIB 6 }
-- snanauMIB ::= { mib-2 34 }
-- *********************************************************************
-- Textual
-- *********************************************************************
-- SnaControlPointName is imported from the APPN
HprNceTypes ::= TEXTUAL-
STATUS
"A bit string identifying the set of functions provided by
network connection endpoint (NCE). The following values
defined
bit 0: control
bit 1: logical
bit 2: boundary
bit 3: route
"
SYNTAX BITS { controlPoint(0),
logicalUnit(1),
boundaryFunction(2),
routeSetup(3) }
HprRtpCounter ::= TEXTUAL-
STATUS
"An object providing statistics for an RTP connection.
Management Station can detect discontinuities in this
by monitoring the correspondingly
hprRtpCounterDisconTime object."
SYNTAX Counter32
-- *********************************************************************
hprObjects OBJECT IDENTIFIER ::= { hprMIB 1 }
-- *********************************************************************
-- *********************************************************************
Clouston & Moore Standards Track [Page 6]
RFC 2238 Definitions of Managed Objects for HPR November 1997
hprGlobal OBJECT IDENTIFIER ::= { hprObjects 1 }
-- *********************************************************************
-- The hprGlobal group applies to both intermediate and end nodes
-- *********************************************************************
hprNodeCpName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Administratively assigned network name for the APPN
where this HPR implementation resides. If this object
the same value as the appnNodeCpName object in the APPN MIB
then the two objects are referring to the same APPN node."
::= { hprGlobal 1 }
hprOperatorPathSwitchSupport OBJECT-
SYNTAX INTEGER {
notSupported(1),
switchTriggerSupported(2),
switchToPathSupported(3)
}
MAX-ACCESS read-
STATUS
"This object indicates an implementation's level of
for an operator-requested path switch
notSupported(1) - the agent does not
operator-requested path
switchTriggerSupported(2) - the agent supports a '
path now' command from
operator, but not a command
switch to a specified
switchToPathSupported(3) - the agent supports both
'switch path now' command and
command to switch to a
path. Note that the
command is not available
this MIB; a system that
it must do so via other means
such as a local
interface."
::= { hprGlobal 2 }
-- *********************************************************************
Clouston & Moore Standards Track [Page 7]
RFC 2238 Definitions of Managed Objects for HPR November 1997
hprAnrRouting OBJECT IDENTIFIER ::= { hprObjects 2 }
-- *********************************************************************
hprAnrsAssigned OBJECT-
SYNTAX Counter32
UNITS "ANR labels
MAX-ACCESS read-
STATUS
"The count of ANR labels assigned by this node since it
last re-initialized. A Management Station can
discontinuities in this counter by monitoring
appnNodeCounterDisconTime object in the APPN MIB."
::= { hprAnrRouting 1 }
hprAnrCounterState OBJECT-
SYNTAX INTEGER {
notActive(1),
active(2)
}
MAX-ACCESS read-
STATUS
"This object is used for a network management station to
on/off the counting of ANR packets in the hprAnrRoutingTable
The initial value of this object is an implementation choice
notActive(1) - the counter
returns no meaningful
active(2) - the counter hprAnrPacketsReceived
being incremented and is
meaningful values
::= { hprAnrRouting 2 }
hprAnrCounterStateTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The time when the hprAnrCounterState object last changed
value. The initial value returned by this object is the
at which the APPN node instrumented with this MIB was
brought up."
::= { hprAnrRouting 3 }
Clouston & Moore Standards Track [Page 8]
RFC 2238 Definitions of Managed Objects for HPR November 1997
hprAnrRoutingTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"The ANR Routing table provides a means of correlating
incoming ANR label (i.e., one assigned by this node) with
TG over which a packet containing the label will be forwarded
When the ANR label identifies a local NCE, the
and hprAnrOutTgNum objects have no meaning. The table
contains an object to count the number of packets
with a given ANR label."
::= { hprAnrRouting 4 }
hprAnrRoutingEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The ANR label is used to index this table."
INDEX { hprAnrLabel }
::= { hprAnrRoutingTable 1 }
HprAnrRoutingEntry ::= SEQUENCE {
hprAnrLabel OCTET STRING
hprAnrType INTEGER
hprAnrOutTgDest DisplayString
hprAnrOutTgNum INTEGER
hprAnrPacketsReceived Counter32,
hprAnrCounterDisconTime
}
hprAnrLabel OBJECT-
SYNTAX OCTET STRING (SIZE (1..8))
MAX-ACCESS not-
STATUS
"The first ANR label in an incoming packet."
::= { hprAnrRoutingEntry 1 }
hprAnrType OBJECT-
SYNTAX INTEGER {
nce(1),
tg(2)
Clouston & Moore Standards Track [Page 9]
RFC 2238 Definitions of Managed Objects for HPR November 1997
}
MAX-ACCESS read-
STATUS
"An object indicating whether an ANR label assigned by
node identifies a local NCE or a TG on which outgoing
are forwarded
nce(1) - the ANR label identifies a local NCE. In
case the hprAnrOutTgDest and
objects have no meaning
tg(2) - the ANR label identifies a TG."
::= { hprAnrRoutingEntry 2 }
hprAnrOutTgDest OBJECT-
SYNTAX DisplayString (SIZE (0 | 3..17))
MAX-ACCESS read-
STATUS
"Destination node for the TG over which packets with this
label are forwarded. This is the fully qualified name of
APPN network node or end node, formatted according to
SnaControlPointName textual convention. If the ANR
identifies a local NCE, then this object returns a zero-
string
This object corresponds to the appnLocalTgDest object in
APPN MIB."
::= { hprAnrRoutingEntry 3 }
hprAnrOutTgNum OBJECT-
SYNTAX INTEGER (0..255)
MAX-ACCESS read-
STATUS
"Number of the TG over which packets with this ANR label
forwarded. If the ANR label identifies a local NCE, then
object returns the value 0, since 0 is not a valid TG
for a TG that supports HPR
This object corresponds to the appnLocalTgNum object in
APPN MIB."
::= { hprAnrRoutingEntry 4 }
hprAnrPacketsReceived OBJECT-
Clouston & Moore Standards Track [Page 10]
RFC 2238 Definitions of Managed Objects for HPR November 1997
SYNTAX Counter32
UNITS "ANR packets
MAX-ACCESS read-
STATUS
"The count of packets received with this ANR label as
first label
A Management Station can detect discontinuities in
counter by monitoring the hprAnrCounterDisconTime object
the same row."
::= { hprAnrRoutingEntry 5 }
hprAnrCounterDisconTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of the sysUpTime object when
hprAnrPacketsReceived counter for this ANR label
experienced a discontinuity. This will be the more recent
two times: the time at which the ANR label was associated
either an outgoing TG or a local NCE, or the time at which
ANR counters were last turned on or off."
::= { hprAnrRoutingEntry 6 }
-- *********************************************************************
hprTransportUser OBJECT IDENTIFIER ::= { hprObjects 3 }
-- *********************************************************************
-- Transport Service User (TU) Table: (RTP Connection Users
--
-- There will be several users of the HPR transport and each HPR
-- shall maintain a table of these users
-- *********************************************************************
hprNceTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"The Network Connection Endpoint (NCE) table."
::= { hprTransportUser 1 }
hprNceEntry OBJECT-
SYNTAX
Clouston & Moore Standards Track [Page 11]
RFC 2238 Definitions of Managed Objects for HPR November 1997
MAX-ACCESS not-
STATUS
"The NCE ID is used to index this table."
INDEX { hprNceId }
::= { hprNceTable 1 }
HprNceEntry ::= SEQUENCE {
hprNceId OCTET STRING
hprNceType HprNceTypes
hprNceDefault HprNceTypes
hprNceInstanceId OCTET
}
hprNceId OBJECT-
SYNTAX OCTET STRING (SIZE (1..8))
MAX-ACCESS not-
STATUS
"The Network Connection Endpoint (NCE) ID. NCEs
Control Points (Cp), Logical Units (Lu), HPR
Functions (Bf) and Route Setup (Rs) Functions. A value
this object can be retrieved from any of the
objects in the APPN MIB
-
-
-
-
-
In each case this value identifies a row in this
containing information related to that in the APPN MIB."
::= { hprNceEntry 1 }
hprNceType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A bit string identifying the function types provided by
Network Connection Endpoint (NCE)."
::= { hprNceEntry 2 }
Clouston & Moore Standards Track [Page 12]
RFC 2238 Definitions of Managed Objects for HPR November 1997
hprNceDefault OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"A bit string identifying the function types for which
Network Connection Endpoint (NCE) is the default NCE.
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
Management Station."
::= { hprNceEntry 3 }
hprNceInstanceId OBJECT-
SYNTAX OCTET STRING (SIZE (4))
MAX-ACCESS read-
STATUS
"The NCE instance identifier (NCEII) identifying the
instance of this NCE. An NCEII is used to denote
instances (IPLs) of an NCE component. Each time an NCE
activated (IPL'd), it acquires a different, unique NCEII."
::= { hprNceEntry 4 }
-- *********************************************************************
hprRtp OBJECT IDENTIFIER ::= { hprObjects 4 }
-- *********************************************************************
-- *********************************************************************
--
-- The RTP group is implemented by all managed nodes supporting
-- HPR Transport Tower. The group contains several scalars (
-- objects) and a table
-- *********************************************************************
-- *********************************************************************
hprRtpGlobe OBJECT IDENTIFIER ::= { hprRtp 1}
-- *********************************************************************
hprRtpGlobeConnSetups OBJECT-
SYNTAX Counter32
UNITS "RTP connection setups
MAX-ACCESS read-
STATUS
"The count of RTP connection setups in which this node
participated, as either sender or receiver, since it was
re-initialized. Retries of a setup attempt do not cause
Clouston & Moore Standards Track [Page 13]
RFC 2238 Definitions of Managed Objects for HPR November 1997
counter to be incremented
A Management Station can detect discontinuities in
counter by monitoring the appnNodeCounterDisconTime
in the APPN MIB."
::= { hprRtpGlobe 1 }
hprRtpGlobeCtrState OBJECT-
SYNTAX INTEGER {
notActive(1),
active(2)
}
MAX-ACCESS read-
STATUS
"This object allows a network management station to turn
counters in the hprRtpTable on and off. The initial value
this object is an implementation choice
notActive(1) - the counters in the hprRtpTable
returning no meaningful
active(2) - the counters in the hprRtpTable
being incremented and are
meaningful values
::= { hprRtpGlobe 2 }
hprRtpGlobeCtrStateTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The time when the value of the hprRtpGlobeCtrState
last changed. The initial value returned by this object
the time at which the APPN node instrumented with this
was last brought up."
::= { hprRtpGlobe 3 }
-- *********************************************************************
-- The RTP Connection
-- There may be many RTP connections on a node supporting the
-- specified in the RTP option set. Each node implementing this
-- set shall maintain a table of these RTP connections
-- *********************************************************************
hprRtpTable OBJECT-
Clouston & Moore Standards Track [Page 14]
RFC 2238 Definitions of Managed Objects for HPR November 1997
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"The RTP Connection table
::= { hprRtp 2 }
hprRtpEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"The local NCE ID and local TCID are used to index
table."
{ hprRtpLocNceId
hprRtpLocTcid }
::= { hprRtpTable 1 }
HprRtpEntry ::= SEQUENCE {
hprRtpLocNceId OCTET STRING, -- local nce
hprRtpLocTcid OCTET STRING, -- local
hprRtpRemCpName SnaControlPointName,-- remote cp
hprRtpRemNceId OCTET STRING, -- remote nce
hprRtpRemTcid OCTET STRING, -- remote
hprRtpPathSwitchTrigger INTEGER, -- trigger (read-write
hprRtpRscv OCTET STRING, --
hprRtpTopic DisplayString, -- topic (cos
hprRtpState INTEGER, --
hprRtpUpTime TimeTicks, -- up
hprRtpLivenessTimer Unsigned32, -- liveness
hprRtpShortReqTimer Unsigned32, -- short request
hprRtpPathSwTimer Unsigned32, -- path switch
hprRtpLivenessTimeouts HprRtpCounter, -- liveness
hprRtpShortReqTimeouts HprRtpCounter, -- short req
hprRtpMaxSendRate Gauge32, -- maximum send
hprRtpMinSendRate Gauge32, -- minimum send
hprRtpCurSendRate Gauge32, -- current send
hprRtpSmRdTripDelay Gauge32, -- smooth rnd
hprRtpSendPackets HprRtpCounter, -- packets
Clouston & Moore Standards Track [Page 15]
RFC 2238 Definitions of Managed Objects for HPR November 1997
hprRtpRecvPackets HprRtpCounter, -- packets
hprRtpSendBytes HprRtpCounter, -- bytes
hprRtpRecvBytes HprRtpCounter, -- bytes
hprRtpRetrPackets HprRtpCounter, -- pkts re-
hprRtpPacketsDiscarded HprRtpCounter, -- pkts
hprRtpDetectGaps HprRtpCounter, -- gaps
hprRtpRateReqSends HprRtpCounter, -- rate req
hprRtpOkErrPathSws HprRtpCounter, -- ok err path
hprRtpBadErrPathSws HprRtpCounter, -- bad err path
hprRtpOkOpPathSws HprRtpCounter, -- ok op path
hprRtpBadOpPathSws HprRtpCounter, -- bad op path
hprRtpCounterDisconTime TimeStamp -- discontinuity
}
hprRtpLocNceId OBJECT-
SYNTAX OCTET STRING (SIZE (1..8))
MAX-ACCESS not-
STATUS
"The local Network Connection Endpoint (NCE) ID of this
connection. NCEs identify CPs, LUs, Boundary Functions (BFs),
and Route Setup (RS) components. A value for this object
be retrieved from any of the following objects in the
MIB
-
-
-
-
-
In each case this value identifies a row in this
containing information related to that in the APPN MIB."
::= { hprRtpEntry 1 }
hprRtpLocTcid OBJECT-
SYNTAX OCTET STRING (SIZE (8))
MAX-ACCESS not-
STATUS
"The local TCID of this RTP connection. A value for
object can be retrieved from either the appnIsInRtpTcid
or the appnIsRtpTcid object the APPN MIB; in each case
value identifies a row in this table containing
Clouston & Moore Standards Track [Page 16]
RFC 2238 Definitions of Managed Objects for HPR November 1997
related to that in the APPN MIB."
::= { hprRtpEntry 2 }
hprRtpRemCpName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Administratively assigned network name for the remote node
this RTP connection."
::= { hprRtpEntry 3 }
hprRtpRemNceId OBJECT-
SYNTAX OCTET STRING (SIZE (1..8))
MAX-ACCESS read-
STATUS
"The remote Network Connection Endpoint (NCE) of this
connection. NCEs identify CPs, LUs, Boundary Functions (BFs),
and Route Setup (RS) components."
::= { hprRtpEntry 4 }
hprRtpRemTcid OBJECT-
SYNTAX OCTET STRING (SIZE (8))
MAX-ACCESS read-
STATUS
"The remote TCID of this RTP connection."
::= { hprRtpEntry 5 }
hprRtpPathSwitchTrigger OBJECT-
SYNTAX INTEGER {
ready(1),
switchPathNow(2)
}
MAX-ACCESS read-
STATUS
"Object by which a Management Station can trigger an operator
requested path switch, by setting the value
switchPathNow(2). Setting this object to switchPathNow(2)
triggers a path switch even if its previous value was
switchPathNow(2).
Clouston & Moore Standards Track [Page 17]
RFC 2238 Definitions of Managed Objects for HPR November 1997
The value ready(1) is returned on GET operations until a
has been processed; after that the value received on the
recent SET is returned
This MIB module provides no support for an operator-
switch to a specified path."
::= { hprRtpEntry 6 }
hprRtpRscv OBJECT-
SYNTAX OCTET STRING (SIZE (0..255))
MAX-ACCESS read-
STATUS
"The forward Route Selection Control Vector for this
connection. The format of this vector is described in
Formats
The value returned in this object during a path switch
implementation-dependent: it may be the old path, the
path, a zero-length string, or some other valid RSCV string."
::= { hprRtpEntry 7 }
hprRtpTopic OBJECT-
SYNTAX DisplayString (SIZE(8))
MAX-ACCESS read-
STATUS
"The topic for this RTP connection. This is used to
the Class of Service."
::= { hprRtpEntry 8 }
hprRtpState OBJECT-
SYNTAX INTEGER {
rtpListening(1),
rtpCalling(2),
rtpConnected(3),
rtpPathSwitching(4),
rtpDisconnecting(5),
other(99)
}
MAX-ACCESS read-
STATUS
"The state of the RTP connection, from the perspective of
local RTP protocol machine
Clouston & Moore Standards Track [Page 18]
RFC 2238 Definitions of Managed Objects for HPR November 1997
rtpListening - connection open; waiting for other
to call
rtpCalling - connection opened, attempting to
out, have not yet received any
from other
rtpConnected - connection is active; responded to
call-in or received other end's
from a call-out
rtpPathSwitching - the path switch timer is running
attempting to find a new path for
connection
rtpDisconnecting - no sessions are using this connection
in process of bringing it
other - the connection is not in any of
states listed above."
::= { hprRtpEntry 9 }
hprRtpUpTime OBJECT-
SYNTAX
UNITS "1/100ths of a second
MAX-ACCESS read-
STATUS
"The length of time the RTP connection has been up,
in 1/100ths of a second."
::= { hprRtpEntry 10 }
hprRtpLivenessTimer OBJECT-
SYNTAX Unsigned32
UNITS "1/100ths of a second
MAX-ACCESS read-
STATUS
"The value of the liveness (ALIVE) timer of this
connection, in units of 1/100th of a second. When this
expires and no packet has arrived from the partner since
was last set, packets with Status Request indicators will
sent to see if the RTP connection is still alive."
::= { hprRtpEntry 11 }
hprRtpShortReqTimer OBJECT-
SYNTAX Unsigned32
UNITS "1/100ths of a second
MAX-ACCESS read-
STATUS
Clouston & Moore Standards Track [Page 19]
RFC 2238 Definitions of Managed Objects for HPR November 1997
"The value of the RTP SHORT_REQ timer, in units of 1/100 of
second. This timer represents the maximum time that a
waits for a reply from a receiver."
::= { hprRtpEntry 12 }
hprRtpPathSwTimer OBJECT-
SYNTAX Unsigned32
UNITS "1/100ths of a second
MAX-ACCESS read-
STATUS
"The length of time that RTP should attempt a path
for a connection, in units of 1/100th of a second."
::= { hprRtpEntry 13 }
hprRtpLivenessTimeouts OBJECT-
SYNTAX
UNITS "liveness timeouts
MAX-ACCESS read-
STATUS
"The count of liveness timeouts for this RTP connection."
::= { hprRtpEntry 14 }
hprRtpShortReqTimeouts OBJECT-
SYNTAX
UNITS "short request timeouts
MAX-ACCESS read-
STATUS
"The count of short request timeouts for this RTP connection."
::= { hprRtpEntry 15 }
hprRtpMaxSendRate OBJECT-
SYNTAX Gauge32
UNITS "bytes per second
MAX-ACCESS read-
STATUS
"The high-water mark for this RTP connection's send rate,
units of bytes per second. This is the high-water mark
the entire life of the connection, not just the high-
mark for the connection's current path
Clouston & Moore Standards Track [Page 20]
RFC 2238 Definitions of Managed Objects for HPR November 1997
For more details on this and other parameters related to HPR
see the High Performance Routing Architecture Reference."
::= { hprRtpEntry 16 }
hprRtpMinSendRate OBJECT-
SYNTAX Gauge32
UNITS "bytes per second
MAX-ACCESS read-
STATUS
"The low-water mark for this RTP connection's send rate,
units of bytes per second. This is the low-water mark for
entire life of the connection, not just the low-water mark
the connection's current path
For more details on this and other parameters related to HPR
see the High Performance Routing Architecture Reference."
::= { hprRtpEntry 17 }
hprRtpCurSendRate OBJECT-
SYNTAX Gauge32
UNITS "bytes per second
MAX-ACCESS read-
STATUS
"The current send rate for this RTP connection, in units
bytes per second
For more details on this and other parameters related to HPR
see the High Performance Routing Architecture Reference."
::= { hprRtpEntry 18 }
hprRtpSmRdTripDelay OBJECT-
SYNTAX Gauge32
UNITS "1/1000ths of a second
MAX-ACCESS read-
STATUS
"The smoothed round trip delay for this RTP connection,
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."
::= { hprRtpEntry 19 }
Clouston & Moore Standards Track [Page 21]
RFC 2238 Definitions of Managed Objects for HPR November 1997
hprRtpSendPackets OBJECT-
SYNTAX
UNITS "RTP packets
MAX-ACCESS read-
STATUS
"The count of packets successfully sent on this
connection."
::= { hprRtpEntry 20 }
hprRtpRecvPackets OBJECT-
SYNTAX
UNITS "RTP packets
MAX-ACCESS read-
STATUS
"The count of packets received on this RTP connection.
counter is incremented only once if duplicate copies of
packet are received."
::= { hprRtpEntry 21 }
hprRtpSendBytes OBJECT-
SYNTAX
UNITS "bytes
MAX-ACCESS read-
STATUS
"The count of bytes sent on this RTP connection. Both
Transport Header (THDR) bytes and data bytes are included
this count."
::= { hprRtpEntry 22 }
hprRtpRecvBytes OBJECT-
SYNTAX
UNITS "bytes
MAX-ACCESS read-
STATUS
"The count of bytes received on this RTP connection. Both
Transport Header (THDR) bytes and data bytes are included
this count."
::= { hprRtpEntry 23 }
hprRtpRetrPackets OBJECT-
Clouston & Moore Standards Track [Page 22]
RFC 2238 Definitions of Managed Objects for HPR November 1997
SYNTAX
UNITS "RTP packets
MAX-ACCESS read-
STATUS
"The count of packets retransmitted on this RTP connection."
::= { hprRtpEntry 24 }
hprRtpPacketsDiscarded OBJECT-
SYNTAX
UNITS "RTP packets
MAX-ACCESS read-
STATUS
"The count of packets received on this RTP connection and
discarded. A packet may be discarded because it is
to be a duplicate, or for other reasons."
::= { hprRtpEntry 25 }
hprRtpDetectGaps OBJECT-
SYNTAX
UNITS "gaps
MAX-ACCESS read-
STATUS
"The count of gaps detected on this RTP connection."
::= { hprRtpEntry 26 }
hprRtpRateReqSends OBJECT-
SYNTAX
UNITS "rate requests
MAX-ACCESS read-
STATUS
"The count of Rate Requests sent on this RTP connection."
::= { hprRtpEntry 27 }
hprRtpOkErrPathSws OBJECT-
SYNTAX
UNITS "path switch attempts
MAX-ACCESS read-
STATUS
"The count of successful path switch attempts for this
Clouston & Moore Standards Track [Page 23]
RFC 2238 Definitions of Managed Objects for HPR November 1997
connection due to errors."
::= { hprRtpEntry 28 }
hprRtpBadErrPathSws OBJECT-
SYNTAX
UNITS "path switch attempts
MAX-ACCESS read-
STATUS
"The count of unsuccessful path switches for this
connection due to errors."
::= { hprRtpEntry 29 }
hprRtpOkOpPathSws OBJECT-
SYNTAX
UNITS "path switches
MAX-ACCESS read-
STATUS
"The count of successful path switches for this RTP
due to operator requests."
::= { hprRtpEntry 30 }
hprRtpBadOpPathSws OBJECT-
SYNTAX
UNITS "path switches
MAX-ACCESS read-
STATUS
"The count of unsuccessful path switches for this
connection due to operator requests. This counter is
incremented by an implementation that does not
operator-requested path switches, even if a Management
requests such a path switch by setting
hprRtpPathSwitchTrigger object."
::= { hprRtpEntry 31 }
hprRtpCounterDisconTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The value of the sysUpTime object when the counters for
RTP connection last experienced a discontinuity. This will
Clouston & Moore Standards Track [Page 24]
RFC 2238 Definitions of Managed Objects for HPR November 1997
the more recent of two times: the time at which
connection was established or the time at which the
counters were last turned on or off."
::= { hprRtpEntry 32 }
-- *********************************************************************
-- The RTP Connection Status
-- This table contains statistics and historical information related
-- both successful and unsuccessful RTP path switches.
-- information can be important for both trend analysis and
-- determination
--
-- Note the terminology here: when RTP is triggered to find a new
-- for a connection, this initiates a 'path switch,' which will end
-- being either successful or unsuccessful. During this path switch
-- RTP will make one or more 'path switch attempts,' which are
-- to find a new path for the connection and switch the connection
-- it. This 'new' path may be the same path that the connection
-- using before the path switch
--
-- It is an implementation option how many entries to keep in
-- table, and how long to retain any individual entry
-- *********************************************************************
hprRtpStatusTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"RTP Connection Status Table: This table contains
information on RTP connections. An entry is created in
table when a path switch is completed, either successfully
unsuccessfully."
::= { hprRtp 3 }
hprRtpStatusEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"This table is indexed by local NCE ID, local TCID, and
integer hprRtpStatusIndex. Thus the primary grouping of
rows is by RTP connection, with the multiple entries for
given RTP connection ordered by time."
{ hprRtpStatusLocNceId
Clouston & Moore Standards Track [Page 25]
RFC 2238 Definitions of Managed Objects for HPR November 1997
hprRtpStatusLocTcid
hprRtpStatusIndex }
::= { hprRtpStatusTable 1 }
HprRtpStatusEntry ::= SEQUENCE {
hprRtpStatusLocNceId OCTET STRING, -- local nce
hprRtpStatusLocTcid OCTET STRING, -- local
hprRtpStatusIndex Unsigned32, --
hprRtpStatusStartTime DateAndTime, -- time
hprRtpStatusEndTime DateAndTime, -- time
hprRtpStatusRemCpName SnaControlPointName,-- remote cp
hprRtpStatusRemNceId OCTET STRING, -- remote nce
hprRtpStatusRemTcid OCTET STRING, -- remote
hprRtpStatusNewRscv OCTET STRING, -- new
hprRtpStatusOldRscv OCTET STRING, -- old
hprRtpStatusCause INTEGER, --
hprRtpStatusLastAttemptResult INTEGER -- result of
}
hprRtpStatusLocNceId OBJECT-
SYNTAX OCTET STRING (SIZE (1..8))
MAX-ACCESS not-
STATUS
"The local Network Connection Endpoint (NCE) of this
connection. NCEs identify CPs, LUs, Boundary Functions (BFs),
and Route Setup (RS) components."
::= { hprRtpStatusEntry 1 }
hprRtpStatusLocTcid OBJECT-
SYNTAX OCTET STRING (SIZE (8))
MAX-ACCESS not-
STATUS
"The local TCID of this RTP connection."
::= { hprRtpStatusEntry 2 }
hprRtpStatusIndex OBJECT-
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-
STATUS
"Table index. This value begins at one and is
when a new entry is added to the table. It is
implementation choice whether to run a single counter
Clouston & Moore Standards Track [Page 26]
RFC 2238 Definitions of Managed Objects for HPR November 1997
all entries in the table, or to run a separate counter
the entries for each RTP connection. In the unlikely
of a wrap, it is assumed that Management Stations will
the ability to order table entries correctly."
::= { hprRtpStatusEntry 3 }
hprRtpStatusStartTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The time when the path switch began."
::= { hprRtpStatusEntry 4 }
hprRtpStatusEndTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"The time when the path switch was ended, either
or unsuccessfully."
::= { hprRtpStatusEntry 5 }
hprRtpStatusRemCpName OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"Administratively assigned network name for the remote node
this RTP connection."
::= { hprRtpStatusEntry 6 }
hprRtpStatusRemNceId OBJECT-
SYNTAX OCTET STRING (SIZE (1..8))
MAX-ACCESS read-
STATUS
"The remote Network Connection Endpoint (NCE) of this
connection. NCEs identify CPs, LUs, Boundary Functions (BFs),
and Route Setup (RS) components."
::= { hprRtpStatusEntry 7 }
hprRtpStatusRemTcid OBJECT-
Clouston & Moore Standards Track [Page 27]
RFC 2238 Definitions of Managed Objects for HPR November 1997
SYNTAX OCTET STRING (SIZE (8))
MAX-ACCESS read-
STATUS
"The remote TCID of this RTP connection."
::= { hprRtpStatusEntry 8 }
hprRtpStatusNewRscv OBJECT-
SYNTAX OCTET STRING (SIZE (0..255))
MAX-ACCESS read-
STATUS
"The new Route Selection Control Vector for this
connection. A zero-length string indicates that no value
available, perhaps because the implementation does not
RSCVs."
::= { hprRtpStatusEntry 9 }
hprRtpStatusOldRscv OBJECT-
SYNTAX OCTET STRING (SIZE (0..255))
MAX-ACCESS read-
STATUS
"The old Route Selection Control Vector for this
connection. A zero-length string indicates that no value
available, perhaps because the implementation does not
RSCVs."
::= { hprRtpStatusEntry 10 }
hprRtpStatusCause OBJECT-
SYNTAX INTEGER {
other(1),
rtpConnFail(2),
locLinkFail(3),
remLinkFail(4),
operRequest(5)
}
MAX-ACCESS read-
STATUS
"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
Clouston & Moore Standards Track [Page 28]
RFC 2238 Definitions of Managed Objects for HPR November 1997
remLinkFail(4) - Remote link failure (learned from TDUs),
operRequest(5) - Operator requested path switch. "
::= { hprRtpStatusEntry 11 }
hprRtpStatusLastAttemptResult OBJECT-
SYNTAX INTEGER { successful(1),
initiatorMoving(2),
directorySearchFailed(3),
rscvCalculationFailed(4),
negativeRouteSetupReply(5),
backoutRouteSetupReply(6),
timeoutDuringFirstAttempt(7),
otherUnsuccessful(8)
}
MAX-ACCESS read-
STATUS
"The result of the last completed path switch attempt. If
path switch is aborted in the middle of a path switch
because the path switch timer expires, the result of
previous path switch attempt is reported
The values are defined as follows
successful(1) - The final path
attempt was successful
initiatorMoving(2) - The final path
attempt failed because
initiator is mobile,
there was no active
out of this node
directorySearchFailed(3) - The final path
attempt failed because
directory search for
destination node's CP
failed
rscvCalculationFailed(4) - The final path
attempt failed because
RSCV to the node
the remote RTP
could not be calculated
negativeRouteSetupReply(5) - The final path
attempt failed because
setup failed for the
path
backoutRouteSetupReply(6) - The final path
attempt failed because
Clouston & Moore Standards Track [Page 29]
RFC 2238 Definitions of Managed Objects for HPR November 1997
remote RTP endpoint
to continue the
connection
timeoutDuringFirstAttempt(7) - The path switch
expired during the
path switch attempt
otherUnsuccessful(8) - The final path
attempt failed for a
other than those
above."
::= { hprRtpStatusEntry 12 }
-- ***************************************************************
-- Conformance
-- ***************************************************************
hprConformance OBJECT IDENTIFIER ::= { hprMIB 2 }
hprCompliances OBJECT IDENTIFIER ::= { hprConformance 1 }
hprGroups OBJECT IDENTIFIER ::= { hprConformance 2 }
-- Compliance
hprCompliance MODULE-
STATUS
"The compliance statement for the SNMPv2 entities
implement the HPR MIB."
MODULE -- this
-- Unconditionally mandatory
MANDATORY-GROUPS {
hprGlobalConfGroup
hprAnrRoutingConfGroup
}
-- Conditionally mandatory
GROUP
"The hprRtpConfGroup is mandatory for HPR
supporting the HPR transport tower."
::= { hprCompliances 1 }
Clouston & Moore Standards Track [Page 30]
RFC 2238 Definitions of Managed Objects for HPR November 1997
-- Units of
hprGlobalConfGroup OBJECT-
OBJECTS {
hprNodeCpName
}
STATUS
"A collection of objects providing the instrumentation of
general information and capabilities."
::= { hprGroups 1 }
hprAnrRoutingConfGroup OBJECT-
OBJECTS {
hprAnrsAssigned
hprAnrCounterState
hprAnrCounterStateTime
hprAnrType
hprAnrOutTgDest
hprAnrOutTgNum
hprAnrPacketsReceived
}
STATUS
"A collection of objects providing instrumentation for
node's ANR routing."
::= { hprGroups 2 }
hprTransportUserConfGroup OBJECT-
OBJECTS {
hprNceType
hprNceDefault
}
STATUS
"A collection of objects providing information on the users
the HPR transport known to the node."
::= { hprGroups 3 }
hprRtpConfGroup OBJECT-
OBJECTS {
hprRtpGlobeConnSetups
hprRtpGlobeCtrState
Clouston & Moore Standards Track [Page 31]
RFC 2238 Definitions of Managed Objects for HPR November 1997
hprRtpGlobeCtrStateTime
hprRtpRemCpName
hprRtpRemNceId
hprRtpRemTcid
hprRtpPathSwitchTrigger
hprRtpRscv
hprRtpTopic
hprRtpState
hprRtpUpTime
hprRtpLivenessTimer
hprRtpShortReqTimer
hprRtpPathSwTimer
hprRtpLivenessTimeouts
hprRtpShortReqTimeouts
hprRtpMaxSendRate
hprRtpMinSendRate
hprRtpCurSendRate
hprRtpSmRdTripDelay
hprRtpSendPackets
hprRtpRecvPackets
hprRtpSendBytes
hprRtpRecvBytes
hprRtpRetrPackets
hprRtpPacketsDiscarded
hprRtpDetectGaps
hprRtpRateReqSends
hprRtpOkErrPathSws
hprRtpBadErrPathSws
hprRtpOkOpPathSws
hprRtpBadOpPathSws
hprRtpCounterDisconTime
hprRtpStatusStartTime
hprRtpStatusEndTime
hprRtpStatusRemNceId
hprRtpStatusRemTcid
hprRtpStatusRemCpName
hprRtpStatusNewRscv
hprRtpStatusOldRscv
hprRtpStatusCause
}
Clouston & Moore Standards Track [Page 32]
RFC 2238 Definitions of Managed Objects for HPR November 1997
STATUS
"A collection of objects providing the instrumentation for
connection end points."
::= { hprGroups 4 }
-- end of conformance
6.
This MIB module is the product of the IETF SNA NAU MIB WG and the
APPN/HPR MIBs SIG. Thanks to Ray Bird, IBM Corporation; Jim Cobban
Nortel; and Laura Petrie, IBM Corporation, for their
and review
7.
[1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser
"Structure of Management Information for version 2
the Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996.
[2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser
"Textual Conventions for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[3] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser
"Conformance Statements for Version 2 of the
Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[4] Clouston, B., and B. Moore, "Definition of Managed Objects
APPN", RFC 2115, June 1997.
[5] IBM, APPN High Performance Routing Architecture Reference, SV40-
1018-00.
[6] IBM, SNA/MS Formats, GC31-8302-00
8. Security
In most cases, MIBs are not themselves security risks; if
security is operating as intended, the use of a MIB to
information about a system, or to change some parameter at
system, is a tool, not a threat
Clouston & Moore Standards Track [Page 33]
RFC 2238 Definitions of Managed Objects for HPR November 1997
None of the read-only objects in the HPR MIB reports a password,
data, or anything else that is particularly sensitive.
enterprises view their network configuration itself, as well
information about network usage and performance, as corporate assets
such enterprises may wish to restrict SNMP access to most of
objects in the MIB
One read-write object in the MIB can affect network operations
o hprRtpPathSwitchTrigger: Setting this object to 'switchPathNow
triggers an immediate path switch attempt. An HPR path
does not itself disrupt the SNA sessions using the
connection undergoing the path switch. However, frequent
switches for many RTP connections can have an adverse impact
overall network performance
It is recommended that SNMP access to this object be restricted
Other read-write objects control the gathering of
management data; controlling access to these objects is
critical
9. Authors'
Bob
Cisco
7025 Kit Creek
P.O. Box 14987
Research Triangle Park, NC 27709,
Phone: +1 919 472 2333
EMail: clouston@cisco.
Bob
IBM
800 Park Offices
CNMA/664
P.O. Box 12195
Research Triangle Park, NC 27709,
Phone: +1 919 254 4436
EMail: remoore@ralvm6.vnet.ibm.
Clouston & Moore Standards Track [Page 34]
RFC 2238 Definitions of Managed Objects for HPR November 1997
10. Full Copyright
Copyright (C) The Internet Society (1997). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Clouston & Moore Standards Track [Page 35]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
