Help with any Ideas for Global configuration of VOIP OUI and Voice VLAN on Daisy chain ports.

Help with any Ideas for Global configuration of VOIP OUI and Voice VLAN on Daisy chain ports.

Help with any Ideas for Global configuration of VOIP OUI and Voice VLAN on Daisy chain ports.
Help with any Ideas for Global configuration of VOIP OUI and Voice VLAN on Daisy chain ports.
Friday
Hardware Version: V1
Firmware Version: 1.20.1

 

Good morning everyone,

 

I would like some help with a configuration issue I am facing at work.
We have an Omada environment without a Gateway, managed through the Omada Software on a dedicated server, where all routing is performed by a TP-Link L3 core switch and then forwarded to a firewall from another vendor.

 

That said, here is the problem:
We configured a "voice VLAN" using the "switch profile" option, in tagged mode across all our other VLANs, with the LLDP-MED option enabled on all of them.

In our environment, we use VOIP phones in a daisy-chain setup with desktop computers: Switch → VOIP → Desktop.

 

 

However, the switches are not tagging the voice VLAN on the VOIP device, nor are they passing the data VLAN through to the desktop.

I noticed there is no way to configure the OUI address of our VOIP devices within the Omada Software, as it can be done through the graphical interface when the switches are in standalone mode.

 

I also verified that when checking the voice VLAN status via the switch CLI, it reports the VLAN ID as 0, instead of the previously configured voice VLAN ID defined in the "switch profile" inside Omada Software.

 

I have seen several posts online about configuring voice VLANs in the Omada environment, but all of them require applying CLI commands specifically for each port. The challenge is that our environment is very dynamic, and ports are frequently reassigned to either add or remove VOIP devices. I have also had very poor experiences with the "CLI device profile" feature within Omada Software—at one point, applying a configuration locked up the switch, forcing me to reset it and resulting in a full day of downtime and rework.

 

So, does anyone have any ideas on how to safely and globally enable VOIP devices in a daisy-chain setup?

 

I know that if all switches were running in standalone mode, this could be done easily through the graphical interface of the devices. I don’t understand why these functions still haven’t been migrated into the Omada Software configuration environment!

 

 

Well gentlemen, I am open to suggestions. Thank you very much for taking the time to read this rather long post of mine.

 

  0      
  0      
#1
Options