Dangers of global port tagging

We have dozens of switches around our sites. We use VLAN 3 for VoIP. It's becoming unmanageable tagging only those ports which have VoIP devices plugged into them as, invariably, the socket designation on the wall/patch panel unavoidably differs from the port number on the switch.

What are the dangers of simply tagging ALL ports with this VLAN, given that less than 10% of them will ever have a device plugged in which can make use of that traffic?

Thanks in advance.
stalbansschoolAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andy MIT Systems ManagerCommented:
In theory yes you can tag all the ports but I really would not recommend it at all. Basically each tagged port (i.e. all of them) will get all traffic broadcasts for the VOIP network, resulting in network issues. (To be honest doing this kind of defeats the purpose of a vlan in the first place).

When you plug a phone into a switch port you need to setup the port ID for that VLAN anyway to make it work so even if you did tag all ports you'll still need to make individual changes on the switch anyway to add new phones, so it won't make setup any easier.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cyclops3590Sr Software EngineerCommented:
agree with Morty.  you don't mention what kind of switch you have but some you can configure to auto-provision a port to the voice vlan and all of its setting dynamically easing your admin responsibilities.  something to look into anyway.
stalbansschoolAuthor Commented:
Thank you both.

We are predominantly using Netgear GS748TPS as edge switches. (I should have mentioned this is the question).

Our VoIP handsets contain gigabit switches allowing us to daisy-chain PCs where we are low on data sockets (which has happened in may places - some of our site is 1,100 years old with 4ft thick walls so only has the bar minimum data provision!) As such, I guess setting the port ID for the voice VLAN would preclude daisy-chained PCs picking up the default VLAN without some VLAN config on the PCs' NICs.

However, I take both points - we want to avoid issues with broadcasts, so need to limit the use of VLAN tagging to just the ports on which we need it; we also need to investigate auto-provisioning as this could be a solution to the admin overhead.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Voice Over IP

From novice to tech pro — start learning today.