Networking Is Not Trivia(l)

Fun fact: my friends and family have banned me from playing Trivial Pursuit.  I played the Genus 4 edition in college so much that I practically memorized the card deck.  I can’t play the Star Wars version or any other licensed set.  I chalk a lot of this up to the fact that my mind seems to be wired for trivia.  For whatever reason, pointless facts stick in my head like glue.  I knew what an aglet was before Phinneas & Ferb.  My head is filled with random statistics and anecdotes about subjects no one cares about.  I’ve been accused in the past of reading encyclopedias in my spare time.  Amusingly enough, I do tend to consume articles on Wikipedia quite often.  All of this lead me to picking a career in computers.

Information Technology is filled with all kinds of interesting trivia.  Whether it’s knowing that Admiral Grace Hopper coined the term “bug” or remembering that the default OSPF reference bandwidth is 100 Mb, there are thousands of informational nuggets laying around, waiting to be discovered and cataloged away for a rainy day.  With my love of learning mindless minutia, it comes as no surprise that I tend to devour all kinds of information related to computing.  After a while I started to realize that simply amassing all of this information doesn’t do any good for anyone.  Simply remembering that EIGRP bandwidth values are multiplied by 256 doesn’t do any good without a bigger picture of realizing it’s for backwards compatibility with IGRP.  The individual facts themselves are useless without context and application.

I tried to learn how to play the guitar many years ago.  I went out and got a starter acoustic guitar and a book of chords and spent many diligent hours practicing the proper fingering to make something other than noise.  I was getting fairly good at producing chords without a second thought.  It kind of started falling apart when I tried to play my first song, though.  While I was good at making the individual notes, when it came time to string them together into something that sounded like a song I wasn’t quite up to snuff.  In much the same way, being an effective IT professional is more than just knowing a whole bunch of stuff.  It’s finding a way to take all that knowledge and apply it somehow.  You need to find a way to take all those little random bits of trivia and learn to apply them to problems to fix things efficiently.  People that depend on IT don’t really care what the multicast address for RIPv2 updates is.  What they want is a stable routing table when they have some sort of access list blocking traffic.  It’s up to us to make a song out of all the network chords we’ve learned.

It’s important to know all of those bits of trivia in the long run.  They come in handy for things like tests or cocktail party anecdotes.  However, you need to be sure to treat them like building blocks.  Take what you need to form a bigger picture.  You won’t become bogged down in the details of deciding what parts to implement based on sheer knowledge alone.  Instead, you can build a successful strategy.  Think of the idea of the gestalt – things are often greater than the sum of their parts.  That’s how you should look at IT-related facts.


Tom’s Take

I’m never going to stop learning trivia.  It’s as ingrained into my personality as snark and sarcasm.  However, if I’m going to find a way to make money off of all that trivia, I need to be sure to remember that factoids are useless without application.  I must always keep in mind that solutions are key to decision makers.  After all, the snark and sarcasm aren’t likely to amount to much of career.  At least not in networking.

Study Advice – Listen To That Little Voice

During Show 109 of the Packet Pushers podcast, I had the unique honor to be involved in an episode that included the uber geek Scott Morris, distinguished Cisco Press author Wendell Odom, and the very first CCDE, Russ White.  Along with Natalie Timms, the CCIE Security program manager and Amy Arnold, we discussed a lot of various topics around the subject of certification.  One of the topics that came up about 37 minutes in was about being persistent in your studies.  Amy brought up a good point that you need to find a study habit that works for you.  I followed up with a comment that I still have a voice in the back of my head that tells me I need to study.  I promised a blog post about that, so here it is only a month late.

I took three years to get my CCIE.  Only the last year really involved intense study on a regular basis.  The previous 24 months, I spent a great deal of time and effort with my regular job.  I picked up a book from time to time and refresh my memory, but I wasn’t doing the kind of heavy duty labbing necessary to hone my CCIE skills.  After I had some conversations with my mentors about what the CCIE really meant to me, I jumped in and started doing as much studying as I could every night.  Almost all of my study time came after my kids went to bed.  Basically, from 8 p.m. until about 1 a.m. I fired up my GNS3 lab and tested various scenarios and brain teasers.  I took me a bit of time before I really settled into a routine, though.  There were lots of things that kept tugging at my attention.  The devilsh Internet, the seductive allure of my television, and the siren call of video games all competed to see which one could lure me away from the warm glow of my console screen.  I had to spend a great deal of time focusing on making a conscious decision to drop what I was doing and start working on my lab.  It’s a lot like running, in a way.  Most runners will tell you that if you can get outside and start running, the rest is easy.  It’s overcoming all the obstacles in your way that are trying to keep you from running.  You have to push past the distractions and keep moving no matter what.  Don’t let an email or a text message keep you from starting R1.  Don’t let a late-night snack run distract you from loading a troubleshooting configuration.  The real key is to get started.  Crack open those lab manuals and fire up your routers, whether they be real or virtual.  After that, the rest just falls into place.

