Langsung ke konten utama

CCNA / MCSE / CCNP Certification: Making Failure Work For You

Whether you're on the road to the CCNA, CCNP, MCSE, or you're on any other computer certification track, the odds are that sooner or later, you're going to fail an exam.  It's happened to almost all of us, yours truly included.   What you have to keep in mind in these times is that success is not a straight line.  You've probably seen charts showing the growth of an industry or a business -- you know, the ones that go from left to right, and look kind of jagged.  The line goes up for a while, then down a bit, then up some more, then down a little.  

The key?  While every business has its setbacks, the net result is that the line goes up and progress is made.  That's how you want your certification pursuit and your career to go as well - upward!

I'm not asking you to be happy about failing an exam.  You're allowed to get mad for a few minutes, vow to never take another exam again, and be disappointed.  What you're not allowed to do is stay that way.  

If you put your books away in a fit of anger, get them out.  If you took some time off, it's time to get back to work.  Again, there's nothing wrong with being unhappy about failing an exam.  It's how you handle that failure that counts.  No inventor, executive, or entrepreneur has ever been right 100% of the time.  Learn something from your failure.   Was your study time quality study time?  Did you get some hands-on practice with the technology you're studying?  Asking yourself these questions can be tough, but it can be highly valuable in making sure you don't fail the next time.  And there must be a next time - because the one thing you cannot do is quit.

Besides, take it from someone who's been there - your temporary failure makes your eventual success that much sweeter.

Komentar

Postingan populer dari blog ini

CCNP / BSCI Exam Tutorial: Route Summarization And The OSPF Null Interface

CCNP exam success, particularly on the BSCI exam, demands you understand the details of route summarization.  This skill not only requires that you have a comfort level with binary conversions, but you have to know how and where to apply route summarization with each individual protocol. You also have to know the "side effects" of route summarization.  With OSPF, there will actually be an extra interface created at the point of summarization, and this catches a lot of CCNP candidates by surprise.  Let's take a look at the null0 interface and how it relates to OSPF summarization. On R1, the following networks are redistributed into OSPF, and then summarized. interface Loopback16  ip address 16.16.16.16 255.0.0.0 interface Loopback17  ip address 17.17.17.17 255.0.0.0 interface Loopback18  ip address 18.18.18.18 255.0.0.0 interface Loopback19  ip address 19.19.19.19 255.0.0.0 R1(config)#router ospf 1 R1(config-router)#redi

CCNA / CCNP Home Lab Tutorial: The VLAN.DAT File

CCNA and CCNP candidates who have their own Cisco home labs often email me about an odd situation that occurs when they erase a switch's configuration.  Their startup configuration is gone, as they expect, but the VLAN and VTP information is still there! Sounds strange, doesn't it?   Let's look at an example.  On SW1, we run show vlan brief and see in this abbreviated output that there are three additional vlans in use: SW1#show vlan br 10   VLAN0010                         active 20   VLAN0020                         active 30   VLAN0030                         active We want to totally erase the router's startup configuration, so we use the write erase command, confirm it, and reload without saving the running config: SW1#write erase Erasing the nvram filesystem will remove all configuration files! Continue?  [confirm] [OK] Erase of nvram: complete 00:06:00: %SYS-7-NV_BLOCK_INIT: Initalized the geometry of nvram

CCNP / BCMSN Exam Tutorial: VLAN Trunking Protocol (VTP)

Passing the BCMSN exam and getting one step closer to the CCNP certification means learning and noticing details that you were not presented with in your CCNA studies. (Yes, I know – you had more than enough details then, right?)   One protocol you’ve got to learn more details about is VTP, which seemed simple enough in your CCNA studies!  Part of learning the details is mastering the fundamentals, so in this tutorial we’ll review the basics of VTP. In show vtp status readouts, the "VTP Operating Mode" is set to "Server" by default.  The more familiar term for VTP Operating Mode is simply VTP Mode, and Server is the default.  It's through the usage of VTP modes that we can place limits on which switches can delete and create VLANs. In Server mode, a VTP switch can be used to create, modify, and delete VLANs.  This means that a VTP deployment has to have at least one switch in Server mode, or VLAN creation will not be possible.  Again, this is the defa