Gigabit Ethernet Interfaces Commands

This section describes the commands used to configure Gigabit Ethernet services for Layer 2 VPNs.

For detailed information about concepts and configuration, see the Configure Gigabit Ethernet for Layer 2 VPNs chapter in the L2VPN and Ethernet Services Configuration Guide for Cisco NCS 5000 Series Routers.

l2transport (Ethernet)

To enable Layer 2 transport port mode on an Ethernet interface and enter Layer 2 transport configuration mode, use the l2transport command in interface or Subinterface configuration mode for an Ethernet interface. To disable Layer 2 transport port mode on an Ethernet interface, use the no form of this command.

l2transport

no l2transport

This command has no keywords or arguments.

Command Default

None

Command Modes

Interface configuration

Sub-interface configuration

Command History

Release

Modification

Release 6.0

This command was introduced.

Usage Guidelines

The l2transport command and these configuration items are mutually exclusive:

  • IPv4 address and L3 feature configuration
  • IPv4 enable and L3 feature configuration
  • Bundle-enabling configuration
  • L3 sub-interfaces
  • Layer 3 QoS Policy

Note

  • After an interface or connection is set to Layer 2 switched, commands such as ipv4 address are not usable. If you configure routing commands on the interface, l2transport is rejected.

  • The l2transport command is mutually exclusive with any Layer 3 interface configuration.

Task ID

Task ID

Operations

l2vpn

read, write

Examples

The following example shows how to enable Layer 2 transport port mode on an Ethernet interface and enter Layer 2 transport configuration mode: 

Router# configure
Router(config)# interface TenGigE 0/2/0/0
Router(config-if)# l2transport
Router(config-if-l2)#

Note

Ensure that the l2transport command is applied on the same line as the interface command for the Ethernet sub-interface.

The following example shows how to use the l2transport command on an Ethernet sub-interface: 

Router# configure
Router(config)# interface TenGigE 0/1/0/3.10 l2transport
Router(config-subif)# encapsulation dot1q 10

Examples

The following example shows how to configure an interface or connection as Layer 2 switched under several different modes:

Ethernet Port Mode: 


Router# configure
Router(config)# interface TenGigE 0/0/0/10 
Router(config-if)# l2transport

Ethernet VLAN Mode: 


Router# configure
Router(config)# interface TenGigE 0/0/0/0.1 l2transport
Router(config-if)# encapsulation dot1q 10

Ethernet VLAN Mode (QinQ): 


Router# configure
Router(config)# interface TenGigE 0/0/0/0.1 l2transport
Router(config-if)# encapsulation dot1q 10 second-dot1q 11

Note

Ensure that the l2transport command is applied on the same line as the interface command for the Ethernet subinterface.

Related Commands

Command Description

encapsulation dot1q

Defines the matching criteria to map 802.1Q frames ingress on an interface to the appropriate service instance.  

encapsulation dot1q second-dot1q

Defines the matching criteria to map Q-in-Q ingress frames on an interface to the appropriate service instance.  

flood mode ac-ingress-replication

To add BUM traffic queueing support for attachment circuits in a bridge domain, use the flood mode ac-ingress-replication command in the L2VPN bridge group bridge domain configuration mode. To return to the default behavior, use the no form of this command.

flood mode ac-ingress-replication

This command has no keywords or arguments.

Command Default

BUM traffic queueing support is not supported for attachment circuits in a bridge domain.

Command Modes

L2VPN bridge group bridge domain configuration

Command History

Release Modification

Release 7.2.1

This command was introduced.

Release 7.2.2

This command was deprecated.

Usage Guidelines

BUM traffic queueing support for attachment circuits in a bridge domain is not supported on devices that have multiple NPUs or line cards. It is only supported on single NPU devices.

Examples

Perform this task to add BUM traffic queueing support for attachment circuits in a bridge domain

Router# configure
Router(config)# l2vpn
Router(config-l2vpn)# bridge group 10
Router(config-l2vpn-bg)# bridge-domain 1
Router(config-l2vpn-bg-bd)# flood mode ac-ingress-replication
Router(config-l2vpn-bg-bd)# commit