Components of a complete RPR proposal

Size: px

Start display at page:

Download "Components of a complete RPR proposal"

Arlene Wells
5 years ago
Views:

1 OAM in RPR Italo Busi, Alcatel Frederic Thepot, Dynarc Constantinos Bassias, Lantern Jason Fan, Luminous Henry Hsiaw, NEC Wai-Chau Hui, Nortel Robin Olsson, Vitesse

2 Components of a complete RPR proposal Topology Discovery jcf_topo_0x.pdf Protection Switching RPR MAC jal_prot_0x.pdf OAM and Layer Mgmt cb_layer_01.pdf ib_oamp_01.pdf MAC Service Definition Media Access Control Frame Format am_mrm_0x.pdf rs_frame_0x.pdf Transit Path Bandwidth Mgmt. sa_transi_0x.pdf hp_bwmgnt_0x.pdf Bridging PHY interface hp_brcom_01.pdf Ethernet SONET/SDH rb_phys_0x.pdf hp_grs_0x.pdf 2

3 Table of Contents Introduction OAM RPR Ping description RPR Ping messages definition Conclusion 3

4 Introduction

5 Scope of the presentation Define some OAM mechanism that can help operators in fault management of RPR networks Clarify the motivation for an OAM RPR Ping mechanism Describe the OAM RPR Ping mechanism Define the set of messages we need to support this feature 5

6 OAM RPR Ping description

7 OAM Functionality in RPR We need an on-demand in-service troubleshooting mechanism to check reachability, at the MAC level, between two RPR stations on a ring It is triggered on operator requests, through a traditional operator/ne interface (e.g. a CLI or a MIB interface) It requires exchanging only two type of messages This mechanism is very similar to already existing mechanisms for connectionless networks, like the Ping in IP networks Some enhancements are introduced for dual counter rotating ring topologies 7

8 Reference Ring Topology A B Clockwise ringlet Counterclockwise ringlet Problem to be solved check the reachability at the RPR MAC layer between the two stations A and B 8

9 RPR Ping request Ping_Request A B Clockwise ringlet Counterclockwise ringlet Operator asks node A to check reachability of node B Node A sends an RPR Ping Request to node B 9

10 Loopback request options When asking for an RPP Ping, the operator can specify the following options How the RPR ping request OAM RPR frame should be sent: Through the shortest path (selected using the topology discovery information) default On the clockwise ringlet On the counterclockwise ringlet The CoS value to use for the loopback request (the highest priority default) How the addressed station should respond with the RPR ping reply OAM RPR frame Through the shortest path (selected using the topology discovery information) default On the clockwise ringlet On the counterclockwise ringlet 10

11 Loopback reply A Ping_Reply B Clockwise ringlet Counterclockwise ringlet When node B receives the RPR Ping Request, it generates the RPR Ping Reply to node A 11

12 RPR Ping Reply reception When station A receives back the RPR Ping Request within a predefined timeout value it notifies the operator that the ping procedure has succeeded Otherwise, the ping procedure is declared as failed and the operator is notified about this failure 12

13 Loopback Messages Definition

14 OAM RPR Frame Format RPR Header Message type OAM Type Specific Fields Checksum FCS 1 Byte 2 Bytes A OAM RPR control frame format is defined This allows IEEE to easily update OAM functionality Proposed values for the OAM Type are defined in the next slide The format, structure and syntax of the Specific Fields are defined for each OAM frame type The Checksum is the CRC-16 calculated on all the OAM payload (from the OAM Type field) 14

15 OAM Type Proposed Values OAM Type 0x00 0x01 Description RPR Ping Request RPR Ping Reply All the others Reserved for future use All the received RPR OAM frames that are addressed to the station and have a reserved OAM Type must be discarded 15

16 Ping Request OAM RPR Frame RPR Header Message type OAM Type Request Type Identifier Sequence Number Checksum FCS 1 Byte 1 Byte 2 Bytes 2 Bytes 2 Bytes OAM Type 0x00 value is assigned Request Type Signal to the looped station how it has to respond Proposed values are defined in the next slide Identifier and Sequence Number Used to correlated requests with replies. How to use them is left to the implementation. 16

17 Request Type Proposed Values Request Type 0x00 0x01 0x02 0x03 0x04 All the others Description The echoed station replies on the ringlet chosen by the shortest path (via topology discovery) The echoed station replies on the clockwise ringlet The echoed station replies on the counterclockwise ringlet The echoed station replies on the same ringlet it has received the request The echoed station replies on the opposite ringlet it has received the request Reserved for future use All the received RPR OAM loopback request frames that have a reserved Request Type must be discarded 17

18 Ping Reply OAM RPR Frame RPR Header Message type OAM Type Reserved Identifier Sequence Number Checksum FCS 1 Byte 1 Byte 2 Bytes 2 Bytes 2 Bytes OAM Type 0x01 value is assigned Reserved It is set to 0x00 in transmission and ignored in reception Identifier and Sequence Number They are copied from the request message 18

19 Conclusion

20 Conclusions The RPR OAM ping can allow operators to check the reachability, at the MAC level, between two RPR stations on the ring This mechanism is very simple, implying the exchange of only two messages It is very similar to already existing mechanisms, like the IP Ping It adds some particular testing features targeted to a dual counter rotating ring topology (RPR Rings) It is proposed to adopt this mechanism as an OAM functionality for the IEEE RPR MAC Standard 20

OAM Proposal Italo Busi, Alcatel (Presenter) Leon Bruckman, Corrigent (Presenter)

OAM Proposal Italo Busi, Alcatel (Presenter) Leon Bruckman, Corrigent (Presenter) Costantinos Bassias, Lantern Jason Fan, Luminous Henry Hsiaw, NEC Wai-Chau Hui, Nortel Angela Faber, Telcordia Robin Olsson,