- Table of Contents
-
- H3C MSR Routers Configuration Examples-6W100
- 00-Preface
- 01-H3C MSR Routers RBAC Configuration Examples (Comware V7)
- 02-H3C MSR Routers Ethernet Link Aggregation Configuration Examples (Comware V7)
- 03-H3C MSR Routers Port Isolation Configuration Examples (Comware V7)
- 04-H3C MSR Routers VLAN Configuration Examples (Comware V7)
- 05-H3C MSR Routers QinQ Configuration Examples (Comware V7)
- 06-H3C MSR Routers PPP Configuration Examples (Comware V7)
- 07-H3C MSR Routers OSPF Configuration Examples (Comware V7)
- 08-H3C MSR Routers OSPFv3 Configuration Examples (Comware V7)
- 09-H3C MSR Routers IPv6 IS-IS Configuration Examples (Comware V7)
- 10-H3C MSR Routers BGP Configuration Examples (Comware V7)
- Related Documents
-
Title | Size | Download |
---|---|---|
05-H3C MSR Routers QinQ Configuration Examples (Comware V7) | 129.99 KB |
H3C MSR Routers QinQ Configuration Examples (Comware V7)
Copyright © 2017 New H3C Technologies Co., Ltd. All rights reserved.
No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.
The information in this document is subject to change without notice.
Contents
General configuration restrictions and guidelines
Configuration restrictions and guidelines
Configuring devices between PE A and PE B
Introduction
This document provides examples for using QinQ to transmit 802.1Q-tagged customer traffic in the service provider network.
A QinQ-enabled port tags all incoming frames (tagged or untagged) with the PVID tag.
The devices in the service provider network learn MAC addresses of CVLANs into the MAC address table of the SVLAN.
Prerequisites
This document applies to Comware V7-based MSR routers. Procedures and information in the examples might be slightly different depending on the software or hardware version of the router.
The configuration examples in this document were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.
This document assumes that you have basic knowledge of H3C QinQ.
General configuration restrictions and guidelines
QinQ is supported only on the following interfaces:
· Fixed Ethernet interfaces on the MSR3600-51 and MSR3600-28.
· Interfaces on the HMIM 24GSW, HMIM 24GSW-PoE, and HMIM 8GSW interface modules of the MSR routers.
Example: Configuring QinQ
Network requirements
As shown in Figure 1:
· The service provider assigns VLAN 1000 to Company A's VLANs 100 through 150.
· The service provider assigns VLAN 2000 to Company B's VLANs 120 through 200.
Configure QinQ on PE A and PE B to transmit traffic in VLANs 1000 and 2000 for Company A and Company B, respectively.
Software version used
This configuration example was created and verified on R0106.
Configuration restrictions and guidelines
When you configure QinQ, follow these restrictions and guidelines:
· You only need to configure QinQ on customer-side ports of PEs.
· The link type of the customer-side port can be access, hybrid, or trunk.
¡ If the link type is access, you must assign the port to the SVLAN.
¡ If the link type is trunk, you must assign the port to the SVLAN, and set the SVLAN ID as the PVID of the port.
¡ If the link type is hybrid, you must assign the port to the SVLAN as an untagged VLAN member, and set the SVLAN ID as the PVID of the port. The settings ensure that the port can forward traffic to the customer site with the SVLAN tag removed.
¡ Set the MTU to a minimum of 1504 bytes for each port on the path of QinQ frames. This value is the sum of the default Ethernet interface MTU (1500 bytes) and the length (4 bytes) of a CVLAN tag. The CVLAN tag of QinQ frames is treated as part of the payload during transmission.
¡ Configure all the ports on the forwarding path to allow frames from VLANs 1000 and 2000 to pass through without removing the VLAN tag.
Configuration procedures
Configuring PE A
1. Create VLANs 1000 and 2000.
<PE_A> system-view
[PE_A] vlan 1000
[PE_A-vlan1000] quit
[PE_A] vlan 2000
[PE_A-vlan2000] quit
2. Configure GigabitEthernet 2/0/1:
# Configure the port as an access port, and assign the port to VLAN 1000.
[PE_A] interface gigabitethernet 2/0/1
[PE_A-GigabitEthernet2/0/1] port access vlan 1000
# Enable QinQ on the port.
[PE_A-GigabitEthernet2/0/1] qinq enable
[PE_A-GigabitEthernet2/0/1] quit
3. Configure GigabitEthernet 2/0/2:
# Configure the port as an access port, and assign the port to VLAN 2000.
[PE_A] interface gigabitethernet 2/0/2
[PE_A-GigabitEthernet2/0/2] port access vlan 2000
# Enable QinQ on the port.
[PE_A-GigabitEthernet2/0/2] qinq enable
[PE_A-GigabitEthernet2/0/2] quit
4. Configure GigabitEthernet 2/0/3:
# Configure the port as a trunk port.
[PE_A] interface gigabitethernet 2/0/3
[PE_A-GigabitEthernet2/0/3] port link-type trunk
# Assign the port to VLANs 1000 and 2000.
[PE_A-GigabitEthernet2/0/3] port trunk permit vlan 1000 2000
# Remove the port from VLAN 1.
[PE_A-GigabitEthernet2/0/3] undo port trunk permit vlan 1
[PE_A-GigabitEthernet2/0/3] quit
Configuring PE B
1. Create VLANs 1000 and 2000.
<PE_B> system-view
[PE_B] vlan 1000
[PE_B-vlan1000] quit
[PE_B] vlan 2000
[PE_B-vlan2000] quit
2. Configure GigabitEthernet 2/0/1:
# Configure the port as an access port, and assign the port to VLAN 2000.
[PE_B] interface gigabitethernet 2/0/1
[PE_B-GigabitEthernet2/0/1] port access vlan 2000
# Enable QinQ on the port.
[PE_B-GigabitEthernet2/0/1] qinq enable
[PE_B-GigabitEthernet2/0/1] quit
3. Configure GigabitEthernet 2/0/2:
# Configure the port as an access port, and assign the port to VLAN 1000.
[PE_B] interface gigabitethernet 2/0/2
[PE_B-GigabitEthernet2/0/2] port access vlan 1000
# Enable QinQ on the port.
[PE_B-GigabitEthernet2/0/2] qinq enable
[PE_B-GigabitEthernet2/0/2] quit
4. Configure GigabitEthernet 2/0/3:
# Configure the port as a trunk port.
[PE_B] interface gigabitethernet 2/0/3
[PE_B-GigabitEthernet2/0/3] port link-type trunk
# Assign the port to VLANs 1000 and 2000.
[PE_B-GigabitEthernet2/0/3] port trunk permit vlan 1000 2000
# Remove the port from VLAN 1.
[PE_B-GigabitEthernet2/0/3] undo port trunk permit vlan 1
[PE_B-GigabitEthernet2/0/3] quit
Configuring devices between PE A and PE B
# Set the MTU to a minimum of 1504 bytes for each port on the path of QinQ frames. (Details not shown.)
# Configure all ports on the forwarding path to allow frames from VLANs 1000 and 2000 to pass through without removing the VLAN tag. (Details not shown.)
Verifying the configuration
1. Verify that each company's PCs in the same CVLAN can ping each other across the service provider network:
# Verify that Company A's two remote hosts (192.168.100.67 and 192.168.100.24) in CVLAN 100 can ping each other.
C:\Windows\System32>ping 192.168.100.67
Pinging 192.168.100.67 with 32 bytes of data:
Reply from 192.168.100.67: bytes=32 time<1ms TTL=255
Reply from 192.168.100.67: bytes=32 time=11ms TTL=255
Reply from 192.168.100.67: bytes=32 time<1ms TTL=255
Reply from 192.168.100.67: bytes=32 time<1ms TTL=255
Ping statistics for 192.168.100.67:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 11ms, Average = 2ms
# Display the ARP table of the host at 192.168.100.24.
C:\Windows\System32>arp -a
Interface: 192.168.100.24 --- 0x15
Internet Address Physical Address Type
192.168.100.67 0c-da-41-b2-1e-31 dynamic
192.168.100.255 ff-ff-ff-ff-ff-ff static
224.0.0.22 01-00-5e-00-00-16 static
224.0.0.252 01-00-5e-00-00-fc static
239.255.255.250 01-00-5e-7f-ff-fa static
2. Verify that the two companies' PCs cannot communicate at Layer 2 even if their CVLAN IDs are the same. The ARP tables on one company's PCs do not contain entries for MAC addresses of the other company's PCs. (Details not shown.)
Configuration files
· PE A:
#
vlan 1000
#
vlan 2000
#
interface GigabitEthernet2/0/1
port link-mode bridge
port access vlan 1000
qinq enable
#
interface GigabitEthernet2/0/2
port link-mode bridge
port access vlan 2000
qinq enable
#
interface GigabitEthernet2/0/3
port link-mode bridge
port link-type trunk
undo port trunk permit vlan 1
port trunk permit vlan 1000 2000
#
· PE B:
#
vlan 1000
#
vlan 2000
interface GigabitEthernet2/0/1
port link-mode bridge
port access vlan 2000
qinq enable
#
interface GigabitEthernet2/0/2
port link-mode bridge
port access vlan 1000
qinq enable
#
interface GigabitEthernet2/0/3
port link-mode bridge
port link-type trunk
undo port trunk permit vlan 1
port trunk permit vlan 1000 2000
#
Related documentation
· H3C MSR Series Routers Layer 2—LAN Switching Configuration Guide (V7)
· H3C MSR Series Routers Layer 2—LAN Switching Command Reference (V7)