My Experiences with IPv6

I finally cleared enough time on my calendar to start thinking about IPv6 for my corporate network. It’s been quite a while since I last considered implementing IPv6. Fortunately we haven’t had a reason to move forward, so my procrastination has not caused us any grief.
I spent a couple of hours reviewing Ivan Pepelnjak’s Enterprise IPv6 First Steps webinar. Great stuff! It hit on many of the topics I was interested in, including end host address assignments, native IPv6 DNS servers and transition techniques. Armed with a bit of knowledge (always dangerous), I decided to activate IPv6 on my home LAN.
At first I thought my ISP, Comcast, did not support IPv6. I looked for awhile on Comcast’s website to find a rollout schedule, but every link took me back to www.comcast6.net. It was not helpful. I finally broke down and called Comcast support. I was told that IPv6 is enabled in my area, and pretty much everywhere in the Comcast network. My issue turned out to be an old Comcast-provided cable modem. The key to figuring this out is to visit the following web page - http://mydeviceinfo.comcast.net/. This page has an easy-to-use chart of approved devices and whether they support IPv6. I printed this out and took it to my local Comcast office, where they fortunately had a replacement modem available. Be warned, the folks at the Comcast office had never heard of IPv6, but they were able to find a modem on my printed out list. So if you are going to try this yourself, bring the list!
Basic IPv6 Configuration
At home I use a Cisco 1811W router, currently running IOS Advanced IP Services 15.1(4)M6. The following configuration got me up and running on the IPv6 Internet:
ipv6 unicast-routing
ipv6 cef
!
interface FastEthernet0
description ISP Link
ipv6 address autoconfig default
ipv6 enable
ipv6 dhcp client pd comcast-ipv6 rapid-commit
!
interface BVI254
description Home
ipv6 address FE80::1 link-local
ipv6 address comcast-ipv6 ::1/64
ipv6 enable
Adding Security
Of course, the above configuration is wide-open to the Internet, which likely isn’t to be your preferred configuration. I chose to implement Cisco’s Zone Based Firewall solution, using the following configuration (hat tip to Jeremy Stretch for a fine overview):
zone security Trusted
zone security Internet
zone-pair security Trusted->Internet source Trusted destination Internet
service-policy type inspect Trusted_to_Internet
zone-pair security Internet->Trusted source Internet destination Trusted
service-policy type inspect Internet_to_Trusted
! Inside to Outside
class-map type inspect match-any All_Protocols
match protocol tcp
match protocol udp
class-map type inspect match-any Specific_Protocols
match protocol icmp
match protocol http
match protocol https
match protocol ftp
match protocol dns
match protocol ntp
policy-map type inspect Trusted_to_Internet
class type inspect Specific_Protocols
  inspect
class type inspect All_Protocols
  inspect
class class-default
  drop

interface BVI254

 zone-member security Trusted

interface FastEthernet0

 zone-member security Internet

