Cisco ME 3800x and ME 3600x Switches Software Configuration Guide, Cisco IOS Release 15.4(2)S

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Book Contents

Find Matches in This Book

Available Languages

Download Options

Book Title

Cisco ME 3800x and ME 3600x Switches Software Configuration Guide, Cisco IOS Release 15.4(2)S

Chapter Title

Configuring IEEE 802.1ad

PDF - Complete Book (14.22 MB) PDF - This Chapter (448.0 KB)
View with Adobe Reader on a variety of devices

Results

Updated:: April 7, 2021

Configuring IEEE 802.1ad

Provider networks handle traffic from a large number of customers. It is important that one customer’s traffic is isolated from the other customer’s traffic. IEEE 802.1ad implements standard protocols for double tagging of data. The data traffic coming from the customer side are double tagged in the provider network where the inner tag is the customer-tag (C-tag) and the outer tag is the provider-tag (S-tag). The control packets use different MAC address value in provider network.

The Cisco ME3600x, ME3800x, and ME3600x-24CX-M switches already support VLAN double tagging through a feature called QinQ. 802.1ad is the standardized version of QinQ. It also extends the support for Layer 2 Protocol Tunneling Protocol (L2PT). By offering transparent Layer 2 connectivity, the service provider does not get involved in the customer’s Layer 3 network. This makes provisioning and maintenance simple, and reduces the operational cost.

Prerequisites for IEEE 802.1ad

The ethertype should be programmable per port.

Restrictions for IEEE 802.1ad

Follow these restrictions and guidelines when you configure 802.1ad:

The 802.1ad protocol supports only switchports and EFPs.
The EFP cross connect, SVI based cross connect, EFP local connect, and VPLS are not supported.
The support is on EVCs with BD as the service.
Routing over SVI with 802.1ad EVCs is not supported.
QoS supports 802.1q EVCs.
QoS for DEI (classification, marking, weighted tail-drop) is not supported on 802.1ad EVCs.
Only outer tag etype of 0x88a8 is supported, and the custom ethertype of 0x9100 and 0x9200 are not supported.
The global Ethernet dot1ad command is not supported.
Ethernet 802.1ad is not supported on Port-channels.
L2PT is not supported on switchports.
L2PT is not supported for 802.1ad.
The l2protocol forward command is available only on the main interface of the switchports and the L3 ports.
The l2protocol forward command on a main interface and on EVCs supports all the CE 2.0 protocols.
The l2protocol forward command is available on EVC service instance.
The l2protocol peer and l2protocol drop commands are not supported.
The EFP with encapsulation default cannot achieve the functionality of reverse direction pop (at egress) when the ingress rewrite of push is applied. So, the traffic with 802.1ad tag coming in on NNI cannot get the tag popped off on the S-UNI EFP.
The CFM support on VLANs that are part of 802.1ad network are not available.
802.1ad is supported on the following port types:

Port	EVC	Switchport
C-UNI	Ethertype 0x8100 C-VLAN BPDU Any EVCs	Ethertype 0x8100 C-VLAN BPDU Trunk or Access
S-UNI	Ethertype 0x88a8 S-VLAN BPDU (Only Encapsulation default is supported)	Ethertype 0x88a8 S-VLAN BPDU Access only
NNI	Ethertype 0x88a8 S-VLAN BPDU Any EVC	Ethertype 0x88a8 S-VLAN BPDU Trunk

Port

EVC

Switchport

C-UNI

Ethertype 0x8100

C-VLAN BPDU

Any EVCs

Ethertype 0x8100

C-VLAN BPDU

Trunk or Access

S-UNI

Ethertype 0x88a8

S-VLAN BPDU (Only Encapsulation default is supported)

Ethertype 0x88a8

S-VLAN BPDU

Access only

NNI

Ethertype 0x88a8

S-VLAN BPDU

Any EVC

Ethertype 0x88a8

S-VLAN BPDU

Trunk

Information About IEEE 802.1ad

To configure IEEE 802.1ad support, you should understand the following concepts:

How Provider Bridges Work

Provider bridges pass the network traffic of many customers, and each customer's traffic flow must be isolated from one another. For the Layer 2 protocols within customer domains to function properly, geographically separated customer sites must appear to be connected through a LAN, and the provider network must be transparent.

The IEEE has reserved 33 Layer 2 MAC addresses for customer devices operating Layer 2 protocols. If a provider bridge uses these standard MAC addresses for its Layer 2 protocols, the customers' and service provider's Layer 2 traffic will be mixed together. Provider bridges solve this traffic-mixing issue by providing Layer 2 protocol data unit (PDU) tunneling for customers using a provider bridge (S-bridge) component and a provider edge bridge (C-bridge) component. Figure 23-1 shows the topology.

Figure 23-1 Layer 2 PDU Tunneling

S-Bridge Component

The S-bridge component is capable of inserting or removing a service provider VLAN (S-VLAN) for all traffic on a particular port. IEEE 802.1ad adds a new tag called a Service tag (S-tag) to all the ingress frames from a customer to the service provider.

