05-QinQ典型配置指导
本章节下载: 05-QinQ典型配置指导 (497.34 KB)
目 录
本文主要介绍了使用QinQ功能在运营商网络中传输用户数据的配置方式,包括基本QinQ和灵活QinQ两种主要功能。其中灵活QinQ又分为基于端口配置和基于QoS策略配置:基于端口配置操作上更简单直接;而基于QoS策略的配置则更为灵活,可以制定丰富的外层标签封装策略。
基本QinQ是基于端口方式实现的。当端口上配置了基本QinQ功能后,不论从该端口收到报文是否带有VLAN Tag,设备都会为该报文封装本端口缺省VLAN的Tag。该功能实现简单,适用于在运营商网络中通过外层VLAN来区分某个用户网络的所有数据。
图1-1 基本QinQ组网示意图
Customer A和Customer B各有两个分支机构需要通过运营商网络进行通信,如图1-1所示。现要求运营商网络能够为两个用户网络的分支机构间的通信提供相互隔离的通道,并保证用户网络的VLAN信息能够准确传输。
运营商网络中可用的资源包括VLAN1000和VLAN2000,PE A和PE B设备之间的设备采用的TPID值为0x8200。
要完成该组网需求,需要在PE A和PE B设备上对各用户的数据进行区分,使用VLAN进行区分是比较简单的方式。考虑到用户网络中已经存在私有VLAN,并且私有VLAN信息需要准确传输至远端用户网络,因此,可以使用基本QinQ功能,在保留用户数据中私有VLAN信息的前提下,再封装一层运营商网络VLAN来区分各个用户的数据。本例中,使用VLAN1000来标识Customer A的数据;使用VLAN2000来标识Customer B的数据。
在PE A和PE B上分别进行以下配置:
l PE A:在GigabitEthernet1/0/1和GigabitEthernet1/0/2端口上配置基本QinQ功能,并将缺省VLAN分别配置为VLAN1000和VLAN2000。同时,还需要配置PE A在从GigabitEthernet1/0/3端口发出数据时,保留VLAN Tag,且采用的TPID值为0x8200。
l PE B:在GigabitEthernet1/0/1和GigabitEthernet1/0/2端口上配置基本QinQ功能,并将缺省VLAN分别配置为VLAN2000和VLAN1000。同时,还需要配置PE B在从GigabitEthernet1/0/3端口发出数据时,保留VLAN Tag,且采用的TPID值为0x8200。
l 在PE A和PE B设备接入用户的端口上,需要配置在发送报文时去掉报文的VLAN Tag,以保证用户网络接收的数据中不会包含运营商的VLAN信息。
表1-1 配置适用的产品与软件版本关系
产品 |
软件版本 |
S7500E系列以太网交换机 |
Release 6100系列,Release 6300系列,Release 6600系列,Release 6610系列 |
S7600系列以太网交换机 |
Release 6600系列,Release 6610系列 |
S5800&S5820X系列以太网交换机 |
Release 1110,Release 1211 |
CE3000-32F以太网交换机 |
Release 1211 |
S5810系列以太网交换机 |
Release 1102 |
S5500-EI系列以太网交换机 |
Release 2202,Release 2208 |
S5500-EI-D系列以太网交换机 |
Release 2208 |
S5500-SI系列以太网交换机 |
Release 2202 ,Release 2208 |
S5120-EI系列以太网交换机 |
Release 2202,Release 2208 |
S5120-EI-D系列以太网交换机 |
Release 1505 |
S5120-SI系列以太网交换机 |
Release 1101,Release 1505 |
S5120-LI系列以太网交换机 |
Release 1107 |
E552&E528以太网交换机 |
Release 1103 |
S3610&S5510系列以太网交换机 |
Release 5301,Release 5303,Release 5306,Release 5309 |
S3500-EA系列以太网交换机 |
Release 5303,Release 5309 |
S3100V2系列以太网交换机 |
Release 5103 |
E126B以太网交换机 |
Release 5103 |
(1) PE A的配置
# 创建VLAN1000和VLAN2000。
<PE_A> system-view
[PE_A] vlan 1000
[PE_A-vlan1000] quit
[PE_A] vlan 2000
[PE_A-vlan2000] quit
l GigabitEthernet1/0/1端口的配置
# 配置端口为Hybrid端口,缺省VLAN为1000,且在发送VLAN1000的报文时去掉VLAN Tag。
[PE_A] interface GigabitEthernet 1/0/1
[PE_A-GigabitEthernet1/0/1] port link-type hybrid
[PE_A-GigabitEthernet1/0/1] port hybrid pvid vlan 1000
[PE_A-GigabitEthernet1/0/1] port hybrid vlan 1000 untagged
除S3610/S5510/S3500-EA产品外,其余产品对接入用户网络端口的端口类型没有限制,只需要保证端口允许缺省VLAN不带VLAN Tag通过即可。对于S3610/S5510/S3500-EA产品,则有以下要求:
l 如果PE设备使用的是S3610或S5510系列交换机的Release 5301版本,则在接入用户网络的端口上,还必须允许用户网络的VLAN通过,因此,只能将端口配置为Hybrid端口。在此例中,需要配置“port hybrid vlan 100 to 150 1000 untagged”。
l 如果PE设备使用的是S3610/S5510/S3500-EA系列交换机的的Release 5303及以上版本,可以在接入用户网络的端口上关闭VLAN检查功能(在端口视图下执行vlan-check disable命令),这样该端口即可以不必允许用户网络的私有VLAN通过。下文不再赘述。
# 开启GigabitEthernet1/0/1端口的QinQ功能。
[PE_A-GigabitEthernet1/0/1] qinq enable
l GigabitEthernet1/0/2端口的配置
# 配置端口为Access端口,允许VLAN2000的报文通过。
[PE_A] interface GigabitEthernet 1/0/2
[PE_A-GigabitEthernet1/0/2] port access vlan 2000
# 开启GigabitEthernet1/0/2端口的QinQ功能。
[PE_A-GigabitEthernet1/0/2] qinq enable
[PE_A-GigabitEthernet1/0/2] quit
l GigabitEthernet1/0/3端口的配置
# 配置端口为Trunk端口,且允许VLAN1000和VLAN2000的报文通过。
[PE_A] interface GigabitEthernet 1/0/3
[PE_A-GigabitEthernet1/0/3] port link-type trunk
[PE_A-GigabitEthernet1/0/3] port trunk permit vlan 1000 2000
[PE_A-GigabitEthernet1/0/3] quit
l 配置PE A在向运营商网络内发送报文时,采用的TPID值为0x8200。配置TPID值有以下四种方式:
# 方式一(适用于S5500-SI/S5120-EI/S5500-EI-D/S3100V2/E126B系列交换机):在系统视图下配置全局报文的TPID值,该值对所有端口发送的报文均生效。
[PE_A] qinq ethernet type 8200
# 方式二(适用于S5500-EI系列交换机):在系统视图下配置全局运营商网络的TPID值,该值对所有未开启QinQ功能的端口发送的报文均生效。
[PE_A] qinq ethernet type service-tag 8200
# 方式三(适用于S3610/S5510/S3500-EA/S5120-SI/S5120-EI-D/S5120-LI/E552&E528系列交换机):在端口视图下配置当前端口使用的TPID值。
[PE_A] interface GigabitEthernet 1/0/3
[PE_A-GigabitEthernet1/0/3] qinq ethernet-type 8200
# 方式四(适用于S5800/S5820X/CE3000-32F/S7500E/S10500/S7600系列交换机):在端口视图下配置当前端口报文时使用的TPID值。
[PE_A] interface GigabitEthernet 1/0/3
[PE_A-GigabitEthernet1/0/3] qinq ethernet-type service-tag 8200
(2) PE B的配置
# 创建VLAN1000和VLAN2000。
<PE_B> system-view
[PE_B] vlan 1000
[PE_B-vlan1000] quit
[PE_B] vlan 2000
[PE_B-vlan2000] quit
l GigabitEthernet1/0/1端口的配置
# 配置端口为Hybrid端口,缺省VLAN为2000,且在发送VLAN2000的报文时去掉VLAN Tag。
[PE_B] interface GigabitEthernet 1/0/1
[PE_B-GigabitEthernet1/0/1] port link-type hybrid
[PE_B-GigabitEthernet1/0/1] port hybrid pvid vlan 2000
[PE_B-GigabitEthernet1/0/1] port hybrid vlan 2000 untagged
# 开启GigabitEthernet1/0/1端口的QinQ功能。
[PE_B-GigabitEthernet1/0/1] qinq enable
l GigabitEthernet1/0/2端口的配置
# 配置端口为Access端口,允许VLAN1000的报文通过。
[PE_B] interface GigabitEthernet 1/0/2
[PE_B-GigabitEthernet1/0/2] port access vlan 1000
# 开启GigabitEthernet1/0/2端口的QinQ功能。
[PE_B-GigabitEthernet1/0/2] qinq enable
[PE_B-GigabitEthernet1/0/2] quit
l GigabitEthernet1/0/3端口的配置
# 配置端口为Trunk端口,且允许VLAN1000和VLAN2000的报文通过。
[PE_B] interface GigabitEthernet 1/0/3
[PE_B-GigabitEthernet1/0/3] port link-type trunk
[PE_B-GigabitEthernet1/0/3] port trunk permit vlan 1000 2000
[PE_B-GigabitEthernet1/0/3] quit
l 配置PE B在向运营商网络内发送报文时,采用的TPID值为0x8200。此处以S5500-EI系列交换机为例,其它产品的配置方式请参见PE A的配置部分。
[PE_B] qinq ethernet-type service-tag 8200
(3) 公共网络设备的配置
由于PE A和PE B之间使用的网络设备可能来自于其他厂商,这里只介绍基本原理:配置运营商网络中PE A到PE B之间的路径上的设备端口都允许VLAN1000和VLAN2000的报文携带VLAN Tag通过即可。
l PE A的配置
#
qinq ethernet-type service-tag 8200
#
vlan 1000
#
vlan 2000
#
interface GigabitEthernet1/0/1
port link-type hybrid
port hybrid vlan 1 1000 untagged
qinq enable
#
interface GigabitEthernet1/0/2
port access vlan 2000
qinq enable
#
interface GigabitEthernet1/0/3
port link-type trunk
port trunk permit vlan 1 1000 2000
l PE B的配置
#
qinq ethernet-type service-tag 8200
#
vlan 1000
#
vlan 2000
interface GigabitEthernet1/0/1
port link-type hybrid
port hybrid vlan 1 2000 untagged
qinq enable
#
interface GigabitEthernet1/0/2
port access vlan 1000
qinq enable
#
interface GigabitEthernet1/0/3
port link-type trunk
port trunk permit vlan 1 1000 2000
无
基本QinQ功能可以确保各个用户网络的数据在运营商网络传输时相互隔离,但具有一定的局限性。由于每个端口只能为接收的所有报文封装同样的外层标签,因此对于用户网络中使用不同VLAN来区分的不同业务数据,在运营商网络中就无法进行区分,也就无法针对不同业务进行网络资源的分配和优化。
使用灵活QinQ功能可以解决这个问题,它对基本QinQ的功能进行了扩展,对同一端口接收的报文,可以根据用户网络VLAN的不同来为其封装不同的外层VLAN Tag。
图1-2 灵活QinQ组网示意图(基于端口配置)
Customer A和Customer B各有两个分支机构需要通过运营商网络进行通信,如图1-2所示。现要求运营商网络能够通过QinQ方式使用户的分支机构间进行数据传输,并能够针对用户网络中用VLAN来标识的各种业务数据,在运营商网络中提供相应的差别服务,使优先级高的业务得到优先传输。其中:
l Customer A网络中各业务的传输优先等级为:普通业务数据(VLAN10~VLAN20)最低,IP语音数据(VLAN21~VLAN30)较高,视讯数据(VLAN31~VLAN40)最高。
l Customer B网络中各业务的传输优先等级为:普通业务数据(VLAN15~VLAN25)最低,IP语音数据(VLAN26~VLAN35)较高,存储备份业务(VLAN36~VLAN40)最高。
l 运营商网络中根据报文的802.1p优先级作为传输优先等级的参考。
在网络中,使用不同的VLAN标签来区分业务数据是比较简单和常见的方式。在本例中,如果需要在运营商网络中既能实现各用户网络数据的隔离,又能区分每个用户的不同数据,则必须要为用户的各种业务数据封装不同的VLAN Tag,即配置灵活QinQ功能。
根据运营商网络中可用的VLAN资源,为两个用户分别分配3个VLAN用于灵活QinQ:
l 为Customer A分配VLAN1001、VLAN1002和VLAN1003,分配传输普通业务数据、IP语音数据和视讯数据
l 为Customer B分配VLAN2001、VLAN2002和VLAN2003,分配传输普通业务数据、IP语音数据和存储备份业务数据
经过VLAN分配后,各用户数据在运营商网络中的预期传输情况如图1-3所示:
图1-3 配置灵活QinQ后用户数据的传输情况
按以上的组网规划,需要在PE A和PE B设备的端口上进行以下配置:
l PE A:在GigabitEthernet1/0/1和GigabitEthernet1/0/2端口上配置灵活QinQ功能,分别为Customer A和Customer B的数据按业务不同封装不同的VLAN Tag。在GigabitEthernet1/0/3端口上允许为这两个用户封装的所有外层VLAN通过。
l PE B:在GigabitEthernet1/0/1和GigabitEthernet1/0/2端口上配置灵活QinQ功能,分别为Customer B和Customer A的数据按业务不同封装不同的VLAN Tag。在GigabitEthernet1/0/3端口上允许为这两个用户封装的所有外层VLAN通过。
产品 |
软件版本 |
S5500-EI系列以太网交换机 |
Release 2202,Release 2208 |
S5500-EI-D系列以太网交换机 |
Release 2208 |
S5500-SI系列以太网交换机 |
Release 2202 ,Release 2208 |
S5120-EI系列以太网交换机 |
Release 2202,Release 2208 |
S5120-EI-D系列以太网交换机 |
Release 1505 |
S5120-SI系列以太网交换机 |
Release 1101,Release 1505 |
S5120-LI系列以太网交换机 |
Release 1107 |
E552&E528以太网交换机 |
Release 1103 |
S3610&S5510系列以太网交换机 |
Release 5301,Release 5303,Release 5306,Release 5309 |
S3500-EA系列以太网交换机 |
Release 5303,Release 5309 |
S3100V2-EI系列以太网交换机 |
Release 5103 |
(1) Provider A的配置
# 创建为用户数据分配的VLAN,即VLAN1001~VLAN1003、VLAN2001~VLAN2003。
<PE_A> system-view
[PE_A] vlan 1001 to 1003
[PE_A] vlan 2001 to 2003
l GigabitEthernet1/0/1端口的配置
# 配置端口为Hybrid端口,允许VLAN1001~VLAN1003的报文通过,并且在发送时去掉外层Tag。
[PE_A] interface gigabitethernet 1/0/1
[PE_A-GigabitEthernet1/0/1] port link-type hybrid
[PE_A-GigabitEthernet1/0/1] port hybrid vlan 1001 to 1003 untagged
对于S3610/S5510/S3500-EA产品,对接入用户网络端口还需要进行以下配置:
l 如果PE设备使用的是S3610或S5510系列交换机的Release 5301版本,则在接入用户网络的端口上,还必须允许用户网络的VLAN通过。
l 如果PE设备使用的是S3610/S5510/S3500-EA系列交换机的的Release 5303及以上版本,可以在接入用户网络的端口上关闭VLAN检查功能(在端口视图下执行vlan-check disable命令),这样该端口即可以不必允许用户网络的私有VLAN通过。下文不再赘述。
# 在端口上配置灵活QinQ功能,为原始VLAN为VLAN10~VLAN20的报文封装VLAN1001的外层标签。
[PE_A-GigabitEthernet1/0/1] qinq vid 1001
[PE_A-GigabitEthernet1/0/1-vid-1001] raw-vlan-id inbound 10 to 20
[PE_A-GigabitEthernet1/0/1-vid-1001] quit
# 同样方法为原始VLAN为VLAN21~VLAN30和VLAN31~VLAN40的用户数据分别封装VLAN1002和VLAN1003的外层标签。
[PE_A-GigabitEthernet1/0/1] qinq vid 1002
[PE_A-GigabitEthernet1/0/1-vid-1002] raw-vlan-id inbound 21 to 30
[PE_A-GigabitEthernet1/0/1-vid-1002] quit
[PE_A-GigabitEthernet1/0/1] qinq vid 1003
[PE_A-GigabitEthernet1/0/1-vid-1003] raw-vlan-id inbound 31 to 40
[PE_A-GigabitEthernet1/0/1-vid-1003] quit
l GigabitEthernet1/0/2端口的配置
# 配置端口为Hybrid端口,允许VLAN2001~VLAN2003的报文通过,并且在发送时去掉外层Tag。
[PE_A] interface gigabitethernet 1/0/2
[PE_A-GigabitEthernet1/0/2] port link-type hybrid
[PE_A-GigabitEthernet1/0/2] port hybrid vlan 2001 to 2003 untagged
# 在端口上配置灵活QinQ功能,为原始VLAN为VLAN15~VLAN25的报文封装VLAN2001的外层标签。
[PE_A-GigabitEthernet1/0/2] qinq vid 2001
[PE_A-GigabitEthernet1/0/2-vid-2001] raw-vlan-id inbound 15 to 25
[PE_A-GigabitEthernet1/0/2-vid-2001] quit
# 同样方法为原始VLAN为VLAN26~VLAN35和VLAN36~VLAN40的用户数据分别封装VLAN2002和VLAN2003的外层标签。
[PE_A-GigabitEthernet1/0/2] qinq vid 2002
[PE_A-GigabitEthernet1/0/2-vid-2002] raw-vlan-id inbound 26 to 35
[PE_A-GigabitEthernet1/0/2-vid-2002] quit
[PE_A-GigabitEthernet1/0/2] qinq vid 2003
[PE_A-GigabitEthernet1/0/2-vid-2003] raw-vlan-id inbound 36 to 40
[PE_A-GigabitEthernet1/0/2-vid-2003] quit
l GigabitEthernet1/0/3端口的配置
# 配置端口为Trunk端口,且允许VLAN1001~VLAN1003和VLAN2001~VLAN2003的报文通过。
[PE_A] interface gigabitethernet 1/0/3
[PE_A-GigabitEthernet1/0/3] port link-type trunk
[PE_A-GigabitEthernet1/0/3] port trunk permit vlan 1001 to 1003 2001 to 2003
[PE_A-GigabitEthernet1/0/3] quit
l 调整不同业务数据的传输优先级(仅S5500-EI系列交换机支持)
调整报文的传输优先级主要通过QoS策略中的重标记功能来实现,为使运营商网络对不同VLAN报文能够采取不同的传输等级,需要重标记报文中的802.1p优先级。
# 创建流分类,匹配外层标签为VLAN1001或VALN2001的报文。
[PE_A] traffic classifier low_priority operator or
[PE_A-classifier-low_priority] if-match service-vlan-id 1001
[PE_A-classifier-low_priority] if-match service-vlan-id 2001
[PE_A-classifier-low_priority] quit
# 配置流行为,动作为将802.1p优先级重标记为2。
[PE_A]traffic behavior low_priority
[PE_A-behavior-low_priority] remark dot1p 2
[PE_A-behavior-low_priority] quit
# 按同样方法为外层标签为VLAN 1002或VLAN 2002以及外层标签为VLAN1003或VLAN2003的报文配置流分类和流行为,动作为将802.1p优先级重标记为4和6。
[PE_A] traffic classifier mid_priority operator or
[PE_A-classifier-mid_priority] if-match service-vlan-id 1002
[PE_A-classifier-mid_priority] if-match service-vlan-id 2002
[PE_A-classifier-mid_priority] quit
[PE_A] traffic behavior mid_priority
[PE_A-behavior-mid_priority] remark dot1p 4
[PE_A-behavior-mid_priority] quit
[PE_A] traffic classifier high_priority operator or
[PE_A-classifier-high_priority] if-match service-vlan-id 1003
[PE_A-classifier-high_priority] if-match service-vlan-id 2003
[PE_A-classifier-high_priority] quit
[PE_A] traffic behavior high_priority
[PE_A-behavior-high_priority] remark dot1p 6
[PE_A-behavior-high_priority] quit
# 创建重标记的QoS策略,将以上三对流分类和流行为分别进行关联。并将策略应用到GigabitEthernet1/0/3端口的出方向。
[PE_A] qos policy remark_priority
[PE_A-qospolicy-remark_priority] classifier low_priority behavior low_priority
[PE_A-qospolicy-remark_priority] classifier mid_priority behavior mid_priority
[PE_A-qospolicy-remark_priority] classifier high_priority behavior high_priority
[PE_A-qospolicy-remark_priority] quit
[PE_A] interface GigabitEthernet 1/0/3
[PE_A-GigabitEthernet1/0/3] qos apply policy remark_priority outbound
# 配置端口GigabitEthernet1/0/3信任报文的802.1p优先级,从而可以按照接收到的QinQ报文的802.1p优先级确定报文的传输优先等级。
[PE_A-GigabitEthernet1/0/3] qos trust dot1p
(2) Provider B的配置
# 创建为用户数据分配的VLAN,即VLAN1001~VLAN1003、VLAN2001~VLAN2003。
<PE_B> system-view
[PE_B] vlan 1001 to 1003
[PE_B] vlan 2001 to 2003
l GigabitEthernet1/0/1端口的配置
# 配置端口为Hybrid端口,允许VLAN2001~VLAN2003的报文通过,并且在发送时去掉外层Tag。
[PE_B] interface gigabitethernet 1/0/1
[PE_B-GigabitEthernet1/0/1] port link-type hybrid
[PE_B-GigabitEthernet1/0/1] port hybrid vlan 2001 to 2003 untagged
# 在端口上配置灵活QinQ功能,为原始VLAN为VLAN15~VLAN25的报文封装VLAN2001的外层标签。
[PE_B-GigabitEthernet1/0/1] qinq vid 2001
[PE_B-GigabitEthernet1/0/1-vid-2001] raw-vlan-id inbound 15 to 25
[PE_B-GigabitEthernet1/0/1-vid-2001] quit
# 同样方法为原始VLAN为VLAN26~VLAN35和VLAN36~VLAN40的用户数据分别封装VLAN2002和VLAN2003的外层标签。
[PE_B-GigabitEthernet1/0/1] qinq vid 2002
[PE_B-GigabitEthernet1/0/1-vid-2002] raw-vlan-id inbound 26 to 35
[PE_B-GigabitEthernet1/0/1-vid-2002] quit
[PE_B-GigabitEthernet1/0/1] qinq vid 2003
[PE_B-GigabitEthernet1/0/1-vid-2003] raw-vlan-id inbound 36 to 40
[PE_B-GigabitEthernet1/0/1-vid-2003] quit
l GigabitEthernet1/0/2端口的配置
# 配置端口为Hybrid端口,允许VLAN1001~VLAN1003的报文通过,并且在发送时去掉外层Tag。
[PE_B] interface gigabitethernet 1/0/2
[PE_B-GigabitEthernet1/0/2] port link-type hybrid
[PE_B-GigabitEthernet1/0/2] port hybrid vlan 1001 to 1003 untagged
# 在端口上配置灵活QinQ功能,为原始VLAN为VLAN10~VLAN20的报文封装VLAN1001的外层标签。
[PE_B-GigabitEthernet1/0/2] qinq vid 1001
[PE_B-GigabitEthernet1/0/2-vid-1001] raw-vlan-id inbound 10 to 20
[PE_B-GigabitEthernet1/0/2-vid-1001] quit
# 同样方法为原始VLAN为VLAN21~VLAN30和VLAN31~VLAN40的用户数据分别封装VLAN1002和VLAN1003的外层标签。
[PE_B-GigabitEthernet1/0/2] qinq vid 1002
[PE_B-GigabitEthernet1/0/2-vid-1002] raw-vlan-id inbound 21 to 30
[PE_B-GigabitEthernet1/0/2-vid-1002] quit
[PE_B-GigabitEthernet1/0/2] qinq vid 1003
[PE_B-GigabitEthernet1/0/2-vid-1003] raw-vlan-id inbound 31 to 40
[PE_B-GigabitEthernet1/0/2-vid-1003] quit
l GigabitEthernet1/0/3端口的配置
# 配置端口为Trunk端口,且允许VLAN1001~VLAN1003和VLAN2001~VLAN2003的报文通过。
[PE_B] interface gigabitethernet 1/0/3
[PE_B-GigabitEthernet1/0/3] port link-type trunk
[PE_B-GigabitEthernet1/0/3] port trunk permit vlan 1001 to 1003 2001 to 2003
l 调整不同业务数据的传输优先级(仅S5500-EI系列交换机支持)
# 在PE B上配置QoS策略,对不同外层标签的报文重标记802.1p优先级,并应用在GigabitEthernet1/0/3端口的出方向,以便运营商网络内的其它设备作为传输优先级参考。配置方法与PE A完全一致,这里不再赘述。
# 配置端口GigabitEthernet1/0/3信任报文的802.1p优先级,从而可以按照接收到的QinQ报文的802.1p优先级确定报文的传输优先等级。
[PE_B-GigabitEthernet1/0/3] qos trust dot1p
(3) 公共网络设备的配置
由于PE A和PE B之间使用的公共网络设备可能来自于其他厂商,这里只介绍配置项目,具体配置方式请参见产品的配置手册:
l 配置运营商网络中PE A到PE B之间的路径上的设备端口都允许VLAN1001~VLAN1003和VLAN2001~VLAN2003的报文携带VLAN Tag通过
l 要使PE设备为QinQ报文重标记的802.1p优先级在全网生效,需要在各设备传输QinQ报文使其能够按照802.1p优先级来确定报文的发送优先等级。
l PE_A的配置
#
vlan 1001 to 1003
#
vlan 2001 to 2003
#
traffic classifier low_priority operator or
if-match service-vlan-id 1003
if-match service-vlan-id 2003
traffic classifier high_priority operator or
if-match service-vlan-id 1001
if-match service-vlan-id 2001
traffic classifier mid_priority operator or
if-match service-vlan-id 1002
if-match service-vlan-id 2002
#
traffic behavior low_priority
remark dot1p 6
traffic behavior high_priority
remark dot1p 2
traffic behavior mid_priority
remark dot1p 4
#
qos policy remark_priority
classifier low_priority behavior low_priority
classifier mid_priority behavior mid_priority
classifier high_priority behavior high_priority
#
interface GigabitEthernet1/0/1
port link-type hybrid
port hybrid vlan 1 1001 to 1003 untagged
qinq vid 1001
raw-vlan-id inbound 10 to 20
qinq vid 1002
raw-vlan-id inbound 21 to 30
qinq vid 1003
raw-vlan-id inbound 31 to 40
#
interface GigabitEthernet1/0/2
port link-type hybrid
port hybrid vlan 1 2001 to 2003 untagged
qinq vid 2001
raw-vlan-id inbound 15 to 25
qinq vid 2002
raw-vlan-id inbound 26 to 35
qinq vid 2003
raw-vlan-id inbound 36 to 40
#
interface GigabitEthernet1/0/3
port link-type trunk
port trunk permit vlan 1 1001 to 1003 2001 to 2003
qos apply policy remark_priority outbound
qos trust dot1p
l ProviderB的配置
#
vlan 1001 to 1003
#
vlan 2001 to 2003
#
#
traffic classifier low_priority operator or
if-match service-vlan-id 1003
if-match service-vlan-id 2003
traffic classifier high_priority operator or
if-match service-vlan-id 1001
if-match service-vlan-id 2001
traffic classifier mid_priority operator or
if-match service-vlan-id 1002
if-match service-vlan-id 2002
#
traffic behavior low_priority
remark dot1p 6
traffic behavior high_priority
remark dot1p 2
traffic behavior mid_priority
remark dot1p 4
#
qos policy remark_priority
classifier low_priority behavior low_priority
classifier mid_priority behavior mid_priority
classifier high_priority behavior high_priority
#
interface GigabitEthernet1/0/1
port link-type hybrid
port hybrid vlan 1 2001 to 2003 untagged
qinq vid 2001
raw-vlan-id inbound 15 to 25
qinq vid 2002
raw-vlan-id inbound 26 to 35
qinq vid 2003
raw-vlan-id inbound 36 to 40
#
interface GigabitEthernet1/0/2
port link-type hybrid
port hybrid vlan 1 1001 to 1003 untagged
qinq vid 1001
raw-vlan-id inbound 10 to 20
qinq vid 1002
raw-vlan-id inbound 21 to 30
qinq vid 1003
raw-vlan-id inbound 31 to 40
#
interface GigabitEthernet1/0/3
port link-type trunk
port trunk permit vlan 1 1001 to 1003 2001 to 2003
qos apply policy remark_priority outbound
qos trust dot1p
l 缺省情况下,设备为报文封装外层标签时使用的802.1p优先级为接收端口的端口优先级。
l 对于除S5500-EI以外的设备,如果需要在本地重标记QinQ报文的优先级,请使用基于QoS策略配置的QinQ功能。
l 在S3610/S5510/S3500-EA系列交换机上,基本QinQ和灵活QinQ功能不能一个端口上同时配置,且不能在镜像反射口上配置灵活QinQ功能;在表1-2中所列的其它系列交换机上,基本QinQ和灵活QinQ功能可以同时配置。在端口同时配置了这两种功能时,满足灵活QinQ配置的报文将按灵活QinQ处理,不满足灵活QinQ配置的报文将按基本QinQ处理。
l 一个内层VLAN Tag只能对应一个外层VLAN Tag。如果用户想改变报文的外层VLAN Tag,需要先删除旧的外层VLAN Tag配置,然后再配置新的外层VLAN Tag。
基本QinQ功能可以确保各个用户网络的数据在运营商网络传输时相互隔离,但具有一定的局限性。由于每个端口只能为接收的所有报文封装同样的外层标签,因此对于用户网络中使用不同VLAN来区分的不同业务数据,在运营商网络中就无法进行区分,也就无法针对不同业务进行网络资源的分配和优化。
使用灵活QinQ功能可以解决这个问题,它对基本QinQ的功能进行了扩展,对同一端口接收的报文,可以根据用户网络VLAN的不同来为其封装不同的外层VLAN Tag。
图1-4 灵活QinQ组网示意图(基于QoS策略配置)
Customer A和Customer B各有两个分支机构需要通过运营商网络进行通信,如图1-2所示。现要求运营商网络能够通过QinQ方式使用户的分支机构间进行数据传输,并能够针对用户网络中用VLAN来标识的各种业务数据,在运营商网络中提供相应的差别服务,使优先级高的业务得到优先传输。其中:
l Customer A网络中各业务的传输优先等级为:普通业务数据(VLAN10~VLAN20)最低,IP语音数据(VLAN21~VLAN30)较高,视讯数据(VLAN31~VLAN40)最高。
l Customer B网络中各业务的传输优先等级为:普通业务数据(VLAN15~VLAN25)最低,IP语音数据(VLAN26~VLAN35)较高,存储备份业务(VLAN36~VLAN40)最高。
在网络中,使用不同的VLAN标签来区分业务数据是比较简单和常见的方式。在本例中,如果需要在运营商网络中既能实现各用户网络数据的隔离,又能区分每个用户的不同数据,则必须要为用户的各种业务数据封装不同的VLAN Tag,即配置灵活QinQ功能。
根据运营商网络中可用的VLAN资源,为两个用户分别分配3个VLAN用于灵活QinQ:
l 为Customer A分配VLAN1001、VLAN1002和VLAN1003,分配传输普通业务数据、IP语音数据和视讯数据
l 为Customer B分配VLAN2001、VLAN2002和VLAN2003,分配传输普通业务数据、IP语音数据和存储备份业务数据
经过VLAN分配后,各用户数据在运营商网络中的预期传输情况如图1-3所示:
图1-5 配置灵活QinQ后用户数据的传输情况
按以上的组网规划,需要在PE A和PE B设备的端口上进行以下配置:
l PE A:为Customer A创建用于灵活QinQ的QoS策略,流分类为匹配用户不同业务的原始VLAN,流行为为封装为用户业务分配的外层VLAN,将该策略应用到GigabitEthernet1/0/1端口的入方向,同理为Customer B创建QoS策略并应用到GigabitEthernet1/0/2端口的入方向。在GigabitEthernet1/0/3端口上允许为这两个用户封装的所有外层VLAN通过。
l PE B:为Customer A创建用于灵活QinQ的QoS策略,流分类为匹配用户不同业务的原始VLAN,流行为为封装为用户业务分配的外层VLAN,将该策略应用到GigabitEthernet1/0/2端口的入方向,同理为Customer B创建QoS策略并应用到GigabitEthernet1/0/1端口的入方向。在GigabitEthernet1/0/3端口上允许为这两个用户封装的所有外层VLAN通过。
表1-3 配置适用的产品与软件版本关系
产品 |
软件版本 |
S7500E系列以太网交换机 |
Release 6100系列,Release 6300系列,Release 6600系列,Release 6610系列 |
S7600系列以太网交换机 |
Release 6600系列,Release 6610系列 |
S5800&S5820X系列以太网交换机 |
Release 1110,Release 1211 |
CE3000-32F以太网交换机 |
Release 1211 |
S5500-EI系列以太网交换机 |
Release 2202,Release 2208 |
S5500-EI-D系列以太网交换机 |
Release 2208 |
S5500-SI系列以太网交换机 |
Release 2202 ,Release 2208 |
S5120-EI系列以太网交换机 |
Release 2202,Release 2208 |
S3610&S5510系列以太网交换机 |
Release 5301,Release 5303,Release 5306,Release 5309 |
S3500-EA系列以太网交换机 |
Release 5303,Release 5309 |
S3100V2-EI系列以太网交换机 |
Release 5103 |
(1) Provider A的配置
# 创建为用户数据分配的VLAN,即VLAN1001~VLAN1003、VLAN2001~VLAN2003。
<PE_A> system-view
[PE_A] vlan 1001 to 1003
[PE_A] vlan 2001 to 2003
l GigabitEthernet1/0/1端口的配置
# 配置端口为Hybrid端口,允许VLAN1001~VLAN1003的报文通过,并且在发送时去掉外层Tag。
[PE_A] interface gigabitethernet 1/0/1
[PE_A-GigabitEthernet1/0/1] port link-type hybrid
[PE_A-GigabitEthernet1/0/1] port hybrid vlan 1001 to 1003 untagged
对于S3610/S5510/S3500-EA产品,对接入用户网络端口还需要进行以下配置:
l 如果PE设备使用的是S3610或S5510系列交换机的Release 5301版本,则在接入用户网络的端口上,还必须允许用户网络的VLAN通过。
l 如果PE设备使用的是S3610/S5510/S3500-EA系列交换机的的Release 5303及以上版本,可以在接入用户网络的端口上关闭VLAN检查功能(在端口视图下执行vlan-check disable命令),这样该端口即可以不必允许用户网络的私有VLAN通过。下文不再赘述。
# 开启该端口的基本QinQ功能。
[PE_A-GigabitEthernet1/0/1] qinq enable
l GigabitEthernet1/0/2端口的配置
# 配置端口为Hybrid端口,允许VLAN2001~VLAN2003的报文通过,并且在发送时去掉外层Tag。
[PE_A] interface gigabitethernet 1/0/2
[PE_A-GigabitEthernet1/0/2] port link-type hybrid
[PE_A-GigabitEthernet1/0/2] port hybrid vlan 2001 to 2003 untagged
# 开启该端口的基本QinQ功能。
[PE_A-GigabitEthernet1/0/2] qinq enable
l GigabitEthernet1/0/3端口的配置
# 配置端口为Trunk端口,且允许VLAN1001~VLAN1003和VLAN2001~VLAN2003的报文通过。
[PE_A] interface gigabitethernet 1/0/3
[PE_A-GigabitEthernet1/0/3] port link-type trunk
[PE_A-GigabitEthernet1/0/3] port trunk permit vlan 1001 to 1003 2001 to 2003
[PE_A-GigabitEthernet1/0/3] quit
l QoS策略的配置
# 为Customer A创建一个流分类,匹配规则为用户网络中普通业务数据对应的VLAN。
[PE_A] traffic classifier customer_A_pc
[PE_A-classifier-customer_A_pc] if-match customer-vlan-id 10 to 20
[PE_A-classifier-customer_A_pc] quit
# 按同样方法创建匹配Customer A网络中语音数据和视讯数据的流分类。
[PE_A] traffic classifier customer_A_voice
[PE_A-classifier-customer_A_voice] if-match customer-vlan-id 21 to 30
[PE_A-classifier-customer_A_voice] quit
[PE_A] traffic classifier customer_A_video
[PE_A-classifier-customer_A_video] if-match customer-vlan-id 31 to 40
[PE_A-classifier-customer_A_video] quit
# 为Customer A的三种业务数据创建三个流行为,动作为封装相应的外层VLAN。
[PE_A] traffic behavior customer_A_pc
[PE_A-behavior-customer_A_pc] nest top-most vlan-id 1001
[PE_A-behavior-customer_A_pc] quit
[PE_A] traffic behavior customer_A_voice
[PE_A-behavior-customer_A_voice] nest top-most vlan-id 1002
[PE_A-behavior-customer_A_voice] quit
[PE_A] traffic behavior customer_A_video
[PE_A-behavior-customer_A_video] nest top-most vlan-id 1003
[PE_A-behavior-customer_A_video] quit
# 创建用于Customer A的QoS策略,将匹配用户业务数据的流分类与封装相应外层VLAN的流行为进行一一关联。
[PE_A] qos policy customer_A
[PE_A-qospolicy-customer_A] classifier customer_A_pc behavior customer_A_pc
[PE_A-qospolicy-customer_A] classifier customer_A_voice behavior customer_A_voice
[PE_A-qospolicy-customer_A] classifier customer_A_video behavior customer_A_video
[PE_A-qospolicy-customer_A] quit
# 将上面创建的策略应用到GigabitEthernet 1/0/1端口的入方向。
[PE_A] interface gigabitethernet 1/0/1
[PE_A-GigabitEthernet1/0/1] qos apply policy customer_A inbound
# 使用类似方法为Customer B的三种业务数据创建流分类。
[PE_A] traffic classifier customer_B_pc
[PE_A-classifier-customer_B_pc] if-match customer-vlan-id 15 to 25
[PE_A-classifier-customer_B_pc] quit
[PE_A] traffic classifier customer_B_voice
[PE_A-classifier-customer_B_voice] if-match customer-vlan-id 26 to 35
[PE_A-classifier-customer_B_voice] quit
[PE_A] traffic classifier customer_B_storage
[PE_A-classifier-customer_B_storage] if-match customer-vlan-id 36 to 40
[PE_A-classifier-customer_B_storage] quit
#为Customer B的三种业务数据创建三个流行为,动作为封装相应的外层VLAN。
[PE_A] traffic behavior customer_B_pc
[PE_A-behavior-customer_B_pc] nest top-most vlan-id 2001
[PE_A-behavior-customer_B_pc] quit
[PE_A] traffic behavior customer_B_voice
[PE_A-behavior-customer_B_voice] nest top-most vlan-id 2002
[PE_A-behavior-customer_B_voice] quit
[PE_A] traffic behavior customer_B_storage
[PE_A-behavior-customer_B_storage] nest top-most vlan-id 2003
[PE_A-behavior-customer_B_storage] quit
# 创建用于Customer B的QoS策略,将匹配用户业务数据的流分类与封装相应外层VLAN的流行为进行一一关联。
[PE_A] qos policy customer_B
[PE_A-qospolicy-customer_B] classifier customer_B_pc behavior customer_B_pc
[PE_A-qospolicy-customer_B] classifier customer_B_voice behavior customer_B_voice
[PE_A-qospolicy-customer_B] classifier customer_B_storage behavior customer_B_storage
[PE_A-qospolicy-customer_B] quit
# 将上面创建的策略应用到GigabitEthernet 1/0/2端口的入方向。
[PE_A] interface gigabitethernet 1/0/2
[PE_A-GigabitEthernet1/0/2] qos apply policy customer_B inbound
(2) Provider B的配置
# 创建为用户数据分配的VLAN,即VLAN1001~VLAN1003、VLAN2001~VLAN2003。
<PE_B> system-view
[PE_B] vlan 1001 to 1003
[PE_B] vlan 2001 to 2003
l GigabitEthernet1/0/1端口的配置
# 配置端口为Hybrid端口,允许VLAN2001~VLAN2003的报文通过,并且在发送时去掉外层Tag。
[PE_B] interface gigabitethernet 1/0/1
[PE_B-GigabitEthernet1/0/1] port link-type hybrid
[PE_B-GigabitEthernet1/0/1] port hybrid vlan 2001 to 2003 untagged
# 开启该端口的基本QinQ功能。
[PE_B-GigabitEthernet1/0/1] qinq enable
l GigabitEthernet1/0/2端口的配置
# 配置端口为Hybrid端口,允许VLAN1001~VLAN1003的报文通过,并且在发送时去掉外层Tag。
[PE_B] interface gigabitethernet 1/0/2
[PE_B-GigabitEthernet1/0/2] port link-type hybrid
[PE_B-GigabitEthernet1/0/2] port hybrid vlan 1001 to 1003 untagged
# 开启该端口的基本QinQ功能。
[PE_B-GigabitEthernet1/0/2] qinq enable
l GigabitEthernet1/0/3端口的配置
# 配置端口为Trunk端口,且允许VLAN1001~VLAN1003和VLAN2001~VLAN2003的报文通过。
[PE_B] interface gigabitethernet 1/0/3
[PE_B-GigabitEthernet1/0/3] port link-type trunk
[PE_B-GigabitEthernet1/0/3] port trunk permit vlan 1001 to 1003 2001 to 2003
l QoS策略的配置
# 按PE A设备的配置方法,为Customer A的业务数据配置流分类。
[PE_B] traffic classifier customer_A_pc
[PE_B-classifier-customer_A_pc] if-match customer-vlan-id 10 to 20
[PE_B-classifier-customer_A_pc] quit
[PE_B] traffic classifier customer_A_voice
[PE_B-classifier-customer_A_voice] if-match customer-vlan-id 21 to 30
[PE_B-classifier-customer_A_voice] quit
[PE_B] traffic classifier customer_A_video
[PE_B-classifier-customer_A_video] if-match customer-vlan-id 31 to 40
[PE_B-classifier-customer_A_video] quit
# 为Customer A的三种业务数据创建三个流行为,动作为封装相应的外层VLAN。
[PE_B] traffic behavior customer_A_pc
[PE_B-behavior-customer_A_pc] nest top-most vlan-id 1001
[PE_B-behavior-customer_A_pc] quit
[PE_B] traffic behavior customer_A_voice
[PE_B-behavior-customer_A_voice] nest top-most vlan-id 1002
[PE_B-behavior-customer_A_voice] quit
[PE_B] traffic behavior customer_A_video
[PE_B-behavior-customer_A_video] nest top-most vlan-id 1003
[PE_B-behavior-customer_A_video] quit
# 创建用于Customer A的QoS策略,将匹配用户业务数据的流分类与封装相应外层VLAN的流行为进行一一关联。
[PE_B] qos policy customer_A
[PE_B-qospolicy-customer_A] classifier customer_A_pc behavior customer_A_pc
[PE_B-qospolicy-customer_A] classifier customer_A_voice behavior customer_A_voice
[PE_B-qospolicy-customer_A] classifier customer_A_video behavior customer_A_video
[PE_B-qospolicy-customer_A] quit
# 将上面创建的策略应用到GigabitEthernet 1/0/2端口的入方向。
[PE_B] interface gigabitethernet 1/0/2
[PE_B-GigabitEthernet1/0/2] qos apply policy customer_A inbound
# 使用类似方法为Customer B的三种业务数据创建流分类。
[PE_B] traffic classifier customer_B_pc
[PE_B-classifier-customer_B_pc] if-match customer-vlan-id 15 to 25
[PE_B-classifier-customer_B_pc] quit
[PE_B] traffic classifier customer_B_voice
[PE_B-classifier-customer_B_voice] if-match customer-vlan-id 26 to 35
[PE_B-classifier-customer_B_voice] quit
[PE_B] traffic classifier customer_B_storage
[PE_B-classifier-customer_B_storage] if-match customer-vlan-id 36 to 40
[PE_B-classifier-customer_B_storage] quit
#为Customer B的三种业务数据创建三个流行为,动作为封装相应的外层VLAN。
[PE_B] traffic behavior customer_B_pc
[PE_B-behavior-customer_B_pc] nest top-most vlan-id 2001
[PE_B-behavior-customer_B_pc] quit
[PE_B] traffic behavior customer_B_voice
[PE_B-behavior-customer_B_voice] nest top-most vlan-id 2002
[PE_B-behavior-customer_B_voice] quit
[PE_B] traffic behavior customer_B_storage
[PE_B-behavior-customer_B_storage] nest top-most vlan-id 2003
[PE_B-behavior-customer_B_storage] quit
# 创建用于Customer B的QoS策略,将匹配用户业务数据的流分类与封装相应外层VLAN的流行为进行一一关联。
[PE_B] qos policy customer_B
[PE_B-qospolicy-customer_B] classifier customer_B_pc behavior customer_B_pc
[PE_B-qospolicy-customer_B] classifier customer_B_voice behavior customer_B_voice
[PE_B-qospolicy-customer_B] classifier customer_B_storage behavior customer_B_storage
[PE_B-qospolicy-customer_B] quit
# 将上面创建的策略应用到GigabitEthernet 1/0/1端口的入方向。
[PE_B] interface gigabitethernet 1/0/1
[PE_B-GigabitEthernet1/0/1] qos apply policy customer_B inbound
(3) 公共网络设备的配置
由于PE A和PE B之间使用的公共网络设备可能来自于其他厂商,这里只介绍基本原理:配置运营商网络中PE A到PE B之间的路径上的设备端口都允许VLAN1001~VLAN1003和VLAN2001~VLAN2003的报文携带VLAN Tag通过即可。
l PE_A的配置
#
vlan 1001 to 1003
#
vlan 2001 to 2003
#
traffic classifier customer_A_pc operator and
if-match customer-vlan-id 10 to 20
traffic classifier customer_A_voice operator and
if-match customer-vlan-id 21 to 30
traffic classifier customer_A_video operator and
if-match customer-vlan-id 31 to 40
traffic classifier customer_B_pc operator and
if-match customer-vlan-id 15 to 25
traffic classifier customer_B_voice operator and
if-match customer-vlan-id 26 to 35
traffic classifier customer_B_storage operator and
if-match customer-vlan-id 36 to 40 #
#
traffic behavior customer_A_pc
nest top-most vlan-id 1001
traffic behavior customer_A_voice
nest top-most vlan-id 1002
traffic behavior customer_A_video
nest top-most vlan-id 1003
traffic behavior customer_B_pc
nest top-most vlan-id 2001
traffic behavior customer_B_voice
nest top-most vlan-id 2002
traffic behavior customer_B_storage
nest top-most vlan-id 2003
#
qos policy customer_A
classifier customer_A_pc behavior customer_A_pc
classifier customer_A_voice behavior customer_A_voice
classifier customer_A_video behavior customer_A_video
qos policy customer_B
classifier customer_B_pc behavior customer_B_pc
classifier customer_B_voice behavior customer_B_voice
classifier customer_B_storage behavior customer_B_storage
interface GigabitEthernet1/0/1
port link-type hybrid
port hybrid vlan 1 1001 to 1003 untagged
qinq enable
qos apply policy customer_A inbound
#
interface GigabitEthernet1/0/2
port link-type hybrid
port hybrid vlan 1 2001 to 2003 untagged
qinq enable
qos apply policy customer_B inbound
#
interface GigabitEthernet1/0/3
port link-type trunk
port trunk permit vlan 1 1001 to 1003 2001 to 2003
l ProviderB的配置
#
vlan 1001 to 1003
#
vlan 2001 to 2003
#
traffic classifier customer_A_pc operator and
if-match customer-vlan-id 10 to 20
traffic classifier customer_A_voice operator and
if-match customer-vlan-id 21 to 30
traffic classifier customer_A_video operator and
if-match customer-vlan-id 31 to 40
traffic classifier customer_B_pc operator and
if-match customer-vlan-id 15 to 25
traffic classifier customer_B_voice operator and
if-match customer-vlan-id 26 to 35
traffic classifier customer_B_storage operator and
if-match customer-vlan-id 36 to 40 #
#
traffic behavior customer_A_pc
nest top-most vlan-id 1001
traffic behavior customer_A_voice
nest top-most vlan-id 1002
traffic behavior customer_A_video
nest top-most vlan-id 1003
traffic behavior customer_B_pc
nest top-most vlan-id 2001
traffic behavior customer_B_voice
nest top-most vlan-id 2002
traffic behavior customer_B_storage
nest top-most vlan-id 2003
#
qos policy customer_A
classifier customer_A_pc behavior customer_A_pc
classifier customer_A_voice behavior customer_A_voice
classifier customer_A_video behavior customer_A_video
qos policy customer_B
classifier customer_B_pc behavior customer_B_pc
classifier customer_B_voice behavior customer_B_voice
classifier customer_B_storage behavior customer_B_storage
interface GigabitEthernet1/0/1
port link-type hybrid
port hybrid vlan 1 2001 to 2003 untagged
qinq enable
qos apply policy customer_B inbound
#
interface GigabitEthernet1/0/2
port link-type hybrid
port hybrid vlan 1 1001 to 1003 untagged
qinq enable
qos apply policy customer_A inbound
#
interface GigabitEthernet1/0/3
port link-type trunk
port trunk permit vlan 1 1001 to 1003 2001 to 2003
当配置了灵活QinQ的端口接收到报文时,满足灵活QinQ配置的报文将按灵活QinQ处理,不满足灵活QinQ配置的报文将按基本QinQ处理。
不同款型规格的资料略有差异, 详细信息请向具体销售和400咨询。H3C保留在没有任何通知或提示的情况下对资料内容进行修改的权利!