Network components out-of-the-box default to VLAN1, so in a properly designed LAN, you can tell anything that doesn't belong because it's in VLAN1.
Or, you may have other ways to keep everything under control.
If you ever get to setup a LAN on a greenfields site, it's easy to exclude VLAN 1 from your design.
Otherwise, when working on network upgrades to existing networks, it is virtually impossible to wean everybody off VLAN1, so just make sure you always try to use sensible new subnets with non-VLAN1.
Its bad practise... VLAN 1 has special significance in Cisco switching as it is used for control traffic regardless of whether its allowed on a trunk or not. VTP, PAgP & CDP will all be transmitted on a trunk using a VLAN Tag of 1.
VLAN 1 should never be used for user traffic. It should also be pruned from all trunks unless you are interoperating with MST & PVST+ (typically with other vendors switches).
It seemed to me that the "route it" push from Cisco was mostly a response to their hardware's failure to provide the feature of distributed "trunks" (Link aggregation), like their competitor Nortel does.
Now that Cisco offers VSS, things are a little different.
Switched networks add less latency than routed networks, and this is how WANs now work with the advent of MPLS, etc...
So in fact, I have to disagree with you ADB100 - if you can avoid routing it, it will go faster, so it's often better if you don't route unless you have to.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.