Network Working Group R. Steinberger
Request for Comments: 3201 Paradyne Networks
Category: Standards Track O. Nicklass
RAD Data Communications Ltd.
January 2002
Network Working Group R. Steinberger
Request for Comments: 3201 Paradyne Networks
Category: Standards Track O. Nicklass
RAD Data Communications Ltd.
January 2002
Definitions of Managed Objects for Circuit to Interface Translation
电路到接口转换的托管对象定义
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 (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
Abstract
摘要
This memo defines an extension of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines objects for managing the insertion of interesting Circuit Interfaces into the ifTable. This is important for circuits that must be used within other MIB modules which require an ifEntry. It allows for integrated monitoring of circuits as well as routing to circuits using unaltered, pre-existing MIB modules.
此备忘录定义了管理信息库（MIB）的扩展，用于基于TCP/IP的Internet中的网络管理协议。特别是，它定义了用于管理将感兴趣的电路接口插入ifTable的对象。这对于必须在需要ifEntry的其他MIB模块内使用的电路非常重要。它允许对电路进行集成监控，以及使用不变的、预先存在的MIB模块路由到电路。
Table of Contents
目录
1. The SNMP Management Framework ............................... 2
2. Conventions ................................................. 3
3. Overview .................................................... 3
3.1. Circuit Concepts .......................................... 4
3.2. Theory of Operation ....................................... 4
3.2.1. Creation Process ........................................ 4
3.2.2. Destruction Process ..................................... 5
3.2.2.1. Manual Row Destruction ................................ 5
3.2.2.2. Automatic Row Destruction ............................. 5
3.2.3. Modification Process .................................... 5
3.2.4. Persistence of Data ..................................... 5
4. Relation to Other MIB Modules ............................... 6
4.1. Frame Relay DTE MIB ....................................... 6
1. The SNMP Management Framework ............................... 2
2. Conventions ................................................. 3
3. Overview .................................................... 3
3.1. Circuit Concepts .......................................... 4
3.2. Theory of Operation ....................................... 4
3.2.1. Creation Process ........................................ 4
3.2.2. Destruction Process ..................................... 5
3.2.2.1. Manual Row Destruction ................................ 5
3.2.2.2. Automatic Row Destruction ............................. 5
3.2.3. Modification Process .................................... 5
3.2.4. Persistence of Data ..................................... 5
4. Relation to Other MIB Modules ............................... 6
4.1. Frame Relay DTE MIB ....................................... 6
4.2. Frame Relay Service MIB ................................... 6
4.3. ATM MIB ................................................... 6
4.4. Interfaces Group MIB ...................................... 6
4.4.1. Interfaces Table (ifTable, ifXtable) .................... 6
4.4.2. Stack Table (ifStackTable) .............................. 9
4.5. Other MIB Modules ......................................... 11
5. Structure of the MIB Module ................................. 11
5.1. ciCircuitTable ............................................ 11
5.2. ciIfMapTable .............................................. 11
6. Object Definitions .......................................... 11
7. Acknowledgments ............................................. 19
8. References .................................................. 19
9. Security Considerations ..................................... 21
10. IANA Considerations ........................................ 21
11. Authors' Addresses ......................................... 22
12. Full Copyright Statement ................................... 23
4.2. Frame Relay Service MIB ................................... 6
4.3. ATM MIB ................................................... 6
4.4. Interfaces Group MIB ...................................... 6
4.4.1. Interfaces Table (ifTable, ifXtable) .................... 6
4.4.2. Stack Table (ifStackTable) .............................. 9
4.5. Other MIB Modules ......................................... 11
5. Structure of the MIB Module ................................. 11
5.1. ciCircuitTable ............................................ 11
5.2. ciIfMapTable .............................................. 11
6. Object Definitions .......................................... 11
7. Acknowledgments ............................................. 19
8. References .................................................. 19
9. Security Considerations ..................................... 21
10. IANA Considerations ........................................ 21
11. Authors' Addresses ......................................... 22
12. Full Copyright Statement ................................... 23
The SNMP Management Framework presently consists of five major components:
SNMP管理框架目前由五个主要组件组成：
o An overall architecture, described in RFC 2571 [1].
o RFC 2571[1]中描述的总体架构。
o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second version, called SMIv2, is described in STD 58, RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7].
o 为管理目的描述和命名对象和事件的机制。这种管理信息结构（SMI）的第一个版本称为SMIv1，并在STD 16、RFC 1155[2]、STD 16、RFC 1212[3]和RFC 1215[4]中进行了描述。第二个版本称为SMIv2，在STD 58、RFC 2578[5]、RFC 2579[6]和RFC 2580[7]中进行了描述。
o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [8]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12].
o 用于传输管理信息的消息协议。SNMP消息协议的第一个版本称为SNMPv1，在STD 15、RFC 1157[8]中进行了描述。SNMP消息协议的第二个版本不是互联网标准跟踪协议，称为SNMPv2c，在RFC 1901[9]和RFC 1906[10]中进行了描述。消息协议的第三个版本称为SNMPv3，在RFC 1906[10]、RFC 2572[11]和RFC 2574[12]中进行了描述。
o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [8]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [13].
o 访问管理信息的协议操作。STD 15、RFC 1157[8]中描述了第一组协议操作和相关PDU格式。RFC 1905[13]中描述了第二组协议操作和相关PDU格式。
o A set of fundamental applications described in RFC 2573 [14] and the view-based access control mechanism described in RFC 2575 [15].
o RFC 2573[14]中描述的一组基本应用程序和RFC 2575[15]中描述的基于视图的访问控制机制。
A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [16].
有关当前SNMP管理框架的更详细介绍，请参见RFC 2570[16]。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI.
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB中的对象是使用SMI中定义的机制定义的。
This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB.
此备忘录指定了符合SMIv2的MIB模块。通过适当的翻译，可以生成符合SMIv1的MIB。生成的已翻译MIB必须在语义上等效，除非由于无法翻译而省略了对象或事件（使用计数器64）。在翻译过程中，SMIv2中的一些机器可读信息将转换为SMIv1中的文本描述。但是，这种机器可读信息的丢失不被认为会改变MIB的语义。
The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when they appear in this document, are to be interpreted as described in RFC 2119 [21].
本文件中出现的关键词必须、不得、必需、应、不应、应、不应、推荐、不推荐、可和可选时，应按照RFC 2119[21]中所述进行解释。
This MIB module addresses the concept of inserting circuits, which are potentially virtual, into the ifTable. There are multiple reasons to allow circuits to be added to the ifTable. The most prevalent of which are the standard routing MIB tables such as the ipCidrRouteTable (IP-FORWARD-MIB) and the ipNetToMediaTable (IP-MIB) act on the ifIndex and the RMON MIBs (RMON-MIB and RMON2-MIB as defined in RFC 2819 [23] and RFC 2021 [19]) require the use of an ifIndex a DataSource.
此MIB模块解决了将可能是虚拟的电路插入ifTable的概念。允许将电路添加到ifTable有多种原因。其中最普遍的是标准路由MIB表，如IPCIDROUTTETABLE（IP-FORWARD-MIB）和ipNetToMediaTable（IP-MIB）作用于ifIndex和RMON MIB（RFC 2819[23]和RFC 2021[19]中定义的RMON-MIB和RMON2-MIB），需要使用ifIndex a数据源。
There is a further need to potentially monitor or manage a circuit based on the directional flow of traffic going through it. For instance, monitoring of protocols passed on a circuit using RMON-II (RFC 2021 [19]) does not currently capture the direction of the flow. This MIB module provides the capability to define an interface based on the specific direction of the flow.
还需要根据通过电路的定向交通流对电路进行潜在的监控或管理。例如，使用RMON-II（RFC 2021[19]）对电路上传递的协议进行监控，目前无法捕获流的方向。此MIB模块提供基于特定流方向定义接口的功能。
This section provides an overview and background of how to use this MIB module.
本节提供如何使用此MIB模块的概述和背景。
There are multiple MIB modules that define circuits. Three commonly used MIB modules are FRAME-RELAY-DTE-MIB (RFC 2115) [20], FRNETSERV-MIB (RFC 2954) [18], and ATM-MIB (RFC 2515) [22]. These define management objects for frame relay DTEs, frame relay services, and ATM respectively. Each of these MIB modules contain the ability to add or delete circuits; however, none create a specific ifEntry for a circuit. The reason for this is that there are potentially multiple circuits and not every circuit needs to be managed as an individual interface. For example, not every circuit on a device needs to be monitored with RMON and not every circuit needs to be included as an individual circuit for routing. Further, the Interfaces Group MIB (RFC 2863) [17] strongly recommends that conceptual rows not be added to the ifTable for virtual circuits.
有多个定义电路的MIB模块。三种常用的MIB模块是帧中继DTE-MIB（RFC 2115）[20]、FRNETSERV-MIB（RFC 2954）[18]和ATM-MIB（RFC 2515）[22]。它们分别为帧中继DTE、帧中继服务和ATM定义管理对象。每个MIB模块都包含添加或删除电路的功能；但是，没有为回路创建特定的ifEntry。这是因为可能存在多个电路，而不是每个电路都需要作为单独的接口进行管理。例如，并非设备上的每个电路都需要使用RMON进行监控，也并非每个电路都需要作为单独的电路进行布线。此外，接口组MIB（RFC 2863）[17]强烈建议不要将概念行添加到虚拟电路的ifTable中。
The rationale for creating conceptual rows in the ifTable for these circuits is that there is a need for their use in either management of routing or monitoring of data. Both of these functions require mapping to an ifIndex.
为这些电路在ifTable中创建概念行的基本原理是，需要将其用于路由管理或数据监控。这两个函数都需要映射到ifIndex。
This MIB module is designed such that only those circuits that require an ifIndex need be added to the ifTable. This prevents over-populating the ifTable with useless or otherwise unused indices.
此MIB模块的设计使得只有那些需要ifIndex的电路才需要添加到ifTable。这可以防止用无用或未使用的索引过度填充ifTable。
While this document often refers to ATM and frame relay, it is not specifically designed for only those types of circuits. Any circuit that is defined in a MIB module but does not have its own ifIndex MAY be added with this MIB module.
虽然本文档通常涉及ATM和帧中继，但它并不是专门为这些类型的电路设计的。在MIB模块中定义但没有自己的ifIndex的任何电路都可以与此MIB模块一起添加。
In some cases, devices will automatically populate the rows of ciCircuitTable as circuits are created or discovered. However, in many cases, it may be necessary for a network manager to manually create rows.
在某些情况下，在创建或发现电路时，设备会自动填充ciCircuitTable的行。但是，在许多情况下，网络管理器可能需要手动创建行。
Manual creation of rows requires the following steps:
手动创建行需要以下步骤：
1) Locate or create the circuit that is to be added on the device.
1) 找到或创建要添加到设备上的回路。
2) Create a row in ciCircuitTable for each flow type that is required.
2) 在ciCircuitTable中为所需的每种流类型创建一行。
The first step above requires some knowledge of the circuits that exist on a device. Typically, logical ports have entries in the
上面的第一步需要了解设备上存在的电路。通常，逻辑端口在
ifTable. If, for example, the ifType for the logical port is frameRelay(32), the circuits can be located in the frCircuitTable of the Frame Relay DTE MIB (FRAME-RELAY-DTE-MIB) [18]. If, as another example, the ifType for the logical port is frameRelayService(44), the circuits can be located in the frPVCEndptTable of the Frame Relay Service MIB (FRNETSERV-MIB) [20]. If, as a final example, the ifType for the logical port is aal5(49), the circuits can be located in the aal5VccTable of the ATM MIB (ATM-MIB) [22]. An entry describing the circuit MUST exist in some table prior to creating a row in ciCircuitTable. The object identifier that MUST be used in the circuit definition is the lexicographically smallest accessible OID that fully describes the the circuit.
如果可以的话。例如，如果逻辑端口的ifType为frameRelay（32），则电路可以位于帧中继DTE MIB（Frame-Relay-DTE-MIB）的FRCircuit表中[18]。作为另一个示例，如果逻辑端口的ifType为frameRelayService（44），则电路可以位于帧中继服务MIB（FRNETSERV-MIB）的frPVCEndptTable中[20]。最后一个示例是，如果逻辑端口的ifType为aal5（49），则电路可以位于ATM MIB（ATM-MIB）的aal5VccTable中[22]。在ciCircuitTable中创建行之前，描述电路的条目必须存在于某个表中。回路定义中必须使用的对象标识符是完全描述回路的词典最小可访问OID。
Manual row destruction is straight forward. Any row can be destroyed and the resources allocated to it are freed by setting the value of its status object (ciCircuitStatus) to destroy(6). It should be noted that when ciCircuitStatus is set to destroy(6) all associated rows in the ifTable and in ciIfMapTable will also be destroyed. This process MAY trigger further row destruction in other tables as well.
手动行销毁是直接的。通过将其状态对象（ciCircuitStatus）的值设置为destroy（6），可以销毁任何行并释放分配给它的资源。应注意，当ciCircuitStatus设置为销毁（6）时，ifTable和ciIfMapTable中的所有关联行也将被销毁。此过程还可能触发其他表中的进一步行销毁。
Rows in the tables MAY be destroyed automatically based on the existence of the circuit on which they rely. When a circuit no longer exists in the device, the data in the tables has no relation to anything known on the network. For this reason, rows MUST be removed from this table as soon as it is discovered that the associated circuits no longer exist. The effects of automatic row destruction are the same as manual row destruction.
表中的行可能会根据它们所依赖的电路的存在而自动销毁。当设备中不再存在电路时，表中的数据与网络上的任何已知数据都没有关系。因此，一旦发现关联回路不再存在，必须立即从此表中删除行。自动行销毁的效果与手动行销毁的效果相同。
Since no objects in the MIB module can be changed once rows are active, there are no modification caveats.
由于一旦行处于活动状态，就不能更改MIB模块中的任何对象，因此没有修改警告。
Each row in the tables of this MIB module relies on information from other MIB modules. The rules for persistence of the data SHOULD follow the same rules as those of the underlying MIB module. For example, if the circuit defined by ciCircuitObject would normally be stored in non-volatile memory, then the ciCircuitEntry SHOULD also be non-volatile.
此MIB模块表中的每一行都依赖于来自其他MIB模块的信息。数据持久化的规则应遵循与底层MIB模块相同的规则。例如，如果ciCircuitObject定义的电路通常存储在非易失性内存中，那么ciCircuitEntry也应该是非易失性的。
There is no required relation to the Frame Relay DTE MIB beyond the fact that rows in the frCircuitTable MAY be referenced. However, if frCircuitLogicalIfIndex is being used to represent the same information as a ciCircuitEntry with a value of ciCircuitFlow equal to both(3), the implementation MAY use the same ifIndex.
除了可以引用frCircuitTable中的行之外，与帧中继DTE MIB没有必需的关系。但是，如果使用frCircuitLogicalIfIndex表示与CircuitEntry相同的信息，且CircuitFlow的值等于（3），则实现可能使用相同的ifIndex。
There is no explicit relation to the Frame Relay Service MIB beyond the fact that a rows in the frPVCEndptTable MAY be referenced.
除了可以引用frPVCEndptTable中的行之外，与帧中继服务MIB没有明确的关系。
There is no explicit relation to the ATM MIB beyond the fact that rows in multiple tables may be referenced.
除了可以引用多个表中的行之外，与ATM MIB没有明确的关系。
The following specifies how the Interfaces Group defined in the IF-MIB will be used for the management of interfaces created by this MIB module.
下面指定如何使用IF-MIB中定义的接口组来管理此MIB模块创建的接口。
Values of specific ifTable objects for circuit interfaces are as follows:
电路接口的特定ifTable对象的值如下所示：
Object Name Value of Object
=========== =====================================================
Object Name Value of Object
=========== =====================================================
ifIndex Each entry in the circuit table is represented by an ifEntry. The value of ifIndex is defined by the agent such that it complies with any internal numbering scheme.
ifIndex回路表中的每个条目都由ifIndex条目表示。ifIndex的值由代理定义，以使其符合任何内部编号方案。
ifType The value of ifType is specific to the type of circuit desired. For example, the value for frame relay virtual circuits is frDlciEndPt(193) and the value for ATM virtual circuits is atmVciEndPt(194). If the circuit is to be used in RMON, propVirtual(53) SHOULD NOT be used.
ifType ifType的值特定于所需的电路类型。例如，帧中继虚拟电路的值为frdciendpt（193），而ATM虚拟电路的值为atmVciEndPt（194）。如果要在RMON中使用电路，则不应使用propVirtual（53）。
ifMtu Set to the size in octets of the largest packet, frame or PDU supported on the circuit. If this is not known to the ifMtu object shall be set to zero. If the circuit is not modeled as a packet-oriented interface, this object SHOULD NOT be supported and result in noSuchInstance.
ifMtu设置为电路上支持的最大数据包、帧或PDU的大小（以八位字节为单位）。如果ifMtu不知道这一点，则应将对象设置为零。如果电路未建模为面向数据包的接口，则不应支持此对象，并导致noSuchInstance。
ifSpeed The peak bandwidth in bits per second available for use. This will equal either the ifSpeed of the logical link if policing is not enforced or the maximum information rate otherwise. If neither is known, the ifSpeed object shall be set to zero.
ifSpeed可用的峰值带宽（以比特/秒为单位）。这将等于逻辑链路的ifSpeed（如果未强制执行监控），或者等于最大信息速率（否则）。如果两者都未知，则应将ifSpeed对象设置为零。
ifPhysAddress This will always be an octet string of zero length.
如果physaddress，这将始终是长度为零的八位字节字符串。
ifInOctets The number of octets received by the network (ingress) for this circuit. This counter should count only octets included the header information and user data. If the device does not support statistics on the circuit, this object MUST NOT be supported and result in noSuchInstance.
ifInOctets网络（入口）接收到的该电路的八位字节数。此计数器应仅计算包含标头信息和用户数据的八位字节。如果设备不支持电路统计信息，则不得支持此对象并导致noSuchInstance。
ifInUcastPkts The unerrored number of frames, packets or PDUs received by the network (ingress) for this circuit. If the device does not support statistics on the circuit, this object MUST NOT be supported and result in noSuchInstance.
ifInUcastPkts网络（入口）接收到的该电路的未错误帧数、数据包数或PDU数。如果设备不支持电路统计信息，则不得支持此对象并导致noSuchInstance。
ifInDiscards The number of received frames, packets or PDUs for this circuit discarded due to ingress buffer congestion and traffic policing. If the device does not support statistics on the circuit, this object MUST NOT be supported and result in noSuchInstance.
i指示由于入口缓冲区拥塞和流量监控而丢弃的该电路的接收帧、数据包或PDU的数量。如果设备不支持电路统计信息，则不得支持此对象并导致noSuchInstance。
ifInErrors The number of received frames, packets or PDUs for this circuit that are discarded because of an error. If the device does not support statistics on the circuit, this object MUST NOT be supported and result in noSuchInstance.
IFinerror由于错误而丢弃的该电路的接收帧、数据包或PDU的数量。如果设备不支持电路统计信息，则不得支持此对象并导致noSuchInstance。
ifOutOctets The number of octets sent by the network (egress) for this circuit. This counter should count only octets included the header information and user data. If the device does not support statistics on the circuit, this object MUST NOT be supported and result in noSuchInstance.
ifOutOctets网络（出口）为此电路发送的八位字节数。此计数器应仅计算包含标头信息和用户数据的八位字节。如果设备不支持电路统计信息，则不得支持此对象并导致noSuchInstance。
ifOutUcastpkts The number of unerrored frames, packets or PDUs sent by the network (egress) for this circuit. If the device does not support statistics on the circuit, this object MUST NOT be supported and result in noSuchInstance.
IFOUTUCASTPKT是网络（出口）为此电路发送的未错误帧、数据包或PDU的数量。如果设备不支持电路统计信息，则不得支持此对象并导致noSuchInstance。
ifOutDiscards The number of frames, packets or PDUs discarded in the egress direction for this circuit. Possible reasons are as follows: policing, congestion. If the device does not support statistics on the circuit, this object MUST NOT be supported and result in noSuchInstance.
IfoutDiscard在该电路的出口方向上丢弃的帧、数据包或PDU的数量。可能的原因如下：治安、拥挤。如果设备不支持电路统计信息，则不得支持此对象并导致noSuchInstance。
ifOutErrors The number of frames, packets or PDUs discarded for this circuit in the egress direction because of an error. If the device does not support statistics on the circuit, this object MUST NOT be supported and result in noSuchInstance.
IoutErrors由于错误而在出口方向上为此电路丢弃的帧、数据包或PDU的数量。如果设备不支持电路统计信息，则不得支持此对象并导致noSuchInstance。
ifInBroadcastPkts If the device does not support statistics on the circuit, this object MUST NOT be supported and result in noSuchInstance.
ifInBroadcastPkts如果设备不支持电路统计信息，则不得支持此对象并导致noSuchInstance。
ifOutBroadcastPkts If the device does not support Broadcast packets on the circuit, this object should not be supported and result in noSuchInstance.
ifOutBroadcastPkts如果设备不支持电路上的广播数据包，则不应支持此对象并导致noSuchInstance。
ifLinkUpDownTrapEnable Set to false(2). Circuits often have a predefined notification mechanism. In such instances, the number of notification sent would be doubled if this were enabled.
IflinkUpDownTrappenable设置为false（2）。电路通常具有预定义的通知机制。在这种情况下，如果启用此功能，发送的通知数量将增加一倍。
ifPromiscuousMode Set to false(2). If the circuit is not modeled as a packet-oriented interface, this object SHOULD NOT be supported and result in noSuchInstance.
ifPromiscuousMode设置为false（2）。如果电路未建模为面向数据包的接口，则不应支持此对象，并导致noSuchInstance。
ifConnectorPresent Set to false(2).
ifConnectorPresent设置为false（2）。
All other values are supported as stated in the IF-MIB documentation.
如IF-MIB文档中所述，支持所有其他值。
This section describes by example how to use ifStackTable to represent the relationship between circuit and logical link interfaces.
本节通过示例介绍如何使用ifStackTable表示电路和逻辑链路接口之间的关系。
Example 1: Circuits (C) on a frame relay logical link.
示例1：帧中继逻辑链路上的电路（C）。
+---+ +---+ +---+
| C | | C | | C |
+-+-+ +-+-+ +-+-+
| | |
+---+------+------+---+
| Frame Relay Service |
+----------+----------+
|
+----------+----------+
| Physical Layer |
+---------------------+
+---+ +---+ +---+
| C | | C | | C |
+-+-+ +-+-+ +-+-+
| | |
+---+------+------+---+
| Frame Relay Service |
+----------+----------+
|
+----------+----------+
| Physical Layer |
+---------------------+
The assignment of the index values could for example be (for a V35 physical interface):
例如，索引值的分配可以是（对于V35物理接口）：
ifIndex Description
======= ===========
1 frDlciEndPt (type 193)
2 frDlciEndPt (type 193)
3 frDlciEndPt (type 193)
4 frameRelayService (type 44)
5 v35 (type 33)
ifIndex Description
======= ===========
1 frDlciEndPt (type 193)
2 frDlciEndPt (type 193)
3 frDlciEndPt (type 193)
4 frameRelayService (type 44)
5 v35 (type 33)
The ifStackTable is then used to show the relationships between each interface.
然后使用ifStackTable显示每个接口之间的关系。
HigherLayer LowerLayer
=========== ==========
0 1
0 2
0 3
1 4
2 4
3 4
4 5
5 0
HigherLayer LowerLayer
=========== ==========
0 1
0 2
0 3
1 4
2 4
3 4
4 5
5 0
In the above example the frame relay logical link could just as easily be of type frameRelay(32) instead.
在上面的示例中，帧中继逻辑链路可以很容易地改为帧中继（32）类型。
Example 2: Circuits (C) on a AAL5 logical link.
示例2：AAL5逻辑链路上的电路（C）。
+---+ +---+ +---+
| C | | C | | C |
+-+-+ +-+-+ +-+-+
| | |
+---+------+------+---+
| AAL5 Layer |
+----------+----------+
|
+----------+----------+
| ATM Layer |
+---------------------+
|
+----------+----------+
| Physical Layer |
+---------------------+
+---+ +---+ +---+
| C | | C | | C |
+-+-+ +-+-+ +-+-+
| | |
+---+------+------+---+
| AAL5 Layer |
+----------+----------+
|
+----------+----------+
| ATM Layer |
+---------------------+
|
+----------+----------+
| Physical Layer |
+---------------------+
The assignment of the index values could for example be (for a DS3 physical interface):
例如，索引值的分配可以是（对于DS3物理接口）：
ifIndex Description
======= ===========
1 atmVciEndPt (type 194)
2 atmVciEndPt (type 194)
3 atmVciEndPt (type 194)
4 aal5 (type 49)
5 atm (type 37)
6 ds3 (type 30)
ifIndex Description
======= ===========
1 atmVciEndPt (type 194)
2 atmVciEndPt (type 194)
3 atmVciEndPt (type 194)
4 aal5 (type 49)
5 atm (type 37)
6 ds3 (type 30)
The ifStackTable is then used to show the relationships between each interface.
然后使用ifStackTable显示每个接口之间的关系。
HigherLayer LowerLayer
=========== ==========
0 1
0 2
0 3
1 4
2 4
3 4
4 5
5 6
6 0
HigherLayer LowerLayer
=========== ==========
0 1
0 2
0 3
1 4
2 4
3 4
4 5
5 6
6 0
There is no explicit relation to any other media specific MIB module beyond the fact that rows in multiple tables may be referenced.
除了可以引用多个表中的行之外，与任何其他特定于媒体的MIB模块都没有明确的关系。
The CIRCUIT-IF-MIB consists of the following components:
CIRCUIT-IF-MIB由以下部件组成：
o ciCircuitTable
o 循环电路
o ciIfMapTable
o ciIfMapTable
Refer to the compliance statement defined within for a definition of what objects MUST be implemented.
有关必须实现哪些对象的定义，请参阅中定义的符合性声明。
The ciCircuitTable is the central control table for operations of the Circuit Interfaces MIB. It provides a means of mapping a circuit to its ifIndex as well as forcing the insertion of an ifIndex into the ifTable. The agent is responsible for managing the ifIndex itself such that no device dependent indexing scheme is violated.
ciCircuitTable是电路接口MIB操作的中央控制表。它提供了一种将电路映射到其ifIndex的方法，以及强制将ifIndex插入ifTable的方法。代理负责管理ifIndex本身，以确保不违反设备相关的索引方案。
A row in this table MUST exist in order for a row to exist in any other table in this MIB module.
此表中的行必须存在，才能在此MIB模块中的任何其他表中存在行。
This table maps the ifIndex back to the circuit that it is associated with.
此表将ifIndex映射回与其关联的回路。
CIRCUIT-IF-MIB DEFINITIONS ::= BEGIN
CIRCUIT-IF-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, mib-2, Gauge32 FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowStatus, TimeStamp, RowPointer, StorageType FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF ifIndex, InterfaceIndex FROM IF-MIB;
从SNMPv2 SMI文本约定中导入模块标识、对象类型、mib-2、仪表32、行状态、时间戳、行指针、SNMPv2 TC模块的存储类型、SNMPv2 CONF ifIndex中的对象组、IF-mib中的接口索引；
circuitIfMIB MODULE-IDENTITY LAST-UPDATED "200201030000Z" -- January 3, 2002 ORGANIZATION "IETF Frame Relay Service MIB Working Group" CONTACT-INFO
circuitIfMIB模块标识最后更新“200201030000Z”-2002年1月3日组织“IETF帧中继服务MIB工作组”联系方式
"IETF Frame Relay Service MIB (frnetmib) Working Group
IETF帧中继服务MIB（frnetmib）工作组
WG Charter: http://www.ietf.org/html.charters/
frnetmib-charter.html
WG-email: frnetmib@sunroof.eng.sun.com
Subscribe: frnetmib-request@sunroof.eng.sun.com
Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
WG Charter: http://www.ietf.org/html.charters/
frnetmib-charter.html
WG-email: frnetmib@sunroof.eng.sun.com
Subscribe: frnetmib-request@sunroof.eng.sun.com
Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib
Chair: Andy Malis Vivace Networks Email: Andy.Malis@vivacenetworks.com
主席：Andy Malis Vivace Networks电子邮件：Andy。Malis@vivacenetworks.com
WG editor: Robert Steinberger Paradyne Networks and Fujitsu Network Communications Email: robert.steinberger@fnc.fujitsu.com
工作组编辑：罗伯特·斯坦伯格·帕拉丹网络和富士通网络通讯电子邮件：罗伯特。steinberger@fnc.fujitsu.com
Co-author: Orly Nicklass
RAD Data Communications Ltd.
EMail: Orly_n@rad.co.il"
DESCRIPTION
"The MIB module to allow insertion of selected circuit into
the ifTable."
REVISION "200201030000Z" -- January 3, 2002
DESCRIPTION
"Initial version, published as RFC 3201"
::= { mib-2 94 }
Co-author: Orly Nicklass
RAD Data Communications Ltd.
EMail: Orly_n@rad.co.il"
DESCRIPTION
"The MIB module to allow insertion of selected circuit into
the ifTable."
REVISION "200201030000Z" -- January 3, 2002
DESCRIPTION
"Initial version, published as RFC 3201"
::= { mib-2 94 }
-- Textual Conventions
--文本约定
CiFlowDirection ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The direction of data flow thru a circuit.
CiFlowDirection ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The direction of data flow thru a circuit.
transmit(1) - Only transmitted data
receive(2) - Only received data
both(3) - Both transmitted and received data."
SYNTAX INTEGER {
transmit(1),
receive(2),
both(3)
}
transmit(1) - Only transmitted data
receive(2) - Only received data
both(3) - Both transmitted and received data."
SYNTAX INTEGER {
transmit(1),
receive(2),
both(3)
}
ciObjects OBJECT IDENTIFIER ::= { circuitIfMIB 1 }
ciCapabilities OBJECT IDENTIFIER ::= { circuitIfMIB 2 }
ciConformance OBJECT IDENTIFIER ::= { circuitIfMIB 3 }
ciObjects OBJECT IDENTIFIER ::= { circuitIfMIB 1 }
ciCapabilities OBJECT IDENTIFIER ::= { circuitIfMIB 2 }
ciConformance OBJECT IDENTIFIER ::= { circuitIfMIB 3 }
-- The Circuit Interface Circuit Table
--
-- This table is used to define and display the circuits that
-- are added to the ifTable. It maps circuits to their respective
-- ifIndex values.
-- The Circuit Interface Circuit Table
--
-- This table is used to define and display the circuits that
-- are added to the ifTable. It maps circuits to their respective
-- ifIndex values.
ciCircuitTable OBJECT-TYPE
SYNTAX SEQUENCE OF CiCircuitEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Circuit Interface Circuit Table."
::= { ciObjects 1 }
ciCircuitTable OBJECT-TYPE
SYNTAX SEQUENCE OF CiCircuitEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Circuit Interface Circuit Table."
::= { ciObjects 1 }
ciCircuitEntry OBJECT-TYPE
SYNTAX CiCircuitEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Circuit Interface Circuit Table."
INDEX { ciCircuitObject, ciCircuitFlow }
::= { ciCircuitTable 1 }
ciCircuitEntry OBJECT-TYPE
SYNTAX CiCircuitEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Circuit Interface Circuit Table."
INDEX { ciCircuitObject, ciCircuitFlow }
::= { ciCircuitTable 1 }
CiCircuitEntry ::=
SEQUENCE {
--
-- Index Control Variables
--
ciCircuitObject RowPointer,
ciCircuitFlow CiFlowDirection,
ciCircuitStatus RowStatus,
--
-- Data variables
--
ciCircuitIfIndex InterfaceIndex,
ciCircuitCreateTime TimeStamp,
--
-- Data Persistence
--
ciCircuitStorageType StorageType
}
CiCircuitEntry ::=
SEQUENCE {
--
-- Index Control Variables
--
ciCircuitObject RowPointer,
ciCircuitFlow CiFlowDirection,
ciCircuitStatus RowStatus,
--
-- Data variables
--
ciCircuitIfIndex InterfaceIndex,
ciCircuitCreateTime TimeStamp,
--
-- Data Persistence
--
ciCircuitStorageType StorageType
}
ciCircuitObject OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS not-accessible STATUS current DESCRIPTION "This value contains the RowPointer that uniquely
ciCircuitObject对象类型语法RowPointer MAX-ACCESS不可访问状态当前描述“此值包含唯一
describes the circuit that is to be added to this table. Any RowPointer that will force the size of OBJECT IDENTIFIER of the row to grow beyond the legal limit MUST be rejected.
描述要添加到此表中的回路。必须拒绝任何将强制行的对象标识符的大小增长超过法定限制的行指针。
The purpose of this object is to point a network manager to the table in which the circuit was created as well as define the circuit on which the interface is defined.
此对象的目的是将网络管理器指向创建回路的表，以及定义定义接口的回路。
Valid tables for this object include the frCircuitTable
from the Frame Relay DTE MIB(FRAME-RELAY-DTE-MIB), the
frPVCEndptTable from the Frame Relay Service MIB
(FRNETSERV-MIB), and the aal5VccTable from the ATM MIB
(ATM MIB). However, including circuits from other MIB
tables IS NOT prohibited."
::= { ciCircuitEntry 1 }
Valid tables for this object include the frCircuitTable
from the Frame Relay DTE MIB(FRAME-RELAY-DTE-MIB), the
frPVCEndptTable from the Frame Relay Service MIB
(FRNETSERV-MIB), and the aal5VccTable from the ATM MIB
(ATM MIB). However, including circuits from other MIB
tables IS NOT prohibited."
::= { ciCircuitEntry 1 }
ciCircuitFlow OBJECT-TYPE SYNTAX CiFlowDirection MAX-ACCESS not-accessible STATUS current DESCRIPTION "The direction of data flow through the circuit for which the virtual interface is defined. The following define the information that the virtual interface will report.
ciCircuitFlow对象类型语法CiFlowDirection MAX-ACCESS不可访问状态当前描述“通过定义了虚拟接口的电路的数据流方向。以下定义了虚拟接口将报告的信息。
transmit(1) - Only transmitted frames receive(2) - Only received frames both(3) - Both transmitted and received frames.
发送（1）-仅发送帧接收（2）-仅接收帧两个（3）-发送帧和接收帧两个。
It is recommended that the ifDescr of the circuit
interfaces that are not both(3) SHOULD have text warning
the operators that the particular interface represents
only half the traffic on the circuit."
::= { ciCircuitEntry 2 }
It is recommended that the ifDescr of the circuit
interfaces that are not both(3) SHOULD have text warning
the operators that the particular interface represents
only half the traffic on the circuit."
::= { ciCircuitEntry 2 }
ciCircuitStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of the current row. This object is used to add, delete, and disable rows in this table. When the status changes to active(1), a row will also be added to the interface map table below and a row will be added to the ifTable. These rows SHOULD not be removed until the status is changed from active(1). The value of ifIndex for the row that
ciCircuitStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“当前行的状态。此对象用于添加、删除和禁用此表中的行。当状态更改为active（1）时，还将向下面的接口映射表中添加一行，并向ifTable中添加一行。在状态从“活动”（1）更改之前，不应删除这些行。该行的ifIndex值为
is added to the ifTable is determined by the agent and MUST follow the rules of the ifTable. The value of ifType for that interface will be frDlciEndPt(193) for a frame relay circuit, atmVciEndPt(194) for an ATM circuit, or another ifType defining the circuit type for any other circuit.
添加到ifTable的由代理确定，并且必须遵循ifTable的规则。该接口的ifType值对于帧中继电路为frDlciEndPt（193），对于ATM电路为atmVciEndPt（194），或者定义任何其他电路的电路类型的另一ifType。
When this object is set to destroy(6), the associated row in the interface map table will be removed and the ifIndex will be removed from the ifTable. Removing the ifIndex MAY initiate a chain of events that causes changes to other tables as well.
当此对象设置为destroy（6）时，接口映射表中的关联行将被删除，ifIndex将从ifTable中删除。删除ifIndex可能会引发一系列事件，这些事件也会导致其他表发生更改。
The rows added to this table MUST have a valid object identifier for ciCircuitObject. This means that the referenced object must exist and it must be in a table that supports circuits.
添加到此表的行必须具有ciCircuitObject的有效对象标识符。这意味着引用对象必须存在，并且必须位于支持回路的表中。
The object referenced by ciCircuitObject MUST exist prior to transitioning a row to active(1). If at any point the object referenced by ciCircuitObject does not exist or the row containing it is not in the active(1) state, the status SHOULD either age out the row or report notReady(3). The effects transitioning from active(1) to notReady(3) are the same as those caused by setting the status to destroy(6).
ciCircuitObject引用的对象必须在将行转换为活动（1）之前存在。如果ciCircuitObject引用的对象在任何时候都不存在，或者包含该对象的行未处于活动（1）状态，则该状态应使该行过期或报告notReady（3）。从active（1）到notReady（3）的转换效果与将状态设置为destroy（6）所产生的效果相同。
Each row in this table relies on information from other
MIB modules. The rules persistence of data SHOULD follow
the same rules as those of the underlying MIB module.
For example, if the circuit defined by ciCircuitObject
would normally be stored in non-volatile memory, then
the row SHOULD also be non-volatile."
::= { ciCircuitEntry 3 }
Each row in this table relies on information from other
MIB modules. The rules persistence of data SHOULD follow
the same rules as those of the underlying MIB module.
For example, if the circuit defined by ciCircuitObject
would normally be stored in non-volatile memory, then
the row SHOULD also be non-volatile."
::= { ciCircuitEntry 3 }
ciCircuitIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The ifIndex that the agent assigns to this row."
::= { ciCircuitEntry 4 }
ciCircuitIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The ifIndex that the agent assigns to this row."
::= { ciCircuitEntry 4 }
ciCircuitCreateTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION
ciCircuitCreateTime对象类型语法时间戳MAX-ACCESS只读状态当前说明
"This object returns the value of sysUpTime at the time
the value of ciCircuitStatus last transitioned to
active(1). If ciCircuitStatus has never been active(1),
this object SHOULD return 0."
::= { ciCircuitEntry 5 }
"This object returns the value of sysUpTime at the time
the value of ciCircuitStatus last transitioned to
active(1). If ciCircuitStatus has never been active(1),
this object SHOULD return 0."
::= { ciCircuitEntry 5 }
ciCircuitStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type used for this row."
::= { ciCircuitEntry 6 }
ciCircuitStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type used for this row."
::= { ciCircuitEntry 6 }
-- The Circuit Interface Map Table
--
-- This table maps the ifIndex values that are assigned to
-- rows in the circuit table back to the objects that define
-- the circuits.
-- The Circuit Interface Map Table
--
-- This table maps the ifIndex values that are assigned to
-- rows in the circuit table back to the objects that define
-- the circuits.
ciIfMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF CiIfMapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Circuit Interface Map Table."
::= { ciObjects 2 }
ciIfMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF CiIfMapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Circuit Interface Map Table."
::= { ciObjects 2 }
ciIfMapEntry OBJECT-TYPE
SYNTAX CiIfMapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Circuit Interface Map Table."
INDEX { ifIndex }
::= { ciIfMapTable 1 }
ciIfMapEntry OBJECT-TYPE
SYNTAX CiIfMapEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the Circuit Interface Map Table."
INDEX { ifIndex }
::= { ciIfMapTable 1 }
CiIfMapEntry ::=
SEQUENCE {
--
-- Mapped Object Variables
--
ciIfMapObject RowPointer,
ciIfMapFlow CiFlowDirection
}
CiIfMapEntry ::=
SEQUENCE {
--
-- Mapped Object Variables
--
ciIfMapObject RowPointer,
ciIfMapFlow CiFlowDirection
}
ciIfMapObject OBJECT-TYPE SYNTAX RowPointer
ciIfMapObject对象类型语法行指针
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value contains the value of RowPointer that
corresponds to the current ifIndex."
::= { ciIfMapEntry 1 }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This value contains the value of RowPointer that
corresponds to the current ifIndex."
::= { ciIfMapEntry 1 }
ciIfMapFlow OBJECT-TYPE
SYNTAX CiFlowDirection
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value contains the value of ciCircuitFlow that
corresponds to the current ifIndex."
::= { ciIfMapEntry 2 }
ciIfMapFlow OBJECT-TYPE
SYNTAX CiFlowDirection
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value contains the value of ciCircuitFlow that
corresponds to the current ifIndex."
::= { ciIfMapEntry 2 }
-- Change tracking metrics
--更改跟踪指标
ciIfLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the most recent change to
ciCircuitStatus for any row in ciCircuitTable."
::= { ciObjects 3 }
ciIfLastChange OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of sysUpTime at the most recent change to
ciCircuitStatus for any row in ciCircuitTable."
::= { ciObjects 3 }
ciIfNumActive OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of active rows in ciCircuitTable."
::= { ciObjects 4 }
ciIfNumActive OBJECT-TYPE
SYNTAX Gauge32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of active rows in ciCircuitTable."
::= { ciObjects 4 }
-- Conformance Information
--一致性信息
ciMIBGroups OBJECT IDENTIFIER ::= { ciConformance 1 }
ciMIBCompliances OBJECT IDENTIFIER ::= { ciConformance 2 }
ciMIBGroups OBJECT IDENTIFIER ::= { ciConformance 1 }
ciMIBCompliances OBJECT IDENTIFIER ::= { ciConformance 2 }
-- -- Compliance Statements --
----合规声明--
ciCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for SNMP entities
C符合性模块-符合性状态当前描述“SNMP实体的符合性声明
which support of the Circuit Interfaces MIB module. This group defines the minimum level of support required for compliance." MODULE -- this module MANDATORY-GROUPS { ciCircuitGroup, ciIfMapGroup, ciStatsGroup }
其中电路接口支持MIB模块。此组定义了法规遵从性所需的最低支持级别。“模块--此模块为强制组{ciCircuitGroup、ciIfMapGroup、ciStatsGroup}”
OBJECT ciCircuitStatus SYNTAX INTEGER { active(1) } -- subset of RowStatus MIN-ACCESS read-only DESCRIPTION "Row creation can be done outside of the scope of the SNMP protocol. If this object is implemented with max-access of read-only, then the only value that MUST be returned is active(1)."
对象ciCircuitStatus语法整数{active（1）}——RowStatus最小访问只读描述的子集“行创建可以在SNMP协议的范围之外完成。如果此对象是以只读的最大访问权限实现的，则必须返回的唯一值是active（1）。”
OBJECT ciCircuitStorageType MIN-ACCESS read-only DESCRIPTION "It is legal to support ciCircuitStorageType as read-only as long as the value reported in consistent with the actual storage mechanism employed within the agent."
OBJECT ciCircuitStorageType MIN-ACCESS只读说明“只要报告的值与代理中使用的实际存储机制一致，支持CircuitStorageType为只读是合法的。”
::= { ciMIBCompliances 1 }
::= { ciMIBCompliances 1 }
--
-- Units of Conformance
--
ciCircuitGroup OBJECT-GROUP
OBJECTS {
ciCircuitStatus,
ciCircuitIfIndex,
ciCircuitCreateTime,
ciCircuitStorageType
}
STATUS current
DESCRIPTION
"A collection of required objects providing
information from the circuit table."
::= { ciMIBGroups 1 }
--
-- Units of Conformance
--
ciCircuitGroup OBJECT-GROUP
OBJECTS {
ciCircuitStatus,
ciCircuitIfIndex,
ciCircuitCreateTime,
ciCircuitStorageType
}
STATUS current
DESCRIPTION
"A collection of required objects providing
information from the circuit table."
::= { ciMIBGroups 1 }
ciIfMapGroup OBJECT-GROUP
OBJECTS {
ciIfMapObject,
ciIfMapFlow
}
ciIfMapGroup OBJECT-GROUP
OBJECTS {
ciIfMapObject,
ciIfMapFlow
}
STATUS current
DESCRIPTION
"A collection of required objects providing
information from the interface map table."
::= { ciMIBGroups 2 }
STATUS current
DESCRIPTION
"A collection of required objects providing
information from the interface map table."
::= { ciMIBGroups 2 }
ciStatsGroup OBJECT-GROUP
OBJECTS {
ciIfLastChange,
ciIfNumActive
}
STATUS current
DESCRIPTION
"A collection of statistical metrics used to help manage
the ciCircuitTable."
::= { ciMIBGroups 3 }
END
ciStatsGroup OBJECT-GROUP
OBJECTS {
ciIfLastChange,
ciIfNumActive
}
STATUS current
DESCRIPTION
"A collection of statistical metrics used to help manage
the ciCircuitTable."
::= { ciMIBGroups 3 }
END
This document was produced by the Frame Relay Service MIB Working Group.
本文件由帧中继服务MIB工作组编制。
[1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999.
[1] Harrington，D.，Presohn，R.和B.Wijnen，“描述SNMP管理框架的体系结构”，RFC 2571，1999年4月。
[2] Rose, M. and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[2] Rose，M.和K.McCloghrie，“基于TCP/IP的互联网管理信息的结构和识别”，STD 16，RFC 1155，1990年5月。
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991.
[3] Rose，M.和K.McCloghrie，“简明MIB定义”，STD 16，RFC 1212，1991年3月。
[4] Rose, M., "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991.
[4] Rose，M.“定义用于SNMP的陷阱的约定”，RFC1215，1991年3月。
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[5] McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[6] McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[7] McCloghrie，K.，Perkins，D.，Schoenwaeld，J.，Case，J.，Rose，M.和S.Waldbusser，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May 1990.
[8] Case，J.，Fedor，M.，Schoffstall，M.和J.Davin，“简单网络管理协议”，STD 15，RFC 1157，1990年5月。
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January 1996.
[9] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“基于社区的SNMPv2简介”，RFC 19011996年1月。
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January 1996.
[10] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的传输映射”，RFC 1906，1996年1月。
[11] Case, J., Harrington, D., Presuhn, R. and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999.
[11] Case，J.，Harrington，D.，Presohn，R.和B.Wijnen，“简单网络管理协议（SNMP）的消息处理和调度”，RFC 2572，1999年4月。
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999.
[12] Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）第3版的基于用户的安全模型（USM）”，RFC 2574，1999年4月。
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
[13] Case，J.，McCloghrie，K.，Rose，M.和S.Waldbusser，“简单网络管理协议（SNMPv2）版本2的协议操作”，RFC 1905，1996年1月。
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999.
[14] Levi，D.，Meyer，P.和B.Stewart，“SNMPv3应用”，RFC2573，1999年4月。
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)", RFC 2575, April 1999.
[15] Wijnen，B.，Presuhn，R.和K.McCloghrie，“用于简单网络管理协议（SNMP）的基于视图的访问控制模型（VACM）”，RFC2575，1999年4月。
[16] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April 1999.
[16] Case，J.，Mundy，R.，Partain，D.和B.Stewart，“互联网标准网络管理框架第3版简介”，RFC 25701999年4月。
[17] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[17] McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[18] Rehbehn, K. and D. Fowler, "Definitions of Managed Objects for Frame Relay Service", RFC 2954, October 2000.
[18] Rehbehn，K.和D.Fowler，“帧中继服务管理对象的定义”，RFC 29542000年10月。
[19] Waldbusser, S., "Remote Network Monitoring Management Information Base Version 2 using SMIv2", RFC 2021, January 1997.
[19] Waldbusser，S.，“使用SMIv2的远程网络监控管理信息库版本2”，RFC 2021，1997年1月。
[20] Brown, C. and F. Baker, "Management Information Base for Frame Relay DTEs Using SMIv2", RFC 2115, September 1997.
[20] Brown，C.和F.Baker，“使用SMIv2的帧中继DTE的管理信息库”，RFC 2115，1997年9月。
[21] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[21] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[22] Tesink, K., "Definitions of Managed Objects for ATM Management", RFC 2515, February 1999.
[22] Tesink，K.，“ATM管理的托管对象定义”，RFC2515，1999年2月。
[23] Waldbusser, S., "Remote Network Monitoring Management Information Base", RFC 2819, May 2000.
[23] Waldbusser，S.，“远程网络监测管理信息库”，RFC 2819，2000年5月。
There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations.
此MIB中定义了许多管理对象，它们的MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。
SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB.
SNMPv1本身不是一个安全的环境。即使网络本身是安全的（例如通过使用IPSec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB中的对象。
It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model RFC 2274 [12] and the View-based Access Control Model RFC 2275 [15] is recommended.
建议实施者考虑SNMPv3框架提供的安全特性。具体而言，建议使用基于用户的安全模型RFC 2274[12]和基于视图的访问控制模型RFC 2275[15]。
It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
然后，客户/用户有责任确保授予对此MIB实例访问权限的SNMP实体被正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）对对象的访问权限。
New ifTypes defined specifically for use in this MIB module SHOULD be
in the form of ***EndPt. This is similar to frDlciEndPt(193) and
atmVciEndPt(194) which are already defined.
New ifTypes defined specifically for use in this MIB module SHOULD be
in the form of ***EndPt. This is similar to frDlciEndPt(193) and
atmVciEndPt(194) which are already defined.
Robert Steinberger Fujitsu Network Communications 2801 Telecom Parkway Richardson, TX 75082
德克萨斯州理查森电信大道2801号罗伯特·斯坦伯格富士通网络通信公司，邮编75082
Phone: 1-972-479-4739 EMail: robert.steinberger@fnc.fujitsu.com
电话：1-972-479-4739电子邮件：罗伯特。steinberger@fnc.fujitsu.com
Orly Nicklass, Ph.D RAD Data Communications Ltd. 12 Hanechoshet Street Tel Aviv, Israel 69710
Orly Nicklass博士，RAD数据通信有限公司，以色列特拉维夫Hanechoshet街12号，邮编69710
Phone: 972 3 7659969 EMail: Orly_n@rad.co.il
电话：97237659969电子邮件：Orly_n@rad.co.il
Copyright (C) The Internet Society (2002). All Rights Reserved.
版权所有（C）互联网协会（2002年）。版权所有。
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.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。