RFC2457 日本語訳
2457 Definitions of Managed Objects for Extended Border Node. B.Clouston, B. Moore. November 1998. (Format: TXT=54380 bytes) (Status: PROPOSED STANDARD)
プログラムでの自動翻訳です。
英語原文
Network Working Group B. Clouston
Request for Comments: 2457 Cisco Systems
Category: Standards Track B. Moore
IBM Corporation
November 1998
Cloustonがコメントのために要求するワーキンググループB.をネットワークでつないでください: 2457年のシスコシステムズカテゴリ: 標準化過程B.ムーアIBM社の1998年11月
Definitions of Managed Objects
for Extended Border Node
敷衍された境界ノードのための管理オブジェクトの定義
Status of this Memo
この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.
このドキュメントは、インターネットコミュニティにインターネット標準化過程プロトコルを指定して、改良のために議論と提案を要求します。 このプロトコルの標準化状態と状態への「インターネット公式プロトコル標準」(STD1)の現行版を参照してください。 このメモの分配は無制限です。
Copyright Notice
版権情報
Copyright (C) The Internet Society (1998). All Rights Reserved.
Copyright(C)インターネット協会(1998)。 All rights reserved。
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.
ネットワーク管理プロトコルがインターネットコミュニティにある状態で、このメモは使用のために、Management Information基地の一部(MIB)を定義します。 特に、それは、APPN(高度なPeer-to-Peerネットワーク)EBN(拡張Border Node)能力でネットワーク装置をモニターして、制御するために物を定義します。 このメモは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 SNMP Network Management Framework. . . . . . . . . . 2 3.0Overview. . . . . . . . . . . . . . . . . . . . . . . . . 3 3.1EBN MIB Structure. . . . . . . . . . . . . . . . . . . . 4 3.1.1enbDirグループ.53.1.2ebnIsRscvグループ.53.1.3ebnDirConfigグループ. . . . . . . . . . . . . . . . . . 7 3.1.4ebnCosが分類する序論. . . . . . . . . . . . . . . . . . . . . . . 2 2.0…; . . . . . . . . . . . . . 8 3.1.5 ebnSubnetRoutingListグループ.83.1.6hbnグループの.84.0Definitions. . . . . . . . . . . . . . . . . . . . . . . 9 5.0のSecurity Considerations. . . . . . . . . . . . . . . . . 24 6.0Intellectual Property. . . . . . . . . . . . . . . . . . 25 7.0Acknowledgments. . . . . . . . . . . . . . . . . . . . . 25 8.0References. . . . . . . . . . . . . . . . . . . . . . . . 25
Clouston & Moore Standards Track [Page 1] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[1ページ]RFC2457
9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 27 10.0 Full Copyright Statement . . . . . . . . . . . . . . . . 28
作者の9.0のものが.27 10.0の完全な著作権宣言文. . . . . . . . . . . . . . . . 28を記述します。
1.0 Introduction
1.0 序論
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 Services MIB作業部会の製品です。 それはAdvanced Peerから同輩へのNetworking(APPN)の拡張Border Node(EBN)能力で装置を管理するためのMIBモジュールを定義します。
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].
キーワード“MUST"、「必須NOT」が「必要です」、“SHALL"、「」、“SHOULD"、「「推薦され」て、「5月」の、そして、「任意」のNOTがRFC2119で説明されるように本書では解釈されることであるなら、[13]に参照をつけてくださいだろう。
2.0 The SNMP Network Management Framework
2.0 SNMPネットワークマネージメント枠組み
The SNMP Network Management Framework presently consists of six major components. They are:
SNMP Network Management Frameworkは現在、6個の主要コンポーネントから成ります。 それらは以下の通りです。
o the overall architecture, described in RFC 2271 [7].
o RFC2271[7]で説明された総合的な構造。
o the SMI, described in RFC 1902 [3], - the mechanisms used for
describing and naming objects for the purpose of management.
o RFC1902[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、STD17、RFC1213[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 プロトコル、STD15、RFC1157[1]、RFC1905[6]、そして/または、RFC2272[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].
原文のコンベンションはRFC1903[4]で定義されます、そして、順応声明はRFC1904[5]で定義されます。 一般的なアプリケーションはRFC2273[9]で定義されます。
The Framework permits new objects to be defined for the purpose of experimentation and evaluation.
Frameworkは、新しい物が実験と評価の目的のために定義されるのを可能にします。
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は生産できます。
Clouston & Moore Standards Track [Page 2] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[2ページ]RFC2457
3.0 Overview
3.0 概観
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能力で装置の構成とアクティブな特性をモニターするために提案されたセットの物を特定します。 Extended Border Node機能は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を通して接続されるネットワークでは、別の企業のネットワークトラフィックから企業を保護するのも望ましいかもしれません。 EBNsは、顧客にそのようなネットワークトラフィックを減少するか、または保護するためにネットワークをサブネットに仕切らせます。
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 NNsのクラスタです。 サブネットワーク境界、またはパーティションがEBNとそれに隣接したNNが異なったネットワーク識別子(NETIDs)を持っているところに起こります。 それらは、また、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).
2つのAPPNノードの間の接続はAPPNトランスミッショングループ(TG)です。 サブネット境界のTGはIntersubnetwork Transmission Group(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.
顧客に面している別の挑戦はEBNsによって形成されたサブネット境界を特定することです。 SNANAU APPN MIB[14]はappnNnTopologyグループにおけるサブネット境界を特定します。 SNANAU APPN MIBはAPPN物の管理を提供して、このMIBによって広げられるいくつかのテーブルを含んでいます。
In this document, we describe EBN managed objects.
本書では、私たちはEBN管理オブジェクトについて説明します。
Clouston & Moore Standards Track [Page 3] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[3ページ]RFC2457
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 LUsのサブネット提携を特定します。(論理装置)
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(Serviceのクラス)マッピングを特定します。
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 周囲のBorder Node(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リソースに影響するかもしれないAlert状態のための罠を含んでいます。 APPN/EBN Alertsは全く今日APPN MIB[14]では定義されませんでしたが、彼らは将来、存在できました。 alertTrapに含まれたaffectedObject物のための値は実現で決定します。 それはEBN MIBからのVariablePointerを含むかもしれません。
3.1 EBN MIB Structure
3.1 EBN MIB構造
The EBN MIB module contains the following groups of objects:
EBN MIBモジュールは物の以下のグループを含みます:
o ebnDir - subnet information about LUs.
o ebnDir--LUsのサブネット情報。
o ebnIsRscv - provides the RSCV (Route Selection Control
Vector) and COS for the subnetwork on the BIND destination side
of the EBN.
o ebnIsRscv--RSCV(ルートSelection Control Vector)とCOSをEBNのBIND目的地の側面の上のサブネットワークに提供します。
o ebnDirConfig - objects related to the EBN directory.
o ebnDirConfig--物はEBNディレクトリに関連しました。
o ebnCos - COS mapping between subnetworks,
o ebnCos--サブネットワークの間のCOSマッピング
Clouston & Moore Standards Track [Page 4] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[4ページ]RFC2457
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.
これらのグループは以下でさらに詳細に説明されます。
3.1.1 enbDir group
3.1.1 enbDirは分類します。
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を含みます。(ebnDirTableはappnDirTableへの拡大です)。 それはEBNのディレクトリにおける、LUsのサブネット提携を指定します。
3.1.2 ebnIsRscv group
3.1.2 ebnIsRscvは分類します。
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を含みます。(ebnIsRscvTableはappnIsInTableへの拡大です)。 appnIsInTableはセッションで横断された1つのサブネットワークのためにRSCVとCOS名を考慮するだけです。 この拡大はもう片方のサブネットワークのためのRSCVとCOS名を含んでいます。
When an EBN changes RSCVs before forwarding a BIND, appnIsInRouteInfo contains the incoming RSCV, and ebnIsRscvDestinationRoute contains the outgoing RSCV.
BINDを進める前にEBNがRSCVsを変えるとき、appnIsInRouteInfoは入って来るRSCVを含んでいます、そして、ebnIsRscvDestinationRouteは出発しているRSCVを含んでいます。
The following three cases illustrate the contents of appnIsInRouteInfo and ebnIsRscvDestinationRoute at Extended Border Nodes.
以下の3つのケースが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)
**サブネット1**|-----ISTG------|**サブネット2**EBN1 EBN2 PLU SLU---------------------------->| (1) |、-、-、-、-、-、-、-、-、-、-、-、-、-、--、>| (2) |---------->。(3)
PLU = Primary Logical Unit (session initiator)
SLU = Secondary Logical Unit (session destination)
PLUは第一のLogical Unit(セッション創始者)SLU=二次Logical Unitと等しいです。(セッションの目的地)
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
PLU(または、サブネットにおけるエントリーEBN)からEBN2までEBN1のappnIsInRouteInfo物の値は(1)によって表されたルートを含むRSCVです。 EBN1からEBN2までEBN1のebnIsRscvDestinationRoute物の値はワンバウンドのルートを含む(2)によって表されたRSCVです。 The
Clouston & Moore Standards Track [Page 5] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[5ページ]RFC2457
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のebnIsRscvDestinationRouteの値は(3)によって表されたSLU(または次のサブネットのエントリーEBNに)にルートを含むRSVCです。
2. EBN connected to a NN or PBN
2. NNかPBNに接続されたEBN
**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 NN/PBN
PLU SLU
---------------------------->|
(1) |--------------------------->
(2)
**サブネット1**|-----ISTG------|**サブネット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).
(1)によって表されたNNかPLU(または、サブネットにおけるエントリーEBN)からPBNまでEBN1のappnIsInRouteInfo物の値はルートを含むRSCVです。 EBN1から(2)によって表されたSLUまでEBN1のebnIsRscvDestinationRoute物の値はルートを含むRSCVです。 サブネット2にはSLUがあるに違いないことに注意してください、エントリーノードがEBNよりむしろNNかPBNであるので。 NN/PBNのappnIsInRouteInfo物は(2)によって表されるように同じRSCVを含んでいます。
3. NN or PBN connected to EBN
3. EBNに接続されたNNかPBN
**subnet 1**|-----ISTG ------|**subnet 2**
NN/PBN EBN1
PLU SLU
---------------------------->|
(1) |---------->
(2)
**サブネット1**|-----ISTG------|**サブネット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).
PLUから(1)によって表されたEBN1までNN/PBNのappnIsInRouteInfo物の値はルートを含むRSCVです。 出口ノードがEBNよりむしろNN/PBNであるので、サブネット1にはPLUがあるに違いないことに注意してください。 EBN1のappnIsInRouteInfo物は同じRSCVを含んでいます。 EBN1からSLU(または、次のサブネットのエントリー境界ノード)までEBN1のebnIsRscvDestinationRoute物の値はルートを含むRSCVです、(2)によって表されるように。
The following three cases illustrate the contents of ebnIsRscvDestinationCos at Extended Border Nodes.
以下の3つのケースがExtended Border NodesでebnIsRscvDestinationCosのコンテンツを例証します。
Clouston & Moore Standards Track [Page 6] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[6ページ]RFC2457
1. EBN connected to another EBN
1. 別のEBNに接続されたEBN
**subnet 1**|-----ISTG ------|**subnet 2**
EBN1 EBN2
PLU SLU
COS A
---------------------------->|
COS B
|---------->
**サブネット1**|-----ISTG------|**サブネット2**EBN1 EBN2 PLU SLU COS A---------------------------->| COS B|---------->。
PLU = Primary Logical Unit (session initiator)
SLU = Secondary Logical Unit (session destination)
PLUは第一のLogical Unit(セッション創始者)SLU=二次Logical Unitと等しいです。(セッションの目的地)
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
|--------------------------->
**サブネット1**|-----ISTG------|**サブネット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. EBNに接続されたNNかPBN
**subnet 1**|-----ISTG ------|**subnet 2**
NN/PBN EBN1
PLU SLU
COS A
---------------------------->|
COS B
|---------->
**サブネット1**|-----ISTG------|**サブネット2**NN/PBN EBN1 PLU SLU COS A---------------------------->| COS B|---------->。
The value of the ebnIsRscvDestinationCos object at the EBN2 is
COSB.
EBN2のebnIsRscvDestinationCos物の値はCOSBです。
3.1.3 ebnDirConfig group
3.1.3 ebnDirConfigは分類します。
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グループはLOCATE調査方法が横断するかもしれないサブネットワークの最大数のためにディレクトリキャッシュに関する特殊情報と地方のデフォルト値をEBNに供給する簡単な物から成ります。
Clouston & Moore Standards Track [Page 7] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[7ページ]RFC2457
3.1.4 ebnCos group
3.1.4 ebnCosは分類します。
The ebnCos group contains the ebnCosMapTable, which specifies how COS values are mapped between the non-native subnetwork and the native subnetwork.
ebnCosグループはebnCosMapTableを含みます。(ebnCosMapTableはCOS値が非ネイティブのサブネットワークとネイティブのサブネットワークの間でどう写像されるかを指定します)。
3.1.5 ebnSubnetRoutingList group
3.1.5 ebnSubnetRoutingListは分類します。
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が検索要求をLOCATEに転送するのをその隣接しているノードに示します)。 それは以下のテーブルから成ります:
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を特定するかもしれませんか、またはそれはLUs(部分的なワイルドカード)かすべてのLUs(完全なワイルドカード)のグループを特定できたワイルドカードキャラクタを含むかもしれません。 テーブルの物は、EBNがサブネットルーティングリストにダイナミックなエントリーを追加するかもしれないかどうかと、サブネットルーティングリストエントリーが、より良い検索性能のために再命令されるかもしれないかどうかを示します。
2. ebnSearchTable
2. ebnSearchTable
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がここに検索でそれ自体とそれ自身のネイティブのサブネットワークを捜すか、またはすべてのネイティブのEBNsを捜すのを示す特別なエントリーを考慮します。
3.1.6 hbn group
3.1.6 hbnグループ
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への拡大です。 後部へのRTP(急速なTransportプロトコル)接続がHBNにあるとき、このテーブルは中間的セッションの間、存在しています。 それはNCE ID(ネットワーク接続終点識別子)とTCID(輸送接続識別子)を2番目のRTP接続に提供します。
Clouston & Moore Standards Track [Page 8] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[8ページ]RFC2457
4.0 Definitions
4.0 定義
EBN-MIB DEFINITIONS ::= BEGIN
EBN-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;
IMPORTS MODULE-IDENTITY、OBJECT-TYPE、Unsigned32 FROM SNMPv2-SMI MODULE-COMPLIANCE、OBJECT-GROUP FROM SNMPv2-CONF DisplayString、TEXTUAL-CONVENTION FROM SNMPv2-TC SnaControlPointName--SNAコントロールで許容されたキャラクタ--名前を指すのが制限された文字の組から来るので--これらの名前は国際化を被りやすくはありません。 SNA-NAU-MIBからのAPPN-MIB snanauMIBから。
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"--「ボブCloustonシスコシステムズ7025はクリーク道路私書箱14987リサーチトライアングル公園に装備します、NC 27709、米国Tel:」という1998年4月28日組織「IETF SNAノーMIB WG / AIW APPN MIBs SIG」コンタクトインフォメーション 1 2333年の919 472メール: 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
"
ボブムーアIBM社のBRQA/501P.O. Box12195リサーチトライアングル公園、NC 27709、米国Tel: 1 4436年の919 254メール: " remoore@us.ibm.com "
DESCRIPTION
" The MIB Module for Extended Border Node"
記述は「敷衍された境界ノードのためのMIBモジュール」です。
::= { snanauMIB 7 }
::= snanauMIB7
-- snanauMIB ::= { mib-2 34 }
-- snanauMIB:、:= mib-2 34
Clouston & Moore Standards Track [Page 9] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[9ページ]RFC2457
-- ******************************************************************
-- 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 '*'.
-- 原文..コンベンション------------------------------------------------------------------ SnaNAUWildcardName:、:= TEXTUAL-CONVENTION STATUSの現在の記述は「ネットワークNAU名に完全に資格を与えました」。 エントリーは3つのフォームの1つを取ります: - 明白なエントリーはキャラクタ'*'を含んでいません。 - 部分的なWildcardエントリーには、フォーム'ccc*'があります。そこでは、'ccc'が法的なSNA NAU Nameの1〜16のキャラクタの代理をします。 - 完全なワイルドカードは単一のキャラクタ'*'から成ります。
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))
構文DisplayString(サイズ(1 .17))
-- ******************************************************************
ebnObjects OBJECT IDENTIFIER ::= { ebnMIB 1 }
-- ******************************************************************
-- 物..識別子= { 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ディレクトリGroup--ebnDirTableはappnDirTableへの拡大です。 それは指定します--EBNのディレクトリのLUsのためのサブネット提携。 -- ******************************************************************
ebnDir OBJECT IDENTIFIER ::= { ebnObjects 1 }
ebnDir物の識別子:、:= ebnObjects1
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."
「EBNディレクトリはテーブルの上に置く」ebnDirTable OBJECT-TYPE SYNTAX SEQUENCE OF EbnDirEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 このテーブルはAPPN MIBのappnDirTableへの拡大です。 「エントリーとの1〜1つの通信にはこのテーブルのエントリーがappnDirTableにあります、それらのそれぞれのインデックスのための同じ値を持っている対応するエントリーで。」
::= { ebnDir 1 }
::= ebnDir1
ebnDirEntry OBJECT-TYPE
SYNTAX EbnDirEntry
MAX-ACCESS not-accessible
アクセスしやすくないebnDirEntry OBJECT-TYPE SYNTAX EbnDirEntryマックス-ACCESS
Clouston & Moore Standards Track [Page 10] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[10ページ]RFC2457
STATUS current
DESCRIPTION
"Entry in the EBN Directory Table."
「EBNディレクトリにおけるエントリーはテーブルの上に置く」STATUSの現在の記述。
INDEX { ebnDirLuName }
インデックスebnDirLuName
::= { ebnDirTable 1 }
::= ebnDirTable1
EbnDirEntry ::= SEQUENCE {
ebnDirLuName SnaNAUWildcardName,
ebnDirSubnetAffiliation INTEGER }
EbnDirEntry:、:= 系列ebnDirLuName SnaNAUWildcardName、ebnDirSubnetAffiliation整数
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 OBJECT-TYPE SYNTAX SnaNAUWildcardNameのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述は「給仕ネットワーク・ノードのドメインでネットワークLU名に完全に資格を与えました」。 「この物にAPPN MIBのappnDirLuName物と同じ値があるなら、2個の物が同じLUについて言及しています。」
::= { ebnDirEntry 1 }
::= ebnDirEntry1
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 OBJECT-TYPE SYNTAX INTEGER、ネイティブ(1)(nonNative(2))「副-領域」(3)、マックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「LUのサブネットワーク提携は指定します:、」 - ネイティブ(1): LUがネイティブのAPPNサブネットワークにあります。 - nonNative(2): LUが非ネイティブのAPPNサブネットワークにあります。 - subarea(3): 「「副-領域」ネットワークにはLUがあります。」
::= { ebnDirEntry 2 }
::= ebnDirEntry2
-- ****************************************************************** -- 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--このテーブルはappnIsInTableへのまばらな拡大です。 --EBNに隣接したセッション交差点ISTGs、それはRSCV、およびBINDの目的地の向きに使用されるCOSを含んでいます。 -- ******************************************************************
ebnIsRscv OBJECT IDENTIFIER ::= { ebnObjects 2 }
ebnIsRscv物の識別子:、:= ebnObjects2
ebnIsRscvTable OBJECT-TYPE
ebnIsRscvTableオブジェクト・タイプ
Clouston & Moore Standards Track [Page 11] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[11ページ]RFC2457
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."
「EBN Intermediate Session RSCVはテーブルの上に置く」SYNTAX SEQUENCE OF EbnIsRscvEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 このテーブルはappnIsInTableへの拡大です。 それはBINDの目的地の向きに使用されるRSCVとCOSを含んでいます。 「エントリーがこのEBNが入るか、または残っているときISTGを横断する各セッションのためのこのテーブルにあります、それらのそれぞれのインデックスのための同じ値を持っている対応するエントリーで。」
::= { ebnIsRscv 1}
::= ebnIsRscv1
ebnIsRscvEntry OBJECT-TYPE
SYNTAX EbnIsRscvEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Entry in ebnIsRscvTable."
INDEX { ebnIsRscvCpName,
ebnIsRscvPcid }
ebnIsRscvEntry OBJECT-TYPE SYNTAX EbnIsRscvEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「ebnIsRscvTableのエントリー。」 インデックスebnIsRscvCpName、ebnIsRscvPcid
::= { ebnIsRscvTable 1 }
::= ebnIsRscvTable1
EbnIsRscvEntry ::= SEQUENCE {
ebnIsRscvCpName SnaControlPointName,
ebnIsRscvPcid OCTET STRING,
ebnIsRscvDestinationRoute OCTET STRING,
ebnIsRscvDestinationCos DisplayString }
EbnIsRscvEntry:、:= 系列ebnIsRscvCpName SnaControlPointName、ebnIsRscvPcid八重奏ストリング、ebnIsRscvDestinationRoute八重奏ストリング、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.
「ネットワークが適切な制御点はセッションとPCIDが由来したノードについて命名する」ebnIsRscvCpName OBJECT-TYPE SYNTAX SnaControlPointNameのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 APPNとLENノードに関しては、これはCPが命名する起源LUが位置しているAPPNノードか起源LUが位置しているCP名(LENノードに役立つNN)のどちらかです。 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."
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."
::= { ebnIsRscvEntry 1 }
::= { ebnIsRscvEntry 1 }
Clouston & Moore Standards Track [Page 12] RFC 2457 Extended Border Node MIB November 1998
Clouston & Moore Standards Track [Page 12] RFC 2457 Extended Border Node MIB November 1998
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.
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.
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."
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."
::= { ebnIsRscvEntry 2 }
::= { ebnIsRscvEntry 2 }
ebnIsRscvDestinationRoute OBJECT-TYPE
SYNTAX OCTET STRING(SIZE (0..255))
MAX-ACCESS read-only
ebnIsRscvDestinationRoute OBJECT-TYPE SYNTAX OCTET STRING(SIZE (0..255)) MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The route selection control vector (RSCV x'2B') used in the
direction towards the SLU."
STATUS current DESCRIPTION "The route selection control vector (RSCV x'2B') used in the direction towards the SLU."
::= { 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.
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.
Because the characters allowed in an SNA COS name come from
a restricted character set, these names are not subject to
internationalization."
Because the characters allowed in an SNA COS name come from a restricted character set, these names are not subject to internationalization."
::= { 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 }
Clouston & Moore Standards Track [Page 13] RFC 2457 Extended Border Node MIB November 1998
Clouston & Moore Standards Track [Page 13] RFC 2457 Extended Border Node MIB November 1998
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 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."
::= { 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 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."
::= { 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 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."
::= { 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. -- ******************************************************************
Clouston & Moore Standards Track [Page 14] RFC 2457 Extended Border Node MIB November 1998
Clouston & Moore Standards Track [Page 14] RFC 2457 Extended Border Node MIB November 1998
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.
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.
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."
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."
::= { 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 OBJECT-TYPE SYNTAX EbnCosMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the EBN COS Mapping table."
INDEX { ebnCosMapCpName,
ebnCosMapNonNativeCos }
INDEX { 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 OBJECT-TYPE SYNTAX SnaNAUWildcardName MAX-ACCESS not-accessible STATUS current DESCRIPTION "Fully qualified network CP name for which the COS mapping applies."
::= { ebnCosMapEntry 1 }
::= { ebnCosMapEntry 1 }
ebnCosMapNonNativeCos OBJECT-TYPE
SYNTAX DisplayString (SIZE(1..8))
ebnCosMapNonNativeCos OBJECT-TYPE SYNTAX DisplayString (SIZE(1..8))
Clouston & Moore Standards Track [Page 15] RFC 2457 Extended Border Node MIB November 1998
Clouston & Moore Standards Track [Page 15] RFC 2457 Extended Border Node MIB November 1998
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This object contains one of the following values:
MAX-ACCESS not-accessible STATUS current DESCRIPTION "This object contains one of the following values:
- 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.
- 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.
Because the characters allowed in an SNA COS name come from
a restricted character set, these names are not subject to
internationalization."
Because the characters allowed in an SNA COS name come from a restricted character set, these names are not subject to internationalization."
::= { 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 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.
Because the characters allowed in an SNA COS name come from
a restricted character set, these names are not subject to
internationalization."
Because the characters allowed in an SNA COS name come from a restricted character set, these names are not subject to internationalization."
::= { 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
ebnSubnetSearchTable OBJECT-TYPE SYNTAX SEQUENCE OF EbnSubnetSearchEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION
Clouston & Moore Standards Track [Page 16] RFC 2457 Extended Border Node MIB November 1998
Clouston & Moore Standards Track [Page 16] RFC 2457 Extended Border Node MIB November 1998
"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."
"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."
::= { 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 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."
INDEX { ebnSubnetSearchLuName }
INDEX { 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 OBJECT-TYPE SYNTAX SnaNAUWildcardName MAX-ACCESS not-accessible STATUS current DESCRIPTION "Fully qualified network LU name."
::= { 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 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
Clouston & Moore Standards Track [Page 17] RFC 2457 Extended Border Node MIB November 1998
Clouston & Moore Standards Track [Page 17] RFC 2457 Extended Border Node MIB November 1998
list. full(3) means all native extended border nodes and
adjacent, non-native EBNs and NNs will be added to the
subnetwork routing list."
list. full(3) means all native extended border nodes and adjacent, non-native EBNs and NNs will be added to the subnetwork routing list."
::= { 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 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:
- priority(1): Entries may be reordered.
- defined(2): Entries must not be reordered."
- priority(1): Entries may be reordered. - defined(2): Entries must not be reordered."
::= { ebnSubnetSearchEntry 3 }
::= { ebnSubnetSearchEntry 3 }
-- Border node search table
-- 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."
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."
::= { 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.
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.
Clouston & Moore Standards Track [Page 18] RFC 2457 Extended Border Node MIB November 1998
Clouston & Moore Standards Track [Page 18] RFC 2457 Extended Border Node MIB November 1998
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."
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."
INDEX { ebnSearchLuName,
ebnSearchIndex }
INDEX { 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 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."
::= { 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 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."
::= { ebnSearchEntry 2 }
::= { ebnSearchEntry 2 }
ebnSearchCpName OBJECT-TYPE
SYNTAX DisplayString(SIZE(1..17))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
ebnSearchCpName OBJECT-TYPE SYNTAX DisplayString(SIZE(1..17)) MAX-ACCESS read-only STATUS current DESCRIPTION
Clouston & Moore Standards Track [Page 19] RFC 2457 Extended Border Node MIB November 1998
Clouston & Moore Standards Track [Page 19] RFC 2457 Extended Border Node MIB November 1998
"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:
"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:
'*' indicates that all native EBNs and all adjacent non-
native EBNs and NNs may be added to the routing list
dynamically,
'*' indicates that all native EBNs and all adjacent non- native EBNs and NNs may be added to the routing list dynamically,
'*SELF' indicates that the EBN should search itself and
its native subnetwork at this time during the
cross-subnet search,
'*SELF' indicates that the EBN should search itself and its native subnetwork at this time during the cross-subnet search,
'*EBNS' indicates all native EBNs.
'*EBNS' indicates all native EBNs.
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."
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."
::= { 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 OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of subnets a Locate search procedure may traverse. "
::= { 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."
hbnIsInTable OBJECT-TYPE SYNTAX SEQUENCE OF HbnIsInEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The HBN Intermediate Session table."
Clouston & Moore Standards Track [Page 20] RFC 2457 Extended Border Node MIB November 1998
Clouston & Moore Standards Track [Page 20] RFC 2457 Extended Border Node MIB November 1998
::= { 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.
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.
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:
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 connection in the direction of the PLU:
- NceId: appnIsInRtpNceId (in the APPN MIB)
- Tcid: appnIsinRtpTcid (in the APPN MIB).
RTP connection in the direction of the PLU: - NceId: appnIsInRtpNceId (in the APPN MIB) - Tcid: appnIsinRtpTcid (in the APPN MIB).
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 }
INDEX { 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 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.
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."
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."
Clouston & Moore Standards Track [Page 21] RFC 2457 Extended Border Node MIB November 1998
Clouston & Moore Standards Track [Page 21] RFC 2457 Extended Border Node MIB November 1998
::= { 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.
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.
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."
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."
::= { 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 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."
::= { 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 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."
::= { 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
-- Compliance statements ebnCompliance MODULE-COMPLIANCE
Clouston & Moore Standards Track [Page 22] RFC 2457 Extended Border Node MIB November 1998
Clouston & Moore Standards Track [Page 22] RFC 2457 Extended Border Node MIB November 1998
STATUS current
DESCRIPTION
"The compliance statement for the SNMPv2 entities which
implement the ebnMIB."
STATUS current DESCRIPTION "The compliance statement for the SNMPv2 entities which implement the ebnMIB."
MODULE -- this module
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."
-- Conditionally mandatory groups GROUP hbnIsInGroup DESCRIPTION "The hbnIsInGroup is mandatory only for HPR extended border nodes."
::= {ebnCompliances 1 }
::= {ebnCompliances 1 }
-- Group definitions
ebnDirectoryGroup OBJECT-GROUP
OBJECTS { ebnDirSubnetAffiliation }
STATUS current
DESCRIPTION
"The EBN-related directory objects."
-- Group definitions ebnDirectoryGroup OBJECT-GROUP OBJECTS { ebnDirSubnetAffiliation } STATUS current DESCRIPTION "The EBN-related directory objects."
::= { 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 } STATUS current DESCRIPTION "Two objects representing RSCV and class of service information saved by an EBN."
::= { ebnGroups 2 }
::= { ebnGroups 2 }
ebnDirectoryConfigGroup OBJECT-GROUP
OBJECTS { ebnSearchCacheTime,
ebnMaxSearchCache,
ebnDefaultSubnetVisitCount }
STATUS current
ebnDirectoryConfigGroup OBJECT-GROUP OBJECTS { ebnSearchCacheTime, ebnMaxSearchCache, ebnDefaultSubnetVisitCount } STATUS current
Clouston & Moore Standards Track [Page 23] RFC 2457 Extended Border Node MIB November 1998
Clouston & Moore Standards Track [Page 23] RFC 2457 Extended Border Node MIB November 1998
DESCRIPTION
"The EBN Directory Configuration Group."
DESCRIPTION "The EBN Directory Configuration Group."
::= { ebnGroups 3 }
::= { ebnGroups 3 }
ebnCosMappingGroup OBJECT-GROUP
OBJECTS { ebnCosMapNativeCos }
STATUS current
DESCRIPTION
"The EBN COS Mapping Group."
ebnCosMappingGroup OBJECT-GROUP OBJECTS { ebnCosMapNativeCos } STATUS current DESCRIPTION "The EBN COS Mapping Group."
::= { ebnGroups 4 }
::= { ebnGroups 4 }
ebnSubnetRoutingListGroup OBJECT-GROUP
OBJECTS { ebnSubnetSearchDynamics,
ebnSubnetSearchOrdering,
ebnSearchCpName,
ebnSearchSNVC }
STATUS current
DESCRIPTION
"The Subnet Routing List Group."
ebnSubnetRoutingListGroup OBJECT-GROUP OBJECTS { ebnSubnetSearchDynamics, ebnSubnetSearchOrdering, ebnSearchCpName, ebnSearchSNVC } STATUS current DESCRIPTION "The Subnet Routing List Group."
::= { ebnGroups 5 }
::= { ebnGroups 5 }
hbnIsInGroup OBJECT-GROUP
OBJECTS { hbnIsInRtpNceId, hbnIsInRtpTcid }
STATUS current
DESCRIPTION
"The HBN-related Intermediate Session Objects."
hbnIsInGroup OBJECT-GROUP OBJECTS { hbnIsInRtpNceId, hbnIsInRtpTcid } STATUS current DESCRIPTION "The HBN-related Intermediate Session Objects."
::= { ebnGroups 6 }
::= { ebnGroups 6 }
END
END
5.0 Security Considerations
5.0 Security Considerations
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].
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].
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;
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;
Clouston & Moore Standards Track [Page 24] RFC 2457 Extended Border Node MIB November 1998
Clouston & Moore Standards Track [Page 24] RFC 2457 Extended Border Node MIB November 1998
such enterprises may wish to restrict SNMP access to most of the objects in the MIB.
such enterprises may wish to restrict SNMP access to most of the objects in the MIB.
There are no read-write objects in the EBN MIB.
There are no read-write objects in the EBN MIB.
6.0 Intellectual Property
6.0 Intellectual Property
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.
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.
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.
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.
7.0 Acknowledgments
7.0 Acknowledgments
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の製品です。 デーヴBilling、シスコシステムズをありがとうございます。 ケイティー・リー、IBM社。 マーシャ・ピーターズ、彼らの貢献とレビューのためのIBM社。
8.0 References
8.0の参照箇所
[1] Case, J., Fedor, M. Schoffstall, M. and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990.
[1] ケース、J.、ヒョードル、M.Schoffstall、M.、およびJ.デーヴィン(「簡単なネットワーク管理プロトコル」、STD15、RFC1157)は1990がそうするかもしれません。
[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.ローズ、「TCP/IPベースのインターネットのNetwork Managementのための管理Information基地:」 「MIB-II」、STD17、RFC1213、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]ケース、J.、McCloghrie、K.、ローズ、M.、およびWaldbusser S.、「簡単なネットワーク管理プロトコル(SNMPv2)のバージョン2のための経営情報の構造」、RFC1902(1996年1月)。
Clouston & Moore Standards Track [Page 25] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[25ページ]RFC2457
[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] ケースとJ.とMcCloghrieとK.とローズ、M.とWaldbusser、S.、「簡単なネットワーク管理プロトコル(SNMPv2)のバージョン2のための原文のコンベンション」RFC1903(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] ケースとJ.とMcCloghrieとK.とローズ、M.とWaldbusser、S.、「簡単なネットワーク管理プロトコル(SNMPv2)のバージョン2のための順応声明」RFC1904(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] ケース、J.、McCloghrie、K.、ローズ、M.、およびWaldbusser、S.は「簡単なネットワーク管理プロトコル(SNMPv2)のバージョン2のための操作について議定書の中で述べます」、RFC1905、1996年1月。
[7] Harrington D., Presuhn, R. and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, January 1998.
[7] ハリントンD.とPresuhnとR.とB.Wijnen、「SNMP管理フレームワークについて説明するためのアーキテクチャ」、RFC2271、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] ハリントンD.、Presuhn、R.、およびB.Wijnen、「メッセージ処理と簡単なネットワークマネージメントのために急いでいるのは(SNMP)について議定書の中で述べます」、RFC2272、1998年1月。
[9] Levi D., Meyer P. and B. Stewart, "SNMPv3 Applications", RFC
2273, January 1998.
[9] レビD.とマイヤーP.とB.スチュワート、「SNMPv3アプリケーション」、RFC2273、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] ブルーメンソルとU.とB.Wijnen、「Simple Network Managementプロトコル(SNMPv3)のバージョン3のためのユーザベースのSecurity Model(USM)」、RFC2274、1998年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、「簡単なネットワークマネージメントのための視点ベースのアクセス制御モデル(VACM)は(SNMP)について議定書の中で述べます」、RFC2275、1998年1月。
[12] Hovey, R. and S. Bradner, "The Organizations Involved in the
IETF Standards Process", BCP 11, RFC 2028, October 1996.
[12] ハービとR.とS.ブラドナー、「IETF標準化過程にかかわる組織」、BCP11、RFC2028、1996年10月。
[13] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[13] ブラドナー、S.、「Indicate Requirement LevelsへのRFCsにおける使用のためのキーワード」、BCP14、RFC2119、1997年3月。
[14] Clouston, B. and B. Moore, "Definition of Managed Objects for
APPN", RFC 2455, November 1998.
[14]CloustonとB.とB.ムーア、「APPNのための管理オブジェクトの定義」、RFC2455、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、/pub/standards/aiw/appn/bordernode/ebn4.psbinとしてnetworking.raleigh.ibm.comの公開FTPを通してだけ利用可能なAPPN Extended Border Node Architecture Referenceバージョン1.0。
[16] IBM, SNA/MS Formats, GC31-8302-01
[16]IBM、SNA/MS形式、GC31-8302-01
Clouston & Moore Standards Track [Page 26] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[26ページ]RFC2457
9.0 Authors' Addresses
9.0 作者のアドレス
Bob Clouston Cisco Systems 7025 Kit Creek Road P.O. Box 14987 Research Triangle Park, NC 27709, USA
7025年のボブCloustonシスコシステムズキットクリーク道路私書箱14987リサーチトライアングル公園、NC 27709、米国
Phone: +1-919-472-2333 EMail: clouston@cisco.com
以下に電話をしてください。 +1-919-472-2333 メールしてください: clouston@cisco.com
Robert Moore Dept. BRQA/Bldg. 501/G114 IBM Corporation P.O.Box 12195 3039 Cornwallis Research Triangle Park, NC 27709, USA
ロバート・ムーア部 BRQA/ビルディング 501/G114IBM社の私書箱12195 3039コーンウォリスリサーチトライアングル公園、NC 27709、米国
Phone: +1-919-254-4436 EMail: remoore@us.ibm.com
以下に電話をしてください。 +1-919-254-4436 メールしてください: remoore@us.ibm.com
Clouston & Moore Standards Track [Page 27] RFC 2457 Extended Border Node MIB November 1998
境界ノードMIB1998年11月に広げられたCloustonとムーア標準化過程[27ページ]RFC2457
10.0 Full Copyright Statement
10.0 完全な著作権宣言文
Copyright (C) The Internet Society (1998). All Rights Reserved.
Copyright(C)インターネット協会(1998)。 All rights reserved。
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.
それに関するこのドキュメントと翻訳は、コピーして、それが批評するか、またはそうでなければわかる他のもの、および派生している作品に提供するか、または準備されているかもしれなくて、コピーされて、発行されて、全体か一部分配された実装を助けるかもしれません、どんな種類の制限なしでも、上の版権情報とこのパラグラフがそのようなすべてのコピーと派生している作品の上に含まれていれば。 しかしながら、このドキュメント自体は何らかの方法で変更されないかもしれません、インターネット協会か他のインターネット組織の版権情報か参照を取り除くのなどように、それを英語以外の言語に翻訳するのが著作権のための手順がインターネットStandardsプロセスで定義したどのケースに従わなければならないか、必要に応じてさもなければ、インターネット標準を開発する目的に必要であるのを除いて。
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.
このドキュメントとそして、「そのままで」という基礎とインターネットの振興発展を目的とする組織に、インターネット・エンジニアリング・タスク・フォースが速達の、または、暗示しているすべての保証を放棄するかどうかというここにことであり、他を含んでいて、含まれて、情報の使用がここに侵害しないどんな保証も少しもまっすぐになるという情報か市場性か特定目的への適合性のどんな黙示的な保証。
Clouston & Moore Standards Track [Page 28]
Cloustonとムーア標準化過程[28ページ]
一覧
スポンサーリンク
