Efp Cli Overview - Cisco CRS Configuration Manual

EFP CLI Overview

• An EFP serves four purposes:
You can perform a variety of operations on the traffic flows when a router is configured with EFPs on various
interfaces. Also, you can bridge or tunnel the traffic by many ways from one or more of the router's ingress
EFPs to one or more egress EFPs. This traffic is a mixture of VLAN IDs, single or double (QinQ) encapsulation,
and ethertypes.
The following figure shows the EFP model.
Figure 1: EFP Model
An EFP subinterface is configured to specify which traffic on ingress is vectored to that EFP. This is done by
specifying a VLAN ID or QinQ tagging to match against on ingress. All traffic on ingress is compared to
each EFP's matching criterion, and processed by that EFP if a match occurs. The processing performed by an
EFP can change VLAN IDs, add or remove VLAN tags, and change ethertypes.
EFP CLI Overview
The following commands are typically used to configure an EFP:
• l2transport command - This command identifies a subinterface (or a physical port or bundle-port parent
• encapsulation command - This command is used to specify matching criteria.
• rewrite command - This command is used to specify the VLAN tag rewrite criteria.
Cisco IOS XR Virtual Private Network Configuration Guide for the Cisco CRS Router, Release 6.1.x
4
source/destination MAC address). Each entry usually contains 0, 1 or 2 VLAN tags. A packet that starts
with the same tags as an entry in the filter is said to match the filter; if the start of the packet does not
correspond to any entry in the filter then the packet does not match the filter.
◦ Identifies all frames that belong to a particular flow on a given interface
◦ Performs ingress and egress Ethernet header manipulations
◦ Adds features to the identified frames
◦ Optionally define how to forward those frames in the data path.
interface) as an EFP.
The Carrier Ethernet Model