Part of studying for CCNA exam good results is trying to keep all these new instructions straight with your head! And let’s experience it, there are a lot of instructions you have to know to be able to go the CCNA Examination and make that certification. Listed http://query.nytimes.com/search/sitesearch/?action=click&contentCollection®ion=TopBar&WT.nav=searchWidget&module=SearchSubmit&pgtype=Homepage#/토토사이트 here’s an evaluation of some extremely important distance vector and static routing commands you have to know, in addition to their right utilization and console output.
Bandwidth
IGRP will make a default assumption that any Serial interface working IGRP is connected to a T1 line, which operates at 1544 KBPS. With equal-Charge load-balancing enabled by default, this may be an undesirable assumption.
To change IGRPs assumption, use the bandwidth command to the serial interface in problem. Be aware that this command does NOT actually have an affect on the bandwidth available to the interface; it basically adjustments IGRPs assumption in the bandwidth.
R2#conf t
R2(config)#int s0
R2(config-if)#bandwidth 512
Distinct ip route *
This command clears your routing table of all non-static and non-linked routes. In the lab surroundings, its incredibly helpful as it forces your routers functioning routing protocols to send out and ask for updates, in lieu of looking ahead to the regularly scheduled updates.
R2#obvious ip route *
Debug ip igrp activities
Debug ip igrp activities permits you to see IGRP updates getting despatched and requested. Below, the debug is operate then the routing table is cleared. The router instantly broadcasts update requests via the IGRP-enabled interfaces.
R2#debug ip igrp function
IGRP party debugging is on
06:02:51: IGRP: broadcasting request on BRI0
06:02:fifty one: IGRP: broadcasting request on Serial0.123
Debug ip igrp transactions
To configure IGRP unequal-Price load-sharing Along with the variance command, youve bought to be aware of the metric of the fewer-desirable routes. EIGRP keeps these in its topology desk; IGRP has no these kinds of desk.
To find the metrics of routes not in the routing table, run debug ip igrp transactions. To pressure IGRP updates, the routing desk under was cleared with crystal clear ip route *.
R2#debug ip igrp transactions
IGRP protocol debugging is on
06:05:33: IGRP: acquired update from 172.twelve.123.1 on Serial0.123
06:05:33: subnet 172.twelve.123.0, metric 10476 (neighbor 8476)
06:05:33: community one.0.0.0, metric 8976 (neighbor 501)
06:05:33: IGRP: edition is now three
06:05:33: IGRP: sending update to 255.255.255.255 by way of BRI0 (172.twelve.12.2)
06:05:33: network 1.0.0.0, metric=8976
06:05:33: IGRP: sending update to 255.255.255.255 by means of Serial0.123 (172.12.123.two) – suppressing null update
06:05:34: IGRP: acquired update from 172.12.twelve.1 on BRI0
06:05:34: subnet 172.12.thirteen.0, metric 160250 (neighbor 8476)
06:05:34: network 1.0.0.0, metric 158750 (neighbor 501)
Debug ip rip
R2#debug ip rip
IP protocol debugging is on
six:14:fifty three: RIP: received v2 update from 172.23.23.3 on Ethernet0
6:fourteen:fifty three: 1.0.0.0/8 via 0.0.0.0 in 16 hops (inaccessible)
6:14:fifty three: one.1.one.1/32 by way of 0.0.0.0 in 2 hops
six:fourteen:fifty three: 172.twelve.0.0/sixteen via 0.0.0.0 in 16 hops (inaccessible)
6:fourteen:fifty three: 토토사이트 172.twelve.12.two/32 via 0.0.0.0 in two hops
6:14:53: 172.12.thirteen.0/thirty via 0.0.0.0 in 1 hops
6:14:53: 172.twelve.123.0/24 by way of 0.0.0.0 in one hops
six:14:53: 172.23.0.0/sixteen by means of 0.0.0.0 in 16 hops (inaccessible)
Operate debug ip rip to troubleshoot routing update problems, RIP authentication issues, and to see the routing update contents. Obvious ip route * was run to clear the routing desk also to pressure a RIP update.
Ip route
R2(config)#ip route one.1.one.1 255.255.255.255 172.twelve.123.one
OR
R2(config)#ip route one.one.one.1 255.255.255.255 serial0
To configure a static path to a offered spot IP tackle, make use of the ip route command. The desired destination is followed by a subnet mask, and that can be followed by either the subsequent-hop IP handle or maybe the exit interface around the neighborhood router.
Ip route 0.0.0.0 0.0.0.0
R2(config)#ip route 0.0.0.0 0.0.0.0 172.12.123.1
R2(config)#ip route 0.0.0.0 0.0.0.0 ethernet0
To configure a default static route, use either of these two commands.
You could have any number for the 1st 0.0.0.0″, given that the next list of zeroes may be the subnet mask. Therefore any destination will match this route assertion.
That’s a superb evaluation to start out with! I’ll be back again tomorrow with Component II of the CCNA Test command assessment!