There are two models in which you can design VLANs on a network:
- End-to-End
- Local
End-to-End
End-to-End VLANs span across multiple switches within the network. Regardless of the user’s physical location, they will consistently be assigned to the same VLAN. Consequently, the user’s resources will belong to the same subnet. Management of end-to-end VLANs often involves utilizing VTP through trunked switches, facilitating streamlined management processes.
However, reliance on VTP can sometimes lead to complications. Moreover, by extending the VLAN across the network, you enable broadcasts to traverse multiple switches. While this model may be suitable for small implementations, it may not scale effectively for larger environments.
Local
VLANs are confined to individual switches, typically organized according to geographic location. If a user relocates, they will be assigned to a different VLAN.
Under the Local VLAN model, the local switch connects to a distribution or core switch, where routing takes place. Local VLANs exist solely between the local switch and the distribution or core switch.
To communicate with other networks, traffic travels from the local VLAN to the distribution/core switch and is then routed to its destination. In this setup, VTP (VLAN Trunking Protocol) is not configured, and switches operate in VTP Transparent mode. Since VLANs are not broadcasted to other switches in the network, VTP becomes unnecessary.
One advantage of this model is the elimination of extended layer 2 broadcast domains throughout the network. Troubleshooting is simplified compared to end-to-end VLANs, as traffic follows a defined path. In contrast, end-to-end VLAN traffic traverses multiple switches.
About Author
