.svg?sv=2022-11-02&spr=https&st=2024-12-22T19%3A25%3A46Z&se=2024-12-22T19%3A35%3A46Z&sr=c&sp=r&sig=9gYA0e%2F0L89lknJAOHcEiQRN8yGrSPGn8Flww7cmu40%3D){kind=logo}
Setting Up a CFM ITU-T Y.1731 Configuration Job
- 19 Sep 2024
- 13 Minutes to read
- Contributors
- Print
- PDF
Setting Up a CFM ITU-T Y.1731 Configuration Job
- Updated on 19 Sep 2024
- 13 Minutes to read
- Contributors
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
You can use a job to configure various CFM ITU-T Y.1731 settings. Configuring a device with a CFM ITU-T Y.1731 job is very similar to configuring a device with a CFM IEEE 802.3ag job.
The only difference when configuring for CFM ITU-T Y.1731, compared to CFM IEEE 802.3ag, is that you configure the Maintenance Entity Group (MEG) instead of the Maintenance Association (MA).
This job can be executed on:
- Provider Connectivity Assurance Sensors
- Second generation Provider Connectivity Assurance Sensor Modules
To set up a CFM ITU-T Y.1731 configuration job
Access the page Commission ▶ Jobs.
Set all common configuration job settings, as described in "Creating Configuration Jobs in GUI Mode" and in "Creating Configuration Jobs Using Data Sets".
Select CFM ITU-T Y.1731 in the left pane. The CFM ITU-T Y.1731 tab is displayed.
CFM ITU-T Y.1731 tab
Complete all fields in the CFM ITU-T Y.1731 tab as required.
For more information on MEG-specific parameters, see the table below this procedure.
For more information on other parameters, see "Setting Up a CFM IEEE 802.3ag Configuration Job".Click Apply, then click Close.
Use the Add
button or Duplicate 
button to add CFM ITU-T Y.1731 settings.
Note: When duplicating a row, always select the row to duplicate before clicking the Duplicate button.Click the Refresh
button to refresh the user interface.
button or Duplicate 
button to add CFM ITU-T Y.1731 settings.
button to refresh the user interface.CFM ITU-T Y.1731 tab (Commission ▶ Jobs)
CFM General
| Parameter | Description |
|---|---|
| Library Version | This parameter is only relevant for jobs that will be executed on Assurance Sensor Control's or on second generation Assurance Sensor Modules connected to a sensor: control. It will be ignored for jobs executed on devices. Assurance Sensor Control has two libraries that implement CFM. Possible values are:
|
| Default String format mode | Drop down menu with default string format mode, possible values are:
|
MEG
| Parameter | Description |
|---|---|
| Name | The name of this Maintenance Association or Maintenance Entity Group. Note: To comply with ICC standards, the MEG name you enter should contain a maximum of 13 characters. The system supports MEG names up to 45 characters in length, however. If the MEG's name exceeds 13 characters, the CCM is generated with a non-compliant MEG ID field. |
| Name Format | The format of the Maintenance Association or Maintenance Entity Group name. Possible values are:
|
| MAID String Format Mode | Indicates the string format mode of the Maintenance Association Identifier (MAID). Note: This field will be visible only if the Maintenance Domain (MD) is set to Y.1731 and the Name Format is set to String. Possible values are:
|
| Level | Maintenance level of the Maintenance Association or Maintenance Entity Group. Possible values: 0-7 |
| MEP-ID List | A comma-separated list of all the MEPs that are associated with this Maintenance Association or Maintenance Entity Group. |
| Interval (ms) | The required time interval between Continuity Check Messages (CCM). Expressed in milliseconds. Default: 1,000 milliseconds |
| VCE name | Name of the VCE that will be used in this Maintenance Entity Group.
|
| MHF Creation | Indicates whether the management entity can create MHFs for VIDs on which no Up MEP is configured. Possible values are:
|
| Sender ID Permission | The information (if any) to be included in the Sender ID TLV transmitted in CCMs, LBMs, LTMs and LTRs. The available values are:
|
MA [Maintenance Association]
| Parameter | Description |
|---|---|
| Name | The name of this Maintenance Association or Maintenance Entity Group |
| MEP-ID List | A comma-separated list of all the MEPs that are associated with this Maintenance Association or Maintenance Entity Group. |
| MAID String Format Mode | Indicates the string format mode of the Maintenance Association Identifier (MAID). Note: This field will be visible only if the Maintenance Domain (MD) is set to Y.1731 and the Name Format is set to String. Possible values are:
|
| Interval (ms) | The required time interval between Continuity Check Messages (CCM). Expressed in milliseconds. Default: 1,000 milliseconds |
| VCE name | Name of the VCE that will be used in this Maintenance Association.
|
| MHF Creation | Indicates whether the management entity can create MHFs for VIDs on which no Up MEP has been configured. Possible values are:
|
| Sender ID Permission | Determines what, if anything, is to be included in the Sender ID TLV transmitted in CCMs, LBMs, LTMs and LTRs. Possible values are:
|
| VLAN Type | The VLAN type associated with this Maintenance Association or Maintenance Entity Group. Possible values are:
|
| VLAN ID List | A list of the VLANs associated with this Maintenance Association or Maintenance Entity Group. If you leave the VLAN ID field empty, the association is not attached to a VLAN and the VLAN type is set to None implicitly. |
| Remote MEP Auto-Discovery | Check this box to enable the Remote MEP Auto-Discovery feature for this Maintenance Association or Maintenance Entity Group. When this feature is enabled, remote MEPs are automatically added to the MA/MEG as soon as CCM messages are received from remote MEPs. |
Flow MEPs
| Parameter | Description |
|---|---|
| Name | The name of the Maintenance association End Point. |
| MEP-ID | Near-end MEP ID. |
| VCE name | A VCE is a Virtual Connection Endpoint. To include a VCE in this configuration job, enter the name of the VCE in this field. This value must be the same as the VCE name used for the MEG. See VCE name in the MEG tab. |
| Device port | The port used by this MEP. |
| Direction | The direction in which the MEP faces on the Bridge port. Refer to IEEE802.1ag for more information.
|
| Active | The administrative state of the MEP:
|
| FE MEP-ID | Far-end MEP ID. |
| CCI | Indicates whether or not the MEP generates CCM messages:
|
| CCM Seq. Number | When enabled, a MEP transmits CCMs with a sequence number that increases by one for each CCM. When disabled, a MEP transmits CCMs with the sequence number set to zero. Note: A peer MEP should have the sequence numberenabled to allow a local MEP to perform CCM-based frame loss measurements. |
| Primary VID | The Primary VLAN ID of the MEP. This is always one of the VLAN IDs assigned to the MEP's MA/MEG. The value 0 indicates that either the Primary VLAN ID is that of the MEP's MA/MEG, or that the MEP's MA/MEG is not associated with a VLAN ID. |
| CCM, LTM, CSF Priority | Priority parameter for CCMs, LTMs and CSFs transmitted by the MEP. The possible values are 0–7, with 7 being the highest value allowed to pass through the Bridge Port for any of this MEP's VLAN IDs. Default value: 7 (highest priority) |
| MEG Name Format | The format of the Maintenance Association or Maintenance Entity Group name. Possible values are:
|
| TP | Termination Point (TP) of the VCE (if a VCE is being included in this job). Possible values:
See VCE name above in this table. |
MEP's Alarm & Fault Propagation
| Parameter | Description |
|---|---|
| Lowest priority defect alarm | Lowest priority defect that is allowed to generate a CFM Fault Alarm. |
| Notif. alarm time | The period of time, expressed in milliseconds, for which defects must be present before a Fault Alarm is issued. |
| Notif. reset time | The period of time, expressed in milliseconds, for which defects must be absent before resetting a Fault Alarm. |
| CSF | Check box to enable this MEP to transmit Ethernet Client Signal Failure (ETH-CSF) to its peer MEP upon the detection of a failure or defect event in the Ethernet client signal. That port should also be set up to perform EVC fault propagation and that MEP must also be enabled for fault propagation for this parameter to take effect. |
| Fault propagation | Check box to enable the use of this MEP's status in fault propagation. |
| Propagate on port | The EVC client port to which the MEP status should be propagated. Note: This parameter is ignored if the port you select has not been set up to perform EVC fault propagation. |
DMM (Delay Measurement Message)
| Parameter | Description |
|---|---|
| DMM Name | The name of the delay measurement instance. |
| Priority | Priority value used in VLAN tags, if present, in the transmitted frame. |
| Enable | Check box to enable sending DMM frames at the specified interval. |
| Sampling Interval (ms) | The time at which this delay measurement instance issues DMM frames. Expressed in milliseconds. |
| Ref. period (s) | Reference period in seconds for the delay measurements. |
DMM One-Way Delay
| Parameter | Description |
|---|---|
| Enable | Check box to enable one-way delay measurement for this DMM instance. |
| Max. allowed value (ms) | Maximum one-way delay in the Ref. period. Expressed in milliseconds. If a certain number of consecutive measurements (set in Instant threshold (sample) field) exceeds this value, an alarm is triggered. |
| Instant threshold (sample) | The number of consecutive measurements exceeding the Maximum Allowed value that triggers a one-way delay alarm for this Reference Period. |
| Avg. threshold (ms) | One-way average delay threshold, expressed in milliseconds, that triggers the average one-way delay alarm for this Reference Period. Note: The threshold is expressed in milliseconds, but with microsecond granularity. Consequently, values such as 1.001 milliseconds are acceptable. |
| Variation | Select to enable One-way delay variation measurements for this DMM instance. |
| Variation max. allowed value (ms) | Maximum one-way delay variation, expressed in milliseconds, to monitor in the Reference Period. If a certain number (set by next field value) of consecutive measurements exceeds this value, an alarm is triggered. |
| Variation instant threshold (sample) | Number of consecutive measurements exceeding the Maximum Allowed Value that triggers a one-way delay variation alarm for this Reference Period. |
| Variation avg. threshold (ms) | One-way average delay variation threshold, expressed in milliseconds, that triggers the average one-way delay variation alarm for this Reference Period. Note: The threshold is expressed in milliseconds, but with microsecond granularity. Consequently, values such as 1.001 ms are acceptable. |
DMM Two-Way Delay
| Parameter | Description |
|---|---|
| Enable | Check box to enable Two-way delay measurement for this DMM instance. |
| Max. allowed value (ms) | Maximum two-way delay, expressed in milliseconds, to monitor in the Reference Period. If a certain number (set by next field value) of consecutive measurements exceeds this value, an alarm is triggered. |
| Instant threshold (sample) | Number of consecutive measurements exceeding the Maximum Allowed Value that triggers a two-way delay alarm for this Reference Period. |
| Avg. threshold (ms) | Two-way average delay threshold, expressed in milliseconds, that triggers the average two-way delay alarm for this Reference Period. Note: The threshold is expressed in milliseconds, but with microsecond granularity. Consequently, values such as 1.001 ms are acceptable. |
| Variation | Indicates whether the Two-way delay variation is computed by this DMM instance. |
| Variation max. allowed value (ms) | Maximum two-way delay variation, expressed in milliseconds, to monitor in the Reference Period. If a certain number (set by next field value) of consecutive measurements exceeds this value, an alarm is triggered. |
| Variation instant threshold (sample) | Specify the number of consecutive measurements exceeding the Maximum Allowed Value that triggers a two-way delay variation alarm for this Reference Period. |
| Variation avg. threshold (ms) | Specify the two-way average delay variation threshold, expressed in milliseconds, that triggers the average two-way delay variation alarm for this Reference Period. Note: The threshold is expressed in milliseconds, but with microsecond granularity. Consequently, values such as 1.001 ms are acceptable. |
Packet Loss
| Parameter | Description |
|---|---|
| Name | The name of the packet loss instance. |
| Enable | Check to enable packet loss measurements. |
| Ref. period (s) | The reference period, expressed in seconds, for the continuity measurements. This value must be at least 10 times the value of the Sampling Period. |
| Threshold | The threshold, expressed as a percentage, at which an Excessive Packet Loss (EPL) alarm is triggered. |
| Threshold-ratio (%) | Specify (as a percentage) the maximum ratio of allowed packets lost before issuing an alarm during the reference period. |
SLM (Synthetic Loss Measurements)
| Parameter | Description |
|---|---|
| Name | The name of the SLM instance. |
| Enable | The state of the SLM instance. When enabled, SLM frames are sent at the specified interval. Disabled by default. |
| Priority | Priority value used in VLAN tags, if present, in the transmitted frame. |
| Interval | The time, expressed in milliseconds, at which this SLM instance issues SLM frames. |
| Ref. period (s) | Reference period, expressed in minutes, for the SLM instance. Range: 1 to 1,440 minutes; default: 15 minutes. |
| Near-end threshold (%) | The frame loss threshold for near-end packet loss, expressed as a percentage. |
| Far-end threshold (%) | The frame loss threshold for far-end packet loss, expressed as a percentage. |
© 2024 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms
For legal information about Accedian Skylight products, please visit: Accedian legal terms and tradmarks
Was this article helpful?