Windows Server Vlan Tagging

Posted on

Gatx train. In part of implementing additional Veeam Backup & Recovery servers as part of Atlantic Metro’s managed backup service, and supporting our Cloud/vmware managed hosting and disaster recovery environments, the need for having isolated 802.1q VLANs for inter-site communication was established. Researching how to implement this functionality on Google yielded minimal results and nothing very concrete as to how to accomplish this short of using Powershell. We’ve created this article to help explain the procedure for implementing this functionality. Using Windows Server 2012 R2 (It will work on 2012 original as well), this feature can be enabled by using the NIC Teaming application that is accessible within Server Manager.


To implement VLAN tagging, go in to NIC Teaming within the Server Manager interface. From there, within the Adapters and Interfaces screen, click on Team Interfaces.

Click the Tasks drop-down and select Add Interface.

Enter your new logical interface’s name, and select a VLAN ID.

I hope you find this article helpful. Please follow @atlanticmetro for more information about our tips & tricks and services we offer.

These VLAN configuration examples can help you get your Red Hat Enterprise Linux networks set up correctly.

All but the smallest networks are typically split into Virtual Local Area Networks (VLANs, for short), and I discussed VLAN basics a the previous article. Understanding how to properly configure and troubleshoot VLANs can save you hours of back-and-forth with your network team. In this article, cover VLAN configuration in Red Hat Enterprise Linux (RHEL) systems. By the end of this article, you should be pretty comfortable configuring VLANs on RHEL.

More Linux resources

Virtual local area network (VLAN) tagging requires that the network interface card (NIC) and the router or switch that you use support protocol IEEE 802.1q. Depending on the NIC, you can set your VLAN ID in Device Manager. Not all NICs that support VLAN tagging. Back in 2012, Dinko posted an article, “VLAN tagging problems in Windows Server 2012 Hyper-V”, that described my problem and provided the solution for which I had been hunting. It turns out my Broadcom 10 GigE NICs (but not my 1 GigE NICs) were set to filter VLANs by default. NOTE: Where using RADIUS-assigned VLANs, the UAP's switch port must have all the RADIUS-assigned VLANs configured as tagged VLANs on its switch port. With UniFi switches, the default 'All' network assignment on the UAP's switch port covers that requirement, as long as those VLAN IDs are defined in the controller under Settings Networks, as either a VLAN-Only, Corporate, or Guest Network.

With the background knowledge out of the way, It's time to get your hands dirty with configuration. I’ll start with the most basic VLAN configuration: no VLAN.

Simple example

Windows Server 2008 R2 Vlan Tagging

One of the most common topologies that you will encounter as a sysadmin is a host connected to a switch’s access port. VLAN configuration is handled on the switch, and you configure the interface without any regard for the underlying network topology.

Dhcp Server Vlan Tagging

In the simple topology without VLANs that I discussed previously, your hosts are on the same VLAN and IP subnet. The interface configuration is a simple, static IP address: