This article explains the difference between Voice VLAN and Vendor ID-based VLAN and shows how to configure both features on Zyxel switches. Voice VLAN is used to identify and prioritize voice traffic from IP phones. In a typical office setup, an IP phone may be connected to the switch, and a PC or laptop may be connected behind the phone. Voice VLAN allows the switch to separate voice traffic from regular data traffic and apply the correct VLAN and priority settings.
- What is Voice VLAN?
Voice VLAN is used to identify and prioritize voice traffic from IP phones.
In a typical office setup, an IP phone may be connected to the switch, and a PC or laptop may be connected behind the phone. Voice VLAN allows the switch to separate voice traffic from regular data traffic and apply the correct VLAN and priority settings.
Use Voice VLAN when all IP phones should use the same Voice VLAN ID.
- What is Vendor ID-based VLAN?
Vendor ID-based VLAN allows the switch to assign devices to VLANs based on the vendor OUI, which is the vendor-identifying part of the MAC address.
This is useful when devices from different vendors or device types need to be assigned to different VLANs automatically.
Use Vendor ID-based VLAN when different vendors or device types should use different VLAN IDs.
Voice VLAN vs Vendor ID-based VLAN
| Feature | Voice VLAN | Vendor ID-based VLAN |
|---|---|---|
| Main purpose | Voice traffic separation and prioritization | Vendor-based VLAN assignment |
| Typical use case | IP phones | IP phones, cameras, APs, or other vendor-specific devices |
| OUI matching | Yes | Yes |
| VLAN assignment | Multiple OUI entries use the same Voice VLAN ID | Different OUI profiles can use different VLAN IDs |
| Maximum OUI entries | Up to 6 | Up to 8 |
| Best used when | All voice devices should be in the same VLAN | Different vendors/devices should be placed into different VLANs |
Configure Vendor ID-based VLAN in Nebula
OUI format explanation
OUI is the first part of a MAC address that identifies the device vendor.
For example: 64:16:7F
matches devices in the MAC address range: 64:16:7F:00:00:00 to 64:16:7F:FF:FF:FF
Another example: 1C:74:0D:9C
matches: 1C:74:0D:9C:00:00 to 1C:74:0D:9C:FF:FF
Site-wide > Configure > Switches > Switches settings > Vendor ID based VLANSite-wide > Configure > Switches > Switch portsThe port type needs to be changed to access port; otherwise, the VLAN type is hidden.
PVID is used as the default VLAN for untagged traffic that does not match any Vendor ID based VLAN rule. When using a Vendor ID based VLAN, you usually do not need to change the port PVID to the Vendor VLAN ID. Keep the PVID as the fallback/default VLAN, for example VLAN 1, unless you specifically want all non-matching devices on this port to be placed into another VLAN.
Configure Voice VLAN in Nebula
Voice VLAN is used to separate voice traffic from regular data traffic in a network where an IP phone and a PC may be connected through the same switch port. This helps ensure that voice packets from the IP phone are identified, placed into the correct VLAN, and given higher priority, while normal data traffic from the PC remains in the data VLAN.
In Nebula, the configuration is simplified: the switch port is configured as an Access port with a PVID for data traffic, while the Voice VLAN feature identifies IP phones by their OUI/MAC vendor information and applies the configured Voice VLAN automatically. This allows voice and data traffic to be separated without manually configuring VLAN tags on each IP phone.
Site-wide > Configure > Switches > Switch Settings
Then configure Voice VLAN settings. Specify the VLAN ID and OUI addresses of the IP phones. OUI are the first 3 bytes (first six digits) of a MAC address that represents the vendor. By specifying the IP phone MAC address, the switch can identify voice traffic accordingly. Nebula cloud switch supports up to 6 vendor OUIs.
Site-wide > Configure > Switches > Switch Port
Select and edit the port(s) which are connected to the IP phones, and set the port type as “access”. Assign a PVID for the ports. PVID is used to tag the data packets with the VLAN ID. Next, we’ll use the “Voice VLAN” feature to identify the voice packets for the switch.
Note: Vendor ID-based VLAN in standalone mode
Vendor ID-based VLAN is a Nebula feature and is configured through Nebula Control Center. In standalone mode, this exact feature is usually not available as a separate configuration option.
If the goal is to automatically place IP phones into a dedicated voice VLAN based on their OUI/MAC vendor information, use Voice VLAN instead.
For standalone switch configuration, please refer to this guide: How to Configure Voice VLAN on Zyxel Switches
Comments
0 commentsPlease sign in to leave a comment.