Should be an amazing week with all the other delegates that have been selected already, just look at the talent that is going to be attending:

	Marcus Burton	CWNP	@MarcusBurton
	Sam Clements	SC-WiFi	@Samuel_Clements
	Daniel Cybulskie	SimplyWiFi	@SimplyWifi
	Rocky Gregory	Intensified	@BionicRocky
	Tom Hollingsworth	The Networking Nerd	@NetworkingNerd
	Jennifer Huber	Wireless CCIE, here I come!	@JenniferLucille
	Blake Krone	Digital Lifestyle	@BlakeKrone
	Chris Lyttle	WiFi Kiwi’s Blog	@WiFiKiwi
	Andrew vonNagy	Revolution Wi-Fi	@RevolutionWiFi

I’ve met a lot of the delegates at various Cisco events: Sam and Jennifer I see at all the Cisco Mobility PVT’s, Tom and Andrew I hung out with at Cisco Live 2011 (way too much fun!). I’m looking forward to finally meeting Chris and Rocky in person after talking to them online for a little over a year now!

All and all this should be a great week and I can’t wait for the learning to start! Stay tuned for post event blogs as well, I’m sure I’ll have some good ones!

If you have been following me on Twitter (@blakekrone) or read my other blog post CCIE-Wireless Lab: What Did I Learn you know I’ve been working hard at obtaining those digits for awhile now. It’s quite a relief knowing that I’m done and that it is in fact doable. This time around I wasn’t nervous about the lab at all, I knew I had fixed a lot of my mistakes in practice and speed was on my side. I thought I would share some of my tactics on how I finally conquered the exam.

• ORGANIZE - In order to pass this test you need to be organized, you can’t just step through the exam. The very first thing I do when I sit down is I read the ENTIRE workbook page by page. As I’m reading I’m writing down in outline format the key points to each section and how many points the section is worth. This allows me to have a “checklist” for when 3/4pm comes around and it is time to verify.
• SPEED – The name of the game in version 1 is speed. Given the multitude of WLCs that you are presented with you really need to know how to configure them from the CLI. Notepad is your friend during the lab, every command that I ran on any of my hardware was saved in Notepad documents, this allowed me to verify what I had done (looking for typos), remember what I had done, and also allowed me to copy paste between devices. My favorite code snippet that I used was “save config CR (carriage return) y CR” which allowed me to save the config on my WLCs in a matter of seconds (useful for before lunch, end of day, etc). You also need to know Autonomous CLI backwards and forwards.
• EXECUTE – The very first thing I do in the execute phase is group together common tasks and a proper task flow of my outline. Just because the workbook has something as the last step doesn’t mean you can’t do that first if it makes sense. As I go through my own outline I’m looking at the workbook at the same time, applying all the configurations from my Notepad documents or using the GUI if I have to. By using scripts I can create 6 dynamic interfaces for example across multiple WLCs in less than 5 minutes. As I step through my outline I’m putting a line through each item that I know is correct, and circling anything that I might have to go back to.
• VERIFY – I can’t stress this one enough! This was my biggest failure in all my previous attempts, I simply didn’t know the right show commands to verify my configuration was actually 100% correct and followed what was asked of me. Your verify stage should be started by 3pm, 4pm at the latest to fully get through the entire workbook a second time. Remember, the devil lies in the details on this exam. Just because it doesn’t make sense doesn’t make it wrong, this is a lab not real life!

The CCIE Lab not only tests your technical skills, but it also tests how methodically you can think, something we need to do when we are installing or when we architect a design in real life. I’ve heard multiple times that this lab was designed to be done in 4 hours, I started configuring my hardware at 10am after doing all my planning. We had a 30 minute lunch break around 1115-1145. I was completely done with my configurations by 3pm, which left me 2 hours to verify which was important as I found a couple of typos that I had made. Once 4pm roles around consider your configuration FROZE, DO NOT CHANGE UNLESS ABSOLUTELY NECESSARY! I can’t stress that enough, on one attempt I made the stupid mistake of trying something different on my client PC at 4pm, this resulted in my completely hosing my VM image and I had to ask for them to restore the image. I got the image back at 445pm and had to rush through those steps again.

Finally, don’t give up. I’m not afraid to show this image, it took me 5 tries, but it only took me 1 to pass.

Ok, with that out of the way let’s get down to business without breaking any NDA rules.

