Cisco CCNA authorisation upbringing includes troubleshooting your possess impact and that of others. The prizewinning CCNA authorisation upbringing you crapper do is indeed troubleshooting your possess Cisco router and alter configurations - as I'm ever informing my students, I crapper indorse that some nonachievement you attain has been prefabricated before, and you'll belike wager it again digit day. One much ordinary nonachievement involves digit rattling essential CCNA authorisation topics - Frame Relay and routing protocols.
A enrollee was employed on his CCNA communicating bag work and came up with an engrossing problem. He ordered Frame Relay up in a hub-and-spoke plan with R1 as the hub and R2 and R3 as the spokes. He wrote the mass inclose transpose statements:
frame-relay transpose ip 172.12.123.2 122
frame-relay transpose ip 172.12.123.3 123
He was healthy to sound both spokes from the hub, so he acknowledged everything was employed correctly. Then he organized RIP edition 2 on the router and got the mass termination after streaming debug ip rip and parcel the routing plateau with clear ip line *:
03:33:01: IP: s=172.12.123.1 (local), d=224.0.0.9 (Serial0), len 72, sending broad/multicast
03:33:01: IP: s=172.12.123.1 (local), d=224.0.0.9 (Serial0), len 72, encapsulation failed
You haw hit already patterned the problem, and if you did, your CCNA authorisation communicating studies are feat well! The difficulty is that the roadcast choice was mitt soured the inclose transpose statements. roadcast staleness be organized on inclose transpose statements in visit to beam broadcasts and multicasts crossways the inclose link. As you undergo from your CCNA authorisation communicating studies, RIP edition 1 broadcasts updates and RIP edition 2 multicasts them, so the roadcast choice staleness be inform for either edition to beam updates by using those inclose mappings.
He then rewrote the inclose transpose statements as shown below....
R1(config-if)#frame transpose ip 172.12.123.2 122 broadcast
R1(config-if)#frame transpose ip 172.12.123.3 123 broadcast
... and the RIP updates went discover as expected.
R1#debug ip rip
RIP prescript debugging is on
R1#clear ip line *
06:22:13: RIP: sending generalized letter on Loopback0 to 224.0.0.9
06:22:13: RIP: sending generalized letter on Serial0 to 224.0.0.9
06:22:13: RIP: unnoticed v2 boat from 1.1.1.1 (sourced from digit of our addresses)
06:22:14: RIP: conventional v2 update from 172.12.123.3 on Serial0
06:22:14: 1.1.1.1/32 -> 0.0.0.0 in 3 hops
06:22:14: 2.2.2.2/32 -> 0.0.0.0 in 2 hops
06:22:14: 3.3.3.3/32 -> 0.0.0.0 in 1 hops
06:22:14: 172.12.23.0/24 -> 0.0.0.0 in 1 hops
06:22:14: 172.12.123.0/24 -> 0.0.0.0 in 1 hops
06:22:14: RIP: sending v2 update to 224.0.0.9 via Loopback0 (1.1.1.1)
06:22:14: 2.2.2.2/32 -> 0.0.0.0, amount 3, attach 0
06:22:14: 3.3.3.3/32 -> 0.0.0.0, amount 2, attach 0
06:22:14: 172.12.23.0/24 -> 0.0.0.0, amount 2, attach 0
06:22:14: 172.12.123.0/24 -> 0.0.0.0, amount 1, attach 0
06:22:14: RIP: sending v2 update to 224.0.0.9 via Serial0 (172.12.123.1)
Cisco CCNA authorisation depends on noticing info same these, and there's no meliorate artefact to see these info than by employed on actual Cisco routers and switches. Whether you're dealing demolition instance online or purchase utilised Cisco routers and switches, real-time debugs and configurations are the artefact to CCNA authorisation communicating success!
Chris Bryant, CCIE #12933, is the someone of The Bryant Advantage, bag of over 100 liberated authorisation communicating tutorials, including Cisco CCNA authorisation effort schoolwork articles. His inner Cisco CCNA think pass and Cisco CCNA upbringing is also available!
Visit his journal and clew up for Cisco Certification Central, a regular account crowded with CCNA, Network+, Security+, A+, and CCNP authorisation communicating training questions! A liberated 7-part course, How To Pass The CCNA, is also available, and you crapper listen an in-person or online CCNA rush tent with The Bryant Advantage!
