Related Documentation
- ACX, MX Series
- connection-protection-tlv
- ACX, M, MX, PTX, T Series
- IEEE 802.1ag OAM Connectivity Fault Management Overview
- ACX, M, MX, T Series
- Creating the Maintenance Domain
- Configuring Maintenance Intermediate Points
- Creating a Maintenance Association
- Continuity Check Protocol
- Configuring a Maintenance Endpoint
- Configuring a Connectivity Fault Management Action Profile
- Configuring Linktrace Protocol in CFM
- Configuring Ethernet Local Management Interface
- Configuring Port Status TLV and Interface Status TLV
- Configuring Rate Limiting of Ethernet OAM Messages
- Configuring 802.1ag Ethernet OAM for VPLS
- M, MX, T Series
- Configuring M120 and MX Series Routers for CCC Encapsulated Packets
- Additional Information
- Ethernet Interfaces
Configuring MAC Flush Message Processing in CET Mode
In carrier Ethernet transport (CET) mode, MX Series routers are used as provider edge (PE) routers, and Nokia Siemens Networks A2200 Carrier Ethernet Switches (referred to as E-domain devices) that run standard-based protocols are used in the access side. On the MX Series routers, VPLS pseudowires are configured dynamically through label distribution protocol (LDP). On the E-domain devices, topology changes are detected through connectivity fault management (CFM) sessions running between the E-domain devices and the MX Series PE routers. The MX Series PE routers can bring the carrier Ethernet interface down if there is CFM connectivity loss. This triggers a local MAC flush as well as a targeted label distribution protocol (T-LDP) MAC flush notification that gets sent towards the remote MX Series PEs to trigger MAC flush on them.
In CET inter-op mode, MX Series routers need to interoperate with the Nokia Siemens Networks Ax100 Carrier Ethernet access devices (referred to as A-domain devices) that run legacy protocols. Nokia Siemens Networks A4100 and A8100 devices act as an intermediate between the MX Series PE routers and A-domain devices. These intermediate devices perform interworking function (IWF) procedures so that operations administration management (OAM) sessions can be run between MX Series routers and A-domain devices. There are no VPLS pseudowires between the MX Series PE routers and the Nokia Siemens Networks A4100 and A8100 intermediate devices, so there is no LDP protocol running between the PE routers to send topology change notifications. In order to communicate topology changes, MX Series routers can trigger a MAC flush and propagate it in the core. MX Series routers can use action profiles based upon the connection protection type length value (TLV) event. The action profile brings down the carrier edge logical interface in MX Series PE routers, which will trigger a local MAC flush and also propagate the topology change to the core using LDP notification.
For VPLS there is no end-to-end connectivity monitored. The access rings are independently monitored by running CFM down multiple end points (MEPs) on the working and protection paths for each of the services between the E-domain devices and the MX Series PE routers, and between the A-domain devices and the MX Series PE routers the IWF hosted by the Nokia Siemens Networks A-4100 devices. When there is a connectivity failure on the working path, the Nokia Siemens Networks Ax200 devices perform a switchover to the protection path, triggering a topology change notification (in the form of TLVs carried in CCM) to be sent on the active path.
Figure 1: CET inter-op Dual Homed Topology

Figure 1 describes the dual homed topology on MX Series PE routers connected to the A-domain. When an A-domain device triggers a switchover, it starts switching the service traffic to the new active path. This change is communicated in the HELLO protocol data units (PDUs) sent by that A-domain device on the working and protection paths. When the IWF in A4100 recieves these HELLO PDUs, it converts them to standard CCM messages and also inserts a connection protection TLV. The “Protection-in-use” field of the connection protection TLV is encoded with the currently active path, and is included in the CCM message. CCM messages are received by the MX Series PE routers through the VLAN spoke in A4100. In the above dual homed scenario, one MX Series PE router monitors the working path, and the other MX Series PE router monitors the protection path.
A MAC flush occurs when the CFM session that is monitoring the working path detects that the service traffic has moved to the protection path or when the CFM session that is monitoring the protection path detects that the service traffic has moved to the working path.
Figure 2: CET inter-op Dual Attached Topology

Figure 2 describes the dual attached topology on MX Series PE routers connected to the A-domain. The MAC flush mechanism used in this case is also the same as the one used for the A-domain in the dual homed scenario (Figure 1). However in this case both the CFM sessions are hosted by only one MX Series PE router. When Ax100 in the A-domain detects topology changes, the MX Series PE router receives the connection protection TLV in the CCM message for the working and protection paths with the value of “Protection-in-use” indicating which path is the active one. Based upon the event that is generated for the CFM session, the MX Series PE router will bring down the appropriate interface which will trigger a local MAC flush.
Configuring a Connection Protection TLV Action Profile
An action profile can be configured to perform the interface-down action based on the values of connection-protection-tlv in the received CCM packets.
The following example shows an action profile configuration with explanatory comments added:
Related Documentation
- ACX, MX Series
- connection-protection-tlv
- ACX, M, MX, PTX, T Series
- IEEE 802.1ag OAM Connectivity Fault Management Overview
- ACX, M, MX, T Series
- Creating the Maintenance Domain
- Configuring Maintenance Intermediate Points
- Creating a Maintenance Association
- Continuity Check Protocol
- Configuring a Maintenance Endpoint
- Configuring a Connectivity Fault Management Action Profile
- Configuring Linktrace Protocol in CFM
- Configuring Ethernet Local Management Interface
- Configuring Port Status TLV and Interface Status TLV
- Configuring Rate Limiting of Ethernet OAM Messages
- Configuring 802.1ag Ethernet OAM for VPLS
- M, MX, T Series
- Configuring M120 and MX Series Routers for CCC Encapsulated Packets
- Additional Information
- Ethernet Interfaces
Published: 2013-08-01
Related Documentation
- ACX, MX Series
- connection-protection-tlv
- ACX, M, MX, PTX, T Series
- IEEE 802.1ag OAM Connectivity Fault Management Overview
- ACX, M, MX, T Series
- Creating the Maintenance Domain
- Configuring Maintenance Intermediate Points
- Creating a Maintenance Association
- Continuity Check Protocol
- Configuring a Maintenance Endpoint
- Configuring a Connectivity Fault Management Action Profile
- Configuring Linktrace Protocol in CFM
- Configuring Ethernet Local Management Interface
- Configuring Port Status TLV and Interface Status TLV
- Configuring Rate Limiting of Ethernet OAM Messages
- Configuring 802.1ag Ethernet OAM for VPLS
- M, MX, T Series
- Configuring M120 and MX Series Routers for CCC Encapsulated Packets
- Additional Information
- Ethernet Interfaces