! Outside to Inside (I only allow DNS resolution from OpenDNS servers for content-filtering. I added specific ‘denies’ for domain so I can see if anyone locally is trying to circumvent my security.
ip access-list extended ISP_IN
permit udp host 208.67.222.222 eq domain any
permit udp host 208.67.220.220 eq domain any
deny   udp any eq domain any
ipv6 access-list ISPv6_IN
sequence 21 permit udp host 2620:0:CCD::2 eq domain any
deny udp any eq domain any
class-map type inspect match-any From_Internet
match access-group name ISP_IN
match access-group name ISPv6_IN
policy-map type inspect Internet_to_Trusted
class type inspect From_Internet
  inspect
class class-default
  drop
Overall Thoughts
It’s really not too difficult to get this working, if your ISP supports it. I ran into a lot of trouble trying to implement on an unsupported modem, and then working to determine if this was worthwhile. If your ISP does not support IPv6, you can register with Hurricane Electric’s tunnelbroker.net service and use their templates to configure your router. I went down this path briefly, with nice success, but I ultimately didn’t need to use this service.
Whether this is worthwhile or not depends on your perspective. Enabling IPv6 does not get you any new features or Internet capabilities at this time. I wish that were not the case. I’d love to see companies like Netflix release certain shows earlier on IPv6 servers or something similar. It would drive user adoption and increase pressure on the ISPs to provide this service. The business case for doing something like this is unclear, so it is unlikely to happen.
I was surprised to discover that when the kids are home we have somewhere between 8 – 12 active IPv6 devices on the home network. All of the iPods, iPhones, Kindles, home PCs, etc are IPv6-enabled. The site http://test-ipv6.com/ confirms that each of these devices is fully IPv6 ready (10/10 rating).
So what is out there on the IPv6 Internet? Not too much, in terms of distinct sites. The big ones (Facebook, Google/Youtube, Microsoft) are ready though. Surprisingly, while www.cisco.com is enabled, most of the other Cisco.com URLs do not seem to work. I am also disappointed to learn that OpenDNS’s IPv6 resolvers do not support content filtering. This makes them basically unusable for me, as I count on that service to keep the younger kids out of inappropriate web content.
One final technical issue I found is that it is practically impossible to host a server on IPv6 without opening up that port in your firewall for all IPv6 hosts. For example, if I want to host a web server on 2001:db8::1, I must add an entry in my screening ACL for ::/0 port 80. This is necessary because I cannot guarantee that my provider-assigned prefix will always by 2001:db8::/64. This could be solved with one of two enhancements to IOS:

1. Allowing address wildcards in IPv6 (such as *::1/128, which could be implemented using a bitmask, as in ‘permit tcp ::1 FF:FF:FF:FF:FF:00:00:00:00 eq 80’
2. Allowing the delegated-prefix to be used in ACLs (such as ‘permit tcp comcast-prefix::1/128 eq 80’)

This is a nice-to-have, and not a necessity for my personal usage.

Goals Update

In the spirit of accountability, here are a couple of updates on my stated goals:

 

1) Assist in developing the careers of my co-workers – I never feel terribly confident about meeting this goal. I did recently complete a set of ‘checkpoint’ meetings with my team to get an update on all active projects. That’s a new wrinkle for me; I am generally much more hands-off with my team. I believe this was well-received by the team. I am also attending Cisco Live 2013 with two of my colleagues, as well as guiding the 2013 training choices of my other teammates.

2) Continue offering industry-leading training for the Cisco Certified Design Expert program – I am proud to announce that fifteen active CCDEs took part in my training since I began in 2010. That’s approximately 20% of all certified engineers. I have also completed practice exam review sessions in January and April. I have also opened registration for the July review sessions.

My CCDE Bootcamp in Cairo, originally scheduled for May 2013, has been postponed due to the difficulty in convincing candidates to travel to Egypt. I am hopeful that we will be able to reboot this training in 2014. Lastly, my CCDE Practical Bootcamp scheduled for July 29 – Aug 2 in Orlando, Florida is now guaranteed to run.

3) Spend at least 40% of my professional time creating – This goal has been difficult to meet, and was probably a bit too much of a stretch. I am considering relaxing this goal to 25% moving forward, although no specific decision has been made. I’ve spent quite a bit of time on content creation, especially as it relates to the CCDE program. My current plan is to add additional practice exam questions for my CCDE Practical Bootcamp training, as well as supplement some of my other bootcamp content with more technical details.

4) Get healthier – This is the goal I’ve been most successful in achieving. I successfully completed a 5K run in March. My goal was 30:00 and I completed it in 28:33, without walking. I’ve also lost a significant (for me) amount of body weight. I am extending this goal to lose more body weight and to complete a 5K in 25:00. I may add an endurance-type goal for the fall (10K?), depending on how things go over the next few months.

CCDE Numbering and Requirements

This article is cross-posted from the CCIE Flyer March Issue

Upcoming CCDE Training

A quick note concerning upcoming training offerings. The next CCDE Practice Exam online offering is scheduled for April 27th. Details can be found at http://www.jeremyfilliben.com/p/ccde-practice-exams.html. The next CCDE Practical Bootcamps I am offering are in Cairo, Egypt in May, and Orlando, Florida in July. Details can be found at http://www.jeremyfilliben.com/p/ccde-practical-bootcamp.html.

