Cisco CCNA Examination Tutorial: Utilizing Trivial File Transfer Protocol (TFTP)

One of many first things you do when you begin studying for the CCNA exam is memorizing an inventory of port numbers and the protocols that run on those ports. In the event you're an experienced networker, you understand many of the protocols which might be talked about - DNS, DHCP, FTP, SMTP, and so on. But there's one protocol that you just may not have experience with, however is actually vital for CCNA exam success and success in working with Cisco routers and switches, and that's TFTP - Trivial File Transfer Protocol. TFTP is principally FTP's non-secure relative. There are no passwords, no authentication scheme, no nothing! As someone once informed me, "If I am transferring my files, there's nothing 'trivial' about it." Great. So that you're pondering, "What the heck can we use TFTP for, anyway?" TFTP is used in the Cisco world to perform IOS upgrades and to save lots of configs to a TFTP Server. Cisco routers can themselves function TFTP servers, or you should utilize a workstation to fill that role. For those who wanted to repeat an IOS image to a router, for instance, you can achieve this easily by connecting your PC to the router's console port (through a rollover cable, proper?). Your PC would want to run TFTP server software. There are fairly a few free TFTP server software packages that work quite nicely - simply enter "free tftp server" into Google or your favorite search engine and also you'll see what I mean. Utilizing TFTP in this fashion is a good way to have backup copies of IOS photos or router configs proper on your laptop. And take it from me, when the day comes that you just need those backups, you'll be glad you probably did! Keep in mind that when utilizing the copy command, you first point out the place you're copying from, then where you're copying to: R1copy flash tftp Supply filename []? Instance Handle or name of remote host []? When performing such a replica, you'll want to name the file you're copying, as well as the IP address of the system you're copying to. Utilizing TFTP to carry out IOS upgrades takes somewhat getting used to, especially the syntax of the copy command. google_ad_client = "pub-2311940475806896"; /* 300x250, created 1/6/11 */ google_ad_slot = "0098904308"; google_ad_width = 300; google_ad_height = 250; But realizing that syntax and find out how to use TFTP will indeed get you one step closer to the CCNA! On this CCNA case study, we'll take some primary switching and trunking principle and put it into action. We've two routers (R2 and R3) along with switches (SW1 and SW2). R2 is connected to SW1 at fast zero/2, and R3 is linked to SW2 at quick zero/3. Each routers have IP addresses on the 172.12.23.zero /24 network. For these routers to be able to ping each other, the switches must be able to communicate. These are two 2950 switches, and so they're related by way of crossover cables. Before we worry in regards to the router connectivity, let's make sure the trunk link is up between the switches with the "show interface trunk" command. SW2show interface trunk Port Mode Encapsulation Standing Native vlan Fa0/11 fascinating 802.1q trunking 1 Fa0/12 fascinating 802.1q trunking 1 The default mode of these switches is for the ports to run in dynamic fascinating trunking mode, so we didn't even want to write a configuration to have the trunk type - it is already there! Show vlan transient reinforces the theory that by default, all switch ports are placed into VLAN 1 (except the trunk ports). R2 and R3's Ethernet addresses have already been configured, the trunk line is operational, and each ports are in VLAN 1. We'll ping R2's Ethernet interface from R3, and then R3's Ethernet interface from R2 to verify IP connectivity. R2ping 172.23.23.three Sort escape sequence to abort. Sending 5, a hundred-byte ICMP Echos to 172.23.23.3, timeout is 2 seconds: !!!!! Success price is one hundred pc (5/5), round-journey min/avg/max = 4/4/eight ms R3ping 172.23.23.2 Sort escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.23.23.2, timeout is 2 seconds: !!!!! Success price is 100% (5/5), spherical-journey min/avg/max = 4/4/8 ms With pings, exclamation points indicate IP connectivity, and periods indicate no connectivity. So we have got connectivity! Now let's have a look at if we still have that connectivity when the ports are placed into totally different VLANs. Cisco CCNA concept states that units in different VLANs cannot communicate with out the intervention of a Layer three gadget, but let's have a look at if that's true by placing R2 into VLAN 23. (VTP is already operating on these switches.) SW1conf t Enter configuration instructions, one per line. End with CNTL/Z. SW1(config)int fast 0/2 SW1(config-if)switchport mode access SW1(config-if)switchport entry vlan 23 SW1(config-if)^Z Now that R2 and R3 are in separate VLANs, can they nonetheless send pings backwards and forwards? R2ping 172.23.23.3 Sort escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.23.23.3, timeout is 2 seconds: ..... Success fee is 0 % (0/5) R3ping 172.23.23.2 Sort escape sequence to abort. Sending 5, one hundred-byte ICMP Echos to 172.23.23.2, timeout is 2 seconds: ..... No, they can't. The distinction is that they're now in separate VLANs, and gadgets in different VLANs can't talk unless routing is happening somewhere. Right here, no routing is going down, so the pings don't go through. Put R3's swap port into VLAN 23, and try the ping again. SW2conf t Enter configuration instructions, one per line. End with CNTL/Z. SW2(config)interface fast0/three SW2(config-if)switchport mode access SW2(config-if)switchport entry vlan 23 R3ping 172.23.23.2 Kind escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.23.23.2, timeout is 2 seconds: !!!!! Success price is 100 percent (5/5), spherical-journey min/avg/max = four/four/eight ms R2ping 172.23.23.3 Sort escape sequence to abort. Sending 5, one hundred-byte ICMP Echos to 172.23.23.3, timeout is 2 seconds: !!!!! Now that R2 and R3 are in the identical VLAN, pings can go through. This just proves the idea - that inter-VLAN talk requires a Layer three device. Layer three switches are becoming increasingly well-liked, however router-on-a-stick remains to be round - and we'll see learn how to configure that in our subsequent

access point vs router