H3C SR8800 IM-FW-II User manual
H3C SR8800 10G Core Routers
Layer 2—LAN Switching Configuration Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Software version: SR8800-CMW520-R3347
Document version: 6W103-20120224
Copyright © 2011-2012, Hangzhou H3C Technologies Co., Ltd. and its licensors
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 Hangzhou H3C Technologies Co., Ltd.
Trademarks
H3C, , Aolynk, , H3Care, , TOP G, , IRF, NetPilot, Neocean, NeoVTL,
SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V2G, VnG, PSPT,
XGbus, N-Bus, TiGem, InnoVision and HUASAN are trademarks of Hangzhou H3C Technologies Co.,
Ltd.
All other trademarks that may be mentioned in this manual are the property of their respective owners
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Preface
The H3C SR8800 documentation set includes 13 configuration guides, which describe the software
features for the H3C SR8800 10G Core Routers and guide you through the software configuration
procedures. These configuration guides also provide configuration examples to help you apply software
features to different network scenarios.
The Layer 2—LAN Switching Configuration Guide describes the fundamentals and configuration of
Ethernet link aggregation, port isolation, spanning tree, VLAN, and so on. It describes how you can use
these technologies to isolate users in the same VLAN, eliminate Layer 2 loops, divide VLANs, transmit
customer network packets through the service provider network, modify the VLAN tags of packets, and
so on.
This preface includes:
•Audience
•Conventions
•About the H3C SR8800 documentation set
•Obtaining documentation
•Technical support
•Documentation feedback
Audience
This documentation is intended for:
•Network planners
•Field technical support and servicing engineers
•Network administrators working with the SR8800 series
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Descri
p
tion
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars, from
which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select at least one.
Convention Descri
p
tion
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign can
be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Convention Descri
p
tion
Boldface Window names, button names, field names, and menu items are in Boldface. For
example, the New User window appears; click OK.
> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.
Symbols
Convention Descri
p
tion
WARNING An alert that calls attention to important information that if not understood or followed can
result in personal injury.
CAUTION An alert that calls attention to important information that if not understood or followed can
result in data loss, data corruption, or damage to hardware or software.
IMPORTANT An alert that calls attention to essential information.
NOTE An alert that contains additional or supplementary information.
TIP An alert that provides helpful information.
Network topology icons
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports
Layer 2 forwarding and other Layer 2 features.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your router.
About the H3C SR8800 documentation set
The H3C SR8800 documentation set includes:
Cate
g
or
y
Documents
Pur
p
oses
Product description and Marketing brochures Describe product specifications and benefits.
Cate
g
or
y
Documents
Pur
p
oses
specifications
Technology white papers
Provide an in-depth description of software features
and technologies.
Card datasheets Describe card specifications, features, and standards.
Hardware specifications
and installation
Compliance and safety
manual
Provides regulatory information and the safety
instructions that must be followed during installation.
Installation guide Provides a complete guide to hardware installation
and hardware specifications.
H3C N68 Cabinet
Installation and Remodel
Introduction
Guides you through installing and remodeling H3C
N68 cabinets.
H3C Pluggable SFP
[SFP+][XFP] Transceiver
Modules Installation
Guide
Guides you through installing SFP/SFP+/XFP
transceiver modules.
H3C High-End Network
Products Hot-Swappable
Module Manual
Describes the hot-swappable modules available for
the H3C high-end network products, their external
views, and specifications.
Software configuration Configuration guides Describe software features and configuration
procedures.
Command references Provide a quick reference to all available commands.
Operations and
maintenance Release notes
Provide information about the product release,
including the version history, hardware and software
compatibility matrix, version upgrade information,
technical support information, and software
upgrading.
Obtaining documentation
You can access the most up-to-date H3C product documentation on the World Wide Web
at http://www.h3c.com.
Click the links on the top navigation bar to obtain different categories of product documentation:
[Technical Support & Documents > Technical Documents] – Provides hardware installation, software
upgrading, and software feature configuration and maintenance documentation.
[Products & Solutions] – Provides information about products and technologies, as well as solutions.
[Technical Support & Documents > Software Download] – Provides the documentation released with the
software version.
Technical support
servi[email protected]
http://www.h3c.com
Documentation feedback
We appreciate your comments.
i
Contents
Configuring VLANs······················································································································································ 1
Introduction to VLAN ························································································································································1
VLAN overview·························································································································································1
VLAN fundamentals··················································································································································2
VLAN types ·······························································································································································3
Protocols and standards ··········································································································································3
Configuring basic VLAN settings·····································································································································3
Configure basic settings of a VLAN interface················································································································4
VLAN interface overview·········································································································································4
Configuration procedure ·········································································································································4
VLAN interface configuration example··················································································································5
Configuring port-based VLANs········································································································································6
Introduction to port-based VLAN ····························································································································6
Assigning an access port to a VLAN ·····················································································································8
Assigning a trunk port to a VLAN···························································································································9
Assigning a hybrid port to a VLAN····················································································································· 10
Port-based VLAN configuration example············································································································ 11
MAC-based VLAN configuration·································································································································· 13
Introduction to MAC-based VLAN ······················································································································· 13
Configuring a MAC-based VLAN························································································································ 14
MAC-based VLAN configuration example ········································································································· 15
Displaying and maintaining VLANs····························································································································· 18
MAC address table configuration ····························································································································19
Overview········································································································································································· 19
How a MAC address table entry is created······································································································· 19
Types of MAC address table entries ··················································································································· 20
MAC address table-based frame forwarding ···································································································· 20
Configuring the MAC address table···························································································································· 20
Configuring MAC address table entries ············································································································· 20
Disabling MAC address learning························································································································ 21
Configuring the aging timer for dynamic MAC address entries······································································ 22
Configuring the MAC learning limit···················································································································· 23
Displaying and maintaining MAC address tables ····································································································· 24
MAC address table configuration example ················································································································ 24
Configuring the spanning tree ··································································································································26
STP ··················································································································································································· 26
STP protocol packets ············································································································································· 26
Basic concepts in STP············································································································································ 27
Calculation process of the STP algorithm ··········································································································· 28
RSTP················································································································································································· 33
MSTP················································································································································································ 33
STP and RSTP limitations······································································································································· 33
MSTP features ························································································································································ 33
MSTP basic concepts ············································································································································ 34
How MSTP works ·················································································································································· 37
Implementation of MSTP on routers····················································································································· 38
Protocols and standards ················································································································································ 38
Spanning tree configuration task list···························································································································· 38
ii
Configuring the spanning tree······································································································································ 41
Setting the spanning tree mode ··························································································································· 41
Configuring an MST region ································································································································· 42
Configuring the root bridge or a secondary root bridge·················································································· 43
Configuring the device priority···························································································································· 44
Configuring the maximum hops of an MST region ··························································································· 44
Configuring the network diameter of a switched network················································································ 45
Configuring spanning tree timers ························································································································ 45
Configuring the timeout factor ····························································································································· 46
Configuring the maximum port rate ···················································································································· 47
Configuring edge ports········································································································································· 47
Configuring path costs of ports···························································································································· 48
Configuring the port priority ································································································································ 50
Configuring the port link type ······························································································································ 51
Configuring the mode a port uses to recognize/send MSTP packets ····························································· 52
Enabling the spanning tree feature ····················································································································· 52
Performing mCheck··············································································································································· 53
Configuring the VLAN Ignore feature ················································································································· 54
Configuring Digest Snooping······························································································································· 55
Configuring No Agreement Check······················································································································ 57
Configuring protection functions·························································································································· 59
Displaying and maintaining the spanning tree··········································································································· 62
MSTP configuration example········································································································································ 63
Configuring Ethernet link aggregation ·····················································································································67
Overview········································································································································································· 67
Basic concepts ······················································································································································· 67
Aggregating links in static mode························································································································· 70
Aggregating links in dynamic mode ··················································································································· 72
Load sharing criteria for link aggregation groups····························································································· 74
Ethernet link aggregation configuration task list········································································································· 74
Configuring an aggregation group ····························································································································· 74
Configuration guidelines ······································································································································ 74
Configuring a static aggregation group············································································································· 75
Configuring a dynamic aggregation group······································································································· 77
Configuring an aggregate interface ···························································································································· 79
Configuring the description of an aggregate interface or subinterface·························································· 79
Configuring the MTU of a Layer 3 aggregate interface or subinterface························································· 80
Enabling link state traps for an aggregate interface ························································································· 80
Setting the minimum number of Selected ports for an aggregation group ····················································· 81
Shutting down an aggregate interface ··············································································································· 82
Restoring the default settings for an aggregate interface ················································································· 82
Configuring load sharing criteria for link aggregation groups················································································· 83
Displaying and maintaining Ethernet link aggregation ····························································································· 83
Ethernet link aggregation configuration examples····································································································· 84
Layer 2 static aggregation configuration example···························································································· 84
Layer 2 dynamic aggregation configuration example······················································································ 86
Layer 3 static aggregation configuration example···························································································· 88
Layer 3 dynamic aggregation configuration example······················································································ 89
Configuring port isolation··········································································································································91
Introduction to port isolation ········································································································································· 91
Configuring an isolation group ···································································································································· 92
Assigning ports to an isolation group ················································································································· 92
Specifying the uplink port for an isolation group ······························································································ 92
iii
Displaying and maintaining isolation groups ············································································································· 93
Port isolation configuration example···························································································································· 93
Configuring QinQ······················································································································································95
Introduction to QinQ······················································································································································ 95
Background and benefits······································································································································ 95
How QinQ works·················································································································································· 95
QinQ frame structure ············································································································································ 96
Implementations of QinQ ····································································································································· 97
Modifying the TPID value in a VLAN tag············································································································ 97
Protocols and standards ······································································································································· 98
QinQ configuration task list·········································································································································· 98
Configuring basic QinQ ··············································································································································· 98
Setting the TPID value in VLAN tags ···························································································································· 99
Basic QinQ configuration example ····························································································································· 99
Configuring BPDU tunneling··································································································································· 102
Introduction to BPDU tunneling ···································································································································102
Background··························································································································································102
BPDU Tunneling implementation························································································································103
Configuring BPDU tunneling ·······································································································································104
Configuration prerequisites ································································································································104
Enabling BPDU tunneling for a protocol ···········································································································104
Configuring destination multicast MAC address for BPDUs ···········································································105
BPDU tunneling configuration example ·····················································································································105
Configuring GVRP··················································································································································· 107
Introduction to GVRP····················································································································································107
GARP ····································································································································································107
GVRP·····································································································································································110
Protocols and standards ·····································································································································111
GVRP configuration task list········································································································································111
Configuring GVRP functions········································································································································111
Configuring GARP timers ············································································································································112
Displaying and maintaining GVRP·····························································································································113
GVRP configuration examples ····································································································································114
GVRP normal registration mode configuration example·················································································114
GVRP fixed registration mode configuration example ····················································································115
GVRP forbidden registration mode configuration example············································································117
Configuring VLAN termination······························································································································· 119
Overview·······································································································································································119
Introduction to VLAN termination ······················································································································119
VLAN termination types ······································································································································119
Application scenarios ·········································································································································119
VLAN termination configuration task list ···················································································································121
Configuring TPID for VLAN-tagged packets··············································································································121
Configuring TPID on a Layer 3 Ethernet/aggregate subinterface ·································································123
Configuring TPID on a Layer 2 Ethernet or aggregate interface····································································123
Enabling a QinQ termination-enabled interface/subinterface to transmit broadcast and multicast packets ····124
Configuring QinQ termination ···································································································································125
Configuring unambiguous QinQ termination ··································································································125
Configuring ambiguous QinQ termination·······································································································126
VLAN termination configuration examples················································································································126
Unambiguous QinQ termination configuration example················································································126
Ambiguous QinQ termination configuration example ····················································································128
iv
Configuration example for QinQ termination supporting DHCP relay ·························································130
Configuring LLDP····················································································································································· 133
Overview·······································································································································································133
Background··························································································································································133
Basic concepts ·····················································································································································133
How LLDP works ··················································································································································137
Protocols and standards ·····································································································································137
LLDP configuration task list ··········································································································································137
Performing basic LLDP configuration··························································································································138
Enabling LLDP ······················································································································································138
Setting LLDP operating mode ·····························································································································138
Setting the LLDP re-initialization delay ··············································································································139
Enable LLDP polling·············································································································································139
Configuring the advertisable TLVs ·····················································································································140
Configuring the management address and its encoding format····································································140
Setting other LLDP parameters····························································································································141
Configuring the encapsulation format for LLDPDUs ·························································································142
Configuring CDP compatibility···································································································································143
Configuration prerequisites ································································································································143
Configuring CDP compatibility ··························································································································143
Configuring LLDP trapping ··········································································································································143
Displaying and maintaining LLDP·······························································································································144
LLDP configuration examples ······································································································································145
Basic LLDP configuration example·····················································································································145
CDP-compatible LLDP configuration example···································································································147
Index ········································································································································································ 149
1
Configuring VLANs
Introduction to VLAN
VLAN overview
Ethernet is a network technology based on the Carrier Sense Multiple Access/Collision Detect
(CSMA/CD) mechanism. As the medium is shared in an Ethernet, network performance may degrade as
the number of hosts on the network is increasing. If the number of the hosts in the network reaches a
certain level, problems caused by collisions, broadcasts, and so on emerge, which may cause the
network to malfunction. In addition to the function that suppresses collisions (which can also be achieved
by interconnecting LANs), virtual LAN (VLAN) can isolate broadcast packets as well. VLAN divides a
LAN into multiple logical LANs with each being a broadcast domain. Hosts in the same VLAN can
communicate with each other like in a LAN. However, hosts from different VLANs cannot communicate
directly. In this way, broadcast packets are confined to a single VLAN, as illustrated in the following
figure.
Figure 1 A VLAN diagram
A VLAN can span across physical spaces. The hosts that reside in different network segments may
belong to the same VLAN, users in a VLAN can be connected to the same switch, or span across multiple
switches or routers.
VLAN technology has the following advantages:
•Broadcast traffic is confined to each VLAN, reducing bandwidth utilization and improving network
performance.
•LAN security is improved. Packets in different VLANs are isolated at Layer 2. That is, users in a
VLAN cannot communicate with users in other VLANs directly, unless Layer 3 network devices such
as routers are used.
•A more flexible way to establish virtual workgroups. With VLAN technology, a virtual workgroup
can be created spanning physical network segments. That is, users from the same workgroup do not
have to be within the same physical area, making network construction and maintenance much
easier and more flexible.
2
VLAN fundamentals
To enable a network device to identify frames of different VLANs, a VLAN tag field is inserted into the
data link layer encapsulation.
The format of VLAN-tagged frames is defined in IEEE 802.1Q issued by the Institute of Electrical and
Electronics Engineers (IEEE) in 1999.
In the header of a traditional Ethernet data frame, the field following the destination MAC address and
the source MAC address is the Type field, which indicates the upper layer protocol type. Figure 2
illustrates the format of a traditional Ethernet frame, where DA stands for destination MAC address, SA
stands for source MAC address, and Type refers to the upper layer protocol type of the frame.
Figure 2 The format of a traditional Ethernet frame
IEEE 802.1Q defines a four-byte VLAN Tag between the DA&SA field and the Type field to carry
VLAN-related information, as shown in Figure 3.
Figure 3 The position and the format of VLAN tag
A VLAN tag comprises four fields: the tag protocol identifier (TPID) field, the Priority field, the canonical
format indicator (CFI) field, and the VLAN ID field.
•The 16-bit TPID field with a value of 0x8100 indicates that the frame is VLAN-tagged.
•The Priority field, three bits in length, indicates the 802.1p priority of a packet. For more information
about packet priority, see ACL and QoS Configuration Guide.
•The CFI field, one bit in length, specifies whether or not the MAC addresses are encapsulated in
standard format when packets are transmitted across different medium. With the field set to 0, MAC
addresses are encapsulated in standard format; with the field set to 1, MAC addresses are
encapsulated in non-standard format. The filed is 0 by default.
•The VLAN ID field, 12 bits in length and with its value ranging from 0 to 4095, identifies the ID of
the VLAN a packet belongs to. As VLAN IDs of 0 and 4095 are reserved by the protocol, the value
of this field actually ranges from 1 to 4094.
A network device determines the VLAN to which a packet belongs by the VLAN ID field the packet
carries. The VLAN tag determines the way a packet is processed. For more information, see “Introduction
to port-based VLAN.”
3
NOTE:
•The Ethernet II encapsulation format is used here. Besides the Ethernet II encapsulation format, other
encapsulation formats, including 802.2 LLC, 802.2 SNAP, and 802.3 raw, are also supported by
Ethernet. The VLAN tag fields are also added to frames encapsulated in these formats for VLAN
identification.
•For a frame with multiple VLAN tags, the network device handles it according to its outer-most VLAN
tag, and transmits its inner VLAN tags as payload.
•VLAN 4094 is not available when different types of service cards are intermixed.
VLAN types
You can implement VLANs based on the following criteria:
•Port
•MAC address
Protocols and standards
•IEEE 802.1Q, IEEE Standards for Local and Metropolitan Area Networks: Virtual Bridged Local
Area Networks
Configuring basic VLAN settings
To configure basic VLAN settings:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Create VLANs. vlan { vlan-id1 [to vlan-id2 ]|
all }
Optional.
Use this command to create VLANs in bulk.
3. Enter VLAN view. vlan vlan-id
By default, only the default VLAN (that is,
VLAN 1) exists in the system.
If the specified VLAN does not exist, this
command creates the VLAN first.
4. Configure the VLAN
name. name text
Optional.
By default, the VLAN ID is used as the name
of a VLAN. For example, VLAN 0001.
5. Specify a descriptive
string for the VLAN. description text
Optional.
By default, the VLAN ID is used as the
description. For example, VLAN 0001.
NOTE:
The router does not support VLAN 4094 when it works in hybrid mode. For more information about
system working modes, see
Fundamentals Configuration Guide
.
4
Configure basic settings of a VLAN interface
VLAN interface overview
For hosts of different VLANs to communicate, you must use a router or Layer 3 switch to perform layer 3
forwarding. To achieve this, VLAN interfaces are used.
VLAN interfaces are Layer 3 virtual interfaces used for Layer 3 interoperability between different VLANs.
Each VLAN corresponds to one VLAN interface. After you assign an IP address to a VLAN interface, this
interface can serve as the gateway for the network devices in the VLAN and allows IP address-based
Layer 3 forwarding.
Configuration procedure
To perform basic VLAN interface configuration:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Create a VLAN interface
and enter VLAN interface
view.
interface vlan-interface
vlan-interface-id
This command leads you to VLAN interface
view if the VLAN interface already exists.
3. Configure an IP address
for the VLAN interface. ip address ip-address { mask
| mask-length } [ sub ]
Optional.
Not configured by default
4. Specify the description of
the VLAN interface. description text
Optional.
By default, VLAN interface name is used. For
example, Vlan-interface1 Interface.
5. Set the MTU for the VLAN
interface. mtu size Optional.
By default, the MTU is 1500 bytes.
6. Restore the default
settings for the VLAN
interface. default Optional.
7. Bring up the VLAN
interface. undo shutdown
Optional.
By default, a VLAN interface is up. The VLAN
interface is up if one or more ports in the
VLAN is up, and goes down if all ports in the
VLAN go down.
A VLAN interface shut down with the
shutdown command, however, will be in the
DOWN (Administratively) state until you
bring it up, regardless of how the state of the
ports in the VLAN changes.
NOTE:
Before creating a VLAN interface, make sure that the correspondin
g
VLAN already exists. Otherwise, the
specified VLAN interface will not be created.
5
VLAN interface configuration example
Network requirements
As shown in Figure 4, PC A is assigned to VLAN 5. PC B is assigned to VLAN 10. The PCs belong to
different IP subnets and cannot communicate with each other.
Configure VLAN interfaces on Router A and configure the PCs to enable Layer 3 communication between
the PCs.
Figure 4 Network diagram
Configuration procedure
1. Configure Router A
# Create VLAN 5 and assign GigabitEthernet 3/1/1 to it.
<RouterA> system-view
[RouterA] vlan 5
[RouterA-vlan5] port gigabitethernet 3/1/1
# Create VLAN 10 and assign GigabitEthernet 3/1/2 to it.
[RouterA-vlan5] vlan 10
[RouterA-vlan10] port gigabitethernet 3/1/2
[RouterA-vlan10] quit
# Create VLAN-interface 5 and configure its IP address as 192.168.0.10/24.
[RouterA] interface vlan-interface 5
[RouterA-Vlan-interface5] ip address 192.168.0.10 24
[RouterA-Vlan-interface5] quit
# Create VLAN-interface 10 and configure its IP address as 192.168.1.20/24.
[RouterA] interface vlan-interface 10
[RouterA-Vlan-interface10] ip address 192.168.1.20 24
[RouterA-Vlan-interface10] return
2. Configure PC A
# Configure the default gateway of the PC as 192.168.0.10.
3. Configure PC B
# Configure the default gateway of the PC as 192.168.1.20.
Verifying the configurations
1. The PCs can ping each other.
2. Display brief information about Layer 3 interfaces on Router A to verify the configuration.
6
<RouterA> display ip interface brief
*down: administratively down
(s): spoofing
Interface Physical Protocol IP Address Description
Vlan5 up up 192.168.0.10 Vlan-inte...
Vlan10 up up 192.168.1.20 Vlan-inte...
Configuring port-based VLANs
Introduction to port-based VLAN
Port-based VLANs group VLAN members by port. A port forwards traffic for a VLAN only after it is
assigned to the VLAN.
Port link type
You can configure the link type of a port as access, trunk, or hybrid. The three link types use different
VLAN tag handling methods.
•An access port belongs to only one VLAN and sends traffic untagged. It is typically used to connect
a terminal device unable to recognize VLAN tagged-packets or when there is no need to
differentiate VLAN members. As shown in Figure 5,because Device A is connected with common
PCs that cannot recognize VLAN tagged-packets, you need to configure Device A’s ports that
connect the PCs as access ports.
•A trunk port can carry multiple VLANs to receive and send traffic for them. Except traffic of the port
VLAN (PVID), traffic sent through a trunk port will be VLAN tagged. Usually, ports connecting
network devices are configured as trunk ports. As shown in Figure 5, because Device A and Device
B need to transmit packets of VLAN 2 and VLAN 3, you need to configure the ports connecting
Device A and Device B as trunk ports, and assign them to VLAN 2 and VLAN 3.
•Like a trunk port, a hybrid port can carry multiple VLANs to receive and send traffic for them. Unlike
a trunk port, a hybrid port allows traffic of all VLANs to pass through untagged. Usually, hybrid
ports are configured to connect network devices whose support for VLAN tagged-packets you are
uncertain about. As shown in Figure 5, Device B connects a small-sized LAN in which some PCs
belong to VLAN 2 while some other PCs belong to VLAN 3. In this case, you need to configure
Device B’s port connecting the LAN as a hybrid port that allows packets of VLAN 2 and VLAN 3
to pass through untagged.
7
Figure 5 Port link types
PVID
You can configure a port VLAN (PVID) for a port. By default, VLAN 1 is the PVID for all ports.
•An access port can join only one VLAN. The VLAN to which the access port belongs is the PVID of
the port. The PVID of the access port changes along with the VLAN to which the port belongs.
•A trunk or hybrid port can join multiple VLANs, and you can configure a PVID for the port.
•You can use a nonexistent VLAN as the PVID for a hybrid or trunk port but not for an access port.
Therefore, after you remove the VLAN that an access port resides in with the undo vlan command,
the PVID of the port changes to VLAN 1. The removal of a VLAN specified as the PVID of a trunk or
hybrid port, however, does not affect the setting of the PVID on the port.
NOTE:
•It is recommended that you set the same PVID for the local and remote ports.
•Make sure that a port is assigned to its PVID. Otherwise, when receiving frames tagged with the PVID or
untagged frames (including protocol packets such as MSTP BPDUs), the port filters out these frames.
Ports of different link types handle frames as follows:
Port type Actions (in the inbound direction)
Actions (in the outbound
direction)
Unta
gg
ed frame Ta
gg
ed frame
Access Tag the frame with the
PVID tag.
•Receive the frame if its
VLAN ID is the same as the
PVID.
•Drop the frame if its VLAN
ID is different from the
PVID.
Remove the VLAN tag and send
the frame.
8
Port type Actions (in the inbound direction)
Actions (in the outbound
direction)
Unta
gg
ed frame Ta
gg
ed frame
Trunk
Check whether the PVID
is permitted on the port:
•If yes, tag the frame
with the PVID tag.
•If not, drop the frame.
•Receive the frame if its
VLAN is carried on the
port.
•Drop the frame if its VLAN
is not carried on the port.
•Remove the tag and send the
frame if the frame carries the
PVID tag and the port
belongs to the PVID.
•Send the frame without
removing the tag if its VLAN
is carried on the port but is
different from the default
one.
Hybrid
Send the frame if its VLAN is
carried on the port. The frame is
sent with the VLAN tag removed
or intact depending on your
configuration with the port
hybrid vlan command. This is
true of the PVID.
Assigning an access port to a VLAN
You can assign an access port to a VLAN in VLAN view, interface view (including Ethernet interface view,
Layer 2 aggregate interface view, and Layer 2 VE interface view), or port group view.
To assign one or multiple access ports to a VLAN in VLAN view:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
2. Enter VLAN view. vlan vlan-id
If the specified VLAN does not
exist, this command creates the
VLAN first.
3. Assign one or multiple access
ports to the VLAN. port interface-list By default, all ports belong to
VLAN 1.
To assign an access port (in interface view) or a group of ports (in port group view) to a VLAN:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
9
Ste
p
Command
Remarks
2. Enter interface view or port
group view.
•Enter Ethernet interface view:
interface interface-type
interface-number
•Enter Layer 2 aggregate
interface view:
interface bridge-aggregation
interface-number
•Enter Layer 2 virtual Ethernet
interface view:
interface ve-bridge
interface-number
•Enter port group view:
port-group manual
port-group-name
Use any one of the commands.
3. Configure the link type of the
port or ports as access. port link-type access
Optional.
The link type of a port is access by
default.
4. Assign the current access
port(s) to a VLAN. port access vlan vlan-id
Optional.
By default, all access ports belong
to VLAN 1.
NOTE:
•Before assigning an access port to a VLAN, create the VLAN first.
•In VLAN view, you can assign only Layer 2 Ethernet interfaces to the current VLAN.
Assigning a trunk port to a VLAN
A trunk port can carry multiple VLANs. You can assign it to a VLAN in interface view (including Ethernet
interface view, Layer 2 aggregate interface view, and Layer 2 VE interface view) or port group view.
To assign a trunk port to one or multiple VLANs:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
10
Ste
p
Command
Remarks
2. Enter interface view or port
group view.
•Enter Ethernet interface view:
interface interface-type
interface-number
•Enter Layer 2 aggregate
interface view:
interface bridge-aggregation
interface-number
•Enter Layer 2 virtual Ethernet
interface view:
interface ve-bridge
interface-number
•Enter port group view:
port-group manual
port-group-name
Use any one of the commands.
3. Configure the link type of the
port or ports as trunk. port link-type trunk N/A
4. Assign the trunk port(s) to the
specified VLAN(s). port trunk permit vlan { vlan-id-list |
all }
By default, a trunk port carries
only VLAN 1.
5. Configure the PVID of the trunk
port(s). port trunk pvid vlan vlan-id Optional.
By default, the PVID is VLAN 1.
NOTE:
•To chan
g
e the link type of a port from trunk to hybrid or vice versa, you must set the link type to access
first.
•After configuring the PVID for a trunk port, you must use the port trunk permit vlan command to
configure the trunk port to allow packets from the PVID to pass through, so that the egress port can
forward packets from the PVID.
Assigning a hybrid port to a VLAN
A hybrid port can carry multiple VLANs. You can assign it to a VLAN in interface view (including Ethernet
interface view, Layer 2 aggregate interface view, and Layer 2 VE interface view) or port group view.
To assign a hybrid port to one or multiple VLANs:
Ste
p
Command
Remarks
1. Enter system view. system-view N/A
Other manuals for SR8800 IM-FW-II
2
Table of contents
Other H3C Network Router manuals
H3C
H3C AR19 Series User manual
H3C
H3C MSR3600-28 User manual
H3C
H3C CR16000-F User manual
H3C
H3C AR 18-2 Series User manual
H3C
H3C S3100-52P User manual
H3C
H3C MSR3600-28-X1 User manual
H3C
H3C MSR 930 Operating and maintenance manual
H3C
H3C S5510 Series User manual
H3C
H3C CR16000-F User manual
H3C
H3C S9500 Series User manual
H3C
H3C CR16000-F User manual
H3C
H3C H3C S7500E Series Installation instructions
H3C
H3C S3100-52P User manual
H3C
H3C S5120-EI Series User manual
H3C
H3C SR6600 Series Installation guide
H3C
H3C SR6600 SPE-FWM Installation manual
H3C
H3C MSR 2600 Series User manual
H3C
H3C SR6616 Operating and maintenance manual
H3C
H3C S3100-52P User manual
H3C
H3C S3100 Series Installation instructions
