Network Working Group D. Zelig, Ed.
Request for Comments: 5603 Oversi
Category: Standards Track T. Nadeau, Ed.
BT
July 2009
Network Working Group D. Zelig, Ed.
Request for Comments: 5603 Oversi
Category: Standards Track T. Nadeau, Ed.
BT
July 2009
Ethernet Pseudowire (PW) Management Information Base (MIB)
以太网伪线（PW）管理信息库（MIB）
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 describes managed objects for modeling of Ethernet pseudowire (PW) services.
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了用于以太网伪线（PW）服务建模的托管对象。
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) 2009 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2009 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date of publication of this document (http://trustee.ietf.org/license-info). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
本文件受BCP 78和IETF信托在本文件出版之日生效的与IETF文件有关的法律规定的约束(http://trustee.ietf.org/license-info). 请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。
This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.
本文件可能包含2008年11月10日之前发布或公开的IETF文件或IETF贡献中的材料。控制某些材料版权的人员可能未授予IETF信托允许在IETF标准流程之外修改此类材料的权利。在未从控制此类材料版权的人员处获得充分许可的情况下，不得在IETF标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
Table of Contents
目录
1. Introduction ....................................................2
2. The Internet-Standard Management Framework ......................2
3. Conventions .....................................................3
4. Overview ........................................................3
5. Feature Checklist ...............................................4
6. PW ENET MIB Module Usage ........................................4
7. PW-ENET Management Model ........................................5
8. Example of the PW-ENET MIB Module Usage .........................6
9. Service-Delimiting Modes ........................................6
10. Object Definitions .............................................9
11. Security Considerations .......................................19
12. IANA Considerations ...........................................21
13. References ....................................................21
13.1. Normative References .....................................21
13.2. Informative References ...................................22
14. Acknowledgments ...............................................22
1. Introduction ....................................................2
2. The Internet-Standard Management Framework ......................2
3. Conventions .....................................................3
4. Overview ........................................................3
5. Feature Checklist ...............................................4
6. PW ENET MIB Module Usage ........................................4
7. PW-ENET Management Model ........................................5
8. Example of the PW-ENET MIB Module Usage .........................6
9. Service-Delimiting Modes ........................................6
10. Object Definitions .............................................9
11. Security Considerations .......................................19
12. IANA Considerations ...........................................21
13. References ....................................................21
13.1. Normative References .....................................21
13.2. Informative References ...................................22
14. Acknowledgments ...............................................22
This document describes a model for managing Ethernet pseudowire services for transmission over a Packet Switched Network (PSN). This MIB module is generic and common to all types of PSNs supported in the Pseudowire Emulation Edge-to-Edge (PWE3) architecture [RFC3985], which describes the transport and encapsulation of L1 and L2 services over supported PSN types.
本文档描述了一种用于管理以太网伪线服务的模型，用于在分组交换网络（PSN）上传输。此MIB模块是伪线仿真边缘到边缘（PWE3）体系结构[RFC3985]中支持的所有类型PSN的通用模块，该体系结构描述了受支持PSN类型上L1和L2服务的传输和封装。
In particular, the MIB module associates a port or specific VLANs on top of a physical Ethernet port or a virtual Ethernet interface (for Virtual Private LAN Service (VPLS)) to a point-to-point PW. It is complementary to the PW-STD-MIB [RFC5601], which manages the generic PW parameters common to all services, including all supported PSN types.
具体而言，MIB模块将物理以太网端口或虚拟以太网接口（用于虚拟专用LAN服务（VPLS））上的端口或特定VLAN与点对点PW相关联。它是对PW-STD-MIB[RFC5601]的补充，PW-STD-MIB[RFC5601]管理所有服务通用的PW参数，包括所有支持的PSN类型。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC 3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。此备忘录指定了一个MIB模块
that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].
符合SMIv2，标准58、RFC 2578[RFC2578]、标准58、RFC 2579[RFC2579]和标准58、RFC 2580[RFC2580]中描述了SMIv2。
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 [BCP14].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[BCP14]中所述进行解释。
This document adopts the definitions, acronyms, and mechanisms described in [RFC3985] and [RFC3916]. Unless otherwise stated, the mechanisms of [RFC3985] apply and will not be re-described here.
本文件采用[RFC3985]和[RFC3916]中所述的定义、首字母缩略词和机制。除非另有说明，[RFC3985]的机制适用，此处不再重复说明。
The MIB module structure for defining a PW service is composed of three layers of MIB modules functioning together. This general model is defined in the PWE3 architecture [RFC3985]. The layering model is intended to sufficiently isolate PW services from the underlying PSN layer that carries the emulated service. This is done at the same time as providing a standard means for connecting any supported services to any supported PSNs.
用于定义PW服务的MIB模块结构由三层MIB模块组成，它们一起工作。该通用模型在PWE3体系结构[RFC3985]中定义。分层模型旨在将PW服务与承载模拟服务的底层PSN层充分隔离。这与提供将任何受支持的服务连接到任何受支持的PSN的标准方法同时完成。
The first layer, known as the service layer, contains service-specific modules. These modules define service-specific management objects that interface or collaborate with existing MIB modules for the native version of the service. The service-specific module "glues" the standard modules to the PWE3 MIB modules.
第一层称为服务层，包含特定于服务的模块。这些模块定义特定于服务的管理对象，这些对象与服务本机版本的现有MIB模块进行接口或协作。特定于服务的模块将标准模块“粘合”到PWE3 MIB模块。
The next layer of the PWE3 MIB framework is the PW MIB module [RFC5601]. This module is used to configure general parameters of PWs that are common to all types of emulated services and PSNs. This layer is connected to the service-specific layer above and the PSN layer below.
PWE3 MIB框架的下一层是PW MIB模块[RFC5601]。此模块用于配置PWs的通用参数，这些参数对于所有类型的仿真服务和PSN都是通用的。该层连接到上面的服务特定层和下面的PSN层。
The PSN layer provides PSN-specific modules for each type of PSN. These modules associate the PW with one or more "tunnels" that carry the service over the PSN. These modules are used to "glue" the PW service to the underlying PSN-specific MIB modules. This document defines the MIB module for Ethernet PW over any PSN type.
PSN层为每种类型的PSN提供特定于PSN的模块。这些模块将PW与通过PSN承载服务的一个或多个“隧道”相关联。这些模块用于将PW服务“粘合”到底层特定于PSN的MIB模块。本文件定义了任何PSN类型上以太网PW的MIB模块。
This module uses Textual Conventions (TCs) and objects as defined in [RFC2578], [RFC2579], [RFC2580], [RFC2863], [RFC4363], [RFC4502], and [RFC5601].
本模块使用[RFC2578]、[RFC2579]、[RFC2580]、[RFC2863]、[RFC4363]、[RFC4502]和[RFC5601]中定义的文本约定（TC）和对象。
The Etherlike-MIB [RFC3635] does not support virtual Ethernet ports; however, it is sometimes desired to manage the PW as an Ethernet port via the Etherlike-MIB. This MIB module supports an option to recognize the PW as an ifIndex, enabling standard use of the Etherlike-MIB to manage the PW.
以太式MIB[RFC3635]不支持虚拟以太网端口；然而，有时需要通过类似以太网的MIB将PW作为以太网端口进行管理。此MIB模块支持将PW识别为ifIndex的选项，从而支持以太式MIB的标准使用来管理PW。
The PW Ethernet MIB module (PW-ENET-STD-MIB) is designed to satisfy the following requirements and constraints:
PW以太网MIB模块（PW-ENET-STD-MIB）的设计满足以下要求和约束：
- The MIB module is designed to work with the PW-STD-MIB [RFC5601].
- MIB模块设计用于与PW-STD-MIB[RFC5601]配合使用。
- The MIB module is agnostic to the PSN type.
- MIB模块与PSN类型无关。
- The MIB module supports various options for selecting Ethernet packets into the PW, as defined in [RFC4448]. These include port-based PW, VLAN-based PW, and VLAN-manipulated based (change, add, or remove) between the port to be emulated and the PW.
- MIB模块支持将以太网数据包选择到PW中的各种选项，如[RFC4448]中所定义。这些包括基于端口的PW、基于VLAN的PW以及要仿真的端口和PW之间基于VLAN的（更改、添加或删除）。
- In the case of an MPLS PSN, the MIB module supports the use of multiple PWs to carry the same Ethernet service. These PWs can be used to support Label-Only-Inferred-PSC LSPs (L-LSPs) or EXP-Inferred-PSC LSPs (E-LSPs) that are from a single Class of Service (CoS), when mapping of the Ethernet user priority (PRI) bits to the PSN CoS is required.
- 在MPLS PSN的情况下，MIB模块支持使用多个PW来承载相同的以太网服务。当需要将以太网用户优先级（PRI）位映射到PSN CoS时，这些PWs可用于支持来自单一服务类别（CoS）的仅标签推断PSC LSP（L-LSP）或EXP推断PSC LSP（E-LSP）。
- The MIB module enables both point-to-point Ethernet services and VPLS services as discussed in the L2VPN working group [RFC4664].
- MIB模块支持L2VPN工作组[RFC4664]中讨论的点对点以太网服务和VPLS服务。
- The MIB module allows modeling of the PW as an Ethernet virtual port to be managed via existing Ethernet MIBs like Etherlike-MIB [RFC3635].
- MIB模块允许将PW建模为以太网虚拟端口，通过现有的以太网MIB（如以太网MIB）进行管理[RFC3635]。
- The PW table (pwTable) is used for all PW types (ATM, FR, Ethernet, SONET, etc.). This table contains high-level generic parameters related to the PW creation. A row is typically created by the operator (see [RFC5542] for other options) for each PW service.
- PW表（pwTable）用于所有PW类型（ATM、FR、以太网、SONET等）。此表包含与PW创建相关的高级通用参数。通常由操作员为每个PW服务创建一行（其他选项请参见[RFC5542]）。
- Based on the PSN type defined for the PW, rows are created in the PSN-specific module (for example, [RFC5602]) and associated to the pwTable by the common pwIndex.
- 根据为PW定义的PSN类型，在PSN特定模块（例如，[RFC5602]）中创建行，并通过公共pwIndex与pwTable关联。
- If the PW type is Ethernet or EthernetTagged a row is created by the agent in the pwEnetTable.
- 如果PW类型为Ethernet或EthernetTagged，则代理将在PWenet表中创建一行。
The management model for the Ethernet PW is shown in Figure 1, and is based on the PW layering [RFC3985].
以太网PW的管理模型如图1所示，基于PW分层[RFC3985]。
+--------------------------------------+
| PE Device |
+--------------------------------------+
Single | | |
AC | | Single | PW Instance
<------>o Forwarder + PW Instance X<=========>
| | |
+--------------------------------------+
^
|
May be modeled as
ifIndex
+--------------------------------------+
| PE Device |
+--------------------------------------+
Single | | |
AC | | Single | PW Instance
<------>o Forwarder + PW Instance X<=========>
| | |
+--------------------------------------+
^
|
May be modeled as
ifIndex
Notation: o A physical CE-bound PE port. + A PW IWF instance interface to the forwarder. X A PE PSN-bound port.
表示法：o物理CE绑定的PE端口+到转发器的PW IWF实例接口。X一个PE PSN绑定端口。
Figure 1: A simple point-to-point service
图1：一个简单的点到点服务
In the typical point-to-point service, the object pwEnetPortIfIndex associates the physical CE-bound PE port ('o') to the PW (it is allowed to have multiple PWs associated to the same physical port). This MIB module also manages some of the possible operations of the forwarder.
在典型的点对点服务中，对象pWentePortifindex将物理CE绑定PE端口（“o”）与PW关联（允许多个PW与同一物理端口关联）。该MIB模块还管理转发器的一些可能操作。
In some models, it is convenient to model the forwarder virtual interface to a PW IWF instance ('+') as an ifIndex. As discussed in [RFC5601], this is possible by using the PW ifType in the ifTable and indicating the ifIndex in the main pwTable. In case of Ethernet PW, a virtual interface of ifType = etherLike will be assigned on top of the PW interface to enable statistics gathering and statuses and other management configuration tasks via existing tools. This way, the PW instance is managed as virtual Ethernet interface in the PE.
在某些模型中，可以方便地将PW IWF实例（“+”）的转发器虚拟接口建模为ifIndex。如[RFC5601]所述，这可以通过在ifTable中使用PW ifType并在主pwTable中指示ifIndex来实现。对于Ethernet PW，将在PW接口的顶部分配一个ifType=etherLike的虚拟接口，以通过现有工具实现统计数据收集和状态以及其他管理配置任务。这样，PW实例在PE中作为虚拟以太网接口进行管理。
The model for using the PW in non-point-to-point applications, such as VPLS, is done with the same principle in mind, except that the creation of the tables is related typically to an auto-discovery process.
在非点对点应用程序（如VPL）中使用PW的模型也遵循相同的原则，只是表的创建通常与自动发现过程相关。
Assume we would like to create a PW of type VLAN between two PEs, for VLAN value 5.
假设我们想在两个PE之间创建一个VLAN类型的PW，VLAN值为5。
- Follows the example in [RFC5601], with pwType equals 'ethernetTagged'.
- 遵循[RFC5601]中的示例，pwType等于“ethernetTagged”。
- The agent creates a row in the pwEnetTable and a row in the pwEnetStatsTable for the specified pwIndex. The pwEnetPwInstance is automatically set by the agent to the value of 1.
- 代理为指定的pwIndex在PWENETETABLE和pwEnetStatsTable中创建一行。代理程序会自动将pwEnetPwInstance设置为值1。
- The operator fills the following entries in the pwEnetTable:
- 操作员在PWENETER表中填写以下条目：
pwEnetPwVlan 5, pwEnetVlanMode noChange, pwEnetPortVlan 5,
pwEnetPwVlan 5，PWENETVLAN模式无更改，pwEnetPortVlan 5，
pwEnetPortIfIndex 1001, pwEnetPwIfIndex 0, -- Not managed in the -- Etherlike MIB module ...
pwEnetPortIfIndex 1001，pwEnetPwIfIndex 0，--未在类以太网MIB模块中管理。。。
- The PW is ready for forwarding when signaling has been accomplished successfully between the two peers.
- 当两个对等方之间成功完成信令时，PW准备好转发。
This section describes how the MIB module supports point-to-point applications with various VLAN service-delimiting options on the original Ethernet port and the corresponding PW mode and VLAN values. If the PW is attached to VPLS service, the PW is associated to a virtual interface that is attached to a bridge or VPLS forwarder. The bridging function between local physical ports and virtual interfaces that are later associated to PWs is not handled via this MIB module.
本节介绍MIB模块如何支持在原始以太网端口上具有各种VLAN服务定界选项的点到点应用程序，以及相应的PW模式和VLAN值。如果PW连接到VPLS服务，则PW与连接到网桥或VPLS转发器的虚拟接口相关联。本地物理端口和后来与PWs关联的虚拟接口之间的桥接功能不通过此MIB模块处理。
There are three main service types that are supported by this MIB module:
此MIB模块支持三种主要服务类型：
(1) Port mode: In this mode, the whole traffic from the port is mapped to the PW.
(1) 端口模式：在此模式下，来自端口的全部流量映射到PW。
A. In the typical application, the packet is sent to the PW as is:
A.在典型应用中，数据包按原样发送至PW：
pwEnetPwVlan 4095, pwEnetVlanMode portMode, pwEnetPortVlan 4095,
pwEnetPwVlan 4095，PWENETVLAN模式端口模式，PWENETPORTLAN 4095，
pwType Ethernet,
PW型以太网，
B. It is possible to add a provider tag (value 10, for example) to the packet when it is sent over the PW:
B.通过PW发送数据包时，可以向数据包添加提供者标签（例如，值10）：
pwEnetPwVlan 10, pwEnetVlanMode addVlan, pwEnetPortVlan 4095,
pwEnetPwVlan 10，PWENETVLAN模式addVlan，pwEnetPortVlan 4095，
pwType SHOULD be set to 'EthernetTagged'.
pwType应设置为“EthernetTagged”。
(2) Single VLAN: In this mode, only the first VLAN field on the packet from the physical port is the service-delimiting tag, as an example VLAN=5. The following options of processing are possible:
(2) 单VLAN：在此模式下，只有来自物理端口的数据包上的第一个VLAN字段是服务定界标记，例如VLAN=5。以下处理选项是可能的：
A. One-to-one mapping: The service-delimiting tag is kept as is on the PW.
A.一对一映射：服务定界标记保留在PW上。
pwEnetPwVlan 5, pwEnetVlanMode noChange, pwEnetPortVlan 5,
pwEnetPwVlan 5，PWENETVLAN模式无更改，pwEnetPortVlan 5，
pwType SHOULD be set to 'EthernetTagged'.
pwType应设置为“EthernetTagged”。
B. VLAN change mapping: The service-delimiting tag changes its value (to the value of 6) on the PW.
B.VLAN更改映射：服务定界标记在PW上更改其值（值为6）。
pwEnetPwVlan 6, pwEnetVlanMode changeVlan, pwEnetPortVlan 5,
pwEnetPwVlan 6，PWENETVLAN模式更改VLAN，pwEnetPortVlan 5，
pwType SHOULD be set to 'EthernetTagged'.
pwType应设置为“EthernetTagged”。
C. The service-delimiting tag is removed when the packet is sent to the PW.
C.当数据包被发送到PW时，服务定界标签被移除。
pwEnetPwVlan 4095, pwEnetVlanMode removeVlan, pwEnetPortVlan 5,
pwEnetPwVlan 4095，PWENETVLAN模式移除VLAN，pwEnetPortVlan 5，
pwType SHOULD be set to 'EthernetTagged'.
pwType应设置为“EthernetTagged”。
It should be noted that this mode is also applicable when the service-delimiting tag is a service provider tag (VLAN=5 in this case), and the node removes this VLAN and maps the traffic to a single PW independent of the packet format on top of this VLAN.
应该注意，当服务定界标记是服务提供者标记（在本例中为VLAN=5）并且节点移除该VLAN并将流量映射到独立于该VLAN上的分组格式的单个PW时，该模式也适用。
D. Untagged packets mapped to a PW as is (packets with a VLAN field from the same port MAY be mapped to other PWs).
D.映射到PW的未标记数据包（来自同一端口的具有VLAN字段的数据包可以映射到其他PW）。
pwEnetPwVlan 0, pwEnetVlanMode noChange, pwEnetPortVlan 0,
pwEnetPwVlan 0，PWenetVLAN模式无更改，pwEnetPortVlan 0，
pwType MAY equal 'Ethernet' or 'EthernetTagged'.
pwType可以等于“Ethernet”或“EthernetTagged”。
E. Untagged packets mapped to a PW, and a VLAN field is added to the packet.
E.映射到PW的未标记数据包，并向数据包添加VLAN字段。
pwEnetPwVlan 6, pwEnetVlanMode addVlan, pwEnetPortVlan 0,
pwEnetPwVlan 6，PWENETVLAN模式添加VLAN，pwEnetPortVlan 0，
pwType SHOULD be set to 'EthernetTagged'.
pwType应设置为“EthernetTagged”。
F. A provider VLAN (value 10) is added to packets arriving with VLAN value 5 before they are sent to the PW.
F.在将VLAN值为5的数据包发送到PW之前，向其添加一个提供者VLAN（值10）。
pwEnetPwVlan 10, pwEnetVlanMode addVlan, pwEnetPortVlan 5,
pwEnetPwVlan 10，PWENETVLAN模式addVlan，pwEnetPortVlan 5，
pwType SHOULD be set to 'EthernetTagged'.
pwType应设置为“EthernetTagged”。
(3) Nested VLAN (QinQ): When only the first VLAN is the service-delimiting tag, one of the modes as described in 2) SHOULD be used. If the service-delimiting tag is both the first VLAN and the second VLAN, the following option is supported by this MIB module:
(3) 嵌套VLAN（QinQ）：当只有第一个VLAN是服务定界标记时，应使用2）中所述的模式之一。如果服务定界标记同时是第一个VLAN和第二个VLAN，则此MIB模块支持以下选项：
Assuming the provider VLAN tag equals 5 and the user VLAN tag equal 100, this traffic can be mapped to the PW without the provider tag by using the following configuration:
假设提供者VLAN标记等于5，用户VLAN标记等于100，则可以使用以下配置将此流量映射到PW，而不使用提供者标记：
pwEnetPwVlan 100, pwEnetVlanMode removeVLAN, pwEnetPortVlan 5,
pwEnetPwVlan 100，PWENETVLAN模式移除VLAN，pwEnetPortVlan 5，
It is RECOMMENDED that the pwType would equal 'EthernetTagged', but pwType equal to 'Ethernet' MAY be used as well.
建议pwType等于“EthernetTagged”，但也可以使用等于“Ethernet”的pwType。
Packets with the same provider tag MAY be mapped to other PWs.
具有相同提供者标签的分组可以映射到其他pw。
(4) Other scenarios are considered out of scope and should be handled by other MIB modules that manage the forwarder and the Native Service Processing (NSP) sections.
(4) 其他场景被视为超出范围，应由管理转发器和本机服务处理（NSP）部分的其他MIB模块处理。
PW-ENET-STD-MIB DEFINITIONS ::= BEGIN
PW-ENET-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS OBJECT-TYPE, MODULE-IDENTITY, Unsigned32, mib-2 FROM SNMPv2-SMI -- [RFC2578]
从SNMPv2 SMI--[RFC2578]导入对象类型、模块标识、无符号32、mib-2
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580]
SNMPv2配置文件[RFC2580]中的模块合规性、对象组
StorageType, RowStatus FROM SNMPv2-TC -- [RFC2579]
来自SNMPv2 TC的存储类型、行状态--[RFC2579]
InterfaceIndexOrZero FROM IF-MIB -- [RFC2863]
来自IF-MIB的接口索引或零--[RFC2863]
ZeroBasedCounter32 FROM RMON2-MIB -- [RFC4502]
来自RMON2-MIB的ZeroBasedCounter32--[RFC4502]
pwIndex FROM PW-STD-MIB -- [RFC5601]
来自PW-STD-MIB的pwIndex--[RFC5601]
VlanIdOrAnyOrNone FROM Q-BRIDGE-MIB; -- [RFC4363]
来自Q-BRIDGE-MIB的VLANIDoranyorone；——[RFC4363]
pwEnetStdMIB MODULE-IDENTITY LAST-UPDATED "200906150000Z" -- 15 June 2009 00:00:00 GMT
pwEnetStdMIB模块标识最后更新“200906150000Z”-2009年6月15日00:00:00 GMT
ORGANIZATION "Pseudowire Edge-to-Edge Emulation (PWE3) Working Group"
组织“伪线边到边仿真（PWE3）工作组”
CONTACT-INFO "David Zelig Email: davidz@oversi.com
联系人信息“David Zelig电子邮件：davidz@oversi.com
Thomas D. Nadeau Email: tom.nadeau@bt.com " DESCRIPTION "This MIB module describes a model for managing Ethernet point-to-point pseudowire services over a Packet Switched Network (PSN).
托马斯·纳多电子邮件：汤姆。nadeau@bt.com“说明”此MIB模块描述了一种用于通过分组交换网络（PSN）管理以太网点对点伪线服务的模型。
Copyright (c) 2009 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2009 IETF信托基金和被确定为代码作者的人员。版权所有。
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
在满足以下条件的情况下，允许以源代码和二进制格式重新分发和使用，无论是否修改：
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- 源代码的重新分发必须保留上述版权声明、此条件列表和以下免责声明。
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- 以二进制形式重新分发时，必须在分发时提供的文档和/或其他材料中复制上述版权声明、本条件列表和以下免责声明。
- Neither the name of Internet Society, IETF or IETF Trust, nor the names of specific contributors, may be used to endorse or promote products derived from this software without specific prior written permission.
- 未经事先书面许可，不得使用互联网协会、IETF或IETF Trust的名称或特定贡献者的名称来认可或推广源自本软件的产品。
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS 'AS IS' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
本软件由版权所有者和贡献者“按原样”提供，不承担任何明示或暗示的担保，包括但不限于适销性和特定用途适用性的暗示担保。在任何情况下，版权所有人或贡献者均不对任何直接、间接、偶然、特殊、惩戒性或后果性损害（包括但不限于替代商品或服务的采购；使用、数据或利润的损失；或业务中断）负责，无论是在合同中还是在任何责任理论下，严格责任，或因使用本软件而产生的侵权行为（包括疏忽或其他），即使告知可能发生此类损害。
This version of this MIB module is part of RFC 5603;
此版本的MIB模块是RFC 5603的一部分；
see the RFC itself for full legal notices."
有关完整的法律通知，请参见RFC本身。”
-- Revision history REVISION "200906150000Z" -- 15 June 2009 00:00:00 GMT DESCRIPTION "Initial version published as part of RFC 5603."
--修订历史版本“200906150000Z”-2009年6月15日00:00:00 GMT说明“作为RFC 5603的一部分发布的初始版本。”
::= { mib-2 180 }
::= { mib-2 180 }
pwEnetObjects OBJECT IDENTIFIER ::= { pwEnetStdMIB 1 }
pwEnetConformance OBJECT IDENTIFIER ::= { pwEnetStdMIB 2 }
pwEnetObjects OBJECT IDENTIFIER ::= { pwEnetStdMIB 1 }
pwEnetConformance OBJECT IDENTIFIER ::= { pwEnetStdMIB 2 }
-- -- Ethernet PW table --
----以太网PW表--
pwEnetTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwEnetEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the index to the Ethernet tables
associated with this Ethernet PW, the VLAN configuration,
and the VLAN mode."
::= { pwEnetObjects 1 }
pwEnetTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwEnetEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains the index to the Ethernet tables
associated with this Ethernet PW, the VLAN configuration,
and the VLAN mode."
::= { pwEnetObjects 1 }
pwEnetEntry OBJECT-TYPE SYNTAX PwEnetEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table is indexed by the same index that was created for the associated entry in the PW generic table in the
pwEnetEntry对象类型语法pwEnetEntry MAX-ACCESS not ACCESS STATUS current DESCRIPTION“此表由为中的PW generic表中的关联项创建的相同索引编制索引
PW-STD-MIB module. The pwIndex and the pwEnetPwInstance are used as indexes to allow multiple VLANs to exist on the same PW.
PW-STD-MIB模块。pwIndex和pwEnetPwInstance用作索引，以允许在同一PW上存在多个VLAN。
An entry is created in this table by the agent for every entry in the pwTable with a pwType of 'ethernetTagged' or 'ethernet'. Additional rows may be created by the operator or the agent if multiple entries are required for the same PW.
代理在此表中为pwTable中具有“ethernetTagged”或“ethernet”类型的每个条目创建一个条目。如果同一PW需要多个条目，操作员或代理可以创建其他行。
The value of pwEnetPwInstance can be arbitrarily selected to make the row unique; however, implementations that know the VLAN field value when the row is created MAY use the value of the VLAN itself for better readability and backward compatibility with older versions of this MIB
pwEnetPwInstance的值可以任意选择，使行唯一；但是，在创建行时知道VLAN字段值的实现可能会使用VLAN本身的值，以提高可读性并与此MIB的旧版本向后兼容
module.
单元
This table provides Ethernet port mapping and VLAN configuration for each Ethernet PW.
此表提供了每个以太网PW的以太网端口映射和VLAN配置。
All read-create objects in this table MAY be changed at any time; however, change of some objects (for example, pwEnetVlanMode) during the PW forwarding state MAY cause traffic disruption.
此表中的所有读取创建对象可以随时更改；但是，在PW转发状态期间更改某些对象（例如，pwEnetVlanMode）可能会导致通信中断。
Manual entries in this table SHOULD be preserved after a reboot, and the agent MUST ensure the integrity of those entries. If the set of entries of a specific row is found to be inconsistent after reboot, the PW pwOperStatus MUST be declared as notPresent(5). "
重新启动后应保留此表中的手动条目，并且代理必须确保这些条目的完整性。如果在重新启动后发现特定行的条目集不一致，则必须将PW pwOperStatus声明为notPresent（5）。"
INDEX { pwIndex, pwEnetPwInstance }
::= { pwEnetTable 1 }
INDEX { pwIndex, pwEnetPwInstance }
::= { pwEnetTable 1 }
PwEnetEntry ::= SEQUENCE {
pwEnetPwInstance Unsigned32,
pwEnetPwVlan VlanIdOrAnyOrNone,
pwEnetVlanMode INTEGER,
pwEnetPortVlan VlanIdOrAnyOrNone,
PwEnetEntry ::= SEQUENCE {
pwEnetPwInstance Unsigned32,
pwEnetPwVlan VlanIdOrAnyOrNone,
pwEnetVlanMode INTEGER,
pwEnetPortVlan VlanIdOrAnyOrNone,
pwEnetPortIfIndex InterfaceIndexOrZero, pwEnetPwIfIndex InterfaceIndexOrZero,
pwEnetPortIfIndex接口索引零，pwEnetPwIfIndex接口索引零，
pwEnetRowStatus RowStatus, pwEnetStorageType StorageType }
pwEnetRowStatus RowStatus，pwEnetStorageType StorageType}
pwEnetPwInstance OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "If multiple rows are mapped to the same PW, this index is used to uniquely identify the individual row. If the value of the VLAN field is known at the time of row creation, the value of pwEnetPwVlan MAY be used for better readability and backward compatibility with older versions of this MIB module. Otherwise, the value 1 SHOULD be set to the first row for each pwIndex for better readability and in order that the management application will know in advance how to access the first row when it was created by the agent.
pwEnetPwInstance对象类型语法Unsigned32 MAX-ACCESS不可访问状态当前描述如果多行映射到同一PW，则此索引用于唯一标识单个行。如果在创建行时知道VLAN字段的值，则可以使用pwEnetPwVlan的值来提高可读性，并与此MIB模块的旧版本向后兼容。否则，应将值1设置为每个pwIndex的第一行，以提高可读性，并使管理应用程序在代理创建第一行时提前知道如何访问第一行。
"
::= { pwEnetEntry 1 }
"
::= { pwEnetEntry 1 }
pwEnetPwVlan OBJECT-TYPE
SYNTAX VlanIdOrAnyOrNone
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object defines the (service-delimiting) VLAN field
value on the PW. The value 4095 MUST be used if the
object is not applicable, for example, when mapping all
packets from an Ethernet port to this PW (raw mode).
The value 0 MUST be set to indicate untagged frames
(from the PW point of view), i.e., when pwEnetVlanMode
equals 'noChange' and pwEnetPortVlan equals 0."
::= { pwEnetEntry 2 }
pwEnetPwVlan OBJECT-TYPE
SYNTAX VlanIdOrAnyOrNone
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object defines the (service-delimiting) VLAN field
value on the PW. The value 4095 MUST be used if the
object is not applicable, for example, when mapping all
packets from an Ethernet port to this PW (raw mode).
The value 0 MUST be set to indicate untagged frames
(from the PW point of view), i.e., when pwEnetVlanMode
equals 'noChange' and pwEnetPortVlan equals 0."
::= { pwEnetEntry 2 }
pwEnetVlanMode OBJECT-TYPE
SYNTAX INTEGER {
other(0),
portBased(1),
noChange(2),
changeVlan(3),
addVlan(4),
removeVlan(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the mode of VLAN handling between the
port or the virtual port associated with the PW and the
PW encapsulation.
pwEnetVlanMode OBJECT-TYPE
SYNTAX INTEGER {
other(0),
portBased(1),
noChange(2),
changeVlan(3),
addVlan(4),
removeVlan(5)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the mode of VLAN handling between the
port or the virtual port associated with the PW and the
PW encapsulation.
- 'other' indicates an operation that is not defined by this MIB module.
- “其他”表示此MIB模块未定义的操作。
- 'portBased' indicates that the forwarder will forward packets between the port and the PW independent of their structure (i.e., there are no service-delimiting VLAN tags from the PE standpoint).
- “基于端口”表示转发器将在端口和PW之间转发数据包，而不受其结构的影响（即，从PE的角度来看，没有服务界定VLAN标记）。
- 'noChange' indicates that the PW contains the original user VLAN, as specified in pwEnetPortVlan; i.e., the VLAN on the PE-CE link is the service-delimiting tag and is kept 'as is' on the PW.
- “noChange”表示PW包含原始用户VLAN，如pwEnetPortVlan中所指定；i、 例如，PE-CE链路上的VLAN是服务定界标签，在PW上保持“原样”。
- 'changeVlan' indicates that the VLAN field on the PW may be different than the VLAN field on the user's
- “changeVlan”表示PW上的VLAN字段可能不同于用户计算机上的VLAN字段
port. The VLAN on the PE-CE link is the service-delimiting tag but has a different value on the PW.
港口城市PE-CE链路上的VLAN是服务定界标记，但在PW上具有不同的值。
- 'addVlan' indicates that a VLAN field will be added on the PSN-bound direction (i.e., on the PW). pwEnetPwVlan indicates the value that will be added.
- “addVlan”表示将在PSN绑定方向（即PW）上添加VLAN字段。pwEnetPwVlan表示将要添加的值。
- 'removeVlan' indicates that the encapsulation on the PW does not include the service-delimiting VLAN field. Note that PRI bits transparency is lost in this case.
- “removeVlan”表示PW上的封装不包括服务定界VLAN字段。请注意，在这种情况下，PRI位透明度将丢失。
- Implementation of 'portsbased', 'removeVlan', 'addVlan'
'other', and 'changeVlan' is OPTIONAL.
"
DEFVAL { noChange }
::= { pwEnetEntry 3 }
- Implementation of 'portsbased', 'removeVlan', 'addVlan'
'other', and 'changeVlan' is OPTIONAL.
"
DEFVAL { noChange }
::= { pwEnetEntry 3 }
pwEnetPortVlan OBJECT-TYPE SYNTAX VlanIdOrAnyOrNone MAX-ACCESS read-create STATUS current DESCRIPTION "This object defines if the mapping between the original port (physical port or VPLS virtual port) to the PW is VLAN based or not. In case of VLAN mapping, this object indicates the VLAN value on the original port.
pwEnetPortVlan对象类型语法VlanIdOrAnyOrNone MAX-ACCESS read create STATUS current DESCRIPTION“此对象定义原始端口（物理端口或VPLS虚拟端口）到PW之间的映射是否基于VLAN。在VLAN映射的情况下，此对象指示原始端口上的VLAN值。
The value of '4095' MUST be used if the whole original port traffic is mapped to the same PW. Note that a pwType of 'ethernetTagged' can still be used if service-delimiting tag is added on the PW (pwEnetVlanMode equals 'addVlan').
如果整个原始端口流量映射到同一PW，则必须使用值“4095”。请注意，如果在PW上添加了服务定界标记（pwEnetVlanMode等于“addVlan”），则仍可使用“ethernetTagged”的pwType。
This object MUST be equal to pwEnetPwVlan if pwEnetVlanMode equals 'noChange'.
如果pwEnetVlanMode等于“noChange”，则此对象必须等于pwEnetPwVlan。
The value 0 indicates that packets without a VLAN field
(i.e., untagged frames) on the port are associated to this
PW. This allows the same behavior as assigning 'Default
VLAN' to untagged frames.
"
DEFVAL { 4095 }
::= { pwEnetEntry 4 }
The value 0 indicates that packets without a VLAN field
(i.e., untagged frames) on the port are associated to this
PW. This allows the same behavior as assigning 'Default
VLAN' to untagged frames.
"
DEFVAL { 4095 }
::= { pwEnetEntry 4 }
pwEnetPortIfIndex OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-create STATUS current DESCRIPTION
pwEnetPortIfIndex对象类型语法接口INDEXORZERO MAX-ACCESS读取创建状态当前描述
"This object is used to specify the ifIndex of the Ethernet port associated with this PW for point-to-point Ethernet service, or the ifIndex of the virtual interface of the VPLS instance associated with the PW if the service is VPLS. Two rows in this table can point to the same ifIndex only if there is no overlap of VLAN values specified in pwEnetPortVlan that are associated with this port.
“此对象用于为点到点以太网服务指定与此PW关联的以太网端口的ifIndex，或者如果服务为VPLS，则指定与此PW关联的VPLS实例的虚拟接口的ifIndex。只有在pwEnet中指定的VLAN值没有重叠时，此表中的两行才能指向同一ifIndex。”与此端口关联的PortVlan。
A value of zero indicates that association to an ifIndex is not yet known."
值为零表示尚未知道与ifIndex的关联。”
::= { pwEnetEntry 5 }
::= { pwEnetEntry 5 }
pwEnetPwIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If the PW is modeled as an ifIndex in the ifTable, this
object indicates the value of the ifIndex representing the
Ethernet PW on the PSN side in the Etherlike-MIB. Note that
this value may be different from the value of pwIfIndex
that represents the ifIndex of the PW for ifType 'pw'."
DEFVAL { 0 }
::= { pwEnetEntry 6 }
pwEnetPwIfIndex OBJECT-TYPE
SYNTAX InterfaceIndexOrZero
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"If the PW is modeled as an ifIndex in the ifTable, this
object indicates the value of the ifIndex representing the
Ethernet PW on the PSN side in the Etherlike-MIB. Note that
this value may be different from the value of pwIfIndex
that represents the ifIndex of the PW for ifType 'pw'."
DEFVAL { 0 }
::= { pwEnetEntry 6 }
pwEnetRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object enables creating, deleting, and modifying this
row."
::= { pwEnetEntry 7 }
pwEnetRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object enables creating, deleting, and modifying this
row."
::= { pwEnetEntry 7 }
pwEnetStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the storage type of this row."
DEFVAL { nonVolatile }
::= { pwEnetEntry 8 }
pwEnetStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object indicates the storage type of this row."
DEFVAL { nonVolatile }
::= { pwEnetEntry 8 }
-- -- Ethernet PW Statistics Table --
----以太网PW统计表--
pwEnetStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwEnetStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains statistical counters specific for
Ethernet PW."
::= { pwEnetObjects 2 }
pwEnetStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF PwEnetStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains statistical counters specific for
Ethernet PW."
::= { pwEnetObjects 2 }
pwEnetStatsEntry OBJECT-TYPE
SYNTAX PwEnetStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry represents the statistics gathered for the
PW carrying the Ethernet."
INDEX { pwIndex }
::= { pwEnetStatsTable 1 }
pwEnetStatsEntry OBJECT-TYPE
SYNTAX PwEnetStatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Each entry represents the statistics gathered for the
PW carrying the Ethernet."
INDEX { pwIndex }
::= { pwEnetStatsTable 1 }
PwEnetStatsEntry ::= SEQUENCE {
pwEnetStatsIllegalVlan ZeroBasedCounter32,
pwEnetStatsIllegalLength ZeroBasedCounter32
}
PwEnetStatsEntry ::= SEQUENCE {
pwEnetStatsIllegalVlan ZeroBasedCounter32,
pwEnetStatsIllegalLength ZeroBasedCounter32
}
pwEnetStatsIllegalVlan OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received (from the PSN) on this PW
with either an illegal VLAN field, a missing VLAN field
when one was expected, or an excessive VLAN field when
it was not expected. This counter may not be applicable
in some cases, and MUST return the value of zero in
such a case."
::= { pwEnetStatsEntry 1 }
pwEnetStatsIllegalVlan OBJECT-TYPE
SYNTAX ZeroBasedCounter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The number of packets received (from the PSN) on this PW
with either an illegal VLAN field, a missing VLAN field
when one was expected, or an excessive VLAN field when
it was not expected. This counter may not be applicable
in some cases, and MUST return the value of zero in
such a case."
::= { pwEnetStatsEntry 1 }
pwEnetStatsIllegalLength OBJECT-TYPE SYNTAX ZeroBasedCounter32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of packets that were received with an illegal Ethernet packet length on this PW. An illegal length is defined as being greater than the value in the advertised MTU supported, or shorter than the allowed Ethernet packet size."
PWENETSTATSILLEGALLENGHT对象类型语法ZeroBasedCounter32 MAX-ACCESS只读状态当前描述“在此PW上以非法以太网数据包长度接收的数据包数。非法长度定义为大于受支持的播发MTU中的值，或小于允许的以太网数据包大小。”
::= { pwEnetStatsEntry 2 }
::= { pwEnetStatsEntry 2 }
---
--- Conformance description
---
---
--- Conformance description
---
pwEnetGroups OBJECT IDENTIFIER ::= { pwEnetConformance 1 }
pwEnetCompliances OBJECT IDENTIFIER ::= { pwEnetConformance 2 }
pwEnetGroups OBJECT IDENTIFIER ::= { pwEnetConformance 1 }
pwEnetCompliances OBJECT IDENTIFIER ::= { pwEnetConformance 2 }
-- Compliance requirement for fully compliant implementations
--完全合规实施的合规性要求
pwEnetModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for agents that provides full
support for the PW-ENET-STD-MIB module. Such devices
can then be monitored and also be configured using
this MIB module."
MODULE -- this module
MANDATORY-GROUPS {
pwEnetGroup,
pwEnetStatsGroup
}
pwEnetModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for agents that provides full
support for the PW-ENET-STD-MIB module. Such devices
can then be monitored and also be configured using
this MIB module."
MODULE -- this module
MANDATORY-GROUPS {
pwEnetGroup,
pwEnetStatsGroup
}
OBJECT pwEnetVlanMode DESCRIPTION "An implementation MUST support at least the value noChange(2)."
对象pwEnetVlanMode描述“实现必须至少支持noChange（2）值。”
OBJECT pwEnetPwIfIndex
MIN-ACCESS read-only
DESCRIPTION "Write access and values other than zero are
required only for implementations that support
modeling the Ethernet PW in the Etherlike-MIB."
OBJECT pwEnetRowStatus
SYNTAX RowStatus { active(1), notInService(2),
notReady(3) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6)
}
MIN-ACCESS read-only
DESCRIPTION "Support for createAndWait is not required. Support
of notReady is not required for implementations that
do not support signaling.
Support of read-write is not required for
implementations that do not support more than one
VLAN mapping to the same PW."
::= { pwEnetCompliances 1 }
OBJECT pwEnetPwIfIndex
MIN-ACCESS read-only
DESCRIPTION "Write access and values other than zero are
required only for implementations that support
modeling the Ethernet PW in the Etherlike-MIB."
OBJECT pwEnetRowStatus
SYNTAX RowStatus { active(1), notInService(2),
notReady(3) }
WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6)
}
MIN-ACCESS read-only
DESCRIPTION "Support for createAndWait is not required. Support
of notReady is not required for implementations that
do not support signaling.
Support of read-write is not required for
implementations that do not support more than one
VLAN mapping to the same PW."
::= { pwEnetCompliances 1 }
-- Compliance requirement for read-only compliant implementations
--只读兼容实现的法规遵从性要求
pwEnetModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for agents that provide read-only support for the PW-ENET-STD-MIB module. Such devices can then be monitored but cannot be configured using this MIB module."
PWENETModuleRadonlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“为PW-ENET-STD-MIB模块提供只读支持的代理的符合性声明。然后可以监视此类设备，但不能使用此MIB模块进行配置。”
MODULE -- this module MANDATORY-GROUPS { pwEnetGroup, pwEnetStatsGroup }
MODULE——此模块为强制组{pWenteGroup，pWenteStatsGroup}
OBJECT pwEnetPwVlan MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象pwEnetPwVlan最小访问只读描述“不需要写访问。”
OBJECT pwEnetVlanMode MIN-ACCESS read-only DESCRIPTION "Write access is not required. An implementation MUST support at least the value noChange(2)."
对象pwEnetVlanMode MIN-ACCESS只读说明“不需要写访问。实现必须至少支持noChange（2）值。”
OBJECT pwEnetPortVlan MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象pwEnetPortVlan最小访问只读描述“不需要写访问。”
OBJECT pwEnetPortIfIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象pwEnetPortIfIndex MIN-ACCESS只读说明“不需要写访问。”
OBJECT pwEnetPwIfIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required. Values other than zero are required only for implementations that support modeling the Ethernet PW in the Etherlike-MIB."
对象pwEnetPwIfIndex MIN-ACCESS只读描述“不需要写访问。只有支持以太MIB中以太网PW建模的实现才需要零以外的值。”
OBJECT pwEnetRowStatus SYNTAX RowStatus { active(1), notInService(2), notReady(3) } MIN-ACCESS read-only DESCRIPTION "Write access is not required. Support of notReady is not required for implementations that do not support signaling."
对象pwEnetRowStatus语法RowStatus{active（1）、notInService（2）、notReady（3）}MIN-ACCESS只读说明“不需要写访问。不支持信令的实现不需要支持notReady。”
OBJECT pwEnetStorageType
对象类型
MIN-ACCESS read-only DESCRIPTION "Write access is not required."
MIN-ACCESS只读说明“不需要写访问。”
::= { pwEnetCompliances 2 }
::= { pwEnetCompliances 2 }
-- Units of conformance
--一致性单位
pwEnetGroup OBJECT-GROUP
OBJECTS {
pwEnetPwVlan,
pwEnetVlanMode,
pwEnetPortVlan,
pwEnetPortIfIndex,
pwEnetPwIfIndex,
pwEnetRowStatus,
pwEnetStorageType
}
STATUS current
DESCRIPTION
"Collection of objects for basic Ethernet PW configuration."
::= { pwEnetGroups 1 }
pwEnetGroup OBJECT-GROUP
OBJECTS {
pwEnetPwVlan,
pwEnetVlanMode,
pwEnetPortVlan,
pwEnetPortIfIndex,
pwEnetPwIfIndex,
pwEnetRowStatus,
pwEnetStorageType
}
STATUS current
DESCRIPTION
"Collection of objects for basic Ethernet PW configuration."
::= { pwEnetGroups 1 }
pwEnetStatsGroup OBJECT-GROUP
OBJECTS {
pwEnetStatsIllegalVlan,
pwEnetStatsIllegalLength
}
STATUS current
DESCRIPTION
"Collection of objects counting various PW level errors."
::= { pwEnetGroups 2 }
pwEnetStatsGroup OBJECT-GROUP
OBJECTS {
pwEnetStatsIllegalVlan,
pwEnetStatsIllegalLength
}
STATUS current
DESCRIPTION
"Collection of objects counting various PW level errors."
::= { pwEnetGroups 2 }
END
终止
It is clear that this MIB module is potentially useful for monitoring of PW-capable PEs. This MIB module can also be used for configuration of certain objects, and anything that can be configured can be incorrectly configured, with potentially disastrous results.
很明显，该MIB模块对于监控具有PW功能的PEs可能有用。此MIB模块还可用于配置某些对象，可以配置的任何内容都可能被错误配置，从而导致潜在的灾难性后果。
There are a number of management objects defined in this MIB module with 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. These are the tables and objects and their sensitivity/vulnerability:
此MIB模块中定义了许多管理对象，其MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。以下是表和对象及其敏感度/漏洞：
o the pwEnetTable contains objects to provision Ethernet PWs. Unauthorized access to objects in these tables could result in disruption of traffic on the network. The use of stronger mechanisms such as SNMPv3 security should be considered where possible. Specifically, SNMPv3 VACM and USM MUST be used with any v3 agent that implements this MIB module. Administrators should consider whether read access to these objects should be allowed, since read access may be undesirable under certain circumstances.
o PWENetable包含用于配置以太网PWs的对象。未经授权访问这些表中的对象可能会导致网络流量中断。在可能的情况下，应考虑使用更强的机制，如SNMPv3安全性。具体来说，SNMPv3 VACM和USM必须与实现此MIB模块的任何v3代理一起使用。管理员应该考虑是否应该允许对这些对象的读访问，因为在某些情况下读访问可能是不可取的。
Some of the readable objects in this MIB module (i.e., objects with a MAX-ACCESS other than not-accessible) may be considered sensitive or vulnerable in some network environments. It is thus important to control even GET and/or NOTIFY access to these objects and possibly to even encrypt the values of these objects when sending them over the network via SNMP. These are the tables and objects and their sensitivity/vulnerability:
在某些网络环境中，此MIB模块中的某些可读对象（即具有MAX-ACCESS而非not ACCESS的对象）可能被视为敏感或易受攻击。因此，在通过SNMP通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
o the pwEnetTable shows the Ethernet PW service configuration. If an administrator does not want to reveal this information, then these tables should be considered sensitive/vulnerable.
o PWENETER表显示以太网PW服务配置。如果管理员不想透露此信息，则应将这些表视为敏感/易受攻击。
SNMP versions prior to SNMPv3 did not include adequate security. 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 module.
SNMPv3之前的SNMP版本未包含足够的安全性。即使网络本身是安全的（例如通过使用IPsec），即使如此，也无法控制安全网络上的谁可以访问和获取/设置（读取/更改/创建/删除）此MIB模块中的对象。
It is RECOMMENDED that implementers consider the security features as provided by the SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3 cryptographic mechanisms (for authentication and privacy).
建议实施者考虑SNMPv3框架所提供的安全特性（参见[RCFC310]，第8节），包括对SNMPv3加密机制的完全支持（用于身份验证和隐私）。
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module 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.
此外，不建议部署SNMPv3之前的SNMP版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER value recorded in the SMI Numbers registry:
本文档中的MIB模块使用SMI编号注册表中记录的以下IANA分配对象标识符值：
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
Descriptor OBJECT IDENTIFIER value
---------- -----------------------
pwEnetStdMIB { mib-2 180 }
pwEnetStdMIB{mib-2180}
[BCP14] Bradner, S., "Key words for use in RFCs to Indicate requirement Levels", BCP 14, RFC 2119, March 1997.
[BCP14]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2578]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，1999年4月。
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2579]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的文本约定”，STD 58，RFC 2579，1999年4月。
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2580]McCloghrie，K.，Perkins，D.，和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年6月。
[RFC3635] Flick, J., "Definitions of Managed Objects for the Ethernet-like Interface Types", RFC 3635, September 2003.
[RFC3635]Flick，J.，“类似以太网接口类型的托管对象定义”，RFC 3635，2003年9月。
[RFC4448] Martini, L., Ed., Rosen, E., El-Aawar, N., and G. Heron, "Encapsulation Methods for Transport of Ethernet over MPLS Networks", RFC 4448, April 2006.
[RFC4448]Martini，L.，Ed.，Rosen，E.，El Aawar，N.，和G.Heron，“通过MPLS网络传输以太网的封装方法”，RFC 4448，2006年4月。
[RFC4502] Waldbusser, S., "Remote Network Monitoring Management Information Base Version 2", RFC 4502, May 2006.
[RFC4502]Waldbusser，S.，“远程网络监控管理信息库版本2”，RFC4502，2006年5月。
[RFC4363] Levi, D. and D. Harrington, "Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering, and Virtual LAN Extensions", RFC 4363, January 2006.
[RFC4363]Levi，D.和D.Harrington，“具有流量类、多播过滤和虚拟LAN扩展的网桥的托管对象定义”，RFC 4363，2006年1月。
[RFC5601] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) Management Information Base (MIB)", RFC 5601, July 2009.
[RFC5601]Zelig，D.，Ed.，和T.Nadeau，Ed.，“伪线（PW）管理信息库（MIB）”，RFC 56012009年7月。
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年12月。
[RFC3916] Xiao, X., Ed., McPherson, D., Ed., and P. Pate, Ed., "Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3)", RFC 3916, September 2004.
[RFC3916]Xiao，X.，Ed.，McPherson，D.，Ed.，和P.Pate，Ed.，“伪线仿真边到边（PWE3）的要求”，RFC 39162004年9月。
[RFC3985] Bryant, S., Ed., and P. Pate, Ed., "Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture", RFC 3985, March 2005.
[RFC3985]Bryant，S.，Ed.，和P.Pate，Ed.，“伪线仿真边到边（PWE3）架构”，RFC 39852005年3月。
[RFC4664] Andersson, L., Ed., and E. Rosen, Ed., "Framework for Layer 2 Virtual Private Networks (L2VPNs)", RFC 4664, September 2006.
[RFC4664]Andersson，L.，Ed.，和E.Rosen，Ed.，“第二层虚拟专用网络（L2VPN）框架”，RFC 4664，2006年9月。
[RFC5542] Nadeau, T., Ed., Zelig, D., Ed., and O. Nicklass, Ed., "Definitions of Textual Conventions for Pseudowires (PW) Management", RFC 5542, May 2009.
[RFC5542]Nadeau，T.，Ed.，Zelig，D.，Ed.，和O.Nicklass，Ed.，“伪线（PW）管理文本约定的定义”，RFC 5542，2009年5月。
[RFC5602] Zelig, D., Ed., and T. Nadeau, Ed., "Pseudowire (PW) over MPLS PSN Management Information Base (MIB)", RFC 5602, July 2009.
[RFC5602]Zelig，D.，Ed.，和T.Nadeau，Ed.，“MPLS PSN管理信息库（MIB）上的伪线（PW）”，RFC 5602，2009年7月。
This document was produced by the PWE3 Working Group. Special thanks to Orly Nicklass for close review and good suggestions.
本文件由PWE3工作组编制。特别感谢Orly Nicklass的仔细审查和良好建议。
Authors' Addresses
作者地址
David Zelig (editor) Oversi Networks 1 Rishon Letzion St. Petah Tikva Israel
David Zelig（编辑）Oversi Networks 1 Rishon Letzion St.Petah Tikva以色列
Phone: +972 77 3337 750
EMail: davidz@oversi.com
Phone: +972 77 3337 750
EMail: davidz@oversi.com
Thomas D. Nadeau (editor) BT BT Centre 81 Newgate Street London EC1A 7AJ United Kingdom
Thomas D.Nadeau（编辑）英国电信中心伦敦纽盖特街81号EC1A 7AJ英国电信中心
EMail: tom.nadeau@bt.com
EMail: tom.nadeau@bt.com