This is a hard situation and I’ve been there. The CCIE is fickle... it really doesn’t mean an expert as what you are being tested on doesn’t represent any design principle today... it’s a gut check and nothing more.
I almost look at it like a military tough-guy school. It’s not so much about applying what the CCIE teaches you as much as it demonstrates that you have “overcome the shitshow” and that you can handle almost any project in terms of stress and workload (not content) through research and testing. You almost have to put blinders on and just focus on the borderline stupid structure that is the CCIE.
It’s really hard to say that your job would or would not help you on your journey but for most it’s the latter.
Keep cracking on INE, Cisco365 labs, etc... you’ll get there! Remember, as long as you don’t stop, it’s not a matter of “if” you get your CCIE as much as “when” you get it!
In the end, the CCIE doesn’t mean you are an expert, and being an expert doesn’t mean you you’ll get your CCIE. It’s a badge of “yeah I did it.” That’s all.
Thank you for the reassuring words. It helped me a lot just to get over the mental block that I have been dealing with lately.
If it makes you any better, I didn't get my digits until 10 years into the field.
You just have to put in the yards and the LABBING. You have to be able to clear the INE and C360 full labs with your eyes closed in 4 hours. Then you know you're ready. Also TSHOOT dear god that is what fails most people. Your troubleshooting methodology has to be SPOT ON with each technology - you should be able to find the problem via drilling down 3-4 show commands - there is no time to log in and stare at multiple show runs hoping to spot the error.
Speed speed speed. Get your speed up. Read the scenarios top to bottom before you start a single conf t. Then notepad that shit in one pass e.g. setting up OSPF, might as well turn on ip mpls as well and run up your LDP in a single pass. etc. Also learn the famous TCL troubleshooting script where you basically ping everything from everything, run that constantly to make sure you haven't messed anything up and catch it right away.
Plus second time round you'll know exactly whats coming... its like you paid 1500USD for an official dump :) The details may change but the basic scenario is going to be the same.
I would say I agree 99%. I say that because I see A LOT of job postings that require a CCIE regardless of what is in the job description. So yes, in one way having a set of numbers is as you put it a "yes, it did it" badge but it also opens up a lot of doors for people.
Routers, switches and firewalls. Network blogs, news and network management articles. Cisco, Juniper, Brocade and more all welcome.