- Table of Contents
-
- 04-Layer 2—LAN Switching Configuration Guide
- 00-Preface
- 01-MAC address table configuration
- 02-Ethernet link aggregation configuration
- 03-VLAN configuration
- 04-VLAN mapping configuration
- 05-Loop detection configuration
- 06-Spanning tree configuration
- 07-LLDP configuration
- 08-Service loopback group configuration
- 09-MVRP configuration
- 10-PFC configuration
- 11-Cut-through Layer 2 forwarding configuration
- Related Documents
-
Title | Size | Download |
---|---|---|
00-Preface | 100.53 KB |
Preface
This configuration guide describes the LAN switching fundamentals and configuration procedures. It describes how to configure a Layer 2 network in the following aspects:
· Layer 2 traffic control and load sharing.
· Eliminating Layer 2 loops.
· Isolating users within a VLAN and dividing VLANs.
· Modifying VLAN tags of packets.
This preface includes the following topics about the documentation:
· Audience.
· Conventions.
Audience
This documentation is intended for:
· Network planners.
· Field technical support and servicing engineers.
· Network administrators.
Conventions
The following information describes the conventions used in the documentation.
Command conventions
Convention |
Description |
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 a minimum of one. |
[ 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 |
Description |
Boldface |
Window names, button names, field names, and menu items are in Boldface. For example, the New User window opens; click OK. |
> |
Multi-level menus are separated by angle brackets. For example, File > Create > Folder. |
Symbols
Convention |
Description |
An alert that calls attention to important information that if not understood or followed can result in personal injury. |
|
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. |
|
An alert that calls attention to essential information. |
|
NOTE: |
An alert that contains additional or supplementary information. |
An alert that provides helpful information. |
Network topology icons
Convention |
Description |
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. |
|
Represents an access controller, a unified wired-WLAN module, or the access controller engine on a unified wired-WLAN switch. |
|
Represents an access point. |
|
Represents a wireless terminator unit. |
|
Represents a wireless terminator. |
|
Represents a mesh access point. |
|
Represents omnidirectional signals. |
|
Represents directional signals. |
|
Represents a security product, such as a firewall, UTM, multiservice security gateway, or load balancing device. |
|
Represents a security module, such as a firewall, load balancing, NetStream, SSL VPN, IPS, or ACG module. |
Examples provided in this document
Examples in this document might use devices that differ from your device in hardware model, configuration, or software version. It is normal that the port numbers, sample output, screenshots, and other information in the examples differ from what you have on your device.
Documentation feedback
You can e-mail your comments about product documentation to info@h3c.com.
We appreciate your comments.