The VLAN in the S-tag is used for forwarding the traffic in the service provider network. Different customers use different S-VLANs, which results in each customer's traffic being isolated. In the S-tag, provider bridges use an Ethertype value that is different from the standard 802.1Q Ethertype value, and do not understand the standard Ethertype. This difference makes customer traffic tagged with the standard Ethertype appear as untagged in the provider network so customer traffic is tunneled in the port VLAN of the provider port. The 802.1ad service provider user network interfaces (S-UNIs) and network to network interfaces (NNIs) implement the S-bridge component.

For example, a VLAN tag has a VLAN ID of 1, the C-tag Ethertype value is 8100 0001, the S-tag Ethertype value is 88A8 0001, and the class of service (CoS) is zero.

C-tag S-tag

------------------------------------------------------- -----------------------------------------------

0x8100 | Priority bits | CFI | C-VLAN-ID 0x88A8 | Priority bits | 0 | S-VLAN-ID

------------------------------------------------------- -----------------------------------------------

C-Bridge Component

All the C-VLANs entering on a UNI port in an S-bridge component are provided the same service (marked with the same S-VLAN). Although, C-VLAN components are not supported, a customer may want to tag a particular C-VLAN packet separately to differentiate between services. Provider bridges allow C-VLAN packet tagging with a provider edge bridge, called the C-bridge component of the provider bridge. C-bridge components are C-VLAN aware and can insert or remove a C-VLAN 802.1Q tag. The C-bridge UNI port is capable of identifying the customer 802.1Q tag and inserting or removing an S-tag on the packet on a per service instance or C-VLAN basis. A C-VLAN tagged service instance allows service instance selection and identification by C-VLAN. The 802.1ad customer user network interfaces (C-UNIs) implement the C-component.

MAC Addresses for Layer 2 Protocols

Customers' Layer 2 PDUs received by a provider bridge are not forwarded, so Layer 2 protocols running in customer sites do not know the complete network topology. By using a different set of addresses for the Layer 2 protocols running in provider bridges, IEEE 802.1ad causes customers' Layer 2 PDUs entering the provider bridge to appear as unknown multicast traffic and forwards it on customer ports (on the same S-VLAN). Customers' Layer 2 protocols can then run transparently.

Table 23-1 shows the Layer 2 MAC addresses reserved for the C-VLAN component.

Table 23-1 Reserved Layer 2 MAC Addresses for a C-VLAN Component
Assignment	Value
Bridge Group Address	01-80-c2-00-00-00
IEEE Std 802.3 Full Duplex PAUSE operation	01-80-c2-00-00-01
IEEE Std. 802.3 Slow_Protocols_Multicast address	01-80-c2-00-00-02
IEEE Std. 802.1X PAE address	01-80-c2-00-00-03
Reserved for future standardization - media access method-specific	01-80-c2-00-00-04
Reserved for future standardization - media access method- specific	01-80-c2-00-00-05
Reserved for future standardization	01-80-c2-00-00-06
Reserved for future standardization	01-80-c2-00-00-07
Provider Bridge Group Address	01-80-c2-00-00-08
Reserved for future standardization	01-80-c2-00-00-09
Reserved for future standardization	01-80-c2-00-00-0a
Reserved for future standardization	01-80-c2-00-00-0b
Reserved for future standardization	01-80-c2-00-00-0c
Provider Bridge GVRP Address	01-80-c2-00-00-0d
IEEE Std. 802.1AB Link Layer Discovery Protocol multicast address	01-80-c2-00-00-0e
Reserved for future standardization	01-80-c2-00-00-0f

Table 23-2 shows the Layer 2 MAC addresses reserved for an S-VLAN component. These addresses are a subset of the C-VLAN component addresses, and the C-bridge does not forward the provider's bridge protocol data units (BPDUs) to a customer network.

Table 23-2 Reserved Layer 2 MAC Addresses for an S-VLAN Component
Assignment	Value
IEEE Std 802.3 Full Duplex PAUSE operation	01-80-c2-00-00-01
IEEE Std. 802.3 Slow_Protocols_Multicast address	01-80-c2-00-00-02
IEEE Std. 802.1X PAE address	01-80-c2-00-00-03
Reserved for future standardization - media access method specific	01-80-c2-00-00-04
Reserved for future standardization - media access method specific	01-80-c2-00-00-05
Reserved for future standardization	01-80-c2-00-00-06
Reserved for future standardization	01-80-c2-00-00-07
Provider Bridge Group Address	01-80-c2-00-00-08
Reserved for future standardization	01-80-c2-00-00-09
Reserved for future standardization	01-80-c2-00-00-0a

Guidelines for Handling BPDU

The general BPDU guidelines are listed here:

UNI-C Ports

The guidelines pertaining to UNI-C ports are:

