

Switch(config-if)#switchport trunk encapsulation dot1q Since the VLAN needs to be added to the VLAN database anyways, this should not be too much of an issue. The disadvantage is that when a VLAN is added to the router, it needs to be added to the allowed VLAN list on the switch. This serves two purposes it is a good management practice to restrict VLANs where they are not needed, and the router will not be able to accept traffic on other VLANs without adding another sub-interface, so this shows you clearly on the switch side what VLANs are available for routing. The switch port needs to be configured as a trunk, and in this case I am also setting the allowed VLANs. You should use the fastest available ports to maximize throughput.

Conversely, if you have a single data VLAN, a wireless VLAN, and a voice VLAN, with the majority of the traffic from each going back to a central site over a WAN connection, this may be a very legitimate production use of router on a stick.Ĭonnect an Ethernet port on the router to a switch port.

If you have all your PCs on one VLAN, and a couple servers that you are doing large file transfers with on another, and your printers on their own VLAN, you are probably going to see some serious issues. The topology and network usage will largely determine how big an impact this will have. You have to determine the potential impact to your network. You are pushing all your traffic between two VLANs through a single interface, which could become a network bottleneck. Another thing that cuts both ways is that you gain some simplicity by minimizing the number of routing devices, but you add complexity to the configuration of the router. You may also wish to make use of some of the more advanced features on a router, such as firewalling. Most branches will have a router for WAN or internet access, using the same router for routing between VLANs saves the cost of a Layer 3 switch. There are a few reasons you would use this configuration, and several not to. This configuration uses sub-interfaces on the separate VLANs and an 802.1q or ISL trunk to perform the routing. Router on a stick (or One Armed Router) is a common name for a configuration used for routing between VLANs on a single Ethernet (including Fast/Gig/10Gig) interface.
