Switch(config-if-range)# switchport access vlan 33 Switch(config-if-range)# switchport mode access Switch(config)# interface range fastEthernet 0/2 – 3 We will assign the vlan 33 to port2 and port3 as it is in vlan 33, while other ports will be assign with vlan 44. Configure the each device according to following configuration.įour ports are required to be configured as access ports because these ports are connected with the PCs. We can configure an IP address on each sub-interface in order to make communication possible between different Vlans.ĭesign the lab according to following figure and we have four PC/host PC0 & PC1 are belongs to vlan 33 and PC2 & PC3 are belong to vlan 44. In this lesson I will show you how you can use a router connecting different Vlans with each other with single switch & this is known as “router on a stick” or “inter-vlan routing”.įor inter clan routing you are required to create the sub-interfaces for each vlan on a router. You require a router if you want to interconnect VLANs with each other. I’ve taken the CCNA twice now (I passed both - the first one expired) and didn’ t see anything like this on either.Router on a stick configuration on Packet Tracerīy default the nodes associated to same vlans can communicate with each other in switching environment. When looking around for a good page to reference for this article, I read a lot of pages that said that this is a definite CCNA or CCDA test topic. It’s just logical to use the same sub-interface number as the VLAN ID. I picked F0/0.2 and F0/0.3 because we’re using VLANs 2 and 3, but it doesn’t matter what the sub-interface names are at all. I’m also assuming that you are doing to use 802.1q trunks.Ĭonfigure the router sub-interfaces for each network. How about some sample configurations to bring it all together? Of course, I’m assuming you’re using a Cisco router and Cisco switch. In our example, we have two works stations connected to a switch on VLANs 2 and 3. Here’s a terrible diagram to show what we’re doing. I would also have two routers that are each configured as a router-on-a-stick and run HSRP or something similar for redundancy and availability. If I were to implement a setup like this, I would have two switches with at least 2 trunks between them. If either one goes down, you’re whole network is gone. You have two single-points-of-failure in the router and switch. Setting your network up this way may set you up for disaster, though. Savings, ease of managment, and security? Wow! Since it segments your network, you can also apply inbound or outbound ACLs to control traffic. It also centralizes the network into a single point, so every network is directly attached, and no routing protocols are really needed. First, it can save you a lot of cash since you don’t need an expensive layer-3 switch or additional routers for all the VLANs. Using a router-on-a-stick gives you a few things. The router is configured with Ethernet sub-interfaces (just as you do frame-relay or ATM sub-interfaces) - one for each VLAN. Here’s how it works: The router is plugged into a port on a switch that is configured as a trunk that carries all the important VLANs. You literally take a single Ethernet interface, put it on multiple VLANs, and set up the IP address stuff. A router-on-a-stick is a network configuration that uses a single router interface as a gateway for more than one network segment. It’s a funny name for a very serious topic, though. Ever heard of a router-on-a-stick? Go ahead and laugh…everyone does.
0 kommentar(er)
