D-Link TM DES-6500, Manual

Page: 75 / 352

DES-6500 Chassis-based Layer 3 Ethernet Switch Manual
74
VLAN and Trunk Groups
The members of a trunk group have the same VLAN setting. Any VLAN setting on the members of a trunk group will
apply to the other member ports.
NOTE: In order to use VLAN segmentation in conjunction with port trunk
groups, you can first set the port trunk group(s), and then you may
configure VLAN settings. If you wish to change the port trunk grouping
with VLANs already in place, you will not need to reconfigure the VLAN
settings after changing the port trunk group settings. VLAN settings will
automatically change in conjunction with the change of the port trunk
group settings.
Protocol VLANs
The DES-6500 switch incorporates protocol-based VLANs. This standard, defined by the IEEE 802.1v standard maps
packets to protocol-defined VLANs by examining the type octet within the packet header to discover the type of protocol
associated with it. After assessing the protocol, the Switch will forward the packets to all ports within the protocol-assigned
VLAN. This feature will benefit the administrator by better balancing load sharing and enhancing traffic classification. The
Switch supports fourteen (14) pre-defined protocols for configuration. The user may also choose a protocol that is not one
of the fourteen defined protocols by properly configuring the
userDefined protocol VLAN. The supported protocols for the
protocol VLAN function on this switch include IP, IPX, DEC LAT, SNAP, NetBIOS, AppleTalk, XNS, SNA, IPv6, RARP
and VINES.
The following is a list of type headers for each protocol listed for VLAN configuration.
Protocol Type Header in Hexadecimal Form
IP over Ethernet 0x0800
IPX 802.3 0xFFFF
IPX 802.2 0xE0E0
IPX SNAP 0x8137
IPX over Ethernet2 0x8137
decLAT 0x6000
SNA 802.2 0x0404
netBios 0xF0F0
XNS 0x0600
VINES 0x0BAD
IPV6 0x86DD
AppleTalk 0x809B
RARP 0x8035
SNA over Ethernet2 0x80D5
Table 6- 3. Protocol VLAN and the corresponding type header
In configuring the user-defined protocol, the administrator must make sure that the pre-defined user type header does not
match any other type header. A match may cause discrepancies within the local network and failure to define the VLAN to
which to forward packets.