G.8032/Y.1344：互联网协议方面——传输环保护切换标准

5星 · 超过95%的资源需积分: 10 11 浏览量更新于2024-07-24 收藏 1.42MB PDF 举报

《ITU-T G.8032/Y.1344 V3：互联网协议方面—传输以太网环保护切换推荐》这份由国际电信联盟（ITU）发布的G.8032系列标准的最新版本（2012年2月），详细规定了ETH层以太网环形拓扑中的自动保护切换（APS）协议和保护切换机制。它聚焦于以太网环保护的特性，包括网络架构和Ring APS（Ring Protection Switching, 环形保护切换）的具体实现。在G.8032/Y.1344中，推荐的核心内容是针对IP层的以太网传输，旨在确保在数据通信网络中提供高可用性和可靠性。该标准关注的是将数据包通过运输层进行传输时，如何利用以太网技术构建环状网络结构，并通过APS协议来管理网络故障情况下数据的无缝切换。APS协议允许在网络出现链路故障时，能快速并可靠地从主路径切换到备份路径，从而避免服务中断。标准涵盖了全球信息基础设施（Series Y）下的互联网协议相关议题，以及下一代网络的发展方向。对于互联网协议方面的应用，它特别强调了传输以太网环保护的必要性，这对于电信运营商、数据中心和企业网络部署至关重要。通过遵循G.8032/Y.1344，网络管理员可以设计出具备高可用性的网络架构，确保关键业务的连续运行。此外，G.8032标准系列属于传输系统和媒体（Series G）、数字系统和网络部分，与传统模拟信道传输系统（G.100-G.199）和金属线通信系统特性（G.200-G.299）等通用特性有所区别，更侧重于现代数字通信和光纤网络环境中的应用。标准涉及的范围广泛，包括协调无线电电话和线路电话（G.400-G.449）、传输媒体和光学系统的特性（G.450-G.499），以及数字传输技术（G.600-G.699）等。 ITU-T G.8032/Y.1344 V3标准是现代网络设计者和运维人员的重要参考资料，提供了在面临网络故障时保护关键业务连续性的有效策略和方法，对于维护网络的稳定性和高效运行具有重要意义。

10 Rec. ITU-T G.8032/Y.1344 (02/2012)

G.8032-Y.1344(12)_F9-3

Ring

node

ERP

ETH_FF

ERP control

process

RPL owner node

ETH_FF

ETH_C

ERP contro

process

ERP control

process

ETH_FF

ERP

control

ETH_C

Ring

node

ETH_FF

ERP control

process

control

ERP

ETH_C

control

ERP

(

)

Ring node B Ring node D

MEP

MEP MEP

RPL

connection point

(blocked)

RPL neighbour node

control

Figure 9-3 – MEPs in Ethernet ring protection switching architecture

Figure 9-4 represents the model of an Ethernet ring node. MEPs represented on each ring port are

used for monitoring the ring link.

If an MEP detects a defect, which contributes to an SF defect condition, it informs the ERP control

process that a failure condition has been detected. An ERP control function uses the ETH_CI_SSF

information, forwarded from the ETHx/ETH-m_A_Sk, to assert the SF condition of the ring link.

The Ethernet ring protection switching mechanism requires the R-APS protocol to coordinate the

switching behaviour among all Ethernet ring nodes. The R-APS protocol communication is

performed using R-APS messages. R-APS messages are transmitted and received at an ERP control

process. The ETHDi/ETH_A function in [ITU-T G.8021] extracts ETH_CI_RAPS information

from a received R-APS message and sends the ETH_CI_RAPS information to the ERP control

process. A received R-APS message is also forwarded to the ETH_FF. The ETHDi/ETH_A

function also generates R-APS messages using the ETH_CI_RAPS information received from the

ERP control process.

R-APS messages are forwarded using an ETH_FF function for R-APS traffic, represented in

Figure 9-4 as R-APS_FF. Traffic, other than R-APS traffic, is forwarded by use of other ETH_FF

functions, represented in Figure 9-4 as Service_FF. R-APS messages use a dedicated VLAN. Only

one traffic VLAN is depicted in Figure 9-4. More traffic VLANs could be supported using multiple

