Internet Engineering Task Force (IETF) S. Mansfield, Ed.
Request for Comments: 5950 E. Gray, Ed.
Category: Informational Ericsson
ISSN: 2070-1721 K. Lam, Ed.
Alcatel-Lucent
September 2010
Internet Engineering Task Force (IETF) S. Mansfield, Ed.
Request for Comments: 5950 E. Gray, Ed.
Category: Informational Ericsson
ISSN: 2070-1721 K. Lam, Ed.
Alcatel-Lucent
September 2010
Network Management Framework for MPLS-based Transport Networks
基于MPLS传输网络的网络管理框架
Abstract
摘要
This document provides the network management framework for the Transport Profile for Multi-Protocol Label Switching (MPLS-TP).
本文档提供了多协议标签交换（MPLS-TP）传输配置文件的网络管理框架。
This framework relies on the management terminology from the ITU-T to describe the management architecture that could be used for an MPLS-TP management network.
该框架依赖ITU-T中的管理术语来描述可用于MPLS-TP管理网络的管理体系结构。
The management of the MPLS-TP network could be based on multi-tiered distributed management systems. This document provides a description of the network and element management architectures that could be applied and also describes heuristics associated with fault, configuration, and performance aspects of the management system.
MPLS-TP网络的管理可以基于多层分布式管理系统。本文档描述了可应用的网络和元件管理体系结构，还描述了与管理系统的故障、配置和性能方面相关的启发式方法。
This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunication Union Telecommunication Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the IETF MPLS and PWE3 architectures to support the capabilities and functionalities of a packet transport network.
本文件是联合互联网工程任务组（IETF）/国际电信联盟电信标准化部门（ITU-T）努力的成果，旨在将MPLS传输配置文件纳入IETF MPLS和PWE3体系结构中，以支持分组传输网络的能力和功能。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
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). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非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/rfc5950.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc5950.
Copyright Notice
版权公告
Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2010 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
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Management Architecture . . . . . . . . . . . . . . . . . . . 5
2.1. Network Management Architecture . . . . . . . . . . . . . 5
2.2. Element Management Architecture . . . . . . . . . . . . . 6
2.3. Standard Management Interfaces . . . . . . . . . . . . . . 10
2.4. Management- and Control-Specific Terminology . . . . . . . 11
2.5. Management Channel . . . . . . . . . . . . . . . . . . . . 11
3. Fault Management . . . . . . . . . . . . . . . . . . . . . . . 13
3.1. Supervision . . . . . . . . . . . . . . . . . . . . . . . 13
3.2. Validation . . . . . . . . . . . . . . . . . . . . . . . . 13
3.3. Alarm Handling . . . . . . . . . . . . . . . . . . . . . . 13
4. Configuration Management . . . . . . . . . . . . . . . . . . . 13
4.1. LSP Ownership Handover . . . . . . . . . . . . . . . . . . 14
5. Performance Management . . . . . . . . . . . . . . . . . . . . 15
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
7. Security Considerations . . . . . . . . . . . . . . . . . . . 16
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8.1. Normative References . . . . . . . . . . . . . . . . . . . 16
8.2. Informative References . . . . . . . . . . . . . . . . . . 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3
2. Management Architecture . . . . . . . . . . . . . . . . . . . 5
2.1. Network Management Architecture . . . . . . . . . . . . . 5
2.2. Element Management Architecture . . . . . . . . . . . . . 6
2.3. Standard Management Interfaces . . . . . . . . . . . . . . 10
2.4. Management- and Control-Specific Terminology . . . . . . . 11
2.5. Management Channel . . . . . . . . . . . . . . . . . . . . 11
3. Fault Management . . . . . . . . . . . . . . . . . . . . . . . 13
3.1. Supervision . . . . . . . . . . . . . . . . . . . . . . . 13
3.2. Validation . . . . . . . . . . . . . . . . . . . . . . . . 13
3.3. Alarm Handling . . . . . . . . . . . . . . . . . . . . . . 13
4. Configuration Management . . . . . . . . . . . . . . . . . . . 13
4.1. LSP Ownership Handover . . . . . . . . . . . . . . . . . . 14
5. Performance Management . . . . . . . . . . . . . . . . . . . . 15
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
7. Security Considerations . . . . . . . . . . . . . . . . . . . 16
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
8.1. Normative References . . . . . . . . . . . . . . . . . . . 16
8.2. Informative References . . . . . . . . . . . . . . . . . . 17
This document provides the network management framework for the Transport Profile for Multi-Protocol Label Switching (MPLS-TP). Requirements for network management in an MPLS-TP network are documented in "Network Management Requirements for MPLS-based Transport Networks" [3], and this document explains how network elements and networks that support MPLS-TP can be managed using solutions that satisfy those requirements. The relationship between Operations, Administration, and Maintenance (OAM), management, and other framework documents is described in the MPLS-TP framework [4] document.
本文档提供了多协议标签交换（MPLS-TP）传输配置文件的网络管理框架。MPLS-TP网络中的网络管理要求记录在“基于MPLS的传输网络的网络管理要求”[3]中，本文件解释了如何使用满足这些要求的解决方案来管理支持MPLS-TP的网元和网络。MPLS-TP框架[4]文档中描述了操作、管理和维护（OAM）、管理和其他框架文档之间的关系。
This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunication Union Telecommunication Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the IETF MPLS and PWE3 architectures to support the capabilities and functionalities of a packet transport network.
本文件是联合互联网工程任务组（IETF）/国际电信联盟电信标准化部门（ITU-T）努力的成果，旨在将MPLS传输配置文件纳入IETF MPLS和PWE3体系结构中，以支持分组传输网络的能力和功能。
This framework relies on the management terminology from the ITU-T to describe the management architecture that could be used for an MPLS-TP management network. The terminology listed below are taken from/based on the definitions found in ITU-T G.7710 [6], ITU-T G.7712 [7], and ITU-T M.3013 [13].
该框架依赖ITU-T中的管理术语来描述可用于MPLS-TP管理网络的管理体系结构。以下所列术语取自/基于ITU-T G.7710[6]、ITU-T G.7712[7]和ITU-T M.3013[13]中的定义。
o Communication Channel (CCh): A logical channel between network elements (NEs) that can be used in (for example) management plane applications or control plane applications. For MPLS-TP, the physical channel supporting the CCh is the MPLS-TP Management Communication Channel (MCC).
o 通信信道（CCh）：网元（NE）之间的逻辑信道，可用于（例如）管理平面应用或控制平面应用。对于MPLS-TP，支持CCh的物理信道是MPLS-TP管理通信信道（MCC）。
o Data Communication Network (DCN): A network that supports Layer 1 (physical), Layer 2 (data-link), and Layer 3 (network) functionality for distributed management communications related to the management plane, for distributed signaling communications related to the control plane, and other operations communications (e.g., order-wire/voice communications, software downloads, etc.). See ITU-T G.7712 [7].
o 数据通信网络（DCN）：支持第1层（物理）、第2层（数据链路）和第3层（网络）功能的网络，用于与管理平面相关的分布式管理通信、与控制平面相关的分布式信令通信和其他操作通信（例如，订购有线/语音通信、软件下载等）。参见ITU-T g.7712[7]。
o Equipment Management Function (EMF): The management functions within an NE. See ITU-T G.7710 [6].
o 设备管理功能（EMF）：网元内的管理功能。见ITU-T G.7710[6]。
o Local Craft Terminal (LCT): An out-of-band device that connects to an NE for management purposes. See ITU-T G.7710 [6].
o 本地工艺终端（LCT）：为了管理目的连接到网元的带外设备。见ITU-T G.7710[6]。
o Label Switched Path (LSP): An MPLS-TP LSP is an LSP that uses a subset of the capabilities of an MPLS LSP in order to meet the requirements of an MPLS transport network as described in the MPLS-TP framework [4].
o 标签交换路径（LSP）：MPLS-TP LSP是使用MPLS LSP功能子集以满足MPLS-TP框架[4]中所述MPLS传输网络要求的LSP。
o Management Application Function (MAF): An application process that participates in system management. See ITU-T G.7710 [6].
o 管理应用程序功能（MAF）：参与系统管理的应用程序流程。见ITU-T G.7710[6]。
o Management Communication Channel (MCC): A CCh dedicated for management plane communications. See ITU-T G.7712 [7].
o 管理通信信道（MCC）：专用于管理平面通信的CCh。见ITU-T G.7712[7]。
o Message Communication Function (MCF): The communications process that performs functions such as information interchange and relay. See ITU-T M.3013 [13].
o 消息通信功能（MCF）：执行信息交换和中继等功能的通信过程。见ITU-T M.3013[13]。
o Management Communication Network (MCN): A DCN supporting management plane communication is referred to as a Management Communication Network (MCN). See ITU-T G.7712 [7].
o 管理通信网络（MCN）：支持管理平面通信的DCN称为管理通信网络（MCN）。见ITU-T G.7712[7]。
o MPLS-TP NE: A network element (NE) that supports MPLS-TP functions. Another term that is used for a network element is node. In terms of this document, the term node is equivalent to NE.
o MPLS-TP网元：支持MPLS-TP功能的网元。用于网络元素的另一个术语是节点。在本文件中，术语节点等同于NE。
o MPLS-TP network: A network in which MPLS-TP NEs are deployed.
o MPLS-TP网络：部署MPLS-TP网元的网络。
o Network Element Function (NEF): The set of functions necessary to manage a network element. See ITU-T M.3010 [11].
o 网元功能（NEF）：管理网元所需的一组功能。见ITU-T M.3010[11]。
o Operations, Administration, and Maintenance (OAM): For the MPLS-TP effort the term OAM means the set of tools that consist of "operation" activities that are undertaken to keep the network up and running, "administration" activities that keep track of resources in the network and how they are used, and "maintenance" activities that facilitate repairs and upgrades. For a complete expansion of the acronym, see "The OAM Acronym Soup" [15].
o 操作、管理和维护（OAM）：对于MPLS-TP工作，术语OAM是指由“操作”活动组成的一组工具，这些活动用于保持网络正常运行，“管理”活动用于跟踪网络中的资源及其使用方式，以及“维护”促进维修和升级的活动。有关首字母缩略词的完整扩展，请参见“OAM首字母缩略词汤”[15]。
o Operations System (OS): A system that performs the functions that support processing of information related to operations, administration, maintenance, and provisioning (OAM&P) (see "The OAM Acronym Soup" [15]) for the networks, including surveillance and testing functions to support customer access maintenance. See ITU-T M.3010 [11].
o 操作系统（OS）：执行支持网络操作、管理、维护和供应（OAM&P）（参见“OAM首字母缩略词Soup”[15]）相关信息处理功能的系统，包括支持客户访问维护的监视和测试功能。见ITU-T M.3010[11]。
o Signaling Communication Network (SCN): A DCN supporting control plane communication is referred to as a Signaling Communication Network (SCN). See ITU-T G.7712 [7].
o 信令通信网络（SCN）：支持控制平面通信的DCN称为信令通信网络（SCN）。见ITU-T G.7712[7]。
o Signaling Communication Channel (SCC): A CCh dedicated for control plane communications. The SCC may be used for GMPLS/ASON signaling and/or other control plane messages (e.g., routing messages). See ITU-T G.7712 [7].
o 信令通信信道（SCC）：专用于控制平面通信的CCh。SCC可用于GMPLS/ASON信令和/或其他控制平面消息（例如，路由消息）。见ITU-T G.7712[7]。
The management of the MPLS-TP network could be based on a multi-tiered distributed management systems, for example as described in ITU-T M.3010 [11] and ITU-T M.3060/Y.2401 [12]. Each tier provides a predefined level of network management capabilities. The lowest tier of this organization model includes the MPLS-TP network element that provides the transport service and the Operations System (OS) at the Element Management Level. The Management Application Function (MAF) within the NEs and OSs provides the management support. The MAF at each entity can include agents only, managers only, or both agents and managers. The MAF that includes managers is capable of managing an agent included in other MAF.
MPLS-TP网络的管理可以基于多层分布式管理系统，例如，如ITU-T M.3010[11]和ITU-T M.3060/Y.2401[12]中所述。每一层都提供预定义级别的网络管理功能。该组织模型的最低层包括提供传输服务的MPLS-TP网元和网元管理级别的操作系统（OS）。网元和OSs中的管理应用功能（MAF）提供管理支持。每个实体的MAF可以仅包括代理、经理或代理和经理。包含经理的MAF能够管理其他MAF中包含的代理。
The management communication to peer NEs and/or OSs is provided via the Message Communication Function (MCF) within each entity (e.g., NE and OS). The user can access the management of the MPLS-TP transport network via a Local Craft Terminal (LCT) attached to the NE or via a Work Station (WS) attached to the OS.
通过每个实体（例如，网元和操作系统）内的消息通信功能（MCF）提供与对等网元和/或OSs的管理通信。用户可以通过连接到网元的本地工艺终端（LCT）或连接到OS的工作站（WS）访问MPLS-TP传输网络的管理。
A transport Management Network (MN) may consist of several transport-technology-specific Management Networks. Management network partitioning (Figure 1) below (based on ITU-T G.7710 [6]) shows the management network partitioning. Notation used in G.7710 for a transport-technology-specific MN is x.MN, where x is the transport-specific technology. An MPLS-TP-specific MN is abbreviated as MT.MN. Where there is no ambiguity, we will use "MN" for an MPLS-TP-specific MN. In the figure below, O.MSN is equivalent to an OTN management Subnetwork.
一个传输管理网络（MN）可以由几个特定于传输技术的管理网络组成。下面的管理网络分区（图1）（基于ITU-T G.7710[6]）显示了管理网络分区。G.7710中用于特定于传输技术的MN的符号是x.MN，其中x是特定于传输的技术。MPLS TP特定MN缩写为MT.MN。在没有歧义的地方，我们将使用“MN”表示MPLS TP特定的MN。在下图中，O.MSN相当于OTN管理子网。
______________________________ _________________________________
|.-------.-------.----.-------.||.--------.--------.----.--------.|
|: : : : :||: : : : :|
|:O.MSN-1:O.MSN-2: .. :O.MSN-n:||:MT.MSN-1:MT.MSN-2: .. :MT.MSN-n:|
|: : : : :||: : : : :|
'-============================-''-===============================-'
_______________________________
|.-------.-------.-----.-------.|
|: : : : :|
|:x.MSN-1:x.MSN-2: ... :x.MSN-n:|
|: : : : :|
'-=============================-'
______________________________ _________________________________
|.-------.-------.----.-------.||.--------.--------.----.--------.|
|: : : : :||: : : : :|
|:O.MSN-1:O.MSN-2: .. :O.MSN-n:||:MT.MSN-1:MT.MSN-2: .. :MT.MSN-n:|
|: : : : :||: : : : :|
'-============================-''-===============================-'
_______________________________
|.-------.-------.-----.-------.|
|: : : : :|
|:x.MSN-1:x.MSN-2: ... :x.MSN-n:|
|: : : : :|
'-=============================-'
Management Network Partitioning
管理网络分区
Figure 1
图1
The management of the MPLS-TP network is separable from the management of the other technology-specific networks, and it operates independently of any particular client- or server-layer management plane.
MPLS-TP网络的管理与其他特定于技术的网络的管理是分开的，它独立于任何特定的客户端或服务器层管理平面运行。
An MPLS-TP Management Network (MT.MN) could be partitioned into MPLS-TP Management SubNetworks ("MT.MSN" or "MPLS-TP MSN", or just "MSN" where usage is unambiguous) for consideration of scalability (e.g., geographic or load balancing) or administration (e.g., operation or ownership).
MPLS-TP管理网络（MT.MN）可划分为MPLS-TP管理子网（“MT.MSN”或“MPLS-TP MSN”，或仅“MSN”，其中使用是明确的），以考虑可伸缩性（例如，地理或负载平衡）或管理（例如，操作或所有权）。
The MPLS-TP MSN could be connected to other parts of the MN through one or more LCTs and/or OSs. The Message Communication Function (MCF) of an MPLS-TP NE initiates/terminates, routes, or otherwise processes management messages over CChs or via an external interface.
MPLS-TP MSN可以通过一个或多个LCT和/或OSs连接到MN的其他部分。MPLS-TP网元的消息通信功能（MCF）通过CCH或通过外部接口发起/终止、路由或以其他方式处理管理消息。
Multiple addressable MPLS-TP NEs could be present at a single physical location (i.e., site or office). The inter-site communications link between the MPLS-TP NEs will normally be provided by the CChs. Within a particular site, the NEs could communicate via an intra-site CCh or via a LAN.
多个可寻址MPLS-TP网元可以存在于单个物理位置（即站点或办公室）。MPLS-TP网元之间的站点间通信链路通常由CChs提供。在特定站点内，网元可以通过站点内CCh或LAN进行通信。
The Equipment Management Function (EMF) of an MPLS-TP NE provides the means through which a management system manages the NE.
MPLS-TP网元的设备管理功能（EMF）提供了管理系统管理网元的方法。
The EMF interacts with the NE's transport functions by exchanging Management Information (MI) across the Management Point (MP) Reference Points. The EMF may contain a number of functions that
EMF通过在管理点（MP）参考点之间交换管理信息（MI），与网元的传输功能进行交互。EMF可能包含许多函数
provide a data reduction mechanism on the information received across the MP Reference Points.
针对MP参考点接收到的信息提供数据缩减机制。
The EMF includes functions such as Date and Time, FCAPS (Fault, Configuration, Accounting, Performance, and Security) management, and Control Plane functions. The EMF provides event message processing, data storage, and logging. The management Agent, a component of the EMF, converts internal management information (MI signals) into Management Application messages and vice versa. The Agent responds to Management Application messages from the Message Communication Function (MCF) by performing the appropriate operations on (for example) the Managed Objects in a Management Information Base (MIB), as necessary. The MCF contains communications functions related to the world outside of the NE (i.e., Date and Time source, Management Plane, Control Plane, Local Craft Terminal, and Local Alarms).
EMF包括诸如日期和时间、FCAPS（故障、配置、记帐、性能和安全）管理和控制平面功能等功能。EMF提供事件消息处理、数据存储和日志记录。管理代理是EMF的一个组件，它将内部管理信息（MI信号）转换为管理应用程序消息，反之亦然。代理根据需要对管理信息库（MIB）中的受管对象（例如）执行适当的操作，以响应来自消息通信功能（MCF）的管理应用程序消息。MCF包含与网元外部世界相关的通信功能（即日期和时间源、管理平面、控制平面、本地工艺终端和本地警报）。
The Date and Time functions keep track of the NE's date/time, which is used by the FCAPS management functions to e.g., time stamp event reports.
日期和时间功能跟踪网元的日期/时间，FCAPS管理功能使用该日期/时间，例如，时间戳事件报告。
Below are diagrams that illustrate the components of the Equipment Management Function (EMF) of a Network Element (NE). The high-level decomposition of the Network Element Function (NEF) picture (Figure 2) provides the breakdown of the NEF, then the EMF picture (Figure 3) provides the details of Equipment Management Function, and finally the Message Communication Function (MCF) picture (Figure 4) details the MCF.
下图说明了网元（NE）的设备管理功能（EMF）的组件。网元功能（NEF）图（图2）的高级分解提供了NEF的分解，然后EMF图（图3）提供了设备管理功能的详细信息，最后消息通信功能（MCF）图（图4）提供了MCF的详细信息。
____________________________________________________
| Network Element Function (NEF) |
| _________________________________________ |
|| | |
|| Transport Plane Atomic Functions | |
||_________________________________________| |
| | |
| | Management |
| | Information |
| ___________________|_________________ |
| | (from date/time)<-----------+ |
| | Equipment | | |
| | Management (to/from management)<--------+ | |
| | Function | | | |
| | (EMF) (to/from control)<-----+ | | |
| | | | | | |
| | (to local alarm)---+ | | | |
| |_____________________________________| | | | | |
| | | | | |
| +--------------------------------------+ | | | |
| | +---------------------------------------+ | | |
| | | +----------------------------------------+ | |
| | | | +-----------------------------------------+ |external
| | | | | Date & Time _________________ |time
| | | | | Interface | Message | |source
| | | | +-------------- Communication <-----------------------
| | | | | Function (MCF) | |
| | | | Management | | |management
| | | +----------------> | |plane
| | | Plane Interface <---------------------->
| | | | | |local
| | | | | |craft
| | | Control Plane | | |terminal
| | +------------------> <---------------------->
| | Interface | | |control
| | | | |plane
| | Local Alarm | <---------------------->
| +--------------------> | |
| Interface | | |to local
| | | |alarms
| |_________________--------------------->
|____________________________________________________|
____________________________________________________
| Network Element Function (NEF) |
| _________________________________________ |
|| | |
|| Transport Plane Atomic Functions | |
||_________________________________________| |
| | |
| | Management |
| | Information |
| ___________________|_________________ |
| | (from date/time)<-----------+ |
| | Equipment | | |
| | Management (to/from management)<--------+ | |
| | Function | | | |
| | (EMF) (to/from control)<-----+ | | |
| | | | | | |
| | (to local alarm)---+ | | | |
| |_____________________________________| | | | | |
| | | | | |
| +--------------------------------------+ | | | |
| | +---------------------------------------+ | | |
| | | +----------------------------------------+ | |
| | | | +-----------------------------------------+ |external
| | | | | Date & Time _________________ |time
| | | | | Interface | Message | |source
| | | | +-------------- Communication <-----------------------
| | | | | Function (MCF) | |
| | | | Management | | |management
| | | +----------------> | |plane
| | | Plane Interface <---------------------->
| | | | | |local
| | | | | |craft
| | | Control Plane | | |terminal
| | +------------------> <---------------------->
| | Interface | | |control
| | | | |plane
| | Local Alarm | <---------------------->
| +--------------------> | |
| Interface | | |to local
| | | |alarms
| |_________________--------------------->
|____________________________________________________|
High-Level Decomposition of NEF
NEF的高级分解
Figure 2
图2
______________________________________________________
| _______________________________________ |
| Equipment | Management Application ||
| Management | Function (MAF) ||
| Function | _________________ ||
| (EMF) || | __________________||
| ___________||_______________ | | ||
| | | | | Date & Time ||
| | Date & Time Functions | | | Interface ||<-- 1
| |____________________________| | |__________________||
| ___________||_______________ | __________________||
| | | | | ||
| | Fault Management | | | Management ||
| |____________________________| | | Plane Interface ||<-> 2
| ___________||_______________ | |__________________||
| | | | ||
| | Configuration Management | | __________________||
| |____________________________| | | ||
| ___________||_______________ | | Control ||
| | | | | Plane Interface ||<-> 3
| | Account Management | | |__________________||
| |____________________________| | ||
| ___________||_______________ | ||
| | | | ||
| | Performance Management | | ||
| |____________________________| | ||
| ___________||_______________ | ||
| | | | ||
| | Security Management | | ||
| |____________________________| | ||
| ___________||_______________ | ||
| | | | ||
| | Control Plane Function | | ||
| |____________________________| | ||
| || | __________________||
| || | | ||
| || | | Local Alarm ||
| +----->| Agent | | Interface ||--> 4
| v ||_________________| |__________________||
| .-===-. |_______________________________________||
| | MIB | |
| `-._.-' |
|______________________________________________________|
______________________________________________________
| _______________________________________ |
| Equipment | Management Application ||
| Management | Function (MAF) ||
| Function | _________________ ||
| (EMF) || | __________________||
| ___________||_______________ | | ||
| | | | | Date & Time ||
| | Date & Time Functions | | | Interface ||<-- 1
| |____________________________| | |__________________||
| ___________||_______________ | __________________||
| | | | | ||
| | Fault Management | | | Management ||
| |____________________________| | | Plane Interface ||<-> 2
| ___________||_______________ | |__________________||
| | | | ||
| | Configuration Management | | __________________||
| |____________________________| | | ||
| ___________||_______________ | | Control ||
| | | | | Plane Interface ||<-> 3
| | Account Management | | |__________________||
| |____________________________| | ||
| ___________||_______________ | ||
| | | | ||
| | Performance Management | | ||
| |____________________________| | ||
| ___________||_______________ | ||
| | | | ||
| | Security Management | | ||
| |____________________________| | ||
| ___________||_______________ | ||
| | | | ||
| | Control Plane Function | | ||
| |____________________________| | ||
| || | __________________||
| || | | ||
| || | | Local Alarm ||
| +----->| Agent | | Interface ||--> 4
| v ||_________________| |__________________||
| .-===-. |_______________________________________||
| | MIB | |
| `-._.-' |
|______________________________________________________|
Equipment Management Function
设备管理职能
Figure 3
图3
_________________
| |
| Message |
| Communication |
| Function (MCF) |
| _______________ |
Date & Time || || external
1 <--------------|| Date & Time ||<--------------
Information || Communication || time source
||_______________||
| |
| _______________ |
Management || || management
Plane || Management || plane
2 <------------->|| Plane ||<------------->
Information || Communication || (e.g. - EMS,
||_______________|| peer NE)
| |
| _______________ | control
Control Plane || || plane
3 <------------->|| Control Plane ||<------------->
Information || Communication || (e.g. - EMS,
||_______________|| peer NE)
| : |
| : | local craft
| : | terminal
| : |<------------->
| _______________ |
Local Alarm || || to local
4 -------------->|| Local Alarm ||-------------->
Information || Communication || alarms...
||_______________||
|_________________|
_________________
| |
| Message |
| Communication |
| Function (MCF) |
| _______________ |
Date & Time || || external
1 <--------------|| Date & Time ||<--------------
Information || Communication || time source
||_______________||
| |
| _______________ |
Management || || management
Plane || Management || plane
2 <------------->|| Plane ||<------------->
Information || Communication || (e.g. - EMS,
||_______________|| peer NE)
| |
| _______________ | control
Control Plane || || plane
3 <------------->|| Control Plane ||<------------->
Information || Communication || (e.g. - EMS,
||_______________|| peer NE)
| : |
| : | local craft
| : | terminal
| : |<------------->
| _______________ |
Local Alarm || || to local
4 -------------->|| Local Alarm ||-------------->
Information || Communication || alarms...
||_______________||
|_________________|
Message Communication Function
消息通信功能
Figure 4
图4
The "Network Management Requirements for MPLS-based Transport Networks" document [3] places no restriction on which management interface is to be used for managing an MPLS-TP network. It is possible to provision and manage an end-to-end connection across a network where some segments are created/managed/deleted, for example by NETCONF or SNMP and other segments by CORBA interfaces. Use of any network management interface for one management-related purpose does not preclude use of another network management interface for
“基于MPLS的传输网络的网络管理要求”文件[3]对用于管理MPLS-TP网络的管理接口没有任何限制。可以通过网络提供和管理端到端连接，其中一些网段是通过NETCONF或SNMP创建/管理/删除的，而其他网段是通过CORBA接口创建/管理/删除的。将任何网络管理接口用于一个管理相关目的并不排除将另一个网络管理接口用于
other management-related purposes, or the same purpose at another time. The protocol(s) to be supported are at the discretion of the operator.
其他与管理相关的目的，或另一时间的相同目的。待支持的协议由运营商自行决定。
Data Communication Network (DCN) is the common term for the network used to transport Management and Signaling information between: management systems and network elements, management systems to other management systems, and networks elements to other network elements. The Management Communications Network (MCN) is the part of the DCN that supports the transport of Management information for the Management Plane. The Signaling Communications Network (SCN) is the part of the DCN that supports transport of signaling information for the Control Plane. As shown in , the communication channel terminology picture (Figure 5) each technology has its own terminology that is used for the channels that support the transfer of management and control plane information. For MPLS-TP, the management plane uses the Management Communication Channel (MCC), and the control plane uses the Signaling Communication Channel (SCC).
数据通信网络（DCN）是用于在管理系统和网元、管理系统到其他管理系统以及网元到其他网元之间传输管理和信令信息的网络的通用术语。管理通信网络（MCN）是DCN的一部分，支持管理平面的管理信息传输。信令通信网络（SCN）是DCN的一部分，支持控制平面信令信息的传输。如中所示，通信信道术语图（图5）每种技术都有自己的术语，用于支持管理和控制平面信息传输的信道。对于MPLS-TP，管理平面使用管理通信信道（MCC），控制平面使用信令通信信道（SCC）。
The Communication Channel (CCh) provides a logical channel between NEs for transferring Management and/or Signaling information. Note that some technologies provide separate communication channels for Management (MCC) and Signaling (SCC).
通信信道（CCh）在网元之间提供用于传输管理和/或信令信息的逻辑信道。注意，一些技术为管理（MCC）和信令（SCC）提供单独的通信信道。
MPLS-TP NEs communicate via the DCN. The DCN connects NEs with management systems, NEs with NEs, and management systems with management systems.
MPLS-TP网元通过DCN进行通信。DCN将网元与管理系统、网元与网元以及管理系统与管理系统连接起来。
Common Terminology ____
__________ __________ | |
| | | | /->| NE | \ ____
|Management| |Operations| / |____| \ | |
|Station | <---> |System | |(CCh) | NE |
|__________| |__________| \ _|__ / |____|
\->| | /
| NE |
|____|
Network Elements use a Communication
Channel (CCh) for Transport of Information
Common Terminology ____
__________ __________ | |
| | | | /->| NE | \ ____
|Management| |Operations| / |____| \ | |
|Station | <---> |System | |(CCh) | NE |
|__________| |__________| \ _|__ / |____|
\->| | /
| NE |
|____|
Network Elements use a Communication
Channel (CCh) for Transport of Information
Management Terminology ____
__________ __________ | |
| | | | /->| NE | \ ____
|Management| |Operations| / |____| \ | |
|Station | <---> |System | |(MCC) | NE |
|__________| |__________| \ _|__ / |____|
\->| | /
| NE |
|____|
Network Elements use a Management
Communication Channel (MCC) for Transport
of Management Information
Management Terminology ____
__________ __________ | |
| | | | /->| NE | \ ____
|Management| |Operations| / |____| \ | |
|Station | <---> |System | |(MCC) | NE |
|__________| |__________| \ _|__ / |____|
\->| | /
| NE |
|____|
Network Elements use a Management
Communication Channel (MCC) for Transport
of Management Information
Control Terminology ____
__________ __________ | |
| | | | /->| NE | \ ____
|Management| |Operations| / |____| \ | |
|Station | <---> |System | |(SCC) | NE |
|__________| |__________| \ _|__ / |____|
\->| | /
| NE |
|____|
Network Elements use a Control/Signaling
Communication Channel (SCC) for Transport
of Signaling Information
Control Terminology ____
__________ __________ | |
| | | | /->| NE | \ ____
|Management| |Operations| / |____| \ | |
|Station | <---> |System | |(SCC) | NE |
|__________| |__________| \ _|__ / |____|
\->| | /
| NE |
|____|
Network Elements use a Control/Signaling
Communication Channel (SCC) for Transport
of Signaling Information
Communication Channel Terminology
通信信道术语
Figure 5
图5
A fault is the inability of a function to perform a required action. This does not include an inability due to preventive maintenance, lack of external resources, or planned actions. Fault management provides the mechanisms to detect, verify, isolate, notify, and recover from the fault.
故障是指功能无法执行所需操作。这不包括由于预防性维护、缺乏外部资源或计划的行动而导致的无能力。故障管理提供了检测、验证、隔离、通知和恢复故障的机制。
ITU-T G.7710 [6] lists five basic categories of supervision that provide the functionality necessary to detect, verify, and notify a fault. The categories are: Transmission Supervision, Quality of Service Supervision, Processing Supervision, Hardware Supervision, and Environment Supervision. Each of the categories provides a set of recommendations to ensure that the fault management process is fulfilled.
ITU-T G.7710[6]列出了五种基本的监督类别，它们提供了检测、验证和通知故障所需的功能。其类别为：输电监管、服务质量监管、加工监管、硬件监管和环境监管。每个类别都提供了一组建议，以确保故障管理过程得以完成。
ITU-T G.7710 [6] describes a fault cause as a limited interruption of the required function. It is not reasonable for every fault cause to be reported to maintenance personnel. The validation process is used to turn fault causes (events) into failures (alarms).
ITU-T G.7710[6]将故障原因描述为所需功能的有限中断。向维护人员报告每一个故障原因是不合理的。验证过程用于将故障原因（事件）转化为故障（警报）。
Within an element management system, it is important to consider mechanisms to support severity assignment, alarm reporting control, and logging.
在元素管理系统中，重要的是考虑支持严重性分配、警报报告控制和日志记录的机制。
Configuration management provides the mechanisms to:
配置管理提供了以下机制：
o provision the MPLS-TP services
o 提供MPLS-TP服务
o set up security for the MPLS-TP services and MPLS-TP network elements
o 为MPLS-TP服务和MPLS-TP网络元素设置安全性
o provide the destination for fault notifications and performance parameters
o 提供故障通知和性能参数的目标
o configure and control OAM
o 配置和控制OAM
Also associated with configuration management are hardware and software provisioning and inventory reporting.
与配置管理相关的还有硬件和软件资源调配以及资源清册报告。
MPLS-TP networks can be managed not only by Network Management Systems (i.e., Management Plane (MP)), but also by Control Plane (CP) protocols. The utilization of the control plane is not a mandatory requirement (see MPLS-TP Requirements [2]), but it is often used by network operators in order to make network configuration and Label Switched Path (LSP) recovery both faster and simpler.
MPLS-TP网络不仅可以通过网络管理系统（即管理平面（MP））进行管理，还可以通过控制平面（CP）协议进行管理。控制平面的使用不是强制性要求（参见MPLS-TP要求[2]），但网络运营商经常使用它，以便使网络配置和标签交换路径（LSP）恢复更快、更简单。
In networks where both CP and MP are provided, an LSP could be created by either (CP or MP). The entity creating an LSP owns the data plane resources comprising that LSP. Only the owner of an LSP is typically able to modify/delete it. This results in a need for interaction between the MP and CP to allow either to manage all the resources of a network.
在同时提供CP和MP的网络中，LSP可以由（CP或MP）创建。创建LSP的实体拥有组成该LSP的数据平面资源。通常只有LSP的所有者才能修改/删除它。这导致需要在MP和CP之间进行交互，以允许任何一方管理网络的所有资源。
Network operators might prefer to have full control of the network resources during the set-up phase and then allow the network to be automatically maintained by the Control Plane. This can be achieved by creating LSPs via the Management Plane and subsequently transferring LSP ownership to the Control Plane. This is referred to as "ownership handover" RFC 5493 [10]. MP to CP ownership handover is then considered a requirement where a Control Plane is in use that supports it. The converse (CP to MP ownership handover) is a feature that is recommended -- but not required -- for (G)MPLS networks because it has only minor applications (for example, moving LSPs from one path to another as a maintenance operation).
网络运营商可能更愿意在设置阶段完全控制网络资源，然后允许控制平面自动维护网络。这可以通过通过管理平面创建LSP并随后将LSP所有权转移到控制平面来实现。这被称为“所有权移交”RFC 5493[10]。然后，MP到CP所有权移交被视为一项要求，其中使用支持它的控制平面。相反（CP-to-MP所有权切换）是（G）MPLS网络的推荐功能，但不是必需的，因为它只有较小的应用程序（例如，作为维护操作将LSP从一条路径移动到另一条路径）。
The LSP handover procedure has already been standardized for GMPLS networks, where the signaling protocol used is RSVP-TE (RFC 3209 [1]). The utilization of RSVP-TE enhancements are defined in [5].
LSP切换程序已经为GMPLS网络标准化，其中使用的信令协议是RSVP-TE（RFC 3209[1]）。[5]中定义了RSVP-TE增强的使用。
MP and CP interworking also includes the exchange of information that is either requested by the MP, or a notification by the CP as a consequence of a request from the MP or an automatic action (for example, a failure occurs or an operation is performed). The CP is asked to notify the MP in a reliable manner about the status of the operations it performs and to provide a mechanism to monitor the status of Control Plane objects (e.g., TE Link status, available resources), and to log operations related to Control Plane LSP. Logging is one of the most critical aspects because the MP always needs to have an accurate history and status of each LSP and all Data Plane resources involved in it.
MP和CP互通还包括MP请求的信息交换，或CP因MP请求或自动操作（例如，发生故障或执行操作）而发出的通知。CP被要求以可靠的方式通知MP其执行的操作的状态，并提供一种机制来监控控制平面对象的状态（例如，TE链路状态、可用资源），并记录与控制平面LSP相关的操作。日志记录是最关键的方面之一，因为MP始终需要每个LSP以及其中涉及的所有数据平面资源的准确历史记录和状态。
Performance statistics could overwhelm a Management Network, so it is important to provide flexible instrumentation that enables control over the amount of performance data to be collected. Mechanisms for limiting the quantity of information collected are well known and deployed in IETF standards (see RFC 2819 (RMON) [8] and RFC 4502 (RMON2) [9]). The details of the performance data collected (including loss and delay measurement data) are found in the "Network Management Requirements for MPLS-based Transport Networks" document [3].
性能统计数据可能会压倒管理网络，因此提供灵活的工具以控制要收集的性能数据量非常重要。IETF标准（参见RFC 2819（RMON）[8]和RFC 4502（RMON2）[9]）中众所周知并部署了限制收集信息量的机制。收集的性能数据（包括损耗和延迟测量数据）的详细信息见“基于MPLS的传输网络的网络管理要求”文档[3]。
A distinction is made between performance data that is collected on-demand and data that is collected proactively. The definitions of on-demand and proactive measurement are provided for OAM in the "Network Management Requirements for MPLS-based Transport Networks" document [3].
区分按需收集的性能数据和主动收集的数据。“基于MPLS的传输网络的网络管理要求”文档[3]中为OAM提供了按需和主动测量的定义。
On-demand measurement provides the operator with the ability to do performance measurement for maintenance purpose, such as diagnosis or to provide detailed verification of proactive measurement. It is used typically on specific LSP service instances for a limited time, thus limiting its impact on network performance under normal operations. Therefore, on-demand measurement does not result in scaling issues.
按需测量使操作员能够为维护目的进行性能测量，如诊断或提供主动测量的详细验证。它通常在有限的时间内用于特定的LSP服务实例，从而限制其在正常操作下对网络性能的影响。因此，按需测量不会导致缩放问题。
Proactive measurement is used continuously over time after being configured with periodicity and storage information. Data collected from proactive measurement are usually used for verifying the performance of the service. Proactive performance monitoring has the potential to overwhelm both the process of collecting performance data at a network element (for some arbitrary number of service instances traversing the NE), and the process of reporting this information to the OS. As a consequence of these considerations, operators would typically limit the services to which proactive performance measurement would be applied to a very selective subset of the services being provided and would limit the reporting of this information to statistical summaries (as opposed to raw or detailed performance statistics).
在配置了周期性和存储信息后，主动测量会随着时间的推移持续使用。从主动测量收集的数据通常用于验证服务的性能。主动性能监控有可能压倒在网元上收集性能数据的过程（对于通过网元的任意数量的服务实例），以及向操作系统报告此信息的过程。由于这些考虑因素，运营商通常会将主动绩效测量应用于所提供服务的一个非常有选择性的子集的服务限制，并将此信息的报告限制为统计摘要（而不是原始或详细的绩效统计）。
The authors/editors gratefully acknowledge the thoughtful review, comments and explanations provided by Diego Caviglia, Bernd Zeuner and Dan Romascanu.
作者/编辑感谢Diego Caviglia、Bernd Zeuner和Dan Romascanu提供的深思熟虑的评论、评论和解释。
The ability for the authorized network operator to access EMF interfaces (Section 2.3) when needed is critical to proper operation. Therefore, the EMF interfaces need to be protected from denial-of-service conditions or attack. The EMF interfaces that use or access private information should be protected from eavesdropping, mis-configuration, and/or mal-configuration by unauthorized network elements, systems, or users.
授权网络运营商在需要时访问EMF接口（第2.3节）的能力对于正确操作至关重要。因此，需要保护EMF接口免受拒绝服务条件或攻击。应保护使用或访问私有信息的EMF接口免受未经授权的网元、系统或用户的窃听、错误配置和/或错误配置。
Performance of diagnostic functions and path characterization involves extracting a significant amount of information about network construction that the network operator considers private.
诊断功能和路径特征的执行涉及提取网络运营商认为私有的大量网络结构信息。
Section 4.3 of the "Security Framework for MPLS and GMPLS Networks" document [14] provides a description of the attacks on the Operation and Management Plane and also discusses the background necessary to understand security practices in Internet Service Provider environments. The security practices described are applicable to MPLS-TP environments.
“MPLS和GMPLS网络安全框架”文件[14]第4.3节描述了对运营和管理层面的攻击，并讨论了理解互联网服务提供商环境中安全实践所需的背景知识。所描述的安全实践适用于MPLS-TP环境。
[1] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, December 2001.
[1] Awduche，D.，Berger，L.，Gan，D.，Li，T.，Srinivasan，V.，和G.Swallow，“RSVP-TE：LSP隧道RSVP的扩展”，RFC 3209，2001年12月。
[2] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., and S. Ueno, "Requirements of an MPLS Transport Profile", RFC 5654, September 2009.
[2] Niven Jenkins，B.，Brungard，D.，Betts，M.，Sprecher，N.，和S.Ueno，“MPLS传输配置文件的要求”，RFC 56542009年9月。
[3] Lam, K., Mansfield, S., and E. Gray, "Network Management Requirements for MPLS-based Transport Networks", RFC 5951, September 2010.
[3] Lam，K.，Mansfield，S.，和E.Gray，“基于MPLS的传输网络的网络管理要求”，RFC 59512010年9月。
[4] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L. Berger, "A Framework for MPLS in Transport Networks", RFC 5921, July 2010.
[4] Bocci，M.，Bryant，S.，Frost，D.，Levrau，L.，和L.Berger，“传输网络中MPLS的框架”，RFC 59212010年7月。
[5] Caviglia, D., Ceccarelli, D., Bramanti, D., Li, D., and S. Bardalai, "RSVP-TE Signaling Extension for LSP Handover from the Management Plane to the Control Plane in a GMPLS-Enabled Transport Network", RFC 5852, April 2010.
[5] Caviglia，D.，Ceccarelli，D.，Bramanti，D.，Li，D.，和S.Bardalai，“在启用GMPLS的传输网络中，用于LSP从管理平面切换到控制平面的RSVP-TE信令扩展”，RFC 5852，2010年4月。
[6] International Telecommunication Union, "Common equipment management function requirements", ITU-T Recommendation G.7710/ Y.1701, July 2007.
[6] 国际电信联盟，“通用设备管理功能要求”，ITU-T建议G.7710/Y.17011907年7月。
[7] International Telecommunication Union, "Architecture and specification of data communication network", ITU-T Recommendation G.7712/Y.1703, June 2008.
[7] 国际电信联盟，“数据通信网络的结构和规范”，ITU-T建议G.7712/Y.1703，2008年6月。
[8] Waldbusser, S., "Remote Network Monitoring Management Information Base", STD 59, RFC 2819, May 2000.
[8] Waldbusser，S.，“远程网络监控管理信息库”，STD 59，RFC 2819，2000年5月。
[9] Waldbusser, S., "Remote Network Monitoring Management Information Base Version 2", RFC 4502, May 2006.
[9] Waldbusser，S.，“远程网络监控管理信息库版本2”，RFC 4502，2006年5月。
[10] Caviglia, D., Bramanti, D., Li, D., and D. McDysan, "Requirements for the Conversion between Permanent Connections and Switched Connections in a Generalized Multiprotocol Label Switching (GMPLS) Network", RFC 5493, April 2009.
[10] Caviglia，D.，Bramanti，D.，Li，D.，和D.McDysan，“通用多协议标签交换（GMPLS）网络中永久连接和交换连接之间转换的要求”，RFC 5493，2009年4月。
[11] International Telecommunication Union, "Principles for a telecommunication management network", ITU-T Recommendation M.3010, April 2005.
[11] 国际电信联盟，“电信管理网络原则”，ITU-T建议M.3010，2005年4月。
[12] International Telecommunication Union, "Principles for the Management of Next Generation Networks", ITU-T Recommendation M.3060/Y.2401, March 2006.
[12] 国际电信联盟，“下一代网络管理原则”，ITU-T建议M.3060/Y.2401，2006年3月。
[13] International Telecommunication Union, "Considerations for a telecommunication management network", ITU-T Recommendation M.3013, February 2000.
[13] 国际电信联盟，“电信管理网络的考虑”，ITU-T建议M.3013，2000年2月。
[14] Fang, L., "Security Framework for MPLS and GMPLS Networks", RFC 5920, July 2010.
[14] Fang，L.“MPLS和GMPLS网络的安全框架”，RFC 5920，2010年7月。
[15] Andersson, L., Helvoort, H., Bonica, R., Romascanu, D., and S. Mansfield, ""The OAM Acronym Soup"", Work in progress, June 2010.
[15] 安德森，L.，赫尔沃特，H.，博尼卡，R.，罗马斯坎努，D.，和S.曼斯菲尔德，“OAM首字母缩略词汤”，正在进行的工作，2010年6月。
Authors' Addresses
作者地址
Scott Mansfield (editor) Ericsson 300 Holger Way San Jose, CA 95134 US
斯科特·曼斯菲尔德（编辑）爱立信加利福尼亚州圣何塞霍尔格路300号，美国95134
Phone: +1 724 931 9316
Email: scott.mansfield@ericsson.com
Phone: +1 724 931 9316
Email: scott.mansfield@ericsson.com
Eric Gray (editor) Ericsson 900 Chelmsford Street Lowell, MA 01851 US
埃里克·格雷（编辑）美国马萨诸塞州洛厄尔切姆斯福德街900号爱立信01851
Phone: +1 978 275 7470
Email: eric.gray@ericsson.com
Phone: +1 978 275 7470
Email: eric.gray@ericsson.com
Hing-Kam Lam (editor) Alcatel-Lucent 600-700 Mountain Ave Murray Hill, NJ 07974 US
兴锦林（编辑）美国新泽西州默里山山道阿尔卡特朗讯600-700号，邮编07974
Phone: +1 908 582 0672
Email: Kam.Lam@alcatel-lucent.com
Phone: +1 908 582 0672
Email: Kam.Lam@alcatel-lucent.com