snagrat Posted May 15, 2019 Posted May 15, 2019 What has to be tagged and untagged to get the pass through port on a IP phone working on a different VLAN? Say for example, phone is on VLAN 100 and computer needs to be on VLAN 200 TIA
bwestlake Posted May 15, 2019 Posted May 15, 2019 vLAN200 as Primary then, vLAN100 Tagged Make sure handset is set to pickup vLAN100 for voip
FN-GM Posted May 15, 2019 Posted May 15, 2019 What switches do you have? On a Cisco switch you use these commands: PC VLAN Switch Mode Access VLAN X Phone VLAN Switchport Voice VLAN X
snagrat Posted May 16, 2019 Author Posted May 16, 2019 It is a mixture of switches. Some Netgear, D-Link and HP.
NetworkServices Posted May 16, 2019 Posted May 16, 2019 On Procurve switches I've always untagged the phone VLAN and tagged the VLAN for which you want the PC port to be a part of.
caffrey Posted May 16, 2019 Posted May 16, 2019 Unifi is easier, just apply a port profile - I also have a DHCP option 144 for polycom phones
snagrat Posted May 16, 2019 Author Posted May 16, 2019 On Procurve switches I've always untagged the phone VLAN and tagged the VLAN for which you want the PC port to be a part of. Do you need to configure the phone to tell it what vlan the PC port is on?
Davit2005 Posted May 16, 2019 Posted May 16, 2019 All HPs here and Mitel IP phones, PC/Data traffic always untagged and Phone/VOIP traffic always tagged on switch ports, the phones then strip the tagged data passing thru untagged traffic to the PC port of the phone. Same with HP switches and Cisco IP phones from my experience.
Norphy Posted May 16, 2019 Posted May 16, 2019 On Procurve switches I've always untagged the phone VLAN and tagged the VLAN for which you want the PC port to be a part of. That's the wrong way around. That makes the phone VLAN the primary VLAN and the PC VLAN the secondary. It means that the PC has to be set up with VLAN tagging to be in the correct VLAN, which while possible with appropriate hardware and driver support, is more awkward to implement. The PC VLAN should be untagged, the phone VLAN should be tagged.
NetworkServices Posted May 16, 2019 Posted May 16, 2019 That's the wrong way around. That makes the phone VLAN the primary VLAN and the PC VLAN the secondary. It means that the PC has to be set up with VLAN tagging to be in the correct VLAN, which while possible with appropriate hardware and driver support, is more awkward to implement. The PC VLAN should be untagged, the phone VLAN should be tagged. That's strange. All I've ever had to do was go into the phone config and tell it which VLAN ID to put the PC port on (the same as the tagged VLAN) and it worked. To be honest it's a bit of a non-issue for me anyway as only one or two phones have a PC attached anyway.
Davit2005 Posted May 16, 2019 Posted May 16, 2019 Do you need to configure the phone to tell it what vlan the PC port is on? For instance my IP phone ports simply need to be plugged in to a switch port which is configured in HP terms as tagged for voice, the vlan is also configured as a voice vlan. The phones will automatically pick up the configuration including what vlan they need to be on. The vlan itself has settings on the DHCP server such as tftp server to download any firmware or config files from. I've only had issues with older HP switches that did not support LLDP-MED. This whitepaper explains a bit. https://www.cisco.com/en/US/technologies/tk652/tk701/technologies_white_paper0900aecd804cd46d.html
Norphy Posted May 16, 2019 Posted May 16, 2019 That's strange. All I've ever had to do was go into the phone config and tell it which VLAN ID to put the PC port on (the same as the tagged VLAN) and it worked. To be honest it's a bit of a non-issue for me anyway as only one or two phones have a PC attached anyway. OK, well that's a bit of extra configuration that you wouldn't ordinarily have to do. As already mentioned, the phone would either pick up its correct VLAN (the tagged one) through LLDP-MED or via DHCP options like our older Avaya phones do. 1
NetworkServices Posted May 16, 2019 Posted May 16, 2019 OK, well that's a bit of extra configuration that you wouldn't ordinarily have to do. As already mentioned, the phone would either pick up its correct VLAN (the tagged one) through LLDP-MED or via DHCP options like our older Avaya phones do. Maybe I'll revisit it one day and play around. There was probably once a reason why I did it that way to begin with but it's likely either forgotten or not applicable any more.
Davit2005 Posted May 16, 2019 Posted May 16, 2019 Maybe I'll revisit it one day and play around. There was probably once a reason why I did it that way to begin with but it's likely either forgotten or not applicable any more. Ideally you just want to be able to provision a new phone and plug it in. At the most you want to tagg the voice vlan on the port but there are ways to do that automatically these days and with some switches.
colly72 Posted May 16, 2019 Posted May 16, 2019 Aruba/HP switches here. We tag the VOIP vlan and untag the PC VLAN.
localzuk Posted May 16, 2019 Posted May 16, 2019 This all depends on the switches and phones used. With HP switches and Yealink phones with 3CX, you'd untag the phone VLAN, and tag the PC VLAN, then put the PC VLAN ID into the box for the LAN port on the phone that is being plugged in there. The phone then handles all the tagging of traffic.
snagrat Posted May 16, 2019 Author Posted May 16, 2019 This all depends on the switches and phones used. With HP switches and Yealink phones with 3CX, you'd untag the phone VLAN, and tag the PC VLAN, then put the PC VLAN ID into the box for the LAN port on the phone that is being plugged in there. The phone then handles all the tagging of traffic. I think this is the best way then we aren’t reliant on the switch model across the site. We can provision the VLAN ID on the PBX so we don’t have to manually setup each phone
Davit2005 Posted May 16, 2019 Posted May 16, 2019 (edited) This all depends on the switches and phones used. With HP switches and Yealink phones with 3CX, you'd untag the phone VLAN, and tag the PC VLAN, then put the PC VLAN ID into the box for the LAN port on the phone that is being plugged in there. The phone then handles all the tagging of traffic. Horses for courses I guess :-) . I have 3cx at home with HP ProCurve/Aruba and some older Cisco SPA504G phones. I untagg data and tag voice and this works a treat, the advantage I can see is that if a PC plugs into the port without a phone in between the PC and switch the PC will still work as the port is untagged for data. Edited May 16, 2019 by Davit2005
PotNoodleTech Posted May 17, 2019 Posted May 17, 2019 HP, Unifi switches and Mitel phones here. PC VLAN untagged Phone Vlan Tagged Phones have a menu option to actually type in the number of the phone vlan (in your case 100) so that the phone knows what VLAN to use for it's own commmunication.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now