MPLS-TP OAM 框架详解

1星需积分: 9 133 浏览量更新于2024-08-01 收藏 66KB PDF 举报

"MPLS-TP OAM Framework - draft-ietf-mpls-tp-oam-framework-05" MPLS（多协议标签交换）传输配置（MPLS-TP）是一种基于MPLS和伪线（PW）规程的配置，如在MPLS流量工程（MPLS-TE），伪线（PW）以及多段伪线（MS-PW）架构中所定义，同时增加了针对不依赖控制平面的包传输应用的故障、性能和保护切换管理的额外操作、管理和维护（OAM）规程。 MPLS-TP OAM框架文档（draft-ietf-mpls-tp-oam-framework-05）旨在提供一个全面的OAM过程框架，以满足MPLS-TP的OAM需求。该框架着重于支持一套全面的OAM程序，这些程序能够实现对MPLS-TP网络的高效监控和维护，确保服务质量和可靠性。 OAM是网络管理和维护的重要组成部分，它包括了以下关键功能： 1. **故障管理**：OAM提供故障检测、定位和恢复机制，例如连通性验证、故障指示和环回测试，以快速识别和解决网络问题。 2. **性能管理**：通过度量诸如丢包率、延迟、吞吐量等关键性能指标，OAM帮助监测和优化网络性能，确保服务质量（QoS）。 3. **保护和恢复**：OAM支持快速保护切换，以在检测到故障时自动切换到备份路径，减少业务中断时间。 4. **维护操作**：包括配置管理、状态查询、版本控制等功能，确保网络设备的正确配置和更新。 5. **故障检测和通知**：通过周期性的健康检查和事件触发的检测，OAM能够及时发现网络中的异常情况，并向网络管理员发送警报。 6. **端到端和服务层视图**：OAM提供从单个链路到整个服务路径的可见性，帮助理解网络中的问题是否影响了特定服务或用户。 7. **自动化**：MPLS-TP OAM框架支持自动化的工作流程，如自动故障隔离和修复，减少了人工介入的需求，提高了运维效率。 MPLS-TP OAM框架的制定是IETF（互联网工程任务组）与ITU-T（国际电信联盟电信标准化部门）共同努力的结果，目的是将MPLS-TP整合进IETF的MPLS和PWE3（伪线仿真边缘到边缘）架构中，以增强其在承载电信级服务时的能力和适应性。 MPLS-TP OAM框架是构建和维护高可用性、高性能的MPLS-TP网络的关键工具，对于提供稳定、可靠的IP/MPLS服务至关重要。通过实施这个框架，网络运营商可以实现更精细的网络监控，提高故障诊断速度，以及确保端到端的服务质量。

Internet-Draft MPLS-TP OAM Framework March 2010

OAM domain: A domain, as defined in [11], whose entities are grouped

for the purpose of keeping the OAM confined within that domain.

Note - within the rest of this document the term "domain" is used to

indicate an "OAM domain"

OAM flow: Is the set of all OAM messages originating with a specific

MEP that instrument one direction of a MEG.

OAM information element: An atomic piece of information exchanged

between MEPs in MEG used by an OAM application.

OAM loopback: it is the capability of a node to intercepts some

specific OAM packets and to generate a reply back to their sender.

OAM loopback can work in-service and can support different OAM

functions (e.g., bidirectional on-demand connectivity verification).

OAM Message: One or more OAM information elements that when exchanged

between MEPs or between MEPs and MIPs performs some OAM functionality

(e.g. connectivity verification)

OAM Packet: A packet that carries one or more OAM messages (i.e. OAM

information elements).

Path: See Transport Path

Signal Fail: A condition declared by a MEP when the data forwarding

capability associated with a transport path has failed, e.g. loss of

continuity.

Tandem Connection: A tandem connection is an arbitrary part of a

transport path that can be monitored (via OAM) independent of the

end-to-end monitoring (OAM). The tandem connection may also include

the forwarding engine(s) of the node(s) at the boundaries of the

tandem connection.

This document uses the terms defined in RFC 5654 [11].

This document uses the term ’Per-hop Behavior’ as defined in [14].

3. Functional Components

MPLS-TP defines a profile of the MPLS and PW architectures ([2], [5]

and [7]) that is required to transport service traffic where the

characteristics of information transfer between the transport path

endpoints can be demonstrated to comply with certain performance and

quality guarantees.

Busi et al. Expires September 5, 2010 [Page 8]

Internet-Draft MPLS-TP OAM Framework March 2010

