Internet Engineering Task Force (IETF) P. Pan
Request for Comments: 7697 Infinera
Category: Standards Track S. Aldrin
ISSN: 2070-1721 Google, Inc.
M. Venkatesan
Dell, Inc.
K. Sampath
Redeem
T. Nadeau
Brocade
S. Boutros
VMware, Inc.
January 2016
Internet Engineering Task Force (IETF) P. Pan
Request for Comments: 7697 Infinera
Category: Standards Track S. Aldrin
ISSN: 2070-1721 Google, Inc.
M. Venkatesan
Dell, Inc.
K. Sampath
Redeem
T. Nadeau
Brocade
S. Boutros
VMware, Inc.
January 2016
MPLS Transport Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM) Identifiers Management Information Base (MIB)
MPLS传输配置文件（MPLS-TP）操作、管理和维护（OAM）标识符管理信息库（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 to configure the Operations, Administration, and Maintenance (OAM) identifiers for Multiprotocol Label Switching (MPLS) and the MPLS-based Transport Profile (TP).
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了用于配置多协议标签交换（MPLS）和基于MPLS的传输配置文件（TP）的操作、管理和维护（OAM）标识符的托管对象。
Status of This Memo
关于下段备忘
This is an Internet Standards Track document.
这是一份互联网标准跟踪文件。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。有关互联网标准的更多信息，请参见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7697.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7697.
Copyright Notice
版权公告
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2016 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................3
2. The Internet-Standard Management Framework ......................3
3. Overview ........................................................3
3.1. Conventions Used in This Document ..........................3
3.2. Terminology ................................................4
3.3. Acronyms ...................................................4
4. Feature List ....................................................5
5. Brief Description of MIB Objects ................................5
5.1. mplsOamIdMegTable ..........................................5
5.2. mplsOamIdMeTable ...........................................5
6. MPLS OAM Identifier Configuration for MPLS LSP: Example .........6
7. MPLS OAM Identifiers MIB Definitions ............................8
8. Security Considerations ........................................31
9. IANA Considerations ............................................32
9.1. IANA Considerations for MPLS-OAM-ID-STD-MIB ...............32
10. References ....................................................32
10.1. Normative References .....................................32
10.2. Informative References ...................................34
Acknowledgments ...................................................35
Authors' Addresses ................................................36
1. Introduction ....................................................3
2. The Internet-Standard Management Framework ......................3
3. Overview ........................................................3
3.1. Conventions Used in This Document ..........................3
3.2. Terminology ................................................4
3.3. Acronyms ...................................................4
4. Feature List ....................................................5
5. Brief Description of MIB Objects ................................5
5.1. mplsOamIdMegTable ..........................................5
5.2. mplsOamIdMeTable ...........................................5
6. MPLS OAM Identifier Configuration for MPLS LSP: Example .........6
7. MPLS OAM Identifiers MIB Definitions ............................8
8. Security Considerations ........................................31
9. IANA Considerations ............................................32
9.1. IANA Considerations for MPLS-OAM-ID-STD-MIB ...............32
10. References ....................................................32
10.1. Normative References .....................................32
10.2. Informative References ...................................34
Acknowledgments ...................................................35
Authors' Addresses ................................................36
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 a Transport Profile (TP) based on Multiprotocol Label Switching (MPLS) [RFC3031].
此备忘录定义了管理信息库（MIB）的一部分，用于Internet社区中的网络管理协议。特别是，它描述了用于基于多协议标签交换（MPLS）建模传输配置文件（TP）的托管对象[RFC3031]。
This MIB module should be used for performing the OAM (Operations, Administration, and Maintenance) operations for MPLS Tunnel LSPs (Label Switched Paths), Pseudowires, and Sections.
此MIB模块应用于执行MPLS隧道LSP（标签交换路径）、伪线和段的OAM（操作、管理和维护）操作。
At the time of this writing, SNMP SET is no longer recommended as a way to configure MPLS networks as was described in [RFC3812]. However, since the MIB modules specified in this document are intended to work in parallel with the MIB modules for MPLS specified in [RFC3812], certain objects defined here are specified with a MAX-ACCESS of read-write or read-create so that specifications of the base tables in [RFC3812] and the new MIB modules in this document are consistent. Although the example described in Section 6 specifies means to configure OAM identifiers for MPLS-TP Tunnels, this should be seen as indicating how the MIB values would be returned in the specified circumstances having been configured by alternative means.
在撰写本文时，不再推荐使用SNMP集作为配置MPLS网络的方法，如[RFC3812]中所述。但是，由于本文档中指定的MIB模块旨在与[RFC3812]中指定的MPLS MIB模块并行工作，因此此处定义的某些对象以读写或读创建的最大访问权限进行指定，以便[RFC3812]中的基表规范与本文档中的新MIB模块一致。尽管第6节中描述的示例指定了为MPLS-TP隧道配置OAM标识符的方法，但这应被视为指示在通过替代方法配置的指定情况下如何返回MIB值。
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC3410 [RFC3410].
有关描述当前互联网标准管理框架的文件的详细概述，请参阅RFC3410[RFC3410]第7节。
Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the 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 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].
托管对象通过虚拟信息存储（称为管理信息库或MIB）进行访问。MIB对象通常通过简单网络管理协议（SNMP）进行访问。MIB中的对象是使用管理信息结构（SMI）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”应按照RFC 2119[RFC2119]中的说明进行解释。
This document uses terminology from the Multiprotocol Label Switching Architecture [RFC3031], the MPLS Traffic Engineering (TE) MIB [RFC3812], the MPLS Label Switching Router (LSR) MIB [RFC3813], the OAM Framework for MPLS-Based Transport Networks [RFC6371], "MPLS Transport Profile (MPLS-TP) Identifiers" [RFC6370], MPLS-TP Identifiers Following ITU-T Conventions [RFC6923], and OAM in MPLS Transport Networks [RFC5860].
本文件使用了多协议标签交换体系结构[RFC3031]、MPLS流量工程（TE）MIB[RFC3812]、MPLS标签交换路由器（LSR）MIB[RFC3813]、基于MPLS的传输网络的OAM框架[RFC6371]、“MPLS传输配置文件（MPLS-TP）标识符”[RFC6370]中的术语，遵循ITU-T约定的MPLS-TP标识符[RFC6923]，以及MPLS传输网络中的OAM[RFC5860]。
BFD: Bidirectional Forwarding Detection
双向转发检测
ICC: ITU Carrier Code
国际电联载波代码
IP: Internet Protocol
互联网协议
LSP: Label Switched Path
标签交换路径
LSR: Label Switching Router
标签交换路由器
ME: Maintenance Entity
ME：维护实体
MEG: Maintenance Entity Group
MEG：维护实体组
MEP: Maintenance Entity Group End Point
MEP：维护实体组终点
MIB: Management Information Base
管理信息库
MIP: Maintenance Entity Group Intermediate Point
MIP：维护实体组中间点
MP: Maintenance Point
MP：维修点
MPLS: Multiprotocol Label Switching
多协议标签交换
MPLS-TP: MPLS Transport Profile
MPLS-TP:MPLS传输配置文件
PW: Pseudowire
伪线
TE: Traffic Engineering
交通工程
TP: Transport Profile
TP：运输概况
The MPLS transport profile OAM identifiers MIB module is designed to satisfy the following requirements and constraints:
MPLS传输配置文件OAM标识符MIB模块旨在满足以下要求和约束：
- The MIB module supports configuration of OAM identifiers for MPLS point-to-point Tunnels, point-to-multipoint LSPs, co-routed bidirectional LSPs, associated bidirectional LSPs, and Pseudowires.
- MIB模块支持为MPLS点对点隧道、点对多点LSP、共路由双向LSP、关联双向LSP和伪线配置OAM标识符。
The objects described in this section support the functionality described in [RFC5654] and [RFC6370]. The tables support both IP-compatible and ICC-based OAM identifiers configurations for MPLS Tunnels, LSPs, and Pseudowires.
本节中描述的对象支持[RFC5654]和[RFC6370]中描述的功能。这些表支持MPLS隧道、LSP和伪线的IP兼容和基于ICC的OAM标识符配置。
The mplsOamIdMegTable is used to manage one or more Maintenance Entities (MEs) that belong to the same transport path.
MPLSOMAGE表用于管理属于同一传输路径的一个或多个维护实体（ME）。
When a new entry is created with mplsOamIdMegOperatorType set to ipCompatible (1), then as per [RFC6370] (MEG_ID for an LSP is LSP_ID, and MEG_ID for a PW is PW_Path_ID), MEP_ID can be automatically formed.
当创建一个新条目时，mplsOamIdMegOperatorType设置为ipCompatible（1），则根据[RFC6370]（LSP的MEG_ID为LSP_ID，PW的MEG_ID为PW_路径_ID），可以自动形成MEP_ID。
For an ICC-based transport path, the user is expected to configure the ICC identifier explicitly in this table for MPLS Tunnels, LSPs, and Pseudowires.
对于基于ICC的传输路径，用户应在此表中明确配置MPLS隧道、LSP和伪线的ICC标识符。
The mplsOamIdMeTable defines a relationship between two points (source and sink) of a transport path to which maintenance and monitoring operations apply. The two points that define an ME are called Maintenance Entity Group End Points (MEPs).
mplsOamIdMeTable定义了维护和监视操作应用到的传输路径的两点（源和汇）之间的关系。定义ME的两点称为维护实体组端点（MEP）。
In between MEPs, there are zero or more intermediate points, called Maintenance Entity Group Intermediate Points (MIPs). MEPs and MIPs are associated with the MEG and can be shared by more than one ME in a MEG.
在MEP之间，有零个或多个中间点，称为维护实体组中间点（MIP）。MEP和MIP与MEG关联，可由MEG中的多个ME共享。
In this section, we provide an example of the OAM identifier configuration for an MPLS co-routed bidirectional LSP.
在本节中，我们提供了一个MPLS共路由双向LSP的OAM标识符配置示例。
This example provides usage of MEG and ME tables for management and monitoring operations of an MPLS LSP.
此示例提供了MEG和ME表的使用，用于管理和监视MPLS LSP的操作。
This example considers the OAM identifiers configuration on a head-end LSR to manage and monitor an MPLS LSP. Only relevant objects that are applicable for IP-based OAM identifiers of MPLS co-routed bidirectional LSPs are illustrated here.
此示例考虑头端LSR上的OAM标识符配置，以管理和监视MPLS LSP。这里仅说明适用于MPLS共同路由的双向lsp的基于IP的OAM标识符的相关对象。
In the mplsOamIdMegTable:
在MPLS表格中：
{
-- MEG index (Index to the table)
mplsOamIdMegIndex = 1,
mplsOamIdMegName = "MEG1",
mplsOamIdMegOperatorType = ipCompatible (1),
mplsOamIdMegServicePointerType = lsp (1),
mplsOamIdMegMpLocation = perNode (1),
-- Mandatory parameters needed to activate the row go here
{
-- MEG index (Index to the table)
mplsOamIdMegIndex = 1,
mplsOamIdMegName = "MEG1",
mplsOamIdMegOperatorType = ipCompatible (1),
mplsOamIdMegServicePointerType = lsp (1),
mplsOamIdMegMpLocation = perNode (1),
-- Mandatory parameters needed to activate the row go here
mplsOamIdMegRowStatus = createAndGo (4), mplsOamIdMegPathFlow = coRoutedBidirectionalPointToPoint (2) }
mplsOamIdMegRowStatus=createAndGo（4），mplsOamIdMegPathFlow=coRoutedBidirectionalPointToPoint（2）}
This will create an entry in the mplsOamIdMegTable to manage and monitor the MPLS Tunnel.
这将在MPLS表中创建一个条目来管理和监视MPLS隧道。
The following ME table is used to associate the path information to a MEG.
下表用于将路径信息与MEG关联。
In the mplsOamIdMeTable:
在MPLSOAMIDETABLE中：
{ -- ME index (Index to the table) mplsOamIdMeIndex = 1,
{--ME索引（表的索引）mplsOamIdMeIndex=1，
-- MP index (Index to the table)
mplsOamIdMeMpIndex = 1,
mplsOamIdMeName = "ME1",
mplsOamIdMeMpIfIndex = 0,
-- The source MEP ID is derived from the IP-compatible MPLS LSP
mplsOamIdMeSourceMepIndex = 0,
-- The sink MEP ID is derived from the IP-compatible MPLS LSP
mplsOamIdMeSinkMepIndex = 0,
mplsOamIdMeMpType = mep (1),
mplsOamIdMeMepDirection = down (2),
-- RowPointer MUST point to the first accessible column of an
-- MPLS LSP
mplsOamIdMeServicePointer = mplsTunnelName.1.1.10.20,
-- Mandatory parameters needed to activate the row go here
mplsOamIdMeRowStatus = createAndGo (4)
}
-- MP index (Index to the table)
mplsOamIdMeMpIndex = 1,
mplsOamIdMeName = "ME1",
mplsOamIdMeMpIfIndex = 0,
-- The source MEP ID is derived from the IP-compatible MPLS LSP
mplsOamIdMeSourceMepIndex = 0,
-- The sink MEP ID is derived from the IP-compatible MPLS LSP
mplsOamIdMeSinkMepIndex = 0,
mplsOamIdMeMpType = mep (1),
mplsOamIdMeMepDirection = down (2),
-- RowPointer MUST point to the first accessible column of an
-- MPLS LSP
mplsOamIdMeServicePointer = mplsTunnelName.1.1.10.20,
-- Mandatory parameters needed to activate the row go here
mplsOamIdMeRowStatus = createAndGo (4)
}
MPLS-OAM-ID-STD-MIB DEFINITIONS ::= BEGIN
MPLS-OAM-ID-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Unsigned32 FROM SNMPv2-SMI -- RFC 2578 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- RFC 2580 RowStatus, RowPointer, StorageType FROM SNMPv2-TC -- RFC 2579 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- RFC 3411 IndexIntegerNextFree FROM DIFFSERV-MIB -- RFC 3289 mplsStdMIB FROM MPLS-TC-STD-MIB -- RFC 3811 InterfaceIndexOrZero, ifGeneralInformationGroup, ifCounterDiscontinuityGroup FROM IF-MIB; -- RFC 2863
从SNMPv2 SMI导入MODULE-IDENTITY、OBJECT-TYPE、NOTIFICATION-TYPE、Unsigned32--从SNMPv2 CONF导入RFC 2578 MODULE-COMPLIANCE、OBJECT-GROUP、NOTIFICATION-GROUP--从RFC 2580 RowStatus、RowPointer、，SNMPv2 TC中的StorageType--SNMP-FRAMEWORK-MIB中的RFC 2579 SNMPAdminInstalling--DIFFSERV-MIB中的RFC 3411 IndexIntegerExtFree--MPLS-TC-STD-MIB中的RFC 3289 MPLSTDMIB--RFC 3811 InterfaceIndexOrZero，IF-MIB中的ifGeneralInformationGroup，IFCounterInterruptyGroup；--RFC 2863
mplsOamIdStdMIB MODULE-IDENTITY LAST-UPDATED "201601070000Z" -- January 07, 2016 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO "Sam Aldrin Google, Inc. 1600 Amphitheatre Parkway Mountain View, CA 94043 USA Email: aldrin.ietf@gmail.com
mplsOamIdStdMIB MODULE-IDENTITY上次更新的“201601070000Z”-2016年1月7日组织“多协议标签交换（MPLS）工作组”联系方式“Sam Aldrin Google，Inc.1600美国加利福尼亚州山景公园圆形剧场邮编94043电子邮件：Aldrin。ietf@gmail.com
Thomas D. Nadeau Email: tnadeau@lucidvision.com
Thomas D.Nadeau电子邮件：tnadeau@lucidvision.com
Venkatesan Mahalingam Dell, Inc. 5450 Great America Parkway Santa Clara, CA 95054 USA Email: venkat.mahalingams@gmail.com
Venkatesan Mahalingam Dell，Inc.美国加利福尼亚州圣克拉拉大美洲大道5450号，邮编95054电子邮件：venkat。mahalingams@gmail.com
Kannan KV Sampath Redeem India Email: kannankvs@gmail.com
Kannan KV Sampath兑换印度电子邮件：kannankvs@gmail.com
Ping Pan Infinera
平盘酒店
Sami Boutros VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 USA Email: sboutros@vmware.com"
Sami Boutros VMware，Inc.美国加利福尼亚州帕洛阿尔托Hillview大道3401号，邮编94304电子邮件：sboutros@vmware.com"
DESCRIPTION "Copyright (c) 2016 IETF Trust and the persons identified as authors of the code. All rights reserved.
说明“版权所有（c）2016 IETF信托基金和被确定为代码作者的人员。保留所有权利。
Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).
根据IETF信托有关IETF文件的法律规定第4.c节规定的简化BSD许可证中包含的许可条款，允许以源代码和二进制格式重新分发和使用，无论是否修改(http://trustee.ietf.org/license-info).
This MIB module contains generic object definitions for MPLS OAM identifiers."
此MIB模块包含MPLS OAM标识符的通用对象定义。”
-- Revision history
--修订历史
REVISION "201601070000Z" -- January 07, 2016 DESCRIPTION "MPLS OAM Identifiers MIB objects for Tunnels, LSPs, Pseudowires, and Sections."
修订版“201601070000Z”-2016年1月7日描述“隧道、LSP、伪线和区段的MPLS OAM标识符MIB对象”
::= { mplsStdMIB 21 }
::= { mplsStdMIB 21 }
-- Top-level components of this MIB module
--此MIB模块的顶级组件
-- notifications
mplsOamIdNotifications
OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 0 }
-- tables, scalars
mplsOamIdObjects OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 1 }
-- notifications
mplsOamIdNotifications
OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 0 }
-- tables, scalars
mplsOamIdObjects OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 1 }
-- conformance
mplsOamIdConformance
OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 2 }
-- conformance
mplsOamIdConformance
OBJECT IDENTIFIER ::= { mplsOamIdStdMIB 2 }
-- Start of MPLS Transport Profile MEG table
--开始MPLS传输配置文件MEG表
mplsOamIdMegIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..4294967295)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
mplsOamIdMegIndex, or a zero to indicate
that none exist. Negative values are not allowed,
as they do not correspond to valid values of
mplsOamIdMegIndex."
::= { mplsOamIdObjects 1 }
mplsOamIdMegIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..4294967295)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
mplsOamIdMegIndex, or a zero to indicate
that none exist. Negative values are not allowed,
as they do not correspond to valid values of
mplsOamIdMegIndex."
::= { mplsOamIdObjects 1 }
mplsOamIdMegTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsOamIdMegEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains information about the Maintenance Entity Groups (MEGs).
MPLSOMIDEMAGTABLE MPLSOMIDEMAGENTRY的对象类型语法序列MAX-ACCESS not ACCESS STATUS current DESCRIPTION“此表包含有关维护实体组（MEG）的信息。
A MEG, as mentioned in the MPLS-TP OAM framework, defines
a set of one or more Maintenance Entities (MEs).
MEs define a relationship between any two points of a
transport path in an OAM domain to which maintenance and
monitoring operations apply."
::= { mplsOamIdObjects 2 }
A MEG, as mentioned in the MPLS-TP OAM framework, defines
a set of one or more Maintenance Entities (MEs).
MEs define a relationship between any two points of a
transport path in an OAM domain to which maintenance and
monitoring operations apply."
::= { mplsOamIdObjects 2 }
mplsOamIdMegEntry OBJECT-TYPE SYNTAX MplsOamIdMegEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents an MPLS-TP MEG. An entry can be created by a network administrator or by an SNMP agent as instructed by an MPLS-TP OAM framework.
MPLSAMIDEMEGENTRY对象类型语法MPLSAMIDEMEGENTRY MAX-ACCESS not ACCESS STATUS current DESCRIPTION“此表中的条目表示MPLS-TP MEG。条目可以由网络管理员或SNMP代理按照MPLS-TP OAM框架的指示创建。
When a new entry is created with mplsOamIdMegOperatorType set to ipCompatible (1), then as per RFC 6370 (MEG_ID for an LSP is LSP_ID, and MEG_ID for a PW is PW_Path_ID), MEP_ID can be automatically formed.
当创建一个新条目时，mplsOamIdMegOperatorType设置为ipCompatible（1），然后根据RFC 6370（LSP的MEG_ID为LSP_ID，PW的MEG_ID为PW_路径_ID），可以自动形成MEP_ID。
For a co-routed bidirectional LSP, MEG_ID is A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: Node_ID::Tunnel_Num}::LSP_Num.
对于共同路由的双向LSP，MEG_ID是A1-{Global_ID:：Node_ID:：Tunnel_Num}:：Z9-{Global_ID:：Node_ID:：Tunnel_Num}:：LSP_Num。
For an associated bidirectional LSP, MEG_ID is A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}.
对于关联的双向LSP，MEG_ID为A1-{Global_ID:：Node_ID:：Tunnel_Num:：LSP_Num}:：Z9-{Global_ID:：Node_ID:：Tunnel_Num:：LSP_Num}。
For an LSP, MEP_ID is formed using Global_ID::Node_ID::Tunnel_Num::LSP_Num.
对于LSP，MEP_ID是使用全局_ID:：节点_ID:：隧道_Num:：LSP_Num形成的。
For a PW, MEG_ID is formed using AGI:: A1-{Global_ID::Node_ID::AC_ID}:: Z9-{Global_ID::Node_ID::AC_ID}.
对于PW，MEG_ID是使用AGI:：A1-{Global_ID:：Node_ID:：AC_ID}:：Z9-{Global_ID:：Node_ID:：AC_ID}形成的。
For a PW, MEP_ID is formed using AGI::Global_ID::Node_ID::AC_ID.
对于PW，MEP_ID是使用AGI:：Global_ID:：Node_ID:：AC_ID形成的。
MEP_ID is retrieved from the mplsOamIdMegServicePointer object based on the mplsOamIdMegServicePointerType value. The ICC MEG_ID for an LSP and a PW is formed using the objects mplsOamIdMegIdIcc and mplsOamIdMegIdUmc.
MEP_ID是基于mplsOamIdMegServicePointerType值从mplsOamIdMegServicePointer对象检索的。LSP和PW的ICC MEG_ID使用对象mplsOamIdMegIdIcc和mplsOamIdMegIdUmc形成。
MEP_ID can be formed using MEG_ID::MEP_Index."
REFERENCE
"1. RFC 5860: Requirements for Operations, Administration,
and Maintenance (OAM) in MPLS Transport Networks,
May 2010.
2. RFC 6371: Operations, Administration, and Maintenance
Framework for MPLS-Based Transport Networks,
September 2011, Section 3.
3. RFC 6370: MPLS Transport Profile (MPLS-TP) Identifiers,
September 2011.
4. RFC 6923: MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions, May 2013."
INDEX { mplsOamIdMegIndex }
::= { mplsOamIdMegTable 1 }
MEP_ID can be formed using MEG_ID::MEP_Index."
REFERENCE
"1. RFC 5860: Requirements for Operations, Administration,
and Maintenance (OAM) in MPLS Transport Networks,
May 2010.
2. RFC 6371: Operations, Administration, and Maintenance
Framework for MPLS-Based Transport Networks,
September 2011, Section 3.
3. RFC 6370: MPLS Transport Profile (MPLS-TP) Identifiers,
September 2011.
4. RFC 6923: MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions, May 2013."
INDEX { mplsOamIdMegIndex }
::= { mplsOamIdMegTable 1 }
MplsOamIdMegEntry ::= SEQUENCE {
mplsOamIdMegIndex Unsigned32,
mplsOamIdMegName SnmpAdminString,
mplsOamIdMegOperatorType INTEGER,
mplsOamIdMegIdCc SnmpAdminString,
mplsOamIdMegIdIcc SnmpAdminString,
mplsOamIdMegIdUmc SnmpAdminString,
mplsOamIdMegServicePointerType INTEGER,
mplsOamIdMegMpLocation INTEGER,
mplsOamIdMegPathFlow INTEGER,
mplsOamIdMegOperStatus INTEGER,
mplsOamIdMegSubOperStatus BITS,
mplsOamIdMegRowStatus RowStatus,
mplsOamIdMegStorageType StorageType
}
MplsOamIdMegEntry ::= SEQUENCE {
mplsOamIdMegIndex Unsigned32,
mplsOamIdMegName SnmpAdminString,
mplsOamIdMegOperatorType INTEGER,
mplsOamIdMegIdCc SnmpAdminString,
mplsOamIdMegIdIcc SnmpAdminString,
mplsOamIdMegIdUmc SnmpAdminString,
mplsOamIdMegServicePointerType INTEGER,
mplsOamIdMegMpLocation INTEGER,
mplsOamIdMegPathFlow INTEGER,
mplsOamIdMegOperStatus INTEGER,
mplsOamIdMegSubOperStatus BITS,
mplsOamIdMegRowStatus RowStatus,
mplsOamIdMegStorageType StorageType
}
mplsOamIdMegIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index for the conceptual row identifying a MEG within
this MEG table. Managers should obtain new values for row
creation in this table by reading mplsOamIdMegIndexNext."
::= { mplsOamIdMegEntry 1 }
mplsOamIdMegIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Index for the conceptual row identifying a MEG within
this MEG table. Managers should obtain new values for row
creation in this table by reading mplsOamIdMegIndexNext."
::= { mplsOamIdMegEntry 1 }
mplsOamIdMegName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..48))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Each MEG has a unique name amongst all those used or
available to a service provider or operator. It
facilitates easy identification of administrative
responsibility for each MEG."
::= { mplsOamIdMegEntry 2 }
mplsOamIdMegName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..48))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Each MEG has a unique name amongst all those used or
available to a service provider or operator. It
facilitates easy identification of administrative
responsibility for each MEG."
::= { mplsOamIdMegEntry 2 }
mplsOamIdMegOperatorType OBJECT-TYPE
SYNTAX INTEGER {
ipCompatible (1),
iccBased (2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the operator type for the MEG. Conceptual rows
having 'iccBased' as the operator type MUST have valid
values for the objects mplsOamIdMegIdIcc and
mplsOamIdMegIdUmc when the row status is active."
REFERENCE
"1. RFC 6370: MPLS Transport Profile (MPLS-TP) Identifiers,
September 2011.
2. RFC 6923: MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions, May 2013, Section 3.1."
DEFVAL { ipCompatible }
::= { mplsOamIdMegEntry 3 }
mplsOamIdMegOperatorType OBJECT-TYPE
SYNTAX INTEGER {
ipCompatible (1),
iccBased (2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the operator type for the MEG. Conceptual rows
having 'iccBased' as the operator type MUST have valid
values for the objects mplsOamIdMegIdIcc and
mplsOamIdMegIdUmc when the row status is active."
REFERENCE
"1. RFC 6370: MPLS Transport Profile (MPLS-TP) Identifiers,
September 2011.
2. RFC 6923: MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions, May 2013, Section 3.1."
DEFVAL { ipCompatible }
::= { mplsOamIdMegEntry 3 }
mplsOamIdMegIdCc OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..2)) MAX-ACCESS read-create STATUS current DESCRIPTION "Global uniqueness is assured by concatenating the ICC with a Country Code (CC). The Country Code (alpha-2) is a string of two alphabetic characters represented with uppercase letters (i.e., A-Z).
mplsOamIdMegIdCc对象类型语法SnmpAdminString（大小（0..2））MAX-ACCESS read create STATUS current DESCRIPTION“通过将ICC与国家代码（CC）连接起来确保全局唯一性。国家代码（alpha-2）是由两个字母组成的字符串，用大写字母（即a-Z）表示。
This object MUST contain a non-null value if
the MplsOamIdMegOperatorType value is iccBased (2);
otherwise, a null value with octet size 0
should be assigned."
REFERENCE
"RFC 6923: MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions, May 2013, Section 3."
DEFVAL {""}
::= { mplsOamIdMegEntry 4 }
This object MUST contain a non-null value if
the MplsOamIdMegOperatorType value is iccBased (2);
otherwise, a null value with octet size 0
should be assigned."
REFERENCE
"RFC 6923: MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions, May 2013, Section 3."
DEFVAL {""}
::= { mplsOamIdMegEntry 4 }
mplsOamIdMegIdIcc OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(0..6)) MAX-ACCESS read-create STATUS current DESCRIPTION "Unique code assigned to a network operator or service provider; maintained by the ITU-T. This is the ITU Carrier Code used to form the MEGID.
MPLSOMIDEMGIDICC对象类型语法SnmpAdminString（大小（0..6））MAX-ACCESS read create STATUS current DESCRIPTION“分配给网络运营商或服务提供商的唯一代码；由ITU-T维护。这是用于形成MEGID的ITU载波代码。
This object MUST contain a non-null value if
the MplsOamIdMegOperatorType value is iccBased (2);
otherwise, a null value with octet size 0
should be assigned."
REFERENCE
"RFC 6923: MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions, May 2013, Section 3.1."
DEFVAL {""}
::= { mplsOamIdMegEntry 5 }
This object MUST contain a non-null value if
the MplsOamIdMegOperatorType value is iccBased (2);
otherwise, a null value with octet size 0
should be assigned."
REFERENCE
"RFC 6923: MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions, May 2013, Section 3.1."
DEFVAL {""}
::= { mplsOamIdMegEntry 5 }
mplsOamIdMegIdUmc OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..7))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Unique code assigned by a network operator or service
provider. This code is appended to mplsOamIdMegIdIcc to
form the MEGID.
This object MUST contain a non-null value if
the MplsOamIdMegOperatorType value is iccBased (2);
otherwise, a null value with octet size 0
should be assigned."
REFERENCE
"RFC 6923: MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions, May 2013, Section 7.1."
DEFVAL {""}
::= { mplsOamIdMegEntry 6 }
mplsOamIdMegIdUmc OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..7))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Unique code assigned by a network operator or service
provider. This code is appended to mplsOamIdMegIdIcc to
form the MEGID.
This object MUST contain a non-null value if
the MplsOamIdMegOperatorType value is iccBased (2);
otherwise, a null value with octet size 0
should be assigned."
REFERENCE
"RFC 6923: MPLS Transport Profile (MPLS-TP) Identifiers
Following ITU-T Conventions, May 2013, Section 7.1."
DEFVAL {""}
::= { mplsOamIdMegEntry 6 }
mplsOamIdMegServicePointerType OBJECT-TYPE
SYNTAX INTEGER {
tunnel (1),
lsp (2),
pseudowire (3),
section (4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the service type for the MEG.
If the service type indicates tunnel (1), the service
pointer in the mplsOamIdMeTable points to an entry in
the point-to-point mplsTunnelTable (RFC 3812).
mplsOamIdMegServicePointerType OBJECT-TYPE
SYNTAX INTEGER {
tunnel (1),
lsp (2),
pseudowire (3),
section (4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the service type for the MEG.
If the service type indicates tunnel (1), the service
pointer in the mplsOamIdMeTable points to an entry in
the point-to-point mplsTunnelTable (RFC 3812).
If the service type indicates lsp (2), the service pointer in the mplsOamIdMeTable points to an entry in the co-routed or associated bidirectional mplsTunnelTable.
如果服务类型指示lsp（2），则MPLSOAMIDETABLE中的服务指针将指向共同路由或关联的双向mplsTunnelTable中的条目。
If the value is the pseudowire (3) service type, the service pointer in the mplsOamIdMeTable points to an entry in the pwTable (RFC 5601).
如果该值是伪线（3）服务类型，则MPLSOAMIDETABLE中的服务指针将指向pwTable（RFC 5601）中的一个条目。
If the value is the section (4) service type, the service
pointer in the mplsOamIdMeTable points to an entry in
the mplsTunnelTable (RFC 3812)."
REFERENCE
"1. RFC 3812: Multiprotocol Label Switching (MPLS)
Traffic Engineering (TE) Management Information
Base (MIB), June 2004.
2. RFC 5601: Pseudowire (PW) Management Information
Base (MIB), July 2009."
DEFVAL { lsp }
::= { mplsOamIdMegEntry 7 }
If the value is the section (4) service type, the service
pointer in the mplsOamIdMeTable points to an entry in
the mplsTunnelTable (RFC 3812)."
REFERENCE
"1. RFC 3812: Multiprotocol Label Switching (MPLS)
Traffic Engineering (TE) Management Information
Base (MIB), June 2004.
2. RFC 5601: Pseudowire (PW) Management Information
Base (MIB), July 2009."
DEFVAL { lsp }
::= { mplsOamIdMegEntry 7 }
mplsOamIdMegMpLocation OBJECT-TYPE
SYNTAX INTEGER {
perNode (1),
perInterface (2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the MP location type for this MEG.
mplsOamIdMegMpLocation OBJECT-TYPE
SYNTAX INTEGER {
perNode (1),
perInterface (2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the MP location type for this MEG.
If the value is perNode, then the MEG in the LSR supports only perNode MEPs/MIPs, i.e., only one MEP/MIP in an LSR.
如果该值为每节点，则LSR中的MEG仅支持每节点MEP/MIP，即LSR中仅支持一个MEP/MIP。
If the value is perInterface, then the MEG in the LSR
supports perInterface MEPs/MIPs, i.e., two MEPs/MIPs in
an LSR."
REFERENCE
"RFC 6371: Operations, Administration, and Maintenance
Framework for MPLS-Based Transport Networks,
September 2011."
DEFVAL { perNode }
::= { mplsOamIdMegEntry 8 }
If the value is perInterface, then the MEG in the LSR
supports perInterface MEPs/MIPs, i.e., two MEPs/MIPs in
an LSR."
REFERENCE
"RFC 6371: Operations, Administration, and Maintenance
Framework for MPLS-Based Transport Networks,
September 2011."
DEFVAL { perNode }
::= { mplsOamIdMegEntry 8 }
mplsOamIdMegPathFlow OBJECT-TYPE
SYNTAX INTEGER {
unidirectionalPointToPoint (1),
coRoutedBidirectionalPointToPoint (2),
associatedBidirectionalPointToPoint (3),
unidirectionalPointToMultiPoint (4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the transport path flow for this MEG.
In the case of a unidirectional point-to-point transport
path, a single unidirectional ME is defined to monitor it.
In the case of associated bidirectional point-to-point
transport paths, two independent unidirectional MEs are
defined to independently monitor each direction.
In the case of co-routed bidirectional point-to-point
transport paths, a single bidirectional ME is defined to
monitor both directions congruently.
In the case of unidirectional point-to-multipoint transport
paths, a single unidirectional ME for each leaf is defined
to monitor the transport path from the root to that leaf."
mplsOamIdMegPathFlow OBJECT-TYPE
SYNTAX INTEGER {
unidirectionalPointToPoint (1),
coRoutedBidirectionalPointToPoint (2),
associatedBidirectionalPointToPoint (3),
unidirectionalPointToMultiPoint (4)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the transport path flow for this MEG.
In the case of a unidirectional point-to-point transport
path, a single unidirectional ME is defined to monitor it.
In the case of associated bidirectional point-to-point
transport paths, two independent unidirectional MEs are
defined to independently monitor each direction.
In the case of co-routed bidirectional point-to-point
transport paths, a single bidirectional ME is defined to
monitor both directions congruently.
In the case of unidirectional point-to-multipoint transport
paths, a single unidirectional ME for each leaf is defined
to monitor the transport path from the root to that leaf."
REFERENCE
"RFC 6371: Operations, Administration, and Maintenance
Framework for MPLS-Based Transport Networks,
September 2011."
DEFVAL { coRoutedBidirectionalPointToPoint }
::= { mplsOamIdMegEntry 9 }
REFERENCE
"RFC 6371: Operations, Administration, and Maintenance
Framework for MPLS-Based Transport Networks,
September 2011."
DEFVAL { coRoutedBidirectionalPointToPoint }
::= { mplsOamIdMegEntry 9 }
mplsOamIdMegOperStatus OBJECT-TYPE
SYNTAX INTEGER {
up (1),
down (2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the operational status of the
Maintenance Entity Group (MEG). This object is used to
send the notification to the SNMP manager about the MEG.
mplsOamIdMegOperStatus OBJECT-TYPE
SYNTAX INTEGER {
up (1),
down (2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the operational status of the
Maintenance Entity Group (MEG). This object is used to
send the notification to the SNMP manager about the MEG.
The value up (1) indicates that the MEG and its monitored path are operationally up. The value down (2) indicates that the MEG is operationally down.
值up（1）表示MEG及其监控路径在操作上处于up状态。值down（2）表示MEG运行下降。
When the value of mplsOamIdMegOperStatus is up (1),
all the bits of mplsOamIdMegSubOperStatus must be cleared.
When the value of mplsOamIdMegOperStatus is down (2),
at least one bit of mplsOamIdMegSubOperStatus must be set."
::= { mplsOamIdMegEntry 10 }
When the value of mplsOamIdMegOperStatus is up (1),
all the bits of mplsOamIdMegSubOperStatus must be cleared.
When the value of mplsOamIdMegOperStatus is down (2),
at least one bit of mplsOamIdMegSubOperStatus must be set."
::= { mplsOamIdMegEntry 10 }
mplsOamIdMegSubOperStatus OBJECT-TYPE
SYNTAX BITS {
megDown (0),
meDown (1),
oamAppDown (2),
pathDown (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the reason why the MEG operational
status, as indicated by the object mplsOamIdMegOperStatus,
is down. This object is used to send the notification to
the SNMP manager about the MEG.
mplsOamIdMegSubOperStatus OBJECT-TYPE
SYNTAX BITS {
megDown (0),
meDown (1),
oamAppDown (2),
pathDown (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object specifies the reason why the MEG operational
status, as indicated by the object mplsOamIdMegOperStatus,
is down. This object is used to send the notification to
the SNMP manager about the MEG.
The bit 0 (megDown) indicates that the MEG is down. The bit 1 (meDown) indicates that the ME table is down. The bit 2 (oamAppDown) indicates that the OAM application (LSP or PW) monitored by this MEG is down. Currently, BFD
位0（兆欧下降）表示兆欧下降。位1（meDown）表示ME表已关闭。位2（oamAppDown）表示此MEG监控的OAM应用程序（LSP或PW）已关闭。目前，BFD
is the only supported OAM application.
The bit 3 (pathDown) indicates that the underlying
LSP or PW is down."
::= { mplsOamIdMegEntry 11 }
is the only supported OAM application.
The bit 3 (pathDown) indicates that the underlying
LSP or PW is down."
::= { mplsOamIdMegEntry 11 }
mplsOamIdMegRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or delete
a row in this table. When a row in this table is in the
active(1) state, no objects in that row can be modified
by the agent except mplsOamIdMegRowStatus."
::= { mplsOamIdMegEntry 12 }
mplsOamIdMegRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or delete
a row in this table. When a row in this table is in the
active(1) state, no objects in that row can be modified
by the agent except mplsOamIdMegRowStatus."
::= { mplsOamIdMegEntry 12 }
mplsOamIdMegStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object.
Conceptual rows having the value 'permanent'
need not allow write access to any columnar
objects in the row."
DEFVAL { volatile }
::= { mplsOamIdMegEntry 13 }
mplsOamIdMegStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this
object.
Conceptual rows having the value 'permanent'
need not allow write access to any columnar
objects in the row."
DEFVAL { volatile }
::= { mplsOamIdMegEntry 13 }
-- End of MPLS Transport Profile MEG table
--MPLS传输配置文件MEG表结束
-- Start of MPLS Transport Profile ME table
--开始MPLS传输配置文件ME表
mplsOamIdMeIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..4294967295)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
mplsOamIdMeIndex, or a zero to indicate
that none exist. Negative values are not allowed,
as they do not correspond to valid values of
mplsOamIdMeIndex."
::= { mplsOamIdObjects 3 }
mplsOamIdMeIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..4294967295)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
mplsOamIdMeIndex, or a zero to indicate
that none exist. Negative values are not allowed,
as they do not correspond to valid values of
mplsOamIdMeIndex."
::= { mplsOamIdObjects 3 }
mplsOamIdMeMpIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..4294967295)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
mplsOamIdMeMpIndex, or a zero to indicate
that none exist. Negative values are not allowed,
as they do not correspond to valid values of
mplsOamIdMeMpIndex."
::= { mplsOamIdObjects 4 }
mplsOamIdMeMpIndexNext OBJECT-TYPE
SYNTAX IndexIntegerNextFree (0..4294967295)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains an unused value for
mplsOamIdMeMpIndex, or a zero to indicate
that none exist. Negative values are not allowed,
as they do not correspond to valid values of
mplsOamIdMeMpIndex."
::= { mplsOamIdObjects 4 }
mplsOamIdMeTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsOamIdMeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains MPLS-TP ME information.
mplsOamIdMeTable对象类型MplsOamIdMeEntry MAX-ACCESS的语法序列不可访问状态当前描述“此表包含MPLS-TP ME信息。
The ME is some portion of a transport path that requires management bounded by two points (called MEPs), and the relationship between those points to which maintenance and monitoring operations apply.
ME是传输路径的一部分，需要由两个点（称为MEP）以及维护和监控操作适用的点之间的关系进行管理。
This table is generic enough to handle MEP and MIP
information within a MEG."
::= { mplsOamIdObjects 5 }
This table is generic enough to handle MEP and MIP
information within a MEG."
::= { mplsOamIdObjects 5 }
mplsOamIdMeEntry OBJECT-TYPE SYNTAX MplsOamIdMeEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents an MPLS-TP ME. This entry represents the ME if the source and sink MEPs are defined.
mplsOamIdMeEntry对象类型语法mplsOamIdMeEntry MAX-ACCESS不可访问状态当前描述“此表中的一个条目表示MPLS-TP ME。如果定义了源和汇MEP，则此条目表示ME。
An ME is a point-to-point entity. One ME has two such MEPs. A MEG is a group of one or more MEs. One MEG can have two or more MEPs.
ME是一个点对点实体。一个ME有两个这样的MEP。MEG是由一个或多个MEs组成的组。一个MEG可以有两个或多个MEP。
For a point-to-point LSP, one MEG has one ME, and this ME is associated with two MEPs (source and sink MEPs) within a MEG. Each mplsOamIdMeIndex value denotes the ME within a MEG.
对于点对点LSP，一个MEG有一个ME，该ME与一个MEG内的两个MEP（源和汇MEP）关联。每个mplsOamIdMeIndex值表示MEG中的ME。
In the case of unidirectional point-to-point transport paths, a single unidirectional ME is defined to monitor it, and mplsOamIdMeServicePointer points to a unidirectional point-to-point path.
在单向点到点传输路径的情况下，定义单个单向ME来监视它，并且mplsOamIdMeServicePointer指向单向点到点路径。
In the case of associated bidirectional point-to-point transport paths, two independent unidirectional MEs are defined to independently monitor each direction, and each mplsOamIdMeServicePointer MIB object points to a unique unidirectional transport path. This has implications for transactions that terminate at or query a MIP, as a return path from a MIP to a source MEP does not necessarily exist within the MEG.
在相关联的双向点到点传输路径的情况下，定义两个独立的单向MEs以独立地监视每个方向，并且每个mplsOamIdMeServicePointer MIB对象指向唯一的单向传输路径。这对终止于或查询MIP的事务有影响，因为从MIP到源MEP的返回路径不一定存在于MEG中。
In the case of co-routed bidirectional point-to-point transport paths, a single bidirectional ME is defined to monitor both directions congruently, and the mplsOamIdMeServicePointer MIB object points to a co-routed bidirectional point-to-point transport path.
在共路由双向点到点传输路径的情况下，定义单个双向ME以一致地监视两个方向，并且mplsOamIdMeServicePointer MIB对象指向共路由双向点到点传输路径。
In the case of unidirectional point-to-multipoint transport
paths, a single unidirectional ME for each leaf is defined
to monitor the transport path from the root to that leaf,
and each leaf has different transport path information in
the mplsOamIdMeServicePointer MIB object. Note that the
MplsOamIdMeEntry should be created manually once the MEG
is configured for OAM operations."
INDEX { mplsOamIdMegIndex,
mplsOamIdMeIndex,
mplsOamIdMeMpIndex
}
::= { mplsOamIdMeTable 1 }
In the case of unidirectional point-to-multipoint transport
paths, a single unidirectional ME for each leaf is defined
to monitor the transport path from the root to that leaf,
and each leaf has different transport path information in
the mplsOamIdMeServicePointer MIB object. Note that the
MplsOamIdMeEntry should be created manually once the MEG
is configured for OAM operations."
INDEX { mplsOamIdMegIndex,
mplsOamIdMeIndex,
mplsOamIdMeMpIndex
}
::= { mplsOamIdMeTable 1 }
MplsOamIdMeEntry ::= SEQUENCE {
mplsOamIdMeIndex Unsigned32,
mplsOamIdMeMpIndex Unsigned32,
mplsOamIdMeName SnmpAdminString,
mplsOamIdMeMpIfIndex InterfaceIndexOrZero,
mplsOamIdMeSourceMepIndex Unsigned32,
mplsOamIdMeSinkMepIndex Unsigned32,
mplsOamIdMeMpType INTEGER,
mplsOamIdMeMepDirection INTEGER,
mplsOamIdMeServicePointer RowPointer,
mplsOamIdMeRowStatus RowStatus,
mplsOamIdMeStorageType StorageType
}
MplsOamIdMeEntry ::= SEQUENCE {
mplsOamIdMeIndex Unsigned32,
mplsOamIdMeMpIndex Unsigned32,
mplsOamIdMeName SnmpAdminString,
mplsOamIdMeMpIfIndex InterfaceIndexOrZero,
mplsOamIdMeSourceMepIndex Unsigned32,
mplsOamIdMeSinkMepIndex Unsigned32,
mplsOamIdMeMpType INTEGER,
mplsOamIdMeMepDirection INTEGER,
mplsOamIdMeServicePointer RowPointer,
mplsOamIdMeRowStatus RowStatus,
mplsOamIdMeStorageType StorageType
}
mplsOamIdMeIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Uniquely identifies an ME index within a MEG. Managers
should obtain new values for row creation in this table by
reading mplsOamIdMeIndexNext."
::= { mplsOamIdMeEntry 1 }
mplsOamIdMeIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Uniquely identifies an ME index within a MEG. Managers
should obtain new values for row creation in this table by
reading mplsOamIdMeIndexNext."
::= { mplsOamIdMeEntry 1 }
mplsOamIdMeMpIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Indicates the Maintenance Point (MP) index that is used to
create multiple MEPs in a node of a single ME. The value
of this object can be the MEP index or the MIP index.
Managers should obtain new values for row creation in this
table by reading mplsOamIdMeMpIndexNext."
::= { mplsOamIdMeEntry 2 }
mplsOamIdMeMpIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Indicates the Maintenance Point (MP) index that is used to
create multiple MEPs in a node of a single ME. The value
of this object can be the MEP index or the MIP index.
Managers should obtain new values for row creation in this
table by reading mplsOamIdMeMpIndexNext."
::= { mplsOamIdMeEntry 2 }
mplsOamIdMeName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(1..48))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object denotes the ME name. Each ME has a unique
name within a MEG."
::= { mplsOamIdMeEntry 3 }
mplsOamIdMeName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(1..48))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object denotes the ME name. Each ME has a unique
name within a MEG."
::= { mplsOamIdMeEntry 3 }
mplsOamIdMeMpIfIndex OBJECT-TYPE SYNTAX InterfaceIndexOrZero MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates the MP interface. If the mplsOamIdMegMpLocation object value is perNode (1), the MP interface index should point to the incoming interface or outgoing interface, or be zero (to indicate that the MP OAM packets are initiated from the forwarding engine).
MPLSOAMIDEMPIFINDEX对象类型语法接口IndexorZero MAX-ACCESS read create STATUS current DESCRIPTION”表示MP接口。如果MPLSOAMIDMEMPLOCATION对象值为perNode（1），则MP接口索引应指向传入接口或传出接口，或为零（指示MP OAM数据包是从转发引擎启动的）。
If the mplsOamIdMegMpLocation object value is perInterface (2), the MP interface index should point to the incoming interface or outgoing interface."
如果mplsoamidmemplocation对象值为perInterface（2），则MP接口索引应指向传入接口或传出接口。“
REFERENCE
"1. RFC 6371: Operations, Administration, and Maintenance
Framework for MPLS-Based Transport Networks,
September 2011.
2. RFC 2863: The Interfaces Group MIB, June 2000."
DEFVAL { 0 }
::= { mplsOamIdMeEntry 4 }
REFERENCE
"1. RFC 6371: Operations, Administration, and Maintenance
Framework for MPLS-Based Transport Networks,
September 2011.
2. RFC 2863: The Interfaces Group MIB, June 2000."
DEFVAL { 0 }
::= { mplsOamIdMeEntry 4 }
mplsOamIdMeSourceMepIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the source MEP index of the ME. This object
should be configured if the mplsOamIdMegOperatorType object
in the mplsOamIdMegEntry is configured as iccBased (2).
If the MEG is configured for an IP-based operator,
the value of this object should be set to zero, and the
MEP ID will be automatically derived from the service
identifiers (MPLS-TP LSP/PW Identifier)."
DEFVAL { 0 }
::= { mplsOamIdMeEntry 5 }
mplsOamIdMeSourceMepIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the source MEP index of the ME. This object
should be configured if the mplsOamIdMegOperatorType object
in the mplsOamIdMegEntry is configured as iccBased (2).
If the MEG is configured for an IP-based operator,
the value of this object should be set to zero, and the
MEP ID will be automatically derived from the service
identifiers (MPLS-TP LSP/PW Identifier)."
DEFVAL { 0 }
::= { mplsOamIdMeEntry 5 }
mplsOamIdMeSinkMepIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the sink MEP index of the ME. This object
should be configured if the mplsOamIdMegOperatorType object
in the mplsOamIdMegEntry is configured as iccBased (2).
If the MEG is configured for an IP-based operator,
the value of this object should be set to zero, and the
MEP ID will be automatically derived from the service
identifiers (MPLS-TP LSP/PW Identifier)."
DEFVAL { 0 }
::= { mplsOamIdMeEntry 6 }
mplsOamIdMeSinkMepIndex OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the sink MEP index of the ME. This object
should be configured if the mplsOamIdMegOperatorType object
in the mplsOamIdMegEntry is configured as iccBased (2).
If the MEG is configured for an IP-based operator,
the value of this object should be set to zero, and the
MEP ID will be automatically derived from the service
identifiers (MPLS-TP LSP/PW Identifier)."
DEFVAL { 0 }
::= { mplsOamIdMeEntry 6 }
mplsOamIdMeMpType OBJECT-TYPE
SYNTAX INTEGER {
mep (1),
mip (2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the MP type within the MEG.
mplsOamIdMeMpType OBJECT-TYPE
SYNTAX INTEGER {
mep (1),
mip (2)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the MP type within the MEG.
The object should have the value mep (1) only in the ingress or egress nodes of the transport path.
对象应仅在传输路径的入口或出口节点中具有值mep（1）。
The object can have the value mip (2) in the
intermediate nodes and possibly in the egress nodes
of the transport path."
DEFVAL { mep }
::= { mplsOamIdMeEntry 7 }
The object can have the value mip (2) in the
intermediate nodes and possibly in the egress nodes
of the transport path."
DEFVAL { mep }
::= { mplsOamIdMeEntry 7 }
mplsOamIdMeMepDirection OBJECT-TYPE
SYNTAX INTEGER {
up (1),
down (2),
notApplicable (3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the direction of the MEP. This object
should be configured if mplsOamIdMeMpType is configured
as mep (1); otherwise, notApplicable (3) is set."
DEFVAL { down }
::= { mplsOamIdMeEntry 8 }
mplsOamIdMeMepDirection OBJECT-TYPE
SYNTAX INTEGER {
up (1),
down (2),
notApplicable (3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Indicates the direction of the MEP. This object
should be configured if mplsOamIdMeMpType is configured
as mep (1); otherwise, notApplicable (3) is set."
DEFVAL { down }
::= { mplsOamIdMeEntry 8 }
mplsOamIdMeServicePointer OBJECT-TYPE SYNTAX RowPointer MAX-ACCESS read-create STATUS current DESCRIPTION "This variable represents a pointer to the MPLS-TP transport path. This value MUST point at an entry in the mplsTunnelEntry if mplsOamIdMegServicePointerType is configured as tunnel (1), lsp (2), or section (4), or at an entry in the pwEntry if mplsOamIdMegServicePointerType is configured as pseudowire (3).
MPLSOMIDEMERVICEPOINTER对象类型语法RowPointer MAX-ACCESS read create STATUS current DESCRIPTION“此变量表示指向MPLS-TP传输路径的指针。如果MPLSOMIDEMERVICEPOINTERTYPE配置为隧道（1）、lsp（2）或节（4），则此值必须指向mplsTunnelEntry中的条目，或者如果MPLSOMEGServicePointerType配置为伪线（3），则位于pwEntry中的条目。
Note: This service pointer object is placed in the ME table
instead of the MEG table, since it will be useful in the
point-to-multipoint case, where each ME will point to
different branches of a point-to-multipoint tree."
::= { mplsOamIdMeEntry 9 }
Note: This service pointer object is placed in the ME table
instead of the MEG table, since it will be useful in the
point-to-multipoint case, where each ME will point to
different branches of a point-to-multipoint tree."
::= { mplsOamIdMeEntry 9 }
mplsOamIdMeRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or delete
a row in this table. When a row in this table is in the
active(1) state, no objects in that row can be modified
by the agent except mplsOamIdMeRowStatus."
::= { mplsOamIdMeEntry 10 }
mplsOamIdMeRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or delete
a row in this table. When a row in this table is in the
active(1) state, no objects in that row can be modified
by the agent except mplsOamIdMeRowStatus."
::= { mplsOamIdMeEntry 10 }
mplsOamIdMeStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this object.
Conceptual rows having the value 'permanent'
need not allow write access to any columnar
objects in the row."
DEFVAL { volatile }
::= { mplsOamIdMeEntry 11 }
mplsOamIdMeStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable indicates the storage type for this object.
Conceptual rows having the value 'permanent'
need not allow write access to any columnar
objects in the row."
DEFVAL { volatile }
::= { mplsOamIdMeEntry 11 }
-- End of MPLS Transport Profile ME table
--MPLS传输配置文件ME表的末尾
-- End of MPLS-TP OAM tables
--MPLS-TP OAM表结束
-- Notification definitions of MPLS-TP identifiers
--MPLS-TP标识符的通知定义
mplsOamIdDefectCondition NOTIFICATION-TYPE
OBJECTS {
mplsOamIdMegName,
mplsOamIdMeName,
mplsOamIdMegOperStatus,
mplsOamIdMegSubOperStatus
}
STATUS current
DESCRIPTION
"This notification is sent whenever the operational
status of the MEG is changed."
::= { mplsOamIdNotifications 1 }
mplsOamIdDefectCondition NOTIFICATION-TYPE
OBJECTS {
mplsOamIdMegName,
mplsOamIdMeName,
mplsOamIdMegOperStatus,
mplsOamIdMegSubOperStatus
}
STATUS current
DESCRIPTION
"This notification is sent whenever the operational
status of the MEG is changed."
::= { mplsOamIdNotifications 1 }
-- End of notifications
--通知结束
-- Module compliance
--模块符合性
mplsOamIdCompliances
OBJECT IDENTIFIER ::= { mplsOamIdConformance 1 }
mplsOamIdCompliances
OBJECT IDENTIFIER ::= { mplsOamIdConformance 1 }
mplsOamIdGroups
OBJECT IDENTIFIER ::= { mplsOamIdConformance 2 }
mplsOamIdGroups
OBJECT IDENTIFIER ::= { mplsOamIdConformance 2 }
-- Compliance requirement for fully compliant implementations
--完全合规实施的合规性要求
mplsOamIdModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that provide full support for the MPLS-TP-OAM-STD-MIB. Such devices can then be monitored and also be configured using this MIB module."
MPLSOAMIDModulelCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION“为MPLS-TP-OAM-STD-MIB提供完全支持的代理的符合性声明。然后可以使用此MIB模块监控和配置此类设备。”
MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863
MANDATORY-GROUPS {
ifGeneralInformationGroup,
ifCounterDiscontinuityGroup
}
MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863
MANDATORY-GROUPS {
ifGeneralInformationGroup,
ifCounterDiscontinuityGroup
}
MODULE -- this module
MANDATORY-GROUPS {
mplsOamIdMegGroup,
mplsOamIdMeGroup
}
MODULE -- this module
MANDATORY-GROUPS {
mplsOamIdMegGroup,
mplsOamIdMeGroup
}
GROUP mplsOamIdNotificationObjectsGroup DESCRIPTION "This group is only mandatory for those implementations that can efficiently implement the notifications contained in this group."
GROUP mplsOamIdNotificationObjectsGroup DESCRIPTION“此组仅对于能够有效实现此组中包含的通知的实现是必需的。”
GROUP mplsOamIdNotificationGroup DESCRIPTION "This group is only mandatory for those implementations that can efficiently implement the notifications contained in this group."
GROUP mplsOamIdNotificationGroup DESCRIPTION“此组仅对于能够有效实现此组中包含的通知的实现是必需的。”
::= { mplsOamIdCompliances 1 }
::= { mplsOamIdCompliances 1 }
-- Compliance requirement for read-only implementations
--只读实现的法规遵从性要求
mplsOamIdModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that only provide read-only support for the MPLS-TP-OAM-STD-MIB module."
MPLSOAMIDModuleRadonlyCompliance MODULE-COMPLIANCE状态当前描述“仅为MPLS-TP-OAM-STD-MIB模块提供只读支持的代理的符合性声明。”
MODULE -- this module
模块——这个模块
MANDATORY-GROUPS {
mplsOamIdMegGroup,
mplsOamIdMeGroup
}
MANDATORY-GROUPS {
mplsOamIdMegGroup,
mplsOamIdMeGroup
}
GROUP mplsOamIdNotificationObjectsGroup DESCRIPTION "This group is only mandatory for those implementations that can efficiently implement the notifications contained in this group."
GROUP mplsOamIdNotificationObjectsGroup DESCRIPTION“此组仅对于能够有效实现此组中包含的通知的实现是必需的。”
GROUP mplsOamIdNotificationGroup DESCRIPTION "This group is only mandatory for those implementations that can efficiently implement the notifications contained in this group."
GROUP mplsOamIdNotificationGroup DESCRIPTION“此组仅对于能够有效实现此组中包含的通知的实现是必需的。”
-- mplsOamIdMegTable
--MPLSOA表
OBJECT mplsOamIdMegName MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOMEGNAME最小访问只读描述“不需要写访问。”
OBJECT mplsOamIdMegOperatorType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOAMIDEMAGOperatorType MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsOamIdMegIdCc MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsOamIdMegIdCc MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsOamIdMegIdIcc MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOAMIDEMGIDICC MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsOamIdMegIdUmc MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsOamIdMegIdUmc最小访问只读描述“不需要写访问。”
OBJECT mplsOamIdMegServicePointerType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOMEMAGServicePointerType MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsOamIdMegMpLocation MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOMIDEMMPLOCATION MIN-ACCESS只读描述“不需要写访问。”
OBJECT mplsOamIdMegPathFlow MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOMAGEMPATHFLOW最小访问只读描述“不需要写访问。”
OBJECT mplsOamIdMegRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOAMIDEMGROWSTATUS语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsOamIdMegStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOADMEGStorageType最小访问只读描述“不需要写访问。”
-- mplsOamIdMeTable
--MPLSOAMIDETABLE
OBJECT mplsOamIdMeName MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOAMIDEMENAME最小访问只读描述“不需要写访问。”
OBJECT mplsOamIdMeMpIfIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOAMIDEMPIFINDEX最小访问只读描述“不需要写访问。”
OBJECT mplsOamIdMeSourceMepIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOAMIDMESourceMapIndex最小访问只读说明“不需要写访问。”
OBJECT mplsOamIdMeSinkMepIndex MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOAMIDESINKMEPINDEX最小访问只读说明“不需要写访问。”
OBJECT mplsOamIdMeMpType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOAMIDEMPTYPE MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsOamIdMeMepDirection MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象MPLSOAMIDEMEPDirection最小访问只读描述“不需要写访问。”
OBJECT mplsOamIdMeServicePointer MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsOamIdMeServicePointer最小访问只读描述“不需要写访问。”
OBJECT mplsOamIdMeRowStatus SYNTAX RowStatus { active(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsoamiderowstatus语法RowStatus{active（1）}MIN-ACCESS只读说明“不需要写访问。”
OBJECT mplsOamIdMeStorageType MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象mplsOamIdMeStorageType最小访问只读描述“不需要写访问。”
::= { mplsOamIdCompliances 2 }
::= { mplsOamIdCompliances 2 }
-- Units of conformance
--一致性单位
mplsOamIdMegGroup OBJECT-GROUP
OBJECTS {
mplsOamIdMegIndexNext,
mplsOamIdMegName,
mplsOamIdMegOperatorType,
mplsOamIdMegIdCc,
mplsOamIdMegIdIcc,
mplsOamIdMegIdUmc,
mplsOamIdMegServicePointerType,
mplsOamIdMegMpLocation,
mplsOamIdMegOperStatus,
mplsOamIdMegSubOperStatus,
mplsOamIdMegPathFlow,
mplsOamIdMegRowStatus,
mplsOamIdMegStorageType
}
mplsOamIdMegGroup OBJECT-GROUP
OBJECTS {
mplsOamIdMegIndexNext,
mplsOamIdMegName,
mplsOamIdMegOperatorType,
mplsOamIdMegIdCc,
mplsOamIdMegIdIcc,
mplsOamIdMegIdUmc,
mplsOamIdMegServicePointerType,
mplsOamIdMegMpLocation,
mplsOamIdMegOperStatus,
mplsOamIdMegSubOperStatus,
mplsOamIdMegPathFlow,
mplsOamIdMegRowStatus,
mplsOamIdMegStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for MPLS MEG information."
::= { mplsOamIdGroups 1 }
STATUS current
DESCRIPTION
"Collection of objects needed for MPLS MEG information."
::= { mplsOamIdGroups 1 }
mplsOamIdMeGroup OBJECT-GROUP
OBJECTS {
mplsOamIdMeIndexNext,
mplsOamIdMeMpIndexNext,
mplsOamIdMeName,
mplsOamIdMeMpIfIndex,
mplsOamIdMeSourceMepIndex,
mplsOamIdMeSinkMepIndex,
mplsOamIdMeMpType,
mplsOamIdMeMepDirection,
mplsOamIdMeServicePointer,
mplsOamIdMeRowStatus,
mplsOamIdMeStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for MPLS ME information."
::= { mplsOamIdGroups 2 }
mplsOamIdMeGroup OBJECT-GROUP
OBJECTS {
mplsOamIdMeIndexNext,
mplsOamIdMeMpIndexNext,
mplsOamIdMeName,
mplsOamIdMeMpIfIndex,
mplsOamIdMeSourceMepIndex,
mplsOamIdMeSinkMepIndex,
mplsOamIdMeMpType,
mplsOamIdMeMepDirection,
mplsOamIdMeServicePointer,
mplsOamIdMeRowStatus,
mplsOamIdMeStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for MPLS ME information."
::= { mplsOamIdGroups 2 }
mplsOamIdNotificationObjectsGroup OBJECT-GROUP
OBJECTS {
mplsOamIdMegOperStatus,
mplsOamIdMegSubOperStatus
}
STATUS current
DESCRIPTION
"Collection of objects needed to implement notifications."
::= { mplsOamIdGroups 3 }
mplsOamIdNotificationObjectsGroup OBJECT-GROUP
OBJECTS {
mplsOamIdMegOperStatus,
mplsOamIdMegSubOperStatus
}
STATUS current
DESCRIPTION
"Collection of objects needed to implement notifications."
::= { mplsOamIdGroups 3 }
mplsOamIdNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
mplsOamIdDefectCondition
}
STATUS current
DESCRIPTION
"Set of notifications implemented in this module."
::= { mplsOamIdGroups 4 }
mplsOamIdNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS {
mplsOamIdDefectCondition
}
STATUS current
DESCRIPTION
"Set of notifications implemented in this module."
::= { mplsOamIdGroups 4 }
END
终止
This MIB relates to a system that will provide network connectivity and packet forwarding services. As such, improper manipulation of the objects represented by this MIB may result in denial of service to a large number of end-users.
此MIB涉及将提供网络连接和数据包转发服务的系统。因此，对该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 opens devices to attack.
此MIB模块中定义了许多管理对象，其MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作会使设备受到攻击。
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通过网络发送这些对象时，控制甚至获取和/或通知对这些对象的访问，甚至可能加密这些对象的值，这一点非常重要。以下是表和对象及其敏感度/漏洞：
- The mplsOamIdMegTable and the mplsOamIdMeTable collectively show the MPLS OAM characteristics. If an administrator does not want to reveal this information, then these tables should be considered sensitive/vulnerable.
- mplsOamIdMeTable和mplsOamIdMeTable共同显示MPLS OAM特性。如果管理员不想透露此信息，则应将这些表视为敏感/易受攻击。
SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), 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模块中的对象。
Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353].
Implementations SHOULD provide the security features described by the
SNMPv3 framework (see [RFC3410]), and implementations claiming
compliance to the SNMPv3 standard MUST include full support for
authentication and privacy via the User-based Security Model (USM)
[RFC3414] with the AES cipher algorithm [RFC3826]. Implementations
MAY also provide support for the Transport Security Model (TSM)
[RFC5591] in combination with a secure transport such as SSH
[RFC5592] or TLS/DTLS [RFC6353].
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实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
As described in [RFC4221] and [RFC6639], and as requested in the MPLS-TC-STD-MIB [RFC3811], MPLS-related Standards Track MIB modules should be rooted under the mplsStdMIB subtree. The following subsection lists a new assignment that has been made by IANA under the mplsStdMIB subtree for the MPLS-OAM-ID-STD-MIB module defined in this document. New assignments can only be made via a Standards Action as specified in [RFC5226].
如[RFC4221]和[RFC6639]所述，以及MPLS-TC-STD-MIB[RFC3811]中的要求，MPLS相关标准跟踪MIB模块应在mplsStdMIB子树下扎根。以下小节列出了IANA在本文档中定义的MPLS-OAM-ID-STD-MIB模块的mplsStdMIB子树下进行的新分配。新分配只能通过[RFC5226]中规定的标准操作进行。
IANA has to assign the OID { mplsStdMIB 21 } to the MPLS-OAM-ID-STD-MIB module specified in this document.
IANA必须将OID{mplsStdMIB 21}分配给本文档中指定的MPLS-OAM-ID-STD-MIB模块。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<http://www.rfc-editor.org/info/rfc2119>.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/RFC2578, April 1999, <http://www.rfc-editor.org/info/rfc2578>.
[RFC2578]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“管理信息的结构版本2（SMIv2）”，STD 58，RFC 2578，DOI 10.17487/RFC2578，1999年4月<http://www.rfc-editor.org/info/rfc2578>.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, <http://www.rfc-editor.org/info/rfc2579>.
[RFC2579]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的文本约定”，STD 58，RFC 2579，DOI 10.17487/RFC2579，1999年4月<http://www.rfc-editor.org/info/rfc2579>.
[RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. Schoenwaelder, Ed., "Conformance Statements for SMIv2", STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, <http://www.rfc-editor.org/info/rfc2580>.
[RFC2580]McCloghrie，K.，Ed.，Perkins，D.，Ed.，和J.Schoenwaeld，Ed.“SMIv2的一致性声明”，STD 58，RFC 2580，DOI 10.17487/RFC2580，1999年4月<http://www.rfc-editor.org/info/rfc2580>.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, <http://www.rfc-editor.org/info/rfc2863>.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 2863，DOI 10.17487/RFC2863，2000年6月<http://www.rfc-editor.org/info/rfc2863>.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol Label Switching Architecture", RFC 3031, DOI 10.17487/RFC3031, January 2001, <http://www.rfc-editor.org/info/rfc3031>.
[RFC3031]Rosen，E.，Viswanathan，A.，和R.Callon，“多协议标签交换体系结构”，RFC 3031，DOI 10.17487/RFC3031，2001年1月<http://www.rfc-editor.org/info/rfc3031>.
[RFC3289] Baker, F., Chan, K., and A. Smith, "Management Information Base for the Differentiated Services Architecture", RFC 3289, DOI 10.17487/RFC3289, May 2002, <http://www.rfc-editor.org/info/rfc3289>.
[RFC3289]Baker，F.，Chan，K.和A.Smith，“差异化服务体系结构的管理信息库”，RFC 3289，DOI 10.17487/RFC3289，2002年5月<http://www.rfc-editor.org/info/rfc3289>.
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, DOI 10.17487/RFC3411, December 2002, <http://www.rfc-editor.org/info/rfc3411>.
[RFC3411]Harrington，D.，Presohn，R.，和B.Wijnen，“描述简单网络管理协议（SNMP）管理框架的体系结构”，STD 62，RFC 3411，DOI 10.17487/RFC34112002年12月<http://www.rfc-editor.org/info/rfc3411>.
[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/RFC3414, December 2002, <http://www.rfc-editor.org/info/rfc3414>.
[RFC3414]Blumenthal，U.和B.Wijnen，“简单网络管理协议（SNMPv3）版本3的基于用户的安全模型（USM）”，STD 62，RFC 3414，DOI 10.17487/RFC3414，2002年12月<http://www.rfc-editor.org/info/rfc3414>.
[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model", RFC 3826, DOI 10.17487/RFC3826, June 2004, <http://www.rfc-editor.org/info/rfc3826>.
[RFC3826]Blumenthal，U.，Maino，F.，和K.McCloghrie，“基于SNMP用户的安全模型中的高级加密标准（AES）密码算法”，RFC 3826，DOI 10.17487/RFC3826，2004年6月<http://www.rfc-editor.org/info/rfc3826>.
[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, <http://www.rfc-editor.org/info/rfc5591>.
[RFC5591]Harrington，D.和W.Hardaker，“简单网络管理协议（SNMP）的传输安全模型”，STD 78，RFC 5591，DOI 10.17487/RFC55912009年6月<http://www.rfc-editor.org/info/rfc5591>.
[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 2009, <http://www.rfc-editor.org/info/rfc5592>.
[RFC5592]Harrington，D.，Salowey，J.，和W.Hardaker，“简单网络管理协议（SNMP）的安全外壳传输模型”，RFC 5592，DOI 10.17487/RFC5592，2009年6月<http://www.rfc-editor.org/info/rfc5592>.
[RFC5601] Nadeau, T., Ed., and D. Zelig, Ed., "Pseudowire (PW) Management Information Base (MIB)", RFC 5601, DOI 10.17487/RFC5601, July 2009, <http://www.rfc-editor.org/info/rfc5601>.
[RFC5601]Nadeau，T.，Ed.，和D.Zelig，Ed.，“伪线（PW）管理信息库（MIB）”，RFC 5601，DOI 10.17487/RFC5601，2009年7月<http://www.rfc-editor.org/info/rfc5601>.
[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, <http://www.rfc-editor.org/info/rfc6353>.
[RFC6353]Hardaker，W.“简单网络管理协议（SNMP）的传输层安全（TLS）传输模型”，STD 78，RFC 6353，DOI 10.17487/RFC6353，2011年7月<http://www.rfc-editor.org/info/rfc6353>.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, DOI 10.17487/RFC3410, December 2002, <http://www.rfc-editor.org/info/rfc3410>.
[RFC3410]Case，J.，Mundy，R.，Partain，D.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 3410，DOI 10.17487/RFC3410，2002年12月<http://www.rfc-editor.org/info/rfc3410>.
[RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of Textual Conventions (TCs) for Multiprotocol Label Switching (MPLS) Management", RFC 3811, DOI 10.17487/RFC3811, June 2004, <http://www.rfc-editor.org/info/rfc3811>.
[RFC3811]Nadeau，T.，Ed.，和J.Cucchiara，Ed.，“多协议标签交换（MPLS）管理的文本约定（TC）定义”，RFC 3811，DOI 10.17487/RFC3811，2004年6月<http://www.rfc-editor.org/info/rfc3811>.
[RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)", RFC 3812, DOI 10.17487/RFC3812, June 2004, <http://www.rfc-editor.org/info/rfc3812>.
[RFC3812]Srinivasan，C.，Viswanathan，A.，和T.Nadeau，“多协议标签交换（MPLS）流量工程（TE）管理信息库（MIB）”，RFC 3812，DOI 10.17487/RFC3812，2004年6月<http://www.rfc-editor.org/info/rfc3812>.
[RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) Management Information Base (MIB)", RFC 3813, DOI 10.17487/RFC3813, June 2004, <http://www.rfc-editor.org/info/rfc3813>.
[RFC3813]Srinivasan，C.，Viswanathan，A.，和T.Nadeau，“多协议标签交换（MPLS）标签交换路由器（LSR）管理信息库（MIB）”，RFC 3813，DOI 10.17487/RFC3813，2004年6月<http://www.rfc-editor.org/info/rfc3813>.
[RFC4221] Nadeau, T., Srinivasan, C., and A. Farrel, "Multiprotocol Label Switching (MPLS) Management Overview", RFC 4221, DOI 10.17487/RFC4221, November 2005, <http://www.rfc-editor.org/info/rfc4221>.
[RFC4221]Nadeau，T.，Srinivasan，C.，和A.Farrel，“多协议标签交换（MPLS）管理概述”，RFC 4221DOI 10.17487/RFC4221，2005年11月<http://www.rfc-editor.org/info/rfc4221>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, DOI 10.17487/RFC5226, May 2008, <http://www.rfc-editor.org/info/rfc5226>.
[RFC5226]Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 5226，DOI 10.17487/RFC5226，2008年5月<http://www.rfc-editor.org/info/rfc5226>.
[RFC5654] Niven-Jenkins, B., Ed., Brungard, D., Ed., Betts, M., Ed., Sprecher, N., and S. Ueno, "Requirements of an MPLS Transport Profile", RFC 5654, DOI 10.17487/RFC5654, September 2009, <http://www.rfc-editor.org/info/rfc5654>.
[RFC5654]Niven Jenkins，B.，Ed.，Brungard，D.，Ed.，Betts，M.，Ed.，Sprecher，N.，和S.Ueno，“MPLS传输配置文件的要求”，RFC 5654，DOI 10.17487/RFC5654，2009年9月<http://www.rfc-editor.org/info/rfc5654>.
[RFC5860] Vigoureux, M., Ed., Ward, D., Ed., and M. Betts, Ed., "Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport Networks", RFC 5860, DOI 10.17487/RFC5860, May 2010, <http://www.rfc-editor.org/info/rfc5860>.
[RFC5860]Vigoureux，M.，Ed.，Ward，D.，Ed.，和M.Betts，Ed.“MPLS传输网络中的操作、管理和维护（OAM）要求”，RFC 5860，DOI 10.17487/RFC5860，2010年5月<http://www.rfc-editor.org/info/rfc5860>.
[RFC6370] Bocci, M., Swallow, G., and E. Gray, "MPLS Transport Profile (MPLS-TP) Identifiers", RFC 6370, DOI 10.17487/RFC6370, September 2011, <http://www.rfc-editor.org/info/rfc6370>.
[RFC6370]Bocci，M.，Swallow，G.和E.Gray，“MPLS传输配置文件（MPLS-TP）标识符”，RFC 6370，DOI 10.17487/RFC6370，2011年9月<http://www.rfc-editor.org/info/rfc6370>.
[RFC6371] Busi, I., Ed., and D. Allan, Ed., "Operations, Administration, and Maintenance Framework for MPLS-Based Transport Networks", RFC 6371, DOI 10.17487/RFC6371, September 2011, <http://www.rfc-editor.org/info/rfc6371>.
[RFC6371]Busi，I.，Ed.，和D.Allan，Ed.，“基于MPLS的传输网络的运营、管理和维护框架”，RFC 6371，DOI 10.17487/RFC63711911年9月<http://www.rfc-editor.org/info/rfc6371>.
[RFC6639] King, D., Ed., and M. Venkatesan, Ed., "Multiprotocol Label Switching Transport Profile (MPLS-TP) MIB-Based Management Overview", RFC 6639, DOI 10.17487/RFC6639, June 2012, <http://www.rfc-editor.org/info/rfc6639>.
[RFC6639]King，D.，Ed.，和M.Venkatesan，Ed.，“基于MIB的多协议标签交换传输配置文件（MPLS-TP）管理概述”，RFC 6639，DOI 10.17487/RFC6639，2012年6月<http://www.rfc-editor.org/info/rfc6639>.
[RFC6923] Winter, R., Gray, E., van Helvoort, H., and M. Betts, "MPLS Transport Profile (MPLS-TP) Identifiers Following ITU-T Conventions", RFC 6923, DOI 10.17487/RFC6923, May 2013, <http://www.rfc-editor.org/info/rfc6923>.
[RFC6923]Winter，R.，Gray，E.，van Helvoort，H.，和M.Betts，“遵循ITU-T公约的MPLS传输配置文件（MPLS-TP）标识符”，RFC 6923，DOI 10.17487/RFC6923，2013年5月<http://www.rfc-editor.org/info/rfc6923>.
Acknowledgments
致谢
We wish to thank Muly Ilan, Adrian Farrel, Joan Cucchiara, Weiying Cheng, Mach Chen, Peter Yee, and Tina TSOU for their valuable comments on this document.
我们要感谢Muly Ilan、Adrian Farrel、Joan Cucchiara、郑维英、Mach Chen、Peter Yee和Tina TSOU对本文件的宝贵意见。
The coauthors of this document, the working group chairs, the document shepherd, the responsible AD, and the MPLS Working Group wish to dedicate this RFC to the memory of our friend and colleague Ping Pan, in recognition for his devotion and hard work at the IETF.
本文件的合著者、工作组主席、文件守护者、负责的广告和MPLS工作组希望将本RFC献给我们的朋友和同事潘平，以表彰他在IETF的奉献和辛勤工作。
Authors' Addresses
作者地址
Ping Pan Infinera
平盘酒店
Sam Aldrin Google, Inc. 1600 Amphitheatre Parkway Mountain View, CA 94043 United States
Sam Aldrin Google，Inc.美国加利福尼亚州山景大道1600号圆形剧场，邮编94043
Email: aldrin.ietf@gmail.com
Email: aldrin.ietf@gmail.com
Venkatesan Mahalingam Dell, Inc. 5450 Great America Parkway Santa Clara, CA 95054 United States
Venkatesan Mahalingam Dell，Inc.美国加利福尼亚州圣克拉拉大美洲大道5450号，邮编95054
Email: venkat.mahalingams@gmail.com
Email: venkat.mahalingams@gmail.com
Kannan KV Sampath Redeem India
Kannan KV Sampath拯救印度
Email: kannankvs@gmail.com
Email: kannankvs@gmail.com
Thomas D. Nadeau Brocade
托马斯·纳多·博科
Email: tnadeau@lucidvision.com
Email: tnadeau@lucidvision.com
Sami Boutros VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 United States
Sami Boutros VMware，Inc.美国加利福尼亚州帕洛阿尔托Hillview大道3401号，邮编94304
Email: sboutros@vmware.com
Email: sboutros@vmware.com