NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Auto Voice VLAN setup
We are looking to isolate our VoIP traffic to its own VLAN. For a number of reasons, we'd like this to happen without needing to configure each phone. It looks like Netgear switches support this. ...
Hello davidcts
Have no recent practical experience with that S3300 switch series.
What looks right to me is that the Auto-VoIP VLAN is set to the VLAN ID 88.
But then, strange is that the VLAN 88 does show up as a VLAN-Type: Static
and
the VLAN-Membership for VLAN 88 is set manually to [U]ntagged
and
the Voice-VLAN-Configuration does show Operational State: Disabled
This makes me believe you have -manually- defined the VLAN 88 on top of the Voice-VLAN, manually assigning port 1/g-1 ... 1/g-52 (you don't have to do this in my understanding!) on top of what should be part of the Voice-VLAN-Config automatically once enabled.
So, remove the VLAN 88 port assignments -and- the manually define VLAN 88.
I removed the manually created VLAN 88 from Switching > VLAN > Advanced > VLAN Configuration, which automatically removed any options for it from VLAN Membership.
However, I do not see any way to set the Operational State to Enabled, as displayed under Switching > VLAN > Advanced > Voice VLAN Configuration. When checking Switching > Auto-VoIP > Protocol-based > Port Settings, all ports show Auto VoIP Mode as Enabled.
Something still isn't correct; the phones aren't being pushed over to VLAN 88.
davidcts wrote:
However, I do not see any way to set the Operational State to Enabled, as displayed under Switching > VLAN > Advanced > Voice VLAN Configuration. When checking Switching > Auto-VoIP > Protocol-based > Port Settings, all ports show Auto VoIP Mode as Enabled.
Something still isn't correct; the phones aren't being pushed over to VLAN 88.
Auto-VoIP Global Admin Mode enabled?
Voice-VLAN Interface(s) Interface Mode set to VLAN-ID, and the Value set to 88?
This little document Auto-VoIP and LLDP-MED Guide.pdf should help.
Your tips brought me a big step closer. The Global Admin setting had no impact, but once I set the Interface Mode to VLAN-ID, our phones are registering on VLAN 88.
Unfortunately, our FortiGate routers are not playing well with this configuration. I've got a pair of HA routers in an active/passive setup using ports 45-48.
- Ports 47-48 are running default VLAN on both the switch and routers. This is fine, and dishes out DHCP leases to everything else on default VLAN.
- Ports 45-46 are plugged into the routers on a different ports assigned to a separate LAN (different subnet, etc). The routers have that LAN set to use VLAN 88. But, the switch and routers do no seem to be playing nicely together, and a phone plugged in will not find any DHCP server. So, the phones are completely non-functional in the current configuration.
I've tried to adjust as follows:
- My go-to idea at this point was to alter the MAC address for the VoIP LAN. Unfortunately, FortiGate does not allow this.
- My next idea was to re-input the VLAN under Switching > VLAN > Basic > VLAN Configuration, and then set ports 45-46 to PVID 88 under Switching > VLAN > Advanced > Port PVID Configuration. This doesn't seem to have made any difference.
- My next idea was to manually tag ports 45-46. However, the switch recognizes that VLAN 88 is for Auto-VoIP, and is not allowing me to manually set ports 45-46 as Tagged.
So... how do I get the Netgear switch to play nicely with the FortiGate routers?
Thanks again!
Do the two (or more?) physical HA ports of the have dedicated MAC addresses? Most likely: Yes! So add these MAC address OID part to the OUI table, and add these ports to the Auto-VLAN config. That's about it.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
