> Back to Contents Page

> ## Virtual LANs: Broadcom NetXtreme® 57XX User Guide

> VLAN Overview

> Adding VLANs to Teams

> ### VLAN Overview

> Virtual LANs (VLANs) allow you to split your physical LAN into logical parts, to create logical segmentation of workgroups, 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 Broadcom adapter on your system, depending on the amount of memory available in your system.

> VLANs can be added to a team to allow multiple VLANs with different VLAN IDs. A virtual adapter is created for each VLAN added.

> Although VLANs are commonly used to create individual broadcast domains and/or separate IP subnets, it is sometimes useful for a server to have a presence on more than one VLAN simultaneously. Broadcom adapters support multiple VLANs on a per-port or per-team basis, allowing very flexible network configurations.

> Figure 1: Example of Systems Supporting Multiple VLANs with Tagging

> Figure 1 above shows an example network that uses VLANs. In this example network, the physical LAN consists of a switch, two systems, and five clients. The LAN is logically organized into three different VLANs, each representing a different IP subnet. The features of this network are described in Table 1:

> Table 1: Example VLAN Network Topology
> Component | Description
> --- | ---
> VLAN #1 | An IP subnet consisting of the Main System, PC #3, and PC #5. This subnet represents an engineering group.
> VLAN #2 | Includes the Main System, PCs #1 and #2 via shared media segment, and PC #5. This VLAN is a software development group.
> VLAN #3 | Includes the Main System, the Accounting System and PC #4. This VLAN is an accounting group.
> Main System | A high-use system that needs to be accessed from all VLANs and IP subnets. The Main System has a Broadcom adapter installed. All three IP subnets are accessed via the single physical adapter interface. The system is attached to one of the switch ports, which is configured for VLANs #1, #2, and #3. Both the adapter and the connected switch port have tagging turned on. Because of the tagging VLAN capabilities of both devices, the system is able to communicate on all three IP subnets in this network, but continues to maintain broadcast separation between all of them.
> Accounting System | Available to VLAN #3 only. The Accounting System is isolated from all traffic on VLANs #1 and #2. The switch port connected to the system has tagging turned off.
> PCs #1 and #2 | Attached to a shared media hub that is then connected to the switch. PCs #1 and #2 belong to VLAN #2 only, and are logically in the same IP subnet as the Main System and PC #5. The switch port connected to this segment has tagging turned off.
> PC #3 | A member of VLAN #1, PC #3 can communicate only with the Main System and PC #5. Tagging is not enabled on PC #3 switch port.
> PC #4 | A member of VLAN #3, PC #4 can only communicate with the systems. Tagging is not enabled on PC #4 switch port.
> PC #5 | A member of both VLANs #1 and #2, PC #5 has an Broadcom adapter installed. It is connected to switch port #10. Both the adapter and the switch port are configured for VLANs #1 and #2 and have tagging enabled.

> NOTE: VLAN tagging is only required to be enabled on switch ports that create trunk links to other switches, or on ports connected to tag-capable end-stations, such as systems or workstations with Broadcom adapters.

> #### Adding VLANs to Teams

> Each team supports up to 64 VLANs (63 tagged and 1 untagged). Note that only Broadcom adapters and Alteon® AceNIC adapters can be part of a team with VLANs. With multiple VLANs on an adapter, a server with a single adapter can have a logical presence on multiple IP subnets. With multiple VLANs in a team, a system can have a logical presence on multiple IP subnets and benefit from load balancing and failover. For instructions on adding a VLAN to a team, see Adding a VLAN for Windows operating systems or see Configuring VLANs for NetWare operating systems.

> NOTE: Adapters that are members of a failover team can also be configured to support VLANs. Because VLANs are not supported for an Intel® LOM if an LOM is a member of a failover team, VLANs cannot be configured for that team.

> Back to Contents Page