Have an account?

  •   Personalized content
  •   Your products and support

Need an account?

Create an account

Cisco ME 2600X Series Ethernet Access Switch Software Configuration Guide

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco ME 2600X Series Ethernet Access Switch Software Configuration Guide

Chapter Title

Ethernet Virtual Circuit

Results

Updated:
November 19, 2017

Chapter: Ethernet Virtual Circuit

Contents

Ethernet Virtual Circuit

This chapter describes Ethernet Virtual Circuit (EVC), EVC types, Ethernet Flow Point (EFP), and bridge domain. This chapter also describes procedures to configure EVC.

This chapter comprise the following topics:

Carrier Ethernet

The Carrier Ethernet uses a high bandwidth Ethernet technology to deliver dedicated connectivity. It provides network connectivity by connecting to the customer site through a private Layer 2 Ethernet circuit. The available interfaces are normally 10Mbps and 100Mbps Fast Ethernet, 1000Mb/s Gigabit Ethernet and 10Gb/s Ethernet.

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Toolkit and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http:/​/​www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

Prerequisites for EVC and EFP

  • The EFP point–to–multipoint service supports rewrite ingress with the symmetric option. It does not support the rewrite egress operation.
  • Only two encapsulations are supported—untagged and default. If default is configured, configuring untagged is not required and vice versa.
  • If encapsulation default is configured on an EFP, no other encapsulation match on a EFP can be configured.
  • Encapsulation range limits—Only up to 4 ranges are allowed for each EFP and only up to 8 VLAN ranges are allowed for each port.

Restrictions for EVC and EFP

The following are the general restrictions for the EVC and EFP features:

  • Different EFPs cannot have encapsulation for the same VLAN ID on a single interface. For example, dot1q 10 and dot1q 1-20 are not supported on a single interface because both include the same VLAN 10.
  • Two different Ethernet types are not supported on a single interface. For example, encapsulations dot1q and dot1ad are not supported on the same interface.
  • Rewrite Push 1 tag operation is not supported for encapsulations with double tag.
  • Rewrite Push 2 tag operation is not supported for encapsulations with single or double tag.
  • Rewrite pop operations are not supported for encapsulations, such as untagged, any, default, and for encapsulations involving VLAN range and list.
  • Translate rewrite operations are not supported for encapsulations, such as untagged, any, default, and for encapsulations involving VLAN range and list.
  • Two EFPs on the same bridge domain and on the same interface is not supported.

Information About Carrier Ethernet

The Carrier Ethernet enables you to run different services over a single connection. Next Generation Networks, VoIP, Storage, and Managed Security are some of the services that can run over a single Carrier Ethernet connection.

The Metro Ethernet Forum (MEF) defines the following five attributes to define an Ethernet as Carrier class:

  • Standardized Services
  • Quality of Service
  • Scalability
  • Service Management
  • Reliability

The Carrier Ethernet can be deployed in many ways:

  • Ethernet over SDH/SONET
  • Ethernet over MPLS
  • Native Ethernet

Note

The Cisco ME 2600X system currently supports Native Ethernet only.

Understanding Ethernet Virtual Circuit

The Ethernet Virtual Circuit (EVC) represents the service offered and is carried through the provider network. Each EVC is configured by its unique name across the provider network.

An EVC is an end–to–end representation of a single instance of a Layer 2 service that a service provider offers. It embodies the different parameters based on which the service is offered. EVC prevents data transfer between sites that are not part of the same EVC.

In simple terms, EVC is the A–Z circuit that enables you to pass customer VLANs from one port on a node to another port on another node in the network.

In the Cisco ME 2600X system, the EVC represents a Carrier Ethernet Service and is an entity that provides end–to–end connection between two or more customer end points.

EVC Attributes

Some of the global EVC attributes are:

  • EVC ID—An unique identifier that identifies the EVC
  • EVC Type—E-TREE
  • List of associated EFPs that belong to an EVC

EVC Features

EVC in Cisco ME 2600X supports the following features:

  • Create, delete, or modify EFPs
  • Add EFPs as members of a bridge domain
  • Map Traffic to EFPs based on:
    • 802.1q VLANS (Single VLAN, list, range)
    • Cisco Q-in-Q VLANS (Single outer and single inner VLAN)
    • Proprietary Q-in-Q VLANS (9100, 9200)
    • 802.1ad Provider Bridges (encapsulation and rewrite)
  • Map VLAN—Push, Pop, Translate Single VLAN tag
  • Support for rewriting single or double VLAN tags
  • Support for grouping VLANs from several UNI to a single EVC
  • Support for Ethernet UNI with dual VLAN tag (Cisco-QinQ or IEEE 802.1ad)
  • Support for 802.1Q VLAN ID translation on the 802.1q tagged traffic on the UNI
  • Support for point–to–multipoint EVC
  • Support for 1:1, 1:2, 2:1, and 2:2 VLAN translation
  • EVC MAC address aging
  • Flex Service Mapping (Advanced VLAN translations).
    • Support for dot1ad and Cisco Q-in-Q etype for S-tag
  • Support for Layer 2 Protocol Tunneling (L2PT) for each port

EVC Types

Cisco ME 2600X supports Point–to–multipoint EVCs (E-LINE services):

Ethernet Virtual Private Line

An Ethernet Virtual Private Line (EVPL) is a point–to–multipoint EVC. EVPL is an EVC that supports communication between two UNIs. In EVPL, multiple EVCs can exist on a port and the port can have multiple EFPs. Each EFP is associated with a different bridge domain. See figure below.

Figure 1. Ethernet Virtual Private Line

Interactions of EVC with Other Features

EVC interacts with the following features.

  • LAG
  • REP
  • Dot1ad and Layer 2 Protocol Tunneling
  • MAC learning and MAC address limiting
  • QoS
  • MVR
  • IGMP Snooping

EVC with LAG

EFPs can be configured on a channel group. The traffic, carried by the EFPs, is load balanced across the member links. Ingress traffic for a single EVC can arrive on any member of the bundle. All egress traffic for an EFP uses only one of the member links. The load balancing is achieved by distributing EFPs between the member links. The EFPs on a channel group are grouped and each group is associated with a member link. In the default load balancing mechanism, there is no control over how the EFPs are distributed together, and sometimes the EFP distribution is not ideal. The manual load balancing mechanism can be alternatively used to control the EFP grouping.

When you configure a physical port as part of a channel group, you cannot configure EVCs under that physical port.

  • The number of LAGs supported is 48.
  • LACP protocol is supported on the LAG.

EVC with REP

EVC supports up to 24 segments. You can configure REP over EVC using the bridge domain at the service instance level. REP is not supported on service instances configured with encapsulation untagged or default type.

REP is not supported for Ethernet Private Line and Ethernet Virtual Private Line services.

EVC with Layer 2 Protocol Tunneling

Cisco ME 2600X supports Layer 2 protocol tunneling only at the interface level. Configurations applied at the interface level are applicable to all the EFPs configured on that interface.

The following port actions are supported in this release:

  • Forward—Forwards the unmodified ingress bridge protocol data units (BPDUs) on the data path.
  • Drop—Drops the ingress BPDUs on the interface.
  • Peer—Punts BPDUs to the local instance of the protocol.
