Congrats!!! Regards,
Wayne A. Lawson II - CCIE #5244 Founder & President - IPexpert Mailto: wlaw...@ipexpert.com Telephone: +1.810.326.1444, ext. 101 Live Assistance, Please visit: www.ipexpert.com/chat eFax: +1.810.454.0130 ::Message sent from iPhone:: IPexpert is a premier provider of Classroom and Self-Study Cisco CCNA (R&S, Voice & Security), CCNP, CCVP, CCSP and CCIE (R&S, Voice, Security & Service Provider) Certification Training with locations throughout the United States, Europe and Australia. Be sure to check out our online communities at www.ipexpert.com/communities and our public website at www.ipexpert.com. On Jan 15, 2010, at 1:31 PM, Jeff Knuckle <jknuc...@nationwidelab.com> wrote: > Congrats Jason!!!! excellent recap...... I will go ahead and > reschedule my lab for a Tuesday :-) > > > Jeff > > > -----Original Message----- > From: ccie_voice-boun...@onlinestudylist.com [mailto:ccie_voice- > boun...@onlinestudylist.com] On Behalf Of Jason L. Hawkins > Sent: Friday, January 15, 2010 12:19 PM > To: ccie_voice@onlinestudylist.com > Subject: [OSL | CCIE_Voice] Third times a charm and Strategy CCIE > Voice 25842 > > Finally got my CCIE in Voice #25842. I'd like to thank Vik and > IPExpert for all the help they've given me. Vik is an excellent > instructor and IPExpert is a great training company. > > Thank you! > > Here's what I did to get my number. > > First attempt was v2 in RTP on June 30. > I just wasn't ready and I tried to rush into an exam before the > change. > > Second attempt was v3 in San Jose on Dec 8th. > I was 100% more prepared this time but didn't get my flow started > until late and just choked. > > Third attempt was v3 in San Jose on Jan 12th. > Just continued practicing and going over the things I knew I messed > up on. > > I used IPExpert exclusively. For my first attempt I attended a v2 > OWLE with Mark Snow about 4 weeks before the exam and I schedule a > week of back to back proctor labs sessions the week before. The > training was very good but I just wasn't ready to pass. > > My second attempt I attended a v3 OWLE with Vik Malhi about 4 weeks > before the exam. Vik is an amazing instructor and goes way out of his > way to help out his students and to ensure they understand the > material. I used my work lab to continue practicing before the exam. > > My third attempt I didn't have the money or the vacation time left for > an OWLE because of the holiday's but I reviewed SRNDs while stuck at > the in-laws for xmas. I flew into San Jose three days before the exam > and Vik was gracious enough to allow me to use his equipment to brush > up on a few things. I scheduled a 3 day long proctorlabs session and > knocked out as many labs as I could to work on speed. > > Some non-study related practices I used were the day before the exam I > go out and watch a movie in the theater. I would go for a 30 minute > walk the night before to ensure I got a good nights sleep. Nothing to > strenuous, I didn't want to be soar. All my exam attempts were > scheduled for a Tuesday. The reason for the Tuesday was because of > the joke that cars built on Tuesday run the best. After the RTP > attempt I got a tip to take it in San Jose. I live in Missouri so > flying to RTP was jumping ahead an hour for my body. Flying to San > Jose was jumping back 2 hours for me. So in RTP the exam starts at > 7:15am which to me is 6:15am. On the other hand San Jose the exam > starts at 8:30am so to me that is 10:30am. I don't know about you but > I'm more alert and ready by 10:30 but I'm still "waking" up at 6:15. > You get 8 hours total for the exam. That includes the open ended > questions. > > What I found most helpful was gathering a lot of the information that > was referenced frequently all in one place. For example before even > reading the exam I find what the IP addresses of the servers are and > put them at the top of a notepad. Next I'd get the extension of each > of the phones, the external number mask (if needed), then the mac > address. > > Next I'd access all the routers and run the command "sh ip int bri | e > una." What the command would do is display only the interfaces that > had ip addresses assigned to them. If some of the layer 3 interfaces > haven't been configured yet I would just run the command again after > configuring them and update my reference sheet. > > To make configurations quick and easy for me to recognize I named all > my sites H, A, X. H was for the HQ site, A was for the first branch > site, and X was the next branch site. > > The reference sheet would look like this: > > pub x.x.x.x > sub x.x.x.x > cup x.x.x.x > cuc x.x.x.x > ccx x.x.x.x > ntp x.x.x.x > cue x.x.x.x > > H1 XXX1 [external num mask] SEPAAAABBBBCCCC > H2 XXX2 [external num mask] SEPAAAABBBBCCCC > > A1 XXX1 [external num mask] SEPAAAABBBBCCCC > A2 XXX2 [external num mask] SEPAAAABBBBCCCC > > X1 XXX1 [external num mask] SEPAAAABBBBCCCC > X2 XXX2 [external num mask] SEPAAAABBBBCCCC > > HQ-RTR#sh ip int bri | e una > [output from hq router] > > BR1-RTR#sh ip int bri | e una > [output from br1 router] > > BR2-RTR#sh ip int bri | e una > [output from br2 router] > > After building the reference sheet I read through the exam, totally > skipping the call routing section. I took any of the call routing > pages and set them aside. After reading the exam I did everything I > could with the CLI. Starting with the infrastructure and DHCP, then > QoS, gateways, media resources, etc. If something needed to be > registered to CCM I'd make a note of the registration name on the > reference sheet. Once I did as much as I could to get phones and > gateways registered to CCM I'd start my CCM configurations. I'd start > with the left to right top down approach starting with the system > menu. If allowed I'd recommend using auto register for the phones. > Then I configured the gateways and media resources. Once I had a > basic config and had everything registered is when I'd start the > customization options of the phones. Don't worry about trying to get > everything in one shot. It'll be okay to return to a phone or gateway > config page 3 or 4 or maybe even 5 times to get it completely setup. > Just make sure each time is worth something and you're not wasting > time. Also make use of bulk administration when you can. > > After I had a good base setup is when I finally read the call routing > section. Here's something I used to help me keep the call flow in > order: > > DEV > CSS > PT > TP > CSS > PT > RP > RL > RG > GW > CSS > PT > XFORM > > The CSS/PT naming scheme I used was something like this: > > For call routing and class of restriction I'd use PT-COR-RP-H-LOCAL > PT for partition > COR for class of restriction > RP for route pattern > H for site > then type of call. > > The CSS was named CSS-COR-H-DEV > CSS for calling search space > COR for class of restriction > H for site > DEV because it's a device css > > For phone calling xform patterns I'd use RX-CGN-H-LOCAL-PT > RX for receiving because the phone is receiving the calling number > CGN for calling number > H for site > then type of call > PT for partition > > The CSS was named RX-CGN-H-CSS. > RX for receiving because the phone is receiving the calling number > CGN for calling number > H for site > CSS for calling search space > > For gateway calling/called xform patterns I'd use TX-CGN-H-PH-PT or > TX-CDN-H-LOCAL-PT > TX for transmitting because the gateway transmits the CGN and CDN. > CGN for calling number > CDN for called number > H for site > type of device or call > PT for partition > > The CSS was named TX-CGN-HGW or TX-CDN-HGW > TX for transmitting because the gateway transmits the CGN and CDN. > CGN for calling number > CDN for called number > HGW for the HQ Gateway > > As a disclaimer this was the strategy I used and practiced and > developed over the time I've been studying and labing. This may or > may not fit your style and I'm providing so that my strategy may > supplement the strategy you're currently developing. > > I finished the majority of the test within 6 hours which allowed me 2 > hours to test everything. I basically went back to the beginning of > the lab and checked or tested each and every question in as many > different scenarios as I could. > > I knew I was finally ready to get my CCIE when going through another > mock lab was boring and repetitious and I felt like I wasn't learning > anything new. > _______________________________________________ > For more information regarding industry leading CCIE Lab training, > please visit www.ipexpert.com > _______________________________________________ > For more information regarding industry leading CCIE Lab training, > please visit www.ipexpert.com _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
