To vlan tag or not to tag?

We currently are in a decentralized environment where each Division
has there own switch in the IDF to support the specific departments on
the floor. However I am proposing to move toward a centralized
implementations using VLAN tagging to enable the specific VLANs that
are needed on each floor. This enables me to activate whatever vlan I
need in that IDF without the need to implement new networking switch,
hence cost savings.

Questions I have is if anyone knows the drawbacks of implementing VLAN
tagging? It may be harder to troubleshoot, etc.. but I am curious to
find out from the groups opinion. In the past, cisco products had an
issue with VLAN bleeding, but I don't know if that has totally been
resolved. Again, your opinion and thoughts are welcomed.

Thanks in advance

 

No real security concerns these days. About two years ago, we had vlan
hopping when the 8540 CSR (more like POS) melted down.

The draw back to trunking is that you may over subscribe the one link by
carrying multiple VLANs. But you can always etherchannel it as required
or use a GigE uplink.




--

hsb

"Somehow I imagined this experience would be more rewarding" Calvin
*************** USE ROT13 TO SEE MY EMAIL ADDRESS ****************
********************************************************************
Due to the volume of email that I receive, I may not not be able to
reply to emails sent to my account. Please post a followup instead.
********************************************************************