Future of the CCDE Program

We’ve covered the history of the CCDE over the previous two articles... But what about the future? I expect the number of successful CCDE candidates in 2013 will easily beat 2011’s record of 28. Why? For several reasons:

• Increased Interest in the CCDE Program - I am already seeing record demand for my training offerings. I am also noticing increased activity on the Cisco Learning Network CCDE discussion board. More interest = more candidates!
• Immediate Test Results - This development (introduced in November 2012) will allow unsuccessful candidates to immediately begin preparing for their subsequent attempts. It was common in the early days of the program for candidates to skip every other test date, since they often would not get their results until a few weeks before the next exam offering.
• More Test Dates and Locations - Cisco has already announced four test dates for the CCDE Practical exam, covering a whopping 16 locations. Details can be found at https://learningnetwork.cisco.com/community/certifications/ccde/practical_exam?tab=4.

We’ve already seen a record number of successful candidates during the February testing date -- at least 15, including four of my students! In summary, I am quite confident that the CCDE program is here to stay. This was somewhat in doubt among networkers in the earlier years. I suspect this was due in part to the small number of successful candidates in 2008 - 2010, plus the short life of the CCIE Design certification in the early 2000s. With nearly 100 CCDEs to date, plus the fact that the CCDE is a necessary step on the way to the Cisco Certified Architect program, it is highly unlikely that this certification will be retired. In fact, I suspect the CCDE will broaden into other topics, much like the CCIE. Might there be a CCDE Data Center or CCDE Security in our future?

Certification Requirements

Now that we’ve covered the history and my best guess at a future direction for the CCDE program, how does one actual earn this certification? Like the CCIE program, there is no certification prerequisite needed for the CCDE program. Although CCDE sits on the top of the Network Design pyramid above CCDA and CCDP, neither certification is necessary to attempt the CCDE written exam.

The CCDE written exam is a 120 minute, 90 - 110 question exam that is delivered worldwide at Pearson Vue testing centers. The exam blueprint is quite extensive! Candidates should have strong familiarity with routing protocols, tunneling, quality of service, network management and network security. In contrast to the Practical exam, each written exam question is self-contained. Like all current Cisco exams, it is not possible to go back to previous questions or skip questions during the exam. I really miss that feature of Cisco exams! Without going into any details (respect the NDA!) I am willing to say that there are fewer ‘trivia’ questions on the CCDE written, as compared to the various CCIE-track exams I have taken. Most questions assume a high level of technical knowledge. The questions are more about how to use or evaluate technologies, rather than defining technical terms.

Passing the CCDE written exam recertifies any lower-level Cisco certification (CCNx, CCDx, etc). It also recertifies any current CCIE or CCDE certification. Lastly, passing the exam qualifies you to schedule and take the CCDE Practical exam. Your first CCDE Practical attempt must take place within 18 months of passing the CCDE written exam. You must pass the CCDE Practical within three years of your written exam; if you fail to do so you will be required to retake the written exam prior to any subsequent Practical exam attempts. If you fail the CCDE written exam you must wait six calendar days before re-attempting, and if you pass the exam you must wait six months before retaking the exam.

The CCDE Practical exam is an eight-hour exam that is offered on specific dates and at specific Pearson Vue testing centers. Upcoming test dates can be found on the Cisco Learning Network. The exam currently consists of four distinct scenarios, each consisting of 25 - 35 questions relating to a single network. Each scenario is self-contained; once you complete a scenario there is no reason to remember it for the next test segment. According to the Cisco Learning Network, candidates are required to complete the first and second scenarios in the four hour exam session prior to lunch. After four hours, all participants are escorted to lunch for one hour. Upon returning to the test center, all candidates will begin the third scenario. The third and fourth scenarios must be completed in the four hour exam session that begins after lunch. So in a way you can consider the exam to be two separate four-hour exams, separated by a one hour lunch.

When you have completed the final question of scenario four, your test will end. As you collect your belongings and exit, the Pearson Vue proctor will hand you your score report, with either a “PASS” or “FAIL” result. If you are unsuccessful, the score report will give you a brief breakdown of your results based on the question types present on the exam. If you passed, congratulations! Within a week (and likely sooner) you will receive notification of your CCDE number!

