Setting Up a CFM IEEE 802.3ag Configuration Job

Skylight sensor: control has two libraries that implement CFM.

Possible values are:

• v1 - Select this value if the job will be executed on the sensor: control. The v1 library was included in sensor: control releases before sensor: control 2.4.
• v2 - Select this value if the job will be executed on second generation Skylight sensor: modules. The v2 library is included in sensor: control 2.4 and higher.

• none (-)
• normal
• legacy

• Character String: RFC-2579 display string, except that the character codes 0–31 (decimal) are not used.

The name format must be the same for the other end points.

Possible values: 0–7

Possible values are:

• None: No MHFs can be created.
• Default: Create MHFs if there is no lower active MD level, or if there is a MEP at the next lower active MD level on the component port.
• Explicit: Create MHFs only if there is an MEP at the next lower active MD level on the component port.

The available values are:

• None: The Sender ID TLV is not to be sent.
• Chassis: The Chassis ID Length, Chassis ID subtype, and Chassis ID fields of the Sender ID TLV are to be sent.
• Manage: The Management Address Length and Management Address of the Sender ID TLV are to be sent.
• ChassisManage: The Chassis ID Length, Chassis ID Subtype, Chassis ID, Management Address Length, and Management Address fields are all to be sent.

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:

• Normal: The MEG ID length will have a value equal to the MA/MEG name string length.
• Legacy: The MEG ID length will have a default minimum length field of 13 character.

Default: 1,000 milliseconds

• For Skylight elements, VCEs are optional. They are only required if you wish to define an "up" MEP.
• For sensor: control with v1 library (before sensor: control 2.4), this field is not used.
• For sensor: control with v2 library (for sensor: control 2.4 or higher), this field is required.

Possible values are:

• None: No MHFs can be created.
• Default: Create MHFs if there is no lower active MD level, or if there is a MEP at the next lower active MD level on the port.
• Explicit: Create MHFs only if there is a MEP at the next lower active MD level on the port.
• Defer: Use the Maintenance Domain parameter to determine MHF creation

Possible values are:

• None: The Sender ID TLV is not to be sent.
• Chassis: The Chassis ID Length, Chassis ID subtype, and Chassis ID fields of the Sender ID TLV are to be sent.
• Manage: The Management Address Length and Management Address of the Sender ID TLV are to be sent.
• ChassisManage: The Chassis ID Length, Chassis ID Subtype, Chassis ID, Management Address Length, and Management Address fields are all to be sent.
• Defer: Determined by the domain configuration or system configuration.

Possible values are:

• None: The association is not attached to a VLAN and the contents of the VLAN ID list are ignored.
• C-VLAN: Customer VLAN (typically the inner tag).
• S-VLAN: Service VLAN (typically the outer tag).
• T-VLAN: Tunnel VLAN (either the inner or outer tag).

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.

When this feature is enabled, remote MEPs are automatically added to the MA/MEG as soon as CCM messages are received from remote MEPs.

Maintenance association End Point Identifier (MEPID) for this Maintenance association.

This value is an integer, unique to each MA, that identifies a specific MEP in CCM frames.

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 MA. See VCE name in the MA tab.

Refer to IEEE802.1ag for more information.

• Up: The MEP resides in a bridge that transmits CFM PDUs toward and receives them from, the direction of the Bridge Relay Entity. Up MEP points toward the Bridge Relay Entity.
• Down: The MEP resides in a Bridge that receives CFM PDUs from, and transmits them toward, the direction of the LAN. Down MEP points away the Bridge Relay Entity.

• Checked (Yes): The MEP is to function normally.
• Unchecked (No): The MEP is to cease functioning.

Maintenance association End Point Identifier (MEPID) for this Maintenance association.

This value is an integer, unique to each MA, that identifies a specific MEP in CCM frames.

• Checked (Enabled): The MEP generates CCM messages.
• Unchecked (Disabled): The MEP does not generate CCM messages.

Note: A peer MEP should have the sequence numberenabled to allow a local MEP to perform CCM-based frame loss measurements.

Default value: 7 (highest priority)

Possible values:

• tp-a
• tp-z

See VCE name above in this table.

Note: This parameter is ignored if the port you select has not been set up to perform EVC fault propagation.

If a certain number of consecutive measurements (set in Instant threshold (sample) field) exceeds this value, an alarm is triggered.

Note: The threshold is expressed in milliseconds, but with microsecond granularity. Consequently, values such as 1.001 milliseconds are acceptable.

If a certain number (set by next field value) of consecutive measurements exceeds this value, an alarm is triggered.

Note: The threshold is expressed in milliseconds, but with microsecond granularity. Consequently, values such as 1.001 ms are acceptable.

If a certain number (set by next field value) of consecutive measurements exceeds this value, an alarm is triggered.

Note: The threshold is expressed in milliseconds, but with microsecond granularity. Consequently, values such as 1.001 ms are acceptable.

If a certain number (set by next field value) of consecutive measurements exceeds this value, an alarm is triggered.

Note: The threshold is expressed in milliseconds, but with microsecond granularity. Consequently, values such as 1.001 ms are acceptable.

Range: 1 to 1,440 minutes; default: 15 minutes.