ERPS protocol packets are called Ring Auto Protection Switching (RAPS) Protocol Data Units (PDUs), which are transmitted in ERPS rings to convey ERPS ring information. Figure 1 shows the RAPS PDU format.
Table 1 describes the fields in an RAPS PDU.
Field |
Length |
Description |
---|---|---|
MEL |
3 bits |
Identifies the maintenance entity group (MEG) level of the RAPS PDU. |
Version |
5 bits |
|
OpCode |
8 bits |
Indicates an RAPS PDU. The value of this field is 0x28. |
Flags |
8 bits |
Is ignored upon RAPS PDU receiving. The value of this field is 0x00. |
TLV Offset |
8 bits |
Indicates that the TLV starts after an offset of 32 bytes. The value of this field is 0x20. |
R-APS Specific Information |
32x8 bits |
Is the core field in an RAPS PDU and carries ERPS ring information. There are differences between sub-fields in ERPSv1 and ERPSv2. Figure 2 shows the R-APS Specific Information field format in ERPSv1. Figure 3 shows the R-APS Specific Information field format in ERPSv2. |
TLV |
Not limited |
Describes information to be loaded. The end TLV value is 0x00. |
Table 2 describes sub-fields in the R-APS Specific Information field.
Sub-Field |
Length |
Description |
---|---|---|
Request/State |
4 bits |
Indicates that this RAPS PDU is a request or state PDU. The value can be:
|
Reserved 1 |
4 bits |
Reserved 1 is used in ERPSv1 for message reply or protection identifier. Sub-code is used in
ERPSv2. The value depends on the Request/State field value:
|
Sub-code |
||
Status |
8 bits |
Includes the following status information:
|
Node ID |
6 x 8 bits |
Identifies the MAC address of a node in an ERPS ring. It is informational and does not affect protection switching in the ERPS ring. |
Reserved 2 |
24 x 8 bits |
Is reserved and ignored upon RAPS PDU receiving. The value is all 0 during RAPS PDU transmission. |