There is a downside to all that training, though.  It’s now been 13 months since I passed my CCIE lab.  To this day, I stil have a little voice in the back of my head telling me that I need to be studying.  Every time I flip on the TV or sit down on the couch, I feel like I should have a book in my lap or have a lab diagram staring me in the face.  I’ve taken some certification tests since the lab, but I haven’t really taken a great deal of time to study something that isn’t familiar to me.  I talked about what I wanted to do at the beginning of the year, and I firmly believe now that I’m halfway through that I’ve missed some opportunities to get back on the horse, as it were.  I know that the only way to satisfy that voice that keeps telling me that I should be doing something is to feed it with chapters of study guides and time in front of the lab console again.  I don’t think it will take the same kind of time investment that the CCIE did, but who knows what it might build into in the end?  I certainly never thought I’d be taking the granddaddy of all certification tests when I first started learning about networking all those many years ago.

For those out there just starting to study for your certifications, I would echo Ethan’s advice during the podcast.  You need to make a habit out of studying.  Many people that I talk to want to study for tests, but they want to do it on someone else’s time.  They want their employer to mark off time for study or provide resources for learning.  While I’m all for this kind of idea and would love to see more employers doing things like this, there is a limit that you will eventually reach.  Your employer expects you to spend your time providing a service for them.  If you truly want to have as much study time as you want, you will have to do it outside working hours.  Your boss doesn’t care what you do from 5 p.m. on.  In the case of the CCIE, it was a whole lot easier for me to try and do mock labs on Saturday than it was to try and do them on Tuesday.  The work week doesn’t afford many uninterrupted opportunities for study.  Nights and weekends do.

Make sure you take your study habits as seriously as you do your job.  It might be easy to kid yourself into thinking that you can just pick up the book for five minutes before the next TV show comes one, but we both know that won’t work.  Unless you immerse yourself in studying, all that knowledge that you gained in those scant minutes of furious reading will evaporate when the theme song to that hit sitcom starts.  You don’t have to have total silence, though.  I find that I do some of my best studying when I have some noise in the background that forces me to pay attention to what I’m doing.  However, if you don’t apply some serious consideration to your studies, you’ll probably end up much like I did in the first couple of years of my studies – adrift and listless.  If you can knuckle down and treat it just like you would a troubleshooting task or an installation project, then you’ll do just fine.

CCDE and CCAr – Why All The Hate?

Cisco Live 2012 gave me an opportunity to sit in a session dedicated to the newer Cisco expert certfications.  BRKCRT-8862 is for CCIEs that are looking at moving to the Cisco Certified Design Expert (CCDE) and maybe even the Cisco Certified Architect (CCAr).  The CCDE is a pretty well known certification at this point.  Developed in large part by Russ White, the CCDE tests a candidate on their knowledge of taking a set of requirements and producing a valid design for a given scenario.  Originally envisioned as a board certification exam not unlike the VMware Certified Design Expert (VCDX), the CCDE is instead an 8-hour exam with some multiple choice and some fill-in-the-blank type questions.  The CCDE is a prerequisite for the CCAr, which is the culmination of something Cisco is trying to do with focusing on solutions.  The CCAr tends to focus more on the Planning and Preparation areas of the PPDIOO model.  Cisco tends to see them as “big picture” solutions engineers that focus on more conceptual ideas that revolve around things like business contraints and specific use cases.  From what Cisco was describing, it appears that the role of the CCAr is to gather information about the customer desires that will then be given to the CCDEs to generate a design.  The CCAr is a 5-month long board exam that is graded by three judges (mostly existing CCArs) that are with you during the entire process, from the initial submission of your application up until the final board review.  Note that not all those that apply to the program will be selected for review.

The BRKCRT session highlighted a lot of hesitation in the CCIE ranks where the CCAr is concerned.  Cisco has spent a lot of time over the last three years attempting to have the CCDE reach parity with the CCIE in terms of importance.  Had they simply called it the CCIE: Design it would likely have been much more accepted in the community.  However, there is a legacy of the original failed CCIE: Design track from a decade ago, so I’m sure that Cisco wanted to avoid carrying the negativity forward.  Instead, they’ve had to fight the reputation that the exam has gotten for being too focused on very specific technologies or being a bad representation of what a design test should be.  Much of this criticism focuses on the major test developer, Russ White.  When I first heard of the exam going live, many people said it was easy so long as you asked yourself “What Would Russ White Do?”  With the new version of the exam being recently released, as well as Cisco offering the exam at new locations, the CCDE may very well be on the road to gaining a little more respect.

The CCAr, on the other hand, is a pretty big target.  CCIEs are upset that the CCDE is the only prerequisite for the exam.  After almost twenty years of being told that the CCIE is the most important certification inside of Cisco, if not the world, now we’re told that the CCIE isn’t even good enough for us to get our foot in the door of the Architect board.  I think some of this comes from the reality that many CCIEs are called upon to do designs in their every day work.  Often, after a CCIE goes through all the training necessary to pass the lab exam, they have a very good idea of the capabilities of the product set within their particular track.  Therefore, many companies call on them to produce designs, as they are usually the best suited to make the decision between using a particular model of switch or router or firewall.  However, not all CCIEs are good at design.  Many of them have a “bottom up” view of things that tends to lead them down the path of point solutions without regard for higher-level thinking.  Call it a “forest for the trees” type of mentality.  They get so bogged down on the decisions between what line cards to use or why they’d rather use a 4500 in place of a 6500 that they lose sight of the bigger goals.  There’s also no guarantee that a CCIE will be able to produce a valid design from a pile of non-technical interviews and business requirements instead of data sheets and performance specs.  The CCDE teaches engineers how to keep a bigger view of things in mind when planning a design.

