DawsonKish817

来自NoteExpress知识库
跳转至: 导航搜索

Part of learning for CCNA exam success is keeping all these new instructions directly in-your head! And let us face it, there are always a lot of instructions you need to know to be able to pass the CCNA exam and earn that certification. Heres a review of some essential distance vector and fixed routing instructions you should know, along with their appropriate utilization and unit output. Bandwidth IGRP makes a default assumption that any Serial program working IGRP is connected to a line, which runs at 15-44 KBPS. Dig up further on the affiliated article directory by visiting save on. With equal-cost load-balancing enabled automatically, this may be an undesirable assumption. To change IGRPs prediction, make use of the bandwidth control to the serial interface in question. For further information, consider peeping at: http://www.perrybelcher.snappages.com/blog/2014/02/22/who-is-perry-belcher-information-for-those-who-are-curious. Note that this demand doesnt really affect the bandwidth offered to the interface; it simply changes IGRPs assumption of the bandwidth. R2#conf t R2 config #int s0 R2 config-if #bandwidth 5-12 Obvious internet protocol address route * This command opens your routing table of most non-connected and non-static channels. In a research environment, its very helpful as it causes your hubs working routing protocols to demand and send updates, in the place of waiting for the regularly scheduled updates. R2#clear ip address option * Debug ip address igrp activities Debug ip address igrp events lets you see IGRP updates being sent and required. To read more, please check out: tumbshots. Here, the debug is run and then your routing table is cleared. The modem instantly broadcasts update needs via the IGRP-enabled interfaces. R2#debug ip address igrp event IGRP event debugging is on R2#clear internet protocol address route * 06:02:51: IGRP: transmission request on BRI0 06:02:51: IGRP: transmission demand o-n Serial0.123 Debug internet protocol address igrp transactions To manage IGRP unequal-cost load-sharing with the alternative command, youve got to-know the full of the less-desirable paths. EIGRP keeps these in its topology table; IGRP does not have any such table. To get the metrics of routes not in the routing table, run de-bug internet protocol address igrp transactions. To drive IGRP updates, the routing dining table below was cleaned with clear ip address route *. R2#debug ip address igrp transactions IGRP protocol debugging is on R2#clear ip address option * 06:05:33: IGRP: acquired update from 172.12.123.1 o-n Serial0.123 06:05:33: subnet 172.12.123.0, metric 10476 neighbor 8476 06:05:33: network 1.0.0.0, full 8976 neighbor 501 06:05:33: IGRP: model is currently 3 06:05:33: IGRP: sending update to 255.255.255.255 via BRI0 172.12.12.2 06:05:33: network 1.0.0.0, metric=8976 06:05:33: IGRP: delivering update to 255.255.255.255 via Serial0.123 172.12.123.2 - controlling null update 06:05:34: IGRP: obtained update from 172.12.12.1 on BRI0 06:05:34: subnet 172.12.13.0, metric 160250 friend 8476 06:05:34: network 1.0.0.0, full 158750 friend 501 Debug ip grab R2#debug ip tear Ip Address protocol debugging is on R2#clear ip address option * 6:14:53: RIP: received v-2 update from 172.23.23.3 o-n Ethernet0 6:14:53: 1.0.0.0/8 via 0.0.0.0 in 1-6 hops inaccessible 6:14:53: 1.1.1.1/32 via 0.0.0.0 in 2 hops 6:14:53: 172.12.0.0/16 via 0.0.0.0 in 16 trips inaccessible 6:14:53: 172.12.12.2/32 via 0.0.0.0 in 2 hops 6:14:53: 172.12.13.0/30 via 0.0.0.0 in 1 hops 6:14:53: 172.12.123.0/24 via 0.0.0.0 in 1 hops 6:14:53: 172.23.0.0/16 via 0.0.0.0 in 1-6 trips unavailable Work debug ip rip to troubleshoot routing update problems, RIP certification problems, and to look at the routing update items. This ideal research perry belcher sites encyclopedia has assorted powerful suggestions for how to ponder it. Clear ip address course * was run to drive a RIP update and to clear the routing table. Ip path R2#conf 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 route to certain destination IP address, make use of the ip route command. The location is followed by a subnet mask, and that can be followed by either the next-hop IP address or the exit program to the local switch. Internet protocol address path 0.0.0.0 0.0.0.0 R2#conf t R2 config #ip path 0.0.0.0 0.0.0.0 172.12.123.1 OR R2 config #ip option 0.0.0.0 0.0.0.0 ethernet0 To change a default static route, use either of these two commands. You might have any number for your first 0.0.0.0, considering that the second set of zeroes is the subnet mask. This means that any destination can fit this route statement. Thats a good review to get going with! I will be back to-morrow with Part II of the CCNA assessment command review!.