Service_FFs.

12 Rec. ITU-T G.8032/Y.1344 (02/2012)

b) does not prevent R-APS messages, locally generated at the ERP control process, from being

transmitted over both ring ports;

c) allows R-APS messages received at each ring port to be delivered to the ERP control

process. The ERP control process shall discard all received R-APS messages with a ring ID

that does not match the configured ring ID of the current ERP instance.

Each ERP instance shall only block or unblock its R-APS channel. This is guaranteed by excluding

the connection point from the ETH_FF for the VLAN ID of the R-APS traffic and is equivalent to

performing group address filtering as defined in [IEEE 802.1Q]

On sub-rings without an R-APS virtual channel, the R-APS channel is never blocked on any of its

sub-ring nodes. However, in this case, the R-APS channel is terminated at the interconnection

nodes.

9.6 FDB flush

An FDB flush consists of removing MAC addresses learned on the ring ports of the protected

Ethernet ring from the Ethernet ring node's filtering database.

Each ERP instance may flush only the FDB for the VLAN IDs of the traffic channels of the set of

VLANs it is assigned to protect.

9.7 Ethernet ring protection switching models for interconnection

The Ethernet ring protection switching model for interconnection supports multi-ring/ladder

topologies such as those illustrated in Appendix II.

Figure 9-5 depicts an example of the model on a multi-ring/ladder network defined in this

Recommendation. If the multi-ring/ladder network is in its normal condition, the RPL owner node

of each Ethernet ring blocks the transmission and reception of traffic over the RPL for that Ethernet

ring. Figure 9-5 presents the configuration when no failure is present on any ring link.

In Figure 9-5 there are two interconnected Ethernet rings. Ethernet ring ERP1 is composed of

Ethernet ring nodes A, B, C and D and the ring links between these Ethernet ring nodes. Ethernet

ring ERP2 is composed of Ethernet ring nodes C, D, E and F and the ring links C-to-F, F-to-E, E-to-

D. The ring link between D and C is used for traffic of Ethernet rings ERP1 and ERP2. On their

own ERP2 ring links do not form a closed loop. A closed loop may be formed by the ring links of

ERP2 and the ring link between interconnection nodes that is controlled by ERP1. ERP2 is a sub-

ring. Ethernet ring node A is the RPL owner node for ERP1. Ethernet ring node E is the RPL owner

node for ERP2. These Ethernet ring nodes (A and E) are responsible for blocking the traffic channel

on the RPL for ERP1 and ERP2 respectively. There is no restriction on which ring link on an

Ethernet ring may be set as RPL. For example the RPL of ERP1 could be set as the link between

Ethernet ring nodes C and D.

Ethernet ring nodes C and D that are common to both ERP1 and ERP2, are called the

interconnection nodes. The ring links between the interconnection nodes are controlled and

protected by the Ethernet ring it belongs to. In the example of Figure 9-5, the ring link between

Ethernet ring nodes C and D is part of ERP1 and as such, controlled and protected by ERP1. The

ETH characteristic information (ETH_CI) traffic corresponding to the traffic channel may be

transferred over a common ETH_C function for ERP1 and ERP2 through the interconnection nodes

C and D. Interconnection nodes C and D have separate ERP control processes for each Ethernet

ring.

剩余103页未读，继续阅读

武汉徐哥

粉丝: 0
资源: 2

G.8032/Y.1344：互联网协议方面——传输环保护切换标准

ERPS标准协议英文版_T-REC-G.8032-201202-PDF-E

T-REC-G.988-201606-S!Amd2!PDF-E.pdf

T-REC-G.8032-201508-I!!PDF-E.pdf

T-REC-G.987.3-201010-P!!PDF-E.pdf

T-REC-G.165-199303-I!!PDF-E_ITU-T_rec_g.165_

T-REC-G.169-201105-I!!PDF-E_ITU-T_rec_g.169_

T-REC-G.164-198811-I!!PDF-E_ITU-T_rec_g.164_

T-REC-G.987-201206-I!!PDF-E.pdf

T-REC-G.872-201701-I!!PDF-E.pdf

T-REC-G.988-201010-I!!PDF-E.pdf

最新资源