Filter
Top Products
QinQ (Provider Bridging)
Configuration Example
2. Reboot the box with the configuration saved to transfer into svlan bridge
mode.
3. Configure S-VLANs and port assignments.
Core 1(config)# svlan 100
Core 1(svlan-100)# tagged A1, A2
Core 1(svlan-100)# exit
Core 1(config)# svlan 200
Core 1(svlan-200)# tagged A1, A2
Core 1(svlan-200)# exit
Core 1(config)# interface A1,A2 qinq port-type
provider-network
Note The S-VLAN configuration for the core devices is based on what VLANs
the edge devices (Edge 1 and 2) can send. Per the 802.1ad specification,
all ports carrying customer traffic will be tagged on the VLAN that the port
carries customer frames on.
Configure Provider Core 2 Switch. To configure the Core 2 switch, you
would take the following steps:
1. Enable QinQ.
Core 2(config)# qinq svlan tag-type 88a8
2. Reboot the box with the configuration saved to transfer into svlan bridge
mode.
3. Configure S-VLANs and port assignments.
Core 2(config)# svlan 100
Core 2(svlan-100)# tagged A1, A2
Core 2(svlan-100)# exit
Core 2(config)# svlan 200
Core 2(svlan-100)# tagged A1, A2
Core 2(svlan-100)# exit
Core 2(config)# interface A1,A2 qinq port-type
provider-network
Verify the Configuration. Once the edge and core switch configurations
are completed, QinQ operations can begin. To verify operations, it should be
possible to assign IP-addresses to customer A or B devices in site 1 and site 2
and ping them. If everything has been configured correctly, traffic will flow
through the provider network cloud and reach the other site seamlessly. To
verify the configuration, see also “Displaying QinQ Config and Status” on page
8-24.
8-21