Valid protocols include:
  • Cisco discovery protocol (CDP). For more information, see Cisco Discovery Protocol.
  • Dynamic trunking protocol (DTP). If a port can become a trunk, it may also have the ability to trunk automatically, and in some cases even negotiate what type of trunking to use on the port. DTP provides this ability to negotiate the trunking method with the other device. Default behavior of DTP on interface is 'forward'.
  • Link aggregation control protocol (LACP). For more information, see Link Aggregation Group and Link Aggregation Control Protocol. Default behavior of LACP on interface is 'peer'.
  • Port aggregation protocol (PAgP) aids in the automatic creation of Fast EtherChannel links. PAgP packets are sent between Fast EtherChannel-capable ports in order to negotiate the forming of a channel. Default behavior of PAgP on interface is 'forward'.
  • Spanning tree protocol (STP) is a Layer 2 protocol that runs on bridges and switches. The specification for STP is IEEE 802.1D. The main purpose of STP is to ensure that you do not create loops when you have redundant paths in your network. Loops are deadly to a network. Default behavior of STP on interface is 'forward'.
  • VLAN trunk protocol (VTP) reduces administration in a switched network. When you configure a new VLAN on one VTP server, the VLAN is distributed through all switches in the domain. This reduces the need to configure the same VLAN everywhere. Default behavior of VTP on interface is 'forward'.
  • 802.1X defines 802.1X port-based authentication as a client-server based access control and authentication protocol that restricts unauthorized clients from connecting to a LAN through publicly accessible ports. An authentication server validates each supplicant (client) connected to an authenticator (network access switch) port before making available any services offered by the switch or the LAN. Default behavior of DOT1X on interface is 'forward'.

Note
The pass option, tunnel option, and Layer 2 protocol tunneling at the EFP are not supported in this release.

The following protocols are supported for each port action:

Port Action Supported Protocols
Peer LACP, CDP
Drop STP, VTP, DTP, PAGP, DOT1X, LACP, CDP
Forward STP, VTP, DTP, PAGP, DOT1X, LACP, CDP

The table below lists the default port action for each protocol:

Protocol Default Port Action
CDP Peer
VTP Forward
DTP Forward
STP Forward
PAGP Forward
LACP Peer
DOT1X Forward

See Configuring Layer 2 Protocol Tunneling to configure Layer 2 protocol tunneling.

EVC with MAC Learning and MAC Address Limiting

MAC learning is supported and enabled (by default) only for point–to–multipoint bridge domains. MAC learning can be enabled or disabled for point–to–multipoint bridge domains.

The MAC address limiting for bridge domains provides the capability to control the MAC address learning behavior at the bridge domain level. You can configure an upper limit on the number of MAC addresses that reside in a bridge domain. The remaining MAC addresses are dropped because they are not learned.

The MAC address limiting commands are configured under the bridge domain.

The default MAC address limit on a bridge domain is 32000. The maximum MAC address limit on a bridge domain is 32000.


Note
Both secure and non-secure EFPs cannot coexist in the same bridge domain. If MAC security is enabled on an EFP then it should be enabled on all the EFPs existing in the same bridge domain.

See MAC Learning.

EVC with QoS

See EVCS QoS Support.

EVC with MVR

Multicast VLAN Registration (MVR) is supported only for point–to–multipoint services. Twenty bridge domains can be configured for MVR. The multicast traffic flows from MVR source EFP to multiple MVR receiver EFPs.

See Multicast VLAN Registration.

EVC with IGMP Snooping

Internet Group Management Protocol Snooping (IGMP snooping) is supported only for point–to–multipoint services. IGMP snooping can be enabled only at the bridge domain level. IGMP snooping can be enabled on up to 128 bridge domains.

See IGMP Snooping.

Understanding Ethernet Flow Point

The traffic for the service needs to pass through several switches in the provider network to connect customer sites across the provider network. The instance of a specific EVC service on the physical interface of each network device through which the EVC passes through is called an Ethernet Flow Point (EFP). An EFP is a logical demarcation point of an EVC on an interface. An EFP can be associated with a bridge domain.

In simple terms, an EFP is defined as an end point of an EVC within a node. Because multiple EVCs can pass through one physical interface, the main purpose of an EFP configuration is to recognize the traffic belonging to a specific EVC on that interface and to apply the forwarding behavior and features specific to that EVC.

The EFPs on Cisco ME 2600X can be on all the ports of the Cisco ME 2600X panel.

The possible EFP administrative states are UP and DOWN. This administrative state maps to the EFP administrative state in IOS.

EFP Attributes

The key attributes of an EFP are:

  • Encapsulation string—Defines the classification criteria for an incoming packet.
  • Forwarding operations—Defines the forwarding operation to be applied on frames that belong to this EFP.
  • Ingress rewrite operation—Defines the rewrites to be performed on the frames that belong to this EFP before proceeding with the forwarding operations.

Note

Cisco ME 2600X supports only the Ingress rewrite operation and all the rewrite operations are symmetric in nature.

For a list of supported encapsulation and ingress rewrite operations on point–to–multipoint (P2MP) EVC, see Supported Encapsulation and Rewrite Operations.

Counters

The following counters are supported for EFPs:

  • Ingress packet counts
  • Egress packet counts
  • Ingress bytes
  • Egress bytes

For point–to–multipoint bridge domains, all the counters are enabled by default.

Understanding Bridge Domain

The bridge domain is an Ethernet broadcast domain internal to the device. The bridge domain enables you to decouple the VLAN from the broadcast domain. The bridge domain has one to many mapping with EFPs.

All the EFPs in a node for a specific EVC are grouped using the bridge domain. If EFPs belong to the same bridge domain and have the same bridge domain number, the EFPs receive traffic even if they have different VLAN numbers.

The bridge domain number is local to the node. Different nodes that are part of an EVC can have the same or different bridge domain number. However, the bridge domain number is unique for an EVC within a node.

For EVC, the bridge domain number is from 1 to 16384.

Note

The maximum supported bridge domains at any moment is 4000.

Restriction

The encapsulation and rewrite operations are not allowed if the bridge domain is configured on the EFP. Remove the existing bridge domain from the EFP and then change the encapsulation and rewrite operations.

Supported Bridge Domain

The bridge domain in Cisco ME 2600X can be configured to operate in point–to–multipoint mode only. This bridge domain can be used for Ethernet Private LAN (EPLAN) and Ethernet Virtual Private LAN (EVPLAN).

Cisco ME 2600X supports up to 4000 point–to–multipoint bridge domains.

MAC learning is supported for point–to–multipoint bridge domains.

The point–to–multipoint bridge domain is supported over REP.

Supported Encapsulation and Rewrite Operations

The table below lists the supported encapsulation and rewrite operations for point–to–multipoint (P2MP) EVC and VPLS EFP:


Note

When using encapsulation dot1q <vlan id> exact command, only vlan-type-0x8100 (default) is supported.

