Re: CCIE #6460
Aaron, Excellent job! I was curious about how much experience you had prior to the Lab. Some people in this group have very little experience, and others have 8-10 years experience prior to beginning CCIE track. Could you clue me in? Also, could you give the exact titles of those other three books that you mention. I read many scary Lab stories, then one inspiring one like yours makes me think "it could happen!". Tim - Original Message - From: "Aaron K. Dixon" [EMAIL PROTECTED] To: "GroupStudy LAB" [EMAIL PROTECTED]; "GroupStudy" [EMAIL PROTECTED] Sent: Sunday, November 26, 2000 10:32 AM Subject: CCIE #6460 Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes later, the proctor returned with a yellow sticky note with my number on it. He then asked me if I would erase all of my configs and then I left with a huge grin on my face. I just couldn't believe that all of my studying paid off. I met Chuck Larrieu a few hours later for a victory dinner. I knew that it would be nice to have some company one way or the other and I was glad that it turned out to be for good reasons. Passing the test was very rewarding, but the journey was just as rewarding. It's amazing the amount of material that you learn along the way and the many friends that you make. I have become friends with many people that I may of never met if I wasn't studying for the CCIE. Study Materials I studied the normal books Caslow, Halabi, and Doyle and found them all to be very helpful. I also used three other books extensively that I don't see mentioned very often. I used the configuring cisco routers for bridging, dlsw+, desktop protocols and the Cisco Press Lan Switching Book. I found them both to be very helpful as I work extensively with cisco routers and rarely use cisco switches. I also used the CCIEBootcamp labs which I found to be an excellent resource for practice. There are a lot of other labs, but most of them don't throw everything together like the bootcamp labs. I have to admit that I only completed about half of them and never did the dreaded lab 8, but I studied all 17 of them and read up o
Re: CCIE #6460
-Original Message- From: Tim Ross [EMAIL PROTECTED] To: Aaron K. Dixon [EMAIL PROTECTED]; GroupStudy LAB [EMAIL PROTECTED]; GroupStudy [EMAIL PROTECTED] Date: Wednesday, November 29, 2000 9:11 AM Subject: Re: CCIE #6460 Aaron, Excellent job! I was curious about how much experience you had prior to the Lab. Some people in this group have very little experience, and others have 8-10 years experience prior to beginning CCIE track. Could you clue me in? Also, could you give the exact titles of those other three books that you mention. I read many scary Lab stories, then one inspiring one like yours makes me think "it could happen!". Tim - Original Message - From: "Aaron K. Dixon" [EMAIL PROTECTED] To: "GroupStudy LAB" [EMAIL PROTECTED]; "GroupStudy" [EMAIL PROTECTED] Sent: Sunday, November 26, 2000 10:32 AM Subject: CCIE #6460 Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes later, the proctor returned with a yellow sticky note with my number on it. He then asked me if I would erase all of my configs and then I left with a huge grin on my face. I just couldn't believe that all of my studying paid off. I met Chuck Larrieu a few hours later for a victory dinner. I knew that it would be nice to have some company one way or the other and I was glad that it turned out to be for good reasons. Passing the test was very rewarding, but the journey was just as rewarding. It's amazing the amount of material that you learn along the way and the many friends that you make. I have become friends with many people that I may of never met if I wasn't studying for the CCIE. Study Materials I studied the normal books Caslow, Halabi, and Doyle and found them all to be very helpful. I also used three other books extensively that I don't see mentioned very often. I used the configuring cisco routers for bridging, dlsw+, desktop protocols and the Cisco Press Lan Switching Book. I found them both to be very helpful as I work extensively with cisco routers and rarely use cisco switches. I also used the CCIEBootcamp labs which I found to be an excellent resource for practice. There ar
Re: CCIE #6460
Dear Aaron, Good job !!! I hope I will join you in the next semester ! Regards Elias Aggelidis CCNP+Voice - Original Message - From: "Jonathan Hays" [EMAIL PROTECTED] To: "Aaron K. Dixon" [EMAIL PROTECTED] Cc: "GroupStudy LAB" [EMAIL PROTECTED]; "GroupStudy" [EMAIL PROTECTED] Sent: Monday, November 27, 2000 6:33 PM Subject: Re: CCIE #6460 Very informative and articulate post, Aaron. Thank you. -Jonathan "Aaron K. Dixon" wrote: Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes later, the proctor returned with a yellow sticky note with my number on it. He then asked me if I would erase all of my configs and then I left with a huge grin on my face. I just couldn't believe that all of my studying paid off. I met Chuck Larrieu a few hours later for a victory dinner. I knew that it would be nice to have some company one way or the other and I was glad that it turned out to be for good reasons. Passing the test was very rewarding, but the journey was just as rewarding. It's amazing the amount of material that you learn along the way and the many friends that you make. I have become friends with many people that I may of never met if I wasn't studying for the CCIE. Study Materials I studied the normal books Caslow, Halabi, and Doyle and found them all to be very helpful. I also used three other books extensively that I don't see mentioned very often. I used the configuring cisco routers for bridging, dlsw+, desktop protocols and the Cisco Press Lan Switching Book. I found them both to be very helpful as I work extensively with cisco routers and rarely use cisco switches. I also used the CCIEBootcamp labs which I found to be an excellent resource for practice. There are a lot of other labs, but most of them don't throw everything together like the bootcamp labs. I have to admit that I only completed about half of them and never did the dreaded lab 8, but I studied all 17 of them and read up on anything that I didn't know how to do. It often takes a large amou
RE: CCIE #6460
CONGRATULATIONS WAY TO GO!!! I should add that I have had the pleasure of meeting Aaron twice now - once at Networkers in Florida, and again last Thursday. Aaron is a gentleman in the true sense of the work, very helpful, very informative, and quite an expert in a number of arcane routing issues. He deals in network complexity in depth in his job. It should be no surprise that he found the Lab "easy". The man knows his stuff inside out Hope you and the family are having some fun now, Aaron. Deserve it, man! Chuck -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Aaron K. Dixon Sent: Sunday, November 26, 2000 10:33 AM To: GroupStudy LAB; GroupStudy Subject: CCIE #6460 Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes later, the proctor returned with a yellow sticky note with my number on it. He then asked me if I would erase all of my configs and then I left with a huge grin on my face. I just couldn't believe that all of my studying paid off. I met Chuck Larrieu a few hours later for a victory dinner. I knew that it would be nice to have some company one way or the other and I was glad that it turned out to be for good reasons. Passing the test was very rewarding, but the journey was just as rewarding. It's amazing the amount of material that you learn along the way and the many friends that you make. I have become friends with many people that I may of never met if I wasn't studying for the CCIE. Study Materials I studied the normal books Caslow, Halabi, and Doyle and found them all to be very helpful. I also used three other books extensively that I don't see mentioned very often. I used the configuring cisco routers for bridging, dlsw+, desktop protocols and the Cisco Press Lan Switching Book. I found them both to be very helpful as I work extensively with cisco routers and rarely use cisco switches. I also used the CCIEBootcamp labs which I found to be an excellent resource for practice. There are a lot of other labs, but most of them don't throw everything together like the bootcamp labs. I have to admit that I only completed about half of them and never did the dreaded la
Re: Congrats...! CCIE #6460
Congratulations Aaron! First I want to thank you for your insightful explanation of the training habits that compelled you to achieve your well-deserved CCIE certification. I also want to thank everyone else on this list that has taken the time to help others to understand all of the difficult concepts and protocols involved in networking and Paul for keeping up this list so well. I think others on the list on the seemingly endless pursuit of CCIE certification will agree that the information you provided in your synopsis was not only perceptive but also very helpful (not boring as you stated). It also gave me encouragement and a thought like there is a light at the end of the tunnel, that with hard work and determination any goal is possible. I also agree with Nigel below about the common characteristics of first attempt CCIE's "effective studying, focus, and a strong desire to succeed". In the words of Albert Einstein "In the middle of difficulty lies opportunity." Jeff Lodwick MCSE, CCNP (soon to be CCIE) From: "Nigel Taylor" [EMAIL PROTECTED] Reply-To: "Nigel Taylor" [EMAIL PROTECTED] To: "Aaron K. Dixon" [EMAIL PROTECTED],"GroupStudy LAB" [EMAIL PROTECTED], "GroupStudy" [EMAIL PROTECTED] Subject: Congrats...! CCIE #6460 Date: Mon, 27 Nov 2000 03:50:09 - Many Congratulations Aaron for your well deserved success. As I look forward to the lab it enlightens me to no end knowing that it can be done on the first try as so many of our list members have proven. The common characteristics were effective studying, focus, and a strong desire to succed. As for your synopsis, let me say that it will join the existing (CCIEAdvice.txt - thanks to Chuck L)document as rules to live by on my way up Mount E. Thanks again... Nigel. - Original Message - From: Aaron K. Dixon [EMAIL PROTECTED] To: GroupStudy LAB [EMAIL PROTECTED]; GroupStudy [EMAIL PROTECTED] Sent: Sunday, November 26, 2000 6:32 PM Subject: CCIE #6460 Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes
CCIE #6460
Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes later, the proctor returned with a yellow sticky note with my number on it. He then asked me if I would erase all of my configs and then I left with a huge grin on my face. I just couldn't believe that all of my studying paid off. I met Chuck Larrieu a few hours later for a victory dinner. I knew that it would be nice to have some company one way or the other and I was glad that it turned out to be for good reasons. Passing the test was very rewarding, but the journey was just as rewarding. It's amazing the amount of material that you learn along the way and the many friends that you make. I have become friends with many people that I may of never met if I wasn't studying for the CCIE. Study Materials I studied the normal books Caslow, Halabi, and Doyle and found them all to be very helpful. I also used three other books extensively that I don't see mentioned very often. I used the configuring cisco routers for bridging, dlsw+, desktop protocols and the Cisco Press Lan Switching Book. I found them both to be very helpful as I work extensively with cisco routers and rarely use cisco switches. I also used the CCIEBootcamp labs which I found to be an excellent resource for practice. There are a lot of other labs, but most of them don't throw everything together like the bootcamp labs. I have to admit that I only completed about half of them and never did the dreaded lab 8, but I studied all 17 of them and read up on anything that I didn't know how to do. It often takes a large amount of time to do a full lab, but reading through it and "spotting the issues" can be very helpful. About 2 months ago I attended the ECP1 course which was taught by Bruce Caslow. I found Bruce's methodology to be excellent and really got a lot out of the course. About a month after that I attended Cisco's ASET (www.cisco.com/go/aset) program. This turned out to be an excellent program as well and I just wished that I would of known about it sooner. This is a 3-day lab taught by Jay and Jose in San Jose. The lab is a simulated CCIE environment where each student gets a pod with 8 routers, a cat 3920, cat 5000, and a ls 1010. Jay and Jose really
Congrats...! CCIE #6460
Many Congratulations Aaron for your well deserved success. As I look forward to the lab it enlightens me to no end knowing that it can be done on the first try as so many of our list members have proven. The common characteristics were effective studying, focus, and a strong desire to succed. As for your synopsis, let me say that it will join the existing (CCIEAdvice.txt - thanks to Chuck L)document as rules to live by on my way up Mount E. Thanks again... Nigel. - Original Message - From: Aaron K. Dixon [EMAIL PROTECTED] To: GroupStudy LAB [EMAIL PROTECTED]; GroupStudy [EMAIL PROTECTED] Sent: Sunday, November 26, 2000 6:32 PM Subject: CCIE #6460 Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes later, the proctor returned with a yellow sticky note with my number on it. He then asked me if I would erase all of my configs and then I left with a huge grin on my face. I just couldn't believe that all of my studying paid off. I met Chuck Larrieu a few hours later for a victory dinner. I knew that it would be nice to have some company one way or the other and I was glad that it turned out to be for good reasons. Passing the test was very rewarding, but the journey was just as rewarding. It's amazing the amount of material that you learn along the way and the many friends that you make. I have become friends with many people that I may of never met if I wasn't studying for the CCIE. Study Materials I studied the normal books Caslow, Halabi, and Doyle and found them all to be very helpful. I also used three other books extensively that I don't see mentioned very often. I used the configuring cisco routers for bridging, dlsw+, desktop protocols and the Cisco Press Lan Switching Book. I found them both to be very helpful as I work extensively with cisco routers and rarely use cisco switches. I also used the CCIEBootcamp labs which I found to be an excellent resource for practice. There are a lot of other labs, but most of them don't throw everything together like the bootcamp labs. I have to admit that I only completed about half of them and never did the dreaded lab 8, but I studied all 17 of them and read up
Re: CCIE #6460
hm... 3:36 A.M. - newfound free time? Sincere congrats for making it to the top! Thank-you for putting a great "you can do it if you prepare" face on the lab. Lots of urban myths out there about the "experience" in general but your no nonsense, very clear and understandable account goes a long way to quieting the apprehension I think many of us have about the "lab". Hopefully I'll get there before the numbers get to CCIE#1! thanks again, Kevin Wigle - Original Message - From: "Aaron K. Dixon" [EMAIL PROTECTED] To: "GroupStudy LAB" [EMAIL PROTECTED]; "GroupStudy" [EMAIL PROTECTED] Sent: Sunday, November 26, 2000 1:32 PM Subject: CCIE #6460 Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. snip _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: CCIE #6460
Congrats man! Glad to see hard work paying off. Couple questions about other people that you were at the lab with. You said you were the only person to return. How many people started the lab, and how many people didn't even make it to day 2? Are you sitting right next to people that are also taking the lab? thanx. Rishard ""Aaron K. Dixon"" [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes later, the proctor returned with a yellow sticky note with my number on it. He then asked me if I would erase all of my configs and then I left with a huge grin on my face. I just couldn't believe that all of my studying paid off. I met Chuck Larrieu a few hours later for a victory dinner. I knew that it would be nice to have some company one way or the other and I was glad that it turned out to be for good reasons. Passing the test was very rewarding, but the journey was just as rewarding. It's amazing the amount of material that you learn along the way and the many friends that you make. I have become friends with many people that I may of never met if I wasn't studying for the CCIE. Study Materials I studied the normal books Caslow, Halabi, and Doyle and found them all to be very helpful. I also used three other books extensively that I don't see mentioned very often. I used the configuring cisco routers for bridging, dlsw+, desktop protocols and the Cisco Press Lan Switching Book. I found them both to be very helpful as I work extensively with cisco routers and rarely use cisco switches. I also used the CCIEBootcamp labs which I found to be an excellent resource for practice. There are a lot of other labs, but most of them don't throw everything together like the bootcamp labs. I have to admit that I only completed about half of them and never did the dreaded lab 8, but I studied all 17 of them and read up on anything that I didn't know how to do. It often takes a large amount of time to do a full lab, but reading through it and "spotting the issues" can be very helpful. About 2 months ago I attended the ECP1 course which was taught by
Re: CCIE #6460
Very informative and articulate post, Aaron. Thank you. -Jonathan "Aaron K. Dixon" wrote: Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes later, the proctor returned with a yellow sticky note with my number on it. He then asked me if I would erase all of my configs and then I left with a huge grin on my face. I just couldn't believe that all of my studying paid off. I met Chuck Larrieu a few hours later for a victory dinner. I knew that it would be nice to have some company one way or the other and I was glad that it turned out to be for good reasons. Passing the test was very rewarding, but the journey was just as rewarding. It's amazing the amount of material that you learn along the way and the many friends that you make. I have become friends with many people that I may of never met if I wasn't studying for the CCIE. Study Materials I studied the normal books Caslow, Halabi, and Doyle and found them all to be very helpful. I also used three other books extensively that I don't see mentioned very often. I used the configuring cisco routers for bridging, dlsw+, desktop protocols and the Cisco Press Lan Switching Book. I found them both to be very helpful as I work extensively with cisco routers and rarely use cisco switches. I also used the CCIEBootcamp labs which I found to be an excellent resource for practice. There are a lot of other labs, but most of them don't throw everything together like the bootcamp labs. I have to admit that I only completed about half of them and never did the dreaded lab 8, but I studied all 17 of them and read up on anything that I didn't know how to do. It often takes a large amount of time to do a full lab, but reading through it and "spotting the issues" can be very helpful. About 2 months ago I attended the ECP1 course which was taught by Bruce Caslow. I found Bruce's methodology to be excellent and really got a lot out of the course. About a month after that I attended Cisco's ASET (www.cisco.com/go/aset) program. This turned out to be an excellent program as well and I just wished that I would of known about it sooner. This is a 3-day lab taught by
RE: CCIE #6460
I didn't have anyone sitting next to me, but there was a seat. I believe there are 6 rows for the RS and each row is divided into 2. In San Jose they test 6 people at a time. When I showed up for day one there were 6 people for day 1 and 6 returning for day 2. Out of the day 2 group I believe 2 or 3 made it to day 2 and I don't recall seeing any of them in the afternoon. From my group of 6 there were 3 that made it to day 2 and I was the only one to progress to troubleshooting. Regards, Aaron K. Dixon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rishard Chapoteau Sent: Monday, November 27, 2000 8:22 AM To: [EMAIL PROTECTED] Subject: Re: CCIE #6460 Congrats man! Glad to see hard work paying off. Couple questions about other people that you were at the lab with. You said you were the only person to return. How many people started the lab, and how many people didn't even make it to day 2? Are you sitting right next to people that are also taking the lab? thanx. Rishard ""Aaron K. Dixon"" [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes later, the proctor returned with a yellow sticky note with my number on it. He then asked me if I would erase all of my configs and then I left with a huge grin on my face. I just couldn't believe that all of my studying paid off. I met Chuck Larrieu a few hours later for a victory dinner. I knew that it would be nice to have some company one way or the other and I was glad that it turned out to be for good reasons. Passing the test was very rewarding, but the journey was just as rewarding. It's amazing the amount of material that you learn along the way and the many friends that you make. I have become friends with many people that I may of never met if I wasn't studying for the CCIE. Study Materials I studied the normal books Caslow, Halabi, and Doyle and found them all to be very helpful. I also used three other books extensively that I don't see mentioned very often. I used the configuring cisco routers for bridging
Re: CCIE #6460
Well done Aaron. I hope this opens some nice doors for you. From: "Aaron K. Dixon" [EMAIL PROTECTED] Reply-To: "Aaron K. Dixon" [EMAIL PROTECTED] To: "GroupStudy LAB" [EMAIL PROTECTED],"GroupStudy" [EMAIL PROTECTED] Subject: CCIE #6460 Date: Sun, 26 Nov 2000 12:32:58 -0600 Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes later, the proctor returned with a yellow sticky note with my number on it. He then asked me if I would erase all of my configs and then I left with a huge grin on my face. I just couldn't believe that all of my studying paid off. I met Chuck Larrieu a few hours later for a victory dinner. I knew that it would be nice to have some company one way or the other and I was glad that it turned out to be for good reasons. Passing the test was very rewarding, but the journey was just as rewarding. It's amazing the amount of material that you learn along the way and the many friends that you make. I have become friends with many people that I may of never met if I wasn't studying for the CCIE. Study Materials I studied the normal books Caslow, Halabi, and Doyle and found them all to be very helpful. I also used three other books extensively that I don't see mentioned very often. I used the configuring cisco routers for bridging, dlsw+, desktop protocols and the Cisco Press Lan Switching Book. I found them both to be very helpful as I work extensively with cisco routers and rarely use cisco switches. I also used the CCIEBootcamp labs which I found to be an excellent resource for practice. There are a lot of other labs, but most of them don't throw everything together like the bootcamp labs. I have to admit that I only completed about half of them and never did the dreaded lab 8, but I studied all 17 of them and read up on anything that I didn't know how to do. It often takes a large amount of time to do a full lab, but reading through it and "spotting the issues" can be very helpful. About 2 months ago I attended the ECP1 course which was taught by Bruce Caslow. I found Bruce's methodology to be excellent and really got a lot out of the course. About a month after that I attended Cisco's ASET
RE: CCIE #6460
Hello Aaron, First, a million congratulations to you - it sounds like you did a really good job on the lab. Second, a million thanks to you for your "story" which I found anything but boring. Even though I am only halfway on my expedition towards the CCNP certification, I have often wondered what actually went on behind the closed doors at the CCIE labs, and you have now blown away 90% of the dark clouds. How long did it take you to become a CCIE after you got your CCNP cert? Thanks and enjoy your free time, Ole Ole Drews Jensen Systems Network Manager CCNA, MCSE, MCP+I RWR Enterprises, Inc. [EMAIL PROTECTED] http://www.oledrews.com/ccnp NEED A JOB ??? http://www.oledrews.com/job -Original Message- From: Aaron K. Dixon [mailto:[EMAIL PROTECTED]] Sent: Sunday, November 26, 2000 12:33 PM To: GroupStudy LAB; GroupStudy Subject: CCIE #6460 Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes later, the proctor returned with a yellow sticky note with my number on it. He then asked me if I would erase all of my configs and then I left with a huge grin on my face. I just couldn't believe that all of my studying paid off. I met Chuck Larrieu a few hours later for a victory dinner. I knew that it would be nice to have some company one way or the other and I was glad that it turned out to be for good reasons. Passing the test was very rewarding, but the journey was just as rewarding. It's amazing the amount of material that you learn along the way and the many friends that you make. I have become friends with many people that I may of never met if I wasn't studying for the CCIE. Study Materials I studied the normal books Caslow, Halabi, and Doyle and found them all to be very helpful. I also used three other books extensively that I don't see mentioned very often. I used the configuring cisco routers for bridging, dlsw+, desktop protocols and the Cisco Press Lan Switching Book. I found them both to be very helpful as I work extensively with cisco routers and rarely use cisco switches. I also used the CCIEBootcamp labs which I found to be an
Re: CCIE #6460
Aaron, Well done and thanks for your report. This is the sort of stuff I am looking for. Tony van Ree (Teunis) On Sunday, November 26, 2000 at 12:32:58 PM, Aaron K. Dixon wrote: Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes later, the proctor returned with a yellow sticky note with my number on it. He then asked me if I would erase all of my configs and then I left with a huge grin on my face. I just couldn't believe that all of my studying paid off. I met Chuck Larrieu a few hours later for a victory dinner. I knew that it would be nice to have some company one way or the other and I was glad that it turned out to be for good reasons. Passing the test was very rewarding, but the journey was just as rewarding. It's amazing the amount of material that you learn along the way and the many friends that you make. I have become friends with many people that I may of never met if I wasn't studying for the CCIE. Study Materials I studied the normal books Caslow, Halabi, and Doyle and found them all to be very helpful. I also used three other books extensively that I don't see mentioned very often. I used the configuring cisco routers for bridging, dlsw+, desktop protocols and the Cisco Press Lan Switching Book. I found them both to be very helpful as I work extensively with cisco routers and rarely use cisco switches. I also used the CCIEBootcamp labs which I found to be an excellent resource for practice. There are a lot of other labs, but most of them don't throw everything together like the bootcamp labs. I have to admit that I only completed about half of them and never did the dreaded lab 8, but I studied all 17 of them and read up on anything that I didn't know how to do. It often takes a large amount of time to do a full lab, but reading through it and "spotting the issues" can be very helpful. About 2 months ago I attended the ECP1 course which was taught by Bruce Caslow. I found Bruce's methodology to be excellent and really got a lot out of the course. About a month after that I attended Cisco's ASET (www.cisco.com/go/aset) program. This turned out to be an excellent program as well
Re: CCIE #6460
congrats!! it must be very exciting, eh? in fact, thanks for taking time to share your experience, i really wish i would do the same sometime next year... :) ""Aaron K. Dixon"" [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... Hello all, This is a brief synopsis of my ccie lab and the tools I used to study. If you're not interested you may want to just hit the delete key now. I just thought that I would take a few moments to share my study methodology for the CCIE lab. I've been meaning to do this since I passed the lab on November 15th in San Jose, but I always seem to get sidetracked with all of my newfound free time. This was my first attempt at the lab and I found it to be fairly straight forward. It wasn't as convoluted as I expected and I had seen pretty much everything before. Day 1 The first thing that I did was read through the entire lab TWICE. I realized that I knew how to do everything and went to work on my diagram. I found day one to be very easy and was done by 2 o'clock. I checked and re-checked all of my work and felt very confident in everything that I had done. After that I spent time making sure that ALL of my information was recorded correctly and neatly on my diagram. I felt very confident when I left, but I have to admit as I tried to get some sleep the what if's were creeping in my mind. Day 2 I arrived for Day 2 happy to see the Day 2 binder on my desk and went through the same process of reading the entire lab twice. I realized that I knew exactly what to do on 90% of the lab and may have to browse the cd for the other 10%. Again, I found that there was plenty of time and I had completed everything that I knew how to do by 10:30. I spent the next 30 minutes reviewing the cd and configuring the remaining 10%. I then re-read everything and checked over all of my work and made sure that my diagram was complete. Documentation is very important in the lab not only for troubleshooting, but to ensure that the proctor can see what you were doing. The proctor spends all day at the lab and then has to check your work in the evening or at lunch for day 2. The last thing he wants to do is spend 30 minutes trying to read your diagram. Of course, this is just my opinion. After day 2, I felt real good about my work, but nervous none the less. This made for what seemed like a never ending lunch. Once we arrived back at the facility I was called first and on the way back to the lab I was told that I had made it to troubleshooting and that I had three hours. When I returned to my desk I found the paperwork for troubleshooting and for the first time found out how many points I had. I had gained 70 of the 75 points and only needed 10 of the 25 from troubleshooting. At that point, I knew that I had passed and just needed to knock out the troubleshooting. As I looked around I realized that no one else had progressed from Day 2. I spent about an hour and a half on troubleshooting and felt like I fixed everything so I turned in my sheet. About 5 minutes later, the proctor returned with a yellow sticky note with my number on it. He then asked me if I would erase all of my configs and then I left with a huge grin on my face. I just couldn't believe that all of my studying paid off. I met Chuck Larrieu a few hours later for a victory dinner. I knew that it would be nice to have some company one way or the other and I was glad that it turned out to be for good reasons. Passing the test was very rewarding, but the journey was just as rewarding. It's amazing the amount of material that you learn along the way and the many friends that you make. I have become friends with many people that I may of never met if I wasn't studying for the CCIE. Study Materials I studied the normal books Caslow, Halabi, and Doyle and found them all to be very helpful. I also used three other books extensively that I don't see mentioned very often. I used the configuring cisco routers for bridging, dlsw+, desktop protocols and the Cisco Press Lan Switching Book. I found them both to be very helpful as I work extensively with cisco routers and rarely use cisco switches. I also used the CCIEBootcamp labs which I found to be an excellent resource for practice. There are a lot of other labs, but most of them don't throw everything together like the bootcamp labs. I have to admit that I only completed about half of them and never did the dreaded lab 8, but I studied all 17 of them and read up on anything that I didn't know how to do. It often takes a large amount of time to do a full lab, but reading through it and "spotting the issues" can be very helpful. About 2 months ago I attended the ECP1 course which was taught by Bruce Caslow. I found Bruce's methodology to be excellent and really got a lot out of the course. About a month after that I attended Cisco's ASET
Re: CCIE #6460
AWESOME! Congrats! Just curious... what's after a CCIE? Are there other networking certifications that are more valued or more difficult to attain? _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