Recertification Requirements

Successful CCDE candidates must maintain their certification credentials by completing one of the following exams every two years:

• Any CCIE Track Written Exam
• Any CCIE Track Lab Exam
• The CCDE Written Exam
• The CCDE Practical Exam - has anyone done this for recertification?
• Successful Completion of the CCAr Program (Both Interview and Board Review) - This one is special, as it recertifies all lower-level certifications for five years... If my reading of the recertification policies correct.

CCDE Numbering System

As many know, the CCIE certification numbering policy began at #1025 and has increased sequentially from there. During the initial public unveiling of the CCDE program in 2007, the team requested thoughts on how CCDEs should be identified. There were several humorous responses, including binary and hexadecimal. The team settled on an eight-digit decimal string. The first four digits signify the year in which a candidate passed the Practical exam. The second four digits uniquely identify the candidate among those that passed in that year. My CCDE number is 20090003, which means I passed in 2009. From the “0003” portion you can infer that I passed early in the year, as compared to someone whose number is significantly higher. For example, four candidates passed during my February 2009 test date. We were given the numbers 20090001 - 20090004. The next test date had five successful candidates, who were given numbers 20090005 - 20090009. According to Cisco, there is no specific meaning about which number you receive during a test date. In fact, my original paperwork indicated my number would be 20090004, but the plaque I received had number 20090003.

It appears now that Cisco is also numbering CCDE candidates by theatre. All of the candidates that I know of that passed in Sydney in February 2013 received low 2013 numbers (20130001 - 20130003, at least). So a bit more information is conveyed by the numbering system. This was not the case in the earlier days of the CCDE program.

There are two other common representations of the CCDE number. The first is the use of a double-colon “::” to eliminate a string of zeros. Using this makes my number 2009::3. I certainly hope every recognizes the IPv6 aspect of this! It is also common to see the second half of the CCDE number represented in hex, especially if it makes it more interesting. For example, 2009::13 is more fun to write as 2009::D.

Next month's article will cover the preparation methods that successful candidates have used.

About Jeremy:

Jeremy Filliben is a 15 year CCIE (Routing/Switching #3851) and a CCDE-certified network architect. Jeremy was a member of the CCDE beta program and passed practical exam in 2009. Jeremy has trained 16 of the ~80 individuals who have passed the CCDE practical exam since 2010 (more than all other training organizations combined). His next CCDE Practical Bootcamp is scheduled for the week of July 29th in Orlando, Florida. More information on Jeremy's CCDE training offerings can be found at www.jeremyfilliben.com.

History of the CCDE Part 2

This article is cross-posted from the CCIE Flyer, published February 2013

We left off last month with the quasi-beta CCDE Practical exam which was offered in October 2008.

Community reaction to the beta was mixed. Most participants felt that the process was worthwhile, as it had forced them to learn technologies and concepts that were outside of their comfort zone. The actual testing experience was (and still is) quite different from the CCIE labs we've all come to know. The entire exam takes place on a single PC, with no 'real-world' devices. There are no routers to configure and most importantly, no proctor to ask clarifying questions. This has been the primary complaint I have heard in the 3+ years I've been training CCDE candidates. The second most common complaint was the long wait time in receiving exam results. It was often the case that registration for the subsequent offering closed within a week of receiving results for the prior exam. Later in this article we will cover the new grading system, which addresses this issue.

The low pass-rate from the October 2008 offering, coupled with the slow announcement of results contributed to a very light turnout for the first exam offering in 2009. Only 27 candidates took part in this exam, which was now held in both London and Chicago. Approximately twelve weeks later, four candidates received passing marks (myself included). For the August 2009 exam date, Cisco announced that they were expanding testing to Hong Kong, but the test site was canceled due to lack of registrations (this also occurred in December 2009). A total of 14 candidates passed the CCDE Practical exam in 2009.

Cisco offered the CCDE Practical exam three more times in 2010. During this year only 13 candidates passed the exam. Testing locations were expanded to include Hong Kong and Sydney. During Cisco Live 2010 in Orlando, Cisco announced some upcoming changes to the Practical exam. The exam would soon be moving to a four-scenario format, rather than six scenarios. It would also be completely rewritten and reformatted to ensure that all major protocols and scenario types would be present on each exam. These announcements turned out to be a bit premature, as they were not implemented until the first test date of 2012. To be fair, CCDE Practical content development is hard work, and it takes a lot of effort to be certain that the test questions are valid. The registration fee also increased to $1400 this year. I believe this was an across-the-board increase for all Cisco Expert level certifications.

The CCDE made a strong push in 2011 to get more candidates into the CCDE program. If I recall correctly, there were several Webex-based CCDE overview sessions provided by the team. The CCDE team created Youtube overview videos to remove some of the mystery from the exam. The exam was offered four times in 2011, with a record 28 successful candidates. Testing was conducted in Bangalore for the first time.

As mentioned earlier, 2012 brought a significant changes to the CCDE Practical exam. The CCDE exams (both written and practical) were relauched as ‘CCDE 2.0.’ The Practical now consists of four distinct scenarios, as opposed to the previous six-scenario exam, but by all indications the exam did not get easier! The second development was that it is no longer possible to miss any significant technologies on the exam. Due to the mixing and matching of scenarios on previous iterations of the exam, it was possible to completely miss a core technology like IS-IS. The new format makes this extremely unlikely, if not impossible. The final significant change in 2012 was the announcement of all testing dates and locations at the beginning of the year. This allowed CCDE candidates to gear their preparation toward a specific test site and date. The CCDE Practical exam was offered three times this year, and testing expanded to include, at various times, San Jose, Raleigh, Istanbul, and Bangkok. According to the CCDE team, testing center locations are determined by candidate demand. They use the locations of CCDE written exam participants to judge whether they should offer the CCDE Practical exam in a specific location.

In November, the final CCDE Practical exam offering of 2012 brought a much-requested improvement to the candidate experience--immediate scoring! As candidates completed the exam and exited their Pearson Vue testing center, a score report was handed to them with either a ‘Pass’ or ‘Fail’ result, just like any non-Beta Cisco written exam. Even unsuccessful candidates were able to appreciate this immediate feedback, as it allowed them to consider whether they wished to prepare for the next scheduled exam date. There were 24 successful CCDE Practical candidates in 2012, bringing the worldwide number of CCDEs to 90. This includes the eight individuals who created the exam, and assumes no one has allowed their CCDE credentials to lapse.

Next month's article will cover the (near term) future of the CCDE program, CCDE certification and recertification requirements, and the numbering system used to identify successful candidates.

About Jeremy:

Jeremy Filliben is a 15 year CCIE (Routing/Switching #3851) and a CCDE-certified network architect. Jeremy was a member of the CCDE beta program and passed practical exam in 2009. Jeremy has trained 11 of the 63 individuals who have passed the CCDE practical exam since 2010 (more than all other training organizations combined). His next CCDE Practical Bootcamp is scheduled for the week of July 29th in Orlando, Florida. More information on Jeremy's CCDE training offerings can be found at www.jeremyfilliben.com.

Goals for 2013

Over the final months of 2012 I started considering my professional and personal goals. After starting with a large list, I’ve narrowed it down to the following. I am comfortable committing to these publicly, which I hope will encourage me to keep to them.

1) Assist in developing the careers of my co-workers - I work with a great team of network engineers, and I consider one of my primary responsibilities to assist them with their professional development goals. I do this by providing recommendations for training and assigning skill-stretching projects to my team. They always respond well to these challenges. I already get helpful feedback from my team, so I will continue to rely on this feedback to measure my success.

2) Continue offering industry-leading training for the Cisco Certified Design Expert program – I’ve been fortunate to assist dozens of excellent engineers with their pursuit of CCDE credentials. In 2013 I will continue offering my CCDE Practice Exam Training, as well as further develop my classroom-based CCDE Bootcamp offering. If you are interested in attending in-person classroom training for the CCDE, please send me an email. I will measure my success by the feedback I receive from training participants.