Table 1 Supported Encapsulation and Rewrite Operations for P2MP EVC and VPLS EFP
Encapsulation Criterion Ingress Rewrite Action
encapsulation default No rewrite
encapsulation dot1q any No rewrite
encapsulation dot1q range No rewrite
encapsulation dot1q list No rewrite
encapsulation untagged No rewrite
encapsulation dot1q <vlan id> No rewrite
encapsulation dot1q <vlan id> exact No rewrite
encapsulation dot1q range, list exact No rewrite
encapsulation dot1q range exact No rewrite
encapsulation dot1q list exact No rewrite
encapsulation dot1q any second-dot1q <vlan id> No rewrite
encapsulation dot1q range second-dot1q <vlan id> No rewrite
encapsulation dot1q <vlan id> second-dot1q <vlan id> No rewrite
encapsulation dot1q <vlan id> second-dot1q list No rewrite
encapsulation dot1ad any No rewrite
encapsulation dot1ad range No rewrite
encapsulation dot1ad <vlan id> No rewrite
encapsulation dot1ad <vlan id> exact No rewrite
encapsulation dot1ad any dot1q <vlan id> No rewrite
encapsulation dot1ad range dot1q <vlan id> No rewrite
encapsulation dot1ad <vlan id> dot1q <vlan id> No rewrite
encapsulation dot1ad <vlan id> dot1q list No rewrite
encapsulation dot1q any vlan-type <type value> No rewrite
encapsulation dot1q range vlan-type <type value> No rewrite
encapsulation dot1q <vlan id> vlan-type <type value> No rewrite
encapsulation dot1q <vlan id> vlan-type <type value> exact No rewrite
encapsulation dot1q any vlan-type <type value> dot1q <vlan id> No rewrite
encapsulation dot1q range vlan-type <type value> dot1q <vlan id> No rewrite
encapsulation dot1q <vlan id> vlan-type <type value> dot1q <vlan id> No rewrite
encapsulation dot1q <vlan id> vlan-type <type value> dot1q list No rewrite
encapsulation default rewrite ingress tag push dot1q <vlan id> symmetric
encapsulation dot1q any rewrite ingress tag push dot1q <vlan id> symmetric
encapsulation dot1q range rewrite ingress tag push dot1q <vlan id> symmetric
encapsulation dot1q list rewrite ingress tag push dot1q <vlan id> symmetric
encapsulation untagged rewrite ingress tag push dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> rewrite ingress tag push dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> exact rewrite ingress tag push dot1q <vlan id> symmetric
encapsulation dot1q range, list exact rewrite ingress tag push dot1q <vlan id> symmetric
encapsulation dot1q range exact rewrite ingress tag push dot1q <vlan id> symmetric
encapsulation dot1q list exact rewrite ingress tag push dot1q <vlan id> symmetric
encapsulation default rewrite ingress tag push dot1ad <vlan id> symmetric
encapsulation dot1q any rewrite ingress tag push dot1ad <vlan id> symmetric
encapsulation dot1q range rewrite ingress tag push dot1ad <vlan id> symmetric
encapsulation dot1q list rewrite ingress tag push dot1ad <vlan id> symmetric
encapsulation untagged rewrite ingress tag push dot1ad <vlan id> symmetric
encapsulation dot1q <vlan id> rewrite ingress tag push dot1ad <vlan id> symmetric
encapsulation dot1q <vlan id> exact rewrite ingress tag push dot1ad <vlan id> symmetric
encapsulation dot1q range, list exact rewrite ingress tag push dot1ad <vlan id> symmetric
encapsulation dot1q range exact rewrite ingress tag push dot1ad <vlan id> symmetric
encapsulation dot1q list exact rewrite ingress tag push dot1ad <vlan id> symmetric
encapsulation default rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
encapsulation dot1q any rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
encapsulation dot1q range rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
encapsulation dot1q list rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
encapsulation untagged rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
encapsulation untagged, dot1q range, list rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
encapsulation dot1q <vlan id> rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
encapsulation dot1q <vlan id> exact rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
encapsulation dot1q range, list exact rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
encapsulation dot1q range exact rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
encapsulation dot1q list exact rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
encapsulation untagged rewrite ingress tag push dot1q <vlan id> second-dot1q <vlan id> symmetric
encapsulation untagged rewrite ingress tag push dot1ad <vlan id> dot1q <vlan id> symmetric
encapsulation untagged rewrite ingress tag push dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> exact rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
encapsulation dot1ad <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
encapsulation dot1ad <vlan id> exact rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
encapsulation dot1q <vlan id> exact rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
encapsulation dot1ad <vlan id> rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
encapsulation dot1ad <vlan id> exact rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
encapsulation dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
encapsulation dot1q <vlan id> exact rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
encapsulation dot1ad <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
encapsulation dot1ad <vlan id> exact rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
encapsulation dot1q <vlan id> rewrite ingress tag translate 1-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> exact rewrite ingress tag translate 1-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
encapsulation dot1ad <vlan id> rewrite ingress tag translate 1-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
encapsulation dot1ad <vlan id> exact rewrite ingress tag translate 1-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag translate 1-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> rewrite ingress tag translate 1-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> exact rewrite ingress tag translate 1-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
encapsulation dot1ad <vlan id> rewrite ingress tag translate 1-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
encapsulation dot1ad <vlan id> exact rewrite ingress tag translate 1-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag translate 1-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> rewrite ingress tag translate 1-to-2 dot1q <vlan id> vlan-type <type-value> second-dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> exact rewrite ingress tag translate 1-to-2 dot1q <vlan id> vlan-type <type-value> second-dot1q <vlan id> symmetric
encapsulation dot1ad <vlan id> rewrite ingress tag translate 1-to-2 dot1q <vlan id> vlan-type <type-value> second-dot1q <vlan id> symmetric
encapsulation dot1ad <vlan id> exact rewrite ingress tag translate 1-to-2 dot1q <vlan id> vlan-type <type-value> second-dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-2 dot1q <vlan id> vlan-type <type-value> second-dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag translate 1-to-2 dot1q <vlan id> vlan-type <type-value> second-dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1q <vlan id> symmetric
encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 2-to-1 dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1ad <vlan id> symmetric
encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1ad <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1ad <vlan id> symmetric
encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1q <vlan id> vlan-type <type value> symmetric
encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1q <vlan id> vlan-type <type value> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1q <vlan id> vlan-type <type value> symmetric
encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> symmetric
encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> symmetric
encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag pop 2 symmetric
encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag pop 2 symmetric
encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag pop 2 symmetric
encapsulation dot1q <vlan id> rewrite ingress tag pop 1 symmetric
encapsulation dot1q <vlan id> exact rewrite ingress tag pop 1 symmetric
encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag pop 1 symmetric
encapsulation dot1ad <vlan id> rewrite ingress tag pop 1 symmetric
encapsulation dot1ad <vlan id> exact rewrite ingress tag pop 1 symmetric
encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag pop 1 symmetric
encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag pop 1 symmetric
encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag pop 1 symmetric
encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag pop 1 symmetric

How to Configure EVC

The following tasks describe how to configure EVC on the Cisco ME 2600X device:

Configuring an Ethernet Service Instance

To configure an EVC service instance under the point–to–multipoint bridge domain, complete the following steps:

Prerequisite

Manually Booting from a Cisco IOS Software Image