VLAN-aware L2 protocols can be peered, tunneled, or dropped. From the config mode only L2 protocol forward option is allowed.
Port L2 protocols can either be peered or dropped. They cannot be tunneled. From the config mode only L2 protocol forward option is allowed.

UNI-S Ports

The guidelines pertaining to UNI-S ports are:

Packets with C-Bridge addresses (00 - 0F) that are not part of S-Bridge addresses (01 - 0A) are treated as data packet (tunneled).
VLAN-aware L2 protocols cannot be peered because the port is not C-VLAN aware. They can only be tunneled or dropped.
Port L2 protocols can be peered, tunneled, or dropped.

NNI Ports

The Dot1add NNI ports behave in the same way as the customer facing S-bridge ports, with the following exceptions:

On NNI ports, frames received with DA 01-80-C2-00-00-08 contain STP BPDU. The frames are received and transmitted. On S-UNI ports, any such frames that are received are dropped, and none are sent.
On NNI ports, frames received with DA 01-80-C2-00-00-02 include CDP Pagp, VTP, DTP, and UDLD protocols.

Interoperability of QinQ and Dot1ad

The interoperability of QinQ and Dot1ad network enables the exchange of data frames between the networks. The 802.1Q network outer tag VLANs are mapped to the provider S-VLANs of the 802.1ad network.

Figure 23-2 illustrates the interoperability of a Dot1ad network and a QinQ network.

Figure 23-2 Interoperability of Dot1ad Network and a QinQ Network

How to Configure IEEE 802.1ad

This section contains the information about following procedures:

Configuring a Switchport

A switchport can be configured as a UNI-C port, UNI-S port, or NNI port.

UNI-C Port

A UNI-C port can be configured as either a trunk port or an access port. Perform the following tasks to configure a UNI-C port as an access port for 802.1ad.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. ethernet dot1ad {nni | uni {c-port | s-port}}

5. switchport

6. switchport mode {access | trunk}

7. switchport access vlan vlan-id

8. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Switch> enable	Enables privileged EXEC mode.
Step 2	configure terminal Example: Switch# configure terminal	Enters global configuration mode.
Step 3	interface type number Example: Switch# interface gigabitethernet 0/1	Configures an interface.
Step 4	ethernet dot1ad {nni \| uni {c-port \| s-port}} Example: Switch(config-if)# ethernet dot1ad uni c-port	Configures a dot1ad NNI port or UNI port. In this example, it is a UNI-C port.
Step 5	switchport Example: Switch(config-if)# switchport	Put the interface into Layer 2 mode.
Step 6	switchport mode {access \| trunk} Example: Switch(config-if)# switchport mode access	Sets the interface type. In this example, it is Access.
Step 7	switchport access vlan vlan-id Example: Switch(config-if)# switchport access 1000	Sets the VLAN when an interface is in access mode. In this example, the VLAN is set to 1000.
Step 8	end Example: Switch(config-if)# end	Returns the CLI to privileged EXEC mode.

UNI-S Port

On a UNI-S port, all the customer VLANs that enter are provided with the same service. The port allows only access configuration. In this mode, the customer’s port is configured as a trunk port. Therefore, the traffic entering the UNI-S port is tagged traffic.

Perform the following tasks to configure a UNI-S port as an access port for 802.1ad.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. switchport

5. switchport mode {access | trunk}

6. ethernet dot1ad {nni | uni {c-port | s-port}}

7. switchport access vlan vlan-id

8. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Switch> enable	Enables privileged EXEC mode.
Step 2	configure terminal Example: Switch# configure terminal	Enters global configuration mode.
Step 3	interface type number Example: Switch# interface gigabitethernet 0/1	Configures an interface.
Step 4	switchport Example: Switch(config-if)# switchport	Put the interface into Layer 2 mode.
Step 5	switchport mode {access \| trunk} Example: Switch(config-if)# switchport mode access	Sets the interface type. In this example, it is Access.
Step 6	ethernet dot1ad {nni \| uni {c-port \| s-port}} Example: Switch(config-if)# ethernet dot1ad uni s-port	Configures a dot1ad NNI port or UNI port. In this example, it is a UNI-S port.
Step 7	switchport access vlan vlan-id Example: Switch(config-if)# switchport access vlan 999	Sets the VLAN when an interface is in access mode. In this example, the VLAN is set to 999.
Step 8	end Example: Switch(config-if)# end	Returns the CLI to privileged EXEC mode.

NNI Port

NNI port allows only trunk configuration. On an NNI port, the frames received on all the allowed VLANs are bridged to the respective internal VLANs.

Perform the following tasks to configure an NNI port as a trunk port for 802.1ad.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. switchport

5. switchport mode {access | trunk}

6. ethernet dot1ad {nni | uni {c-port | s-port}}

7. switchport trunk allowed vlan vlan-list

8. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Switch> enable	Enables privileged EXEC mode.
Step 2	configure terminal Example: Switch# configure terminal	Enters global configuration mode.
Step 3	interface type number Example: Switch# interface gigabitethernet 0/1	Configures an interface.
Step 4	switchport Example: Switch(config-if)# switchport	Put the interface into Layer 2 mode.
Step 5	switchport mode {access \| trunk} Example: Switch(config-if)# switchport mode trunk	Sets the interface type. In this example, it is Trunk.
Step 6	ethernet dot1ad {nni \| uni {c-port \| s-port}} Example: Switch(config-if)# ethernet dot1ad nni	Configures a dot1ad NNI port or UNI port. In this example, it is an NNI.
Step 7	switchport trunk allowed vlan vlan-list Example: Switch(config-if)# switchport trunk allowed vlan 999	Sets the list of allowed VLANs that transmit traffic from this interface in tagged format when in trunking mode.
Step 8	end Example: Switch(config-if)# end	Returns the CLI to privileged EXEC mode.

Examples

The following example shows how to configure a UNI-C port as an access port. In this example, all the frames that are received are bridged to one internal VLAN 1000. The transmitted frames do not have the access VLAN Dot1q tag.

Switch# configure terminal

Switch(config)# interface gig0/1

Switch(config-if # ethernet dot1ad uni c-port

Switch(config-if)# switchport

Switch(config-if)# switchport mode access

Switch(config-if)# switchport access vlan 1000

The following example shows how to configure a UNI-C port as a trunk port. In this example, all the frames that are received on all allowed VLANs (1000 and 2000) are bridged to the respective internal VLANs. The transmitted frames have the respective internal VLAN Dot1q tag.

Switch# configure terminal

outer(config)# interface gig0/1

Switch(config-if)# ethernet dot1ad uni c-port

Switch(config-if)# switchport

Switch(config-if)# switchport mode trunk

Switch(config-if)# switchport access vlan 1000, 2000

The following example shows how to configure a UNI-S port. In this example, all the frames that are received are bridged to one internal VLAN (999). The transmitted frames do not have the access VLAN Dot1q tag.

Switch# configure terminal

Switch(config)# interface gig0/1

Switch(config-if)# switchport

Switch(config-if)# switchport mode access

Switch(config-if)# ethernet dot1ad uni s-port

Switch(config-if)# switchport access vlan 999

The following example shows how to configure an NNI port. Only trunk configuration is allowed on an NNI port. In this example, all the frames that are received on all the allowed VLANs (999) are bridged to the respective internal VLANs. The transmitted frames have the respective internal VLAN Dot1q tag.

Switch# configure terminal

Switch(config)# interface gig0/1

Switch(config-if)# switchport

Switch(config-if)# switchport mode trunk

Switch(config-if)# ethernet dot1ad nni

Switch(config-if)# switchport trunk allowed vlan 999

Configuring a Layer 2 Protocol Forward

Perform the following tasks to configure the Layer 2 protocol forward:

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. switchport access vlan vlan-id

5. ethernet dot1ad {nni | uni {c-port | s-port}}

6. l2protocol [forward] [ protocol ]

7. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Switch> enable	Enables privileged EXEC mode.
Step 2	configure terminal Example: Switch# configure terminal	Enters global configuration mode.
Step 3	interface type number Example: Switch(config)# interface gigabitethernet 0/1	Configures an interface.
Step 4	switchport access vlan vlan-id Example: Switch(config)# switchport access vlan 500	Sets the VLAN when an interface is in access mode.
Step 5	ethernet dot1ad {nni \| uni {c-port \| s-port}} Example: Switch(config-if)# ethernet dot1ad uni s-port	Configures a dot1ad NNI port or UNI port. In this example, it is a UNI S-port.
Step 6	l2 protocol [forward] [ protocol ] Example: Switch(config-if)# l2 protocol forward vtp	Processes or forwards the Layer 2 BPDUs. In this example, all the BPDUs are forwarded except VTP PDUs.
Step 7	end Example: Switch(config-if)# end	Returns the CLI to privileged EXEC mode.

Examples

The following example shows how to configure a Layer 2 protocol forward:

Switch# configure terminal

Switch(config)# interface gig0/1

Switch(config-if)# switchport access vlan 500

Switch(config-if)# ethernet dot1ad uni s-port

Switch(config-if)# l2protocol forward vtp

Configuring a Switchport for Translating QinQ to 802.1ad

Translating a QinQ port to 802.1ad involves configuring the port connecting to QinQ port and NNI port.

Perform the following tasks to configure a port connecting to the QinQ port.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. switchport mode {access | trunk}

5. switchport trunk allowed vlan vlan-list

6. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Switch> enable	Enables privileged EXEC mode.
Step 2	configure terminal Example: Switch# configure terminal	Enters global configuration mode.
Step 3	interface type number Example: Switch# interface gigabitethernet 0/1	Configures an interface.
Step 4	switchport mode {access \| trunk} Example: Switch(config-if)# switchport mode trunk	Sets the interface type. In this example, it is Trunk.
Step 5	switchport trunk allowed vlan vlan-list Example: Switch(config-if)# switchport trunk allowed vlan 1000	Sets the list of allowed VLANs that transmit traffic from this interface in tagged format when in trunking mode.
Step 6	end Example: Switch(config-if)# end	Returns the CLI to privileged EXEC mode.

Perform the following tasks to configure an NNI port.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. ethernet dot1ad {nni | uni {c-port | s-port}}

5. switchport

6. switchport mode {access | trunk}

7. switchport trunk allowed vlan vlan-list

8. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Switch> enable	Enables privileged EXEC mode.
Step 2	configure terminal Example: Switch# configure terminal	Enters global configuration mode.
Step 3	interface type number Example: Switch# interface gigabitethernet 0/1	Configures an interface.
Step 4	ethernet dot1ad {nni \| uni {c-port \| s-port}} Example: Switch(config-if)# ethernet dot1ad nni	Configures a dot1ad NNI port or UNI port. In this example, it is an NNI.
Step 5	switchport Example: Switch(config-if)# switchport	Put the interface into Layer 2 mode.
Step 6	switchport mode {access \| trunk} Example: Switch(config-if)# switchport mode trunk	Sets the interface type. In this example, it is Trunk.
Step 7	switchport trunk allowed vlan vlan-list Example: Switch(config-if)# switchport trunk allowed vlan 999-1199	Sets the list of allowed VLANs that transmit traffic from this interface in tagged format when in trunking mode.
Step 8	end Example: Switch(config-if)# end	Returns the CLI to privileged EXEC mode.

Examples

The following example shows how to translate a QinQ port to 802.1ad. In this example, the peer switch to gig0/1 multiplexes various customer VLANs into VLAN 1000.

Switch# configure terminal

Switch(config)# interface gig0/1

Switch(config-if)# switchport mode trunk

Switch(config-if)# switchport trunk allowed vlan 1000

Switch# configure terminal

Switch(config)# interface gig0/1

Switch(config-if)# ethernet dot1ad nni

Switch(config-if)# switchport

Switch(config-if)# switchport mode trunk

Switch(config-if)# switchport trunk allowed vlan 1000,1199

Configuring a Customer-Facing UNI-C Port with EVC

Perform the following tasks to configure a UNI-C port.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. ethernet dot1ad {nni | uni {c-port | s-port}}

5. service instance id service-type

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

7. bridge-domain vlan-id

8. service instance id service-type

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

10. bridge-domain vlan-id

11. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Switch> enable	Enables privileged EXEC mode.
Step 2	configure terminal Example: Switch# configure terminal	Enters global configuration mode.
Step 3	interface type number Example: Switch(config)# interface gigabitethernet 0/1	Configures an interface.
Step 4	ethernet dot1ad {nni \| uni {c-port \| s-port}} Example: Switch(config-if)# ethernet dot1ad uni c-port	Configures a dot1ad NNI port or UNI port. In this example, it is a UNI C port.
Step 5	service instance id service-type Example: Switch(config-if)# service instance 1 ethernet	Configures an Ethernet service instance. In this example, the service instance is 1.
Step 6	encapsulation dot1q vlan-id second-dot1q {any \| vlan-id } [native] Example: Switch(config-if)# encapsulation dot1q 1-100	Enables IEEE 802.1Q encapsulation of traffic on a specified subinterface in a VLAN.
Step 7	bridge-domain vlan-id Example: Switch(config-if)# bridge-domain 1000	Binds a service instance or a MAC tunnel to a bridge domain.
Step 8	service instance id service-type Example: Switch(config-if)# service instance 2 ethernet	Configures an Ethernet service instance. In this example, the service instance is 2.
Step 9	encapsulation dot1q vlan-id second-dot1q {any \| vlan-id } [native] Example: Switch(config-if)# encapsulation dot1q 102-4094	Enables IEEE 802.1Q encapsulation of traffic on a specified subinterface in a VLAN.
Step 10	bridge-domain vlan-id Example: Switch(config-if)# bridge-domain 500	Binds a service instance or a MAC tunnel to a bridge domain.
Step 11	end Example: Switch(config-if)# end	Returns the CLI to privileged EXEC mode.

Perform the following tasks to configure an NNI port.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. ethernet dot1ad {nni | uni {c-port | s-port}}

5. service instance id service-type

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

7. rewrite ingress tag push 1 symmetric

8. bridge-domain vlan-id

9. service instance id service-type

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

11. rewrite ingress tag push 1 symmetric

12. bridge-domain vlan-id

13. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Switch> enable	Enables privileged EXEC mode.
Step 2	configure terminal Example: Switch# configure terminal	Enters global configuration mode.
Step 3	interface type number Example: Switch(config)# interface gigabitethernet 0/1	Configures an interface.
Step 4	ethernet dot1ad {nni \| uni {c-port \| s-port}} Example: Switch(config-if)# ethernet dot1ad uni c-port	Configures a dot1ad NNI port or UNI port. In this example, it is a UNI C port.
Step 5	service instance id service-type Example: Switch(config-if)# service instance 1 ethernet	Configures an Ethernet service instance. In this example, the service instance is 1.
Step 6	encapsulation dot1q vlan-id second-dot1q {any \| vlan-id } [native] Example: Switch(config-if)# encapsulation dot1q 1000 second-dot1q 1-100	Enables IEEE 802.1Q encapsulation of traffic on a specified subinterface in a VLAN.
Step 7	rewrite ingress tag push 1 symmetric Example: Switch(config-if)# rewrite ingress tag push 1 symmetric	Specifies the encapsulation adjustment that is to be performed on the frame ingress to the service instance.
Step 8	bridge-domain vlan-id Example: Switch(config-if)# bridge-domain 1000	Binds a service instance or a MAC tunnel to a bridge domain.
Step 9	service instance id service-type Example: Switch(config-if)# service instance 2 ethernet	Configures an Ethernet service instance. In this example, the service instance is 2.
Step 10	encapsulation dot1q vlan-id second-dot1q {any \| vlan-id } [native] Example: Switch(config-if)# encapsulation dot1q 500 second-dot1q 102-4094	Enables IEEE 802.1Q encapsulation of traffic on a specified subinterface in a VLAN.
Step 11	rewrite ingress tag push 1 symmetric Example: Switch(config-if)# rewrite ingress tag push 1 symmetric	Specifies the encapsulation adjustment that is to be performed on the frame ingress to the service instance.
Step 12	bridge-domain vlan-id Example: Switch(config-if)# bridge-domain 500	Binds a service instance or a MAC tunnel to a bridge domain.
Step 13	end Example: Switch(config-if)# end	Returns the CLI to privileged EXEC mode.

Examples

The following example shows how to configure a customer-facing UNI port. In this example, a dot1q frame coming on VLAN 50 matches service instance 1, and on the ingress port, the rewrite command pushes the 1000 outer-vlan.

Switch# configure terminal

Switch(config)# interface gig0/1

Switch(config-if)# ethernet dot1ad uni c-port

Switch(config-if)# service instance 1 ethernet

Switch(config-if)# encapsulation dot1q 1-100

Switch(config-if)# bridge-domain 1000
Switch(config-if)# service instance 2 ethernet
Switch(config-if)# encapsulation dot1q 102-4094
Switch(config-if)# bridge-domain 500

Switch# configure terminal

Switch(config)# interface gig0/1

Switch(config-if)# ethernet dot1ad nni

Switch(config-if)# service instance 1 ethernet

Switch(config-if)# encapsulation dotad 1000 second dot1q 1-100

Switch(config-if)# rewrite ingress tag push 1 symmetric
Switch(config-if)# bridge-domain 1000
Switch(config-if)# service instance 2ethernet

Switch(config-if)# encapsulation dotad 500 second dot1q 102-4094

Switch(config-if)# rewrite ingress tag push 1 symmetric
Switch(config-if)# bridge-domain 500

Configuring a Customer-Facing UNI-C Port and Switchport on NNI with EVC

Perform the following tasks to configure a UNI-C port.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. ethernet dot1ad {nni | uni {c-port | s-port}}

5. service instance id service-type

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

7. bridge-domain vlan-id

8. service instance id service-type

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

10. bridge-domain vlan-id

11. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Switch> enable	Enables privileged EXEC mode.
Step 2	configure terminal Example: Switch# configure terminal	Enters global configuration mode.
Step 3	interface type number Example: Switch(config)# interface gigabitethernet 0/1	Configures an interface.
Step 4	ethernet dot1ad {nni \| uni {c-port \| s-port}} Example: Switch(config-if)# ethernet dot1ad uni c-port	Configures a dot1ad NNI port or UNI port. In this example, it is a UNI C port.
Step 5	service instance id service-type Example: Switch(config-if)# service instance 1 ethernet	Configures an Ethernet service instance. In this example, the service instance is 1.
Step 6	encapsulation dot1q vlan-id second-dot1q {any \| vlan-id } [native] Example: Switch(config-if)# encapsulation dot1q 1-100	Enables IEEE 802.1Q encapsulation of traffic on a specified subinterface in a VLAN.
Step 7	bridge-domain vlan-id Example: Switch(config-if)# bridge-domain 1000	Binds a service instance or a MAC tunnel to a bridge domain.
Step 8	service instance id service-type Example: Switch(config-if)# service instance 2 ethernet	Configures an Ethernet service instance. In this example, the service instance is 2.
Step 9	encapsulation dot1q vlan-id second-dot1q {any \| vlan-id } [native] Example: Switch(config-if)# encapsulation dot1q 102-4094	Enables IEEE 802.1Q encapsulation of traffic on a specified subinterface in a VLAN.
Step 10	bridge-domain vlan-id Example: Switch(config-if)# bridge-domain 500	Binds a service instance or a MAC tunnel to a bridge domain.
Step 11	end Example: Switch(config-if)# end	Returns the CLI to privileged EXEC mode.

Perform the following tasks to configure an NNI port.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. ethernet dot1ad {nni | uni {c-port | s-port}}

5. switchport

6. switchport mode {access | trunk}

7. switchport trunk allowed vlan vlan-list

8. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Switch> enable	Enables privileged EXEC mode.
Step 2	configure terminal Example: Switch# configure terminal	Enters global configuration mode.
Step 3	interface type number Example: Switch# interface gigabitethernet 0/1	Configures an interface.
Step 4	ethernet dot1ad {nni \| uni {c-port \| s-port}} Example: Switch(config-if)# ethernet dot1ad nni	Configures a dot1ad NNI port or UNI port. In this example, it is an NNI.
Step 5	switchport Example: Switch(config-if)# switchport	Put the interface into Layer 2 mode.
Step 6	switchport mode {access \| trunk} Example: Switch(config-if)# switchport mode trunk	Sets the interface type. In this example, it is Trunk.
Step 7	switchport trunk allowed vlan vlan-list Example: Switch(config-if)# switchport trunk allowed vlan 500-1000	Sets the list of allowed VLANs that transmit traffic from this interface in tagged format when in trunking mode.
Step 8	end Example: Switch(config-if)# end	Returns the CLI to privileged EXEC mode.

Examples

The following example shows how to configure a customer-facing UNI-C port and switchport on NNI with EVC:

Switch# configure terminal

Switch(config)# interface gig0/1

Switch(config-if)# ethernet dot1ad uni c-port

Switch(config-if)# service instance 1 ethernet

Switch(config-if)# encapsulation dot1q 1-100

Switch(config-if)# bridge-domain 1000
Switch(config-if)# service instance 2 ethernet
Switch(config-if)# encapsulation dot1q 102-4094
Switch(config-if)# bridge-domain 500

Switch# configure terminal

Switch(config)# interface gig0/1

Switch(config-if)# switchport
Switch(config-if)# ethernet dot1ad uni
Switch(config-if)# switchport mode trunk
Switch(config-if)# switchport allowed vlan 1000,500

Configuring a Customer-Facing UNI-S Port with EVC

Perform the following tasks to configure a UNI-S port.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. ethernet dot1ad {nni | uni {c-port | s-port}}

5. service instance id service-type

6. encapsulation default

7. bridge-domain vlan-id

8. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Switch> enable	Enables privileged EXEC mode.
Step 2	configure terminal Example: Switch# configure terminal	Enters global configuration mode.
Step 3	interface type number Example: Switch(config)# interface gigabitethernet 0/1	Configures an interface.
Step 4	ethernet dot1ad {nni \| uni {c-port \| s-port}} Example: Switch(config-if)# ethernet dot1ad uni s-port	Configures a dot1ad NNI port or UNI port. In this example, it is a UNI-S port.
Step 5	service instance id service-type Example: Switch(config-if)# service instance 1 ethernet	Configures an Ethernet service instance. In this example, the service instance is 1.
Step 6	encapsulation default Example: Switch(config-if)# encapsulation default	Configures the default service instance on a port. Anything that does not meet the criteria of other service instances on the same physical interface falls into this service instance.
Step 7	bridge-domain vlan-id Example: Switch(config-if)# bridge-domain 1000	Binds a service instance or a MAC tunnel to a bridge domain.
Step 8	end Example: Switch(config-if)# end	Returns the CLI to privileged EXEC mode.

Perform the following tasks to configure an NNI port.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface type number

4. ethernet dot1ad {nni | uni {c-port | s-port}}

5. service instance id service-type

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

7. rewrite ingress tag push dot1ad 999 symmetric

8. bridge-domain vlan-id

9. end

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Switch> enable	Enables privileged EXEC mode.
Step 2	configure terminal Example: Switch# configure terminal	Enters global configuration mode.
Step 3	interface type number Example: Switch(config)# interface gigabitethernet 0/1	Configures an interface.
Step 4	ethernet dot1ad {nni \| uni {c-port \| s-port}} Example: Switch(config-if)# ethernet dot1ad uni c-port	Configures a dot1ad NNI or UNI port. In this example, it is a UNI C port.
Step 5	service instance id service-type Example: Switch(config-if)# service instance 1 ethernet	Configures an Ethernet service instance. In this example, the service instance is 1.
Step 6	encapsulation dot1q vlan-id second-dot1q {any \| vlan-id } [native] Example: Switch(config-if)# encapsulation dotad 1000 second-dot1q 1-100	Enables IEEE 802.1Q encapsulation of traffic on a specified subinterface in a VLAN.
Step 7	rewrite ingress tag push dot1ad <> symmetric Example: Switch(config-if)# rewrite ingress tag push dot1ad 999 symmetric	Specifies the encapsulation adjustment that is to be performed on the frame ingress to the service instance.
Step 8	bridge-domain vlan-id Example: Switch(config-if)# bridge-domain 1000	Binds a service instance or a MAC tunnel to a bridge domain.
Step 9	end Example: Switch(config-if)# end	Returns the CLI to privileged EXEC mode.

Examples

The following example shows how to configure an NNI port:

Switch# configure terminal

Switch(config)# interface gig0/1

Switch(config-if)# ethernet dot1ad nni

Switch(config-if)# service instance 1 ethernet

Switch(config-if-srv)# encapsulation dotad 1000

Switch(config-if-srv)# rewrite ingress tag push dot1ad 999 symmetric
Switch(config-if-srv)# bridge-domain 1000

Configuration Examples for IEEE 802.1ad

Example: Configuring an 802.1ad S-Bridge UNI

The following example shows how to configure GigabitEthernet interface 0/1 of a PE as an 802.1ad S-bridge UNI. In this example, only Cisco Discovery Protocol PDUs will be forwarded (tunneled). Cisco Discovery Protocol PDUs will be forwarded between the PE and a customer device.

Switch# configure terminal

Switch(config)# interface GigabitEthernet 0/1

Switch(config-if)# switchport access vlan 500

Switch(config-if)# ethernet dot1ad uni s-port

Example: Configuring an 802.1ad C-Bridge UNI

The following example shows how to configure interface GigabitEthernet 0/1 of a PE as an 802.1ad C-bridge UNI. In this example, only Cisco Discovery Protocol PDUs will be processed.

Switch# configure terminal

Switch(config)# interface GigabitEthernet 0/1

Switch(config-if)# switchport mode trunk

Switch(config-if)# ethernet dot1ad uni c-port

Displaying a Dot1ad Configuration

You can display a Dot1ad configuration using the show ethernet dot1ad command. This command displays the Dot1ad configuration for all interfaces. To display the configuration on a particular interface, use the show ethernet dot1ad interface command.

The following example shows how to display a Dot1ad configuration on all interfaces:

Switch# show ethernet dot1ad

Interface: GigabitEthernet 0/1

DOT1AD C-Bridge Port

L2protocol pass

Interface: GigabitEthernet 0/2

DOT1AD C-Bridge Port

L2protocol pass

Additional References

Related Topic	Document Title
Cisco IOS commands: master list of commands with complete command syntax, command mode, command history, defaults, usage guidelines, and examples	Cisco IOS Master Commands List, All Releases

Standards

Standard	Title
IEEE 802.1ad	Provider Bridges

Technical Assistance

Description	Link
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.	http://www.cisco.com/cisco/web/support/index.html

Glossary

DTP —Dynamic Trunking Protocol

GARP —Generic Attribute Registration Protocol

GMRP —GARP Multicast Registration Protocol

GVRP —Generic VLAN Registration Protocol

LLDP —Link Layer Discovery Protocol

OAM —Operations, Administration, and Maintenance

PagP —Port Aggregation Protocol

PVST —Per-VLAN Spanning Tree

UDLD —UniDirectional Link Detection

VTP —VLAN Trunk Protocol

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)

