stalbansschool
asked on
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.
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.
Last Comment
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Switches / Hubs
A switch is a device that filters and forwards packets of data between LAN segments. Switches operate at the data link layer or the network layer of the Open Systems Interconnection (OSI) Reference Model and therefore support any packet protocol. LANs that use switches to join segments are called switched LANs or, in the case of Ethernet networks, switched Ethernet LANs. A hub is a connection point for devices in a network. Hubs are commonly used to connect segments of a LAN. A hub contains multiple ports; when a packet arrives at one port, it is copied to the other ports so that all segments of the LAN can see all packets.
23K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
ASKER
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.