Configuring The Protocol-Based Vlan; Introduction To The Protocol-Based Vlan - H3C S9500 Series Operation Manual

Routing switches
Hide thumbs Also See for S9500 Series:
Table of Contents

Advertisement

Operation Manual – VLAN
H3C S9500 Series Routing Switches
Note:
To change the link type of a port from trunk to hybrid or vice versa, you must set the
link type to access first.
Ensure that a VLAN already exists before configuring it to pass through a certain
hybrid port.

1.5 Configuring the Protocol-Based VLAN

1.5.1 Introduction to the Protocol-Based VLAN

In this approach, inbound packets are assigned with different VLAN IDs based on their
protocol type and encapsulation format. The protocols that can be used to categorize
VLANs include: IP, IPX, and AppleTalk (AT). The encapsulation formats include:
Ethernet II, 802.3, 802.3 raw, 802.2 LLC, and 802.2 SNAP.
A protocol-based VLAN can be defined by a protocol template, which is determined by
the encapsulation format and protocol type. A port can be associated to multiple
protocol templates. An untagged packet (that is, packet carrying no VLAN tag) reaching
a port associated with a protocol-based VLAN will be processed as follows.
If the packet matches a protocol template, the packet will be tagged with the VLAN
ID of the protocol-based VLAN defined by the protocol template, and then sent to
the specified VLAN.
If the packet matches no protocol template, the packet will be tagged with the
default VLAN ID of the port.
A tagged packet (that is, a packet carrying VLAN tags) reaching the port is processed in
the same way as that of port-based VLAN.
If the port is configured to permit packets with the VLAN tag, the packet is
forwarded.
If the port is configured to deny packets with the VLAN tag, the packet is dropped.
This feature is mainly used to bind the service type with VLAN for ease of management
and maintenance.
1-10
Chapter 1 VLAN Configuration

Advertisement

Table of Contents
loading

Table of Contents