3) Spend at least 40% of my professional time creating – In past years one my goals has been related to learning. That one was always too easy, as I find that I am constantly reading and studying simply to keep up with the industry and my projects. This year I am going to flip this around and hold myself accountable for creating content. In this category I am including blog posts, course development, writing projects and professional projects. My plan is to measure this based on output, with some guesstimating about the amount of time each project requires. It’s an art, not a science!

4) Get healthier – This is clearly a personal goal, and it is my hope that by publicly announcing it I’ll do a better job of sticking to it. I will measure this goal’s results by feedback from my physician during my annual physical, plus on whether I keep to my exercise goals. I also committed to my son that we would run a 5K in the spring. I *think* I am on track for this… wish me luck! We also run the Newark Main Street Mile in October. I intend to beat my 2012 time by 30 seconds.

I’m going to keep this list to four items. Any more and I will lose focus. If at the end of the year I neglect to provide a ‘How did I do?’ post, please let me know!

Thank you for reading!
Jeremy

History of the CCDE Part 1

This article is cross-posted from the CCIE Flyer, published December 2012

If you are looking for the registration page for the January CCDE Practice Exams, please go to http://www.jeremyfilliben.com/p/ccde-practice-exams.html

What happens when some of Cisco's most senior CCIEs realize they don't have the correct knowledge of IOS trivia to pass the CCIE R/S written exam? They create a new certification program that more accurately covers their current roles, of course! In addition to this predicament, Cisco was getting pressure from customers and partners to develop engineers who could build more scalable and resilient networks. Many readers will agree that the CCIE program develops excellent network implementation skills. Active CCIEs know most of the IOS knobs that can be turned to make networks do things no one else could imagine. One thing the CCIE program does not develop, however, is a solid understanding of network design. The CCIE lab exam is an excellent guide for what not to do in a production network, with three (or more) active routing protocols in an eight router topology. Many CCIEs (especially senior ones) are looked upon to provide network designs and are given titles like 'Network Architect' or 'Network Design Engineer', but historically there was no way to differentiate CCIE-certified individuals who have design skills and those who do not.

In 2007 Cisco commissioned a team to develop a certification program that would test candidates on their ability to design and redesign networks that support the goals of resiliency, scalability and supportability. While I was not a member of this team, I have spoken with team members about this phase of the CCDE program. Cisco included several large customers in this program design phase to ensure that the resulting certification actually covered the skills that customers were seeking in the hiring decisions. The program was formally announced to the Cisco engineer community at Cisco Live 2007 in Anaheim, California. I was fortunate enough to be invited to this meeting. Russ White, Steve Barnes and Bruce Pinsky (all Cisco employees at the time) discussed the goals of this program and offered several example written exam questions. During the following Q&A period there was a spirited discussion concerning the focus of the exam. Was it a Service Provider exam, or an Enterprise exam? The team asserted that the skills being tested were universal, and that a good design engineer with proper technical knowledge of the tools at his/her disposal could develop network designs that meet the needs of either company. At the time this was an eye-opening concept. While I had worked in both the SP and Enterprise realms, I considered myself an Enterprise network engineer/architect and found little use for concepts like MPLS and L2TPv3 in my work. Follow-up discussions with other meeting participants revealed that many others felt the same as I did. I've come to find that even today the CCDE exam is a bit of a Rorschach test; engineers with an Enterprise background often remark on how SP-focused the exam is, while SP engineers feel the exam has too much Enterprise-related content!

The CCDE team, led by David Bump, invited all participants to take the CCDE written Beta exam in the Fall of 2007. They supplied an extensive book list, which was only slightly different than the current book list found at https://learningnetwork.cisco.com/docs/DOC-1673. I immediately decided that this would be my next certification goal, as I had recently taken and passed the CCIE R/S written exam to maintain my CCIE certification, but I too found the process to be difficult (I failed the exam once due to my lack of knowledge concerning L2 LAN technology).