Cisco ME 3800x and ME 3600x Switches Software Configuration Guide, Cisco IOS Release 15.4(2)S

Bias-Free Language

Results

Chapter: Configuring IEEE 802.1ad

Configuring IEEE 802.1ad

Prerequisites for IEEE 802.1ad

Restrictions for IEEE 802.1ad

Information About IEEE 802.1ad

How Provider Bridges Work

S-Bridge Component

C-Bridge Component

MAC Addresses for Layer 2 Protocols

Guidelines for Handling BPDU

UNI-C Ports

UNI-S Ports

NNI Ports

Interoperability of QinQ and Dot1ad

How to Configure IEEE 802.1ad

Configuring a Switchport

UNI-C Port

SUMMARY STEPS

DETAILED STEPS

UNI-S Port

SUMMARY STEPS

DETAILED STEPS

NNI Port

SUMMARY STEPS

DETAILED STEPS

Examples

Configuring a Layer 2 Protocol Forward

SUMMARY STEPS

DETAILED STEPS

Examples

Configuring a Switchport for Translating QinQ to 802.1ad

SUMMARY STEPS

DETAILED STEPS

SUMMARY STEPS

DETAILED STEPS

Examples

Configuring a Customer-Facing UNI-C Port with EVC

SUMMARY STEPS

DETAILED STEPS

SUMMARY STEPS

DETAILED STEPS

Examples

Configuring a Customer-Facing UNI-C Port and Switchport on NNI with EVC

SUMMARY STEPS

DETAILED STEPS

SUMMARY STEPS

DETAILED STEPS

Examples

Configuring a Customer-Facing UNI-S Port with EVC

SUMMARY STEPS

DETAILED STEPS

SUMMARY STEPS

DETAILED STEPS

Examples

Configuration Examples for IEEE 802.1ad

Example: Configuring an 802.1ad S-Bridge UNI

Example: Configuring an 802.1ad C-Bridge UNI

Displaying a Dot1ad Configuration

Additional References

Related Documents

Standards

Technical Assistance

Glossary

Was this Document Helpful?

Contact Cisco