Virtual Network (VLAN) Troubleshooting
UniFi makes it easy to create and manage virtual networks (VLANs), however certain misconfigurations may result in broken network connectivity. This article walks through the most common symptoms and the mistakes associated with them.
Please note that the mistakes described do not apply to VLANs whose VLAN ID is set to 1.
Using the VLAN Viewer
The VLAN Viewer, found in the Ports tab of UniFi Network, can help to give you a bird’s eye view of your VLAN tags. Additionally, it is helpful for finding incorrect port tagging that may disrupt connectivity in your network.
- Determine the VLAN having problems.
- Follow the path of switch ports from the problematic region back to your network gateway. Write down these ports.
- Use the VLAN Viewer to make sure all ports along the path of travel are properly configured, as outlined in this article.
Wireless Clients Unable to Join WiFi
If clients are unable to join a particular WiFi instance, it is usually a result of one or more incorrectly configured switch port that prevents them from receiving an IP address. This commonly occurs after adding a new switch, moving APs, changing port configurations, or creating a new WiFi.
Common Mistakes
1. The VLAN associated with a WiFi instance is configured as the Primary (Native) Network on the AP’s direct uplink port.
Clients will be unable to connect to the Broken WiFi because VLAN 20 is also configured as the Primary (Native) VLAN on the switch port to which the AP is directly connected.
2. The VLAN associated with a WiFi instance is not allowed (tagged) on an upstream switch port.
Clients will be unable to connect to the Broken WiFi because VLAN 20 is not allowed (tagged) on an upstream switch port that AP traffic must pass through to reach the gateway and DHCP server.
Valid Configuration
The following image illustrates one example of a functioning configuration. Notice that mistake (1) does not apply here because neither port using VLAN 20 as the Primary (Native) VLAN has an AP directly connected to it.
UniFi Devices Offline or Not Appearing for Adoption
Some network changes, such as adding or moving devices, changing port configurations, or using the Network Override feature, can cause a UniFi device to go offline. This is due to the UniFi device not receiving an IP address, or having an invalid IP address. The same symptoms and solutions apply to wired UniFi devices that cannot be adopted.
Common Mistakes
1. The Network Override feature is used to assign a device to a VLAN that is already used as the Primary (Native) Network of the switch port it is connected to.
The UniFi device will be unreachable because VLAN 20 is also configured as the Primary (Native) VLAN on the switch port to which the device is directly connected.
2. The Network Override feature is used to assign a device to a VLAN that is not allowed (tagged) on an upstream switch port.
The UniFi device will be unreachable because VLAN 20 is not allowed (tagged) on an upstream switch port that the device's traffic must pass through to reach the gateway and DHCP server.
3. The Primary (Native) Network of a switch port a device is connected to is not allowed (tagged) on an upstream switch port.
The UniFi device will be unreachable because VLAN 10 is not allowed (tagged) on an upstream switch port that the device's traffic must pass through to reach the gateway and DHCP server.
Valid Configuration
The following image illustrates one example of a functioning configuration that also uses the Network Override feature. Notice that mistake (1) does not apply here because neither port using VLAN 20 as the Primary (Native) VLAN has the UniFi device connected to it.