After what seemed like an eternity, the CCDE team announced that they would unveil the CCDE practical exam format during Cisco Live 2008. The Cisco Certification Lounge hosted a computer with an early version of the CCDE Practical Exam Demo (the current version can be found at https://learningnetwork.cisco.com/docs/DOC-2438). For most of the week there was a crowd around this PC, and to add to the pressure the screen contents were simulcast to a large overhead display monitor so everyone within 25 feet could watch you take the exam. Talk about pressure! I earned a score of 22% on the demo and surprisingly that made it onto the makeshift leaderboard. I checked back at the end of the week and noted that the highest score achieved was only 44%. Clearly the practical was going to be a difficult exam.

The first offering of the CCDE Practical exam was an ungraded Alpha exam presented to selected Cisco employees in mid-2008. It did not result in any passing scores; its goal was to iron out any bugs in the testing engine.  At Cisco Live the certification team also announced that there would not be a large-scale Beta exam for the CCDE practical. While the first offering was referred to as a Beta exam, it was not restricted to CCDE Beta team participants and only CCDE Beta program participants were able to receive the reduced price ($980 instead of $1260; current price is $1500). This first official CCDE Practical Exam was offered in October 2008. While I was unable to attend due to a personal commitment, my friend Colin McNamara did a nice job of writing up the experience on his blog. The post can be found at http://www.colinmcnamara.com/my-experience-taking-the-ccde-practical-beta/. After ten weeks of grading, three of the forty-two candidates received passing scores.

Next month's article will cover the history of the CCDE program to the present time and the numbering system used to identify successful CCDE candidates.

For additional information about the early days of the CCDE program, see Michael Morris's blog at http://www.networkworld.com/community/morris. He no longer updates it, but he wrote extensively about the CCDE beta program and Michael was one of the first three candidates to pass the CCDE Practical exam.

About Jeremy:

Jeremy Filliben is a 14-year CCIE (Routing/Switching #3851) and a CCDE-certified network architect. Jeremy was a member of the CCDE beta program and passed practical exam in 2009. Jeremy has trained eleven of the roughly 63 individuals who have passed the CCDE practical exam since 2010 (more than all other training organizations combined). More information on Jeremy's CCDE training offerings can be found at www.jeremyfilliben.com.

January 2013 CCDE Practice Exams

Registration is now open for the January/February 2013 CCDE Practice exam offering. This offering consists of four scenarios based on the CCDE 2.0 Technology Topics and CCDE 2.0 Blueprint. The practice exams have been updated to reflect the CCDE Version 2.0 changes as described by Cisco. In addition to an overview of the CCDE exam, the overview presentation will also include:

• Differential analysis of the CCDE version 1.0 and 2.0 blueprints
• Overview of the CCDE Practical exam format changes between 1.0 and 2.0
• Listing of all new technical content on the CCDE Practical exam, as listed in the Written 2.0 blueprint

The review sessions are scheduled for Saturday, January 26th at 9am ET and Saturday, February 2nd at 9am ET. This should give participants enough time to incorporate their practice exam results into their study plans for the actual Cisco exam on Tuesday, February 19th.

We will cover a broad array of technical content from the CCDE 2.0 Blueprint. Topics will include:

• IP Routing protocols (OSPF, EIGRP, BGP, IS-IS)
• Tunneling (MPLS, GRE, DMVPN)
• Security (uRPF, Filtering, Encryption)
• Quality of Service (Congestion Management, Congestion Avoidance, Packet Marking)
• Network Management (Netflow, SNMP, IPFIX, OOB Management)

The exams cover an array of network designs, balanced between Service Provider and Enterprise topics. To be clear, I do not cover all the technical content that candidates will face on the CCDE Practical exam. That would be impossible to do in four practice scenarios. The primary goals of this offering are:

1. Provide an experience-based overview of the CCDE Practical exam
2. Familiarize candidates with the depth and breadth of individual CCDE Practical scenarios
3. Share my methods for determining the correct answer for each type of question on the exam

I am confident that my practice exam offering meets these goals. I encourage candidates to use the link below to register for this offering. As always, previous participants are encouraged to attend these sessions at no cost. Just drop me an email and I will send you the Webex link.

If you have any questions about the offering or the CCDE program, please write me at jeremy@filliben.com.

CCDE Practice Exam Registration Link