Filter
Top Products
QinQ (Provider Bridging)
Configuration Example
3. Configure S-VLANs and ports connected to the customer network.
Edge1 (config)# svlan100
Edge1(svlan-100)# untagged A1
Edge1(svlan-100)# exit
Edge1(config)# int A1 qinq port-type customer-network
Edge1(config)# svlan 200
Edge1(svlan-200)# untagged A2
Edge1(svlan-200)# exit
Edge1(config)# int A2 qinq port-type customer-network
Note In this example, customer A is assigned S-VLAN 100 and customer B is
assigned S-VLAN 200. However, the same customer can be associated with
more that one SVLAN. Also, interfaces A1 and A2 are configured as
customer network ports because they are linked to customer bridges.
4. Configure the provider ports leading to the core of the provider network.
Edge1(config)# svlan 100 tagged A3, A4
Edge1(config)# svlan 200 tagged A3, A4
Edge1(config)# interface A3,A4 qinq port-type
provider-network
Note As recommended by IEEE 802.1ad specification, uplink ports should
generally be configured as tagged ports for S-VLANs that are used to carry
customer traffic. However, this is not a mandatory requirement on
ProCurve switches—S-VLANs that are used for internal provider network
use (not carrying customer traffic but for management of the provider
network devices) can have untagged port memberships.
Configure Provider Edge 2 Switch. The configuration details for the
“Edge 2” switch mirrors the configuration for the Edge 1 switch. All customer
traffic received on port A1 from customer A’s site 2 will be associated with
S-VLAN 100. Similarly, all customer B’s site 2 traffic will be associated with
S-VLAN 200.
To configure the switch, you would do the following steps:
1. Enable QinQ.
Edge 2(config)# qinq svlan tag-type 88a8
8-19