1) FOR THE BETA: FAILURE IS THE ONLY OPTION? This test was poorly delivered, I had so many errors and mistakes in my exam that even if I were to have done lets say a 90% correct I still had no chance of passing. I had about 4 exhibits that didn’t show up resulting in me using my best guess elimination trying to pick the right 2 or 3 correct answers that maybe had a chance of correlating together. There was a few questions that I had the same answer listed twice, but, the kicker is that had they used the right negative (can / can’t, etc) one of them would be the right answer! So when you are presented with that which one do you choose?!?

2) KNOW THY PHY! I was thoroughly impressed with the fact that Cisco actually made more questions regarding the physical RF layer on the exam. All through the NA/NP exams I have felt there is a lack of RF questions, the exams are more of a how do you design a Cisco solution than how do you design RF networks. This has resulted in me always recommending people look at the CWNP exams to supplement the Cisco exam series, something I’m hoping to do once I get those magical numbers.

3) KNOW THE OBSCURE! Anyone can answer a question that is obvious about the Cisco product line, but can you answer the strange odd questions about Fresnel zones and odd/even bits? Or can you answer the strange QoS questions regarding UP packet markings at all the different levels (switch, IOS AP, thin AP, WLC, etc) and where the markings are in the packets structure?

4) READ, READ, READ! You can never read those design guides or technotes enough times, each time you read them you’ll find something else that is important. If you are truly committed to the CCIE-Wireless track you’ll find yourself reading these documents a hundred times before your lab. All those exam questions have to be backed up somewhere so the answers are there, you just need to figure out how to retain all that obscure information from above.

5) GET YOUR HANDS DIRTY! The key is to take what you read a hundred times and actually try applying the practices in a lab environment, yes this is the written but if you start to get into the habit of doing labs now that will set you up for success later on when you sit the 8 hour expensive lunch known as the IE Lab.

6) FINALLY, HAVE FUN! I know this one seems strange, but it’s just a test, this doesn’t determine whether or not you are going to be a garbage man or a doctor. If you fail, you just know now what you need to study and what the questions are like.

So, to conclude I’m sure glad I didn’t spend the full price to sit this test, I am bummed that I’m out $50 without even having a chance at passing given all of my errors on my test, but I provided feedback to the development team that will hopefully allow them to create a better test once it hits production. So far from what I have heard from others that took the beta exam my experience seems to be on par with them as well. As long as we all provided feedback then Cisco got what they wanted, guinea pigs to let them know what needs to be fixed before it goes live.

If you sat the exam please feel free to post your feedback in the comments, I’d love to hear what others thought about the exam!

For every Cisco Live! event that is held Cisco builds their own network to support the conference attendees, sponsors, and speakers. This gives Cisco the opportunity to get a large set of data points regarding their products performance in abusive conditions. Lately we have seen or heard about the BYOD (bring your own device) phenomenon that is sweeping across the enterprise network and there is no better place to see that than a large IT conference. One can safely assume that for all the 14,000+ in attendance each person will have at least 1 Wi-Fi connected device. Now let’s assume that a large chunk of those in attendance are like me and also have their laptop and a tablet with them, that’s a lot of connected devices to support! Whenever I talk with customers about wireless deployments the first thing I will say when we get to the point of turning on a network is that the client will cause the best wireless network to fail. We always push to make sure that the latest drivers are applied to the devices going to be used to ensure proper roaming and performance. But how do you manage that when you have no control over the devices being used? In the future we’ll use tools like Cisco NCS and ISE, for now we just hope it works!

Throughout the conference I was switching between my iPhone, iPad, and MacBook Pro all utilizing the wireless network, whether it be to connect with friends using the Cisco Live! event app (think Foursquare but just for attendees), downloading slides from ciscolivevirtual.com, or using FaceTime with the family. The wireless network allowed all of us to stay connected while roaming across 191 Cisco CleanAir APs with at times over 200 clients connected to a single AP! I’ll admit Monday was a little rough on the RF with some people experience data rate shifting but most of the issues that arose were from the backend services: DHCP, DNS, and some routing issues. To quote a common phrase amongst us in the wireless business on Twitter “It’s not the wireless!”

By the end of the conference you truly saw the power of the need for a wireless network to be pervasive and complete, the upcoming generations expect to be always connected and have access to the resources they find useful to complete a task at hand, after all this is “the human network” and the only way to achieve that is to provide a means for communicating.