The problem, however, is that both the CCDE and CCIE are still focused on providing their respective documents, whether they be for design or implementation.  Someone still has to lay the groundwork for the project and figure out how to focus the task of the designers.  Without an even bigger picture, design is just throwing things at the wall until something sticks.  Some designers understand that and ask specific questions before diving into their work.  These are the folks that are the target of the CCAr program.  Cisco doesn’t just want a bill of materials or a pretty Visio document handed to the customer.  They want a cohesive plan and design delivered to sell a vision, whether it be an architecture like a connected sports stadium or a connected energy grid.  Architects take into account more than just technology.  They are constantly thinking about esoteric things like regulatory laws and other logistic restraints.  These are the kinds of things that CCIEs and CCDEs either shy away from or would rather not think about.

Look at it like this:  The CCAr is like the CEO of the team.  They have the vision and the desire to go out and kickstart things by looking at the big picture.  They have to play the role of project manager and pre-sales at the same time.  They keep a handle on the non-technical aspects of the project.  Once they’ve determined the direction, the send in the CCDEs.  These guys take all the documentation the CCAr has generated and meld it with the best practices needed to create a valid, working design.  Once the CCDEs have everything in order, it’s up to the CCIEs to go out and make it all work.  They are the technical piece that gets the hard work accomplished.  The CCAr may not be typing commands in on the CLI, but they are the ones running interference from the other side by keeping customers appraised and kicking over rocks to find things the designers need to know.

If you’d like to read a few more takes on the CCDE, check out Russ White’s Why CCDE? post at the Packet Pushers site.  Also, read about the journey to CCDE success from CCDE 2012::1, Ronnie Angello (@rangello)

Tom’s Take

I’ll be shocked if there are ever more than a hundred Cisco Certified Architects.  The level of thinking required for this exam isn’t something that can be taught.  You are either born to be a technical architect or you aren’t.  With that being said, I think that the skills that are crucial to having a well rounded view of architecture are best served by requiring both the CCIE and CCDE as a prerequisite for the CCAr.  Design without technical know-how is a dicey proposition at best, but trying to attain and architecture role without knowing how to design is equally capable of colossal folly.  Just like any recipe, you need a good mix of both to make the final product come out right.

The CCIE Spelling Bee

I’ve seen a lot of discussion recently about the CCIE with regards to how “hard” the test really is.  There is no denying that the exam is of a very high difficulty level.  The discussion revolves around application.  It has been said that one of the reasons the CCIE lab exam is so difficult is because it doesn’t test the candidate on “real world” network designs.  According to these folks, the CCIE lab tests you on things that you would never see yourself doing in reality outside a lab environment solely for the purpose of seeing how well you can follow directions.  There is some merit to this, as the overview for the CCIE clearly states that this is not a “best practices” examination of networking theory.  It’s a practical implementation test with a given set of parameters and instructions.  There was also a story told in one of my bootcamps with Narbik Kocharians about a student taking a mock lab that took two hours to finish the first section because he spent all his time doing it the “right” way and ensuring there couldn’t be any possible problems down the road.  He thought like an engineer working on a production network instead of a CCIE candidate.  Those clues tend to lend credence to the idea that the CCIE is hard because you are doing things you might not do otherwise.

The more I thought about this, the more I realized the CCIE lab exam is a lot like another type of test that almost every one of us has taken at some point in our lives – a spelling bee.  The time honored tradition of rounding up a group of students and giving them strange words out of the dictionary to see how well they can disassemble them and regurgitate them back in serialized order.  When you think about it, there’s a lot in common with the granddaddy of networking exams.  Both are practical, in that multiple choice isn’t allowed (curiously, the first round of the Scripps National Spelling Bee uses a multiple choice format sometimes, similar to the CCIE written qualification exam).  Both exams don’t give any points for partial credit.  Transposing two letters of a word gets you the same number of points as forgetting to enable mls qos on a switch in the lab (zero).  Both exams give you all the answers up front.  For the CCIE, it’s all there in the documentation. In the spelling bee, you usually get a word list of some kind, either the Spell It! book or Webster’s Third International Dictionary.  In both cases, the amount of documentation that must be sorted through is rather large.  Both tests tend to introduce a large amount of performance anxiety.  And finally, both tests tend to focus on things you wouldn’t normally see for the sake of testing the candidate’s abilities.

Think about this for a moment.  The winning words for the last three National Spelling Bee winners were (in order) cymotrichous, Stromuhr, and Laodicean.  I can’t even pronounce those words, let alone use them in general conversation.  There are even differences in the vocabulary I use in my blog posts versus the words I use in conversation.  Does it make the above words any less valid if the only appear in a dictionary?  No, it doesn’t.  Yes, many of the constructs in the CCIE lab are presented in such a way as to test the candidate’s grasp on applying concepts.  Yes, the lab is crafted in such a way as to eliminate several obvious choices that make life easier.  Just like a spelling bee doesn’t give you access to the dictionary.  Yes, there is a time crunch in the lab.  Just like a spelling bee doesn’t give you three hours to think about how to spell the word.  You only have 2.5 minutes to spell the word from the time it’s first pronounced.  Overall, both the spelling bee and the CCIE lab exam take specific examples that demonstrate advanced concepts and give the test takers a short amount of time to produce results.  It shouldn’t matter that I may never configure multi-router redistribution or RIP neighbor relationships across RSPAN VLANs.  The point is that these examples are designed to test my knowledge of a subject, just like cymotrichous is designed to test my spelling ability a lot better than dog or cat.

