User’s Manual
peer MEP.
• cRDI
Fault Cause indicating that a CCM is received with Remote Defect Indication -
from this peer MEP.
• cPeriod
Fault Cause indicating that a CCM is received with a period different what is
configured for this MEP - from this peer MEP.
• cPriority
Fault Cause indicating that a CCM is received with a priority different what is
configured for this MEP - from this peer MEP.
Buttons
: Click to add a new peer MEP.
Functional Configuration
Continuity Check:
Object Description
• 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' has to be the same.
• Frame rate
Selecting the frame rate of CCM PDU. 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 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' has to be the same.
To Next Page
Loading...
Need help?
General
