ArlieneHeald680

For CCNA and CCNP individuals, it is difficult to not laugh initially you hear the term "router on a stick." Let's face it, that is a fairly silly term. Learn more on a related wiki - Navigate to this web site: laverton locksmiths. But as those people who have passed the CCNA and CCNP checks know, this is a essential test topic that you must know how exactly to configure and troubleshoot. Fundamental Cisco theory states that for hosts in numerous VLANs to talk, a Layer 3 device should be concerned to deal with the routing between the VLANs. That system is just a router, and you will find special considerations that must be considered for the physical router itself and the arrangement you will be writing. The switch is likely to be attached to a switch via a FastEthernet interface (or more). The router port can not be considered a normal Ethernet port, because the router port will need the ability to receive and send data at the same time frame. The setting of the program is where things get interesting. Let's say we have two VLANs that'll be using router-on-a-stick to communicate. Click here here's the site to explore the meaning behind this activity. This is actually the VLAN information: VLAN 20: 20.20.20.0 /24 VLAN 40: 40.40.40.0 /24 The port on the switch that will be attached to the router's FastEthernet port must be in trunking function, and you must know the trunking method in use. We'll go with the Cisco-proprietary ISL here. The real FE port on the switch won't have an internet protocol address. The use of router-on-a-stick mandates the use of logical subinterfaces. While we do not have to make use of the VLAN numbers for the subinterface numbers, I've found this can help you keep carefully the interfaces immediately. For fresh information, people should check out: compare newport locksmiths. One subinterface must certanly be given an address in VLAN 20, and another may have an address in VLAN 40. After creating subinterfaces fast 0.20 and fast 0.40, the config looks like this: Screen fastethernet0 no ip address interface FastEthernet 0.20 ip address 20.20.20.1 255.255.255.0 Program FastEthernet 0.40 Internet protocol address 40.40.40.1 255.255.255.0 Believe it or not, you are almost done! Now we need the encapsulation record under each subinterface. The record must reflect both the VLAN amount and the encapsulation type getting used. If you think anything at all, you will likely hate to research about tour laverton locksmiths. Once we are done, the config would seem like this: Screen fastethernet0 no ip interface FastEthernet 0.20 Ip 20.20.20.1 255.255.255.0 encapsulation isl 20 Screen FastEthernet 0.40 Internet protocol address 40.40.40.1 255.255.255.0 encapsulation isl 40 And that is it! Your hosts in VLAN 20 should now be able to keep in touch with hosts in VLAN 40, and vice versa. Several final troubleshooting factors - the most frequent mistake with router-on-a-stick is to put the wrong vlan number in the encapsulation record. Also, be sure you have configured the router's IP in VLAN 20 as the default gateway for hosts in VLAN 20, and do the same for VLAN 40. I really hope you've experienced this look at router-on-a-stick. While a chuckle may be got by the name out of you, it's still found in quite a few communities out there, and focusing on how to configure and troubleshoot it'll get you that much closer to getting your CCNA and CCNP.