Tom’s Take

There’s no denying the CCIE is a hard exam.  The question of real word application versus crafted lab scenarios is a semantic one at best.  While many feel that making the exam reflect scenarios that you might encounter in your job every day would be more appropriate, I feel that having it test a broad subject matter with intricate questions is a better application.  I’d much rather be looking at a problem and think to myself, “Hey! I’ve seen this in the lab before!”  That way, I feel more comfortable having seen it work in a controlled environment before.  At the end of the day, making the CCIE lab a “real world” test is as bad an idea as making the National Spelling Bee only test over words used in everyday conversation.  The test would soon become a very rigid and insular example of the mythical “real world” that would either need to be updated every six months to stay current or it wouldn’t be updated frequently enough and eventually become what people are accusing it of today, namely being a “bad” example of the real world.  I think it’s better to stretch our horizons and spend a little time thinking outside the box for solutions that may not apply in every day life but force us to think about our methods and processes.  Whether that involves routing protocol configuration or challenging the “I before E except after C” rule, the end result is the same.  People question more and dig deeper rather than just accepting someone’s idea of what reality looks like.  And, after all, we know that in our world, I and E really come after two Cs.

So Long To The CCIP

The Cisco Certified Internetwork Professional (CCIP) certification has always been the goal of those network professionals that wanted to march to the beat of a different drummer.  People like me that concentrate on the enterprise/campus side of things revel in our use of OSPF and EIGRP.  We live and die by IOS and get cold sweats at night when someone mentions IS-IS.  The ideal CCIP candidate, on the other hand, loves all of this service provider oriented talk.  They want to spend all their time talking about ingress QoS policies.  They cackle with glee when the subject of MPLS-TE comes up.  They think users are just a myth that exist on the other side of the mythical CPE Wall.

The problem, though, is that the CCIP hasn’t really been focused on the service provider arena for a while now.  While the other professional level exams have received overhauls in the recent past, no one touched the CCIP.  When the CCVP and CCSP became the CCNP: Voice and CCNP: Security, no one wanted to make the CCNP: Internetwork.  The coursework for the CCIP has always relied heavily on other tracks to exist.  QoS is a big part of the SP world, so the QoS exam was borrowed from the voice track.  Routing is another huge part, so the old Building Cisco Scalable Internetworks (BSCI) test was repurposed as well.  The only pure CCIP exams were over BGP and MPLS.  You could even take a composite exam if you were feeling up to the challenge of getting your teeth kicked in for twice as long.  However, the routing exam has caused some consternation.  When I originally studied for my CCNP three years ago, the BSCI book was a handbook of enterprise and service provider routing.  It contained a lot of information about every routing protocol.  While it focused on OSPF and EIGRP, there was a touch of BGP and IS-IS as well.  It served as the foundation for the CCNP, CCDP, and the CCIP.  This made sense with Cisco’s foundation being the router.  However, when Cisco changed the tests and courseware for the CCNP with their latest refresh, the new ROUTE test was a shell of its former self.  Based on the blueprint (login required), it still tests on OSPF, EIGRP, and BGP somewhat.  It even throws in IPv6 routing as well, which is a sorely needed topic.  However, there’s no IS-IS.  None. Nada. Zilch.  How’s that supposed to help the SP engineer that might use IS-IS all the time and never see EIGRP?  Something needed to be done.  And every passing day that the CCIP relied upon tests that didn’t fulfill the criteria of the people being certified was a day that it passed closer to irrelevance.

Thankfully, Cisco decided in May 2012 to overhaul the entire CCIP track.  Now known as the CCNP: Service Provider, it finally focuses on the things that service provider network professionals will be doing.  The four new tests are specific to the SP track.  There are no overlapping tests.  The prerequisite for the CCNP: SP is the CCNA: SP, which is two SP-specific tests of it’s own.  Cisco has finally figured out that most SP engineers exist in a world all their own with very little in common with enterprise/campus folks.  A quick glance at Mirek Burnejko’s excellent IT Certfication Master page for the CCNP:SP shows that the SPROUTE test will focus on IS-IS, OSPFv2 and v3, and BGP.  No EIGRP to be found.  It also tests these topics on IOS-XR and IOS-XE, the new flavors of IOS that run on the equipment that would be found in an SP environment.  If you’d like to see more about the ins and outs of IOS-XR, check out Jeff Fry’s (@fryguy_pa) IOS-XR posts.  The SPADVROUTE test focuses on BGP and multicast, the two odd ducks of routing.  This means that you can spend your time reading Jeff Doyle’s Routing TCP/IP Volume 2 and take a test basically over that whole book.  The SPCORE covers QoS and MPLS functionality such as MPLS-TE.  That’s where I’d expect to see the TE stuff, since it’s usually configured in the network core and not on the edges.  The SPEDGE test covers MPLS VPNs, as well as VPN technologies in general.  I like that Cisco chose to split the core and edge pieces of the CCNP: SP, as there are people that may spend their entire careers working on P routers and never see a piece of CPE equipment.  Conversely, there are those that want to stay as far away from the core as possible and would prefer to make the PE router their device of choice.

