Russ White, CCIE No. 2635, is a member of the Routing Protocol Design and Architecture Team at Cisco Systems. In this interview he presents valuable insights into CCDE Design Track Certification with OnNetworking.
Sunday, August 31, 2008
Friday, August 29, 2008
Quote of the Week - 08/29/08
"Nothing in this world can take the place of persistence. Talent will not; nothing is more common than unsuccessful people with talent. Genius will not; unrewarded genius is almost a proverb. Education will not; the world is full of educated derelicts. Persistence and determination alone are omnipotent. The slogan “Press On” has solved and always will solve the problems of the human race." - (John) Calvin Coolidge
This quote has been pretty important for me during my CCIE studies and in life in general. Persistence and determination will eventually conquer everything else. Keep fighting and moving forward.
This quote has been pretty important for me during my CCIE studies and in life in general. Persistence and determination will eventually conquer everything else. Keep fighting and moving forward.
Wednesday, August 27, 2008
CCIE Lab Advice
This was a past Lab Advice from someone attending a QA session with Bill Parkhurst a long time ago. I have updated it a little to be posted here, but most of it still holds true.
The #1 reason for failure is lack of knowledge.
- Study concepts. Do not try to memorize configurations or scenarios.
For example, understand how an OSPF DR is chosen. The lab proctors generally power cycle all of the equipment BEFORE grading. This could change your OSPF DR if you didn't configure the router you want to always be the DR properly.
- Practice each concept on its own. For example, practice OSPF WITHOUT also turning on BGP. This will ensure that any behaviors you see are attributed ONLY to OSPF and you don't confuse a behavior that was caused by BGP to be an OSPF behavior.
- Practice Labs should be used for self evaluation. Time yourself when using a practice lab to simulate the CCIE Lab Exam experience. Only use the practice lab 1 time.
The #2 reason for failure is anxiety.
- To reduce anxiety, travel to your lab location early the day before. Visit the CCIE lab facilities the day before if possible.
- Have confidence in your abilities. If you have been studying the technology and concepts, you are ready for ANY scenario. The core R&S concepts include Layer 2 switching, VLANs, IGPs, FR, and BGP.
- If you do get jammed up on a topic, try to drop it and come back to it, even if that means configuring a work around so you can move on. Let the solution come to you while thinking on other topics, or spend time at the end of the day on it, so you do not run out of time, and miss other topics because of it.
- If needed, take a break and go to the bathroom, or get a drink and a take a minute to relax. This may seem contradictory of having a time limit, but it will help clear you head to use the time you do have more effectively.
Practice good test taking skills.
- Skim the exam for the first 5 to 10 minutes once you get it.
- Spend a reasonable amount of time diagramming your network. This diagram will help you to understand things, as well as provide benefits throughout the rest of the exam.
- Use documentation or help commands to configure the remaining exam requirements that you are not familiar with LAST...remember this is a Pass or Fail exam. You only need 80 points. Not all 100 points.
- If you believe you have a hardware problem, do NOT spend more than 10 minutes trying to fix the hardware. Ask the lab proctor to investigate the issue. The lab proctor will stop the clock and send you away while he/she checks the hardware. If it is a hardware problem, the proctor will resolve and restart your clock. If it is NOT a hardware problem, you will at least KNOW it is not a hardware problem. On the other hand, if you have a hardware problem that you spend 90 minutes trying to resolve, you will not regain this time after you and the proctor finally replace the hardware.
- You are allowed to ask the proctor anything. But ask intelligent questions, as you need to convey to the proctor that you understand the material but just need clarification on the wording of the requirement. For example, if you are unsure of what a question is asking, ask the proctor something like this:
If I interpret this question this way......then I plan to do X. But If I interpret this question this other way......then I plan to do Y. Which way should I interpret it?
Miscellaneous:
- Lab exams are usually about 17 pages long.
- A new lab is written every month and an old lab is retired every month. There are more than 1 lab exams available to be given at any time. Each lab achieves roughly the same pass rate.
- The average person that passes the CCIE exam takes 2.5 lab attempts.
CCIE candidates can cancel a lab exam up to 28 days before their exam date WITHOUT being charged. Therefore, if you are willing to take an exam in 4 weeks, you can usually schedule it in 4 weeks. Otherwise, your lab exam will probably be 6 months out.
- Grading is done with an automated script. The script gives full credit for any question that works properly. If a particular question does not work properly, the lab proctor manually checks to validate whether or not the question was answered properly. Partial credit is not given. 5 point questions are rare. When they do occur, there is usually a modular piece to it so that 2 or 3 points can be earned without getting all 5 points
The #1 reason for failure is lack of knowledge.
- Study concepts. Do not try to memorize configurations or scenarios.
For example, understand how an OSPF DR is chosen. The lab proctors generally power cycle all of the equipment BEFORE grading. This could change your OSPF DR if you didn't configure the router you want to always be the DR properly.
- Practice each concept on its own. For example, practice OSPF WITHOUT also turning on BGP. This will ensure that any behaviors you see are attributed ONLY to OSPF and you don't confuse a behavior that was caused by BGP to be an OSPF behavior.
- Practice Labs should be used for self evaluation. Time yourself when using a practice lab to simulate the CCIE Lab Exam experience. Only use the practice lab 1 time.
The #2 reason for failure is anxiety.
- To reduce anxiety, travel to your lab location early the day before. Visit the CCIE lab facilities the day before if possible.
- Have confidence in your abilities. If you have been studying the technology and concepts, you are ready for ANY scenario. The core R&S concepts include Layer 2 switching, VLANs, IGPs, FR, and BGP.
- If you do get jammed up on a topic, try to drop it and come back to it, even if that means configuring a work around so you can move on. Let the solution come to you while thinking on other topics, or spend time at the end of the day on it, so you do not run out of time, and miss other topics because of it.
- If needed, take a break and go to the bathroom, or get a drink and a take a minute to relax. This may seem contradictory of having a time limit, but it will help clear you head to use the time you do have more effectively.
Practice good test taking skills.
- Skim the exam for the first 5 to 10 minutes once you get it.
- Spend a reasonable amount of time diagramming your network. This diagram will help you to understand things, as well as provide benefits throughout the rest of the exam.
- Use documentation or help commands to configure the remaining exam requirements that you are not familiar with LAST...remember this is a Pass or Fail exam. You only need 80 points. Not all 100 points.
- If you believe you have a hardware problem, do NOT spend more than 10 minutes trying to fix the hardware. Ask the lab proctor to investigate the issue. The lab proctor will stop the clock and send you away while he/she checks the hardware. If it is a hardware problem, the proctor will resolve and restart your clock. If it is NOT a hardware problem, you will at least KNOW it is not a hardware problem. On the other hand, if you have a hardware problem that you spend 90 minutes trying to resolve, you will not regain this time after you and the proctor finally replace the hardware.
- You are allowed to ask the proctor anything. But ask intelligent questions, as you need to convey to the proctor that you understand the material but just need clarification on the wording of the requirement. For example, if you are unsure of what a question is asking, ask the proctor something like this:
If I interpret this question this way......then I plan to do X. But If I interpret this question this other way......then I plan to do Y. Which way should I interpret it?
Miscellaneous:
- Lab exams are usually about 17 pages long.
- A new lab is written every month and an old lab is retired every month. There are more than 1 lab exams available to be given at any time. Each lab achieves roughly the same pass rate.
- The average person that passes the CCIE exam takes 2.5 lab attempts.
CCIE candidates can cancel a lab exam up to 28 days before their exam date WITHOUT being charged. Therefore, if you are willing to take an exam in 4 weeks, you can usually schedule it in 4 weeks. Otherwise, your lab exam will probably be 6 months out.
- Grading is done with an automated script. The script gives full credit for any question that works properly. If a particular question does not work properly, the lab proctor manually checks to validate whether or not the question was answered properly. Partial credit is not given. 5 point questions are rare. When they do occur, there is usually a modular piece to it so that 2 or 3 points can be earned without getting all 5 points
Configure router as Frame-Relay Switch
I call this the obligatory Router acting as a Frame-Relay Switch post.
You will find that a lot of blogs or websites post information on configuring a router to act as a frame-relay switch. The reason for this is that is a great way to simulate frame-relay in a lab and is very important in order to work on frame-relay and how it effects various other protocols and technologies. Instead of providing yet another example of how to accomplish this, this post is to provide a link to some of those examples out there.
I personally always had an old 4500 Router with 2 4 port serial cards acting as my frame-relay switch. It served dual duty as the frame switch and one of my backbone router via an ethernet interface. As you will see though, a very cost effective with is with 2500 series routers.
Link - InternetworkExpert's examples on 2501 and 2520 series routers
Link - Example posted on CCIEtalk
Link - Example for 2520 from Chris Bryant CCIE #12933
Link - Another good example from Kyle Lutz on Tech Exams
A simple search will provide even more examples.
You will find that a lot of blogs or websites post information on configuring a router to act as a frame-relay switch. The reason for this is that is a great way to simulate frame-relay in a lab and is very important in order to work on frame-relay and how it effects various other protocols and technologies. Instead of providing yet another example of how to accomplish this, this post is to provide a link to some of those examples out there.
I personally always had an old 4500 Router with 2 4 port serial cards acting as my frame-relay switch. It served dual duty as the frame switch and one of my backbone router via an ethernet interface. As you will see though, a very cost effective with is with 2500 series routers.
Link - InternetworkExpert's examples on 2501 and 2520 series routers
Link - Example posted on CCIEtalk
Link - Example for 2520 from Chris Bryant CCIE #12933
Link - Another good example from Kyle Lutz on Tech Exams
A simple search will provide even more examples.
Tuesday, August 26, 2008
Global Power in CCIE numbers?
An interesting article for those CCIEs out there or those striving towards the numbered goal.
http://www.pbs.org/cringely/pulpit/2008/pulpit_20080822_005393.html
It discusses the number of CCIEs compared to population and gross domestic product to gauge a countries networking investments.
Also interesting to note, from the article, is that 50% of CCIEs work for Cisco.
http://www.pbs.org/cringely/pulpit/2008/pulpit_20080822_005393.html
It discusses the number of CCIEs compared to population and gross domestic product to gauge a countries networking investments.
Also interesting to note, from the article, is that 50% of CCIEs work for Cisco.
Monday, August 25, 2008
Quick Lists - IOS Version Information
A Quick List on IOS Version information brought to you by Packet Life.
Packet Life Cheat Sheets
Packet Life Cheat Sheets
http://packetlife.net/cheatsheets/
Download all Packet Life Cheat Sheets
http://packetlife.net/static/cheatsheets/cheatsheets.zip
Download all Packet Life Cheat Sheets
http://packetlife.net/static/cheatsheets/cheatsheets.zip
Sunday, August 24, 2008
About the Blogger
A little about myself and my history. You can use the links for the quick version.
LinkedIn Profile
Facebook Profile
CCIE Verification Link (CCO Required)
I have over ten years of experience in designing, implementing, analyzing, troubleshooting, and documenting complex data communication networks. My expertise is in routing, switching, and security with main focus on the dominant player in the networking industry, Cisco. Some assumption is made that you know about Cisco, if you have found yourself here at this blog.
I started in data networks when I joined the United States Marine Corps in May of 1998. I worked on many different networks of various sizes, complexity, funding and certainly locations that many have not. We built custom data networking portables, that were self contained networking pods with room for techs and engineers on the inside that could be transported and dropped off anywhere. This was even before the General Dynamics Tactical Data Networks pods were developed.
Upon leaving the USMC, I transitioned to Wam!Net, a subcontractor to EDS on the NMCI (Navy Marine Corps Intranet). It was a natural transition for me, but ultimately proved to be a place I would have to leave to continue my growth as a Network Engineer. They have since become a part of the Harris Corporation with a few other names along the way.
I left Wam!Net to go out on my own. During this period I contracted to individual companies and eventually found myself contracting through Modis IT to Disney working on their networks supporting Disneyland and Disney's California Adventure. It was an interesting experience to work on network equipment in a small closet on the back end of a dinosaur shaped sunglass hut.
I spent some time after this working directly for Riverside County IT in Riverside, CA. The change was welcomed at the time for more steady work away from contracting. This was an interesting position as I worked on DMVPN for the county in some of it's early forms. I also worked with the Riverside County fire department to build an in house alerting and reporting system working over the network.
After RCIT, I spent a couple years at Kaiser Permanente at the data center in Corona, CA. I did a lot of work on data center equipment, mostly 10GB and 1GB ethernet connections for high volume traffic like medical imaging and document retrieval. I designed and built out the network expansion into the LA Data Center, which has now migrated to Irvine. It was during this time that my main study for the CCIE Routing and Switching track kicked into high gear with the help of my study partner, David Vasek CCIE #16333.
My family and I relocated to the area where I grew up in late 2006. I began working for Fiserv EFT in Portland, OR. Our division of Fiserv processes debit and credit transactions. Next time you are at the ATM, you can think of this blog. Anything and everything in networking, we do in some fashion. This is an exciting time of growth after Fiserv's acquisition of CheckFree.
As for current study I am working on CCIE Security track, and putting some effort towards the CCDE blueprint. Check out the profiles for more information, and feel free to add me as a contact.
LinkedIn Profile
Facebook Profile
CCIE Verification Link (CCO Required)
I have over ten years of experience in designing, implementing, analyzing, troubleshooting, and documenting complex data communication networks. My expertise is in routing, switching, and security with main focus on the dominant player in the networking industry, Cisco. Some assumption is made that you know about Cisco, if you have found yourself here at this blog.
I started in data networks when I joined the United States Marine Corps in May of 1998. I worked on many different networks of various sizes, complexity, funding and certainly locations that many have not. We built custom data networking portables, that were self contained networking pods with room for techs and engineers on the inside that could be transported and dropped off anywhere. This was even before the General Dynamics Tactical Data Networks pods were developed.
Upon leaving the USMC, I transitioned to Wam!Net, a subcontractor to EDS on the NMCI (Navy Marine Corps Intranet). It was a natural transition for me, but ultimately proved to be a place I would have to leave to continue my growth as a Network Engineer. They have since become a part of the Harris Corporation with a few other names along the way.
I left Wam!Net to go out on my own. During this period I contracted to individual companies and eventually found myself contracting through Modis IT to Disney working on their networks supporting Disneyland and Disney's California Adventure. It was an interesting experience to work on network equipment in a small closet on the back end of a dinosaur shaped sunglass hut.
I spent some time after this working directly for Riverside County IT in Riverside, CA. The change was welcomed at the time for more steady work away from contracting. This was an interesting position as I worked on DMVPN for the county in some of it's early forms. I also worked with the Riverside County fire department to build an in house alerting and reporting system working over the network.
After RCIT, I spent a couple years at Kaiser Permanente at the data center in Corona, CA. I did a lot of work on data center equipment, mostly 10GB and 1GB ethernet connections for high volume traffic like medical imaging and document retrieval. I designed and built out the network expansion into the LA Data Center, which has now migrated to Irvine. It was during this time that my main study for the CCIE Routing and Switching track kicked into high gear with the help of my study partner, David Vasek CCIE #16333.
My family and I relocated to the area where I grew up in late 2006. I began working for Fiserv EFT in Portland, OR. Our division of Fiserv processes debit and credit transactions. Next time you are at the ATM, you can think of this blog. Anything and everything in networking, we do in some fashion. This is an exciting time of growth after Fiserv's acquisition of CheckFree.As for current study I am working on CCIE Security track, and putting some effort towards the CCDE blueprint. Check out the profiles for more information, and feel free to add me as a contact.
Blog Opening
Welcome to the Blog. This Blog will focus on computer networking focusing on routing, switching, and security. The Blog will generally have a Cisco Systems focus similar to the current industry, but will cover industry aspects and other vendors as well. The Blog will build off of public information and consolidate some of the great resources and tools that have been created and published over the years.
The initial posts will introduce myself and give readers some background about me and my experience. Technical posts will follow after that. Right now I have no goal as to how often they will happen, but smaller updates and quick links and resources will be published in between.
The initial posts will introduce myself and give readers some background about me and my experience. Technical posts will follow after that. Right now I have no goal as to how often they will happen, but smaller updates and quick links and resources will be published in between.
Subscribe to:
Posts (Atom)