SUMMARY STEPS

    1.    enable

    2.    configure terminal

    3.    interface ethernet evc [evc-id]

    4.    interface type number

    5.    service instance id ethernet [evc-id]

    6.    encapsulation dot1q {any | vlan-id [vlan-id [-vlan-id]]} second-dot1q {any | vlan-id [vlan-id [-vlan-id]]}

    7.    rewrite ingress tag {push {dot1q vlan-id | dot1q vlan-id second-dot1q vlan-id | dot1ad vlan-id dot1q vlan-id} | pop {1 | 2} | translate {1-to-1 {dot1q vlan-id | dot1ad vlan-id}| 2-to-1 dot1q vlan-id | dot1ad vlan-id}| 1-to-2 {dot1q vlan-id second-dot1q vlan-id | dot1ad vlan-id dot1q vlan-id} | 2-to-2 {dot1q vlan-id second-dot1q vlan-id | dot1ad vlan-id dot1q vlan-id}} {symmetric}

    8.    bridge-domain bridge-id [split-horizon ]

    9.    exit


DETAILED STEPS
     Command or ActionPurpose
    Step 1enable


    Example:
    Switch> enable
     

    Enables privileged EXEC mode.

    • Enter your password if prompted.
     
    Step 2configure terminal


    Example:
    Switch# configure terminal
     

    Enters global configuration mode.

     
    Step 3interface ethernet evc [evc-id]


    Example:
    Switch(config)# ethernet evc evc_101
     

    Configures an EVC.

     
    Step 4interface type number


    Example:
    Switch(config)# interface TenGigabitEthernet 0/45
     

    Specifies the interface to configure and enters interface configuration mode.

     
    Step 5service instance id ethernet [evc-id]


    Example:
    Switch(config-if)# service instance 101 ethernet
     

    Configures an Ethernet service instance on an interface and enters service instance configuration mode.

     
    Step 6encapsulation dot1q {any | vlan-id [vlan-id [-vlan-id]]} second-dot1q {any | vlan-id [vlan-id [-vlan-id]]}

    Example:
    Switch(config-if-srv)# encapsulation dot1q 100 second dot1q 200
     

    Defines the matching criteria that maps the ingress dot1q, QinQ, or untagged frames on an interface to the appropriate service instance.

     
    Step 7rewrite ingress tag {push {dot1q vlan-id | dot1q vlan-id second-dot1q vlan-id | dot1ad vlan-id dot1q vlan-id} | pop {1 | 2} | translate {1-to-1 {dot1q vlan-id | dot1ad vlan-id}| 2-to-1 dot1q vlan-id | dot1ad vlan-id}| 1-to-2 {dot1q vlan-id second-dot1q vlan-id | dot1ad vlan-id dot1q vlan-id} | 2-to-2 {dot1q vlan-id second-dot1q vlan-id | dot1ad vlan-id dot1q vlan-id}} {symmetric}

    Example:
    Switch(config-if-srv)# rewrite ingress tag push dot1q 20
     

    Specifies the rewrite operation to be applied on the frame ingress to the service instance.

     
    Step 8bridge-domain bridge-id [split-horizon ]


    Example:
    Switch(config-if-srv)# bridge-domain 12
     

    Binds the Ethernet service instance to a bridge domain instance where bridge-id is the identifier for the bridge domain instance.

    The valid values for bridge-id range from 1 to 4096.

     
    Step 9exit


    Example:
    Switch(config-if-srv)# exit
     

    Exits the service instance configuration mode.

     

    Configuring Layer 2 Protocol Tunneling

    SUMMARY STEPS

      1.    enable

      2.    configure terminal

      3.    interface type slot/port

      4.    l2protocol [drop|forward|peer] [cdp|dot1x|dtp|lacp|pagp|stp|vtp]

      5.    end


    DETAILED STEPS
       Command or ActionPurpose
      Step 1enable


      Example:
      Switch> enable
       

      Enables privileged EXEC mode.

      • Enter your password if prompted.
       
      Step 2configure terminal


      Example:
      Switch# configure terminal
       

      Enters global configuration mode.

       
      Step 3interface type slot/port


      Example:
      Switch(config)# interface TenGigabitEthernet 0/45
       

      Specifies the interface to configure and enters interface configuration mode.

       
      Step 4l2protocol [drop|forward|peer] [cdp|dot1x|dtp|lacp|pagp|stp|vtp]

      Example:
      Switch(config-if)# l2protocol forward cdp
       

      Configures Layer 2 protocol tunneling actions for each interface.

       
      Step 5end


      Example:
      Switch(config-if)# end
       

      Returns to privileged EXEC mode.

       

      Verifying the EVC Configuration

      Use the following show commands to verify the EVC configuration:
      • show ethernet service instance
      • show l2protocol interface

      Ethernet Service Instance

      Use the following command to show the Ethernet service instances:

      Switch# show ethernet service instance
      Identifier  Type      Interface             State     CE-Vlans
150        static     GigabitEthernet0/43      Up                                            
170        static     GigabitEthernet0/44      Up                                            
160        static     TenGigabitEthernet0/48   Up

      Layer 2 Protocol Interface

      Use the following command to show the layer 2 protocol interfaces:

      Switch# show l2protocol interface gigabitEthernet 0/25
      Protocol Drop Counter
-------- -------------
cdp                 0
stp                 0
vtp                 0
dtp                 0
pagp                0
dot1x               0
lldp                0
lacp               41
udld                0

      Configuration Examples for EVC

      Ethernet Service Instance

      The following example shows how to configure an Ethernet service instance:

      Switch> enable
Switch# configure terminal
Switch(config)# ethernet evc evc_101
Switch(config-if)# service instance id ethernet
Switch(config-if)# encapsulation  dot1q 100
Switch(config-if-srv)# rewrite ingress tag push dot1q 20 symmetric
Switch(config-if-srv)# bridge-domain 12
Switch(config-if-srv)# exit

      The following example shows how to configure a rewrite using Cisco IOS commands:

      Switch> enable