The CCNP: SP is available today at any Prometric/VUE testing center.  You can find out more about the certification from Cisco’s website or by visiting Mirek’s site above.

Tom’s Take

Cisco has done a great job of breaking the CCIP up into bite-sized chunks that have clearly defined topic boundaries.  I can choose to focus on interior routing without worrying about multicast.  I can focus on MPLS VPN without thinking too much about MPLS-TE.  I can focus on the important parts one at a time.  The new CCNP: SP also addresses the shortcomings I’ve seen with the old CCIP test.  By giving the SP track a dedicated testing platform all by itself, Cisco no longer has to worry that test changes in one area will carry over to a separate track and cause confusion and delay.  As well, with the new branding and focus on the service provider arena, Cisco has shown that it has not forsaken those that want to spend their time working behind the scenes at ISPs.

Cisco CoLaboratory – Any Questions? Any Answers?

Cisco has recently announced the details of their CoLaboratory program for the CCNP certification.  This program is focused on those out there certified as CCNPs with a couple of years of job experience that want to help shape the future of the CCNP certification.  You get to spend eight weeks helping develop a subset of exam questions that may find their way into the question pool for the various CCNP or CCDx tests.  And you’re rewarded for all your hard work with a one-year extension to your current CCNP/CCDx certification.

I got a chance to participate in the CCNA CoLab program a couple of years ago.  I thought it would be pretty easy, right?  I mean, I’ve taken the test.  I know the content forwards and backwards.  How hard could it be to write questions for the test?  Really Hard.  Turns out that there are a lot of things that go into writing a good test question.  Things I never even thought of.  Like ensuring that the candidate doesn’t have a good chance of guessing the answer.  Or getting rid of “all of the above” as an answer choice.  Turns out that most of the time “all of the above” is the choice, it’s the most often picked answer.  Same for “none of the above”.  I spent my eight weeks not only writing good, challenging questions for aspiring network rock stars, but I got a crash course in why the Cisco tests look and read the way they do.  I found a new respect for those people that spend all their time trying to capture the essence of very dry reading material in just a few words and maybe a diagram.

I also found that I’ve become more critical of shoddy test writing.  Not just all/none of the above type stuff either.  How about questions that ask for 3 correct answers and there are only four choices?  There’s a good chance I’ll get that one right even just guessing.  Or one of my favorite questions to make fun of: “Each answer represents a part of the solution.  Choose all correct steps that apply.”  Those questions are not only easy to boil down to quick binary choices, but I hate that often there is one answer that sticks out so plainly that you know it must be the right answer.  Then there’s the old multiple choice standby: when all else fails, pick the longest answer.  I can’t tell you how much time I spent on my question submissions writing “good” bad answers.  There’s a whole methodology that I never knew anything about.  And making sure the longest answer isn’t the right one every time is a lot harder than you might think.

Tom’s Take

In the end, I loved my participation in the Cisco CoLaboratory program.  It gave me a chance to see tests from the other side of the curtain and learn how to better word questions and answers to extract the maximum amount of knowledge from candidates.  If you are at all interested in certifications, or if you’ve ever sat in a certification test and said to yourself, “This question is stupid!  I could write a better question than this.”, you should head over to the Cisco CoLaboratory page and sign up to participate.  That way you get to come up with good questions.  And hopefully better answers.

CCIE Data Center – The Waiting Is The Hardest Part

By now, you’ve probably read the posts from Jeff Fry and Tony Bourke letting the cat out of the CCIE bag for the oft-rumored CCIE Data Center (DC) certification.  As was the case last year, a PDF posted to the Cisco Live Virtual website spoiled all the speculation.  Contained within the slide deck for BRKCRT-1612 Evolution of Data Centre Certification and Training is a wealth of confirmation starting around slide 18.  It spells out in bold letters the CCIE DC 1.0 program.  It seems to be focused around three major technology pillars: Unified Computing, Unified Fabric, and Unified Network Services.  As people who have read my blog since last year have probably surmised, this wasn’t really a surprise to me after Cisco Live 2011.

As I surmised eight months ago, it encompasses the Nexus product line top to bottom, with the 7009, 5548, 2232, and 1000v switches all being represented.  Also included just for you storage folks is a 9222i MDS SAN switch.  There’s even a Catalyst 3750 thrown in for good measure.  Maybe they’re using it to fill an air gap in the rack or something.  From the UCS server side of the house, you’ll likely get to see a UCS 6248 fabric interconnect and a 5148 blade chassis.  And because no CCIE lab would exist without a head scratcher on the blueprint there is also an ACE 4710 module.  I’m sure that this has to do with the requirement that almost every data center needs some kind of load balancer or application delivery controller.  As I mentioned before and Tony mentioned in his blog post, don’t be surprised to see an ACE GSS module in there as well.  Might be worth a two point question.

Is the CCIE SAN Dead?

If you’re currently studying for your SAN CCIE, don’t give up just yet.  While there hasn’t been any official announcement just yet, that also doesn’t mean the SAN program is being retired any time soon.  There will be more than enough time for you SAN jockeys to finish up this CCIE just in time to start studying for a new one.  If you figure that the announcement will be made by Cisco Live Melbourne near the end of March, it will likely be three months for the written beta.  That puts the wide release of the written exam at Cisco Live San Diego in June.  The lab will be in beta from that point forward, so it will be the tail end of the year before the first non-guinea pigs are sitting the CCIE DC lab.  Since you SAN folks are buried in your own track right now, keep heading down that path.  I’m sure that all the SAN-OS configs and FCoE experience will serve you well on the new exam, as UCS relies heavily on storage networking.  In fact, I wouldn’t be surprised to see some sort of bridge program run concurrently with the CCIE SAN / CCIE DC candidates for the first 6-8 months where SAN CCIEs can sit the DC lab as an opportunity and incentive to upgrade.  After all, the first DC CCIEs are likely to be SAN folks anyway.  Why not try to certify all you can?

