Encapsulation Formats; Implementation Of Protocol-Based Vlan - H3C S3100 Series Operation Manual

Packets with the value of the type or length field being in the range 0x05DD to 0x05FF are regarded as
illegal packets and thus discarded directly.
The switch identifies whether a packet is an Ethernet II packet or an 802.2/802.3 packet according to
the ranges of the two fields.

Encapsulation Formats

Table 1-4 lists the encapsulation formats supported by some protocols. In brackets are type values of
these protocols.
Table 1-4 Encapsulation formats
Encapsulation (left)
Protocol (down)
IP (0x0800)
IPX (0x8137)
AppleTalk (0x809B)

Implementation of Protocol-Based VLAN

S3100 series Ethernet switches assign the packet to the specific VLAN by matching the packet with the
protocol template.
The protocol template is the standard to determine the protocol to which a packet belongs. Protocol
templates include standard templates and user-defined templates:
The standard template adopts the RFC-defined packet encapsulation formats and values of some
specific fields as the matching criteria.
The user-defined template adopts the user-defined encapsulation formats and values of some
specific fields as the matching criteria.
After configuring the protocol template, you must add a port to the protocol-based VLAN and associate
this port with the protocol template. This port will add VLAN tags to the packets based on protocol types.
The port in the protocol-based VLAN must be connected to a client. However, a common client cannot
process VLAN-tagged packets. In order that the client can process the packets out of this port, you must
configure the port in the protocol-based VLAN as a hybrid port and configure the port to remove VLAN
tags when forwarding packets of all VLANs.
Ethernet II 802.3 raw
Supported Not supported
Supported Supported
Supported Not supported
1-9
802.2 LLC 802.2 SNAP
Not supported Supported
Supported Supported
Not supported Supported