To configure an Ethernet CFM MD policy and subordinate objects

Related information

Many of the forms accessed in this procedure can also be accessed using the Service Topology map. See Working with topology maps for information about working with maps.

Note: You can only perform this procedure when a service exists to associate with the MD policy or subordinate objects.

Steps

This policy defines the MD for Ethernet-based services such as VPLS, Epipe, VPRN, and IES, including SAPs and SDP bindings, for use in Ethernet CFM OAM diagnostic tests.

 
1 

Choose Tools→Ethernet CFM→Maintenance Domain Policies from the NFM-P main menu. The Maintenance Domain Policies form opens.

2 

Click Create or select an existing MD and click Properties. The Maintenance Domain - Global Policy (Create|Edit) form opens.

3 

Configure the general parameters.

4 

Click OK to save the policy and close the form, or click Apply to save the policy. See To release and distribute a policy to distribute the policy to NEs.

Add a Global MEG to an MD
 
5 

To add a Global MEG to an MD:

  1. Click on the Global Maintenance Entity Group tab and click Create. The Global Maintenance Entity Group (Create) form opens with the General tab displayed.

  2. Configure the general parameters.

  3. Configure the Name Format and Name parameters in the Maintenance Entity Group panel.

    If you select icc-based as the Name Format, then the associated Name value must be 8 to 13 characters long.

  4. Configure the parameters in the Initial MEG Configuration panel.

    When you are creating a Global MEG for a 7750 SR-c4, 7750 SR-c12, or 7450 ESS-6, the Initial CCM Interval must be set to 1s.

    For Wavence nodes, the value static is not supported for the Initial MHF-Creation parameter. If static is selected during MEP configuration, then the default value none gets assigned to the node.

    You can only configure the Initial CFM Hold Down Timer (Centiseconds) parameter when the Initial CCM Interval is set to 10 ms or 100 ms.

    When the Initial CCM Interval parameter is set to 10 ms or 100 ms, you cannot configure automatic MEP creation in Step 7 .

    Note:

    When a Global MEG is created and applied, you can open the Global Maintenance Entity Group form at any time and view on the General tab two information fields that display the number of local MEGs and the number of MEPs currently associated with the Global MEG.

  5. Save your changes.

Add a MEG sub-group to a Global MEG
 
6 

To add a MEG sub-group to a Global MEG, perform one of the following:

  1. Add a new MEG sub-group to a Global MEG.

    1. Select a Global MEG and click Properties. The Global Maintenance Entity Group (Edit) form opens with the General tab displayed.

    2. Click on the MEG Sub-Group tab and click Create. The MEG Sub-Group (Create) form opens.

    3. Configure the required parameters.

    4. Save your changes.

  2. Automatically create a new MEG sub-group based on existing remote MEP lists.

    Note: You can only create MEG sub-groups using this method when a valid remote MEP list exists and the remote MEPs on the list are CCM enabled.

    Perform the following:

    1. Select a Global MEG and click Properties. The Global Maintenance Entity Group (Edit) form opens with the General tab displayed.

    2. Click Discover MEG Sub Groups. If this button is not visible, click More Actions and choose Discover MEG Sub Groups. When remote MEPs on valid lists are CCM enabled, new MEG sub-groups are created from the remote MEP lists. The new MEG sub-groups are listed on the Global Maintenance Entity Group (Edit) form.

    3. Save your changes.

Associate a service with a Global MEG
 
7 

