rfc1593.txt
来自「RFC 的详细文档！」· 文本 代码 · 共 2,001 行 · 第 1/5 页
TXT
2,001 行
Network Working Group W. McKenzie
Request for Comments: 1593 J. Cheng
Category: Informational IBM Networking Systems
March 1994
SNA APPN Node MIB
Status of this Memo
This memo provides information for the Internet community. This memo
does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
Abstract
This RFC describes IBM's SNMP support for SNA Advanced Peer-to-Peer
Networking (APPN) nodes.
Table of Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1 APPN Node Group . . . . . . . . . . . . . . . . . . . . . . 3
2.1.1 APPN Node General Information . . . . . . . . . . . . . 4
2.1.2 APPN Network Node Information . . . . . . . . . . . . . 6
2.1.3 APPN End Node Information . . . . . . . . . . . . . . . 8
2.1.4 APPN Port Information . . . . . . . . . . . . . . . . 10
2.1.4.1 General Port Information . . . . . . . . . . . . . 10
2.1.4.2 TCP/IP Port Information . . . . . . . . . . . . . 14
2.1.4.3 Data Link Switch Port Information . . . . . . . . 15
2.1.4.4 Token Ring Port Information . . . . . . . . . . . 16
2.1.4.5 Port DLC Trace Information . . . . . . . . . . . . 17
2.1.5 APPN Link Station Information . . . . . . . . . . . . 23
2.1.5.1 General Link Station Information . . . . . . . . . 23
2.1.5.2 TCP/IP Link Station Information . . . . . . . . . 35
2.1.5.3 Data Link Switch Link Station Information . . . . 37
2.1.5.4 Token Ring Link Station Information . . . . . . . 39
2.1.5.5 Link Station Status Information . . . . . . . . . 41
2.1.6 SNMP Performance Information for APPN Subagent . . . . 46
2.1.7 Performance Information for APPN Node . . . . . . . . 49
2.1.8 XID Statistics . . . . . . . . . . . . . . . . . . . . 50
2.2 APPN Topology Group . . . . . . . . . . . . . . . . . . . 51
2.2.1 Topology Performance Information . . . . . . . . . . . 52
2.2.1.1 Topology Route Information . . . . . . . . . . . . 58
2.2.2 Adjacent Node Table . . . . . . . . . . . . . . . . . 60
2.2.3 Network Node Topology . . . . . . . . . . . . . . . . 62
2.2.3.1 NN Topology Table (Indexed by Node Name) . . . . . 62
McKenzie & Cheng [Page 1]
RFC 1593 SNA APPN Node MIB March 1994
2.2.3.2 NN TG Table (Indexed by Node Names and TG Number) 66
2.2.3.3 NN Topology Table (Indexed by FRSN and Node Name) 73
2.2.3.4 NN TG Table (Indexed by FRSN, Node Names, and TG
Number) . . . . . . . . . . . . . . . . . . . . . 77
2.3 APPN Node Local Topology Group . . . . . . . . . . . . . . 83
2.3.1 Local Topology This Node . . . . . . . . . . . . . . . 84
2.3.1.1 Local General Information . . . . . . . . . . . . 84
2.3.1.2 Local NN Specific Information . . . . . . . . . . 85
2.3.1.3 Local TG Information . . . . . . . . . . . . . . . 87
2.3.2 Client End Nodes Topology Known to Serving NN . . . . 93
2.3.2.1 Client End Nodes Information . . . . . . . . . . . 93
2.3.2.2 Client End Nodes TG Information (Tail Vectors) . . 94
2.4 APPN Directory Group . . . . . . . . . . . . . . . . . . . 99
2.4.1 Directory Performance Information . . . . . . . . . . 99
2.4.2 Directory Cache Table . . . . . . . . . . . . . . . . 102
2.5 APPN Class Of Service Group . . . . . . . . . . . . . . . 105
2.5.1 COS Mode Table . . . . . . . . . . . . . . . . . . . . 108
2.5.2 COS Name Table . . . . . . . . . . . . . . . . . . . . 109
2.5.3 COS Node Row Table . . . . . . . . . . . . . . . . . . 110
2.5.4 COS TG Row Table . . . . . . . . . . . . . . . . . . . 113
3.0 Acknowledgements . . . . . . . . . . . . . . . . . . . . . 119
4.0 Security Considerations . . . . . . . . . . . . . . . . . . 119
5.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 120
1.0 Introduction
This module contains managed objects which describe the following:
o The APPN node (either an APPN network node or an APPN end node)
o The connections of the node to other SNA nodes
o The APPN network topology (as reflected in the network topology
database that is replicated in each APPN network node.
This module does not describe the SNA logical units (LUs) served by
the APPN node nor does it describe the sessions between LUs. Managed
objects for that information are under development.
McKenzie & Cheng [Page 2]
RFC 1593 SNA APPN Node MIB March 1994
2.0 Definitions
IBM-6611-APPN-MIB DEFINITIONS ::= BEGIN
IMPORTS
enterprises, Counter, IpAddress,
Gauge, TimeTicks
FROM RFC1155-SMI
DisplayString
FROM RFC1213-MIB
OBJECT-TYPE
FROM RFC-1212;
-- ******************************************************************
ibm OBJECT IDENTIFIER ::= { enterprises 2 }
ibmProd OBJECT IDENTIFIER ::= { ibm 6 }
ibm6611 OBJECT IDENTIFIER ::= { ibmProd 2 }
ibmappn OBJECT IDENTIFIER ::= { ibm6611 13 }
-- ******************** The APPN Node Group *********************
ibmappnNode OBJECT IDENTIFIER ::= { ibmappn 1 }
ibmappnGeneralInfoAndCaps OBJECT IDENTIFIER ::= { ibmappnNode 1 }
ibmappnNnUniqueInfoAndCaps OBJECT IDENTIFIER ::= { ibmappnNode 2 }
ibmappnEnUniqueCaps OBJECT IDENTIFIER ::= { ibmappnNode 3 }
ibmappnPortInformation OBJECT IDENTIFIER ::= { ibmappnNode 4 }
ibmappnLinkStationInformation OBJECT IDENTIFIER ::= { ibmappnNode 5 }
ibmappnSnmpInformation OBJECT IDENTIFIER ::= { ibmappnNode 6 }
ibmappnMemoryUse OBJECT IDENTIFIER ::= { ibmappnNode 7 }
ibmappnXidInformation OBJECT IDENTIFIER ::= { ibmappnNode 8 }
-- This group provides global information about the
-- APPN node, which is either a network node or an end node.
-- The first section applies to all APPN nodes.
-- The second section applies only to network nodes.
-- The third section applies only to end nodes.
-- The fourth section applies to Port information.
-- The fifth section applies to SNA link station Information.
-- The sixth section applies to SNMP traffic for this APPN sub-agent
-- The seventh section applies to APPN memory usage.
-- The eighth section applies to XID activities.
McKenzie & Cheng [Page 3]
RFC 1593 SNA APPN Node MIB March 1994
-- APPN General Information
-- This section applies to both network and end nodes.
ibmappnNodeCpName OBJECT-TYPE
SYNTAX DisplayString (SIZE (3..17))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Administratively-assigned network name
for this node in the format NETID.CPNAME."
::= { ibmappnGeneralInfoAndCaps 1 }
ibmappnNodeNetid OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..8))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Administratively-assigned APPN network identification,
which can be from one to eight characters.
This ID is used with the control point name
to create a fully-qualified control point name."
::= { ibmappnGeneralInfoAndCaps 2 }
ibmappnNodeBlockNum OBJECT-TYPE
SYNTAX DisplayString (SIZE (3))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The block number is the first three digits of the node_id.
These 3 hexadecimal digits identify the product and are not
configurable."
::= { ibmappnGeneralInfoAndCaps 3 }
ibmappnNodeIdNum OBJECT-TYPE
SYNTAX DisplayString (SIZE (5))
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The ID number is the last 5 digits of the node_id.
These 5 hexadecimal digits are administratively defined and
combined with the 3 digit block number form the node_id.
This node_id is used to identify the local node and is
include in APPN alerts as well as being included in XIDs.
A unique value is required for connections to SNA
McKenzie & Cheng [Page 4]
RFC 1593 SNA APPN Node MIB March 1994
sub-area."
::= { ibmappnGeneralInfoAndCaps 4 }
ibmappnNodeType OBJECT-TYPE
SYNTAX INTEGER {
networkNode(1),
endNode(2),
len(4)
}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Type of APPN node, either network, len, or end node."
::= { ibmappnGeneralInfoAndCaps 5 }
ibmappnNodeUpTime OBJECT-TYPE
SYNTAX TimeTicks
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Time (in hundredths of a second) since this APPN node
was initialized."
::= { ibmappnGeneralInfoAndCaps 6 }
ibmappnNodeNegotLs OBJECT-TYPE
SYNTAX INTEGER {yes(1), no(2)}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether this node supports negotiable
link stations."
::= { ibmappnGeneralInfoAndCaps 7 }
ibmappnNodeSegReasm OBJECT-TYPE
SYNTAX INTEGER {yes(1), no(2)}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether this node supports segment
reassembly. This is only supported when
segment generation is also supported."
::= { ibmappnGeneralInfoAndCaps 8 }
McKenzie & Cheng [Page 5]
RFC 1593 SNA APPN Node MIB March 1994
ibmappnNodeBindReasm OBJECT-TYPE
SYNTAX INTEGER {yes(1), no(2)}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether this node supports Bind segment
reassembly. This will only be supported when Bind
segment generation is also supported."
::= { ibmappnGeneralInfoAndCaps 9 }
ibmappnNodeParallelTg OBJECT-TYPE
SYNTAX INTEGER {yes(1), no(2)}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether this node supports parallel TGs."
::= { ibmappnGeneralInfoAndCaps 10 }
ibmappnNodeService OBJECT-TYPE
SYNTAX INTEGER {yes(1), no(2)}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether this node allows call-in from nodes not
defined locally."
::= { ibmappnGeneralInfoAndCaps 11 }
ibmappnNodeAdaptiveBindPacing OBJECT-TYPE
SYNTAX INTEGER {yes(1), no(2)}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether this node supports adaptive bind pacing."
::= { ibmappnGeneralInfoAndCaps 12 }
-- **************************************************************
-- APPN Network Node Information
-- This section provides global information about the
-- APPN network node.
ibmappnNodeNnRcvRegChar OBJECT-TYPE
SYNTAX INTEGER {yes(1), no(2)}
McKenzie & Cheng [Page 6]
RFC 1593 SNA APPN Node MIB March 1994
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether this node supports receiving registered
characteristics."
::= { ibmappnNnUniqueInfoAndCaps 1 }
ibmappnNodeNnGateway OBJECT-TYPE
SYNTAX INTEGER {yes(1), no(2)}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether this is a gateway node."
::= { ibmappnNnUniqueInfoAndCaps 2 }
ibmappnNodeNnCentralDirectory OBJECT-TYPE
SYNTAX INTEGER {yes(1), no(2)}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether this node supports central directory
cache."
::= { ibmappnNnUniqueInfoAndCaps 3 }
ibmappnNodeNnTreeCache OBJECT-TYPE
SYNTAX INTEGER {yes(1), no(2)}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether this node supports route tree cache."
::= { ibmappnNnUniqueInfoAndCaps 4 }
ibmappnNodeNnTreeUpdate OBJECT-TYPE
SYNTAX INTEGER {yes(1), no(2)}
ACCESS read-only
STATUS mandatory
DESCRIPTION
"Indicates whether this node supports
incremental_tree_update, which is only
supported when tree caching is supported."
::= { ibmappnNnUniqueInfoAndCaps 5 }
ibmappnNodeNnRouteAddResist OBJECT-TYPE
McKenzie & Cheng [Page 7]
RFC 1593 SNA APPN Node MIB March 1994
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
⌨️ 快捷键说明
复制代码Ctrl + C
搜索代码Ctrl + F
全屏模式F11
增大字号Ctrl + =
减小字号Ctrl + -
显示快捷键?