Expect the formal announcement of the program to happen sometime between March 6th and March 20th.  It will likely come with a few new additions to the UCS line and be promoted as a way to prove to the world that Cisco is very serious about servers now.  Shortly after that, expect an announcement for signups for the beta written exam.  I’d bank on 150-200 questions of all kinds, from FCoE to UCS Manager.  It’ll take some time to get all those graded, so while you’re waiting to see if you’ve hit the cut score, head over to the Data Center Supplemental Learning page and start refreshing things.  Maybe you’ll have a chance to head to San Jose and sit in my favorite building on Tasman Drive to try and break a brand new lab.  Then, you’ll just be waiting for your score report.  That’s the hardest part.

CCIE Numbers Skyrocket – Red Alert?

Congratulations to Chris Martin, CCIE# 34310, according to IPExpert’s Successful Candidates page.  Thanks to Windows Calculator and my non-binary math skills, that means we’ve had 5,000 new numbers since my pass back in June.  That’s not counting the repeat passes that keep the same number.  The new numbers have been skyrocketing in the last 3 months, shooting up over 2,000 since Blake Krone passed his lab at the end of October.

I’ve heard a lot of interesting theories in the past couple of weeks about why the numbers are shooting up so quickly.  Some attribute it to the official Cisco 360 training program churning out candidates left and right.  There are also those that believe there is something hinkey is going on with the numbering scheme.  Is Cisco pre-allocating numbers to each lab seat every day and then discarding them if the lab isn’t passed?  Are they counting by even numbers now?  Is the numbering now logarithmic?  Add in the recent troubles that Marc La Porte has had with Cisco and his unofficial CCIE Hall of Fame Webpage and the conspiracy theories started spreading like wildfire.  Why is Cisco trying to take down the page?  Are they trying to hide something?

After listening to all the theories and rumors and some of the more outlandish theories that I didn’t even bother to put down, I keep thinking back to a conversation that I had with Terry Slattery back at Cisco Live 2011.  Being the fanboy that I am, I had a chance to ask Terry what he thought about the CCIE numbers climbing ever so higher.  Some of the thoughts he shared with me were rather intriguing and got me to thinking about things in a light that I hadn’t really considered before.  With the acceleration of the new numbers being spit out, I think now more than ever that Terry might have been on to something.

Let’s say for the sake of argument that there isn’t anything funny going on with the numbers.  Let’s also assume that there isn’t rampant cheating going on, as some have suggested to me.  That means that we have a large number of people taking and passing the lab.  But we aren’t hearing about them.  They don’t have blogs or spend time on Groupstudy or post success stories on LinkedIn.  There isn’t any information about them out there.  Almost as if they didn’t really have a big presence on the Internet.  As if they weren’t really looking to market their skills to others and instead were either already at jobs that required the CCIE or had one lined up and ready to go.  Where would such a thing be possible?

China.

Stop and think about it for a minute.  According to Cisco, China is seeing explosive growth in networking, everything ranging from power systems to survellience.  They’re ramping up and infrastructure that’s going to need to support over a billion people all looking to get connected somehow.  China is leading the way in deploying IPv6 internally as a way to alleviate the exhaustion of IPv4 addresses.  Ask yourself then: Where are they getting all these engineers?  How many of your friends and colleagues are flying to China to work on these massive projects?  I’m guessing hardly any.  Why’s that?  Where is the supply coming from to meet this massive demand?

I believe that there are sponsored learning facilities inside China that are essentially functioning like advanced technology vocational technology centers in an effort to train a workforce to go out and assume the roles needed to build and maintain advanced networking and computing infrastructures.  That way, they don’t need to sort out all the details of arranging for a large number of visas to allow foreign engineers to come and work for months at a time.  They also don’t have to worry about bad press from said foreign engineers coming back home and discussing things like the Internet filtering policies.  Instead, they can focus on creating a highly-skilled group of workers to go out and tackle these huge projects.  Because these facilities are likely sponsored or run by the government, profit is of less concern than results.  And if you have a populace that is willing to clamor toward a job that doesn’t involve manual labor or other undesirable work, you would have a motivated pool of talent to pick from.  Taking into account the mind-bending numbers of people available for these jobs, passing even 1,000 extra CCIEs into the global pool is a blip on the radar for China.

One other thing that I’ve mentioned before lends credence to the Chinese CCIE theory in my mind.  Remember those dastardly Open Ended Questions that I hated so much?  Guess which testing facility instituted the in-person interview process that led to the OEQs before the new troubleshooting section?  That’s right, Beijing.  I’m not accusing anyone of wrongdoing.  But the fact that the OEQ program originated there means they must have had a very high pass rate they were suspect of in the first place.  What if the pass rate is still legitimately high even with the new safeguards against impropriety?  Since Cisco doesn’t release numbers on pass rate per lab, I guess we’ll never know.

