To vlan tag or not to tag?

Discussion in 'Cisco' started by budyerr, Jul 7, 2004.

  1. budyerr

    budyerr Guest

    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
    budyerr, Jul 7, 2004
    1. Advertisements

  2. budyerr

    Hansang Bae Guest

    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.



    "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.
    Hansang Bae, Jul 8, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.