To associate a service with a Global MEG, perform one of the following:

  1. Automatically associate all NEs in a service with a Global MEG.

    1. Select an MD and click Properties. The Maintenance Domain - Global Policy (Edit) form opens.

    2. Click on the Global Maintenance Entity Group tab and click Create. The Global Maintenance Entity Group (Create) form opens with the General tab displayed.

    3. Click on the Service tab and click Create. The Service (Create) form opens.

    4. Select a Service.

    5. Configure the Follow Service Topology Changes parameter, if required.

      Note:

      Enabling this parameter will cause relevant Ethernet OAM objects in the MEG and MEG sub-groups to automatically change in response to topology changes in the service or composite service you selected in 4 . Such changes include the addition or deletion of sites, SDP bindings, and access interfaces. Applicable CFM tests (as specified in a test suite) will also be automatically generated and/or deleted, as required. The specific Ethernet OAM objects that will respond to a service topology change are dependent on the selections you make in 7 below.

    6. Configure the required parameters in the Auto-Creation of MEG(s) panel.

    7. Configure the required parameters in the Auto-Creation of MEP(s) panel.

      Note:

      You cannot configure the MEP(s) Creation on Access Interfaces, MEP(s) Creation on SDP Bindings, or Virtual MEP(s) Creation on VPLS Sites parameters when the Initial CCM Interval parameter in Step 5 is set to 10 ms or 100 ms.

      For 7210 SAS-K NEs, to enable the Primary VLAN Enable parameter, you must enable the Primary VLAN parameter in the system resource profile for the device; see To configure the global system resource profile on a 7210 SAS or 7250 IXR.

    8. Configure the required parameters in the Auto-Creation of MIP(s) panel.

    9. Save your changes.

  2. Associate a single NE on a service with a Global MEG.

    1. Select an MD and click Properties. The Maintenance Domain Global Policy (Edit) form opens.

    2. Click on the Global Maintenance Entity Group tab, select a Global MEG, and click Properties. The Global Maintenance Entity Group (Edit) form opens.

    3. Click on the NE Maintenance Entity Group tab and click Create. The NE Maintenance Entity Group (Create) form opens with the General tab displayed.

    4. Select a site.

    5. Configure the required parameters.

      You can only configure the CFM Hold Down Timer (Centiseconds) parameter when the CCM interval is set to 10 ms or 100 ms.

      You cannot choose the 10 ms and 100 ms options for the CCM interval parameter when the CCM Padding Packet Size(Bytes) parameter is enabled.

      Note:

      Only the parameters that are supported on the selected site are displayed when you open the form.

    6. Click on the Service tab.

      If the selected site supports only the service ID as the key identifier in an NE maintenance group, click on the Service ID tab, then click Create. The MEG Service (Create) form opens.

      If the selected site supports the service name as the key identifier in an NE maintenance group, both the Service ID and Service Name tabs are available. Click on the required tab, then click Create. The MEG Service (Create) form opens.

      On supporting NEs, you can choose either the service ID or the service name as the identifier for the associated service. To change from ID to name, or from name to ID, select the required tab, click Create, and configure the change. The previous configuration is removed, and the updated identifier is used.

    7. Configure the required parameters.

    8. Save your changes.

      Note:

      When an NE Maintenance Entity Group is created and applied, you can open the NE Maintenance Entity Group (Edit) form at any time and view on the General tab an information field that displays the number of MEPs currently associated with the NE Maintenance Entity Group.

Add an Ethernet path to the Global MEG
 
8 

To add an Ethernet path to the Global MEG:

  1. On the Global Maintenance Entity Group (Edit) form, click on the Ethernet Path tab and click Create. The Ethernet Path (Create) form opens.

    Note:

    You must specify an Ethernet tunnel path or Ethernet ring path on this form.

  2. Select an Ethernet tunnel path or an Ethernet Ring Path.

  3. Configure the required parameters.

  4. Save your changes.

Add an NE MEG to the MD
 
9 

To add an NE MEG to the MD:

  1. Click on the NE Maintenance Entity Group tab and click Create. The Maintenance Entity Group (Create) form opens with the General tab displayed.

  2. Select a site for the NE MEG.

  3. Select a Unicast Hub MEP for the NE MEG. The Unicast Hub MEP panel is only displayed when the site you selected in 2 is a 7450 ESS, 7750 SR, or 7950 XRS NE.

    Configuring this parameter allows you to add a unicast MEP to the remote MEPs list. This enables the deployment of a hub-and-spoke topology where multiple MEPs acting as spokes can communicate with one hub MEP. In this scenario, the remote MEP has a MEP Mac Address which is the Operational MAC Address of the Unicast Hub MEP.

    See the MEP ID parameter description for additional information and constraints on configuring a unicast CCM hub.

  4. Configure the required parameters. The following restrictions apply:

    • The VLAN ID parameter is configurable only when the selected NE is an OmniSwitch.

    • The CFM Hold Down Timer (Centiseconds) parameter is only configurable when the CCM interval is set to 10 ms or 100 ms.

    • The 10 ms and 100 ms options of the CCM interval parameter cannot be configured when the CCM Padding Packet Size(Bytes) parameter is enabled.

  5. Click OK.

  6. To associate a template with the NE MEG, select an NE MEG and click Properties. The Maintenance Entity Group (Edit) form opens. Otherwise, go to 8 .

  7. Click on the Templates tab and select an associated template.

  8. Click on the Service tab and click Create. The MEG Service (Create) form opens.

  9. Configure the required parameters.

    On supporting NEs, you can specify a user-defined ID in the Sender ID TLV of LBM and LTM PDUs. To use this option, set the ID-Permission parameter to the chassis option, and perform Procedure To configure the Sender-ID TLV of a CFM PDU for an NE.

  10. Save your changes.

