. Section of learning for CCNA test success is maintaining all these new commands immediately in-your head! And let's face it, there are certainly a lot of instructions you need to know to be able to move the CCNA exam and make that accreditation. Here is a review of some essential distance vector and static routing commands you need to know, with their proper use and system output.

Bandwidth

IGRP makes a standard assumption that any Serial screen running IGRP is attached to a line, which runs at 15-44 KBPS. With equal-cost load-balancing enabled automatically, this may be an undesirable assumption.

To modify IGRPs prediction, make use of the bandwidth demand to the serial interface in question. We found out about perry belcher articles by searching Yahoo. I found out about http://perrybelcher.page.tl/ by browsing the Internet. Remember that this control does NOT really affect the bandwidth offered to the interface; it only changes IGRPs assumption of the bandwidth.

R2#conf t

R2( config )#int s0

R2( config-if )#bandwidth 512

Clear ip route *

This command opens your routing table of most non-static and non-connected paths. In a lab setting, its very handy as it makes your routers running routing protocols to request and send updates, as opposed to waiting for the regularly scheduled updates.

R2#clear ip address way *

Debug internet protocol address igrp events

Debug internet protocol address igrp activities allows you to see IGRP updates being sent and required. Here, the de-bug is run and then your routing dining table is removed. The hub straight away shows update needs via the interfaces.

R2#debug ip igrp event

IGRP event debugging is o-n

R2#clear ip way *

06:02:51: IGRP: transmission demand on BRI0

06:02:51: IGRP: broadcasting request o-n Serial0.123

De-bug ip address igrp transactions

To manage IGRP unequal-cost load-sharing with the command, youve got to-know the full of the less-desirable channels. Dig up extra resources on an affiliated wiki - Click here: perrybelcher.sitew.org/#blog.a article. EIGRP retains these in its topology table; IGRP has no such table.

To have the metrics of channels perhaps not in the routing dining table, run debug ip address igrp transactions. To push IGRP changes, the routing dining table below was eliminated with clear ip address route *.

R2#debug internet protocol address igrp transactions

IGRP protocol debugging is on

R2#clear internet protocol address path *

06:05:33: IGRP: received 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, metric 8976 (neighbor 501)

06:05:33: IGRP: model is now 3

06:05:33: IGRP: delivering update to 255.255.255.255 via BRI0 (172.12.12.2)

06:05:33: community 1.0.0.0, metric=8976

06:05:33: IGRP: delivering update to 255.255.255.255 via Serial0.123 (172.12.123.2) - suppressing null update

06:05:34: IGRP: acquired update from 172.12.12.1 on BRI0

06:05:34: subnet 172.12.13.0, full 160250 (neighbor 8476)

06:05:34: network 1.0.0.0, full 158750 (friend 501)

De-bug ip split

R2#debug ip rip

Internet Protocol Address protocol debugging is on

R2#clear ip address way *

6:14:53: RIP: received v2 update from 172.23.23.3 on Ethernet0

6:14:53: 1.0.0.0/8 via 0.0.0.0 in 16 hops (unavailable)

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 16 hops (unavailable)

Work de-bug ip address rip to troubleshoot routing update problems, RIP certification problems, and to look at the routing update articles. Clear ip route * was run to drive a RIP update and to clear the routing table.

Ip way

R2#conf t

R2( config )#ip option 1.1.1.1 255.255.255.255 172.12.123.1

OR

R2( config )#ip way 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 both the next-hop IP-ADDRESS or the exit interface to the local router.

Ip course 0.0.0.0 0.0.0.0

R2#conf t

R2( config )#ip route 0.0.0.0 0.0.0.0 172.12.123.1

OR

R2( config )#ip course 0.0.0.0 0.0.0.0 ethernet0

To change a default static route, use either of the two commands.

You might have any number for the first 0.0.0.0', since the second group of zeroes may be the subnet mask. This elegant TM wiki has varied striking lessons for how to think over this idea. This ensures that any destination will fit this path statement.

That's a great assessment to get going with! I will be back to-morrow with Part II of this CCNA exam demand evaluation!.