In order to describe the required OAM functionality, this document

introduces a set of high-level functional components.

3.1. Maintenance Entity and Maintenance Entity Group

MPLS-TP OAM operates in the context of Maintenance Entities (MEs)

that are a relationship between two points of a point to point

transport path or a root and a leaf of a point to multipoint

transport path to which maintenance and monitoring operations apply.

These two points are called Maintenance Entity Group (MEG) End Points

(MEPs). In between these two points zero or more intermediate points,

called Maintenance Entity Group Intermediate Points (MIPs), MAY exist

and can be shared by more than one ME in a MEG.

The abstract reference model for an ME with MEPs and MIPs is

described in Figure 1 below:

+-+ +-+ +-+ +-+

|A|----|B|----|C|----|D|

+-+ +-+ +-+ +-+

Figure 1 ME Abstract Reference Model

The instantiation of this abstract model to different MPLS-TP

entities is described in section 4. In this model, nodes A, B, C and

D can be LER/LSR for an LSP or the {S|T}-PEs for a MS-PW. MEPs reside

in nodes A and D while MIPs reside in nodes B and C. The links

connecting adjacent nodes can be physical links, (sub-)layer

LSPs/PSTs, or serving layer paths.

This functional model defines the relationships between all OAM

entities from a maintenance perspective, to allow each Maintenance

Entity to monitor and manage the (sub-)layer network under its

responsibility and to localize problems efficiently.

Another OAM functional component is referred to as Maintenance Entity

Group, which is a collection of one or more MEs that belongs to the

same transport path and that are maintained and monitored as a group.

An MPLS-TP Maintenance Entity Group may be defined to monitor the

transport path for fault and/or performance management.

The MEPs that form an MEG are configured and managed to limit the

scope of an OAM flow within the MEG that the MEPs belong to (i.e.

within the domain of the transport path that is being monitored and

managed). A misbranching fault may cause OAM packets to be delivered

to a MEP that is not in the MEG of origin.

Busi et al. Expires September 5, 2010 [Page 9]

Internet-Draft MPLS-TP OAM Framework March 2010

In case of unidirectional point-to-point transport paths, a single

unidirectional Maintenance Entity is defined to monitor it.

In case of associated bi-directional point-to-point transport paths,

two independent unidirectional Maintenance Entities are defined to

independently monitor each direction. This has implications for

transactions that terminate at or query a MIP as a return path from

MIP to source MEP does not necessarily exist in a unidirectional MEG.

In case of co-routed bi-directional point-to-point transport paths, a

single bidirectional Maintenance Entity is defined to monitor both

directions congruently.

In case of unidirectional point-to-multipoint transport paths, a

single unidirectional Maintenance entity for each leaf is defined to

monitor the transport path from the root to that leaf.

The reference model for the p2mp MEG is represented in Figure 2.

+-+

/--|D|

/ +-+

+-+

/--|C|

+-+ +-+/ +-+\ +-+

|A|----|B| \--|E|

+-+ +-+\ +-+ +-+

\--|F|

+-+

Figure 2 Reference Model for p2mp MEG

In case of p2mp transport paths, the OAM operations are independent

for each ME (A-D, A-E and A-F):

o Fault conditions - some faults may impact more than one ME

depending from where the failure is located;

o Packet loss - packet dropping may impact more than one ME

depending from where the packets are lost;

o Packet delay - will be unique per ME.

Each leaf (i.e. D, E and F) terminates OAM flows to monitor the ME

from itself and the root while the root (i.e. A) generates OAM

Busi et al. Expires September 5, 2010 [Page 10]

剩余45页未读，继续阅读

风尘客09

粉丝: 4
资源: 26

MPLS-TP OAM 框架详解

draft-sprecher-mpls-tp-oam-analysis-02.pdf

draft-ietf-mpls-tp-oam-framework-11.pdf

Technique Analysis of T-MPLS OAM and MPLS-TP OAM

MPLS-TP OAM Communication Based on MPLS-TP Sign Label

ITU-T G.8113.1 mpls-tp oam

华为 NE20E-S V800R011C10 配置指南 - MPLS-TP OAM配置

华为 ME60 V800R011C10 配置指南 - MPLS-TP OAM配置

华为 (信息图) NE系列路由器特性微图 MPLS-TP OAM

华为 NE05E&NE08E V300R003C10SPC500 特性描述 - MPLS-TP OAM

MPLS-TP OAM 要求与功能规范

最新资源