Transition Networks
S4224 Web User Guide
33558 Rev. C
Page 221 of 669
MEP Functional Configuration
Continuity Check
Continuity Check based on transmitting/receiving CCM PDU can be enabled/disabled. Continuity Check
Messages (CCMs) are ‘heartbeat’ messages exchanged periodically between the MEPs in a service.
Each MEP sends out multicast CCMs, and receives CCMs from all the other MEPs in the service (its
‘peer’ MEPs). This allows each MEP to discover its peer MEPs and to verify that there is connectivity
between them. MIPs also receive CCMs; the MIPs use the discovered information to build a MAC
learning database for use when responding to a Linktrace.
Enable
Continuity Check based on transmitting/receiving CCM PDU can be enabled/disabled. The CCM PDU is
always transmitted as Multi-cast Class 1.
Priority
The priority to be inserted as PCP bits in TAG (if any). In case of enable of Continuity Check and Loss
Measurement both implemented on SW based CCM, 'Priority' must be the same.
Frame rate
Select the frame rate of CCM PDU. The selections are 1 f/sec, 300 f/sec, 10 f/sec, 1 f/sec, 6 f/min, 1
f/min, or 6 f/hour. This is the inverse of transmission period as described in Y.1731. This value has the
following uses:
The transmission rate of the CCM PDU.
Fault Cause cLOC is declared if no CCM PDU has been received within 3.5 periods -
see 'cLOC'.
Fault Cause cPeriod is declared if a CCM PDU has been received with a different period
- see 'cPeriod'.
Selecting 300f/sec or 100f/sec will configure HW based CCM (if possible). Selecting other
frame rates will configure SW based CCM. In case of enable of Continuity Check and Loss
Measurement both implemented on SW based CCM, 'Frame Rate' must be the same.
TLV
Enable/disable TLV insertion in the CCM PDU.