Add a managed MEP to the Global MEG
 
10 

To add a managed MEP to the MEG:

  1. Click on the Managed MEP tab and click Create. The MEP (Create) form opens.

  2. Select a MEG.

  3. Configure the required parameters. The following considerations apply:

    • The Interface Type parameter is configurable when the Type parameter is set to Regular.

    • The Interface Type Port is only available if the MD level is 0.

    • For facility MEPs, the Direction parameter must be set to Down.

  4. Configure the required parameters in the Fault Alarm/Reset Time panel and the CCM panel.

  5. Select a MEG subgroup to associate with the managed MEP.

    Note:

    If a MEG subgroup is not selected, the managed MEP is automatically associated with the default MEG subgroup.

  6. Configure the required parameters in the Test Generation Options panel.

    Note:

    The Role, Use as Test Source, and Use as Test Target parameters are configurable only when you set the Direction parameter to Up.

    You can propagate test generation role settings to all MEPs on a SAP or service site using the Propagate to MEPs button on the ETH-CFM tab of the Access Interface (Edit) and Site (Edit) forms.

  7. If the Type parameter you configured in 3 is set to Virtual, go to 12 .

  8. If the Interface Type parameter you configured in 3 is set to LAG or Port, configure the Facility Fault Notify parameter.

  9. If the Interface Type parameter you configured in 3 is set to LAG, configure the Facility VLAN ID.

    Note:

    If you are configuring a tunnel facility MEP, the Facility VLAN ID parameter value must match the outer encapsulation value of the SAP to which you are connecting the tunnel facility MEP.

  10. In the bottommost panel, select an object of the type specified by the Interface Type parameter you configured in 3 . The Select object_type form opens.

  11. Go to 13 .

  12. Select a service site for the virtual MEP in the Service Site panel.

  13. If the MD for the MEP has a Name Type of none and its Maintenance Association has a Name Format of icc-based, the Y.1731 Tests and AIS tabs are configurable. Otherwise, go to 15 .

  14. Click on the Y.1731 TEST tab and AIS tab and configure the required parameters.

  15. Click on the ETH-CSF tab and configure the required parameters.

    The CSF Rx Multiplier parameter is configurable when the Enable Client Signal Fault parameter is enabled.

    Note:

    ETH-CSF acts as one of the triggers for fault propagation on the receiving MEP, when the Fault Propagation parameter is enabled in 4 .

    When the CSF Rx Multiplier is 0 (meaning that CSF will never timeout) and you need to manually clear the CSF state, you must first disable and then re-enable the Enable Client Signal Fault parameter. Otherwise, CSF must receive a C-DCI flag in a PDU to clear the state automatically, whenever the multiplier is 0.

    If the CSF Rx Frame State read-only indicator displays anything other Client Defect Clear Indication, then a fault exists.

11 

Save your changes.

Add a remote MEP to the MEG
 
12 

Add a remote MEP to the MEG.

Note: When you execute a CCM test or synchronize the managed and unmanaged remote MEP lists, the NFM-P automatically distributes the local MEP and the remote MEP to the remote MEP list, except for 7705 SAR NEs, which are excluded from automatic MEP -distribution.

If you enabled the Enable Auto Remote MEP Discovery parameter in Step 7 b , the auto-discovered remote MEPs will populate this list when CCM is running on the network. You can clear the list of auto-discovered MEPs if required, by clicking on Clear Auto Discovered Remote MEPS.