Switch# configure terminal
Switch(config)# interface g0/30
Switch(config-if)# no shut
Switch(config-if)# service instance 1 ethernet
Switch(config-if-srv)# encapsulation dot1q 13
Switch(config-if-srv)# bridge-domain 13
Switch(config-if-srv)# exit

      Additional References for EVC

      The following sections provide references related to the EVC feature.

      Related Documents

      Related Topic Document Title

      Standards

      Standard Title

      MIBs

      MIB MIBs link

      None.

      To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

      http:/​/​tools.cisco.com/​ITDIT/​MIBS/​servlet/​index

      RFCs

      RFC Title

      No new or modified RFCs are supported, and support for existing RFCs has not been modified.

      		 —

      Technical Assistance

      Description Link

      The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

      To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

      Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

      		 http:/​/​www.cisco.com/​cisco/​web/​support/​index.html
      Ethernet Virtual Circuit

      Ethernet Virtual Circuit

      This chapter describes Ethernet Virtual Circuit (EVC), EVC types, Ethernet Flow Point (EFP), and bridge domain. This chapter also describes procedures to configure EVC.

      This chapter comprise the following topics:

      Carrier Ethernet

      The Carrier Ethernet uses a high bandwidth Ethernet technology to deliver dedicated connectivity. It provides network connectivity by connecting to the customer site through a private Layer 2 Ethernet circuit. The available interfaces are normally 10Mbps and 100Mbps Fast Ethernet, 1000Mb/s Gigabit Ethernet and 10Gb/s Ethernet.

      Finding Feature Information

      Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Toolkit and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.

      Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http:/​/​www.cisco.com/​go/​cfn. An account on Cisco.com is not required.

      Prerequisites for EVC and EFP

      • The EFP point–to–multipoint service supports rewrite ingress with the symmetric option. It does not support the rewrite egress operation.
      • Only two encapsulations are supported—untagged and default. If default is configured, configuring untagged is not required and vice versa.
      • If encapsulation default is configured on an EFP, no other encapsulation match on a EFP can be configured.
      • Encapsulation range limits—Only up to 4 ranges are allowed for each EFP and only up to 8 VLAN ranges are allowed for each port.

      Restrictions for EVC and EFP

      The following are the general restrictions for the EVC and EFP features:

      • Different EFPs cannot have encapsulation for the same VLAN ID on a single interface. For example, dot1q 10 and dot1q 1-20 are not supported on a single interface because both include the same VLAN 10.
      • Two different Ethernet types are not supported on a single interface. For example, encapsulations dot1q and dot1ad are not supported on the same interface.
      • Rewrite Push 1 tag operation is not supported for encapsulations with double tag.
      • Rewrite Push 2 tag operation is not supported for encapsulations with single or double tag.
      • Rewrite pop operations are not supported for encapsulations, such as untagged, any, default, and for encapsulations involving VLAN range and list.
      • Translate rewrite operations are not supported for encapsulations, such as untagged, any, default, and for encapsulations involving VLAN range and list.
      • Two EFPs on the same bridge domain and on the same interface is not supported.

      Information About Carrier Ethernet

      The Carrier Ethernet enables you to run different services over a single connection. Next Generation Networks, VoIP, Storage, and Managed Security are some of the services that can run over a single Carrier Ethernet connection.

      The Metro Ethernet Forum (MEF) defines the following five attributes to define an Ethernet as Carrier class:

      • Standardized Services
      • Quality of Service
      • Scalability
      • Service Management
      • Reliability

      The Carrier Ethernet can be deployed in many ways:

      • Ethernet over SDH/SONET
      • Ethernet over MPLS
      • Native Ethernet

      Note

      The Cisco ME 2600X system currently supports Native Ethernet only.

      Understanding Ethernet Virtual Circuit

      The Ethernet Virtual Circuit (EVC) represents the service offered and is carried through the provider network. Each EVC is configured by its unique name across the provider network.

      An EVC is an end–to–end representation of a single instance of a Layer 2 service that a service provider offers. It embodies the different parameters based on which the service is offered. EVC prevents data transfer between sites that are not part of the same EVC.

      In simple terms, EVC is the A–Z circuit that enables you to pass customer VLANs from one port on a node to another port on another node in the network.

      In the Cisco ME 2600X system, the EVC represents a Carrier Ethernet Service and is an entity that provides end–to–end connection between two or more customer end points.

      EVC Attributes

      Some of the global EVC attributes are:

      • EVC ID—An unique identifier that identifies the EVC
      • EVC Type—E-TREE
      • List of associated EFPs that belong to an EVC

      EVC Features

      EVC in Cisco ME 2600X supports the following features:

      • Create, delete, or modify EFPs
      • Add EFPs as members of a bridge domain
      • Map Traffic to EFPs based on:
        • 802.1q VLANS (Single VLAN, list, range)
        • Cisco Q-in-Q VLANS (Single outer and single inner VLAN)
        • Proprietary Q-in-Q VLANS (9100, 9200)
        • 802.1ad Provider Bridges (encapsulation and rewrite)
      • Map VLAN—Push, Pop, Translate Single VLAN tag
      • Support for rewriting single or double VLAN tags
      • Support for grouping VLANs from several UNI to a single EVC
      • Support for Ethernet UNI with dual VLAN tag (Cisco-QinQ or IEEE 802.1ad)
      • Support for 802.1Q VLAN ID translation on the 802.1q tagged traffic on the UNI
      • Support for point–to–multipoint EVC
      • Support for 1:1, 1:2, 2:1, and 2:2 VLAN translation
      • EVC MAC address aging
      • Flex Service Mapping (Advanced VLAN translations).
        • Support for dot1ad and Cisco Q-in-Q etype for S-tag
      • Support for Layer 2 Protocol Tunneling (L2PT) for each port

      EVC Types

      Cisco ME 2600X supports Point–to–multipoint EVCs (E-LINE services):

      Ethernet Virtual Private Line

      An Ethernet Virtual Private Line (EVPL) is a point–to–multipoint EVC. EVPL is an EVC that supports communication between two UNIs. In EVPL, multiple EVCs can exist on a port and the port can have multiple EFPs. Each EFP is associated with a different bridge domain. See figure below.

      Figure 1. Ethernet Virtual Private Line

      Interactions of EVC with Other Features

      EVC interacts with the following features.

      • LAG
      • REP
      • Dot1ad and Layer 2 Protocol Tunneling
      • MAC learning and MAC address limiting
      • QoS
      • MVR
      • IGMP Snooping

      EVC with LAG

      EFPs can be configured on a channel group. The traffic, carried by the EFPs, is load balanced across the member links. Ingress traffic for a single EVC can arrive on any member of the bundle. All egress traffic for an EFP uses only one of the member links. The load balancing is achieved by distributing EFPs between the member links. The EFPs on a channel group are grouped and each group is associated with a member link. In the default load balancing mechanism, there is no control over how the EFPs are distributed together, and sometimes the EFP distribution is not ideal. The manual load balancing mechanism can be alternatively used to control the EFP grouping.

      When you configure a physical port as part of a channel group, you cannot configure EVCs under that physical port.

      • The number of LAGs supported is 48.
      • LACP protocol is supported on the LAG.

      EVC with REP

      EVC supports up to 24 segments. You can configure REP over EVC using the bridge domain at the service instance level. REP is not supported on service instances configured with encapsulation untagged or default type.

      REP is not supported for Ethernet Private Line and Ethernet Virtual Private Line services.

      EVC with Layer 2 Protocol Tunneling

      Cisco ME 2600X supports Layer 2 protocol tunneling only at the interface level. Configurations applied at the interface level are applicable to all the EFPs configured on that interface.

      The following port actions are supported in this release:

      • Forward—Forwards the unmodified ingress bridge protocol data units (BPDUs) on the data path.
      • Drop—Drops the ingress BPDUs on the interface.
      • Peer—Punts BPDUs to the local instance of the protocol.
      Valid protocols include:
      • Cisco discovery protocol (CDP). For more information, see Cisco Discovery Protocol.
      • Dynamic trunking protocol (DTP). If a port can become a trunk, it may also have the ability to trunk automatically, and in some cases even negotiate what type of trunking to use on the port. DTP provides this ability to negotiate the trunking method with the other device. Default behavior of DTP on interface is 'forward'.
      • Link aggregation control protocol (LACP). For more information, see Link Aggregation Group and Link Aggregation Control Protocol. Default behavior of LACP on interface is 'peer'.
      • Port aggregation protocol (PAgP) aids in the automatic creation of Fast EtherChannel links. PAgP packets are sent between Fast EtherChannel-capable ports in order to negotiate the forming of a channel. Default behavior of PAgP on interface is 'forward'.
      • Spanning tree protocol (STP) is a Layer 2 protocol that runs on bridges and switches. The specification for STP is IEEE 802.1D. The main purpose of STP is to ensure that you do not create loops when you have redundant paths in your network. Loops are deadly to a network. Default behavior of STP on interface is 'forward'.
      • VLAN trunk protocol (VTP) reduces administration in a switched network. When you configure a new VLAN on one VTP server, the VLAN is distributed through all switches in the domain. This reduces the need to configure the same VLAN everywhere. Default behavior of VTP on interface is 'forward'.
      • 802.1X defines 802.1X port-based authentication as a client-server based access control and authentication protocol that restricts unauthorized clients from connecting to a LAN through publicly accessible ports. An authentication server validates each supplicant (client) connected to an authenticator (network access switch) port before making available any services offered by the switch or the LAN. Default behavior of DOT1X on interface is 'forward'.

      Note
      The pass option, tunnel option, and Layer 2 protocol tunneling at the EFP are not supported in this release.

      The following protocols are supported for each port action:

      Port Action Supported Protocols
      Peer LACP, CDP
      Drop STP, VTP, DTP, PAGP, DOT1X, LACP, CDP
      Forward STP, VTP, DTP, PAGP, DOT1X, LACP, CDP

      The table below lists the default port action for each protocol:

      Protocol Default Port Action
      CDP Peer
      VTP Forward
      DTP Forward
      STP Forward
      PAGP Forward
      LACP Peer
      DOT1X Forward

      See Configuring Layer 2 Protocol Tunneling to configure Layer 2 protocol tunneling.

      EVC with MAC Learning and MAC Address Limiting

      MAC learning is supported and enabled (by default) only for point–to–multipoint bridge domains. MAC learning can be enabled or disabled for point–to–multipoint bridge domains.

      The MAC address limiting for bridge domains provides the capability to control the MAC address learning behavior at the bridge domain level. You can configure an upper limit on the number of MAC addresses that reside in a bridge domain. The remaining MAC addresses are dropped because they are not learned.

      The MAC address limiting commands are configured under the bridge domain.

      The default MAC address limit on a bridge domain is 32000. The maximum MAC address limit on a bridge domain is 32000.


      Note
      Both secure and non-secure EFPs cannot coexist in the same bridge domain. If MAC security is enabled on an EFP then it should be enabled on all the EFPs existing in the same bridge domain.

      See MAC Learning.

      EVC with QoS

      See EVCS QoS Support.

      EVC with MVR

      Multicast VLAN Registration (MVR) is supported only for point–to–multipoint services. Twenty bridge domains can be configured for MVR. The multicast traffic flows from MVR source EFP to multiple MVR receiver EFPs.

      See Multicast VLAN Registration.

      EVC with IGMP Snooping

      Internet Group Management Protocol Snooping (IGMP snooping) is supported only for point–to–multipoint services. IGMP snooping can be enabled only at the bridge domain level. IGMP snooping can be enabled on up to 128 bridge domains.

      See IGMP Snooping.

      Understanding Ethernet Flow Point

      The traffic for the service needs to pass through several switches in the provider network to connect customer sites across the provider network. The instance of a specific EVC service on the physical interface of each network device through which the EVC passes through is called an Ethernet Flow Point (EFP). An EFP is a logical demarcation point of an EVC on an interface. An EFP can be associated with a bridge domain.

      In simple terms, an EFP is defined as an end point of an EVC within a node. Because multiple EVCs can pass through one physical interface, the main purpose of an EFP configuration is to recognize the traffic belonging to a specific EVC on that interface and to apply the forwarding behavior and features specific to that EVC.

      The EFPs on Cisco ME 2600X can be on all the ports of the Cisco ME 2600X panel.

      The possible EFP administrative states are UP and DOWN. This administrative state maps to the EFP administrative state in IOS.

      EFP Attributes

      The key attributes of an EFP are:

      • Encapsulation string—Defines the classification criteria for an incoming packet.
      • Forwarding operations—Defines the forwarding operation to be applied on frames that belong to this EFP.
      • Ingress rewrite operation—Defines the rewrites to be performed on the frames that belong to this EFP before proceeding with the forwarding operations.

      Note

      Cisco ME 2600X supports only the Ingress rewrite operation and all the rewrite operations are symmetric in nature.

      For a list of supported encapsulation and ingress rewrite operations on point–to–multipoint (P2MP) EVC, see Supported Encapsulation and Rewrite Operations.

      Counters

      The following counters are supported for EFPs:

      • Ingress packet counts
      • Egress packet counts
      • Ingress bytes
      • Egress bytes

      For point–to–multipoint bridge domains, all the counters are enabled by default.

      Understanding Bridge Domain

      The bridge domain is an Ethernet broadcast domain internal to the device. The bridge domain enables you to decouple the VLAN from the broadcast domain. The bridge domain has one to many mapping with EFPs.

      All the EFPs in a node for a specific EVC are grouped using the bridge domain. If EFPs belong to the same bridge domain and have the same bridge domain number, the EFPs receive traffic even if they have different VLAN numbers.

      The bridge domain number is local to the node. Different nodes that are part of an EVC can have the same or different bridge domain number. However, the bridge domain number is unique for an EVC within a node.

      For EVC, the bridge domain number is from 1 to 16384.

      Note

      The maximum supported bridge domains at any moment is 4000.

      Restriction

      The encapsulation and rewrite operations are not allowed if the bridge domain is configured on the EFP. Remove the existing bridge domain from the EFP and then change the encapsulation and rewrite operations.

      Supported Bridge Domain

      The bridge domain in Cisco ME 2600X can be configured to operate in point–to–multipoint mode only. This bridge domain can be used for Ethernet Private LAN (EPLAN) and Ethernet Virtual Private LAN (EVPLAN).

      Cisco ME 2600X supports up to 4000 point–to–multipoint bridge domains.

      MAC learning is supported for point–to–multipoint bridge domains.

      The point–to–multipoint bridge domain is supported over REP.

      Supported Encapsulation and Rewrite Operations

      The table below lists the supported encapsulation and rewrite operations for point–to–multipoint (P2MP) EVC and VPLS EFP:


      Note

      When using encapsulation dot1q <vlan id> exact command, only vlan-type-0x8100 (default) is supported.

      Table 1 Supported Encapsulation and Rewrite Operations for P2MP EVC and VPLS EFP
      Encapsulation Criterion Ingress Rewrite Action
      encapsulation default No rewrite
      encapsulation dot1q any No rewrite
      encapsulation dot1q range No rewrite
      encapsulation dot1q list No rewrite
      encapsulation untagged No rewrite
      encapsulation dot1q <vlan id> No rewrite
      encapsulation dot1q <vlan id> exact No rewrite
      encapsulation dot1q range, list exact No rewrite
      encapsulation dot1q range exact No rewrite
      encapsulation dot1q list exact No rewrite
      encapsulation dot1q any second-dot1q <vlan id> No rewrite
      encapsulation dot1q range second-dot1q <vlan id> No rewrite
      encapsulation dot1q <vlan id> second-dot1q <vlan id> No rewrite
      encapsulation dot1q <vlan id> second-dot1q list No rewrite
      encapsulation dot1ad any No rewrite
      encapsulation dot1ad range No rewrite
      encapsulation dot1ad <vlan id> No rewrite
      encapsulation dot1ad <vlan id> exact No rewrite
      encapsulation dot1ad any dot1q <vlan id> No rewrite
      encapsulation dot1ad range dot1q <vlan id> No rewrite
      encapsulation dot1ad <vlan id> dot1q <vlan id> No rewrite
      encapsulation dot1ad <vlan id> dot1q list No rewrite
      encapsulation dot1q any vlan-type <type value> No rewrite
      encapsulation dot1q range vlan-type <type value> No rewrite
      encapsulation dot1q <vlan id> vlan-type <type value> No rewrite
      encapsulation dot1q <vlan id> vlan-type <type value> exact No rewrite
      encapsulation dot1q any vlan-type <type value> dot1q <vlan id> No rewrite
      encapsulation dot1q range vlan-type <type value> dot1q <vlan id> No rewrite
      encapsulation dot1q <vlan id> vlan-type <type value> dot1q <vlan id> No rewrite
      encapsulation dot1q <vlan id> vlan-type <type value> dot1q list No rewrite
      encapsulation default rewrite ingress tag push dot1q <vlan id> symmetric
      encapsulation dot1q any rewrite ingress tag push dot1q <vlan id> symmetric
      encapsulation dot1q range rewrite ingress tag push dot1q <vlan id> symmetric
      encapsulation dot1q list rewrite ingress tag push dot1q <vlan id> symmetric
      encapsulation untagged rewrite ingress tag push dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> rewrite ingress tag push dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> exact rewrite ingress tag push dot1q <vlan id> symmetric
      encapsulation dot1q range, list exact rewrite ingress tag push dot1q <vlan id> symmetric
      encapsulation dot1q range exact rewrite ingress tag push dot1q <vlan id> symmetric
      encapsulation dot1q list exact rewrite ingress tag push dot1q <vlan id> symmetric
      encapsulation default rewrite ingress tag push dot1ad <vlan id> symmetric
      encapsulation dot1q any rewrite ingress tag push dot1ad <vlan id> symmetric
      encapsulation dot1q range rewrite ingress tag push dot1ad <vlan id> symmetric
      encapsulation dot1q list rewrite ingress tag push dot1ad <vlan id> symmetric
      encapsulation untagged rewrite ingress tag push dot1ad <vlan id> symmetric
      encapsulation dot1q <vlan id> rewrite ingress tag push dot1ad <vlan id> symmetric
      encapsulation dot1q <vlan id> exact rewrite ingress tag push dot1ad <vlan id> symmetric
      encapsulation dot1q range, list exact rewrite ingress tag push dot1ad <vlan id> symmetric
      encapsulation dot1q range exact rewrite ingress tag push dot1ad <vlan id> symmetric
      encapsulation dot1q list exact rewrite ingress tag push dot1ad <vlan id> symmetric
      encapsulation default rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation dot1q any rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation dot1q range rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation dot1q list rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation untagged rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation untagged, dot1q range, list rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation dot1q <vlan id> rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation dot1q <vlan id> exact rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation dot1q range, list exact rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation dot1q range exact rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation dot1q list exact rewrite ingress tag push dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation untagged rewrite ingress tag push dot1q <vlan id> second-dot1q <vlan id> symmetric
      encapsulation untagged rewrite ingress tag push dot1ad <vlan id> dot1q <vlan id> symmetric
      encapsulation untagged rewrite ingress tag push dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> exact rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
      encapsulation dot1ad <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
      encapsulation dot1ad <vlan id> exact rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
      encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-1 dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
      encapsulation dot1q <vlan id> exact rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
      encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
      encapsulation dot1ad <vlan id> rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
      encapsulation dot1ad <vlan id> exact rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
      encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag translate 1-to-1 dot1ad <vlan id> symmetric
      encapsulation dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
      encapsulation dot1q <vlan id> exact rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
      encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
      encapsulation dot1ad <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
      encapsulation dot1ad <vlan id> exact rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
      encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> dot1q <vlan id> rewrite ingress tag translate 1-to-1 dot1q <vlan id> vlan-type <type-value> symmetric
      encapsulation dot1q <vlan id> rewrite ingress tag translate 1-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> exact rewrite ingress tag translate 1-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
      encapsulation dot1ad <vlan id> rewrite ingress tag translate 1-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
      encapsulation dot1ad <vlan id> exact rewrite ingress tag translate 1-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag translate 1-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> rewrite ingress tag translate 1-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> exact rewrite ingress tag translate 1-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
      encapsulation dot1ad <vlan id> rewrite ingress tag translate 1-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
      encapsulation dot1ad <vlan id> exact rewrite ingress tag translate 1-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag translate 1-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> rewrite ingress tag translate 1-to-2 dot1q <vlan id> vlan-type <type-value> second-dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> exact rewrite ingress tag translate 1-to-2 dot1q <vlan id> vlan-type <type-value> second-dot1q <vlan id> symmetric
      encapsulation dot1ad <vlan id> rewrite ingress tag translate 1-to-2 dot1q <vlan id> vlan-type <type-value> second-dot1q <vlan id> symmetric
      encapsulation dot1ad <vlan id> exact rewrite ingress tag translate 1-to-2 dot1q <vlan id> vlan-type <type-value> second-dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 1-to-2 dot1q <vlan id> vlan-type <type-value> second-dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag translate 1-to-2 dot1q <vlan id> vlan-type <type-value> second-dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1q <vlan id> symmetric
      encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag translate 2-to-1 dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1ad <vlan id> symmetric
      encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1ad <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1ad <vlan id> symmetric
      encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag translate 2-to-1 dot1q <vlan id> vlan-type <type value> symmetric
      encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
      encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1q <vlan id> second-dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
      encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1ad <vlan id> dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> symmetric
      encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag translate 2-to-2 dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> symmetric
      encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag pop 2 symmetric
      encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag pop 2 symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag pop 2 symmetric
      encapsulation dot1q <vlan id> rewrite ingress tag pop 1 symmetric
      encapsulation dot1q <vlan id> exact rewrite ingress tag pop 1 symmetric
      encapsulation dot1q <vlan id> second-dot1q <vlan id> rewrite ingress tag pop 1 symmetric
      encapsulation dot1ad <vlan id> rewrite ingress tag pop 1 symmetric
      encapsulation dot1ad <vlan id> exact rewrite ingress tag pop 1 symmetric
      encapsulation dot1ad <vlan id> dot1q <vlan id> rewrite ingress tag pop 1 symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> rewrite ingress tag pop 1 symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> exact rewrite ingress tag pop 1 symmetric
      encapsulation dot1q <vlan id> vlan-type <type value> second-dot1q <vlan id> rewrite ingress tag pop 1 symmetric

      How to Configure EVC

      The following tasks describe how to configure EVC on the Cisco ME 2600X device:

      Configuring an Ethernet Service Instance

      To configure an EVC service instance under the point–to–multipoint bridge domain, complete the following steps:

      Prerequisite

      Manually Booting from a Cisco IOS Software Image

      SUMMARY STEPS

        1.    enable

        2.    configure terminal

        3.    interface ethernet evc [evc-id]

        4.    interface type number

        5.    service instance id ethernet [evc-id]

        6.    encapsulation dot1q {any | vlan-id [vlan-id [-vlan-id]]} second-dot1q {any | vlan-id [vlan-id [-vlan-id]]}

        7.    rewrite ingress tag {push {dot1q vlan-id | dot1q vlan-id second-dot1q vlan-id | dot1ad vlan-id dot1q vlan-id} | pop {1 | 2} | translate {1-to-1 {dot1q vlan-id | dot1ad vlan-id}| 2-to-1 dot1q vlan-id | dot1ad vlan-id}| 1-to-2 {dot1q vlan-id second-dot1q vlan-id | dot1ad vlan-id dot1q vlan-id} | 2-to-2 {dot1q vlan-id second-dot1q vlan-id | dot1ad vlan-id dot1q vlan-id}} {symmetric}

        8.    bridge-domain bridge-id [split-horizon ]

        9.    exit


      DETAILED STEPS
         Command or ActionPurpose
        Step 1enable


        Example:
        Switch> enable
         

        Enables privileged EXEC mode.

        • Enter your password if prompted.
         
        Step 2configure terminal


        Example:
        Switch# configure terminal
         

        Enters global configuration mode.

         
        Step 3interface ethernet evc [evc-id]


        Example:
        Switch(config)# ethernet evc evc_101
         

        Configures an EVC.

         
        Step 4interface type number


        Example:
        Switch(config)# interface TenGigabitEthernet 0/45
         

        Specifies the interface to configure and enters interface configuration mode.

         
        Step 5service instance id ethernet [evc-id]


        Example:
        Switch(config-if)# service instance 101 ethernet
         

        Configures an Ethernet service instance on an interface and enters service instance configuration mode.

         
        Step 6encapsulation dot1q {any | vlan-id [vlan-id [-vlan-id]]} second-dot1q {any | vlan-id [vlan-id [-vlan-id]]}

        Example:
        Switch(config-if-srv)# encapsulation dot1q 100 second dot1q 200
         

        Defines the matching criteria that maps the ingress dot1q, QinQ, or untagged frames on an interface to the appropriate service instance.

         
        Step 7rewrite ingress tag {push {dot1q vlan-id | dot1q vlan-id second-dot1q vlan-id | dot1ad vlan-id dot1q vlan-id} | pop {1 | 2} | translate {1-to-1 {dot1q vlan-id | dot1ad vlan-id}| 2-to-1 dot1q vlan-id | dot1ad vlan-id}| 1-to-2 {dot1q vlan-id second-dot1q vlan-id | dot1ad vlan-id dot1q vlan-id} | 2-to-2 {dot1q vlan-id second-dot1q vlan-id | dot1ad vlan-id dot1q vlan-id}} {symmetric}

        Example:
        Switch(config-if-srv)# rewrite ingress tag push dot1q 20
         

        Specifies the rewrite operation to be applied on the frame ingress to the service instance.

         
        Step 8bridge-domain bridge-id [split-horizon ]


        Example:
        Switch(config-if-srv)# bridge-domain 12
         

        Binds the Ethernet service instance to a bridge domain instance where bridge-id is the identifier for the bridge domain instance.

        The valid values for bridge-id range from 1 to 4096.

         
        Step 9exit


        Example:
        Switch(config-if-srv)# exit
         

        Exits the service instance configuration mode.

         

        Configuring Layer 2 Protocol Tunneling

        SUMMARY STEPS

          1.    enable

          2.    configure terminal

          3.    interface type slot/port

          4.    l2protocol [drop|forward|peer] [cdp|dot1x|dtp|lacp|pagp|stp|vtp]

          5.    end


        DETAILED STEPS
           Command or ActionPurpose
          Step 1enable


          Example:
          Switch> enable
           

          Enables privileged EXEC mode.

          • Enter your password if prompted.
           
          Step 2configure terminal


          Example:
          Switch# configure terminal
           

          Enters global configuration mode.

           
          Step 3interface type slot/port


          Example:
          Switch(config)# interface TenGigabitEthernet 0/45
           

          Specifies the interface to configure and enters interface configuration mode.

           
          Step 4l2protocol [drop|forward|peer] [cdp|dot1x|dtp|lacp|pagp|stp|vtp]

          Example:
          Switch(config-if)# l2protocol forward cdp
           

          Configures Layer 2 protocol tunneling actions for each interface.

           
          Step 5end


          Example:
          Switch(config-if)# end
           

          Returns to privileged EXEC mode.

           

          Verifying the EVC Configuration

          Use the following show commands to verify the EVC configuration:
          • show ethernet service instance
          • show l2protocol interface

          Ethernet Service Instance

          Use the following command to show the Ethernet service instances:

          Switch# show ethernet service instance
          Identifier  Type      Interface             State     CE-Vlans
