|
Network Working Group Request for Comments: 2155 Category: Standards Track |
B. Clouston Cisco Systems B. Moore IBM Corporation June 1997 |
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.
1. Introduction
2. The SNMPv2 Network Management Framework
3. Overview
3.1 APPN MIB structure
4. Definitions
5. Acknowledgments
6. References
7. Security Considerations
8. Author's Addresses
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.
The SNMP Network Management Framework consists of several components. For the purpose of this specification, the applicable components of the Framework are the SMI and related documents [1, 2, 3], which define the mechanisms used for describing and naming objects for the purpose of management.
The Framework permits new objects to be defined for the purpose of experimentation and evaluation.
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 [7] and the SNA NAU MIB [8] for management of these sessions. See also the DLUR MIB[9], and the HPR MIB[10] 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. End nodes (ENs) 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[11], the SNADLC LLC MIB[12], and the DLSw MIB[13]. 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. 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 from NNs to ENs are kept in a local topology database. Local topology information is shared with other NNs only during the session establishment process, to give the NN responsible for route calculation the necessary information for end-to- end route calculation.
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 [4], [5], [6], and [14].
Highlights of the management functions supported by the APPN MIB module include the following:
This MIB module does not support:
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, including its 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
experimental, Counter32, Gauge32, Integer32, 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
800 Park Offices Drive
RHJA/664
Tel: 1 919 254 4436
E-mail: remoore@ralvm6.vnet.ibm.com
"
DESCRIPTION
"This is the MIB module for objects used to
manage network devices with APPN capabilities."
::= { 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, or an LEN node. -- The first section applies to all three node types.
-- The second section applies only to APPN network nodes.
-- The third section applies only to APPN end nodes and to LEN nodes.
-- The fourth section applies to all three node types.
-- The fifth section applies to all three node types.
-- The sixth section applies only to APPN network nodes. -- APPN General Information
-- This section applies to both APPN network and end nodes, and to
-- LEN end nodes.
::= { appnGeneralInfoAndCaps 1 }
::= { appnGeneralInfoAndCaps 2 }
::= { 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"
::= { 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 }
re-initialized."
::= { appnGeneralInfoAndCaps 12 }
::= { appnGeneralInfoAndCaps 13 }
::= { appnGeneralInfoAndCaps 14 }
::= { appnGeneralInfoAndCaps 15 }
::= { appnGeneralInfoAndCaps 16 }
-- *********************************************************************
-- 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 }
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 }
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
"Indicates whether this end node supports mode name to COS name mapping."
::= { appnEnUniqueCaps 1 }
::= { appnEnUniqueCaps 2 }
::= { appnEnUniqueCaps 3 }
-- *********************************************************************
-- APPN Port information
--
::= { appnPortInformation 1 }
STATUS current
DESCRIPTION
"The port name is used as the index to this table."
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
}
::= { 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 }
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether the node supports negotiable link stations
for this port."
::= { appnPortEntry 8 }
::= { appnPortEntry 9 }
This object corresponds to bytes 21-22 of XID3."
::= { appnPortEntry 10 }
::= { appnPortEntry 11 }
DESCRIPTION
"The total number of successful XID exchanges that have
occurred on all defined link stations on this port since the
last time this port was started."
::= { appnPortEntry 12 }
::= { appnPortEntry 13 }
::= { appnPortEntry 14 }
::= { appnPortEntry 15 }
"Identifies the object, e.g., one in a DLC-specific MIB, that can provide additional information related to this port. 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
--
::= { 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
}
::= { 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 }
::= { appnLsEntry 4 }
::= { appnLsEntry 5 }
DESCRIPTION
"Identifies whether this is a dynamic link station. Dynamic
link stations are created when links that have not been locally
defined are established by adjacent nodes."
::= { 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 }
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 }
::= { appnLsEntry 18 }
::= { appnLsEntry 19 }
UNITS "bytes"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of XID bytes sent. All of the bytes in the SNA basic
transmission unit (BTU), i.e., all of the bytes in the DLC XID
Information Field, are counted."
::= { appnLsEntry 20 }
::= { appnLsEntry 21 }
::= { appnLsEntry 22 }
::= { appnLsEntry 23 }
"Number of echo responses returned from adjacent link station. A response should be returned for each test frame sent by this node. Test frames are sent to adjacent nodes periodically to verify connectivity and to measure the actual round trip time, that is, the time interval from when the test frame is sent until when the response is received."
::= { appnLsEntry 24 }
::= { appnLsEntry 25 }
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 }
"Identifies the object, e.g., one in a DLC-specific MIB, that can provide additional information related to this link station.
If the agent is unable to identify such an object, the value 0.0 is returned."
::= { appnLsEntry 31 }
::= { appnLsEntry 32 }
::= { 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 }
DESCRIPTION
"The network connection endpoint identifier (NCE ID) for CP-CP
sessions if this node supports the HPR transport tower, a
zero-length string if the value is unknown or not meaningful
for this node."
::= { appnLsEntry 38 }
::= { appnLsEntry 39 }
::= { appnLsEntry 40 }
::= { appnLsEntry 41 }
::= { appnLsEntry 42 }
::= { appnLsEntry 43 }
::= { appnLsEntry 44 }
--********************************************************************
-- This table provides information about errors this node encountered
-- with connections to adjacent nodes. Entries are added for exceptional
-- conditions encountered establishing connections and exceptional
-- conditions that resulted in termination of a connection. It is an
-- implementation option how many entries to keep in this table, and
-- how long to retain any individual entry.
--********************************************************************
::= { appnLinkStationInformation 2 }
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table is indexed by the LsStatusIndex, which is an
integer that is continuously updated until it eventually
wraps."
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 }
"Time when the exception condition occurred. This time can be used to identify when this event occurred in relation to other events in the APPN node, for example, the time at which an APPC session was either terminated or failed to be established. This latter time is available in the appcHistSessTime object in the APPC MIB."
::= { appnLsStatusEntry 2 }
::= { appnLsStatusEntry 3 }
The value of this object is determined as follows:
::= { appnLsStatusEntry 4 }
received from the partner. If this value is not available, then the characters '00000000' are returned."
::= { appnLsStatusEntry 5 }
::= { appnLsStatusEntry 6 }
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 }
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 }
"This object identifies the actual bit in error (0 through 7) within the errored byte of the XID. The value 8 indicates that this object has no meaning.
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
--
::= { appnVrnInfo 1 }
INDEX
{ appnVrnName, appnVrnTgNum, appnVrnPortName }
::= { appnVrnTable 1 }
AppnVrnEntry ::= SEQUENCE {
appnVrnName SnaControlPointName,
appnVrnTgNum INTEGER,
appnVrnPortName DisplayString
}
::= { appnVrnEntry 1 }
::= { appnVrnEntry 2 }
DESCRIPTION
"The name of the port this virtual routing node definition is
defined to."
::= { 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.
--
-- 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 CP fully qualified 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.
::= { appnNnTopo 1 }
::= { appnNnTopo 2 }
topology database since the node was last re-initialized."
::= { appnNnTopo 3 }
::= { appnNnTopo 4 }
::= { 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 }
DESCRIPTION
"The FRSN and the fully qualified node name are used to index
this table."
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
}
::= { appnNnTopologyFREntry 1 }
STATUS current
DESCRIPTION
"Administratively assigned network name that is locally defined
at each network node."
::= { 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 }
"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."
::= { appnNnTopologyFREntry 6 }
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 }
--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
}
::= { appnNnTgTopologyFREntry 1 }
::= { appnNnTgTopologyFREntry 2 }
::= { appnNnTgTopologyFREntry 3 }
::= { appnNnTgTopologyFREntry 4 }
::= { appnNnTgTopologyFREntry 5 }
"Indicates whether the destination node is a virtual routing node."
::= { 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 }
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 }
::= { appnNnTgTopologyFREntry 12 }
This is an administratively assigned value representing the relative cost per unit of time to use this TG. Range is from 0, which means no cost, to 255, which indicates maximum cost.
This object corresponds to cv47, byte 13."
::= { appnNnTgTopologyFREntry 13 }
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Cost per byte transmitted.
This is an administratively assigned value representing the relative cost of transmitting a byte over this TG. Range is from 0, which means no cost, to 255, which indicates maximum cost.
This object corresponds to cv47, byte 14."
::= { appnNnTgTopologyFREntry 14 }
This object corresponds to cv47, byte 16."
::= { appnNnTgTopologyFREntry 15 }
This object corresponds to cv47, byte 17."
::= { appnNnTgTopologyFREntry 16 }
This object corresponds to cv47, byte 19."
::= { appnNnTgTopologyFREntry 17 }
This object corresponds to cv47, byte 20."
::= { appnNnTgTopologyFREntry 18 }
This object corresponds to cv47, byte 21."
::= { appnNnTgTopologyFREntry 19 }
This object corresponds to cv47, byte 6, bit 1."
::= { appnNnTgTopologyFREntry 20 }
This object corresponds to cv4680, bytes m+2 through m+5."
::= { appnNnTgTopologyFREntry 21 }
This object corresponds to cv4680, byte m+1, bit 2."
::= { appnNnTgTopologyFREntry 22 }
This object corresponds to cv4680, byte m+1, bit 7."
::= { appnNnTgTopologyFREntry 23 }
SYNTAX INTEGER {
unknown(1),
appnOrBfTg(2),
interchangeTg(3),
virtualRouteTg(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the type of the TG.
This object corresponds to cv4680, byte m+1, bits 3-4."
::= { appnNnTgTopologyFREntry 24 }
This object corresponds to cv4680, byte m+1, bit 5."
::= { appnNnTgTopologyFREntry 25 }
-- ************** The APPN Local Topology Group ************************
-- This MIB Group represents the local topology maintained in
-- both APPN end nodes and network nodes. It consists of two
-- tables:
-- - a table containing information about all of the TGs owned
-- by this node, which is implemented by all node types.
-- - a table containing all of the information known to this node
-- about the TGs owned by its end nodes, which is implemented only
-- by network nodes.
appnLocalTopology OBJECT IDENTIFIER ::= { appnObjects 3 }
-- APPN Local Transmission Group (TG) table
-- This table describes the TGs associated with this node only.
::= { appnLocalTopology 1 }
INDEX
{appnLocalTgDest,
appnLocalTgNum}
::= { appnLocalTgTable 1 }
AppnLocalTgEntry ::= SEQUENCE {
appnLocalTgDest SnaControlPointName,
appnLocalTgNum INTEGER,
appnLocalTgDestVirtual TruthValue,
appnLocalTgDlcData AppnTgDlcData,
appnLocalTgPortName DisplayString,
appnLocalTgQuiescing TruthValue,
appnLocalTgOperational TruthValue,
appnLocalTgCpCpSession INTEGER,
appnLocalTgEffCap AppnTgEffectiveCapacity,
appnLocalTgConnCost INTEGER,
appnLocalTgByteCost INTEGER,
appnLocalTgSecurity AppnTgSecurity,
appnLocalTgDelay AppnTgDelay,
appnLocalTgUsr1 INTEGER,
appnLocalTgUsr2 INTEGER,
appnLocalTgUsr3 INTEGER,
appnLocalTgHprSup INTEGER,
appnLocalTgIntersubnet TruthValue
}
::= { appnLocalTgEntry 1 }
::= { appnLocalTgEntry 2 }
::= { appnLocalTgEntry 3 }
::= { appnLocalTgEntry 4 }
::= { appnLocalTgEntry 5 }
::= { appnLocalTgEntry 6 }
::= { appnLocalTgEntry 7 }
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."
::= { appnLocalTgEntry 8 }
::= { appnLocalTgEntry 9 }
::= { appnLocalTgEntry 10 }
::= { appnLocalTgEntry 11 }
::= { appnLocalTgEntry 12 }
::= { appnLocalTgEntry 13 }
::= { appnLocalTgEntry 14 }
::= { appnLocalTgEntry 15 }
::= { appnLocalTgEntry 16 }
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 TG :
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"
::= { appnLocalTgEntry 17 }
::= { appnLocalTgEntry 18 }
-- APPN Local End Node Transmission Group (TG) table
-- This table describes the TGs associated with all of the end nodes
-- known to this node.
::= { appnLocalTopology 2 }
"This table requires multiple indexes to uniquely identify each TG. They are originating CPname, destination CPname, and the TG number."
INDEX
{appnLocalEnTgOrigin,
appnLocalEnTgDest,
appnLocalEnTgNum}
::= { appnLocalEnTgTable 1 }
AppnLocalEnTgEntry ::= SEQUENCE {
appnLocalEnTgOrigin SnaControlPointName,
appnLocalEnTgDest SnaControlPointName,
appnLocalEnTgNum INTEGER,
appnLocalEnTgEntryTimeLeft AppnTopologyEntryTimeLeft,
appnLocalEnTgDestVirtual TruthValue,
appnLocalEnTgDlcData AppnTgDlcData,
appnLocalEnTgOperational TruthValue,
appnLocalEnTgCpCpSession INTEGER,
appnLocalEnTgEffCap AppnTgEffectiveCapacity,
appnLocalEnTgConnCost INTEGER,
appnLocalEnTgByteCost INTEGER,
appnLocalEnTgSecurity AppnTgSecurity,
appnLocalEnTgDelay AppnTgDelay,
appnLocalEnTgUsr1 INTEGER,
appnLocalEnTgUsr2 INTEGER,
appnLocalEnTgUsr3 INTEGER
}
::= { appnLocalEnTgEntry 1 }
this TG. This is the fully qualified name of a network node, end node, LEN node, or virtual routing node."
::= { appnLocalEnTgEntry 2 }
::= { appnLocalEnTgEntry 3 }
::= { appnLocalEnTgEntry 4 }
::= { appnLocalEnTgEntry 5 }
::= { appnLocalEnTgEntry 6 }
"Indicates whether the transmission group is operational."
::= { appnLocalEnTgEntry 7 }
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."
::= { appnLocalEnTgEntry 8 }
::= { appnLocalEnTgEntry 9 }
::= { appnLocalEnTgEntry 10 }
Range is from 0, which means no cost, to 255."
::= { appnLocalEnTgEntry 11 }
::= { appnLocalEnTgEntry 12 }
::= { appnLocalEnTgEntry 13 }
::= { appnLocalEnTgEntry 14 }
::= { appnLocalEnTgEntry 15 }
an administratively assigned value associated with the TG."
::= { appnLocalEnTgEntry 16 }
-- ************** The APPN Directory Group *****************************
appnDir OBJECT IDENTIFIER ::= { appnObjects 4 }
appnDirPerf OBJECT IDENTIFIER ::= { appnDir 1 }
-- The APPN Directory Group
-- The APPN Directory Database
-- Each APPN network node maintains directories containing information on
-- which LUs (applications) are available and where they are located.
-- LUs can be located in an APPN network node or in any of its attached
-- end nodes.
::= { appnDirPerf 1 }
::= { appnDirPerf 2 }
::= { appnDirPerf 3 }
::= { appnDirPerf 4 }
::= { appnDirPerf 5 }
::= { appnDirPerf 6 }
::= { appnDirPerf 7 }
DESCRIPTION
"Number of broadcast Locates sent since the node was last
re-initialized."
::= { appnDirPerf 8 }
::= { appnDirPerf 9 }
::= { appnDirPerf 10 }
::= { appnDirPerf 11 }
--APPN Directory table
-- This table contains information about all known LUs.
DESCRIPTION
"Table containing information about all known LUs."
::= { appnDir 2 }
INDEX
{appnDirLuName}
::= { appnDirTable 1 }
AppnDirEntry ::= SEQUENCE {
appnDirLuName DisplayString,
appnDirNnServerName SnaControlPointName,
appnDirLuOwnerName SnaControlPointName,
appnDirLuLocation INTEGER,
appnDirType INTEGER
}
- Explicit entries do not contain the character '*'.
- Partial wildcard entries have the form 'ccc*', where
'ccc' represents one to sixteen characters in a
legal SNA LuName.
- A full wildcard entry consists of the single
character '*'"
::= { appnDirEntry 1 }
server. For unassociated end node entries, a zero-length string is returned."
::= { appnDirEntry 2 }
::= { appnDirEntry 3 }
SYNTAX INTEGER {
local(1), --Local
domain(2), --Domain
xdomain(3) --Cross Domain
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Specifies the location of the LU with respect to the local
node."
::= { appnDirEntry 4 }
SYNTAX INTEGER {
home(1), --defined as home entry
cache(2), --learned over time
registered(3) --registered by end node
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Directory types are:
1 - Home
The LU is in the domain of the local node, and the LU
information has been configured at the local node.
2 - Cache
The LU has previously been located by a broadcast
search, and the location information has been saved.
3 - Registered
The LU is at an end node that is in the domain
of the local network node. Registered entries
are registered by the served end node."
::= { appnDirEntry 5 }
-- ************** The APPN Class of Service Group **********************
appnCos OBJECT IDENTIFIER ::= { appnObjects 5 }
-- The APPN Class of Service (COS)
-- Class of Service is a means of expressing the quality of routes and
-- the transmission priority of traffic that flows on these routes.
-- The quality of routes is specified by two tables, a COS weight table
-- for TGs and a COS weight table for nodes. Values in these COS tables
-- are administratively assigned at each APPN node, with seven default
-- tables specified by the APPN architecture.
-- *********************************************************************
::= { appnCos 1 }
INDEX
{appnCosModeName}
::= { appnCosModeTable 1 }
AppnCosModeEntry ::= SEQUENCE {
appnCosModeName SnaModeName,
appnCosModeCosName SnaClassOfServiceName
}
::= { appnCosModeEntry 1 }
::= { appnCosModeEntry 2 }
-- *********************************************************************
::= { appnCos 2 }
INDEX
{appnCosName}
::= { appnCosNameTable 1 }
AppnCosNameEntry ::= SEQUENCE {
appnCosName SnaClassOfServiceName,
appnCosTransPriority INTEGER
}
::= { appnCosNameEntry 1 }
SYNTAX INTEGER {
low(1), --X'01'
medium(2), --X'02'
high(3), --X'03'
network(4) --X'04'
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Transmission priority for this class of service:
low(1) - (X'01'): low priority
medium(2) - (X'02'): medium priority
high(3) - (X'03'): high priority
network(4) - (X'04'): network priority"
::= { appnCosNameEntry 2 }
-- *********************************************************************
::= { appnCos 3 }
"A node entry for a given class of service."
INDEX
{appnCosNodeRowName,
appnCosNodeRowIndex}
::= { appnCosNodeRowTable 1 }
AppnCosNodeRowEntry ::= SEQUENCE {
appnCosNodeRowName SnaClassOfServiceName,
appnCosNodeRowIndex INTEGER,
appnCosNodeRowWgt DisplayString,
appnCosNodeRowResistMin INTEGER,
appnCosNodeRowResistMax INTEGER,
appnCosNodeRowMinCongestAllow INTEGER,
appnCosNodeRowMaxCongestAllow INTEGER
}
::= { appnCosNodeRowEntry 1 }
For each class of service, this subindex orders rows in the appnCosNodeRowTable in the same order as that used for route calculation in the APPN node."
::= { appnCosNodeRowEntry 2 }
specified by this node row.
This value can either be a character representation of an integer, or a formula for calculating the weight."
::= { appnCosNodeRowEntry 3 }
::= { appnCosNodeRowEntry 4 }
::= { appnCosNodeRowEntry 5 }
- (0,0): only low congestion is acceptable
- (0,1): either low or high congestion is acceptable
- (1,1): only high congestion is acceptable.
Note that the combination (1,0) is not defined, since it would identify a range whose lower bound was high congestion and whose upper bound was low congestion."
::= { appnCosNodeRowEntry 6 }
- (0,0): only low congestion is acceptable
- (0,1): either low or high congestion is acceptable
- (1,1): only high congestion is acceptable.
Note that the combination (1,0) is not defined, since it would identify a range whose lower bound was high congestion and whose upper bound was low congestion."
::= { appnCosNodeRowEntry 7 }
-- *********************************************************************
::= { appnCos 4 }
INDEX
{appnCosTgRowName,
appnCosTgRowIndex}
::= { appnCosTgRowTable 1 }
AppnCosTgRowEntry ::= SEQUENCE {
appnCosTgRowName SnaClassOfServiceName,
appnCosTgRowIndex INTEGER,
appnCosTgRowWgt DisplayString,
appnCosTgRowEffCapMin AppnTgEffectiveCapacity,
appnCosTgRowEffCapMax AppnTgEffectiveCapacity,
appnCosTgRowConnCostMin INTEGER,
appnCosTgRowConnCostMax INTEGER,
appnCosTgRowByteCostMin INTEGER,
appnCosTgRowByteCostMax INTEGER,
appnCosTgRowSecurityMin AppnTgSecurity,
appnCosTgRowSecurityMax AppnTgSecurity,
appnCosTgRowDelayMin AppnTgDelay,
appnCosTgRowDelayMax AppnTgDelay,
appnCosTgRowUsr1Min INTEGER,
appnCosTgRowUsr1Max INTEGER,
appnCosTgRowUsr2Min INTEGER,
appnCosTgRowUsr2Max INTEGER,
appnCosTgRowUsr3Min INTEGER,
appnCosTgRowUsr3Max INTEGER
}
::= { appnCosTgRowEntry 1 }
For each class of service, this subindex orders rows in the appnCosTgRowTable in the same order as that used for route calculation in the APPN node."
::= { appnCosTgRowEntry 2 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Weight to be associated with the TGs that fit the criteria
specified by this TG row.
This value can either be a character representation of an integer, or a formula for calculating the weight."
::= { appnCosTgRowEntry 3 }
::= { appnCosTgRowEntry 4 }
::= { appnCosTgRowEntry 5 }
Cost per connect time: a value representing the relative cost per unit of time to use this TG. Range is from 0, which means no cost, to 255."
::= { appnCosTgRowEntry 6 }
"Maximum acceptable cost per connect time for this class of service.
Cost per connect time: a value representing the relative cost per unit of time to use this TG. Range is from 0, which means no cost, to 255."
::= { appnCosTgRowEntry 7 }
Cost per byte transmitted: a value representing the relative cost per unit of time to use this TG. Range is from 0, which means no cost, to 255."
::= { appnCosTgRowEntry 8 }
Cost per byte transmitted: a value representing the relative cost of transmitting a byte over this TG. Range is from 0, which means no cost, to 255."
::= { appnCosTgRowEntry 9 }
::= { appnCosTgRowEntry 10 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Maximum acceptable security for this class of service."
::= { appnCosTgRowEntry 11 }
::= { appnCosTgRowEntry 12 }
::= { appnCosTgRowEntry 13 }
::= { appnCosTgRowEntry 14 }
::= { appnCosTgRowEntry 15 }
SYNTAX INTEGER (0..255)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Minimum acceptable value for this user-defined
characteristic."
::= { appnCosTgRowEntry 16 }
::= { appnCosTgRowEntry 17 }
::= { appnCosTgRowEntry 18 }
::= { appnCosTgRowEntry 19 }
-- *********************************************************************
-- Intermediate Session Information
-- *********************************************************************
appnSessIntermediate OBJECT IDENTIFIER ::= { appnObjects 6 }
-- *********************************************************************
-- Intermediate Session Information Global Objects
-- *********************************************************************
-- The following simple objects allow the collection of intermediate
-- session Information to be started and stopped.
-- *********************************************************************
appnIsInGlobal OBJECT IDENTIFIER ::= { appnSessIntermediate 1 }
SYNTAX INTEGER {
notActive(1),
active(2),
ready(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Object by which a Management Station can deactivate or
activate capture of intermediate-session counts and names, by
setting the value to notActive(1) or active(2), respectively.
The value ready(3) is returned on GET operations until a SET
has been processed; after that the value received on the most
recent SET is returned.
The counts referred to here are the eight objects in the
AppnIsInTable, from appnIsInP2SFmdPius through
appnIsInS2PNonFmdBytes. The names are the four objects in this
table, from appnIsInPriLuName through appnIsInCosName.
Setting this object to the following values has the following effects:
notActive(1) stop collecting count data. If a count is queried, it returns the value 0. Collection of names may, but need not be, disabled.
active(2) start collecting count data. If it is
supported, collection of names is enabled."
::= { appnIsInGlobal 1 }
SYNTAX INTEGER {
notActive(1),
active(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates whether or not the intermediate session counts
are active. The counts referred to here are the eight
objects in the AppnIsInTable, from appnIsInP2SFmdPius through
appnIsInS2PNonFmdBytes. These eight counts are of type Unsigned32 rather than Counter32 because when this object enters the notActive state, either because a Management Station has set appnInInGlobeCtrAdminStatus to notActive or because of a locally-initiated transition, the counts are all reset to 0.
The values for this object are:
notActive(1): collection of counts is not active; if it is queried, a count returns the value 0.
active(2): collection of counts is active."
::= { appnIsInGlobal 2 }
::= { appnIsInGlobal 3 }
SYNTAX INTEGER {
notActive(1),
active(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates the current route selection control vector (RSCV)
collection option in effect, and allows a Management Station to
change the option.
The values for this object are:
notActive(1): collection of route selection control vectors is not active.
active(2): collection of route selection control vectors
is active."
::= { appnIsInGlobal 4 }
::= { appnIsInGlobal 5 }
::= { appnIsInGlobal 6 }
::= { appnIsInGlobal 7 }
-- *********************************************************************
-- Intermediate Session Information Table
-- *********************************************************************
-- This table contains information on intermediate sessions
-- which are currently active.
-- *********************************************************************
"Intermediate Session Information Table"
::= { appnSessIntermediate 2 }
INDEX
{ appnIsInFqCpName,
appnIsInPcid }
::= { appnIsInTable 1 }
AppnIsInEntry ::= SEQUENCE {
appnIsInFqCpName SnaControlPointName,
appnIsInPcid OCTET STRING,
appnIsInSessState INTEGER,
appnIsInPriLuName DisplayString,
appnIsInSecLuName DisplayString,
appnIsInModeName SnaModeName,
appnIsInCosName SnaClassOfServiceName,
appnIsInTransPriority INTEGER,
appnIsInSessType INTEGER,
appnIsInSessUpTime TimeTicks,
appnIsInCtrUpTime TimeTicks,
appnIsInP2SFmdPius Unsigned32,
appnIsInS2PFmdPius Unsigned32,
appnIsInP2SNonFmdPius Unsigned32,
appnIsInS2PNonFmdPius Unsigned32,
appnIsInP2SFmdBytes Unsigned32,
appnIsInS2PFmdBytes Unsigned32,
appnIsInP2SNonFmdBytes Unsigned32,
appnIsInS2PNonFmdBytes Unsigned32,
appnIsInPsAdjCpName SnaControlPointName,
appnIsInPsAdjTgNum INTEGER,
appnIsInPsSendMaxBtuSize INTEGER,
appnIsInPsSendPacingType INTEGER,
appnIsInPsSendRpc Gauge32,
appnIsInPsSendNxWndwSize Gauge32,
appnIsInPsRecvPacingType INTEGER,
appnIsInPsRecvRpc Gauge32,
appnIsInPsRecvNxWndwSize Gauge32,
appnIsInSsAdjCpName SnaControlPointName,
appnIsInSsAdjTgNum INTEGER,
appnIsInSsSendMaxBtuSize INTEGER,
appnIsInSsSendPacingType INTEGER,
appnIsInSsSendRpc Gauge32,
appnIsInSsSendNxWndwSize Gauge32,
appnIsInSsRecvPacingType INTEGER,
appnIsInSsRecvRpc Gauge32,
appnIsInSsRecvNxWndwSize Gauge32,
appnIsInRouteInfo OCTET STRING,
appnIsInRtpNceId OCTET STRING,
appnIsInRtpTcid OCTET STRING
}
::= { appnIsInEntry 1 }
::= { appnIsInEntry 2 }
SYNTAX INTEGER {
inactive(1),
pendactive(2),
active(3),
pendinact(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Indicates the state of the session:
inactive(1) - session is inactive
pendactive(2) - session is pending active
active(3) - session is active
pendinact(4) - session is pending inactive
Active sessions can be deactivated by setting this object to inactive(1)."
::= { appnIsInEntry 3 }
::= { appnIsInEntry 4 }
::= { appnIsInEntry 5 }
::= { appnIsInEntry 6 }
SYNTAX SnaClassOfServiceName
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The Class of Service (COS) name used for this session."
::= { appnIsInEntry 7 }
SYNTAX INTEGER {
low(1), --X'01'
medium(2), --X'02'
high(3), --X'03'
network(4) --X'04'
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Transmission priority for this class of service. Values are:
low(1) - (X'01'): low priority
medium(2) - (X'02'): medium priority
high(3) - (X'03'): high priority
network(4) - (X'04'): network priority"
::= { appnIsInEntry 8 }
SYNTAX INTEGER {
unknown(1),
lu62(2),
lu0thru3(3),
lu62dlur(4),
lu0thru3dlur(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of intermediate session. Defined values are
unknown The session type is not known.
lu62 A session between LUs of type 6.2
(as indicated by the LU type in Bind)
lu0thru3 A session between LUs of type 0, 1, 2, or 3
(as indicated by the LU type in Bind)
lu62dlur A session between LUs of type 6.2
(as indicated by the LU type in Bind).
One of the LUs is a dependent LU supported
by the dependent LU requester (DLUR)
function at this node.
lu0thru3dlur A session between LUs of type 0, 1, 2, or 3 (as indicated by the LU type in Bind) One of the LUs is a dependent LU supported by the dependent LU requester (DLUR) function at this node."
::= { appnIsInEntry 9 }
::= { appnIsInEntry 10 }
::= { appnIsInEntry 11 }
::= { appnIsInEntry 12 }
UNITS "path information units (PIUs)"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Number of FMD PIUs sent from the Secondary LU to the Primary
LU since the counts were last activated."
::= { appnIsInEntry 13 }
::= { appnIsInEntry 14 }
::= { appnIsInEntry 15 }
::= { appnIsInEntry 16 }
"Number of FMD bytes sent from the Secondary LU to the Primary LU since the counts were last activated."
::= { appnIsInEntry 17 }
::= { appnIsInEntry 18 }
::= { appnIsInEntry 19 }
::= { appnIsInEntry 20 }
Values between 257 and 300 are available for other possible
TG 'stand-ins' that may be added to APPN in the future."
::= { appnIsInEntry 21 }
::= { appnIsInEntry 22 }
SYNTAX INTEGER {
fixed(1),
adaptive(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The primary stage type of pacing being used for sending data."
::= { appnIsInEntry 23 }
::= { appnIsInEntry 24 }
::= { appnIsInEntry 25 }
SYNTAX INTEGER {
fixed(1),
adaptive(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The primary stage type of pacing being used for receiving
data."
::= { appnIsInEntry 26 }
::= { appnIsInEntry 27 }
::= { appnIsInEntry 28 }
::= { appnIsInEntry 29 }
Values between 257 and 300 are available for other possible TG 'stand-ins' that may be added to APPN in the future."
::= { appnIsInEntry 30 }
::= { appnIsInEntry 31 }
SYNTAX INTEGER {
fixed(1),
adaptive(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The secondary stage type of pacing being used for sending
data."
::= { appnIsInEntry 32 }
::= { appnIsInEntry 33 }
::= { appnIsInEntry 34 }
SYNTAX INTEGER {
fixed(1),
adaptive(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The secondary stage type of pacing being used for receiving
data."
::= { appnIsInEntry 35 }
::= { appnIsInEntry 36 }
::= { appnIsInEntry 37 }
::= { appnIsInEntry 38 }
::= { appnIsInEntry 39 }
::= { appnIsInEntry 40 }
-- *********************************************************************
-- Intermediate Session RTP Table
-- *********************************************************************
-- This table contains information on intermediate sessions that are
-- being transported on Rapid Transport Protocol (RTP) connections by
-- High Performance Routing (HPR).
-- *********************************************************************
::= { appnSessIntermediate 3 }
INDEX
{ appnIsRtpNceId,
appnIsRtpTcid }
::= { appnIsRtpTable 1 }
AppnIsRtpEntry ::= SEQUENCE {
appnIsRtpNceId OCTET STRING,
appnIsRtpTcid OCTET STRING,
appnIsRtpSessions Gauge32
}
::= { appnIsRtpEntry 1 }
::= { appnIsRtpEntry 2 }
::= { appnIsRtpEntry 3 }
-- *********************************************************************
appnTraps OBJECT IDENTIFIER ::= { appnMIB 2 }
-- *********************************************************************
::= { appnTraps 1 }
::= { appnTraps 2 }
::= { appnTraps 3 }
-- *********************************************************************
-- Conformance information
-- *********************************************************************
appnConformance OBJECT IDENTIFIER ::= {appnMIB 3 }
appnCompliances OBJECT IDENTIFIER ::= {appnConformance 1 }
appnGroups OBJECT IDENTIFIER ::= {appnConformance 2 }
-- Compliance statements
implement the APPN MIB."
MODULE -- this module
-- Unconditionally mandatory groups
MANDATORY-GROUPS {
appnGeneralConfGroup,
appnPortConfGroup,
appnLinkConfGroup,
appnLocalTgConfGroup,
appnDirTableConfGroup
}
-- Conditionally mandatory groups
GROUP appnNnUniqueConfGroup
DESCRIPTION
"The appnNnUniqueConfGroup is mandatory only for
network nodes."
GROUP appnEnUniqueConfGroup
DESCRIPTION
"The appnEnUniqueConfGroup is mandatory only for end
nodes."
GROUP appnVrnConfGroup
DESCRIPTION
"The appnVrnConfGroup is mandatory only for network
nodes and end nodes that implement virtual routing
node support."
GROUP appnNnTopoConfGroup
DESCRIPTION
"The appnNnTopoConfGroup is mandatory only for
network nodes."
GROUP appnLocalEnTopoConfGroup
DESCRIPTION
"The appnLocalEnTopoConfGroup is mandatory only for
network nodes."
GROUP appnLocalDirPerfConfGroup
DESCRIPTION
"The appnLocalDirPerfConfGroup is mandatory only for
APPN network nodes and end nodes."
GROUP appnCosConfGroup
DESCRIPTION
"The appnCosConfGroup is mandatory only for APPN
network nodes and end nodes."
GROUP appnIntSessConfGroup
DESCRIPTION
"The appnIntSessConfGroup is mandatory only for
network nodes."
GROUP appnHprBaseConfGroup
DESCRIPTION
"The appnHprBaseConfGroup is mandatory only for nodes
that implement the HPR base (APPN option set 1400)."
GROUP appnHprRtpConfGroup
DESCRIPTION
"The appnHprRtpConfGroup is mandatory only for nodes
that implement the HPR RTP tower (APPN option set
1401)."
GROUP appnHprCtrlFlowsRtpConfGroup
DESCRIPTION
"The appnHprCtrlFlowsRtpConfGroup is mandatory only
for nodes that implement the HPR Control Flows over
RTP tower (APPN option set 1402)."
GROUP appnHprBfConfGroup
DESCRIPTION
"The appnHprBfConfGroup is mandatory only for nodes
that implement the APPN/HPR boundary function."
GROUP appnTrapConfGroup
DESCRIPTION
"Traps are optional for all nodes."
GROUP appnTrapNotifGroup
DESCRIPTION
"Traps are optional for all nodes."
::= {appnCompliances 1 }
-- Units of conformance
OBJECTS {
appnNodeCpName,
appnNodeMibVersion,
appnNodeId,
appnNodeType,
appnNodeUpTime,
appnNodeParallelTg,
appnNodeAdaptiveBindPacing,
appnNodeHprSupport,
appnNodeCounterDisconTime
}
STATUS current
DESCRIPTION
"A collection of objects providing the instrumentation of
APPN general information and capabilities."
::= { appnGroups 1 }
OBJECTS {
appnPortCommand,
appnPortOperState,
appnPortDlcType,
appnPortPortType,
appnPortSIMRIM,
appnPortLsRole,
appnPortNegotLs,
appnPortDynamicLinkSupport,
appnPortMaxRcvBtuSize,
appnPortMaxIframeWindow,
appnPortDefLsGoodXids,
appnPortDefLsBadXids,
appnPortDynLsGoodXids,
appnPortDynLsBadXids,
appnPortSpecific,
appnPortDlcLocalAddr,
appnPortCounterDisconTime
}
STATUS current
DESCRIPTION
"A collection of objects providing the instrumentation of
APPN port information."
::= { appnGroups 2 }
OBJECTS {
appnLsCommand,
appnLsOperState,
appnLsPortName,
appnLsDlcType,
appnLsDynamic,
appnLsAdjCpName,
appnLsAdjNodeType,
appnLsTgNum,
appnLsLimResource,
appnLsActOnDemand,
appnLsMigration,
appnLsPartnerNodeId,
appnLsCpCpSessionSupport,
appnLsMaxSendBtuSize,
appnLsInXidBytes,
appnLsInMsgBytes,
appnLsInXidFrames,
appnLsInMsgFrames,
appnLsOutXidBytes,
appnLsOutMsgBytes,
appnLsOutXidFrames,
appnLsOutMsgFrames,
appnLsEchoRsps,
appnLsCurrentDelay,
appnLsMaxDelay,
appnLsMinDelay,
appnLsMaxDelayTime,
appnLsGoodXids,
appnLsBadXids,
appnLsSpecific,
appnLsActiveTime,
appnLsCurrentStateTime,
appnLsHprSup,
appnLsLocalAddr,
appnLsRemoteAddr,
appnLsRemoteLsName,
appnLsStatusTime,
appnLsStatusLsName,
appnLsStatusCpName,
appnLsStatusPartnerId,
appnLsStatusTgNum,
appnLsStatusGeneralSense,
appnLsStatusRetry,
appnLsStatusEndSense,
appnLsStatusXidLocalSense,
appnLsStatusXidRemoteSense,
appnLsStatusXidByteInError,
appnLsStatusXidBitInError,
appnLsStatusDlcType,
appnLsStatusLocalAddr,
appnLsStatusRemoteAddr,
appnLsCounterDisconTime
}
STATUS current
DESCRIPTION
"A collection of objects providing the instrumentation of
APPN link information."
::= { appnGroups 3 }
OBJECTS {
appnLocalTgDestVirtual,
appnLocalTgDlcData,
appnLocalTgPortName,
appnLocalTgQuiescing,
appnLocalTgOperational,
appnLocalTgCpCpSession,
appnLocalTgEffCap,
appnLocalTgConnCost,
appnLocalTgByteCost,
appnLocalTgSecurity,
appnLocalTgDelay,
appnLocalTgUsr1,
appnLocalTgUsr2,
appnLocalTgUsr3,
appnLocalTgHprSup,
appnLocalTgIntersubnet
}
STATUS current
DESCRIPTION
"A collection of objects providing the instrumentation of
APPN local TG information."
::= { appnGroups 4 }
OBJECTS {
appnDirNnServerName,
appnDirLuOwnerName,
appnDirLuLocation,
appnDirType
}
STATUS current
DESCRIPTION
"A collection of objects providing the instrumentation of the
APPN directory database."
::= { appnGroups 5 }
OBJECTS {
appnNodeNnCentralDirectory,
appnNodeNnTreeCache,
appnNodeNnRouteAddResist,
appnNodeNnIsr,
appnNodeNnFrsn,
appnNodeNnPeriBorderSup,
appnNodeNnInterchangeSup,
appnNodeNnExteBorderSup,
appnNodeNnSafeStoreFreq,
appnNodeNnRsn,
appnNodeNnCongested,
appnNodeNnIsrDepleted,
appnNodeNnQuiescing,
appnNodeNnGateway
}
STATUS current
DESCRIPTION
"The appnNnUniqueConfGroup is mandatory only for network
nodes."
::= { appnGroups 6 }
OBJECTS {
appnNodeEnModeCosMap,
appnNodeEnNnServer,
appnNodeEnLuSearch
}
STATUS current
DESCRIPTION
"The appnEnUniqueConfGroup is mandatory only for end nodes."
::= { appnGroups 7 }
OBJECTS {
appnVrnPortName
}
STATUS current
DESCRIPTION
"The appnVrnConfGroup is mandatory only for APPN network
nodes and end nodes."
::= { appnGroups 8 }
OBJECTS {
appnNnTopoMaxNodes,
appnNnTopoCurNumNodes,
appnNnTopoNodePurges,
appnNnTopoTgPurges,
appnNnTopoTotalTduWars,
appnNnNodeFREntryTimeLeft,
appnNnNodeFRType,
appnNnNodeFRRsn,
appnNnNodeFRRouteAddResist,
appnNnNodeFRCongested,
appnNnNodeFRIsrDepleted,
appnNnNodeFRQuiescing,
appnNnNodeFRGateway,
appnNnNodeFRCentralDirectory,
appnNnNodeFRIsr,
appnNnNodeFRGarbageCollect,
appnNnNodeFRHprSupport,
appnNnNodeFRPeriBorderSup,
appnNnNodeFRInterchangeSup,
appnNnNodeFRExteBorderSup,
appnNnTgFREntryTimeLeft,
appnNnTgFRDestVirtual,
appnNnTgFRDlcData,
appnNnTgFRRsn,
appnNnTgFROperational,
appnNnTgFRQuiescing,
appnNnTgFRCpCpSession,
appnNnTgFREffCap,
appnNnTgFRConnCost,
appnNnTgFRByteCost,
appnNnTgFRSecurity,
appnNnTgFRDelay,
appnNnTgFRUsr1,
appnNnTgFRUsr2,
appnNnTgFRUsr3,
appnNnTgFRGarbageCollect,
appnNnTgFRSubareaNum,
appnNnTgFRHprSup,
appnNnTgFRDestHprTrans,
appnNnTgFRTypeIndicator,
appnNnTgFRIntersubnet
}
STATUS current
DESCRIPTION
"The appnNnTopoConfGroup is mandatory only for network
nodes."
::= { appnGroups 9 }
OBJECTS {
appnLocalEnTgEntryTimeLeft,
appnLocalEnTgDestVirtual,
appnLocalEnTgDlcData,
appnLocalEnTgOperational,
appnLocalEnTgCpCpSession,
appnLocalEnTgEffCap,
appnLocalEnTgConnCost,
appnLocalEnTgByteCost,
appnLocalEnTgSecurity,
appnLocalEnTgDelay,
appnLocalEnTgUsr1,
appnLocalEnTgUsr2,
appnLocalEnTgUsr3
}
STATUS current
DESCRIPTION
"The appnLocalEnTopoConfGroup is mandatory only for network
nodes."
::= { appnGroups 10 }
OBJECTS {
appnDirMaxCaches,
appnDirCurCaches,
appnDirCurHomeEntries,
appnDirRegEntries,
appnDirInLocates,
appnDirInBcastLocates,
appnDirOutLocates,
appnDirOutBcastLocates,
appnDirNotFoundLocates,
appnDirNotFoundBcastLocates,
appnDirLocateOutstands
}
STATUS current
DESCRIPTION
"The appnLocalDirPerfConfGroup is mandatory only for APPN
network nodes and end nodes."
::= { appnGroups 11 }
OBJECTS {
appnCosModeCosName,
appnCosTransPriority,
appnCosNodeRowWgt,
appnCosNodeRowResistMin,
appnCosNodeRowResistMax,
appnCosNodeRowMinCongestAllow,
appnCosNodeRowMaxCongestAllow,
appnCosTgRowWgt,
appnCosTgRowEffCapMin,
appnCosTgRowEffCapMax,
appnCosTgRowConnCostMin,
appnCosTgRowConnCostMax,
appnCosTgRowByteCostMin,
appnCosTgRowByteCostMax,
appnCosTgRowSecurityMin,
appnCosTgRowSecurityMax,
appnCosTgRowDelayMin,
appnCosTgRowDelayMax,
appnCosTgRowUsr1Min,
appnCosTgRowUsr1Max,
appnCosTgRowUsr2Min,
appnCosTgRowUsr2Max,
appnCosTgRowUsr3Min,
appnCosTgRowUsr3Max
}
STATUS current
DESCRIPTION
"The appnCosConfGroup is mandatory only for APPN network
nodes and end nodes."
::= { appnGroups 12 }
OBJECTS {
appnIsInGlobeCtrAdminStatus,
appnIsInGlobeCtrOperStatus,
appnIsInGlobeCtrStatusTime,
appnIsInGlobeRscv,
appnIsInGlobeRscvTime,
appnIsInGlobeActSess,
appnIsInSessState,
appnIsInPriLuName,
appnIsInSecLuName,
appnIsInModeName,
appnIsInCosName,
appnIsInTransPriority,
appnIsInSessType,
appnIsInSessUpTime,
appnIsInCtrUpTime,
appnIsInP2SFmdPius,
appnIsInS2PFmdPius,
appnIsInP2SNonFmdPius,
appnIsInS2PNonFmdPius,
appnIsInP2SFmdBytes,
appnIsInS2PFmdBytes,
appnIsInP2SNonFmdBytes,
appnIsInS2PNonFmdBytes,
appnIsInPsAdjCpName,
appnIsInPsAdjTgNum,
appnIsInPsSendMaxBtuSize,
appnIsInPsSendPacingType,
appnIsInPsSendRpc,
appnIsInPsSendNxWndwSize,
appnIsInPsRecvPacingType,
appnIsInPsRecvRpc,
appnIsInPsRecvNxWndwSize,
appnIsInSsAdjCpName,
appnIsInSsAdjTgNum,
appnIsInSsSendMaxBtuSize,
appnIsInSsSendPacingType,
appnIsInSsSendRpc,
appnIsInSsSendNxWndwSize,
appnIsInSsRecvPacingType,
appnIsInSsRecvRpc,
appnIsInSsRecvNxWndwSize,
appnIsInRouteInfo
}
STATUS current
DESCRIPTION
"The appnIntSessConfGroup is mandatory only for network
nodes."
::= { appnGroups 13 }
OBJECTS {
appnNodeHprIntRteSetups,
appnNodeHprIntRteRejects,
appnLsErrRecoSup,
appnLsForAnrLabel,
appnLsRevAnrLabel
}
STATUS current
DESCRIPTION
"The appnHprBaseConfGroup is mandatory only for nodes that
implement the HPR base (APPN option set 1400)."
::= { appnGroups 14 }
OBJECTS {
appnNodeMaxSessPerRtpConn,
appnNodeHprOrgRteSetups,
appnNodeHprOrgRteRejects,
appnNodeHprEndRteSetups,
appnNodeHprEndRteRejects,
appnLsBfNceId
}
STATUS current
DESCRIPTION
"The appnHprRtpConfGroup is mandatory only for nodes that
implement the HPR RTP tower (APPN option set 1401)."
::= { appnGroups 15 }
OBJECTS {
appnLsCpCpNceId,
appnLsRouteNceId
}
STATUS current
DESCRIPTION
"The appnHprCtrlFlowsRtpConfGroup is mandatory only for nodes
that implement the HPR Control Flows over RTP tower (APPN
option set 1402)."
::= { appnGroups 16 }
OBJECTS {
appnIsInGlobeHprBfActSess,
appnIsInRtpNceId,
appnIsInRtpTcid,
appnIsRtpSessions
}
STATUS current
DESCRIPTION
"The appnHprBfConfGroup is mandatory only for nodes that
implement the APPN/HPR boundary function."
::= { appnGroups 17 }
OBJECTS {
alertIdNumber,
affectedObject
}
STATUS current
DESCRIPTION
"The appnTrapConfGroup is optional for all APPN nodes. Nodes
implementing this group shall also implement the appnTrapNotifGroup."
::= { appnGroups 18 }
NOTIFICATIONS {
alertTrap
}
STATUS current
DESCRIPTION
"The appnTrapNotifGroup is optional for all APPN nodes.
Nodes implementing this group shall also implement the
appnTrapConfGroup."
::= { appnGroups 19 }
This MIB module is the product of the IETF SNA NAU MIB WG and the AIW APPN/HPR MIBs SIG. Thanks to Wayne Clark, Cisco Systems; Jim Cobban, Nortel; Rich Daugherty, IBM Corporation; Mark Regan, Cisco Systems; and Leo Temoshenko, IBM Corporation, for their contributions and review.
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996.
[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[4] IBM, Systems Network Architecture Technical Overview, GC30-3073.
[5] IBM, Systems Network Architecture APPN Architecture Reference, SC30-3422
[6] IBM, Systems Network Architecture Formats, SC30-3346.
[7] Allen, M., Clouston, B., Kielczewski, Z., Kwan, W., and B. Moore, "Definition of Managed Objects for APPC", RFC 2051, Wall Data Inc., Cisco Systems, Jupiter Technology Inc., IBM Corporation, December 1995.
[8] Kielczewski, Z., Kostick D., and K. Shih, "Definition of Managed Objects for SNA NAUs using SMIv2", RFC 1666, Eicon Technology Corporation, Bell Communications Research, Novell, August 1994.
[9] Clouston, B., and B. Moore, "Definitions of Managed Objects for DLUR", November 1996.
[10] Clouston, B., and B. Moore, "Definitions of Managed Objects for HPR", November 1996.
[11] SNA DLC Services MIB Working Group, Hilgeman, J., Nix, S., Bartky, A., and W. Clark, "Definitions of Managed Objects for SNA Data Link Control (SDLC) using SMIv2", RFC 1747, January 1995. URL: ftp://ds.internic.net/rfc/rfc1747.txt
[12] SNA DLC Services MIB Working Group, Berl, S., Nix, S., and W. Clark, "Definitions of Managed Objects for SNA Data Link Control: LLC", May 1995.
[13] Chen, D., Gayek, P., and S. Nix, "Definitions of Managed Objects for Data Link Switching using SNMPv2", RFC 2024, October 1995.
[14] IBM, Systems Network Architecture Management Services Formats, GC31-8302.
In most cases, MIBs are not themselves security risks; if SNMP security is operating as intended, the use of a MIB to view information about a system, or to change some parameter at the system, is a tool, not a threat.
None of the read-only objects in the APPN MIB reports a password, user data, or anything else that is particularly sensitive. Some enterprises view their network configuration itself, as well as information about network usage and performance, as corporate assets; such enterprises may wish to restrict SNMP access to most of the objects in the MIB.
Four of the read-write objects in the MIB can affect network operations; it is recommended that SNMP access to these objects be restricted. The four objects are:
Other read-write objects control the gathering of network management data; controlling access to these objects is less critical.
Bob Clouston
Cisco Systems
7025 Kit Creek Road
Tel: 1 919 472 2333 E-mail: clouston@cisco.com
Bob Moore
IBM Corporation
800 Park Offices Drive
CNMA/664
Tel: 1 919 254 4436 E-mail: remoore@ralvm6.vnet.ibm.com