When you execute a CCM test or synchronize the managed and unmanaged remote MEP lists within a MEG sub-group, the NFM-P automatically distributes the local MEP and the remote MEP within that MEG sub-group.

If the remote MEP you are adding is to act as a Unicast Hub MEP, the remote MEP’s MEP Mac Address will become the Operational MAC Address of the Unicast Hub MEP. If you subsequently delete the remote MEP, the Operational MAC Address of the configured Unicast Hub MEP will also be cleared.

You can add only one entry to the remote MEP list for a 7705 SAR.

If a local MEP and the corresponding remote MEP are on the same OmniSwitch, deleting the remote MEP results also deletes the corresponding local MEP.

Perform the following:

  1. Click on the Remote MEP tab. The Remote MEP (Create) form opens.

  2. Configure the required parameters.

    See the MEP ID parameter description for additional information and constraints when configuring a remote MEP to act as a unicast CCM hub.

  3. Save your changes.

  4. You can also convert an existing remote MEP on this list that was previously automatically discovered to a static remote MEP by clicking the entry’s Auto Discovered Remote Mep checkbox. The Remote MEP (Edit) form for that entry opens with the General tab displayed.

  5. Disable the Auto Discovered Remote Mep checkbox and click OK. The Remote MEP (Edit) form closes.

13 

Save your changes.

Add an unmanaged remote MEP to the Global MEG
 
14 

To add an unmanaged remote MEP to the Global MEG:

  1. Click on the Unmanaged Remote MEP tab and click Create. The Unmanaged Remote MEP (Create) form opens.

  2. Configure the required parameters.

  3. Select a MEG Sub-Group to associate the unmanaged remote MEP.

    Note:

    If a MEG sub-group is not selected, the unmanaged remote MEP is automatically associated with the default MEG subgroup.

    The outline color of a MEP icon indicates the MEG subgroup to which the MEP belongs.

  4. Configure the required parameters in the Test Generation Options panel. The following considerations apply:

    • The Role, Use as Test Source, and Use as Test Target parameters are configurable only when you set the Direction parameter to Up.

    • You can only configure Test Generation Options when the unmanaged MEP has a MAC address.

    • You can propagate test generation role settings to all MEPs on a SAP or service site using the Propagate to MEPs button on the ETH-CFM tab of the Access Interface and Site (Edit) forms.

  5. Save your changes.

15 

Click Synchronize Remote MEPs to distribute the MEPs to the NEs, if required.

Note: If the managed MEP or unmanaged remote MEP belongs to a MEG sub-group, the remote MEP synchronization will only occur within the MEG sub-group.

16 

Click Resync Remote MEP DB to re-synchronize the Remote MEPs database, if required.

Optionally, you can also view the DB state of any Remote MEP under a Managed MEP. Otherwise, go to Step 17 .

  1. Click on the Managed MEP tab in the Global MEG form, select a Managed MEP, and click Properties. The MEP (Edit) form opens.

  2. Click on the Remote MEP DB State tab, select a Remote MEP, and click Properties. The Remote MEP DB State (View) form opens, with the General tab displayed.

    The presented information includes:

    • MEP ID

    • Remote State

    • Grace Period RX

    • MAC Address

    • Rdi

    • Port Status

    • Interface Status

    • Last CCM

17 

Click the Audit Unicast CCM item in the More Actions menu to automatically populate all the Hub pointers, if required.

Note: For discovered networks with CCM and a remote MEP list configured, Nokia highly recommends the use of this button to set up a correct HUB-spoke topology in NFM-P before executing a CCM test.

The Audit Unicast CCM action will use the remote lists from all NEs to automatically set the Hub MEP pointers to the appropriate MEPs. If an appropriate MEP is not found, an unmanaged MEP with MEP ID and MEP MAC Address matching the unicast remote MEP entry will be created. The Hub MEP pointer is then set to this unmanaged MEP.

If duplicate managed and unmanaged MEPs are detected, the unmanaged MEP is deleted and the managed MEP is used as the unicast Hub MEP. This action also ensures that the Hub MEP is in the same sub-group as the spoke pointing to it.

18 

Save your changes and close the forms.

End of steps