A part of studying for CCNA examination success is protecting all these new commands straight in your head! And let's face it, there are a variety of instructions it's essential to know so as to go the CCNA examination and earn that certification. Here is a review of some very important distance vector and static routing commands it's worthwhile to know, along with their proper usage and console output. Bandwidth IGRP makes a default assumption that any Serial interface operating IGRP is linked to a T1 line, which runs at 1544 KBPS. With equal-price load-balancing enabled by default, this may be an undesirable assumption. To alter IGRP's assumption, use the bandwidth command on the serial interface in question. Observe that this command does NOT really have an effect on the bandwidth available to the interface; it merely modifications IGRP's assumption of the bandwidth. R2conf t R2(config)int s0 R2(config-if)bandwidth 512 Clear ip route * This command clears your routing desk of all non-static and non-connected routes. In a lab setting, it's very useful as a result of it forces your routers working routing protocols to send and request updates, quite than waiting for the frequently scheduled updates. R2clear ip route * Debug ip igrp occasions Debug ip igrp occasions means that you can see IGRP updates being despatched and requested. Right here, the debug is run after which the routing table is cleared. The router immediately broadcasts update requests via the IGRP-enabled interfaces. R2debug ip igrp occasion IGRP occasion debugging is on R2clear ip route * 06:02:fifty one: IGRP: broadcasting request on BRI0 06:02:51: IGRP: broadcasting request on Serial0.123 Debug ip igrp transactions To configure IGRP unequal-price load-sharing with the variance command, you've got to know the metric of the less-fascinating routes. EIGRP keeps these in its topology table; IGRP has no such table. To get the metrics of routes not within the routing desk, run debug ip igrp transactions. To force IGRP updates, the routing desk beneath was cleared with clear ip route *. R2debug ip igrp transactions IGRP protocol debugging is on R2clear ip route * 06:05:33: IGRP: received replace from 172.12.123.1 on Serial0.123 06:05:33: subnet 172.12.123.zero, metric 10476 (neighbor 8476) 06:05:33: network 1.0.0.zero, metric 8976 (neighbor 501) 06:05:33: IGRP: edition is now three 06:05:33: IGRP: sending replace to 255.255.255.255 by way of BRI0 (172.12.12.2) 06:05:33: community 1.0.0.0, metric=8976 06:05:33: IGRP: sending update to 255.255.255.255 by way of Serial0.123 (172.12.123.2) - suppressing null update 06:05:34: IGRP: obtained update from 172.12.12.1 on BRI0 06:05:34: subnet 172.12.13.zero, metric 160250 (neighbor 8476) 06:05:34: community 1.0.0.0, metric 158750 (neighbor 501) Debug ip rip R2debug ip rip IP protocol debugging is on R2clear ip route * 6:14:fifty three: RIP: received v2 update from 172.23.23.three on Ethernet0 6:14:53: 1.0.0.zero/8 via 0.0.0.zero in sixteen hops (inaccessible) 6:14:53: 1.1.1.1/32 by way of 0.0.0.zero in 2 hops 6:14:fifty three: 172.12.0.zero/16 by way of 0.0.0.0 in 16 hops (inaccessible) 6:14:fifty three: 172.12.12.2/32 through 0.0.0.0 in 2 hops 6:14:53: 172.12.13.zero/30 via 0.0.0.0 in 1 hops 6:14:53: 172.12.123.0/24 by way of 0.0.0.0 in 1 hops 6:14:fifty three: 172.23.0.0/sixteen by way of 0.0.0.0 in 16 hops (inaccessible) Run debug ip rip to troubleshoot routing replace problems, RIP authentication problems, and to view the routing replace contents. Clear ip route * was run to clear the routing desk and to pressure a RIP update. Ip route R2conf t R2(config)ip route 1.1.1.1 255.255.255.255 172.12.123.1 OR R2(config)ip route 1.1.1.1 255.255.255.255 serial0 To configure a static path to a given destination IP address, use the ip route command. The vacation spot is adopted by a subnet masks, and that can be adopted by either the following-hop IP tackle or the exit interface on the native router. Ip route 0.0.0.0 0.0.0.0 R2conf t R2(config)ip route 0.0.0.0 0.0.0.zero 172.12.123.1 OR R2(config)ip route 0.0.0.0 0.0.0.zero ethernet0 To configure a default static route, use both of those two commands. You possibly can have any quantity for the first "0.0.0.zero", for the reason that second set of zeroes is the subnet mask. Which means that any vacation spot will match this route statement. That's a great overview to get began with! I will be again tomorrow with Part II of this CCNA exam command overview! DNS behaviors of a Cisco router are necessary subjects for each the CCNA exam and actual-world production networks, and you in all probability did not know there were so many DNS details earlier than you began learning for the exam! On this tutorial, we'll take a look at the ip name-server command and its correct usage. When a command is mistyped on a Cisco router, the default conduct of the router is to aim to resolve it through DNS. First, the router seems to be for an IP Host table on the native router to carry out this decision - that's what the "translating" phrase in the output is referring to. If there's no IP Host table or the IP Host desk doesn't contain an entry for what you typed, the router will send a broadcast in an try to resolve this name by means of a remote DNS server. To stop this broadcast, enter the worldwide command no ip area-lookup. In fact, to use DNS to resolve hostnames, ip area-lookup must be reenabled if it's been turned off. R2contin Translating "contin"...domain server (255.255.255.255) % Unknown command or laptop name, or unable to find computer tackle A command is mistyped as "contin". The Cisco router's default conduct is to resolve this entry regionally via an IP Host table, which isn't current on the router. A broadcast is then sent out to discover a DNS server to perform the title resolution. The DNS lookup try must trip before the configuration can continue. R2conf t R2(config)no ip area-lookup R2contin Translating "contin" % Unknown command or laptop title, or unable to search out laptop handle With "no ip domain-lookup" configured, the router doesn't try to find a distant DNS server. It sees there isn't a native decision configured and nearly instantly sends a message to the console that the name can't be resolved. R2conf t R2(config)ip area-lookup R2(config)ip identify-server 10.1.1.1 R2contin Translating "contin"...domain server (10.1.1.1) A DNS server is put in on the community with the IP address 10.1.1.1. DNS lookup is reenabled with the command ip area-lookup, and the IP deal with of the DNS server is specified with the ip name-server command. It's simply that simple to inform a Cisco router exactly the place
Article Source: http://www.articlecontentprovider.com/articlesubmit
To earn your CCNA, you have to keep quite a lot of instructions straight! In this command evaluate, see many of those instructions outlined and in action from Chris Bryant, CCIE 12933.
You'll be able to learn extra in my website , i'm comfortable that you simply read my article, thnak you , you may go to right here
Please Rate this Article
5 out of 5 4 out of 5 3 out of 5 2 out of 5 1 out of 5
