Users Guide

13 BC0054508-00 M
3 Virtual LANs in Windows
This chapter provides information about VLANs in Windows for teaming.
 VLAN Overview
 “Adding VLANs to Teams” on page 16
VLAN Overview
Virtual LANs (VLANs) allow you to split your physical LAN into logical parts, to
create logical segmentation of work groups, and to enforce security policies for
each logical segment. Each defined VLAN behaves as its own separate network
with its traffic and broadcasts isolated from the others, increasing bandwidth
efficiency within each logical group. Up to 64 VLANs (63 tagged and 1 untagged)
can be defined for each Marvell adapter on your server using the QLASP NIC
teaming driver (through the QCC GUI or QCS CLI), depending on the amount of
memory available in your system. See the respective Linux, VMware, or Windows
documentation for more information on the in-OS NIC bonding/teaming services.
The VLAN definitions are created as follows:
VLANs can be added to a team/bond to allow multiple VLANs with different VLAN
IDs. A virtual adapter is created for each VLAN added.
Windows Server 2012 and later Windows in-OS NIC teaming service
Linux in-OS NIC bonding services
VMware in-OS NIC teaming services
NOTE
Windows Server 2012 and later provide built-in teaming support, called NIC
Teaming. Marvell does not recommend enabling teams through NIC
Teaming and QLASP at the same time on the same adapters.
Windows Server 2016 (or later), Linux, and VMware OSs do not support
Marvell’s QLASP teaming driver.