Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring CFM on Physical Interfaces

    This example provides an overview to help you effectively configure connectivity fault management (CFM) on a network of Juniper Networks MX Series 3D Universal Edge Routers.

    Requirements

    This example uses the following hardware and software components:

    • Juniper Networks Junos Space OAM Insight Application
    • Juniper Networks MX Series provider edge (PE) routers

    Overview

    Service provider networks are large and complex with a wide user base, and they often involve different operators that must work together to provide end-to-end services to enterprise customers. While enterprise end-customer demands continue to increase, so do the requirements for service provider Ethernet networks, particularly in the areas of availability and mean time to repair. The Operations, Administration, and Maintenance (OAM) addresses these challenges and more, thereby directly impacting the competitiveness of the service provider.

    CFM partitions the service network into various administrative domains. For example, operators, providers, and customers may be part of different administrative domains. Each administrative domain is mapped into one maintenance domain providing enough information to perform its own management, thus avoiding security breaches and making end-to-end monitoring possible. Each maintenance domain is associated with a maintenance domain level from 0 through 7. Level allocation is based on the network hierarchy, where outermost domains are assigned a higher level than the innermost domains. Customer end points have to highest maintenance domain level. In a CFM maintenance domain, each service instance is called a maintenance association. A maintenance association can be thought as a full mesh of maintenance endpoints (MEPs) having similar characteristics. MEPs are active CFM entities generating and responding to CFM protocol messages. There is also a maintenance intermediate point (MIP), which is a CFM entity similar to the MEP, but more passive (MIPs only respond to CFM messages).

    MEPs can be up MEPs or down MEPs. A link can connect a MEP at level 5 to a MEP at level 7. The interface at level 5 is an up MEP (because the other end of the link is at MEP level 7) and the interface at level 7 is a down MEP (because the other end of the link is at MEP level 5).

    In a Metro Ethernet network, CFM is commonly used at two levels:

    • By the service provider to check the connectivity among its provider edge (PE) routers
    • By the customer to check the connectivity among its customer edge (CE) routers

    The major features of CFM are:

    • Fault monitoring using the continuity check protocol. This is a neighbor discovery and health check protocol which discovers and maintains adjacencies at the VLAN or link level.
    • Path discovery and fault verification using the linktrace protocol. Similar to IP traceroute, this protocol maps the path taken to a destination MAC address through one or more bridged networks between the source and destination.
    • Fault isolation using the loopback protocol. Similar to IP ping, this protocol works with the continuity check protocol during troubleshooting.

    The Junos Space OAM Insight application provides capabilities for automated end-to-end network management, monitoring, and troubleshooting. OAM provides a set of functions designed to monitor network operation to detect network faults and measure network performance.

    The OAM Insight application supports service-based CFM provision, and performance measurements of Y.1731 standard frames on the network services. Following are the functionality of the Junos Space OAM Insight application:

    • You can a create a CFM service definition that you can use as a starting point for provisioning OAM Insight services. A CFM service is defined as the collection of maintenance end points (MEP), or maintenance intermediate points (MIP) in one maintenance association. A service definition provides a template upon which services are built. It specifies service attributes that are not specific to a service instance These service definitions are capable of providing the basis for most of the service orders your organization will need to create. The OAM Insight provides a set of predefined service definitions. In case these predefined service definitions are not adequate for all your needs, you can create service definitions of your own
    • You can create a service order using the service definition. A service order is an instance of the service definition that completes the definition for a specific customer’s use. You can specify the domain, MEP and physical interfaces during the creation of service order.
    • You can functional audit the service that you have deployed. A functional audit determines whether a deployed service instance is functioning.

    Topology

    CFM can be used to monitor the physical link between two routers. CFM over physical interface are deployed in the OAM Insight application. In the OAM Insight application, you can attach an action profile and an SLA-iterator profile to the devices. Once the action profiles and the SLA-iterator profiles are provisioned in devices, they can be referenced in the remote MEP setting during the CFM deployment.

    The CFM also supports aggregated Ethernet interfaces. On interfaces configured on Modular Port Concentrators (MPCs) and Modular Interface Cards (MICs) on MX Series routers, CFM is not supported on untagged aggregated Ethernet member links. MPCs and MICs do support CFM on untagged and tagged aggregated Ethernet logical interfaces.

    In the following example, two routers (Router 1 and Router 2) are connected by a point-to-point Gigabit Ethernet link. The link between these two routers is monitored using CFM. This is shown in Figure 1. The single boundary is a “down mep” in CFM terminology.

    Figure 1: Ethernet CFM on Physical Interfaces

    Ethernet CFM on Physical Interfaces

    Configuration

    To configure CFM on the physical interfaces, perform these tasks:

    CLI Quick Configuration

    Note: The configurations in this example are only partial examples of complete and functional router configurations. Do not copy these configurations and use them directly on an actual system.

    Router 1

    Configure the interface and CFM:

    [edit]
    interfaces ge-1/0/1 {unit 0 {family inet;}}
    protocols {oam {ethernet {connectivity-fault-management {maintenance-domain private {level 0;maintenance-association private-ma {continuity-check {interval 1s;}mep 100 {interface ge-1/0/1;direction down;auto-discovery;}}}}}}}

    The configuration on Router 2 mirrors that on Router 1, with the exception of the mep-id.

    Router 2

    Configure the interface and CFM:

    [edit]
    interfaces ge-0/2/5 {unit 0 {family inet;}}
    protocols {oam {ethernet {connectivity-fault-management {maintenance-domain private {level 0;maintenance-association private-ma {continuity-check {interval 1s;}mep 200 {interface ge-0/2/5;direction down;auto-discovery;}}}}}}}

    Choosing or Creating a Service Definition

    Step-by-Step Procedure

    A service definition provides a template upon which services are built. It specifies service attributes that are not specific to a service instance.

    The OAM Insight software ships with standard service definitions. First, we check the standard service definitions to determine whether one already exists that will work.

    To create a service definition:

    1. From the View selector, select Device View.

      The workspaces that are applicable to this view are displayed.

    2. From the Junos Space user interface, click the Build icon on the Connectivity Services Director banner.

      The functionalities that you can configure in this mode are displayed in the task pane.

    3. From the View pane, click the plus sign (+) beside the My Network item in the View pane to expand the tree and select the device node you want for which you want to create the CFM profile.

      The device type selected within the device model tree is highlighted.

    4. From the Tasks pane, select the name of the profile that you want to create. To create a CFM profile for a device, select Profiles > OAM.

      The Manage OAM Profiles page is displayed.

    5. Click the New icon at the top of the page.

      The Select Profile Type dialog box is displayed, listing the types of OAM profiles that you can create for the selected device.

    6. Select the CFM Profile radio button from the Select Profile Type dialog box.

      The General Settings page of the CFM Profile creation wizard is displayed.

    7. Enter the name of the service definition. For this example, enter cfm-sd
    8. In Type, select MEP.
    9. In Domain Name, specify the name as DN1.
    10. In Domain Level, select 0.
    11. Select the Remote MEP check box.
    12. Go to the Connectivity Check Settings section.
    13. In Hold interval, specify the value as 1.
    14. In Message interval, select 1s.
    15. In Loss threshold (PDUs), specify the value as 6.
    16. In MEP ID Selection:, select Auto pick.
    17. In Direction, select down.
    18. In Priority, select 1.
    19. Select the Accept continuity check messages from all remote MEPs check box.
    20. In Domain Level, select 0.
    21. Go to the Remote MEP settings section.
    22. Select the StdDef-ActionProfile action profile.
    23. Click the plus icon to add the table.
    24. In SLA profile, select StdDef-SFL.
    25. In the Data TLV size cell, specify the value as 1300.
    26. In the Iteration Count cell, specify the value as 14590.
    27. In the Priority cell, specify the value as 4.
    28. Click Done to complete the CFM profile or service definition creation. The Manage OAM Profiles page includes the new service definition. You have created a customized Service Definition, but it has not yet been published. Before a service definition can be used in provisioning, it must be published.
    29. To publish the service definition, in the Manage OAM Profiles page, select the service definition; then in the Actions menu, select Publish Service Definition. The Publish Service Definition window appears.
    30. To confirm that you want to publish this service definition, click Publish. In the Manage OAM Profiles page, the symbol in the upper left corner of the service definition thumbnail changes to a check mark, indicating that the status has changed to Published.

      The service definition is now ready for use in provisioning.

    Creating a CFM Service Order

    Step-by-Step Procedure

    Now that you have created a suitable service definition you are ready to create and deploy a service order. To create and deploy a service order:

    1. From the View selector, select Device View.

      The workspaces that are applicable to this view are displayed.

    2. From the Junos Space user interface, click the Deploy icon on the Connectivity Services Director banner.

      The functionalities that you can configure in this mode are displayed in the task pane.

    3. From the View pane, click the plus sign (+) beside the My Network item in the View pane to expand the tree and select the device node you want for which you want to create the LFM profile.

      The device type selected within the device model tree is highlighted.

    4. Select the check box beside a service to launch the Manage Service Orders page in the lower half of the pane. The service orders associated with the selected service are displayed. You can perform different actions, such as validating or discarding configuration.
    5. From the Tasks pane, select OAM > CFM .

      The Manage CFM Services page is displayed. In the top half of the window on the right pane, the Manage CFM Services page presents information on existing services in a table.

    6. Select the New icon at the top of the Manage CFM Services page.

      The Create CFM Service Order page is displayed.

      Note: Select the check box beside a previously created service on the Manage CFM Services page to launch the Manage Service Orders page in the lower half of the pane. The service orders associated with the selected service are displayed. You can perform different actions, such as validating or discarding configuration.

    7. In Service Definition, select cfm-sd.
    8. In Name, specify the name of the service order as cfm-so.
    9. Select the end point devices.
    10. In Hold interval, specify the value as 1.
    11. In Message interval, select 1s.
    12. In Loss threshold (PDUs), specify the value as 6.
    13. In MEP ID Selection:, select Auto pick.
    14. In Direction, select down.
    15. In Priority, select 1.
    16. Select the Accept continuity check messages from all remote MEPs check box.
    17. Click Next to go to the Endpoint Settings window.
    18. To configure the first device (PE1), select a device in the left pane.
    19. In CFM Interface, select ge-1/0/1.
    20. Specify the MEP ID value as 100.
    21. To configure the second device (PE1), select a device in the left pane.
    22. In CFM Interface, select ge-0/2/5.
    23. Specify the MEP value as 200.
    24. Click Done.

      The service order is successfully created.

    25. In the Deployment Options window, select Deploy now.
    26. Click OK to start the deployment.

    Deploying a Service Order

    Step-by-Step Procedure

    To deploy the service order:

    1. From the View selector, select Device View.

      The workspaces that are applicable to this view are displayed.

    2. From the Junos Space user interface, click the Deploy icon on the Connectivity Services Director banner.

      The functionalities that you can configure in this mode are displayed in the task pane.

    3. From the View pane, click the plus sign (+) beside the My Network item in the View pane to expand the tree and select the device node you want for which you want to create the LFM profile.

      The device type selected within the device model tree is highlighted.

    4. Select the check box beside a service to launch the Manage Service Orders page in the lower half of the pane. The service orders associated with the selected service are displayed. You can perform different actions, such as validating or discarding configuration.
    5. From the Tasks pane, select OAM > CFM .

      The top part of the right pane displays the Manage CFM Services page, with the table of services, and the bottom part of the right pane displays the Manage CFM Service Orders page, with the table of service orders.

    6. In the Manage CFM Service Orders page, select the service order that you want to deploy.
    7. Click the Deploy Service Order button at the top of the page.

      The Deploy Service window appears.

    8. To deploy the service immediately, select Deploy now, and click OK.

      To deploy the service at a later time, select Schedule Deploy, and select a date and time for deployment, then click OK. The time field specifies the time kept by the server, but in the time zone of the client.

      After scheduling the service order for deployment, the provisioning software begins validating the service order.

    9. To monitor the progress and status of the deployment, in the Order Information window, click the job ID. The Job Management page shows the status of the job.
    10. When you see in the Job Management window that the deployment is successful, return to the Manage CFM Services page in Deploy mode of Device View.

    Step-by-Step Procedure

    Verification

    Performing a Functional Audit and a Configuration Audit

    Purpose

    Now that your new service is deployed, you should validate its configuration and functional integrity. A functional audit runs operational commands on the device to verify that the service is up or down. A configuration audit verifies whether the configuration that was pushed to the device during deployment is actually on the device.

    Action

    To perform a configuration audit and a functional audit of the service:

    1. From the View selector, select Device View.

      The workspaces that are applicable to this view are displayed.

    2. From the Junos Space user interface, click the Deploy icon on the Connectivity Services Director banner.

      The functionalities that you can configure in this mode are displayed in the task pane.

    3. From the View pane, click the plus sign (+) beside the My Network item in the View pane to expand the tree and select the device node you want for which you want to create the LFM profile.

      The device type selected within the device model tree is highlighted.

    4. Select the check box beside a service to launch the Manage Service Orders page in the lower half of the pane. The service orders associated with the selected service are displayed. You can perform different actions, such as validating or discarding configuration.
    5. From the Tasks pane, select OAM > CFM .

      The top part of the right pane displays the Manage CFM Services page, with the table of services, and the bottom part of the right pane displays the Manage CFM Service Orders page, with the table of service orders.

    6. In the Manage CFM Services page, select the service instance you just deployed.
    7. Open the Actions menu to see the list of available tasks and select Perform Functional Audit.
    8. In the Schedule Functional Audit window, you can choose to perform the audit now or schedule it for later. Select Audit now, then click OK.
    9. In the Order Information window, click OK.
    10. Open the Actions menu to see the list of available tasks and select Perform Configuration Audit.
    11. In the Schedule Configuration Audit window, you can choose to perform the audit now or schedule it for later. Select Audit now, and then click OK.
    12. In the Order Information window, click OK.

      When the audit jobs have finished, success is indicated by an up arrow in the top right corner of the service thumbnail.

    13. To view the functional audit results:
      1. In the Manage CFM Services page, select the cfm-so service instance.
      2. Open the Actions menu and select View Functional Audit Results.
      3. In the Functional Audit Results window, select each device to view the results.
    14. To view the results of the configuration audit:
      1. In the Manage CFM Services page, select the cfm-so service instance.
      2. Open the Actions menu and select View Configuration Audit Results.
      3. In the Configuration Audit Results window, select each device in turn and review the results. This report indicates any part of the service configuration that is missing on the device, or is inconsistent with the Junos Space database.

    Following successful audit, the service is deployed and ready to be used.

    Modified: 2016-03-14