Cisco CCNA Examination Tutorial: The Greatest Time To Schedule Your Exam

In getting ready for CCNA examination success, one of the primary steps is to schedule your exam! And when must you do this? Schedule your examination NOW. I can hear you now -- " Why should I schedule my exam now? I haven't began studying yet!" From experience, I can inform you that this system works. Individuals complain about timetables and deadlines, but the fact is that folks do their finest work with a deadline. "Stress" just isn't the soiled phrase that we've made it out to be. A diamond is barely a lump of coal that was put under pressure. I wish I had a nickel for every time I've heard this: "I'll schedule my examination after I'm ready." You know when "ready" is? For many people, NEVER. I do know someone who's been getting ready for his CCNA for years - actually! He's going to schedule that exam when he's ready. He's been getting ready for years! By scheduling your examination now, you give yourself a psychological deadline. You'll be stunned at how targeted your thoughts becomes when you understand the date of your exam before you start. I have used this technique for my CCNA, CCNP, and CCIE exams. It is going to be just right for you! You possibly can schedule your examination with Prometric or VUE proper now! Just search for both of those corporations in your favourite search engine, and register online today. Each websites have test middle locators, so irrespective of where you are on the planet, you can find the testing center nearest you. All of us have times of the day that we're mentally sharper than others. I personally am a "morning individual", so I all the time schedule my exams for first thing within the morning. google_ad_client = "pub-2311940475806896"; /* 300x250, created 1/6/11 */ google_ad_slot = "0098904308"; google_ad_width = 300; google_ad_height = 250; In the event you're stronger within the afternoon, schedule a day exam. Whatever the time of day you're going to take the examination - schedule it now, right now! CCNA examination success depends largely on noticing the details, and that is especially true of configurations involving immediately linked serial interfaces. And of course, it is not enough to note these details - you've got to know what to do about them! A Cisco router is a DTE by default, but instantly connecting DTEs with a DCE/DTE cable isn't enough. In the following example, R1 and R3 are straight linked at their Serial1 interfaces. The road goes up briefly after being opened, however the line protocol goes down after about 30 seconds. R3(config-if)int s1 R3(config-if)ip address 172.12.13.3 255.255.255.zero R3(config-if)no shutdown 2d18h: %LINK-three-UPDOWN: Interface Serial1, changed state to up 2d18h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, modified state to up R3(config-if) 2d18h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, modified state to down The issue is that one of many routers must act because the DCE in order for the road protocol to return up and stay up. If this had been your CCNA / CCNP dwelling lab, you can simply go over and have a look at the DTE/DCE cable to see which router had the DCE end of the cable attached. In this instance, though, we don't have bodily access to the routers. How can we tell which router has the DCE end of the cable connected? R3show controller serial 1 HD unit 1, idb = 0x1C44E8, driver structure at 0x1CBAC8 buffer dimension 1524 HD unit 1, V.35 DCE cable The show controller command offers us this information. (There's a lot more output that this with this command, but it surely's unimportant for our purposes.) The router with the DCE finish of the cable wants to supply a clock charge to the DTE, and we'll do just that with the interface-level clockrate command. R3conf t Enter configuration commands, one per line. End with CNTL/Z. R3(config)int serial1 R3(config-if)clockrate 56000 2d18h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial1, changed state to up In just some seconds, the road protocol goes up and stays up. When troubleshooting a connection, always run show interface first. Should you see the mixture proven beneath, the connection is physically superb but logically down. That's usually the results of a needed keepalive not being present. With Frame Relay, it is probably an LMI subject, but with straight linked serial interfaces the issue is more than likely the DCE finish of the connection not supplying clockrate. R3show interface serial 1 Serial1 is up, line protocol is down Troubleshooting is a giant part of the job, and it is a big a part of the Cisco CCNA and CCNP packages as well. Know your present and debug instructions and you're on your technique to

access point vs router