Tom’s Take

At this rate, we’re looking at seeing CCIE 40,000 before the end of the year.  That’s really going to hit home for people if it took almost 3 years to go from 20,000 to 30,000 and then only takes a year to climb up to 40,000.  I don’t like to think about the idea that lab cheating is so rampant that Cisco has given up trying to protect the value of the CCIE.  Quite the contrary, I’ve heard rumors that the difficulty of the lab is as strong as ever and people are working as hard as they can to get their digits.  To me, that says there is a large contingent of people passing the lab and not talking about it, either by their own choice or the choice of someone above them.  And since we in the U.S. aren’t seeing the workforce flooded with new CCIEs daily, that must mean those passing are someone other than the U.S. (or Europe).  Add in the fact that there aren’t many network rock stars studying Mandarin or watching Ni How Kai-Lan and I am guessing that means that many of our new unknown CCIE brethren are from the Orient.  No crazy conspiracies or funny math.  Just a group of dedicated people doing their best to make it in the world.

2012, Year of the CCIE Data Center?

About six months ago, I wrote out my predictions about the rumored CCIE Data Center certification.  I figured it would be a while before we saw anything about it.  In the interim, there are a lot of people out there that are talking about the desire to have a CCIE focused on things like Cisco UCS and Nexus.  People like Tony Bourke are excited and ready to dive head first into the mountain of material that is likely needed to learn all about being an internetworking expert for DC equipment.  Sadly though, I think Tony’s going to have to wait just a bit longer.

I don’t think we’ll see the CCIE Data Center before December of 2012.

DISCLAIMER: These suppositions are all based on my own research and information.  They do not reflect the opinion of any Cisco employee, or the employees of training partners.  This work is mine and mine alone.

Why do I think that?  Several reasons actually.  The first is that there are new tests due for the professional level specialization for Cisco Data Center learning.  The DC Networking Infrastructure Support and Design Specialist certifications are getting new tests in February.  This is probably a refresh of the existing learning core around Nexus switches, as the new tests reference Unified Fabric in the title.  With these new tests imminent, I think Cisco is going to want a little more stability in their mid-tier coursework before they introduce their expert level certification.  By having a stable platform to reference and teach from, it becomes infinitely easier to build a lab.  The CCIE Voice lab has done this for a while now, only supporting versions 4.2 and 7.x, skipping over 5.x and 6.x.  It makes sense that Cisco isn’t going to want to change the lab every time a new Nexus line card comes out, so having a stable reference platform is critical.  And that can only come if you have a stable learning path from beginning to end.  It will take at least 6 months to work out the kinks in the new material.

Speaking of 6 months, that’s a bit of the magic number when it comes to CCIE programs.  All current programs require a 6 month window for notification of major changes, such as blueprints or technology refreshes.  Since we haven’t heard any rumblings of an imminent blueprint change for the CCIE SAN, I doubt we’ll see the CCIE DC any sooner than the end of the year.  From what I’ve been able to gather, the CCIE DC will be an add-on augmentation to the existing CCIE SAN program rather than being a brand new track.  The amount of overlap between DC and SAN would be very large, and the DC core network would likely include SAN switching in the form of MDS, so keeping both tracks alive doesn’t make a lot of sense.  If you start seeing rumors about a blueprint change coming for the CCIE SAN, that’s when you can bet that you are 6-9 months out from the CCIE DC.

One other reason for the delay is that the CCIE Security lab changes still have not gone live yet (as of this writing).  There are a lot of people in limbo right now waiting to see what is changing in the security internetworking expert realm, many more than those currently taking the CCIE SAN track.  CCIE Security is easily the third most popular track behind R&S and SP.  Keeping all those candidates focused and on task is critical to the overall health of the CCIE program.  Cisco tends to focus on one major track at a time when it comes to CCIE revamps, so with all their efforts focused on the security track presently, I doubt they will begin to look at the DC track until the security lab changes are live and working as intended.  Once the final changes to the security lab are implemented, expect a 6-9 month window before the DC lab goes live.

The final reason that I think the DC will wait until the last part of the year is timing.  If you figure that Cisco is aiming for the latter part of the calendar year to implement something, it won’t happen until after August.  Cisco’s fiscal year begins on August 1, so they tend to freeze things for the month of August while they work out things like reassigning personnel and forecasting projections.  September is the first realistic timeframe to look at changes being implemented, but that’s still a bit of a rush given all the other factors that go into creating a new CCIE track.  Especially one with all the moving parts that would be involved in a full data center network implementation.

Tom’s Take

Creating a program that is as sought after as the CCIE Data Center involves a lot of planning.  Implementing this plan is an involved process that will require lots of trial and error to ensure that it lives up to the standards of the CCIE program.  This isn’t something that should be taken lightly.  I expect that we will hear about the changes to the program around the time frame of Cisco Live 2012.  I think that will be the announcement of the beta program and the recruitment of people to try the written test beta.  With a short window between the release of the cut scores and beta testing the lab, I think that it will be a stretch to get the CCIE DC finalized by the end of the year.  Also, given that the labs tend to shut down around Christmas and not open back up until the new year, I doubt that 2012 will be the year of the CCIE DC.  I’ve been known to be wrong before, though.  So long as we don’t suffer from the Mayan Y2K bug, we might be able to get out butts kicked by a DC lab sometime in 2013.  Here’s hoping.

