CFM Action Profile

CFM Action Profile to Bring Down a Group of Logical Interfaces Overview

With growing networks, there is a requirement of monitoring a large number of services using CFM. To monitor each service, one session per service logical interface is required. If the services are large in number, this method does not scale as the number of sessions are limited. Instead of one CFM session per service, a single CFM session can monitor multiple services.

Also, there are scenarios where the user-to-network interface (UNI) device needs to be brought down based on sessions on network-to-network Interface (NNI) logical interface. Here, the NNI logical interface refers to core interface and UNI physical interface refers to access interface hosting multiple service logical interfaces. Based on core interface monitoring, you can bring down service logical interfaces associated with access interface.

Figure 1 illustrates a topology where a number of services destined to customer-edge (CE) routers share a single port on a provider-edge (PE) router. Each service uses one logical interface. A set of services or logical interfaces (colored in yellow) are destined to one CE router and a set of services or logical interfaces colored in red are destined to another CE router. To monitor each service, you need dedicated down maintenance association end point (MEP) sessions for each service. You can bring down the service by bringing down the service logical interface whenever the session goes down. However, this approach is not scalable if we have large number of services. Monitoring the CFM session on the physical interface is also not feasible because multiple CE routers might be connected and the services to other CE router could be disrupted. To address this issue of monitoring multiple services with a single session, you can create a CCM action profile to bring down a group of logical interfaces by using a CFM session that is configured on a single logical interface.

Figure 1: Topology of Multiple VLAN Services Sharing a Single Port on PE Router Destined to Multiple CE Routers

You can configure CCM action profiles for the following scenarios:

To bring down a group of logical interfaces all having the same parent port when CCM monitoring session is running on one of the logical interface but on a different parent port.
To bring down a group of logical interfaces when CCM monitoring session is running on one of the logical interfaces, all belonging to the same parent port.
To bring down the port, when the CCM monitoring session is running on one of the logical interfaces of a different parent port.

Benefits of Creating CFM Action Profile to Bring Down a Group of Logical Interfaces

Reduces resource requirement in scaled networks where multiple services need to be monitored.
Avoids the need to create individual MEP sessions for each service in a topology that includes multiple services to be monitored, thereby enhancing the performance and scalability of the network.

Configure a CFM Action Profile to Bring Down a Group of Logical Interfaces

To monitor multiple services or IFLs using CFM session configured on a single logical interface, you can create a CCM action profile to bring down a group of logical interfaces. You need to define an action to bring down the interface group in the action profile. You will then define the interface device name and the number of logical interfaces that have to be brought down. A logical interface is represented by a combination of the interface-device-name and unit-list. The following steps explain the procedure to bring down a group of logical interfaces when the interface-device-name and/or unit-list are specified.

In configuration mode, at the [edit protocols oam ethernet connectivity-fault-management] hierarchy level, specify the name of the action profile and the CFM event(s). You can configure more than one event in the action profile.
For example,
Note:
The action interface-group-down will not be supported with events other than adjacency-loss and RDI. Any other events configured results in a commit error.
In configuration mode, at the [edit protocols oam ethernet connectivity-fault-management action-profile profile-name] hierarchy level, define the action to bring down the interface group.
Note:
The action interface-group-down will not be supported with other interface related actions. Any other actions configured results in a commit error.

At the [edit protocols oam ethernet connectivity-fault-management] hierarchy level, define the maintenance domain. Specify the maintenance-association parameters.

For example,

At the

edit protocols oam ethernet connectivity-fault-management
maintenance-domain md-name maintenance-association ma-name

, define the maintenance association endpoint and the associated parameters.

For example,

If the action-profile has interface-group-down action configured, it is mandatory to configure the interface-group at the RMEP level. In the configuration mode at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain md-name maintenance-association ma-name mep mep-id remote-mep mep-id action-profile profile-name include the interface-group statement to bring down the interface group marked with the action profile as interface-group-down.
For example,
Note:
If the interface-group configuration is not included in the RMEP configuration. The configuration results in commit error.
A logical interface is represented by a combination of the interface-device-name and unit-list. Configure the device interface name and the number of logical interfaces at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain md-name maintenance-association ma-name mep mep-id remote-mep mep-id action-profile profile-name interface-group.
For example,
In this configuration example, the interface ge-0/0/0.0 is brought down.
Note:
- At least one of the interface-group parameters, interface-device-name or unit-list must be configured. If the interface device name is not configured, the MEP interface is considered as the device name and the logical interface on that device is brought down.
- If the unit-list parameter exceeds the recommended limit, a commit error occurs.
- If the interface-device-name is not specified in the interface-group, the logical interface numbers mentioned in unit-list for the physical interface is brought down.
- If the unit-list is not specified in the interface-group, IFLs are brought down for the configured interface.

Verify the configuration using show protocols oam command.

Configure a CFM Action Profile to Specify CFM Actions for CFM Events

You can create a connectivity fault management (CFM) action profile to define event flags and thresholds to be monitored. You can also specify the action to be taken when any of the configured events occur. When the CFM events occur, the router performs the corresponding action based on your specification. You can configure one or more events in the action profile. Alternatively, you can configure an action profile and specify default actions when connectivity to a remote maintenance association endpoint (MEP) fails.

Note:

You cannot configure multiple actions at this time. Only one action can be configured. This limitation affects both the action and clear-action statements.

To configure the CFM action profile:

In configuration mode, at the [edit protocols oam ethernet connectivity-fault-management] hierarchy level, specify the name of the action profile and the CFM event(s). You can configure more than one event in the action profile. Possible events include: interface-status-tlv, port-status-tlv, adjacency-loss, RDI.
Specify the action to be taken by the router when the event occurs. The action is triggered when the event occurs. If you have configured more than one event in the action profile, it is not necessary for all events to occur to trigger the action.
Specify the default action to be taken by the router when connectivity to a remote MEP fails. If no action is configured, no action is taken.
Note:
Associating an action profile with the interface-down action on an up MEP CFM session running over a circuit cross-connect (CCC) interface (l2circuit/l2vpn) is not advisable and can result in a deadlock situation.

ON THIS PAGE

CFM Action Profile