- Configuring ATM
- Multiprotocol over ATM Overview
- LAN Emulation Overview
- Configuring LAN Emulation
- Autosense of ATM PVCs and MUX SNAP Encapsulation
- MQC Policy Map on Configured VC Range ATM
- ATM OAM Ping
- OAM Segment Endpoint
- 802.1ah Support for Ethernet Infrastructure
- Define Interface Policy-Map AV Pairs AAA
- IMA Dynamic Bandwidth
- ATM Multilink PPP Support on Multiple VCs
- N:1 PVC Mapping to PWE with Nonunique VPIs
- Local Template-Based ATM PVC Provisioning
- Configuring ATM SNMP Trap and OAM Enhancements
- Configuring ATM PVC F5 OAM Recovery Traps
- Access Circuit Redundancy Support for IMA
- ATM AC VC Signaling and Provisioning
- Index
Contents
- 802.1ah Support for Ethernet Infrastructure
- Finding Feature Information
- Information About 802.1ah Support for Ethernet Infrastructure
- MTP Software Architecture
- IB Backbone Edge Bridge
- Data Plane Processing
- MTP Configuration
- Scalability Information
- How to Configure 802.1ah Support for Ethernet Infrastructure
- Configuration Examples for 802.1ah Support for Ethernet Infrastructure
- Additional References
- Feature Information for 802.1ah Support for Ethernet Infrastructure
802.1ah Support for Ethernet Infrastructure
The Excalibur MAC Tunneling Protocol (MTP) feature is based on IEEE 802.1ah standard and provides Virtual Bridged Local Area Network (VLAN) and MAC scalability. This feature extends the Cisco QinQ (IEEE 802.1ad) capability to support highly scalable Provider Backbone Bridge Architecture (PBB). MTP allows a service provider to interconnect multiple Provider Bridged Networks (PBNs) with maximum 10,48,576 (2 to the power 20) Service VLANS support and extend the MAC address scalability.
- Finding Feature Information
- Information About 802.1ah Support for Ethernet Infrastructure
- How to Configure 802.1ah Support for Ethernet Infrastructure
- Configuration Examples for 802.1ah Support for Ethernet Infrastructure
- Additional References
- Feature Information for 802.1ah Support for Ethernet Infrastructure
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 Search Tool 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 www.cisco.com/go/cfn. An account on Cisco.com is not required.
Information About 802.1ah Support for Ethernet Infrastructure
With this feature, you can scale a Provider Bridged P802.1ad network using the existing Bridged and VLAN deployment. Although the current Cisco QinQ capability provides for VLAN scaling, this feature extends the scaling and interoperability between multiple vendors.
To make forwarding decisions, Bridges in a Provider Backbone Bridged Network (PBBN) need to know the MAC address of each host. MTP resolves the issue of MAC address learning by encapsulating the data packet and MAC addresses (source and destination) into a new Ethernet frame. The header of the new Ethernet frame contains:
Backbone VLAN TAG (B-TAG) with 12 bit Backbone VLAN ID (B-VID)
Destination Backbone MAC (B-MAC)
Source Backbone MAC (B-MAC)
Service Instance TAG (I-TAG) with 24 bit Service Instance ID (I-SID)
MAC scalability is implemented using the B-MACs. Since the new Ethernet frames are encapsulated with MAC address while traversing the PBBN, a bridge needs to learn only the B-MACs. The MAC addresses of hosts are hidden from the Provider Backbone Bridges (PBB), resulting in the PB Bridges to learn only the provider MAC address, independent of the number of hosts or the number of host MAC addresses supported. Since the data packets are sent to specific MAC addresses, the 802.1ah cloud is not flooded with unnecessary traffic. A MAC address may be a static entry in the MAC address table on the Backbone Core Bridge.
The VLAN scalability is implemented using the I-SID. The MTP achieves VLAN scalability by using a backbone VLAN TAG with 12 bit B-VID and the Service Instance TAG with 24 bit Service Instance ID to provide the VLAN scalability necessary to map large number of customers.
- MTP Software Architecture
- IB Backbone Edge Bridge
- Data Plane Processing
- MTP Configuration
- Scalability Information
MTP Software Architecture
The encapsulation and decapsulation of MAC addresses is performed on a Backbone Edge Bridge (BEB) at the edge of the PBBN. A BEB can be an I-Bridge (I-BEB), a B-bridge (B-BEB), or an IB-bridge (IB-BEB). MTP with IB-BEB functionality is also supported. The figure below shows the MTP software architecture:
IB Backbone Edge Bridge
IB-BEB consists of one B-Component and one or more I-Components. An IB-BEB provides the functionality to select the B-MAC and insert I-SIDs based on the supported tags. It also validates the I-SIDs and transmits or receives the frames on the B-VLAN.
The 802.1ah draft describes two types of customer facing interfaces supported by IB-BEB:
MTP supports these interfaces.
Data Plane Processing
The packets on the ingress EFP are tunneled to the appropriate MAC tunnel using the C-MAC bridge domain. For multiple EFPs using the same I-SID, the switching among EFPs is done using the C-MAC bridge domain. The local switching is performed across all ports in the bridge domain even if they span multiple tunnel engines.
MTP Configuration
The table below lists the relationship between various entities in a Cisco 7600 Series router for MTP implementation:
|
Entity to Entity |
Relationship |
|---|---|
|
EFP to C-MAC bridge domain |
many to one |
|
C-MAC bridge domain to I-SID |
one to one |
|
I-SID to B-MAC bridge domain |
many to one |
The figure below shows N to N relationship within a Cisco 7600 Series Router:
Scalability Information
The table below lists the scalability information for MTP:
|
Scalability Factor |
Scalability Number |
|---|---|
|
Total number of EVCs in the system |
32000 |
|
Total number of EVCs per line card |
16000 |
|
Total number of ISIDs in the system |
|
|
Total C-MAC addresses per LC |
128000 (32000 per NPU) |
|
Total number of EVCs per ISID per NPU |
110 |
|
Total number of EVCs per ISID for a two port Excalibur |
220 |
|
Total number of EVCs per ISID for a four port Excalibur |
440 |
|
Total B-bridge-domains per chassis |
4094 |
|
Total I-SIDs or MAC-Tunnels |
16000 |
|
Total entries in a C-MAC table |
32000 |
How to Configure 802.1ah Support for Ethernet Infrastructure
The configuration of 802.1ah support for ethernet infrastructure of Excalibur MTP for Cisco 7600 Router is described in details below.
1.
enable
2.
configure
terminal
3.
interface
gigabitEthernet
slot/port
or
interface
tengigabitEthernet
slot/port
4.
service
instance
id
{Ethernet [service-name]}
5.
encapsulation
untagged
dot1q
{any |
vlan-id[vlan-id[vlan-id]}
second-dot1q {any |vlan-id[vlan-id[vlan-id]]}
6.
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]
7.
bridge-domain
bridge-id
c-mac
8.
exit
9.
exit
10.
ethernet
mac-tunnel
virtual
mac-in-mac-tunnel-identifier
11.
bridge-domain
bridge-id
12.
service
instance
id
{Ethernet [service-name]}
13.
encapsulation
dot1ah
i-sid
i-sid_number
14.
bridge-domain
bridge-id
c-mac
15.
exit
16.
exit
17.
exit
DETAILED STEPS
Configuration Examples for 802.1ah Support for Ethernet Infrastructure
This example shows how to configure Excalibur MTP for Cisco 7600 Routers:
Device>enable Device#configure terminal Device(config)#interface GigabitEthernet 3/1 Device(config-if)#service instance 20 ethernet Device(config-if-srv)#encapsulation dot1q 40 second-dot1q 42 Device(config-if-srv)#rewrite ingress tag pop 1 symmetric Device(config-if-srv)#bridge-domain 21 c-mac Device(config-if-srv)#exit Device(config-if)#exit Device(config)#ethernet mac-tunnel virtual 22 Device(config-tunnel-minm)#bridge-domain 200 Device(config-tunnel-minm)#service in 23 ethernet Device(config-tunnel-srv)#encapsulation dot1ah isid 24 Device(config-tunnel-srv)#bridge-domain 21 c-mac Device(config-tunnel-srv)#exit Device(config-tunnel-minm)#exit Device(config)#exit
Use the following commands to verify the MTP configuration:
You can use the show platform mtp slot slot_num command to verify the MTP configuration. This command shows the information about MTP for each slot:
Device#sh platform mtp slot 3 SLOT TUNNELENGINE VLAN_LIST 3 MacTunnelEngine3/0 200 3 MacTunnelEngine3/1 3 MacTunnelEngine3/2 3 MacTunnelEngine3/3
Device#sh platform mtp c_bd 21 C_BD B_BD SLOT PPE C_BD_COUNT 21 200 3 0 1 Router#
Device#sh platform mtp b_bd 200 B_BD SLOT PPE B_BD_COUNT 200 3 0 1 Router#
Device#sh platform mtp befp 23 BEFP C_BD B_BD SLOT PPE C_BD_COUNT 23 21 200 3 0 1 Router#
You can use show ethernet service mac-tunnel summary to view a summary of information about a specific mac tunnel.
You can use show ethernet service mac-tunnel id [detail] to view information about a specific mac tunnel, and the ID can range from 1 to 4094.
Device#show ethernet service mac-tunnel 1 detail
Tunnel Id: 1
EFP Microblocks:
****************
Microblock type: Bridge-domain
Bridge-domain: 20
No. of Service Instances: 1
Service Instance ID: 16000
Associated Tunnel Id: 1
Encapsulation: dot1ah 1 vlan-type 0x88E7
Rewrite: egress tag push dot1ah 1 vlan-type 0x88E7 symmetric
State: Up
mac-tunnel address map: 0001.0001.0001 0002.0002.0002
EFP Statistics:
Pkts In Bytes In Pkts Out Bytes Out
0 0 0 0
EFP Microblocks:
****************
Microblock type: Bridge-domain
Bridge-domain: 1 c-mac
Microblock type: CFM
CFM encapsulation:
Additional References
The following sections provide references related to the IEEE 802.1ah Support for Ethernet Infrastructure feature.
Related Documents
|
Related Topic |
Document Title |
|---|---|
|
Configuring ATM |
Configuring ATM |
|
ATM commands |
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. |
Feature Information for 802.1ah Support for Ethernet Infrastructure
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
802.1ah Support for Ethernet Infrastructure |
12.2(33)SRE |
The Excalibur MAC Tunneling Protocol (MTP) feature is based on 802.1ah standard and provides VLAN and MAC scalability. This feature extends the Cisco QinQ (IEEE 802.1ad) capability to support highly scalable PBA. In 12.2(33)SRE, this feature was introduced on the Cisco 7600. The following commands were introduced or modified: service instance id, encapsulation untagged dot1q, rewrite ingress tag, bridge-domain bridge-id c-mac, ethernet mac-tunnel virtual, encapsulation dot1ah, bridge-domain bridge-id c-mac, show ethernet service mac-tunnel. |