|
Network Working Group Request for Comments: 2455 Obsoletes: 2155 Category: Standards Track |
B. Clouston Cisco Systems B. Moore IBM Corporation November 1998 |
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Copyright © The Internet Society (1998). All Rights Reserved.
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 APPN (Advanced Peer-to-Peer Networking) capabilities. This memo identifies managed objects for the APPN protocol.
1. Introduction
2. The SNMPv2 Network Management Framework
3. Overview
3.1 Relationship with RFC 2155
3.2 APPN MIB structure
4. Definitions
5. Security Considerations
6. Intellectual Property
7. Acknowledgments
8. References
9. Authors' Addresses
10. Full Copyright Statement
This document is a product of the SNA NAU Services MIB Working Group. It defines a MIB module for managing devices with Advanced Peer-to- Peer Networking (APPN) capabilities.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [17].
The SNMP Management Framework presently consists of five major components:
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB.
This document identifies a set of objects for monitoring the configuration and active characteristics of devices with APPN capabilities, and for controlling certain characteristics. APPN is the aspect of Systems Network Architecture (SNA) that supports peer- to-peer networking. These networks transport both independent and dependent LU session traffic. See the SNANAU APPC MIB [21] and the SNA NAU MIB [22] for management of these sessions. See also RFC 2232, the DLUR MIB [23], and RFC 2238, the HPR MIB [24] for management of extensions to the APPN architecture. In this document, we describe APPN managed objects.
An APPN network comprises various types of nodes, and transmission groups (TGs) that connect the nodes. Network nodes (NNs) provide directory and routing functions for session establishment. NNs may be session end points or intermediate nodes in a session. A border node is a type of network node that connects networks together for session establishment without fully merging them. A branch network node (BrNN) is a network node that is similar to a border node, but with only minimal functions to build a large APPN network within an enterprise. Although a BrNN is defined to be a network node in the APPN architecture, it also has an end node (EN) appearance to upstream NNs in the network. In this MIB module it is treated as a separate node type since it does not fit cleanly as an EN or NN, and this module explicity identifies those objects returned by a BrNN. For example, a BrNN does not implement the appnNnTopo objects since it is the only node in its network topology table; but it does implement the appnSessIntermediate objects since it does have intermediate session support. It also implements two of the appnEnUniqueCaps objects that could be useful to a management application. A BrNN identifies itself as 'endNode' in the appnNodeType object but further identifies itself as a BrNN in the appnNodeBrNn object.
End nodes are session end points that receive directory and routing functions from network nodes, over control-point to control-point (CP-CP) sessions. Low-entry networking (LEN) nodes are also session
end points, but do not support CP-CP sessions, and therefore need additional manual configuration definitions to establish sessions in an APPN network. ENs and LEN nodes may have minimal directory and routing functions to establish control sessions (ENs) or to connect into the APPN network (LEN nodes).
Virtual routing nodes (VRNs) are not really nodes, but rather common definitions among actual nodes in a shared transport facility such as a local area network (LAN) that allow these actual nodes to temporarily establish a logical link with one another without defining each other's link-level addressing information.
Ports and link stations are the node's interface to the data link control (DLC), which provides the physical transport, or to another protocol such as Data Link Switching (DLSw), which provides transport over an IP network. See the SNADLC SDLC MIB[25], the SNADLC LLC MIB[26], and the DLSw MIB[27]. A link station uses a port to make a connection to another node. This connection establishes a TG between the two nodes.
The directory and routing functions enable an NN to find where an LU is located in the network, and calculate the optimal route for the session based on the requested class of service (COS). A network node saves the LU information in a directory database, which is built from LUs defined locally, LU registration from served end nodes, and LUs learned from network searches.
Each NN maintains a local COS database that assigns a routing weight, or relative cost, to each resource for each class of service. For example, the #INTER COS assigns a lower weight to TGs with a greater effective capacity, while the #BATCH COS favors TGs with a lower relative cost per byte.
A node saves network topology information (on NNs, VRNs, and TGs between them) in a network topology database. A node that supports APPN function set 1120, branch awareness, also saves information on TGs to adjacent BrNNs. The topology information includes state and routing characteristics. Topology information is exchanged between NNs over CP-CP sessions such that the database is fully replicated at each NN. Information on TGs to all node types are kept in a local topology database. Local topology information is shared with other nodes only during the session establishment process, to give the NN responsible for route calculation the necessary information for end- to-end route calculation.
A management application can show a full representation of the APPN network from the network and local topology information. To show the network topology, the application need only query the network
topology tables from a single NN. To show all of the BrNNs, the
application must also directly query all destinations of TGs that
indicate they are branch TGs (indicated by the appnNnTgFRBranchTg
object) to see if they have any cascaded BrNNs. For any NNs that do
not indicate branch awareness support (indicated by the
appnNnNodeFRBranchAwareness object), the application must query each
NN's appnLocalTgTable, and then the appnNodeBrNn object of each row's
destination node to identify BrNNs. To show all of the nodes in the
network, including ENs and LEN nodes, the application must query
every NN's appnLocalTgTable, and iteratively do the same for each
BrNN it finds.
SNA names such as LU names, CP names, COS names, and mode names can
be padded with blanks (space characters) in SNA formats. These
blanks are nonsignificant. For example, in a BIND Request Unit (RU)
a COS name of "#INTER" with a length of 6 is identical to a COS name
of "#INTER " with a length of 8. However, in this MIB,
nonsignificant blanks are not included by the agent. Using the COS
name from the previous example, an agent would return a length of 6
and the string "#INTER" with no blanks for appnCosName, regardless of
how it appears in the BIND RU or in internal storage. The lone
exception is the all blank mode name, for which the agent returns a
length of 8 and the string " " (8 blank spaces). The MIB variables that this applies to are identified by a textual convention syntax that also describes this behavior.
When an SNA name is functioning as a table index, an agent treats trailing blanks as significant. If a management station requests the objects from a row with index "#INTER ", the agent does not match this to the row with index "#INTER". Since an agent has no nonsignificant blanks in any of its table indices, the only reason for a Management Station to include them would be to start GetNext processing at a chosen point in a table. For example, a GetNext
request with index "M " would start retrieval from a table at the first row with an 8-character index beginning with "M" or a letter after "M".
The SNA/APPN terms and overall architecture are documented in [18], [19], [20], and [28].
Highlights of the management functions supported by the APPN MIB module include the following:
This MIB module does not support:
This MIB obsoletes RFC 2155 [29] with changes due to additions to the APPN architecture and some implementation experience of RFC 2155. The changes from RFC 2155 are as follows:
The APPN MIB module contains the following groups of objects:
These groups are described below in more detail.
The appnNode group consists of the following tables and objects:
1) appnGeneralInfoAndCaps
This group of objects describes general information about the APPN node. The type of information includes the node type and the time since this node was initialized.
2) appnNnUniqueInfoAndCaps
This group of objects describes information specific to network nodes such as node routing characteristics.
3) appnEnUniqueInfoAndCaps
This group of objects describes information specific to end nodes, with two objects that also apply to branch network nodes. This group includes an object indicating the node's network node server.
4) appnPortInformation
This includes the appnPortTable, which describes the configuration and current status of the ports used by APPN, including the port state and DLC type.
5) appnLinkStationInformation
This includes the appnNodeLsTable, which describes the configuration
and current status of the link stations used by APPN, including the
link state and port name; and the appnLsStatusTable, which provides
information about errors this node encountered with connections to
adjacent nodes, such as the sense data captured during connection
failures. It is a product option to decide how many
appnLsStatusTable entries are kept.
6) appnVrnInfo
This includes the appnVrnTable, which describes the relationship between virtual routing nodes' TGs described in the appnLocalTgTable with ports in the appnPortTable.
The appnNn group consists of the following objects and tables
1) appnNnTopo
These objects contain general information about the network topology database including the number of nodes present, and the number of topology database updates (TDU) wars the node has detected.
2) appnNnTopology
This includes tables representing the APPN network topology database. This includes the network nodes, virtual routing nodes, and TGs between these nodes, as well as the information about these resources carried in topology updates. The tables are first indexed by the same flow reduction sequence number (FRSN) used in topology exchanges between NNs. This allows a management station to retrieve only incremental updates, since the agent will update the FRSN of new or changed resources.
The appnLocalTopology group consists of the following objects and tables:
1) appnLocalThisNode
a) appnLocalGeneral
Contains the local node and type.
b) appnLocalNnSpecific
These objects contain routing information about the local network node.
c) appnLocalTg
This table represents information about this node's local TGs.
2) appnLocalEnTopology
This table represents TG information for EN TGs learned by the NN via TG registration with the local node.
The appnDir group consists of the following objects and tables:
1) appnDirPerf
These objects represent information related to information about the directory database and directory searches involving this node.
2) appnDirTable
This table represents the directory database, listing LUs known to this node, along with the owning node of the LU and the serving NN of the owning node.
The appnCos group consists of the following tables:
1) appnCosModeTable
This table represents the mode to class of service mapping.
2) appnCosNameTable
This table represents the tranmission priority for each class of service.
3) appnCosNodeRowTable
This table represents the node-row information for each class of service, including the weight of each node.
3) appnCosTGRowTable
This table represents the TG-row information for each class of service, including the weight of each TG.
The appnSessIntermediate group consists of the following objects and tables:
1) appnIsInGlobal
These objects allow control of the collection of intermediate session information such as Route Selection Control Vectors (RSCVs) and counters.
2) appnIsInTable
This table contains information on active intermediate sessions.
3) appnIsRtpTable
This table contains information on active intermediate sessions that are being transported on Rapid Transport Protocol (RTP) connections by High Performance Routing (HPR).
One APPN trap is defined. It is intended to correspond to SNA/MS Alerts, but is optional for a product to implement this trap. The trap identifies the Alert ID number and, where possible, the affected resource.
APPN-MIB DEFINITIONS ::= BEGIN
IANAifType
FROM IANAifType-MIB
DisplayString, VariablePointer, RowPointer, DateAndTime,
TruthValue, TimeStamp, TEXTUAL-CONVENTION
FROM SNMPv2-TC
Counter32, Gauge32, Unsigned32, TimeTicks,
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
snanauMIB
FROM SNA-NAU-MIB;
"
Bob Clouston
Cisco Systems
7025 Kit Creek Road
Tel: 1 919 472 2333
E-mail: clouston@cisco.com
Bob Moore
IBM Corporation
4205 S. Miami Boulevard
BRQA/501
Tel: 1 919 254 4436
E-mail: remoore@us.ibm.com
"
DESCRIPTION
"This is the MIB module for objects used to
manage network devices with APPN capabilities."
-- Revision tracking starts with Proposed Standard (RFC 2155)
REVISION "9807151800Z"
DESCRIPTION
"Minor editorial fixes; new value 'none(5)' added
to the enumeration for the appnLocalTgBranchLinkType
object."
REVISION "9805261800Z"
DESCRIPTION
"Post-RFC 2155 conformance definitions added,
appnNodeLsCounterType and appnNodeBrNn objects
added, appnNodeMibVersion object deprecated."
REVISION "9707311800Z"
DESCRIPTION
"Branch network node (Branch Extender) objects added."
REVISION "9703311800Z"
DESCRIPTION
"MLTG objects added."
REVISION "9703201200Z"
DESCRIPTION
"RFC 2155 (Proposed Standard)"
::= { snanauMIB 4 }
-- snanauMIB ::= { mib-2 34 }
-- *********************************************************************
-- Textual Conventions
-- *********************************************************************
SnaNodeIdentification ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An SNA Node Identification consists of two parts, which
together comprise four bytes of hexadecimal data. In SNA the
Node Identification is transported in bytes 2-5 of the XID.
The block number is the first three digits of the Node Identification. These 3 hexadecimal digits identify the product.
The ID number is the last 5 digits of the Node Identification. These 5 hexadecimal digits are administratively defined and combined with the 3-digit block number form the 8-digit Node Identification. A unique value is required for connections to SNA subarea. In some implementations, the value 'bbb00000' (where 'bbb' represents a 3-digit block number) is returned to mean that the ID number is not unique on this node.
An SNA Node Identification is represented as eight ASCII-encoded hexadecimal digits, using the characters '0' - '9' and 'A' - 'F'."
SYNTAX OCTET STRING (SIZE (8))
SnaControlPointName ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A fully qualified SNA control point name, consisting of a 1 to
8 character network identifier (NetId), a period ('.'), and a 1
to 8 character control point name (CpName).
The NetId and CpName are constructed from the uppercase letters 'A' - 'Z' and the numerics '0' - '9', all encoded in ASCII, with the restriction that the first character of each must be a letter. Trailing blanks are not allowed.
Earlier versions of SNA permitted three additional characters in NetIds and CpNames: '#', '@', and '$'. While this use of these characters has been retired, a Management Station should still accept them for backward compatibility."
SYNTAX OCTET STRING (SIZE (3..17))
SnaClassOfServiceName ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An SNA class-of-service (COS) name, ranging from 1 to 8
ASCII characters. COS names take one of two forms:
- a user-defined COS name is constructed from the uppercase
letters 'A' - 'Z' and the numerics '0' - '9', with the
restriction that the first character of the name must be
a letter.
- an SNA-defined user-session COS name begins with the
character '#', which is followed by up to seven
additional characters from the set of uppercase letters
and numerics.
Trailing blanks are not allowed in either form of COS name.
A zero-length string indicates that a COS name is not available."
SYNTAX OCTET STRING (SIZE (0..8))
SnaModeName ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An SNA mode name, ranging from 1 to 8 ASCII characters.
Mode names take one of two forms:
- a user-defined mode name is constructed from the
uppercase letters 'A' - 'Z' and the numerics '0' - '9',
with the restriction that the first character of the name must be a letter.
- an SNA-defined user-session mode name begins with the
character '#', which is followed by up to seven
additional characters from the set of uppercase letters
and numerics.
Trailing blanks are not allowed in either form of mode name, with the single exception of the all-blank mode name, where a string consisting of 8 blanks is returned.
A zero-length string indicates that a mode name is not available."
SYNTAX OCTET STRING (SIZE (0..8))
SnaSenseData ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"To facilitate their display by a Management Station, sense
data objects in the MIB are represented as OCTET STRINGS
containing eight ASCII characters. Eight '0' characters
indicates that no sense data identifying an SNA error
condition is available.
An SNA sense data is represented as eight hexadecimal digits, using the characters '0' - '9' and 'A' - 'F'."
SYNTAX OCTET STRING (SIZE (8))
DisplayableDlcAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"DLC address of a port or link station, represented as an
OCTET STRING containing 0 to 64 ASCII characters.
A Management Station should use a value of this type only
for display. The 'real' DLC address, i.e., the sequence of
bytes that flow in the DLC header, is often available in a
DLC-specific MIB.
The zero-length string indicates that the DLC address in question is not known to the agent."
SYNTAX OCTET STRING (SIZE (0..64))
AppnNodeCounter ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An object providing global statistics for the entire APPN node. A Management Station can detect discontinuities in this counter by monitoring the appnNodeCounterDisconTime object."
SYNTAX Counter32
AppnPortCounter ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An object providing statistics for an APPN port. A
Management Station can detect discontinuities in this counter
by monitoring the appnPortCounterDisconTime object."
SYNTAX Counter32
AppnLinkStationCounter ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"An object providing statistics for an APPN link station. A
Management Station can detect discontinuities in this counter
by monitoring the appnLsCounterDisconTime object."
SYNTAX Counter32
AppnTopologyEntryTimeLeft ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Number of days before deletion of this entry from the topology
database. Range is 0-15. A value of 0 indicates that the
entry is either in the process of being deleted, or is being
marked for deletion at the next garbage collection cycle."
SYNTAX INTEGER (0..15)
AppnTgDlcData ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"DLC-specific data related to a connection network transmission
group. For other TGs, a zero-length string is returned.
Examples of the type of data returned by an object with this syntax include the following:
Token-Ring - MAC/SAP
X.25 Switched - dial digits
X.21 Switched - dial digits
Circuit Switch - dial digits
This MIB does not specify formats for these or any other types of DLC-specific data. Formats may, however, be specified in documents related to a particular DLC.
The contents of an object with this syntax correspond to the contents of the DLC-specific subfields of cv46, documented in (6)."
SYNTAX OCTET STRING (SIZE (0..64))
AppnTgEffectiveCapacity ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value representing the effective capacity of a transmission
group. This is an administratively assigned value derived from
the link bandwidth and maximum load factor. It is encoded in
the same way as byte 7 of cv47, and represents a floating-point
number in units of 300 bits per second."
SYNTAX OCTET STRING (SIZE (1))
AppnTgSecurity ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A value representing the level of security on a transmission
group. A class of service definition includes an indication of
the acceptable TG security value(s) for that class of service.
The following seven values are defined:
nonsecure(1) -
(X'01'): none of the values listed below;
for example, satellite-connected or
located in a nonsecure country
publicSwitchedNetwork(32) -
(X'20'): public switched network; secure
in the sense that there is no
predetermined route that traffic will take
undergroundCable(64) -
(X'40'): underground cable; located in a
secure country (as determined by the
network administrator)
secureConduit(96) -
(X'60'): secure conduit, not guarded; for
example, pressurized pipe
guardedConduit(128) -
(X'80'): guarded conduit; protected
against physical tapping
encrypted(160) -
(X'A0'): link-level encryption is provided
guardedRadiation(192) -
(X'C0'): guarded conduit containing the
transmission medium; protected against
physical and radiation tapping"
SYNTAX INTEGER {
nonsecure(1), -- X'01'
publicSwitchedNetwork(32), -- X'20'
undergroundCable(64), -- X'40'
secureConduit(96), -- X'60'
guardedConduit(128), -- X'80'
encrypted(160), -- X'A0'
guardedRadiation(192) -- X'C0'
}
AppnTgDelay ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Relative amount of time that it takes for a signal to travel
the length of a logical link. This time is represented in
microseconds, using the same encoding scheme used in cv47 in a
topology update. Some of the more common values, along with
their encoded hex values, are:
minimum(0), X'00'
negligible(384), X'4C'
terrestrial(9216), X'71'
packet(147456), X'91'
long(294912), X'99'
maximum(2013265920) X'FF'
"
SYNTAX OCTET STRING (SIZE (1))
-- *********************************************************************
appnObjects OBJECT IDENTIFIER ::= { appnMIB 1 }
-- *********************************************************************
-- ******************** The APPN Node Group ****************************
appnNode OBJECT IDENTIFIER ::= { appnObjects 1 }
appnGeneralInfoAndCaps OBJECT IDENTIFIER ::= { appnNode 1 }
appnNnUniqueInfoAndCaps OBJECT IDENTIFIER ::= { appnNode 2 }
appnEnUniqueCaps OBJECT IDENTIFIER ::= { appnNode 3 }
appnPortInformation OBJECT IDENTIFIER ::= { appnNode 4 }
appnLinkStationInformation OBJECT IDENTIFIER ::= { appnNode 5 }
appnVrnInfo OBJECT IDENTIFIER ::= { appnNode 6 }
-- This group provides global information about an APPN network node,
-- an APPN end node, an APPN branch network node, or an LEN node. -- APPN General Information
-- This section applies to APPN network nodes, end nodes, and branch
-- network nodes, as well as to LEN end nodes.
::= { appnGeneralInfoAndCaps 1 }
-- appnNodeMibVersion OBJECT-TYPE (deprecated: moved to end of module)
::= { appnGeneralInfoAndCaps 3 }
SYNTAX INTEGER {
networkNode(1),
endNode(2),
t21len(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Type of APPN node:
networkNode(1) - APPN network node
endNode(2) - APPN end node
t21len(4) - LEN end node
Note: A branch network node SHALL return endNode(2) as the value of this object. A management application
can distinguish between a branch network node and an actual end node by retrieving the appnNodeBrNn object."
::= { appnGeneralInfoAndCaps 4 }
::= { appnGeneralInfoAndCaps 5 }
::= { appnGeneralInfoAndCaps 6 }
::= { appnGeneralInfoAndCaps 7 }
SYNTAX INTEGER {
noHprSupport(1),
hprBaseOnly(2),
rtpTower(3),
controlFlowsOverRtpTower(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates this node's level of support for high-performance
routing (HPR):
noHprSupport(1) - no HPR support
hprBaseOnly(2) - HPR base (option set 1400)
supported
rtpTower(3) - HPR base and RTP tower
(option set 1401) supported
controlFlowsOverRtpTower(4) - HPR base, RTP tower, and
control flows over RTP
(option set 1402) supported
This object corresponds to cv4580, byte 9, bits 3-4."
::= { appnGeneralInfoAndCaps 8 }
::= { appnGeneralInfoAndCaps 9 }
::= { appnGeneralInfoAndCaps 10 }
::= { appnGeneralInfoAndCaps 11 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of HPR route setups sent for routes
originating in this node since the node was last
reinitialized."
::= { appnGeneralInfoAndCaps 12 }
::= { appnGeneralInfoAndCaps 13 }
::= { appnGeneralInfoAndCaps 14 }
::= { appnGeneralInfoAndCaps 15 }
::= { appnGeneralInfoAndCaps 16 }
SYNTAX INTEGER {
other(1),
noAnr(2),
anrForLocalNces(3),
allAnr(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates which ANR traffic, if any, the node includes in the
counts returned by the APPN link station counters
appnLsInXidBytes, appnLsInMsgBytes, appnLsInXidFrames,
appnLsInMsgFrames, appnLsOutXidBytes, appnLsOutMsgBytes,
appnLsOutXidFrames, and appnLsOutMsgFrames. These counters
are always incremented for ISR traffic.
The following values are defined:
other(1) - the node does something different
from all the options listed below
noAnr(2) - the node does not include any ANR
traffic in these counts
anrForLocalNces(3) - the node includes in these counts
ANR traffic for RTP connections
that terminate in this node, but
not ANR traffic for RTP connections
that pass through this node without
terminating in it
allAnr(4) - the node includes all ANR traffic
in these counts."
::= { appnGeneralInfoAndCaps 17 }
Note: throughout the remainder of this MIB module, branch network node is treated as a third node type, parallel to network node and end node. This is not how branch network nodes are treated in the base APPN architecture, but it
increases clarity to do it here."
::= { appnGeneralInfoAndCaps 18 }
-- *********************************************************************
-- APPN Network Node Information
-- This section provides global information about an APPN network node.
-- *********************************************************************
This object corresponds to cv4580, byte 8, bit 1."
::= { appnNnUniqueInfoAndCaps 1 }
SYNTAX INTEGER {
noCache(1),
cacheNoIncrUpdate(2),
cacheWithIncrUpdate(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates this node's level of support for caching of route
trees. Three levels are specified:
noCache(1) - caching of route trees is not
supported
cacheNoIncrUpdate(2) - caching of route trees is
supported, but without incremental
updates
cacheWithIncrUpdate(3) - caching of route trees with
incremental updates is supported"
::= { appnNnUniqueInfoAndCaps 2 }
"Route addition resistance.
This administratively assigned value indicates the relative desirability of using this node for intermediate session traffic. The value, which can be any integer 0-255, is used in route computation. The lower the value, the more desirable the node is for intermediate routing.
This object corresponds to cv4580, byte 6."
::= { appnNnUniqueInfoAndCaps 3 }
This object corresponds to cv4580, byte 8, bit 2."
::= { appnNnUniqueInfoAndCaps 4 }
::= { appnNnUniqueInfoAndCaps 5 }
This object corresponds to cv4580, byte 9, bit 0."
::= { appnNnUniqueInfoAndCaps 6 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether this node has interchange node support.
This object corresponds to cv4580, byte 9, bit 1."
::= { appnNnUniqueInfoAndCaps 7 }
This object corresponds to cv4580, byte 9, bit 2."
::= { appnNnUniqueInfoAndCaps 8 }
If this number is not zero, then the topology database is saved each time the total number of topology database updates (TDUs) received by this node increases by this number. A value of zero indicates that the topology database is not being saved."
::= { appnNnUniqueInfoAndCaps 9 }
This object corresponds to the numeric value in cv4580, bytes 2-5."
::= { appnNnUniqueInfoAndCaps 10 }
This object corresponds to cv4580, byte 7, bit 0."
::= { appnNnUniqueInfoAndCaps 11 }
This object corresponds to cv4580, byte 7, bit 1."
::= { appnNnUniqueInfoAndCaps 12 }
This object corresponds to cv4580, byte 7, bit 5."
::= { appnNnUniqueInfoAndCaps 13 }
This object corresponds to cv4580, byte 8, bit 0."
::= { appnNnUniqueInfoAndCaps 14 }
-- *********************************************************************
-- APPN End Node Information
-- This section provides global information about an APPN end node. Two
-- of the objects are also implemented by a branch network node.
-- *********************************************************************
::= { appnEnUniqueCaps 1 }
A branch network node shall also implement this object."
::= { appnEnUniqueCaps 2 }
A branch network node shall also implement this object."
::= { appnEnUniqueCaps 3 }
-- *********************************************************************
-- APPN Port information
-- This section provides information about an APPN node's ports.
-- *********************************************************************
::= { appnPortInformation 1 }
INDEX
{ appnPortName }
::= { appnPortTable 1 }
AppnPortEntry ::= SEQUENCE {
appnPortName DisplayString,
appnPortCommand INTEGER,
appnPortOperState INTEGER,
appnPortDlcType IANAifType,
appnPortPortType INTEGER,
appnPortSIMRIM TruthValue,
appnPortLsRole INTEGER,
appnPortNegotLs TruthValue,
appnPortDynamicLinkSupport TruthValue,
appnPortMaxRcvBtuSize INTEGER,
appnPortMaxIframeWindow Gauge32,
appnPortDefLsGoodXids AppnPortCounter,
appnPortDefLsBadXids AppnPortCounter,
appnPortDynLsGoodXids AppnPortCounter,
appnPortDynLsBadXids AppnPortCounter,
appnPortSpecific RowPointer,
appnPortDlcLocalAddr DisplayableDlcAddress,
appnPortCounterDisconTime TimeStamp
}
SYNTAX DisplayString (SIZE (1..10))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Administratively assigned name for this APPN port."
::= { appnPortEntry 1 }
SYNTAX INTEGER {
deactivate(1),
activate(2),
recycle(3),
ready(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Object by which a Management Station can activate, deactivate,
or recycle (i.e., cause to be deactivated and then immediately
activated) a port, by setting the value to activate(1),
deactivate(2), or recycle(3), respectively. The value ready(4)
is returned on GET operations until a SET has been processed;
after that the value received on the most recent SET is
returned."
::= { appnPortEntry 2 }
SYNTAX INTEGER {
inactive(1),
pendactive(2),
active(3),
pendinact(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the current state of this port:
inactive(1) - port is inactive
pendactive(2) - port is pending active
active(3) - port is active
pendinact(4) - port is pending inactive"
::= { appnPortEntry 3 }
::= { appnPortEntry 4 }
SYNTAX INTEGER {
leased(1),
switched(2),
sharedAccessFacilities(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Identifies the type of line used by this port:
leased(1) - leased line
switched(2) - switched line
sharedAccessFacilities(3) - shared access facility, such
as a LAN."
::= { appnPortEntry 5 }
::= { appnPortEntry 6 }
SYNTAX INTEGER {
primary(1),
secondary(2),
negotiable(3),
abm(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Initial role for link stations activated through this port. The values map to the following settings in the initial XID, where 'ABM' indicates asynchronous balanced mode and 'NRM' indicated normal response mode:
primary(1): ABM support = 0 ( = NRM)
role = 01 ( = primary)
secondary(2): ABM support = 0 ( = NRM)
role = 00 ( = secondary)
negotiable(3): ABM support = 0 ( = NRM)
role = 11 ( = negotiable)
abm(4): ABM support = 1 ( = ABM)
role = 11 ( = negotiable)"
::= { appnPortEntry 7 }
::= { appnPortEntry 8 }
::= { appnPortEntry 9 }
This object corresponds to bytes 21-22 of XID3."
::= { appnPortEntry 10 }
::= { appnPortEntry 11 }
::= { appnPortEntry 12 }
::= { appnPortEntry 13 }
::= { appnPortEntry 14 }
SYNTAX AppnPortCounter
UNITS "XID exchanges"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The total number of unsuccessful XID exchanges that have
occurred on all dynamic link stations on this port since the
last time this port was started."
::= { appnPortEntry 15 }
If the agent is unable to identify such an object, the value 0.0 is returned."
::= { appnPortEntry 16 }
::= { appnPortEntry 17 }
::= { appnPortEntry 18 }
-- *********************************************************************
-- APPN Link Station Information
-- This section provides information about an APPN node's link stations.
-- *********************************************************************
::= { appnLinkStationInformation 1 }
INDEX
{ appnLsName }
::= { appnLsTable 1 }
AppnLsEntry ::= SEQUENCE {
appnLsName DisplayString,
appnLsCommand INTEGER,
appnLsOperState INTEGER,
appnLsPortName DisplayString,
appnLsDlcType IANAifType,
appnLsDynamic TruthValue,
appnLsAdjCpName OCTET STRING,
appnLsAdjNodeType INTEGER,
appnLsTgNum INTEGER,
appnLsLimResource TruthValue,
appnLsActOnDemand TruthValue,
appnLsMigration TruthValue,
appnLsPartnerNodeId SnaNodeIdentification,
appnLsCpCpSessionSupport TruthValue,
appnLsMaxSendBtuSize INTEGER,
-- performance data
appnLsInXidBytes AppnLinkStationCounter,
appnLsInMsgBytes AppnLinkStationCounter,
appnLsInXidFrames AppnLinkStationCounter,
appnLsInMsgFrames AppnLinkStationCounter,
appnLsOutXidBytes AppnLinkStationCounter,
appnLsOutMsgBytes AppnLinkStationCounter,
appnLsOutXidFrames AppnLinkStationCounter,
appnLsOutMsgFrames AppnLinkStationCounter,
-- propagation delay
appnLsEchoRsps AppnLinkStationCounter,
appnLsCurrentDelay Gauge32,
appnLsMaxDelay Gauge32,
appnLsMinDelay Gauge32,
appnLsMaxDelayTime DateAndTime,
-- XID Statistics
appnLsGoodXids AppnLinkStationCounter,
appnLsBadXids AppnLinkStationCounter,
-- DLC-specific
appnLsSpecific RowPointer,
appnLsActiveTime Unsigned32,
appnLsCurrentStateTime TimeTicks,
-- HPR-specific
appnLsHprSup INTEGER,
appnLsErrRecoSup TruthValue,
appnLsForAnrLabel OCTET STRING,
appnLsRevAnrLabel OCTET STRING,
appnLsCpCpNceId OCTET STRING,
appnLsRouteNceId OCTET STRING,
appnLsBfNceId OCTET STRING,
appnLsLocalAddr DisplayableDlcAddress,
appnLsRemoteAddr DisplayableDlcAddress,
appnLsRemoteLsName DisplayString,
appnLsCounterDisconTime TimeStamp,
appnLsMltgMember TruthValue
}
::= { appnLsEntry 1 }
SYNTAX INTEGER {
deactivate(1),
activate(2),
recycle(3),
ready(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Object by which a Management Station can activate, deactivate,
or recycle (i.e., cause to be deactivated and then immediately
reactivated) a link station, by setting the value to
activate(1), deactivate(2), or recycle(3), respectively. The
value ready(4) is returned on GET operations until a SET has
been processed; after that the value received on the most
recent SET is returned."
::= { appnLsEntry 2 }
SYNTAX INTEGER {
inactive(1),
sentConnectOut(2), -- pending active
pendXidExch(3), -- pending active
sendActAs(4), -- pending active
sendSetMode(5), -- pending active
otherPendingActive(6),-- pending active
active(7),
sentDeactAsOrd(8), -- pending inactive
sentDiscOrd(9), -- pending inactive
sentDiscImmed(10), -- pending inactive
otherPendingInact(11) -- pending inactive
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"State of this link station. The comments map these more
granular states to the 'traditional' four states for SNA
resources. Values (2) through (5) represent the normal
progression of states when a link station is being activated.
Value (6) represents some other state of a link station in
the process of being activated. Values (8) through (10)
represent different ways a link station can be deactivated.
Value (11) represents some other state of a link station in
the process of being deactivated."
::= { appnLsEntry 3 }
this link station. The name can be from one to ten characters."
::= { appnLsEntry 4 }
::= { appnLsEntry 5 }
::= { appnLsEntry 6 }
The value of this object is determined as follows:
::= { appnLsEntry 7 }
SYNTAX INTEGER {
networkNode(1),
endNode(2),
t21len(4),
unknown(255)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Node type of the adjacent node on this link:
networkNode(1) - APPN network node
endNode(2) - APPN end node
t21len(4) - LEN end node
unknown(255) - the agent does not know the node type
of the adjacent node
"
::= { appnLsEntry 8 }
::= { appnLsEntry 9 }
::= { appnLsEntry 10 }
"Indicates whether the link station is activatable on demand.
Such a link station is reported in the topology as active regardless of its actual state, so that it can be considered in route calculations. If the link station is inactive and is chosen for a route, it will be activated at that time."
::= { appnLsEntry 11 }
In general, migration nodes do not append their CP names on XID3. Such nodes: (1) will not support parallel TGs, (2) should be sent an ACTIVATE PHYSICAL UNIT (ACTPU), provided that the partner supports ACTPUs, and (3) should not be sent segmented BINDs. However, if this node receives an XID3 with an appended CP name, then the partner node will not be treated as a migration node.
In the case of DYNAMIC TGs this object should be set to 'no'."
::= { appnLsEntry 12 }
::= { appnLsEntry 13 }
::= { appnLsEntry 14 }
When the link state (returned by the appnLsOperState object) is inactive or pending active, the value configured at this node is returned. When the link state is active, the value that was negotiated for it is returned. This negotiated value is the smaller of the value configured at this node and the partner's maximum receive BTU length, received in XID."
::= { appnLsEntry 15 }
::= { appnLsEntry 16 }
::= { appnLsEntry 17 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of XID frames received."
::= { appnLsEntry 18 }
::= { appnLsEntry 19 }
::= { appnLsEntry 20 }
::= { appnLsEntry 21 }
::= { appnLsEntry 22 }
::= { appnLsEntry 23 }
::= { appnLsEntry 24 }
::= { appnLsEntry 25 }
This time is represented in milliseconds .
The value 0 is returned if no test signal has been sent and returned."
::= { appnLsEntry 26 }
The value 0 is returned if no test signal has been sent and returned."
::= { appnLsEntry 27 }
The value 00000000 is returned if no test signal has been sent and returned."
::= { appnLsEntry 28 }
::= { appnLsEntry 29 }
::= { appnLsEntry 30 }
If the agent is unable to identify such an object, the value 0.0 is returned."
::= { appnLsEntry 31 }
::= { appnLsEntry 32 }
the link station has been in its current state."
::= { appnLsEntry 33 }
SYNTAX INTEGER {
noHprSupport(1),
hprBaseOnly(2),
rtpTower(3),
controlFlowsOverRtpTower(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the level of high performance routing (HPR) support
over this link:
noHprSupport(1) - no HPR support
hprBaseOnly(2) - HPR base (option set 1400)
supported
rtpTower(3) - HPR base and RTP tower
(option set 1401) supported
controlFlowsOverRtpTower(4) - HPR base, RTP tower, and
control flows over RTP
(option set 1402) supported
If the link is not active, the defined value is returned."
::= { appnLsEntry 34 }
::= { appnLsEntry 35 }
::= { appnLsEntry 36 }
::= { appnLsEntry 37 }
::= { appnLsEntry 38 }
::= { appnLsEntry 39 }
::= { appnLsEntry 40 }
::= { appnLsEntry 41 }
::= { appnLsEntry 42 }
::= { appnLsEntry 43 }
::= { appnLsEntry 44 }
currently the only active link in the TG."
::= { appnLsEntry 45 }
--********************************************************************
-- This table provides information about errors this node encountered
-- with connections to adjacent nodes. Entries are added for exceptional
-- conditions encountered establishing connections, and for exceptional
-- conditions that resulted in termination of a connection. It is an
-- implementation option when entries are removed from this table.
--********************************************************************
It is an implementation option when entries are removed from this table."
::= { appnLinkStationInformation 2 }
INDEX
{ appnLsStatusIndex }
::= { appnLsStatusTable 1 }
AppnLsStatusEntry ::= SEQUENCE {
appnLsStatusIndex INTEGER,
appnLsStatusTime DateAndTime,
appnLsStatusLsName DisplayString,
appnLsStatusCpName DisplayString,
appnLsStatusPartnerId SnaNodeIdentification,
appnLsStatusTgNum INTEGER,
appnLsStatusGeneralSense SnaSenseData,
appnLsStatusRetry TruthValue,
appnLsStatusEndSense SnaSenseData,
appnLsStatusXidLocalSense SnaSenseData,
appnLsStatusXidRemoteSense SnaSenseData,
appnLsStatusXidByteInError INTEGER,
appnLsStatusXidBitInError INTEGER,
appnLsStatusDlcType IANAifType,
appnLsStatusLocalAddr DisplayableDlcAddress,
appnLsStatusRemoteAddr DisplayableDlcAddress
}
::= { appnLsStatusEntry 1 }
::= { appnLsStatusEntry 2 }
::= { appnLsStatusEntry 3 }
The value of this object is determined as follows:
::= { appnLsStatusEntry 4 }
::= { appnLsStatusEntry 5 }
::= { appnLsStatusEntry 6 }
SYNTAX SnaSenseData
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The error sense data associated with the start sequence of
activation of a link up to the beginning of the XID sequence.
This is the sense data that came from Configuration Services whenever the link did not activate or when it went inactive."
::= { appnLsStatusEntry 7 }
::= { appnLsStatusEntry 8 }
This is the sense data that came from the DLC layer."
::= { appnLsStatusEntry 9 }
This is the sense data that came from the local node (this node) when it built the XID Negotiation Error control vector (cv22) to send to the remote node."
::= { appnLsStatusEntry 10 }
SYNTAX SnaSenseData
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The sense data the adjacent node returned to this node
indicating the reason the XID was rejected.
This is the sense data that came from the remote node in the XID Negotiation Error control vector (cv22) it sent to the local node (this node)."
::= { appnLsStatusEntry 11 }
For values in the range 0-65535, this object corresponds to bytes 2-3 of the XID Negotiation (X'22') control vector."
::= { appnLsStatusEntry 12 }
For values in the range 0-7, this object corresponds to byte 4 of the XID Negotiation (X'22') control vector."
::= { appnLsStatusEntry 13 }
::= { appnLsStatusEntry 14 }
::= { appnLsStatusEntry 15 }
::= { appnLsStatusEntry 16 }
-- *********************************************************************
-- APPN Virtual Routing Node Information
-- This section provides information relating a virtual routing node to
-- an APPN port.
-- *********************************************************************
::= { appnVrnInfo 1 }
INDEX
{ appnVrnName, appnVrnTgNum, appnVrnPortName }
::= { appnVrnTable 1 }
AppnVrnEntry ::= SEQUENCE {
appnVrnName SnaControlPointName,
appnVrnTgNum INTEGER,
appnVrnPortName DisplayString
}
::= { appnVrnEntry 1 }
::= { appnVrnEntry 2 }
::= { appnVrnEntry 3 }
-- ************** The APPN Topology Group ******************************
appnNn OBJECT IDENTIFIER ::= { appnObjects 2 }
appnNnTopo OBJECT IDENTIFIER ::= { appnNn 1 }
appnNnTopology OBJECT IDENTIFIER ::= { appnNn 2 }
-- This group is used to represent the entire APPN network-node topology
-- including network nodes, virtual routing nodes and all TGs associated
-- with these nodes, including intersubnetwork TGs (ISTGs) and branch TGs.
--
-- Network nodes
-- The APPN topology database consists of information about every APPN
-- network node in this network node's topology subnetwork. This
-- information is learned over time as each network node exchanges
-- topology information with the network nodes adjacent to it. The
-- database consists of information about each node, and information
-- about all of the transmission groups used by these nodes.
--
-- Virtual routing nodes
-- Information about virtual routing nodes (representing connection
-- networks) is treated in the same way as information about network
-- nodes, and is replicated at each network node. The FRSN, node name,
-- and node type are the only meaningful fields for a virtual routing
-- node. The other node objects return unspecified values. Each
-- node that has defined a TG with this virtual routing node as the
-- destination also defines a TG on this virtual routing node. There
-- is a TG record for each node that uses this virtual routing node.
--
-- The APPN node table represents node information from the APPN topology
-- database, with the FRSN and APPN fully qualified CP name serving as
-- the index. The FRSN is the agent's relative time stamp of an update
-- to the network topology database. After collecting the entire database
-- once, a management application can issue GET NEXT commands starting
-- from the last rows it has retrieved from the appnNnTopologyFRTable and
-- from the appnNnTgTopologyFRTable. When the response to either of these
-- GET NEXT commands returns another row of its respective table, this
-- indicates a change to the agent's topology database. The management
-- application can then retrieve only the updates to the table, using
-- GET NEXT commands starting from the last retrieved node or TG entry.
--
-- The format of the actual APPN topology database is as follows:
--
-- Node table (entry for each node in network)
-- TG table (entry for each TG owned by node)
--
-- Due to SNMP's ASN.1 limitations, we cannot represent the TG table
-- within the node table in this way. We define separate tables for
-- nodes and TGs, adding the node name to each TG entry to provide a
-- means of correlating the TG with its originating node.
database. It is an implementation choice whether to count only network-node entries, or to count all node entries. If the number of node entries exceeds this value, APPN will issue an Alert and the node can no longer participate as a network node. The value 0 indicates that the local node has no defined limit, and the number of node entries is bounded only by memory."
::= { appnNnTopo 1 }
::= { appnNnTopo 2 }
::= { appnNnTopo 3 }
::= { appnNnTopo 4 }
SYNTAX AppnNodeCounter
UNITS "TDU wars"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of TDU wars detected by this node since its last
initialization."
::= { appnNnTopo 5 }
-- APPN network node topology table (using FRSN and name as index)
-- This table describes every APPN network node and virtual routing node
-- represented in this node's topology database.
::= { appnNnTopology 3 }
INDEX
{appnNnNodeFRFrsn,
appnNnNodeFRName}
::= { appnNnTopologyFRTable 1 }
AppnNnTopologyFREntry ::= SEQUENCE {
appnNnNodeFRFrsn Unsigned32,
appnNnNodeFRName SnaControlPointName,
appnNnNodeFREntryTimeLeft AppnTopologyEntryTimeLeft,
appnNnNodeFRType INTEGER,
appnNnNodeFRRsn Unsigned32,
appnNnNodeFRRouteAddResist INTEGER,
appnNnNodeFRCongested TruthValue,
appnNnNodeFRIsrDepleted TruthValue,
appnNnNodeFRQuiescing TruthValue,
appnNnNodeFRGateway TruthValue,
appnNnNodeFRCentralDirectory TruthValue,
appnNnNodeFRIsr TruthValue,
appnNnNodeFRGarbageCollect TruthValue,
appnNnNodeFRHprSupport INTEGER,
appnNnNodeFRPeriBorderSup TruthValue,
appnNnNodeFRInterchangeSup TruthValue,
appnNnNodeFRExteBorderSup TruthValue,
appnNnNodeFRBranchAwareness TruthValue
}
::= { appnNnTopologyFREntry 1 }
::= { appnNnTopologyFREntry 2 }
::= { appnNnTopologyFREntry 3 }
SYNTAX INTEGER {
networkNode(1),
virtualRoutingNode(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Type of APPN node."
::= { appnNnTopologyFREntry 4 }
This object corresponds to the numeric value in cv4580, bytes 2-5."
::= { appnNnTopologyFREntry 5 }
This administratively assigned value indicates the relative desirability of using this node for intermediate session traffic. The value, which can be any integer 0-255, is used in route computation. The lower the value, the more desirable the node is for intermediate routing.
This object corresponds to cv4580, byte 6."
::= { appnNnTopologyFREntry 6 }
STATUS current
DESCRIPTION
"Indicates whether this node is congested. This node is not be
included in route selection by other nodes when this congestion
exists.
This object corresponds to cv4580, byte 7, bit 0."
::= { appnNnTopologyFREntry 7 }
This object corresponds to cv4580, byte 7, bit 1."
::= { appnNnTopologyFREntry 8 }
This object corresponds to cv4580, byte 7, bit 5."
::= { appnNnTopologyFREntry 9 }
This object corresponds to cv4580, byte 8, bit 0."
::= { appnNnTopologyFREntry 10 }
This object corresponds to cv4580, byte 8, bit 1."
::= { appnNnTopologyFREntry 11 }
This object corresponds to cv4580, byte 8, bit 2."
::= { appnNnTopologyFREntry 12 }
This object corresponds to cv4580, byte 7, bit 3."
::= { appnNnTopologyFREntry 13 }
SYNTAX INTEGER {
noHprSupport(1),
hprBaseOnly(2),
rtpTower(3),
controlFlowsOverRtpTower(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the node's level of support for high-performance routing (HPR):
noHprSupport(1) - no HPR support
hprBaseOnly(2) - HPR base (option set 1400)
supported
rtpTower(3) - HPR base and RTP tower
(option set 1401) supported
controlFlowsOverRtpTower(4) - HPR base, RTP tower, and
control flows over RTP
(option set 1402) supported
This object corresponds to cv4580, byte 9, bits 3-4."
::= { appnNnTopologyFREntry 14 }
This object corresponds to cv4580, byte 9, bit 0."
::= { appnNnTopologyFREntry 15 }
This object corresponds to cv4580, byte 9, bit 1."
::= { appnNnTopologyFREntry 16 }
This object corresponds to cv4580, byte 9, bit 2."
::= { appnNnTopologyFREntry 17 }
This object corresponds to cv4580, byte 8, bit 4."
::= { appnNnTopologyFREntry 18 }
--APPN transmission group (TG) table
-- This table describes the TGs associated with all the APPN network
-- nodes known to this node. The originating (owning) node for each
-- TG is repeated here to provide a means of correlating the TGs with
-- the nodes.
::= { appnNnTopology 4 }
INDEX
{appnNnTgFRFrsn,
appnNnTgFROwner,
appnNnTgFRDest,
appnNnTgFRNum}
::= { appnNnTgTopologyFRTable 1 }
AppnNnTgTopologyFREntry ::= SEQUENCE {
appnNnTgFRFrsn Unsigned32,
appnNnTgFROwner SnaControlPointName,
appnNnTgFRDest SnaControlPointName,
appnNnTgFRNum INTEGER,
appnNnTgFREntryTimeLeft AppnTopologyEntryTimeLeft,
appnNnTgFRDestVirtual TruthValue,
appnNnTgFRDlcData AppnTgDlcData,
appnNnTgFRRsn Unsigned32,
appnNnTgFROperational TruthValue,
appnNnTgFRQuiescing TruthValue,
appnNnTgFRCpCpSession INTEGER,
appnNnTgFREffCap AppnTgEffectiveCapacity,
appnNnTgFRConnCost INTEGER,
appnNnTgFRByteCost INTEGER,
appnNnTgFRSecurity AppnTgSecurity,
appnNnTgFRDelay AppnTgDelay,
appnNnTgFRUsr1 INTEGER,
appnNnTgFRUsr2 INTEGER,
appnNnTgFRUsr3 INTEGER,
appnNnTgFRGarbageCollect TruthValue,
appnNnTgFRSubareaNum Unsigned32,
appnNnTgFRHprSup TruthValue,
appnNnTgFRDestHprTrans TruthValue,
appnNnTgFRTypeIndicator INTEGER,
appnNnTgFRIntersubnet TruthValue,
appnNnTgFRMltgLinkType TruthValue,
appnNnTgFRBranchTg TruthValue
}
::= { appnNnTgTopologyFREntry 1 }
::= { appnNnTgTopologyFREntry 2 }
::= { appnNnTgTopologyFREntry 3 }
::= { appnNnTgTopologyFREntry 4 }
::= { appnNnTgTopologyFREntry 5 }
::= { appnNnTgTopologyFREntry 6 }
::= { appnNnTgTopologyFREntry 7 }
This object corresponds to the numeric value in cv47, bytes 2-5"
::= { appnNnTgTopologyFREntry 8 }
This object corresponds to cv47, byte 6, bit 0."
::= { appnNnTgTopologyFREntry 9 }
If the TG owner is either an extended border node or a branch-aware network node (indicated, respectively, by the appnNnNodeFRExteBorderSup and appnNnNodeFRBranchAwareness objects in the corresponding appnNnTopologyFREntry), then this indicator is artificially set to TRUE in the APPN
topology database, to remove the TG from other nodes'
route calculations. A management application can
determine whether the TG is actually quiescing by
examining its appnLocalTgQuiescing object at the TG owner.
This object corresponds to cv47, byte 6, bit 2."
::= { appnNnTgTopologyFREntry 10 }
SYNTAX INTEGER {
supportedUnknownStatus(1),
supportedActive(2),
notSupported(3),
supportedNotActive(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether CP-CP sessions are supported on this TG, and
whether the TG owner's contention-winner session is active on
this TG. Some nodes in the network are not able to
differentiate support and status of CP-CP sessions, and thus
may report the 'supportedUnknownStatus' value.
This object corresponds to cv47, byte 6, bits 3-4."
::= { appnNnTgTopologyFREntry 11