Network Working Group B. Clouston
Request for Comments: 2457 Cisco Systems
Category: Standards Track B. Moore
IBM Corporation
November 1998
Network Working Group B. Clouston
Request for Comments: 2457 Cisco Systems
Category: Standards Track B. Moore
IBM Corporation
November 1998
Definitions of Managed Objects for Extended Border Node
扩展边界节点的托管对象定义
Status of this Memo
本备忘录的状况
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.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
Abstract
摘要
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 Network) EBN (Extended Border Node) capabilities. This memo identifies managed objects for the EBN architecture.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它定义了用于监视和控制具有APPN（高级对等网络）EBN（扩展边界节点）功能的网络设备的对象。此备忘录确定了EBN体系结构的托管对象。
Table of Contents
目录
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 The SNMP Network Management Framework . . . . . . . . . . 2
3.0 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1 EBN MIB Structure . . . . . . . . . . . . . . . . . . . . 4
3.1.1 enbDir group . . . . . . . . . . . . . . . . . . . . . 5
3.1.2 ebnIsRscv group . . . . . . . . . . . . . . . . . . . 5
3.1.3 ebnDirConfig group . . . . . . . . . . . . . . . . . . 7
3.1.4 ebnCos group . . . . . . . . . . . . . . . . . . . . . 8
3.1.5 ebnSubnetRoutingList group . . . . . . . . . . . . . . 8
3.1.6 hbn group . . . . . . . . . . . . . . . . . . . . . . 8
4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . 9
5.0 Security Considerations . . . . . . . . . . . . . . . . . 24
6.0 Intellectual Property . . . . . . . . . . . . . . . . . . 25
7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . 25
8.0 References . . . . . . . . . . . . . . . . . . . . . . . . 25
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 The SNMP Network Management Framework . . . . . . . . . . 2
3.0 Overview . . . . . . . . . . . . . . . . . . . . . . . . . 3
3.1 EBN MIB Structure . . . . . . . . . . . . . . . . . . . . 4
3.1.1 enbDir group . . . . . . . . . . . . . . . . . . . . . 5
3.1.2 ebnIsRscv group . . . . . . . . . . . . . . . . . . . 5
3.1.3 ebnDirConfig group . . . . . . . . . . . . . . . . . . 7
3.1.4 ebnCos group . . . . . . . . . . . . . . . . . . . . . 8
3.1.5 ebnSubnetRoutingList group . . . . . . . . . . . . . . 8
3.1.6 hbn group . . . . . . . . . . . . . . . . . . . . . . 8
4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . 9
5.0 Security Considerations . . . . . . . . . . . . . . . . . 24
6.0 Intellectual Property . . . . . . . . . . . . . . . . . . 25
7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . 25
8.0 References . . . . . . . . . . . . . . . . . . . . . . . . 25
9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 27
10.0 Full Copyright Statement . . . . . . . . . . . . . . . . 28
9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 27
10.0 Full Copyright Statement . . . . . . . . . . . . . . . . 28
This document is a product of the SNA NAU Services MIB Working Group. It defines a MIB module for managing devices with Advanced Peer-to-Peer Networking (APPN) Extended Border Node (EBN) capabilities.
本文件是SNA NAU服务MIB工作组的产品。它定义了一个MIB模块，用于管理具有高级对等网络（APPN）扩展边界节点（EBN）功能的设备。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119, reference [13].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不得”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119，参考文献[13]中的描述进行解释。
The SNMP Network Management Framework presently consists of six major components. They are:
SNMP网络管理框架目前由六个主要组件组成。他们是：
o the overall architecture, described in RFC 2271 [7].
o RFC 2271[7]中描述的总体架构。
o the SMI, described in RFC 1902 [3], - the mechanisms used for describing and naming objects for the purpose of management.
o RFC 1902[3]中描述的SMI——用于描述和命名对象以进行管理的机制。
o the MIB-II, STD 17, RFC 1213 [2], - the core set of managed objects for the Internet suite of protocols.
o MIB-II，STD 17，RFC 1213[2]，-互联网协议套件的核心托管对象集。
o the protocol, STD 15, RFC 1157 [1] and/or RFC 1905 [6] and/or RFC 2272 [8] -- the protocol for accessing managed information.
o 协议STD 15、RFC 1157[1]和/或RFC 1905[6]和/或RFC 2272[8]——用于访问托管信息的协议。
o the user-based security model defined in RFC 2274 [10].
o RFC 2274[10]中定义的基于用户的安全模型。
o the view-based access control model defined in RFC 2275 [11].
o RFC 2275[11]中定义的基于视图的访问控制模型。
Textual conventions are defined in RFC 1903 [4], and conformance statements are defined in RFC 1904 [5]. Common applications are defined in RFC 2273 [9].
文本约定在RFC 1903[4]中定义，一致性声明在RFC 1904[5]中定义。RFC 2273[9]中定义了常见应用程序。
The Framework permits new objects to be defined for the purpose of experimentation and evaluation.
该框架允许为实验和评估目的定义新对象。
This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translation.
此备忘录指定了符合SMIv2的MIB模块。通过适当的翻译，可以生成符合SMIv1的MIB。
This document identifies the proposed set of objects for monitoring the configuration and active characteristics of devices with EBN capabilities. The Extended Border Node function is an APPN enhancement for an APPN network node (NN). It supports topology isolation, subnet interconnection, and session establishment between subnets.
本文件确定了用于监控具有EBN功能的设备的配置和活动特性的拟议对象集。扩展边界节点功能是APPN网络节点（NN）的APPN增强功能。它支持拓扑隔离、子网互连和子网之间的会话建立。
In a single APPN network, all network topology information is propagated to all network nodes. Directory searches can also be forwarded to all network nodes. As the network grows, this network traffic could become prohibitive. Also, in networks where different enterprises are connected via APPN, it may be desirable to shield an enterprise from the network traffic of another enterprise. EBNs allow customers to partition a network into subnets to reduce or shield such network traffic.
在单个APPN网络中，所有网络拓扑信息都会传播到所有网络节点。目录搜索也可以转发到所有网络节点。随着网络的发展，这种网络流量可能会变得令人望而却步。此外，在通过APPN连接不同企业的网络中，可能需要保护一个企业不受另一个企业的网络流量的影响。EBN允许客户将网络划分为子网，以减少或屏蔽此类网络流量。
An EBN provides this function by blocking topology information exchange between subnets, and controlling where directory searches are forwarded. A subnetwork is a cluster of APPN NNs which share the same network topology. Subnetwork boundaries, or partitions, occur where an EBN and an NN adjacent to it have different network identifiers (NETIDs). They may also occur where an EBN and adjacent NN have the same NETID but are configured to have a subnetwork boundary.
EBN通过阻止子网之间的拓扑信息交换以及控制目录搜索转发的位置来提供此功能。子网络是共享相同网络拓扑的APPN NN的群集。子网络边界或分区发生在EBN和与其相邻的NN具有不同网络标识符（NetID）的地方。当EBN和相邻NN具有相同的NETID，但配置为具有子网络边界时，也可能发生这种情况。
The connection between two APPN nodes is an APPN transmission group (TG). A TG at a subnet boundary is called an Intersubnetwork Transmission Group (ISTG).
两个APPN节点之间的连接是一个APPN传输组（TG）。子网边界处的TG称为子网间传输组（ISTG）。
The subnet in which an EBN resides is called its native subnetwork. The subnet across the subnet boundary is called the non-native subnetwork, with respect to the EBN.
EBN所在的子网称为其本机子网。就EBN而言，跨越子网边界的子网称为非本机子网。
A cost of the EBN function is that customers may have difficulty determining the end-to-end route of sessions that cross subnet boundaries, and understanding how the EBN will control directory searches between subnets. This MIB addresses these issues.
EBN功能的一个成本是，客户可能难以确定跨子网边界的会话的端到端路由，也难以理解EBN将如何控制子网之间的目录搜索。这个MIB解决了这些问题。
Another challenge facing customers is to identify subnet boundaries formed by EBNs. The SNANAU APPN MIB [14] identifies subnet boundaries in the appnNnTopology group. The SNANAU APPN MIB provides management of APPN objects, and contains some tables that are extended by this MIB.
客户面临的另一个挑战是识别由EBN形成的子网边界。SNANAU APPN MIB[14]标识APPNNTopology组中的子网边界。SNANAU APPN MIB提供APPN对象的管理，并包含一些由该MIB扩展的表。
In this document, we describe EBN managed objects.
在本文档中，我们将描述EBN托管对象。
The EBN terms and overall architecture are available from the networking.raleigh.ibm.com ftp site [15].
EBN术语和总体架构可从networking.raleigh.ibm.com ftp站点获得[15]。
Highlights of the management functions supported by the EBN MIB module include the following:
EBN MIB模块支持的管理功能要点包括：
o Identifying the subnet affiliation of LUs (logical units)
o 标识逻辑单元（逻辑单元）的子网从属关系
o Identifying session routes in non-native subnets, with correlation to the route in the native subnet provided in the SNANAU APPN MIB.
o 识别非本机子网中的会话路由，与SNANAU APPN MIB中提供的本机子网中的路由相关。
o Identifying the COS (Class of Service) mappings between subnets.
o 确定子网之间的COS（服务类别）映射。
o Identifying the subnet routing lists
o 识别子网路由列表
This MIB module does not support:
此MIB模块不支持：
o Configuration of EBN nodes.
o EBN节点的配置。
o Historical information about session initiation failures.
o 会话启动失败的历史信息。
o Peripheral Border Node (PBN) support. PBN is an APPN function that only supports communication to adjacent subnetworks, and is not expected to be widely implemented.
o 外围边界节点（PBN）支持。PBN是一种APPN功能，仅支持与相邻子网的通信，预计不会广泛实现。
o Traps. The APPN MIB contains a trap for Alert conditions that may affect EBN resources. Although no APPN/EBN Alerts are defined today in the APPN MIB [14], they could exist in the future. The value for the affectedObject object contained in the alertTrap is determined by the implementation. It may contain a VariablePointer from the EBN MIB.
o 陷阱。APPN MIB包含可能影响EBN资源的警报条件陷阱。尽管APPN MIB[14]中目前未定义APPN/EBN警报，但它们可能在将来存在。alertTrap中包含的affectedObject对象的值由实现确定。它可能包含来自EBN MIB的可变指针。
The EBN MIB module contains the following groups of objects:
EBN MIB模块包含以下对象组：
o ebnDir - subnet information about LUs.
o ebnDir-有关LU的子网信息。
o ebnIsRscv - provides the RSCV (Route Selection Control Vector) and COS for the subnetwork on the BIND destination side of the EBN.
o ebnIsRscv-为EBN绑定目的地侧的子网提供RSCV（路由选择控制向量）和COS。
o ebnDirConfig - objects related to the EBN directory.
o ebnDirConfig—与EBN目录相关的对象。
o ebnCos - COS mapping between subnetworks,
o ebnCos-子网之间的COS映射，
o ebnSubnetRoutingList - the customer-supplied list of where to forward search requests.
o ebnSubnetRoutingList—客户提供的转发搜索请求的位置列表。
o hbn - HPR (High Performance Routing) EBN intermediate session information.
o hbn-HPR（高性能路由）EBN中间会话信息。
These groups are described below in more detail.
下面将更详细地描述这些组。
The ebnDir group contains the ebnDirTable, which is an extension to the appnDirTable. It specifies the subnet affiliation of LUs in the EBN's directory.
ebnDir组包含ebnDirTable，它是appnDirTable的扩展。它指定EBN目录中LU的子网从属关系。
The ebnIsRscv group contains the ebnIsRscvTable, which is an extension to the appnIsInTable. The appnIsInTable only allows for the RSCV and COS name for one subnetwork traversed by a session. This extension contains the RSCV and COS name for the other subnetwork.
ebnIsRscv组包含ebnIsRscvTable，它是appnistable的扩展。appnIsInTable仅允许会话遍历的一个子网的RSCV和COS名称。此扩展包含其他子网的RSCV和COS名称。
When an EBN changes RSCVs before forwarding a BIND, appnIsInRouteInfo contains the incoming RSCV, and ebnIsRscvDestinationRoute contains the outgoing RSCV.
当EBN在转发绑定之前更改RSCV时，appnIsInRouteInfo包含传入RSCV，ebnIsRscvDestinationRoute包含传出RSCV。
The following three cases illustrate the contents of appnIsInRouteInfo and ebnIsRscvDestinationRoute at Extended Border Nodes.
以下三个案例说明了扩展边界节点上appnIsInRouteInfo和ebnIsRscvDestinationRoute的内容。
1. EBN connected to another EBN
1. 连接到另一个EBN的EBN
**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 EBN2
PLU SLU
---------------------------->|
(1) |--------------->|
(2) |---------->
(3)
**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 EBN2
PLU SLU
---------------------------->|
(1) |--------------->|
(2) |---------->
(3)
PLU = Primary Logical Unit (session initiator) SLU = Secondary Logical Unit (session destination)
PLU=主逻辑单元（会话启动器）SLU=辅助逻辑单元（会话目标）
The value of the appnIsInRouteInfo object at EBN1 is the RSCV containing the route, represented by (1), from the PLU (or the entry EBN in its subnet) to EBN2. The value of ebnIsRscvDestinationRoute object at EBN1 is the RSCV, represented by (2), containing the one-hop route from EBN1 to EBN2. The
EBN1处appnIsInRouteInfo对象的值是包含从PLU（或其子网中的条目EBN）到EBN2的路由的RSCV，由（1）表示。EBN1处EBNISRSCVDESTIONROUTE对象的值是RSCV，由（2）表示，包含从EBN1到EBN2的一跳路由。这个
appnIsInRouteInfo object at EBN2 also contains the RSCV represented by (2). The value of ebnIsRscvDestinationRoute in EBN2 is the RSVC containing the route to the SLU (or to the next subnet's entry EBN), represented by (3).
EBN2处的appnIsInRouteInfo对象还包含由（2）表示的RSCV。EBN2中EBNISRSCVDESTIONROUTE的值是包含到SLU（或到下一个子网的条目EBN）的路由的RSVC，由（3）表示。
2. EBN connected to a NN or PBN
2. 连接到NN或PBN的EBN
**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 NN/PBN
PLU SLU
---------------------------->|
(1) |--------------------------->
(2)
**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 NN/PBN
PLU SLU
---------------------------->|
(1) |--------------------------->
(2)
The value of the appnIsInRouteInfo object at EBN1 is the RSCV containing the route from the PLU (or the entry EBN in its subnet) to the NN or PBN, represented by (1). The value of the ebnIsRscvDestinationRoute object at EBN1 is the RSCV containing the route from EBN1 to the SLU, represented by (2). Note that the SLU must be in subnet 2, because the entry node is an NN or PBN rather than an EBN. The appnIsInRouteInfo object at NN/PBN contains the same RSCV, as represented by (2).
EBN1处appnIsInRouteInfo对象的值是包含从PLU（或其子网中的条目EBN）到NN或PBN的路由的RSCV，由（1）表示。EBN1处的ebnIsRscvDestinationRoute对象的值是包含从EBN1到SLU的路由的RSCV，由（2）表示。请注意，SLU必须位于子网2中，因为入口节点是NN或PBN，而不是EBN。NN/PBN处的appnIsInRouteInfo对象包含相同的RSCV，如（2）所示。
3. NN or PBN connected to EBN
3. NN或PBN连接到EBN
**subnet 1**|-----ISTG ------|**subnet 2**
NN/PBN EBN1
PLU SLU
---------------------------->|
(1) |---------->
(2)
**subnet 1**|-----ISTG ------|**subnet 2**
NN/PBN EBN1
PLU SLU
---------------------------->|
(1) |---------->
(2)
The value of the appnIsInRouteInfo object at the NN/PBN is the RSCV containing the route from the PLU to EBN1, represented by (1). Note that the PLU must be in subnet 1, because the exit node is an NN/PBN rather than an EBN. The appnIsInRouteInfo object at EBN1 contains the same RSCV. The value of the ebnIsRscvDestinationRoute object at EBN1 is the RSCV containing the route from EBN1 to the SLU (or the next subnet's entry border node), as represented by (2).
NN/PBN处appnIsInRouteInfo对象的值是包含从PLU到EBN1的路由的RSCV，由（1）表示。请注意，PLU必须位于子网1中，因为退出节点是NN/PBN而不是EBN。EBN1处的appnIsInRouteInfo对象包含相同的RSCV。EBN1处的ebnIsRscvDestinationRoute对象的值是包含从EBN1到SLU（或下一个子网的入口边界节点）的路由的RSCV，如（2）所示。
The following three cases illustrate the contents of ebnIsRscvDestinationCos at Extended Border Nodes.
以下三个案例说明了扩展边界节点上EBNISRSCVDESTINATIONCS的内容。
1. EBN connected to another EBN
1. 连接到另一个EBN的EBN
**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 EBN2
PLU SLU
COS A
---------------------------->|
COS B
|---------->
**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 EBN2
PLU SLU
COS A
---------------------------->|
COS B
|---------->
PLU = Primary Logical Unit (session initiator) SLU = Secondary Logical Unit (session destination)
PLU=主逻辑单元（会话启动器）SLU=辅助逻辑单元（会话目标）
The value of ebnIsRscvDestinationCos object at EBN1 is COS A. The value of ebnIsRscvDestinationCos object at EBN2 is COS B.
EBN1处ebnIsRscvDestinationCos对象的值为COS A。EBN2处ebnIsRscvDestinationCos对象的值为COS B。
2. EBN connected to a NN or PBN
2. 连接到NN或PBN的EBN
**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 NN/PBN
PLU SLU
COS A
----------->|
COS B
|--------------------------->
**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 NN/PBN
PLU SLU
COS A
----------->|
COS B
|--------------------------->
The value of the ebvIsRscvDestinationCos object at EBN1 is COS B.
EBN1处的ebvIsRscvDestinationCos对象的值为COS B。
3. NN or PBN connected to EBN
3. NN或PBN连接到EBN
**subnet 1**|-----ISTG ------|**subnet 2**
NN/PBN EBN1
PLU SLU
COS A
---------------------------->|
COS B
|---------->
**subnet 1**|-----ISTG ------|**subnet 2**
NN/PBN EBN1
PLU SLU
COS A
---------------------------->|
COS B
|---------->
The value of the ebnIsRscvDestinationCos object at the EBN2 is COSB.
EBN2处ebnIsRscvDestinationCos对象的值为COSB。
The ebnDirConfig group consists of simple objects that provide EBN-specific information about directory caching and the local default value for the maximum number of subnetworks a LOCATE search procedure may traverse.
ebnDirConfig组由简单对象组成，这些对象提供有关目录缓存的EBN特定信息以及LOCATE search过程可能穿越的最大子网络数的本地默认值。
The ebnCos group contains the ebnCosMapTable, which specifies how COS values are mapped between the non-native subnetwork and the native subnetwork.
ebnCos组包含EBNCOSMATABLE，它指定如何在非本机子网络和本机子网络之间映射COS值。
The ebnSubnetRoutingList group contains information about the customer-supplied EBN subnetwork routing list, which indicates to which adjacent nodes an EBN will forward LOCATE search requests. It consists of the following tables:
ebnSubnetRoutingList组包含有关客户提供的EBN子网路由列表的信息，该列表指示EBN将向哪些相邻节点转发定位搜索请求。它由以下表格组成：
1. ebnSubnetSearchTable
1. ebnSubnetSearchTable
This table has an entry for each LU name that has a defined subnet routing list. The LU name may identify a single LU, or it may contain a wildcard character that could identify a group of LUs (partial wildcard) or all LUs (full wildcard). The objects in the table indicate whether the EBN may add dynamic entries to the subnet routing list, and whether the subnet routing list entries may be reordered for better search performance.
此表为每个具有定义的子网路由列表的LU名称提供了一个条目。LU名称可以标识单个LU，也可以包含可以标识一组LU（部分通配符）或所有LU（完全通配符）的通配符。表中的对象指示EBN是否可以向子网路由列表添加动态条目，以及是否可以重新排序子网路由列表条目以提高搜索性能。
2. ebnSearchTable
2. EBN搜索表
This table has an entry for each control point name which is included in a multi-subnet search for a particular LU name. The index to the table is the LU name to be searched for, and an index which lists the order in which the CP names are to be searched. Both the CP name and the LU name entries in the table allow for partial and full wildcards. The CP name also allows for special entries that indicate that the EBN will search itself and its own native subnetwork at this point in the search, or will search all native EBNs.
此表包含每个控制点名称的条目，该条目包含在特定LU名称的多子网搜索中。表的索引是要搜索的LU名称，以及列出CP名称搜索顺序的索引。表中的CP名称和LU名称项都允许使用部分和完全通配符。CP名称还允许特殊条目，指示EBN将在搜索过程中搜索自身及其自身的本机子网，或搜索所有本机EBN。
The hbn group contains information about HBN (HPR EBN) intermediate sessions. The hbnIsInTable is an extension to the appnIsInTable. This table is present for intermediate sessions when there are back-to-back RTP (Rapid Transport Protocol) connections in an HBN. It provides the NCE ID (network connection endpoint identifier) and TCID (transport connection identifier) for the second RTP connection.
hbn组包含有关hbn（HPR EBN）中间会话的信息。hbnIsInTable是appnIsInTable的扩展。当HBN中存在背对背RTP（快速传输协议）连接时，此表用于中间会话。它为第二个RTP连接提供NCE ID（网络连接端点标识符）和TCID（传输连接标识符）。
EBN-MIB DEFINITIONS ::= BEGIN
EBN-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
DisplayString, TEXTUAL-CONVENTION
FROM SNMPv2-TC
SnaControlPointName
-- Because the characters allowed in an SNA control
-- point name come from a restricted character set,
-- these names are not subject to internationalization.
FROM APPN-MIB
snanauMIB
FROM SNA-NAU-MIB;
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
DisplayString, TEXTUAL-CONVENTION
FROM SNMPv2-TC
SnaControlPointName
-- Because the characters allowed in an SNA control
-- point name come from a restricted character set,
-- these names are not subject to internationalization.
FROM APPN-MIB
snanauMIB
FROM SNA-NAU-MIB;
ebnMIB MODULE-IDENTITY LAST-UPDATED "9804281800Z" -- April 28, 1998 ORGANIZATION "IETF SNA NAU MIB WG / AIW APPN MIBs SIG" CONTACT-INFO " Bob Clouston Cisco Systems 7025 Kit Creek Road P.O. Box 14987 Research Triangle Park, NC 27709, USA Tel: 1 919 472 2333 E-mail: clouston@cisco.com
ebnMIB模块标识最后一次更新“9804281800Z”-1998年4月28日组织“IETF SNA NAU MIB WG/AIW APPN MIBs SIG”联系信息“Bob Clouston Cisco Systems 7025 Kit Creek Road邮政信箱14987美国北卡罗来纳州三角研究公园27709电话：1919 472 2333电子邮件：clouston@cisco.com
Bob Moore IBM Corporation BRQA/501 P.O. Box 12195 Research Triangle Park, NC 27709, USA Tel: 1 919 254 4436 E-mail: remoore@us.ibm.com "
Bob Moore IBM Corporation BRQA/501信箱12195美国北卡罗来纳州三角研究园27709电话：1919 254 4436电子邮件：remoore@us.ibm.com "
DESCRIPTION " The MIB Module for Extended Border Node"
说明“扩展边界节点的MIB模块”
::= { snanauMIB 7 }
::= { snanauMIB 7 }
-- snanauMIB ::= { mib-2 34 }
-- snanauMIB ::= { mib-2 34 }
-- ******************************************************************
-- Textual Conventions
-- ------------------------------------------------------------------
SnaNAUWildcardName ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Fully-qualified network NAU name. Entries take one of three
forms:
- 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 NAU Name.
- A full wildcard consists of a single character '*'.
-- ******************************************************************
-- Textual Conventions
-- ------------------------------------------------------------------
SnaNAUWildcardName ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Fully-qualified network NAU name. Entries take one of three
forms:
- 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 NAU Name.
- A full wildcard consists of a single character '*'.
Because the characters allowed in an SNA NAU name come from a restricted character set, these names are not subject to internationalization."
由于SNA NAU名称中允许的字符来自受限字符集，因此这些名称不受国际化限制。”
SYNTAX DisplayString(SIZE(1..17))
语法显示字符串（大小（1..17））
-- ******************************************************************
ebnObjects OBJECT IDENTIFIER ::= { ebnMIB 1 }
-- ******************************************************************
-- ******************************************************************
ebnObjects OBJECT IDENTIFIER ::= { ebnMIB 1 }
-- ******************************************************************
-- ******************************************************************
-- EBN Directory Group
-- The ebnDirTable is an extension to the appnDirTable. It specifies
-- the subnet affiliation for LUs in the EBN's directory.
-- ******************************************************************
-- ******************************************************************
-- EBN Directory Group
-- The ebnDirTable is an extension to the appnDirTable. It specifies
-- the subnet affiliation for LUs in the EBN's directory.
-- ******************************************************************
ebnDir OBJECT IDENTIFIER ::= { ebnObjects 1 }
ebnDir OBJECT IDENTIFIER ::= { ebnObjects 1 }
ebnDirTable OBJECT-TYPE SYNTAX SEQUENCE OF EbnDirEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The EBN Directory Table. This table is an extension to the APPN MIB's appnDirTable. Entries in this table are in one-to-one correspondence with entries in the appnDirTable, with corresponding entries having identical values for their respective indexes."
EbnDirEntry MAX-ACCESS的ebndiretable对象类型语法序列不可访问状态当前描述“EBN目录表。此表是APPN MIB的appnDirTable的扩展。此表中的条目与附件表中的条目一一对应，对应条目的各自索引值相同。”
::= { ebnDir 1 }
::= { ebnDir 1 }
ebnDirEntry OBJECT-TYPE SYNTAX EbnDirEntry MAX-ACCESS not-accessible
ebnDirEntry对象类型语法ebnDirEntry MAX-ACCESS不可访问
STATUS current DESCRIPTION "Entry in the EBN Directory Table."
状态当前描述“EBN目录表中的条目”
INDEX { ebnDirLuName }
索引{ebnDirLuName}
::= { ebnDirTable 1 }
::= { ebnDirTable 1 }
EbnDirEntry ::= SEQUENCE {
ebnDirLuName SnaNAUWildcardName,
ebnDirSubnetAffiliation INTEGER }
EbnDirEntry ::= SEQUENCE {
ebnDirLuName SnaNAUWildcardName,
ebnDirSubnetAffiliation INTEGER }
ebnDirLuName OBJECT-TYPE SYNTAX SnaNAUWildcardName MAX-ACCESS not-accessible STATUS current DESCRIPTION "Fully qualified network LU name in the domain of a serving network node. If this object has the same value as the appnDirLuName object in the APPN MIB, then the two objects are referring to the same LU."
ebnDirLuName对象类型语法SNANAUVERDIARNAME MAX-ACCESS不可访问状态当前描述“服务网络节点域中的完全限定网络LU名称。如果此对象与APPN MIB中的APNDIRLUNAME对象具有相同的值，则这两个对象引用的是相同的LU。”
::= { ebnDirEntry 1 }
::= { ebnDirEntry 1 }
ebnDirSubnetAffiliation OBJECT-TYPE SYNTAX INTEGER { native (1), nonNative (2), subarea (3) } MAX-ACCESS read-only STATUS current DESCRIPTION "Specifies the subnetwork affiliation of the LU: - native(1) : The LU is in the native APPN subnetwork. - nonNative(2) : The LU is in a non-native APPN subnetwork. - subarea(3) : The LU is in a subarea network."
ebnDirSubnetAffiliation对象类型语法整数{native（1）、nonNative（2）、subrea（3）}MAX-ACCESS只读状态当前描述”指定LU的子网从属关系：-native（1）：LU在本机APPN子网中。-nonNative（2）：LU在非本机APPN子网中。-subrea（3）：LU位于分区网络中。“
::= { ebnDirEntry 2 }
::= { ebnDirEntry 2 }
-- ******************************************************************
-- EBN Intermediate Session RSCV Group
-- This table is a sparse extension to the appnIsInTable. For
-- sessions crossing ISTGs adjacent to the EBN, it contains the RSCV
-- and COS used in the direction of the BIND destination.
-- ******************************************************************
-- ******************************************************************
-- EBN Intermediate Session RSCV Group
-- This table is a sparse extension to the appnIsInTable. For
-- sessions crossing ISTGs adjacent to the EBN, it contains the RSCV
-- and COS used in the direction of the BIND destination.
-- ******************************************************************
ebnIsRscv OBJECT IDENTIFIER ::= { ebnObjects 2 }
ebnIsRscv OBJECT IDENTIFIER ::= { ebnObjects 2 }
ebnIsRscvTable OBJECT-TYPE
ebnIsRscvTable对象类型
SYNTAX SEQUENCE OF EbnIsRscvEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The EBN Intermediate Session RSCV table. This table is an extension to the appnIsInTable. It contains the RSCV and COS used in the direction of the BIND destination. There is an entry in this table for each session that traverses an ISTG when it enters or leaves this EBN, with corresponding entries having identical values for their respective indexes."
EBNIRSCVENTRY MAX-ACCESS不可访问状态当前描述的语法顺序“EBN中间会话RSCV表。此表是appnIsInTable的扩展。它包含绑定目标方向上使用的RSCV和COS。当ISTG进入或离开此EBN时，该表中有一个条目用于每个会话，该会话通过ISTG，相应条目的各自索引值相同。”
::= { ebnIsRscv 1}
::= { ebnIsRscv 1}
ebnIsRscvEntry OBJECT-TYPE SYNTAX EbnIsRscvEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry in ebnIsRscvTable." INDEX { ebnIsRscvCpName, ebnIsRscvPcid }
EBNIRSCVENTRY对象类型语法EBNIRSCVENTRY MAX-ACCESS不可访问状态当前描述“EBNIRSCVTABLE中的条目”。索引{EBNIRSCVCPNAME，EBNIRSCVPCID}
::= { ebnIsRscvTable 1 }
::= { ebnIsRscvTable 1 }
EbnIsRscvEntry ::= SEQUENCE {
ebnIsRscvCpName SnaControlPointName,
ebnIsRscvPcid OCTET STRING,
ebnIsRscvDestinationRoute OCTET STRING,
ebnIsRscvDestinationCos DisplayString }
EbnIsRscvEntry ::= SEQUENCE {
ebnIsRscvCpName SnaControlPointName,
ebnIsRscvPcid OCTET STRING,
ebnIsRscvDestinationRoute OCTET STRING,
ebnIsRscvDestinationCos DisplayString }
ebnIsRscvCpName OBJECT-TYPE SYNTAX SnaControlPointName MAX-ACCESS not-accessible STATUS current DESCRIPTION "The network-qualified control point name of the node at which the session and PCID originated. For APPN and LEN nodes, this is either CP name of the APPN node at which the origin LU is located or the CP name of the NN serving the LEN node at which the origin LU is located. For DLUR resources it is the name of the owning SSCP.
EBNISRSCVCCPNAME对象类型语法SnaControlPointName MAX-ACCESS不可访问状态当前说明“会话和PCID起源的节点的网络限定控制点名称。对于APPN和LEN节点，这是源LU所在的APPN节点的CP名称或为源LU所在的LEN节点提供服务的NN的CP名称。对于DLUR资源，它是拥有SSCP的名称。
If this object has the same value as the appnIsInFqCpName object in the APPN MIB, then the two objects are referring to the same APPN control point."
如果此对象与APPN MIB中的appnIsInFqCpName对象具有相同的值，则这两个对象引用的是同一APPN控制点。“
::= { ebnIsRscvEntry 1 }
::= { ebnIsRscvEntry 1 }
ebnIsRscvPcid OBJECT-TYPE SYNTAX OCTET STRING (SIZE (8)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The procedure correlation identifier (PCID) of a session. It is an 8-octet value.
EBNISRSCVCPCID对象类型语法八位字节字符串（大小（8））MAX-ACCESS not ACCESS STATUS current DESCRIPTION“会话的过程相关标识符（PCID）。它是一个八位字节值。
If this object has the same value as the appnIsInPcid object in the APPN MIB, and if the corresponding ebnIsRscvCpName object has the same value as the corresponding appnIsInFqCpName object, then the entries indexed by these objects are referring to the same session."
如果此对象与APPN MIB中的appnIsInPcid对象具有相同的值，并且如果相应的ebnIsRscvCpName对象与相应的appnIsInFqCpName对象具有相同的值，则这些对象索引的条目引用的是同一会话。”
::= { ebnIsRscvEntry 2 }
::= { ebnIsRscvEntry 2 }
ebnIsRscvDestinationRoute OBJECT-TYPE SYNTAX OCTET STRING(SIZE (0..255)) MAX-ACCESS read-only
EBNISRSCVDESTIONROUTE对象类型语法八位字节字符串（大小（0..255））MAX-ACCESS只读
STATUS current DESCRIPTION "The route selection control vector (RSCV x'2B') used in the direction towards the SLU."
状态当前描述“在朝向SLU的方向上使用的路由选择控制向量（RSCV x'2B'）。”
::= { ebnIsRscvEntry 3 }
::= { ebnIsRscvEntry 3 }
ebnIsRscvDestinationCos OBJECT-TYPE SYNTAX DisplayString (SIZE (1..8)) MAX-ACCESS read-only STATUS current DESCRIPTION "The Class of Service (COS) name used in the direction towards the SLU.
EBNISRSCVDESTINATIONCS对象类型语法DisplayString（大小（1..8））MAX-ACCESS只读状态当前描述“在指向SLU的方向上使用的服务类（COS）名称。
Because the characters allowed in an SNA COS name come from a restricted character set, these names are not subject to internationalization."
由于SNA COS名称中允许的字符来自受限字符集，因此这些名称不受国际化限制。”
::= { ebnIsRscvEntry 4 }
::= { ebnIsRscvEntry 4 }
-- ******************************************************************
-- EBN Directory Config Group
-- The following simple objects provide information about EBN
-- directory.
-- ******************************************************************
-- ******************************************************************
-- EBN Directory Config Group
-- The following simple objects provide information about EBN
-- directory.
-- ******************************************************************
ebnDirConfig OBJECT IDENTIFIER ::= { ebnObjects 3 }
ebnDirConfig OBJECT IDENTIFIER ::= { ebnObjects 3 }
ebnSearchCacheTime OBJECT-TYPE SYNTAX Unsigned32 UNITS "minutes" MAX-ACCESS read-only STATUS current DESCRIPTION "The amount of time in minutes an extended border node will retain information about a multi-subnetwork search, once that that search terminates. A value 0 indicates that the EBN has no defined limit, and the number of entries is bounded only by memory."
ebnSearchCacheTime对象类型语法无符号32单位“分钟”最大访问只读状态当前说明“一旦搜索终止，扩展边界节点将保留有关多个子网络搜索的信息的时间（分钟）。值0表示EBN没有定义的限制，条目数仅由内存限制。”
::= { ebnDirConfig 1 }
::= { ebnDirConfig 1 }
ebnMaxSearchCache OBJECT-TYPE SYNTAX Unsigned32 UNITS "entries" MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of multi-subnet entries to be cached. The value 0 indicates that the local node has no defined limit, and the number of entries is bounded only by memory."
ebnMaxSearchCache对象类型语法Unsigned32单元“条目”MAX-ACCESS只读状态当前描述“要缓存的多子网条目的最大数量。值0表示本地节点没有定义的限制，条目数量仅受内存限制。”
::= { ebnDirConfig 2 }
::= { ebnDirConfig 2 }
ebnDefaultSubnetVisitCount OBJECT-TYPE SYNTAX Unsigned32 UNITS "topology subnetworks" MAX-ACCESS read-only STATUS current DESCRIPTION "The default maximum number of subnetworks a LOCATE search procedure may traverse."
ebnDefaultSubnetVisitCount对象类型语法Unsigned32单元“拓扑子网”MAX-ACCESS只读状态当前描述“定位搜索过程可以遍历的默认最大子网数。”
::= { ebnDirConfig 3 }
::= { ebnDirConfig 3 }
-- ******************************************************************
-- EBN COS Mapping Group
-- The ebnCosMap Table specifies how non-native COS values are mapped
-- to COS values defined in the native subnetwork. The COS mappings
-- that an EBN performs are determined by multiple factors, one of
-- which is a set of user-defined mappings. This table returns the
-- COS mappings that the EBN is actually performing, rather than
-- the user-defined mappings.
-- ******************************************************************
-- ******************************************************************
-- EBN COS Mapping Group
-- The ebnCosMap Table specifies how non-native COS values are mapped
-- to COS values defined in the native subnetwork. The COS mappings
-- that an EBN performs are determined by multiple factors, one of
-- which is a set of user-defined mappings. This table returns the
-- COS mappings that the EBN is actually performing, rather than
-- the user-defined mappings.
-- ******************************************************************
ebnCOS OBJECT IDENTIFIER ::= { ebnObjects 4 }
ebnCOS OBJECT IDENTIFIER ::= { ebnObjects 4 }
ebnCosMapTable OBJECT-TYPE SYNTAX SEQUENCE OF EbnCosMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The EBN COS Mapping Table. This table specifies how non-native COS values are mapped to COS values defined in the native subnetwork.
EBNCOSMPENTRY MAX-ACCESS的ebnCosMapTable对象类型语法序列不可访问状态当前描述“EBN COS映射表。此表指定如何将非本机COS值映射到本机子网中定义的COS值。
Note: The COS mappings that an EBN performs are determined by multiple factors, one of which is a set of user-defined initial mappings. This table returns the COS mappings that the EBN is actually performing at the time it is queried, rather than the user-defined initial ones."
注意：EBN执行的COS映射由多个因素决定，其中一个因素是一组用户定义的初始映射。此表返回EBN在查询时实际执行的COS映射，而不是用户定义的初始映射。”
::= { ebnCOS 1 }
::= { ebnCOS 1 }
ebnCosMapEntry OBJECT-TYPE SYNTAX EbnCosMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the EBN COS Mapping table."
ebnCosMapEntry对象类型语法ebnCosMapEntry MAX-ACCESS不可访问状态当前描述“EBN COS映射表中的一个条目。”
INDEX { ebnCosMapCpName, ebnCosMapNonNativeCos }
索引{ebnCosMapCpName，ebnCosMapNonNativeCos}
::= { ebnCosMapTable 1 }
::= { ebnCosMapTable 1 }
EbnCosMapEntry ::= SEQUENCE {
ebnCosMapCpName SnaNAUWildcardName,
ebnCosMapNonNativeCos DisplayString,
ebnCosMapNativeCos DisplayString }
EbnCosMapEntry ::= SEQUENCE {
ebnCosMapCpName SnaNAUWildcardName,
ebnCosMapNonNativeCos DisplayString,
ebnCosMapNativeCos DisplayString }
ebnCosMapCpName OBJECT-TYPE SYNTAX SnaNAUWildcardName MAX-ACCESS not-accessible STATUS current DESCRIPTION "Fully qualified network CP name for which the COS mapping applies."
ebnCosMapCpName对象类型语法SNANAUVERDICARDNAME MAX-ACCESS不可访问状态当前描述“应用COS映射的完全限定网络CP名称”
::= { ebnCosMapEntry 1 }
::= { ebnCosMapEntry 1 }
ebnCosMapNonNativeCos OBJECT-TYPE SYNTAX DisplayString (SIZE(1..8))
ebnCosMapNonNativeCos对象类型语法显示字符串（大小（1..8））
MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object contains one of the following values:
MAX-ACCESS不可访问状态当前描述“此对象包含以下值之一：
- An 8-character COS name used in a non-native subnetwork. - The single character '*', identifying the entry with the default native COS for a non-native CP name. This entry is used when there is no entry in the table for a non-native CP name / non-native COS pair.
- 非本机子网中使用的8个字符的COS名称。-单个字符“*”，用非本机CP名称的默认本机COS标识条目。当表中没有非本机CP名称/非本机COS对的条目时，使用此条目。
Because the characters allowed in an SNA COS name come from a restricted character set, these names are not subject to internationalization."
由于SNA COS名称中允许的字符来自受限字符集，因此这些名称不受国际化限制。”
::= { ebnCosMapEntry 2 }
::= { ebnCosMapEntry 2 }
ebnCosMapNativeCos OBJECT-TYPE SYNTAX DisplayString (SIZE(1..8)) MAX-ACCESS read-only STATUS current DESCRIPTION "An 8-byte name for the class-of-service, as known in the native subnetwork.
ebnCosMapNativeCos对象类型语法DisplayString（大小（1..8））MAX-ACCESS只读状态当前描述“本机子网中已知的服务类的8字节名称。
Because the characters allowed in an SNA COS name come from a restricted character set, these names are not subject to internationalization."
由于SNA COS名称中允许的字符来自受限字符集，因此这些名称不受国际化限制。”
::= { ebnCosMapEntry 3 }
::= { ebnCosMapEntry 3 }
-- ******************************************************************
-- EBN Subnet Routing List Group
-- The EBN Subnet Routing List indicates to which nodes an EBN
-- forwards search request. This group contains information
-- pertaining to the CONFIGURED Subnet Routing List at an EBN. How a
-- particular search request is routed is determined by a transient
-- list that the EBN creates based on the configured list and other
-- factors.
-- *******************************************************************
-- ******************************************************************
-- EBN Subnet Routing List Group
-- The EBN Subnet Routing List indicates to which nodes an EBN
-- forwards search request. This group contains information
-- pertaining to the CONFIGURED Subnet Routing List at an EBN. How a
-- particular search request is routed is determined by a transient
-- list that the EBN creates based on the configured list and other
-- factors.
-- *******************************************************************
ebnSubnetRoutingList OBJECT IDENTIFIER ::= { ebnObjects 5 }
ebnSubnetRoutingList OBJECT IDENTIFIER ::= { ebnObjects 5 }
ebnSubnetSearchTable OBJECT-TYPE SYNTAX SEQUENCE OF EbnSubnetSearchEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION
EbnSubnetSearchEntry的ebnSubnetSearchTable对象类型语法序列MAX-ACCESS不可访问状态当前说明
"This table contains one entry for each fully qualified LU name for which an associated subnet routing list has been defined. An entry in this table contains general characteristics of the subnet search routing list for an LU name. The routing list itself is represented by a set of contiguous entries in the ebnSearchTable."
“此表包含定义了关联子网路由列表的每个完全限定LU名称的一个条目。此表中的条目包含LU名称的子网搜索路由列表的一般特征。路由列表本身由EBNSearch表中的一组连续条目表示。”
::= { ebnSubnetRoutingList 1 }
::= { ebnSubnetRoutingList 1 }
ebnSubnetSearchEntry OBJECT-TYPE SYNTAX EbnSubnetSearchEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry for the ebnSubnetSearchTable. The entry represents the configured parameters the EBN uses when it is determining how to search for the LU identified by the ebnSubnetSearchLuName object."
ebnSubnetSearchEntry对象类型语法ebnSubnetSearchEntry MAX-ACCESS不可访问状态当前描述“ebnSubnetSearchTable的条目。该条目表示EBN在确定如何搜索ebnSubnetSearchLuName对象标识的LU时使用的配置参数。”
INDEX { ebnSubnetSearchLuName }
索引{ebnSubnetSearchLuName}
::= { ebnSubnetSearchTable 1 }
::= { ebnSubnetSearchTable 1 }
EbnSubnetSearchEntry ::= SEQUENCE {
ebnSubnetSearchLuName SnaNAUWildcardName,
ebnSubnetSearchDynamics INTEGER,
ebnSubnetSearchOrdering INTEGER }
EbnSubnetSearchEntry ::= SEQUENCE {
ebnSubnetSearchLuName SnaNAUWildcardName,
ebnSubnetSearchDynamics INTEGER,
ebnSubnetSearchOrdering INTEGER }
ebnSubnetSearchLuName OBJECT-TYPE SYNTAX SnaNAUWildcardName MAX-ACCESS not-accessible STATUS current DESCRIPTION "Fully qualified network LU name."
ebnSubnetSearchLuName对象类型语法SNANUAULDICARDNAME MAX-ACCESS不可访问状态当前描述“完全限定的网络LU名称”
::= { ebnSubnetSearchEntry 1 }
::= { ebnSubnetSearchEntry 1 }
ebnSubnetSearchDynamics OBJECT-TYPE SYNTAX INTEGER { none(1), limited (2), full (3) } MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates whether an EBN may add dynamic entries to a subnetwork routing list. none(1) means no entries may be added to the subnetwork routing list. limited(2) means only likely entries may be added to the subnetwork routing
ebnSubnetSearchDynamics对象类型语法整数{none（1）、limited（2）、full（3）}MAX-ACCESS只读状态当前描述”表示EBN是否可以向子网路由列表添加动态条目。none（1）表示不能向子网路由列表添加条目。limited（2）意味着只有可能的条目可以添加到子网路由
list. full(3) means all native extended border nodes and adjacent, non-native EBNs and NNs will be added to the subnetwork routing list."
列表完整（3）表示所有本机扩展边界节点和相邻的非本机EBN和NN将添加到子网路由列表中。”
::= { ebnSubnetSearchEntry 2 }
::= { ebnSubnetSearchEntry 2 }
ebnSubnetSearchOrdering OBJECT-TYPE SYNTAX INTEGER{ priority(1), defined(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates whether an EBN may reorder a subnetwork routing list so that entries which are more likely to be successful move to the top of the subnetwork routing list and entries which are more likely to be unsuccessful move to the bottom of the list. The following values are defined:
ebnSubnetSearchOrdering对象类型语法整数{优先级（1），已定义（2）}MAX-ACCESS只读状态当前说明“指示EBN是否可以重新排列子网路由列表，以便更有可能成功的条目移动到子网路由列表的顶部，而更有可能不成功的条目移动到列表的底部。”。定义了以下值：
- priority(1): Entries may be reordered. - defined(2): Entries must not be reordered."
- 优先级（1）：条目可以重新排序。-已定义（2）：条目不得重新排序。“
::= { ebnSubnetSearchEntry 3 }
::= { ebnSubnetSearchEntry 3 }
-- Border node search table
--边界节点搜索表
ebnSearchTable OBJECT-TYPE SYNTAX SEQUENCE OF EbnSearchEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table indicates the CONFIGURED list of control points to which the EBN sends Locate searches for a given fully qualified LU name. Each entry in the table indicates one control point that should be included in a multi-subnet search for a particular LU name."
EbnSearchEntry MAX-ACCESS的ebnSearchTable对象类型语法序列不可访问状态当前描述“此表表示EBN向其发送给定完全限定LU名称的定位搜索的控制点配置列表。表中的每个条目表示一个控制点，该控制点应包含在特定LU名称的多子网搜索中。”
::= { ebnSubnetRoutingList 2 }
::= { ebnSubnetRoutingList 2 }
ebnSearchEntry OBJECT-TYPE SYNTAX EbnSearchEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the ebnSearchTable. An entry can exist in this table only if an entry exists in the ebnSubnetSearchTable with an ebnSubnetSearchLuName value matching this entry's ebnSearchLuName.
EBNSARCHENTRY对象类型语法EBNSARCHENTRY MAX-ACCESS not ACCESS STATUS current DESCRIPTION“ebnSearchTable中的一个条目。只有当ebnSubnetSearchTable中存在一个条目且其ebnSubnetSearchLuName值与该条目的EBNSARCHLUNAME匹配时，该条目才能存在于该表中。
For a given ebnSearchLuName value, the ordering of entries provides by the ebnSearchIndex values corresponds to the order in which the control points to be searched appear in the CONFIGURED search list for the ebnSearchLuName."
对于给定的ebnSearchLuName值，ebnSearchIndex值提供的条目顺序与要搜索的控制点在ebnSearchLuName的配置搜索列表中出现的顺序相对应。”
INDEX { ebnSearchLuName, ebnSearchIndex }
索引{ebnSearchLuName，ebnSearchIndex}
::= { ebnSearchTable 1 }
::= { ebnSearchTable 1 }
EbnSearchEntry ::= SEQUENCE {
ebnSearchLuName SnaNAUWildcardName,
ebnSearchIndex Unsigned32,
ebnSearchCpName DisplayString,
ebnSearchSNVC Unsigned32 }
EbnSearchEntry ::= SEQUENCE {
ebnSearchLuName SnaNAUWildcardName,
ebnSearchIndex Unsigned32,
ebnSearchCpName DisplayString,
ebnSearchSNVC Unsigned32 }
ebnSearchLuName OBJECT-TYPE SYNTAX SnaNAUWildcardName MAX-ACCESS not-accessible STATUS current DESCRIPTION "Fully qualified network LU name. If this object has the same value as the ebnSubnetSearchLuName object, then the two objects are referring to the same LU."
ebnSearchLuName对象类型语法SNANAUVERDICARDNAME MAX-ACCESS不可访问状态当前描述“完全限定的网络LU名称。如果此对象与ebnSubnetSearchLuName对象具有相同的值，则这两个对象引用的是同一LU。”
::= { ebnSearchEntry 1 }
::= { ebnSearchEntry 1 }
ebnSearchIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "Secondary index enumerating the CONFIGURED order in which a search is forwarded to CPs for a particular LU name. The order for an actual search is determined dynamically by the EBN, based on this configured information and on other factors, including whether search dynamics and search ordering are enabled. Information on these last two settings is available in, respectively, the ebnSubnetSearchDynamics and ebnSubnetSearch ordering objects."
ebnSearchIndex对象类型语法Unsigned32 MAX-ACCESS不可访问状态当前说明“二级索引，枚举针对特定LU名称向CPs转发搜索的配置顺序。实际搜索的顺序由EBN根据此配置信息和其他因素（包括是否启用搜索动态和搜索顺序）动态确定。有关最后两个设置的信息分别在ebnSubnetSearchDynamics和ebnSubnetSearch排序对象中提供。”
::= { ebnSearchEntry 2 }
::= { ebnSearchEntry 2 }
ebnSearchCpName OBJECT-TYPE SYNTAX DisplayString(SIZE(1..17)) MAX-ACCESS read-only STATUS current DESCRIPTION
ebnSearchCpName对象类型语法DisplayString（大小（1..17））MAX-ACCESS只读状态当前说明
"This object specifies the CP(s) to which a search should be forwarded. It either follows the SnaNAUWildcardName textual convention or takes one of the following special formats:
“此对象指定搜索应转发到的CP。它遵循SNANAUVERDICARDNAME文本约定或采用以下特殊格式之一：
'*' indicates that all native EBNs and all adjacent non-native EBNs and NNs may be added to the routing list dynamically,
“*”表示可以将所有本机EBN和所有相邻的非本机EBN和NN动态添加到路由列表中，
'*SELF' indicates that the EBN should search itself and its native subnetwork at this time during the cross-subnet search,
“*SELF”表示在跨子网搜索期间，EBN此时应搜索自身及其本机子网，
'*EBNS' indicates all native EBNs.
“*EBN”表示所有本机EBN。
Because the characters allowed in a CP name come from a restricted character set, and because the three formats listed here use no special characters, this object is not subject to internationalization."
由于CP名称中允许的字符来自受限字符集，并且此处列出的三种格式不使用特殊字符，因此此对象不受国际化的约束。”
::= { ebnSearchEntry 3 }
::= { ebnSearchEntry 3 }
ebnSearchSNVC OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of subnets a Locate search procedure may traverse. "
ebnSearchSNVC对象类型语法Unsigned32 MAX-ACCESS只读状态当前说明“定位搜索过程可以遍历的最大子网数。”
::= { ebnSearchEntry 4 }
::= { ebnSearchEntry 4 }
-- *******************************************************************
-- HPR Extended Border Node Intermediate Session Group
-- The hbnIsInTable is a sparse extension to the appnIsInTable.
-- For sessions that use back-to-back RTP connections in an HBN,
-- this table provides the network connection endpoint identifier
-- (NceId) and the transport connection identifier (Tcid) for the
-- second RTP connection.
-- *******************************************************************
-- *******************************************************************
-- HPR Extended Border Node Intermediate Session Group
-- The hbnIsInTable is a sparse extension to the appnIsInTable.
-- For sessions that use back-to-back RTP connections in an HBN,
-- this table provides the network connection endpoint identifier
-- (NceId) and the transport connection identifier (Tcid) for the
-- second RTP connection.
-- *******************************************************************
hbn OBJECT IDENTIFIER ::= { ebnObjects 6 }
hbn OBJECT IDENTIFIER ::= { ebnObjects 6 }
hbnIsInTable OBJECT-TYPE SYNTAX SEQUENCE OF HbnIsInEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The HBN Intermediate Session table."
HBNISTANTERY MAX-ACCESS的HBNISTABLE对象类型语法序列不可访问状态当前描述“HBN中间会话表”
::= { hbn 1}
::= { hbn 1}
hbnIsInEntry OBJECT-TYPE SYNTAX HbnIsInEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry of the HBN Intermediate Session Table. An entry exists in this table for every intermediate session being routed between back-to-back RTP connections in the HBN.
HBNISTRY对象类型语法HBNISTRY MAX-ACCESS not ACCESS STATUS current DESCRIPTION“HBN中间会话表的条目。此表中存在HBN中背对背RTP连接之间路由的每个中间会话的条目。
When an entry for a session exists in this table, the NceIds and Tcids for the back-to-back RTP connections are made available in the following four objects:
当此表中存在会话条目时，背对背RTP连接的NCEID和TCID在以下四个对象中可用：
RTP connection in the direction of the PLU: - NceId: appnIsInRtpNceId (in the APPN MIB) - Tcid: appnIsinRtpTcid (in the APPN MIB).
PLU方向的RTP连接：-NceId:appnIsInRtpNceId（在APPNMIB中）-Tcid:APPNISINRTPTID（在APPNMIB中）。
RTP connection in the direction of the SLU:
- NceId: hbnIsInRtpNceId (in this table)
- Tcid: hbnIsInRtpTcid (in this table)."
RTP connection in the direction of the SLU:
- NceId: hbnIsInRtpNceId (in this table)
- Tcid: hbnIsInRtpTcid (in this table)."
INDEX { hbnIsInFqCpName, hbnIsInPcid }
索引{hbnIsInFqCpName，hbnIsInPcid}
::= { hbnIsInTable 1 }
::= { hbnIsInTable 1 }
HbnIsInEntry ::= SEQUENCE {
hbnIsInFqCpName SnaControlPointName,
hbnIsInPcid OCTET STRING,
hbnIsInRtpNceId OCTET STRING,
hbnIsInRtpTcid OCTET STRING }
HbnIsInEntry ::= SEQUENCE {
hbnIsInFqCpName SnaControlPointName,
hbnIsInPcid OCTET STRING,
hbnIsInRtpNceId OCTET STRING,
hbnIsInRtpTcid OCTET STRING }
hbnIsInFqCpName OBJECT-TYPE SYNTAX SnaControlPointName MAX-ACCESS not-accessible STATUS current DESCRIPTION "The network-qualified control point name of the node at which the session and PCID originated. For APPN and LEN nodes, this is either the CP name of the APPN node at which the origin LU is located or the CP name of the NN serving the LEN node at which the origin LU is located.
hbnIsInFqCpName对象类型语法SnaControlPointName MAX-ACCESS不可访问状态当前说明“会话和PCID起源的节点的网络限定控制点名称。对于APPN和LEN节点，这是源LU所在APPN节点的CP名称或为源LU所在LEN节点提供服务的NN的CP名称。
If this object has the same value as the appnIsInFqCpName object in the APPN MIB, then the two objects are referring to the same APPN control point."
如果此对象与APPN MIB中的appnIsInFqCpName对象具有相同的值，则这两个对象引用的是同一APPN控制点。“
::= { hbnIsInEntry 1 }
::= { hbnIsInEntry 1 }
hbnIsInPcid OBJECT-TYPE SYNTAX OCTET STRING (SIZE(8)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The procedure correlation identifier (PCID) of a session. It is an 8-octet value.
HBNISINCID对象类型语法八位字节字符串（大小（8））MAX-ACCESS not ACCESS STATUS current DESCRIPTION“会话的过程相关标识符（PCID）。它是一个八位字节值。
If this object has the same value as the appnIsInPcid object in the APPN MIB, and if the corresponding hbnIsInFqCpName object has the same value as the corresponding appnIsInFqCpName object, then the entries indexed by these objects are referring to the same session."
如果此对象与APPN MIB中的appnIsInPcid对象具有相同的值，并且如果相应的hbnIsInFqCpName对象与相应的appnIsInFqCpName对象具有相同的值，则这些对象索引的条目引用的是同一会话。”
::= { hbnIsInEntry 2 }
::= { hbnIsInEntry 2 }
hbnIsInRtpNceId OBJECT-TYPE SYNTAX OCTET STRING (SIZE(1..8)) MAX-ACCESS read-only STATUS current DESCRIPTION "The HPR local Network Connection Endpoint of the session in the direction of the SLU."
hbnIsInRtpNceId对象类型语法八位字节字符串（大小（1..8））MAX-ACCESS只读状态当前描述“SLU方向会话的HPR本地网络连接端点”
::= { hbnIsInEntry 3 }
::= { hbnIsInEntry 3 }
hbnIsInRtpTcid OBJECT-TYPE SYNTAX OCTET STRING (SIZE(8)) MAX-ACCESS read-only STATUS current DESCRIPTION "The RTP connection local TCID of the session in the direction of the SLU."
hbnIsInRtpTcid对象类型语法八位字节字符串（大小（8））MAX-ACCESS只读状态当前描述“SLU方向会话的RTP连接本地TCID。”
::= { hbnIsInEntry 4 }
::= { hbnIsInEntry 4 }
-- *******************************************************************
-- Conformance Statement
-- *******************************************************************
ebnConformance OBJECT IDENTIFIER ::= { ebnMIB 2 }
-- *******************************************************************
-- Conformance Statement
-- *******************************************************************
ebnConformance OBJECT IDENTIFIER ::= { ebnMIB 2 }
ebnCompliances OBJECT IDENTIFIER ::= { ebnConformance 1 }
ebnGroups OBJECT IDENTIFIER ::= { ebnConformance 2 }
ebnCompliances OBJECT IDENTIFIER ::= { ebnConformance 1 }
ebnGroups OBJECT IDENTIFIER ::= { ebnConformance 2 }
-- Compliance statements ebnCompliance MODULE-COMPLIANCE
--合规性声明EBN合规性模块-合规性
STATUS current DESCRIPTION "The compliance statement for the SNMPv2 entities which implement the ebnMIB."
状态当前描述“实施ebnMIB的SNMPv2实体的合规性声明。”
MODULE -- this module
模块——这个模块
-- Unconditionally mandatory groups
MANDATORY-GROUPS {
ebnDirectoryGroup,
ebnIsRscvGroup,
ebnDirectoryConfigGroup,
ebnCosMappingGroup,
ebnSubnetRoutingListGroup }
-- Unconditionally mandatory groups
MANDATORY-GROUPS {
ebnDirectoryGroup,
ebnIsRscvGroup,
ebnDirectoryConfigGroup,
ebnCosMappingGroup,
ebnSubnetRoutingListGroup }
-- Conditionally mandatory groups GROUP hbnIsInGroup DESCRIPTION "The hbnIsInGroup is mandatory only for HPR extended border nodes."
--条件强制组组hbnIsInGroup DESCRIPTION“hbnIsInGroup仅对HPR扩展边界节点是强制的。”
::= {ebnCompliances 1 }
::= {ebnCompliances 1 }
-- Group definitions ebnDirectoryGroup OBJECT-GROUP OBJECTS { ebnDirSubnetAffiliation } STATUS current DESCRIPTION "The EBN-related directory objects."
--组定义ebnDirectoryGroup对象组对象{ebnDirSubnetAffiliation}状态当前描述“与EBN相关的目录对象”
::= { ebnGroups 1 }
::= { ebnGroups 1 }
ebnIsRscvGroup OBJECT-GROUP OBJECTS { ebnIsRscvDestinationRoute, ebnIsRscvDestinationCos } STATUS current DESCRIPTION "Two objects representing RSCV and class of service information saved by an EBN."
ebnIsRscvGroup OBJECT-GROUP OBJECTS{ebnIsRscvDestinationRoute，ebnIsRscvDestinationCos}状态当前描述“两个表示由EBN保存的RSCV和服务信息类的对象。”
::= { ebnGroups 2 }
::= { ebnGroups 2 }
ebnDirectoryConfigGroup OBJECT-GROUP OBJECTS { ebnSearchCacheTime, ebnMaxSearchCache, ebnDefaultSubnetVisitCount } STATUS current
ebnDirectoryConfigGroup对象组对象{ebnSearchCacheTime，ebnMaxSearchCache，ebnDefaultSubnetVisitCount}状态当前
DESCRIPTION "The EBN Directory Configuration Group."
说明“EBN目录配置组”
::= { ebnGroups 3 }
::= { ebnGroups 3 }
ebnCosMappingGroup OBJECT-GROUP OBJECTS { ebnCosMapNativeCos } STATUS current DESCRIPTION "The EBN COS Mapping Group."
ebnCosMappingGroup对象组对象{EBNCOSMappingGroupObjects}状态当前描述“EBN COS映射组”
::= { ebnGroups 4 }
::= { ebnGroups 4 }
ebnSubnetRoutingListGroup OBJECT-GROUP OBJECTS { ebnSubnetSearchDynamics, ebnSubnetSearchOrdering, ebnSearchCpName, ebnSearchSNVC } STATUS current DESCRIPTION "The Subnet Routing List Group."
ebnSubnetRoutingListGroup对象组对象{ebnSubnetSearchDynamics，ebnSubnetSearchOrdering，ebnSearchCpName，ebnSearchSNVC}状态当前描述“子网路由列表组”
::= { ebnGroups 5 }
::= { ebnGroups 5 }
hbnIsInGroup OBJECT-GROUP OBJECTS { hbnIsInRtpNceId, hbnIsInRtpTcid } STATUS current DESCRIPTION "The HBN-related Intermediate Session Objects."
hbnIsInGroup对象组对象{hbnIsInRtpNceId，hbnIsInRtpTcid}状态当前描述“与HBN相关的中间会话对象”
::= { ebnGroups 6 }
::= { ebnGroups 6 }
END
终止
Certain management information defined in this MIB may be considered sensitive in some network environments. Therefore, authentication of received SNMP requests and controlled access to management information SHOULD be employed in such environments. An authentication protocol is defined in [10]. A protocol for access control is defined in [11].
在某些网络环境中，此MIB中定义的某些管理信息可能被视为敏感信息。因此，在这样的环境中，应该对接收到的SNMP请求进行身份验证，并控制对管理信息的访问。[10]中定义了认证协议。[11]中定义了访问控制协议。
None of the read-only objects in the EBN 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;
EBN MIB中的只读对象都不会报告密码、用户数据或任何其他特别敏感的内容。一些企业将其网络配置本身以及有关网络使用和性能的信息视为企业资产；
such enterprises may wish to restrict SNMP access to most of the objects in the MIB.
此类企业可能希望限制对MIB中大多数对象的SNMP访问。
There are no read-write objects in the EBN MIB.
EBN MIB中没有读写对象。
The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF Secretariat.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何努力来确定任何此类权利。有关IETF在标准跟踪和标准相关文件中权利的程序信息，请参见BCP-11。可从IETF秘书处获得可供发布的权利声明副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果。
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涉及实施本标准所需技术的专有权利。请将信息发送给IETF执行董事。
This MIB module is the product of the IETF SNA NAU MIB WG and the AIW APPN/HPR MIBs SIG. Thanks to Dave Billing, Cisco Systems; Katie Lee, IBM Corporation; and Marcia Peters, IBM Corporation, for their contributions and review.
该MIB模块是IETF SNA NAU MIB WG和AIW APPN/HPR MIBs SIG的产品。感谢思科系统公司的Dave Billing；李凯蒂,IBM公司,；以及IBM公司的Marcia Peters，感谢他们的贡献和评论。
[1] Case, J., Fedor, M. Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[1] Case，J.，Fedor，M.Schoffstall，M.和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[2] McCloghrie, K., and M. Rose, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, March 1991.
[2] McCloghrie，K.和M.Rose，“基于TCP/IP的互联网网络管理的管理信息库：MIB-II”，STD 17，RFC 1213，1991年3月。
[3] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996.
[3] Case，J.，McCloghrie，K.，Rose，M.，和Waldbusser S.，“简单网络管理协议（SNMPv2）版本2的管理信息结构”，RFC 1902，1996年1月。
[4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[4] Case，J.，McCloghrie，K.，Rose，M.，和Waldbusser，S.，“简单网络管理协议（SNMPv2）版本2的文本约定”，RFC 1903，1996年1月。
[5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[5] Case，J.，McCloghrie，K.，Rose，M.，和Waldbusser，S.，“简单网络管理协议（SNMPv2）版本2的一致性声明”，RFC 1904，1996年1月。
[6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[6] Case，J.，McCloghrie，K.，Rose，M.，和Waldbusser，S.，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[7] Harrington D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2271, January 1998.
[7] Harrington D.，Presohn，R.和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2271，1998年1月。
[8] Harrington D., Presuhn, R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2272, January 1998.
[8] Harrington D.，Presohn，R.和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 2272，1998年1月。
[9] Levi D., Meyer P. and B. Stewart, "SNMPv3 Applications", RFC 2273, January 1998.
[9] Levi D.，Meyer P.和B.Stewart，“SNMPv3应用”，RFC 2273，1998年1月。
[10] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2274, January 1998.
[10] Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版的基于用户的安全模型（USM）”，RFC 22741998年1月。
[11] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2275, January 1998.
[11] Wijnen，B.，Presuhn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC 22751998年1月。
[12] Hovey, R. and S. Bradner, "The Organizations Involved in the IETF Standards Process", BCP 11, RFC 2028, October 1996.
[12] Hovey，R.和S.Bradner，“参与IETF标准过程的组织”，BCP 11，RFC 2028，1996年10月。
[13] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[13] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[14] Clouston, B. and B. Moore, "Definition of Managed Objects for APPN", RFC 2455, November 1998.
[14] Clouston，B.和B.Moore，“APPN管理对象的定义”，RFC 2455，1998年11月。
[15] IBM, APPN Extended Border Node Architecture Reference Version 1.0, available only via anonymous FTP at networking.raleigh.ibm.com, as /pub/standards/aiw/appn/bordernode/ebn4.psbin.
[15] IBM，APPN扩展边界节点体系结构参考版本1.0，仅通过networking.raleigh.IBM.com上的匿名FTP提供，如/pub/standards/aiw/APPN/bordernode/ebn4.psbin。
[16] IBM, SNA/MS Formats, GC31-8302-01
[16] IBM，SNA/MS格式，GC31-8302-01
Bob Clouston Cisco Systems 7025 Kit Creek Road P.O. Box 14987 Research Triangle Park, NC 27709, USA
Bob Clouston Cisco Systems 7025 Kit Creek Road美国北卡罗来纳州三角研究公园14987号邮政信箱，邮编27709
Phone: +1-919-472-2333
EMail: clouston@cisco.com
Phone: +1-919-472-2333
EMail: clouston@cisco.com
Robert Moore Dept. BRQA/Bldg. 501/G114 IBM Corporation P.O.Box 12195 3039 Cornwallis Research Triangle Park, NC 27709, USA
美国北卡罗来纳州康沃利斯研究三角公园12195 3039号IBM公司信箱501/G114号楼BRQA/BRQA部门
Phone: +1-919-254-4436
EMail: remoore@us.ibm.com
Phone: +1-919-254-4436
EMail: remoore@us.ibm.com
Copyright (C) The Internet Society (1998). All Rights Reserved.
版权所有（C）互联网协会（1998年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。