Avaya P580 User Manual page 161

IEEE 802.1Q VLAN
Tagging
Document No. 650-100-700, Issue 1
determine its VLAN membership. As an example,
switches with two VLANs, Sales and R&D, would need a dedicated switch
to switch connections (Trunk) for both VLANs between switches.
Therefore all traffic arriving on that port must belong to the VLAN assigned
to that port since, in this case, no unique identifiers are sent with the frames.
Figure 6-1. Vlans No Tagging
The Avaya Multiservice switch is able to separate VLAN traffic between
switches across a single Trunk port. In order to accomplish this, the switch
implements VLAN Tagging and Trunking. VLAN Tagging is enabled on a
switch port by selecting a Trunk mode for that port; clear, IEEE 802.1Q or
Cisco-Multi Layer mode. A trunk port can send frames in clear mode, with
no VLAN ID, or the VLAN ID, over the same trunk. A frame is classified
as belonging to a particular VLAN based on the value of the VLAN
Identifier (VID) that is included in the Tag Header. Therefore using our
example, and implementing VLAN tagging, we need only one connection
(trunk) between the two switches to carry the traffic from both
VLANs.(Figure 6-2)
Figure 6-2. VLANs with 802.1Q tagging
The Avaya Multiservice switch is compliant with the IEEE 802.1Q standard
for VLANs and defines a Tag Header. Two Tag formats are defined as an
Ethernet Encoded (4 bytes) for 802.3 and Ethernet V2 and SNAP (Service
Network Access Point) for Token Ring and Fiber Distributed Data Interface
(FDDI).
Using VLANs, Hunt Groups, and VTP Snooping
(Figure 6-1) two
6-3