150        static     GigabitEthernet0/43      Up                                            
170        static     GigabitEthernet0/44      Up                                            
160        static     TenGigabitEthernet0/48   Up

          Layer 2 Protocol Interface

          Use the following command to show the layer 2 protocol interfaces:

          Switch# show l2protocol interface gigabitEthernet 0/25
          Protocol Drop Counter
-------- -------------
cdp                 0
stp                 0
vtp                 0
dtp                 0
pagp                0
dot1x               0
lldp                0
lacp               41
udld                0

          Configuration Examples for EVC

          Ethernet Service Instance

          The following example shows how to configure an Ethernet service instance:

          Switch> enable
Switch# configure terminal
Switch(config)# ethernet evc evc_101
Switch(config-if)# service instance id ethernet
Switch(config-if)# encapsulation  dot1q 100
Switch(config-if-srv)# rewrite ingress tag push dot1q 20 symmetric
Switch(config-if-srv)# bridge-domain 12
Switch(config-if-srv)# exit

          The following example shows how to configure a rewrite using Cisco IOS commands:

          Switch> enable
Switch# configure terminal
Switch(config)# interface g0/30
Switch(config-if)# no shut
Switch(config-if)# service instance 1 ethernet
Switch(config-if-srv)# encapsulation dot1q 13
Switch(config-if-srv)# bridge-domain 13
Switch(config-if-srv)# exit

          Additional References for EVC

          The following sections provide references related to the EVC feature.

          Related Documents

          Related Topic Document Title

          Standards

          Standard Title

          MIBs

          MIB MIBs link

          None.

          To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

          http:/​/​tools.cisco.com/​ITDIT/​MIBS/​servlet/​index

          RFCs

          RFC Title

          No new or modified RFCs are supported, and support for existing RFCs has not been modified.

          		 —

          Technical Assistance

          Description Link

          The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

          To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

          Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

          		 http:/​/​www.cisco.com/​cisco/​web/​support/​index.html

          Was this Document Helpful?

          FeedbackFeedback

          Contact Cisco

          Related Cisco Community Discussions

          About Us
          Contact Us
          Work with Us