Certification Merit Badges

I had an interesting exchange with a couple of Twitter folks the other day.  Jason Biniewski (@Jason_Biniewski) started it off with this interesting tweet:

http://twitter.com/#!/Jason_Biniewski/statuses/154445884027965440

Jason, Fernando Montenegro (@fsmontenegro) and I engaged in a little back-and-forth about the relative value of certification.  This is something that I do hear from many people, though.  Many employers don’t see the value of certification.  Some supervisors (like Jason’s) don’t think certifications are worth the paper they are printed on.  I have a totally different stance, and not just because of the giant Wall of Shame behind my desk.

Next time you run into someone that doesn’t think certifications hold much value, ask them to show your their diploma.  If this person is a supervisor or management type, they are sure to happily point out their degree from a prestigious organization.  In some cases, more than one.  Guess what?  In my mind, those college degrees are the same as certifications.  I have a bachelor’s degree.  I have a CCIE.  To me, those are very similar.  They both involve a large amount of studying.  Both study programs are fairly regimented to ensure the student gains the proper amount of knowledge to successfully execute upon that knowledge base.  Both are expensive to chase after.  Both are far from easy.  It just so happens that one of those taught me how to be a business leader and database admin and the other taught me how to work on routers and switches.  In the end, for both of them I ended up with a piece of paper that had my name printed on it that I could hang on my wall as a banner to tell everyone what I had accomplished.

One of the smartest men I ever worked with had no college degree and very few certifications.  No A+, no CCIE.  However, he had an instinctive understanding of the way computers worked and was quick to fix most every problem he encountered.  People constantly underestimated him because they didn’t see his diploma hanging on his wall or noticed his Novell/Microsoft/Cisco certifications.  I only made that mistake once.  That was the moment when I started realizing that certifications aren’t a measure of knowledge in and of themselves.  They’re more like merit badges.

I was a Boy Scout back in the day.  I loved pouring over the scouting handbook and picking out all the merit badges I wanted to earn.  You might even say it was an early precursor to what I’m like today.  I found it interesting that I merely needed to demonstrate my knowledge about a subject and the scouting organization would give me a little badge or pin that told everyone I knew how to make a campfire or pitch a tent.  Whenever I encountered another person with that same merit badge, I knew instinctively that person knew as much about the subject as I did.  I didn’t have to wonder if they knew the ins and outs of something they had a badge for.  That’s what certifications do for you.  They give you a little badge you can put on your resume so you can announce to people that you know a certain amount of basic information.  If you are an MCSE, I know you are familiar with Active Directory.  If you are a CCNA, I know you know what a router is.

If these certifications are so great, why would an employer be hesitant to want you to get one?  I did some thinking and asked a few people and I could really only come up with a couple of reasons.  The first involves companies that aren’t focused on things like value-added reselling.  These companies might be manufacturers or law firms or schools.  They don’t resell their IT services to others but instead consume them in-house.  To these organizations, what you know is more important that telling someone what you know.  So long as you are familiar with setting up Exchange or configuring a floating static route, who cares if you took a test to prove it?  These types of companies typically gain little for paying to have someone certified.  They also don’t see the value in the learning process toward certification.  So long as you can do your job effectively, learning more than is needed isn’t necessary.  I would recommend finding ways to prove that certification can reduce costs or provide extra value for the company as an incentive to get funding or time off for study.  Also, don’t underestimate the potential increase in prestige for employing a higher-caliber technical person.  Some companies treat prestige like a currency.

The other major issue with employers when it comes to certification is fear.  This is usually manifested by the idea that the employer doesn’t want you to pass any tests because they are afraid that you’ll jump ship once you’ve become a CCNA/CCNP/CCIE and leave them holding the bill.  Especially in the VAR space, employers become squeamish if they spend a lot time training someone only to have a competitor swoop in and offer a premium to hire that person away.  The competitor gains a highly trained resource for a pittance compared to the time and effort of training them.  If these types of employers do decide to fund your studies, they will typically do things like have you sign a contract for a length of time or agreement to pay back a portion of the training and certification costs if you decide to leave.  These types of things can be hard to combat.  If you aren’t willing to go the route of certification totally on your own, you may have to sign the agreement or otherwise convince your employer of the benefits of certification.  Just ensure that if you do have to sign an agreement that the clock doesn’t reset for every certification passed.  I’ve heard of people that kept re-upping for a new term with every test passed.  The bill to get out of that contract wasn’t pretty.


Tom’s Take

When I first started working for my present employer, the owner interviewed me and said, “Boy, I’m going to put a quarter of a million dollars into training you to be the best.” Almost eight years later when I passed my CCIE, I asked him if he’d hit his quarter of a million yet. He laughed and replied, “Long ago, son.  And it has been worth every penny.”  I’m fortunate that I get to work with people that understand the value of certifications.  It also helps that I work for a VAR that wants to show them off and use them for competitive advantage in the market.

The next time someone tells you that certifications are a waste of time, ask them where they graduated from, especially if it’s a college.  Explain to them that a certification isn’t any different than a college degree and confers a similar level of knowledge, albeit a little more focused on one area than a general education degree.  Then remind them that the diploma hanging on their wall is worth the same amount at the paper your certification is printed on.  Just don’t ask them how much they payed for their paper.  I’m sure you got a better deal on yours.