Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Suresh Bhandari]

There are other tasks for you to accomplish in the IOS devices before you
can actually register the phones. So, for me, it sounds better if you start
with the IOS devices, and then move to the Web GUI.

This is my opinion, however.



On Wed, Apr 17, 2013 at 3:35 AM, CCIEing  wrote:

> Dear All,
>
> In the devise base strategy  which is better to start with the CUCM and
> the applications or to start with the Router devices ??
>
> I believe to start with CUCM is better that allow the phones to register
> earlier, as all your testing then will depend on it.
>
> Appreciate your feedback and advice
>
>
>
>
> On Wed, Mar 27, 2013 at 2:40 AM, Dane Warner 
> wrote:
>
>> To All,
>>
>> ** **
>>
>> I took my second attempt on Monday, March 25 and did not pass.
>>
>> I was hoping for some insight on concrete suggestions to get faster. 
>>
>> I didn’t get hung up on any one task, I seemed to keep moving forward and
>> tried to type as fast as I could, using CLI shortcuts, etc.
>>
>> I used the device-based methodology and I feel pretty confident of my
>> technical knowledge.
>>
>> Yet I didn’t even get to many tasks at all, I would have needed another
>> 2-3 hours to complete all tasks.
>>
>> I hear of candidates completing all tasks in 6-7 hours, which means I
>> would need to become twice as fast as my last attempt.
>>
>> It almost sounds insurmountable. Do I need to take typing classes?
>>
>> ** **
>>
>> Any recommendations that don’t break the NDA would be greatly appreciated.
>> 
>>
>> ** **
>>
>> Regards,
>>
>> ** **
>>
>> *Dane Warner, CCVP*
>>
>> *Sr. Network Engineer*
>>
>> *Epoch Universal, Inc.*
>>
>> *(909)226-0755*
>>
>> *dwar...@epochuniversal.com  *
>>
>> *[image: Epoch_Logo_Smaller_Transparent]*
>>
>> ___
>> For more information regarding industry leading CCIE Lab training, please
>> visit www.ipexpert.com
>>
>> Are you a CCNP or CCIE and looking for a job? Check out
>> www.PlatinumPlacement.com
>>
>
>
> ___
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
> Are you a CCNP or CCIE and looking for a job? Check out
> www.PlatinumPlacement.com
>



-- 
Suresh Bhandari
<>___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[CCIEing]

Dear All,

In the devise base strategy  which is better to start with the CUCM and the
applications or to start with the Router devices ??

I believe to start with CUCM is better that allow the phones to register
earlier, as all your testing then will depend on it.

Appreciate your feedback and advice




On Wed, Mar 27, 2013 at 2:40 AM, Dane Warner wrote:

> To All,
>
> ** **
>
> I took my second attempt on Monday, March 25 and did not pass.
>
> I was hoping for some insight on concrete suggestions to get faster. 
>
> I didn’t get hung up on any one task, I seemed to keep moving forward and
> tried to type as fast as I could, using CLI shortcuts, etc.
>
> I used the device-based methodology and I feel pretty confident of my
> technical knowledge.
>
> Yet I didn’t even get to many tasks at all, I would have needed another
> 2-3 hours to complete all tasks.
>
> I hear of candidates completing all tasks in 6-7 hours, which means I
> would need to become twice as fast as my last attempt.
>
> It almost sounds insurmountable. Do I need to take typing classes?
>
> ** **
>
> Any recommendations that don’t break the NDA would be greatly appreciated.
> 
>
> ** **
>
> Regards,
>
> ** **
>
> *Dane Warner, CCVP*
>
> *Sr. Network Engineer*
>
> *Epoch Universal, Inc.*
>
> *(909)226-0755*
>
> *dwar...@epochuniversal.com  *
>
> *[image: Epoch_Logo_Smaller_Transparent]*
>
> ___
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
> Are you a CCNP or CCIE and looking for a job? Check out
> www.PlatinumPlacement.com
>
<>___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[donny f]

hi all,

does anyone know the quickest trick on provision phone and DN in exam?
i ever read ,there is "super copy".

tks
d

On Sat, Apr 6, 2013 at 12:50 AM, Peter Simmons  wrote:

>  Bill,
>
> Your feedback has been awesome - much appreciated by all here, I'm certain
> - it has definitely refined and clarified my own vague thinking in this
> area considerably - thankyou!
>
> Could you expand on the phone provisioning method you use?
>
> I'm taking far too long on this during practice (and obviously when I've
> been supporting the profitability of the Cisco catering team in Brussels
> previously...) and it is an area I've been looking to completely transform
> for my next attempt.
>
> Is there a documentation link or example you could point me at on this?
>
> I'd like to see what difference it would make to my times by trying this
> (radically) different approach!
>
> regards
>
> Peter
>
> Peter Simmons
>
>  On 4/3/2013 5:59 PM, William Bell wrote:
>
> I am not familiar with Marko's approach for "on-screen" window placement.
>
> I actually don't have a specific strategy in this area.
>
> I do create a notepad file for the following:
>
>
> basic.txt :  basic infrastructure notes and notes on phone/user configs
> sw.txt : switch configs
> hq.txt : HQ gateway/router configs
> sb.txt : Site B gateway/router configs
> sc.txt : Site C gateway/router configs
> rp.txt : Route plan configs (when I get to that point)
>
> I have the above .txt files open all of the time. I only keep basic.txt
> "up" on the screen. I keep the others minimized. I restore them "as
> needed".
>
> During the course of the exam I will create other notepad files
> temporarily. Most notably:
>
> 1. When I create partitions. I have a naming convention that is basically
> uniform across sites. So, I lay out the HQ versions in notepad. Paste in
> CUCM. Then do a search/replace for "HQ"/"SB". Repeat for Site C. Kill the
> notepad
>
> 2. When I provision phones. I use a series of SQL commands from the CLI to
> provision phones. I type them out in notepad and paste from there. Then I
> kill the notepad.
>
> 3. Troubleshooting questions. Because I don't want to deal with VNC's
> sluggish nature, I'll do my TS work in notepad on the candidate PC and then
> copy/paste to the VNC desktop.
>
> I think that's it.
>
> As far as window orientation. I keep basic.txt in the top right corner of
> the screen. If I need hq.txt/sb.txt/etc. then I restore to bottom right.
> I'll keep (or try to keep) console sessions in the middle and IE sessions
> near the left. But I haven't really thought about it that much.
>
>
> -Bill
>
>  --
> William Bell
> blog: http://ucguerrilla.com
> twitter: @ucguerrilla
>
>
>
>  On Apr 3, 2013, at 12:32 PM, Ramcharan Arya wrote:
>
>Hi Bill,
>
> Thank you very much for nice writeup on strategy.
>
> This is really helpful for CCIE vocie lab aspirants.  Do you have any
> strategy how many notepad sessions to keep open simultaneously.
>
> How to arrange SecureCRT sessions screen, online lab webpage, and notepad
> on 32" screen.
>
> I am still practice same method which I learn during R&S bootcamp with
> Marko.If you have any better approach please share.
>
>
> Regards,
> Ramcharan Arya
> CCIE # 28926 (R&S)
>
>
>
> On Wed, Apr 3, 2013 at 10:57 AM, William Bell wrote:
>
>>  I have had this as a draft for a few days. Just too busy to finish it
>> until now. So, some of my thoughts are redundant to what others have said.
>> Hopefully that isn't a bad thing.
>>
>> Timing is definitely a critical aspect of the exam. I know I have areas
>> where I am slower than I should be. I suspect most people do. Most of my
>> comments herein are based on my self-study practice labs. I have taken the
>> lab a couple of times but most of the tinkering I have done with my method
>> is during self-study. When I sit for the real lab, I don't tinker. I go
>> with whatever method I have been practicing. So, that is suggestion #1:
>> Don't tinker on lab day, stick to your guns and don't 2nd guess your method.
>>
>> Going back to the OP, I believe you should look at the bright side. Your
>> statement "...I seemed to keep moving forward..." is key. The fact you were
>> able to avoid a stall is important. I believe controlling this exam is
>> about rhythm and finding what config approach helps you establish a
>> sustainable and consistent rhythm. Speed on any individual task is critical
>> but rhythm is king in my opinion.
>>
>> Like others (most?), I follow the device-based approach. It has been
>> around since pre 3.0 blueprint (contrary to popular opinion) and is a
>> proven strategy. However, I have found that you will need to customize that
>> approach to suit your needs. For me, it is about managing the transitions.
>> Again, I believe focusing on establishing and maintaining a rhythm is
>> absolutely key. Smoothing the transitions and/or stacking tasks that help
>> ease transitions is important. Also, you won't maintain the same rhythm
>> throughout the ex

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Peter Simmons]

Bill,

Your feedback has been awesome - much appreciated by all here, I'm 
certain - it has definitely refined and clarified my own vague thinking 
in this area considerably - thankyou!


Could you expand on the phone provisioning method you use?

I'm taking far too long on this during practice (and obviously when I've 
been supporting the profitability of the Cisco catering team in Brussels 
previously...) and it is an area I've been looking to completely 
transform for my next attempt.


Is there a documentation link or example you could point me at on this?

I'd like to see what difference it would make to my times by trying this 
(radically) different approach!


regards

Peter

Peter Simmons

On 4/3/2013 5:59 PM, William Bell wrote:

I am not familiar with Marko's approach for "on-screen" window placement.

I actually don't have a specific strategy in this area.

I do create a notepad file for the following:


basic.txt:  basic infrastructure notes and notes on phone/user configs
sw.txt: switch configs
hq.txt: HQ gateway/router configs
sb.txt: Site B gateway/router configs
sc.txt: Site C gateway/router configs
rp.txt: Route plan configs (when I get to that point)

I have the above .txt files open all of the time. I only keep 
basic.txt "up" on the screen. I keep the others minimized. I restore 
them "as needed".


During the course of the exam I will create other notepad files 
temporarily. Most notably:


1. When I create partitions. I have a naming convention that is 
basically uniform across sites. So, I lay out the HQ versions in 
notepad. Paste in CUCM. Then do a search/replace for "HQ"/"SB". Repeat 
for Site C. Kill the notepad


2. When I provision phones. I use a series of SQL commands from the 
CLI to provision phones. I type them out in notepad and paste from 
there. Then I kill the notepad.


3. Troubleshooting questions. Because I don't want to deal with VNC's 
sluggish nature, I'll do my TS work in notepad on the candidate PC and 
then copy/paste to the VNC desktop.


I think that's it.

As far as window orientation. I keep basic.txt in the top right corner 
of the screen. If I need hq.txt/sb.txt/etc. then I restore to bottom 
right. I'll keep (or try to keep) console sessions in the middle and 
IE sessions near the left. But I haven't really thought about it that 
much.



-Bill

--
William Bell
blog: http://ucguerrilla.com
twitter: @ucguerrilla



On Apr 3, 2013, at 12:32 PM, Ramcharan Arya wrote:


Hi Bill,

Thank you very much for nice writeup on strategy.

This is really helpful for CCIE vocie lab aspirants.  Do you have any 
strategy how many notepad sessions to keep open simultaneously.


How to arrange SecureCRT sessions screen, online lab webpage, and 
notepad on 32" screen.


I am still practice same method which I learn during R&S bootcamp 
with Marko.If you have any better approach please share.



Regards,
Ramcharan Arya
CCIE # 28926 (R&S)



On Wed, Apr 3, 2013 at 10:57 AM, William Bell > wrote:


I have had this as a draft for a few days. Just too busy to
finish it until now. So, some of my thoughts are redundant to
what others have said. Hopefully that isn't a bad thing.

Timing is definitely a critical aspect of the exam. I know I have
areas where I am slower than I should be. I suspect most people
do. Most of my comments herein are based on my self-study
practice labs. I have taken the lab a couple of times but most of
the tinkering I have done with my method is during self-study.
When I sit for the real lab, I don't tinker. I go with whatever
method I have been practicing. So, that is suggestion #1: Don't
tinker on lab day, stick to your guns and don't 2nd guess your
method.

Going back to the OP, I believe you should look at the bright
side. Your statement "...I seemed to keep moving forward..." is
key. The fact you were able to avoid a stall is important. I
believe controlling this exam is about rhythm and finding what
config approach helps you establish a sustainable and consistent
rhythm. Speed on any individual task is critical but rhythm is
king in my opinion.

Like others (most?), I follow the device-based approach. It has
been around since pre 3.0 blueprint (contrary to popular opinion)
and is a proven strategy. However, I have found that you will
need to customize that approach to suit your needs. For me, it is
about managing the transitions. Again, I believe focusing on
establishing and maintaining a rhythm is absolutely key.
Smoothing the transitions and/or stacking tasks that help ease
transitions is important. Also, you won't maintain the same
rhythm throughout the exam. Some tasks you will bang out (or
should) very fast. Others, you will need to pay close attention
to what you are doing.

So, suggestion #2 is find your rhythm.

Establishing your rhythm is a product of repetition. Practice,
practic

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[donny f]

hi Bill and others.

What is the quickest way to config phones and DNs in exam ?
I only do it in repetition. if any tips could save my time.

tks

On Wed, Apr 3, 2013 at 7:14 PM, Josh Petro  wrote:

> My goodness Bill! Thank you for the reply and thanks to everyone else for
> replying. This has been outstanding feedback.
> Josh
>  On Apr 3, 2013 1:19 PM, "William Bell"  wrote:
>
>> I separate QoS from standard infrastructure and do it later for two main
>> reasons:
>>
>>
>> 1. I typically use auto qos for LAN QoS. There is just something about
>> the mechanics of that process that is a shift from how I build the CLI
>> commands for other infrastructure bits. That shift is large enough to throw
>> off my rhythm.
>>
>>
>> 2. I like to get my phones, media resources, and GW devices registered to
>> CUCM before dorking with QoS. I then check registrations after QoS is in
>> place. This helps me avoid having too many things to check if my phones or
>> some other device has registration issues. If I do dev reg before QoS then
>> the scope of issue root cause is smaller.
>>
>> -Bill
>>
>>
>>
>>  --
>> William Bell
>> blog: http://ucguerrilla.com
>> twitter: @ucguerrilla
>>
>>
>>
>>  On Apr 3, 2013, at 12:58 PM, Suresh Bhandari wrote:
>>
>>   A real long mail to read But I read it entirely, not skipping a
>> word.
>>
>> Thanks Bill for sharing the concept. I am also following the device based
>> approach, but I haven't thought of what you call it "basic.txt". It will be
>> awesome piece of information in notepad, during the lab day.
>>
>> I saw that everyone is responding QoS as the tail-ender config...
>> what is the speed you can expect at the lab (thinking it might be due to
>> the speed/delay)?
>>
>> Thanks once again.
>>
>>
>> On Wed, Apr 3, 2013 at 9:42 PM, William Bell wrote:
>>
>>>  I have had this as a draft for a few days. Just too busy to finish it
>>> until now. So, some of my thoughts are redundant to what others have said.
>>> Hopefully that isn't a bad thing.
>>>
>>> Timing is definitely a critical aspect of the exam. I know I have areas
>>> where I am slower than I should be. I suspect most people do. Most of my
>>> comments herein are based on my self-study practice labs. I have taken the
>>> lab a couple of times but most of the tinkering I have done with my method
>>> is during self-study. When I sit for the real lab, I don't tinker. I go
>>> with whatever method I have been practicing. So, that is suggestion #1:
>>> Don't tinker on lab day, stick to your guns and don't 2nd guess your method.
>>>
>>> Going back to the OP, I believe you should look at the bright side. Your
>>> statement "...I seemed to keep moving forward..." is key. The fact you were
>>> able to avoid a stall is important. I believe controlling this exam is
>>> about rhythm and finding what config approach helps you establish a
>>> sustainable and consistent rhythm. Speed on any individual task is critical
>>> but rhythm is king in my opinion.
>>>
>>> Like others (most?), I follow the device-based approach. It has been
>>> around since pre 3.0 blueprint (contrary to popular opinion) and is a
>>> proven strategy. However, I have found that you will need to customize that
>>> approach to suit your needs. For me, it is about managing the transitions.
>>> Again, I believe focusing on establishing and maintaining a rhythm is
>>> absolutely key. Smoothing the transitions and/or stacking tasks that help
>>> ease transitions is important. Also, you won't maintain the same rhythm
>>> throughout the exam. Some tasks you will bang out (or should) very fast.
>>> Others, you will need to pay close attention to what you are doing.
>>>
>>> So, suggestion #2 is find your rhythm.
>>>
>>> Establishing your rhythm is a product of repetition. Practice, practice,
>>> practice as Mr. Sears puts it. You may also need some face time with the
>>> real lab to help you come into your rhythm. For example, some of the "weak
>>> spots" I had (or maybe still have) and adjustments I made.
>>>
>>>
>>> 1. Transitioning from read-through to config. The read through is/was
>>> the worst for me. Most people I have spoken with (who have passed or come
>>> close) are able to get through the read-through in 30 minutes. Some say
>>> less. I was taking a whole lot more time than 30 minutes. My budget for
>>> this task is 30m today.
>>>
>>> Adjustments I made:
>>>
>>>
>>>- Dial Plan. I was building out my dial plan (on paper) during the
>>>read through. My logic was that "you have to do it at some point, just do
>>>it now". The flaw with that logic is that to establish a good rhythm, you
>>>need to avoid lingering on a task for too long. I decided that I would
>>>focus on getting the tasks mapped out as quick as possible and the task 
>>> of
>>>mapping out a dial plan could wait. So, I added a section in my table to
>>>track the DP-related tasks by task ID (e.g. 4.1) only.
>>>- Skim. I already know that I am going to do a thorough 

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Josh Petro]

My goodness Bill! Thank you for the reply and thanks to everyone else for
replying. This has been outstanding feedback.
Josh
On Apr 3, 2013 1:19 PM, "William Bell"  wrote:

> I separate QoS from standard infrastructure and do it later for two main
> reasons:
>
>
> 1. I typically use auto qos for LAN QoS. There is just something about the
> mechanics of that process that is a shift from how I build the CLI commands
> for other infrastructure bits. That shift is large enough to throw off my
> rhythm.
>
>
> 2. I like to get my phones, media resources, and GW devices registered to
> CUCM before dorking with QoS. I then check registrations after QoS is in
> place. This helps me avoid having too many things to check if my phones or
> some other device has registration issues. If I do dev reg before QoS then
> the scope of issue root cause is smaller.
>
> -Bill
>
>
>
> --
> William Bell
> blog: http://ucguerrilla.com
> twitter: @ucguerrilla
>
>
>
> On Apr 3, 2013, at 12:58 PM, Suresh Bhandari wrote:
>
> A real long mail to read But I read it entirely, not skipping a word.
>
> Thanks Bill for sharing the concept. I am also following the device based
> approach, but I haven't thought of what you call it "basic.txt". It will be
> awesome piece of information in notepad, during the lab day.
>
> I saw that everyone is responding QoS as the tail-ender config... what
> is the speed you can expect at the lab (thinking it might be due to the
> speed/delay)?
>
> Thanks once again.
>
>
> On Wed, Apr 3, 2013 at 9:42 PM, William Bell  wrote:
>
>> I have had this as a draft for a few days. Just too busy to finish it
>> until now. So, some of my thoughts are redundant to what others have said.
>> Hopefully that isn't a bad thing.
>>
>> Timing is definitely a critical aspect of the exam. I know I have areas
>> where I am slower than I should be. I suspect most people do. Most of my
>> comments herein are based on my self-study practice labs. I have taken the
>> lab a couple of times but most of the tinkering I have done with my method
>> is during self-study. When I sit for the real lab, I don't tinker. I go
>> with whatever method I have been practicing. So, that is suggestion #1:
>> Don't tinker on lab day, stick to your guns and don't 2nd guess your method.
>>
>> Going back to the OP, I believe you should look at the bright side. Your
>> statement "...I seemed to keep moving forward..." is key. The fact you were
>> able to avoid a stall is important. I believe controlling this exam is
>> about rhythm and finding what config approach helps you establish a
>> sustainable and consistent rhythm. Speed on any individual task is critical
>> but rhythm is king in my opinion.
>>
>> Like others (most?), I follow the device-based approach. It has been
>> around since pre 3.0 blueprint (contrary to popular opinion) and is a
>> proven strategy. However, I have found that you will need to customize that
>> approach to suit your needs. For me, it is about managing the transitions.
>> Again, I believe focusing on establishing and maintaining a rhythm is
>> absolutely key. Smoothing the transitions and/or stacking tasks that help
>> ease transitions is important. Also, you won't maintain the same rhythm
>> throughout the exam. Some tasks you will bang out (or should) very fast.
>> Others, you will need to pay close attention to what you are doing.
>>
>> So, suggestion #2 is find your rhythm.
>>
>> Establishing your rhythm is a product of repetition. Practice, practice,
>> practice as Mr. Sears puts it. You may also need some face time with the
>> real lab to help you come into your rhythm. For example, some of the "weak
>> spots" I had (or maybe still have) and adjustments I made.
>>
>>
>> 1. Transitioning from read-through to config. The read through is/was the
>> worst for me. Most people I have spoken with (who have passed or come
>> close) are able to get through the read-through in 30 minutes. Some say
>> less. I was taking a whole lot more time than 30 minutes. My budget for
>> this task is 30m today.
>>
>> Adjustments I made:
>>
>>
>>- Dial Plan. I was building out my dial plan (on paper) during the
>>read through. My logic was that "you have to do it at some point, just do
>>it now". The flaw with that logic is that to establish a good rhythm, you
>>need to avoid lingering on a task for too long. I decided that I would
>>focus on getting the tasks mapped out as quick as possible and the task of
>>mapping out a dial plan could wait. So, I added a section in my table to
>>track the DP-related tasks by task ID (e.g. 4.1) only.
>>- Skim. I already know that I am going to do a thorough read on the
>>questions at least once (during config) and likely twice (during
>>validation). No sense in reading the question in detail 3 times. So, I
>>mainly focus on what devices/apps are affected by the question and put the
>>ID in the table.
>>
>>
>> How I use this task:
>>
>>- I build a tabl

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[William Bell]

I separate QoS from standard infrastructure and do it later for two main 
reasons:


1. I typically use auto qos for LAN QoS. There is just something about the 
mechanics of that process that is a shift from how I build the CLI commands for 
other infrastructure bits. That shift is large enough to throw off my rhythm.


2. I like to get my phones, media resources, and GW devices registered to CUCM 
before dorking with QoS. I then check registrations after QoS is in place. This 
helps me avoid having too many things to check if my phones or some other 
device has registration issues. If I do dev reg before QoS then the scope of 
issue root cause is smaller. 

-Bill



--
William Bell
blog: http://ucguerrilla.com
twitter: @ucguerrilla



On Apr 3, 2013, at 12:58 PM, Suresh Bhandari wrote:

> A real long mail to read But I read it entirely, not skipping a word. 
> 
> Thanks Bill for sharing the concept. I am also following the device based 
> approach, but I haven't thought of what you call it "basic.txt". It will be 
> awesome piece of information in notepad, during the lab day.
> 
> I saw that everyone is responding QoS as the tail-ender config... what is 
> the speed you can expect at the lab (thinking it might be due to the 
> speed/delay)?
> 
> Thanks once again. 
> 
> 
> On Wed, Apr 3, 2013 at 9:42 PM, William Bell  wrote:
> I have had this as a draft for a few days. Just too busy to finish it until 
> now. So, some of my thoughts are redundant to what others have said. 
> Hopefully that isn't a bad thing.
> 
> Timing is definitely a critical aspect of the exam. I know I have areas where 
> I am slower than I should be. I suspect most people do. Most of my comments 
> herein are based on my self-study practice labs. I have taken the lab a 
> couple of times but most of the tinkering I have done with my method is 
> during self-study. When I sit for the real lab, I don't tinker. I go with 
> whatever method I have been practicing. So, that is suggestion #1: Don't 
> tinker on lab day, stick to your guns and don't 2nd guess your method.
> 
> Going back to the OP, I believe you should look at the bright side. Your 
> statement "...I seemed to keep moving forward..." is key. The fact you were 
> able to avoid a stall is important. I believe controlling this exam is about 
> rhythm and finding what config approach helps you establish a sustainable and 
> consistent rhythm. Speed on any individual task is critical but rhythm is 
> king in my opinion. 
> 
> Like others (most?), I follow the device-based approach. It has been around 
> since pre 3.0 blueprint (contrary to popular opinion) and is a proven 
> strategy. However, I have found that you will need to customize that approach 
> to suit your needs. For me, it is about managing the transitions. Again, I 
> believe focusing on establishing and maintaining a rhythm is absolutely key. 
> Smoothing the transitions and/or stacking tasks that help ease transitions is 
> important. Also, you won't maintain the same rhythm throughout the exam. Some 
> tasks you will bang out (or should) very fast. Others, you will need to pay 
> close attention to what you are doing. 
> 
> So, suggestion #2 is find your rhythm. 
> 
> Establishing your rhythm is a product of repetition. Practice, practice, 
> practice as Mr. Sears puts it. You may also need some face time with the real 
> lab to help you come into your rhythm. For example, some of the "weak spots" 
> I had (or maybe still have) and adjustments I made.
> 
> 
> 1. Transitioning from read-through to config. The read through is/was the 
> worst for me. Most people I have spoken with (who have passed or come close) 
> are able to get through the read-through in 30 minutes. Some say less. I was 
> taking a whole lot more time than 30 minutes. My budget for this task is 30m 
> today.
> 
> Adjustments I made:
> 
> Dial Plan. I was building out my dial plan (on paper) during the read 
> through. My logic was that "you have to do it at some point, just do it now". 
> The flaw with that logic is that to establish a good rhythm, you need to 
> avoid lingering on a task for too long. I decided that I would focus on 
> getting the tasks mapped out as quick as possible and the task of mapping out 
> a dial plan could wait. So, I added a section in my table to track the 
> DP-related tasks by task ID (e.g. 4.1) only. 
> Skim. I already know that I am going to do a thorough read on the questions 
> at least once (during config) and likely twice (during validation). No sense 
> in reading the question in detail 3 times. So, I mainly focus on what 
> devices/apps are affected by the question and put the ID in the table. 
> 
> How I use this task:
> I build a table (like the dev-based approach table) to track tasks
> I build a table to track what the PSTN wants to see for off net calls (this 
> is key because I can build an entire h323 config just on that info)
> I track phone/user features/buttons/etc. This goes to speed wh

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[William Bell]

I am not familiar with Marko's approach for "on-screen" window placement. 

I actually don't have a specific strategy in this area.

I do create a notepad file for the following:


basic.txt   :  basic infrastructure notes and notes on phone/user 
configs
sw.txt  : switch configs
hq.txt  : HQ gateway/router configs
sb.txt  : Site B gateway/router configs
sc.txt  : Site C gateway/router configs
rp.txt  : Route plan configs (when I get to that point)

I have the above .txt files open all of the time. I only keep basic.txt "up" on 
the screen. I keep the others minimized. I restore them "as needed". 

During the course of the exam I will create other notepad files temporarily. 
Most notably:

1. When I create partitions. I have a naming convention that is basically 
uniform across sites. So, I lay out the HQ versions in notepad. Paste in CUCM. 
Then do a search/replace for "HQ"/"SB". Repeat for Site C. Kill the notepad

2. When I provision phones. I use a series of SQL commands from the CLI to 
provision phones. I type them out in notepad and paste from there. Then I kill 
the notepad.

3. Troubleshooting questions. Because I don't want to deal with VNC's sluggish 
nature, I'll do my TS work in notepad on the candidate PC and then copy/paste 
to the VNC desktop.

I think that's it. 

As far as window orientation. I keep basic.txt in the top right corner of the 
screen. If I need hq.txt/sb.txt/etc. then I restore to bottom right. I'll keep 
(or try to keep) console sessions in the middle and IE sessions near the left. 
But I haven't really thought about it that much.


-Bill

--
William Bell
blog: http://ucguerrilla.com
twitter: @ucguerrilla



On Apr 3, 2013, at 12:32 PM, Ramcharan Arya wrote:

> Hi Bill,
> 
> Thank you very much for nice writeup on strategy.
> 
> This is really helpful for CCIE vocie lab aspirants.  Do you have any 
> strategy how many notepad sessions to keep open simultaneously.
> 
> How to arrange SecureCRT sessions screen, online lab webpage, and notepad on 
> 32" screen.
> 
> I am still practice same method which I learn during R&S bootcamp with 
> Marko.If you have any better approach please share.
> 
> 
> Regards,
> Ramcharan Arya
> CCIE # 28926 (R&S)
> 
> 
> 
> On Wed, Apr 3, 2013 at 10:57 AM, William Bell  wrote:
> I have had this as a draft for a few days. Just too busy to finish it until 
> now. So, some of my thoughts are redundant to what others have said. 
> Hopefully that isn't a bad thing.
> 
> Timing is definitely a critical aspect of the exam. I know I have areas where 
> I am slower than I should be. I suspect most people do. Most of my comments 
> herein are based on my self-study practice labs. I have taken the lab a 
> couple of times but most of the tinkering I have done with my method is 
> during self-study. When I sit for the real lab, I don't tinker. I go with 
> whatever method I have been practicing. So, that is suggestion #1: Don't 
> tinker on lab day, stick to your guns and don't 2nd guess your method.
> 
> Going back to the OP, I believe you should look at the bright side. Your 
> statement "...I seemed to keep moving forward..." is key. The fact you were 
> able to avoid a stall is important. I believe controlling this exam is about 
> rhythm and finding what config approach helps you establish a sustainable and 
> consistent rhythm. Speed on any individual task is critical but rhythm is 
> king in my opinion. 
> 
> Like others (most?), I follow the device-based approach. It has been around 
> since pre 3.0 blueprint (contrary to popular opinion) and is a proven 
> strategy. However, I have found that you will need to customize that approach 
> to suit your needs. For me, it is about managing the transitions. Again, I 
> believe focusing on establishing and maintaining a rhythm is absolutely key. 
> Smoothing the transitions and/or stacking tasks that help ease transitions is 
> important. Also, you won't maintain the same rhythm throughout the exam. Some 
> tasks you will bang out (or should) very fast. Others, you will need to pay 
> close attention to what you are doing. 
> 
> So, suggestion #2 is find your rhythm. 
> 
> Establishing your rhythm is a product of repetition. Practice, practice, 
> practice as Mr. Sears puts it. You may also need some face time with the real 
> lab to help you come into your rhythm. For example, some of the "weak spots" 
> I had (or maybe still have) and adjustments I made.
> 
> 
> 1. Transitioning from read-through to config. The read through is/was the 
> worst for me. Most people I have spoken with (who have passed or come close) 
> are able to get through the read-through in 30 minutes. Some say less. I was 
> taking a whole lot more time than 30 minutes. My budget for this task is 30m 
> today.
> 
> Adjustments I made:
> 
> Dial Plan. I was building out my dial plan (on paper) during the read 
> through. My logic was that "you have to do it at some point, just do it no

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Suresh Bhandari]

A real long mail to read But I read it entirely, not skipping a word.

Thanks Bill for sharing the concept. I am also following the device based
approach, but I haven't thought of what you call it "basic.txt". It will be
awesome piece of information in notepad, during the lab day.

I saw that everyone is responding QoS as the tail-ender config... what
is the speed you can expect at the lab (thinking it might be due to the
speed/delay)?

Thanks once again.


On Wed, Apr 3, 2013 at 9:42 PM, William Bell  wrote:

> I have had this as a draft for a few days. Just too busy to finish it
> until now. So, some of my thoughts are redundant to what others have said.
> Hopefully that isn't a bad thing.
>
> Timing is definitely a critical aspect of the exam. I know I have areas
> where I am slower than I should be. I suspect most people do. Most of my
> comments herein are based on my self-study practice labs. I have taken the
> lab a couple of times but most of the tinkering I have done with my method
> is during self-study. When I sit for the real lab, I don't tinker. I go
> with whatever method I have been practicing. So, that is suggestion #1:
> Don't tinker on lab day, stick to your guns and don't 2nd guess your method.
>
> Going back to the OP, I believe you should look at the bright side. Your
> statement "...I seemed to keep moving forward..." is key. The fact you were
> able to avoid a stall is important. I believe controlling this exam is
> about rhythm and finding what config approach helps you establish a
> sustainable and consistent rhythm. Speed on any individual task is critical
> but rhythm is king in my opinion.
>
> Like others (most?), I follow the device-based approach. It has been
> around since pre 3.0 blueprint (contrary to popular opinion) and is a
> proven strategy. However, I have found that you will need to customize that
> approach to suit your needs. For me, it is about managing the transitions.
> Again, I believe focusing on establishing and maintaining a rhythm is
> absolutely key. Smoothing the transitions and/or stacking tasks that help
> ease transitions is important. Also, you won't maintain the same rhythm
> throughout the exam. Some tasks you will bang out (or should) very fast.
> Others, you will need to pay close attention to what you are doing.
>
> So, suggestion #2 is find your rhythm.
>
> Establishing your rhythm is a product of repetition. Practice, practice,
> practice as Mr. Sears puts it. You may also need some face time with the
> real lab to help you come into your rhythm. For example, some of the "weak
> spots" I had (or maybe still have) and adjustments I made.
>
>
> 1. Transitioning from read-through to config. The read through is/was the
> worst for me. Most people I have spoken with (who have passed or come
> close) are able to get through the read-through in 30 minutes. Some say
> less. I was taking a whole lot more time than 30 minutes. My budget for
> this task is 30m today.
>
> Adjustments I made:
>
>
>- Dial Plan. I was building out my dial plan (on paper) during the
>read through. My logic was that "you have to do it at some point, just do
>it now". The flaw with that logic is that to establish a good rhythm, you
>need to avoid lingering on a task for too long. I decided that I would
>focus on getting the tasks mapped out as quick as possible and the task of
>mapping out a dial plan could wait. So, I added a section in my table to
>track the DP-related tasks by task ID (e.g. 4.1) only.
>- Skim. I already know that I am going to do a thorough read on the
>questions at least once (during config) and likely twice (during
>validation). No sense in reading the question in detail 3 times. So, I
>mainly focus on what devices/apps are affected by the question and put the
>ID in the table.
>
>
> How I use this task:
>
>- I build a table (like the dev-based approach table) to track tasks
>- I build a table to track what the PSTN wants to see for off net
>calls (this is key because I can build an entire h323 config just on that
>info)
>- I track phone/user features/buttons/etc. This goes to speed when
>customizing phones
>- I build a basic.txt text file to capture IP addresses, vlans,
>interface assignments, etc. I keep this very short. Note that with the new
>exam, the instructions are electronic. This kinda de-emphasizes the need to
>store some of this info.
>
>
>
> 2. Where to stick in QoS. QoS is clearly infrastructure and all of the
> action happens in the router config. However, for me there is a "slow down"
> if I try to stick QoS config in with banging out vlan, ntp, dhcp, rsvp,
> mrm, h323, etc. I can do all of the other IOS configs very quickly in
> notepad. QoS is noticeably "slower" for me.
>
> Adjustment I made:
>
>- I avoid auto qos on the LAN switch if I can. I have found the LAN
>QoS questions to be "incomplete". Meaning, they don't reflect reality in
> 

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Ramcharan Arya]

Hi Bill,

Thank you very much for nice writeup on strategy.

This is really helpful for CCIE vocie lab aspirants.  Do you have any
strategy how many notepad sessions to keep open simultaneously.

How to arrange SecureCRT sessions screen, online lab webpage, and notepad
on 32" screen.

I am still practice same method which I learn during R&S bootcamp with
Marko.If you have any better approach please share.


Regards,
Ramcharan Arya
CCIE # 28926 (R&S)



On Wed, Apr 3, 2013 at 10:57 AM, William Bell  wrote:

> I have had this as a draft for a few days. Just too busy to finish it
> until now. So, some of my thoughts are redundant to what others have said.
> Hopefully that isn't a bad thing.
>
> Timing is definitely a critical aspect of the exam. I know I have areas
> where I am slower than I should be. I suspect most people do. Most of my
> comments herein are based on my self-study practice labs. I have taken the
> lab a couple of times but most of the tinkering I have done with my method
> is during self-study. When I sit for the real lab, I don't tinker. I go
> with whatever method I have been practicing. So, that is suggestion #1:
> Don't tinker on lab day, stick to your guns and don't 2nd guess your method.
>
> Going back to the OP, I believe you should look at the bright side. Your
> statement "...I seemed to keep moving forward..." is key. The fact you were
> able to avoid a stall is important. I believe controlling this exam is
> about rhythm and finding what config approach helps you establish a
> sustainable and consistent rhythm. Speed on any individual task is critical
> but rhythm is king in my opinion.
>
> Like others (most?), I follow the device-based approach. It has been
> around since pre 3.0 blueprint (contrary to popular opinion) and is a
> proven strategy. However, I have found that you will need to customize that
> approach to suit your needs. For me, it is about managing the transitions.
> Again, I believe focusing on establishing and maintaining a rhythm is
> absolutely key. Smoothing the transitions and/or stacking tasks that help
> ease transitions is important. Also, you won't maintain the same rhythm
> throughout the exam. Some tasks you will bang out (or should) very fast.
> Others, you will need to pay close attention to what you are doing.
>
> So, suggestion #2 is find your rhythm.
>
> Establishing your rhythm is a product of repetition. Practice, practice,
> practice as Mr. Sears puts it. You may also need some face time with the
> real lab to help you come into your rhythm. For example, some of the "weak
> spots" I had (or maybe still have) and adjustments I made.
>
>
> 1. Transitioning from read-through to config. The read through is/was the
> worst for me. Most people I have spoken with (who have passed or come
> close) are able to get through the read-through in 30 minutes. Some say
> less. I was taking a whole lot more time than 30 minutes. My budget for
> this task is 30m today.
>
> Adjustments I made:
>
>
>- Dial Plan. I was building out my dial plan (on paper) during the
>read through. My logic was that "you have to do it at some point, just do
>it now". The flaw with that logic is that to establish a good rhythm, you
>need to avoid lingering on a task for too long. I decided that I would
>focus on getting the tasks mapped out as quick as possible and the task of
>mapping out a dial plan could wait. So, I added a section in my table to
>track the DP-related tasks by task ID (e.g. 4.1) only.
>- Skim. I already know that I am going to do a thorough read on the
>questions at least once (during config) and likely twice (during
>validation). No sense in reading the question in detail 3 times. So, I
>mainly focus on what devices/apps are affected by the question and put the
>ID in the table.
>
>
> How I use this task:
>
>- I build a table (like the dev-based approach table) to track tasks
>- I build a table to track what the PSTN wants to see for off net
>calls (this is key because I can build an entire h323 config just on that
>info)
>- I track phone/user features/buttons/etc. This goes to speed when
>customizing phones
>- I build a basic.txt text file to capture IP addresses, vlans,
>interface assignments, etc. I keep this very short. Note that with the new
>exam, the instructions are electronic. This kinda de-emphasizes the need to
>store some of this info.
>
>
>
> 2. Where to stick in QoS. QoS is clearly infrastructure and all of the
> action happens in the router config. However, for me there is a "slow down"
> if I try to stick QoS config in with banging out vlan, ntp, dhcp, rsvp,
> mrm, h323, etc. I can do all of the other IOS configs very quickly in
> notepad. QoS is noticeably "slower" for me.
>
> Adjustment I made:
>
>- I avoid auto qos on the LAN switch if I can. I have found the LAN
>QoS questions to be "incomplete". Meaning, they don't reflect reality in
>any way. 

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[William Bell]

I have had this as a draft for a few days. Just too busy to finish it until 
now. So, some of my thoughts are redundant to what others have said. Hopefully 
that isn't a bad thing.

Timing is definitely a critical aspect of the exam. I know I have areas where I 
am slower than I should be. I suspect most people do. Most of my comments 
herein are based on my self-study practice labs. I have taken the lab a couple 
of times but most of the tinkering I have done with my method is during 
self-study. When I sit for the real lab, I don't tinker. I go with whatever 
method I have been practicing. So, that is suggestion #1: Don't tinker on lab 
day, stick to your guns and don't 2nd guess your method.

Going back to the OP, I believe you should look at the bright side. Your 
statement "...I seemed to keep moving forward..." is key. The fact you were 
able to avoid a stall is important. I believe controlling this exam is about 
rhythm and finding what config approach helps you establish a sustainable and 
consistent rhythm. Speed on any individual task is critical but rhythm is king 
in my opinion. 

Like others (most?), I follow the device-based approach. It has been around 
since pre 3.0 blueprint (contrary to popular opinion) and is a proven strategy. 
However, I have found that you will need to customize that approach to suit 
your needs. For me, it is about managing the transitions. Again, I believe 
focusing on establishing and maintaining a rhythm is absolutely key. Smoothing 
the transitions and/or stacking tasks that help ease transitions is important. 
Also, you won't maintain the same rhythm throughout the exam. Some tasks you 
will bang out (or should) very fast. Others, you will need to pay close 
attention to what you are doing. 

So, suggestion #2 is find your rhythm. 

Establishing your rhythm is a product of repetition. Practice, practice, 
practice as Mr. Sears puts it. You may also need some face time with the real 
lab to help you come into your rhythm. For example, some of the "weak spots" I 
had (or maybe still have) and adjustments I made.


1. Transitioning from read-through to config. The read through is/was the worst 
for me. Most people I have spoken with (who have passed or come close) are able 
to get through the read-through in 30 minutes. Some say less. I was taking a 
whole lot more time than 30 minutes. My budget for this task is 30m today.

Adjustments I made:

Dial Plan. I was building out my dial plan (on paper) during the read through. 
My logic was that "you have to do it at some point, just do it now". The flaw 
with that logic is that to establish a good rhythm, you need to avoid lingering 
on a task for too long. I decided that I would focus on getting the tasks 
mapped out as quick as possible and the task of mapping out a dial plan could 
wait. So, I added a section in my table to track the DP-related tasks by task 
ID (e.g. 4.1) only. 
Skim. I already know that I am going to do a thorough read on the questions at 
least once (during config) and likely twice (during validation). No sense in 
reading the question in detail 3 times. So, I mainly focus on what devices/apps 
are affected by the question and put the ID in the table. 

How I use this task:
I build a table (like the dev-based approach table) to track tasks
I build a table to track what the PSTN wants to see for off net calls (this is 
key because I can build an entire h323 config just on that info)
I track phone/user features/buttons/etc. This goes to speed when customizing 
phones
I build a basic.txt text file to capture IP addresses, vlans, interface 
assignments, etc. I keep this very short. Note that with the new exam, the 
instructions are electronic. This kinda de-emphasizes the need to store some of 
this info. 


2. Where to stick in QoS. QoS is clearly infrastructure and all of the action 
happens in the router config. However, for me there is a "slow down" if I try 
to stick QoS config in with banging out vlan, ntp, dhcp, rsvp, mrm, h323, etc. 
I can do all of the other IOS configs very quickly in notepad. QoS is 
noticeably "slower" for me. 

Adjustment I made:
I avoid auto qos on the LAN switch if I can. I have found the LAN QoS questions 
to be "incomplete". Meaning, they don't reflect reality in any way. So, if I 
can I just bang out the minimum config w/o auto-qos and I do it as part of my 
regular infrastructure.
I push WAN QoS until after I get phones to auto-register. I do all of the 
switch, HQ, SB, and SC infrastructure and I come back to WAN QoS after device 
registration. Lately, I have been practicing with WAN QoS happening after CUCM 
base config (MGCP, MRG, phones, etc.). So, somewhere around the 3 hour mark.  
Others like to tackle it earlier on and that works to. There is no absolute 
here. Just pick a hole that works with your rhythm.

3. Site C and CUE. CUE is a real pain and can really mess with your rhythm. The 
key is to attack it early and check on it often. I treat CUE as backgr

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[William Bell]

To deal with the difference in IP addresses between my home lab and the real 
lab I got in the habit of building what I called the "basic.txt" file. In this 
file I put the following (sample)

!creds

os/web admin  


!hosts
PUB 
SUB 
CUC 
CCX 
UPS 
WS  

BB/NTP  
CUE 

!
! HQ
fa 0/1  R1
fa 0/2  Ph1
fa 0/3  Ph2
fa 0/5  Ph3

!vlan
100 Server  
101 Voice   
102 Data

lo0 

<etc.>


The idea is that you type out the IP addresses once. Then copy/paste into your 
other config notepads / web interfaces as needed. I keep the basic.txt file up 
all of the time. I actually put it in the top right of the screen so that I can 
right click/copy quickly.

Just my 2 cents.

-Bill

--
William Bell
blog: http://ucguerrilla.com
twitter: @ucguerrilla



On Apr 3, 2013, at 2:14 AM, ie ravindra wrote:

> Is there any ways to adapt with IP address scheme. ?
> 
> Thanksm 
> Ravi.
> 
> 
> On Wed, Apr 3, 2013 at 6:46 AM, Josh Petro  wrote:
> Thanks much to all who replied! Strategy seems to be key from what I'm 
> hearing here and elsewhere. 
> 
> On Tue, Apr 2, 2013 at 4:45 PM,  wrote:
> All testing after you finish the lab.  --ms
> 
>  
> 
> Michael Sears, CCIE(V)#38404
> 
> Cisco Certified Unfied Communications Computing Systems Specialist
> 
> Compucom Systems Western Region
> 
> Infrastructure Solutions Consulting
> 
> Office:   +1.720.344.6833
> 
> Mobile: +1.303.328.5590
> 
> Fax:+1.978.863.0740
> 
> 
> 
> “Designing and Implementing Cisco Unified Communications on Unified Computing 
> Systems”
> 
>  
> 
> From: Ramcharan Arya [mailto:ramcharan.a...@gmail.com] 
> Sent: Tuesday, April 02, 2013 2:44 PM
> To: Sears, Michael (msears)
> 
> 
> Cc: ccie_voice@onlinestudylist.com
> Subject: Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy
> 
>  
> 
> Hi Mike,
> 
> Thank you for sharing great information.
> 
> Can you share some detail about approach and sequence to follow like 
> Infrastructure, gateway configuration, QoS and SRST, Presence . Unity, UCCX 
> etc.
> 
> When did you do SRST testing in the middle or at the end of the lab.?
> 
> Please share your experience.
> 
>  
> 
> Thanks & Regards,
> Ramcharan Arya
> 
> CCIE # 28926 ( Routing & Switching)
> 
>  
> 
> On Tue, Apr 2, 2013 at 12:26 PM,  wrote:
> 
> It took me 4 attempts to pass the lab.  Actually the first three attempts 
> helped to develop a strategy for passing.  The proctor in RTP, David, thought 
> me something, don't look at a no pass as a failure but a as learning 
> experience.  After my third attempt I couldn't stand to see another "fail" on 
> the score report.  I took 45 days, doing two labs a day following the same 
> strategy.
> 
> If your typing skills are below 70 words/minute or less or you are hunt and 
> peck typist take a typing class "won't hurt" have to type fast.
> 
> Briefly read the entire lab and absorb as much as possible 5 to 10 minutes 
> maximum regarding CUCM and gateway, QoS, etc.
> 
> Perform all your switch and gateway configurations first including everything 
> so you don't have to revisit them.  Write all configuration for SW and 
> Gateways in notepad prior to putting into devices and same to desktop, leave 
> them there when leaving the lab.  Copy all the customization's you'll need 
> and put in notepad and put on desktop, i.e., media resources, dial-peer, 
> other customizations.  Don't type and memorize things you can obtain from 
> links copy from links and edit
> 
> 1.) Configure the SW first and take what configure you can from there and 
> move onto R1.
> 2.) Configure R1 and take configuration from there to R2 and edit and add 
> additional configuration.
> 3.) Configure R2 including SRST/GK/Dial-peers/MVA/everything.  Move 
> configure from R2 and R1 to R3 and edit.
> 4.) Configure R3/CUE/Presence/SRST using configuration from R1 and R2 
> that's reusable.
> 5.) Don't type the same thing twice.
> 5.) Now move to CUCM.  You should have a pretty good idea of what you 
> will need from reading lab.
> 6.) Open browser to CUCM Pub, Sub, Unity.  Add ntp and any required 
> customizations
> 7.) Configure CUCM moving from left to right, save phones for last.
> 8.) Configure UNITY and all voicemail customization
> 9.) Configure UCCX script and record prompts unless they are pre-recorded 
> for you.
> 10.)Configure Presence if you have it on your lab.
> 11.)Need at least three hours to test and validate.
> 12.)Ma

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[ie ravindra]

Is there any ways to adapt with IP address scheme. ?

Thanksm
Ravi.


On Wed, Apr 3, 2013 at 6:46 AM, Josh Petro  wrote:

> Thanks much to all who replied! Strategy seems to be key from what I'm
> hearing here and elsewhere.
>
> On Tue, Apr 2, 2013 at 4:45 PM,  wrote:
>
>>  All testing after you finish the lab.  --ms
>>
>> ** **
>>
>> Michael Sears, CCIE(V)#38404
>>
>> Cisco Certified Unfied Communications Computing Systems Specialist
>>
>> Compucom Systems Western Region
>>
>> Infrastructure Solutions Consulting
>>
>> Office:   +1.720.344.6833
>>
>> Mobile: +1.303.328.5590
>>
>> Fax:+1.978.863.0740
>>
>> *[image: 3-2-2013 3-02-38 PM]***
>>
>> “Designing and Implementing Cisco Unified Communications on Unified
>> Computing Systems”
>>
>> ** **
>>
>> *From:* Ramcharan Arya [mailto:ramcharan.a...@gmail.com]
>> *Sent:* Tuesday, April 02, 2013 2:44 PM
>> *To:* Sears, Michael (msears)
>>
>> *Cc:* ccie_voice@onlinestudylist.com
>> *Subject:* Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy
>>
>> ** **
>>
>> Hi Mike,
>>
>> Thank you for sharing great information.
>>
>> Can you share some detail about approach and sequence to follow like
>> Infrastructure, gateway configuration, QoS and SRST, Presence . Unity, UCCX
>> etc.
>>
>> When did you do SRST testing in the middle or at the end of the lab.?
>>
>> Please share your experience.
>>
>> ** **
>>
>> Thanks & Regards,
>> Ramcharan Arya
>>
>> CCIE # 28926 ( Routing & Switching)
>>
>> ** **
>>
>> On Tue, Apr 2, 2013 at 12:26 PM,  wrote:
>>
>> It took me 4 attempts to pass the lab.  Actually the first three attempts
>> helped to develop a strategy for passing.  The proctor in RTP, David,
>> thought me something, don't look at a no pass as a failure but a as
>> learning experience.  After my third attempt I couldn't stand to see
>> another "fail" on the score report.  I took 45 days, doing two labs a day
>> following the same strategy.
>>
>> If your typing skills are below 70 words/minute or less or you are hunt
>> and peck typist take a typing class "won't hurt" have to type fast.
>>
>> Briefly read the entire lab and absorb as much as possible 5 to 10
>> minutes maximum regarding CUCM and gateway, QoS, etc.
>>
>> Perform all your switch and gateway configurations first including
>> everything so you don't have to revisit them.  Write all configuration for
>> SW and Gateways in notepad prior to putting into devices and same to
>> desktop, leave them there when leaving the lab.  Copy all the
>> customization's you'll need and put in notepad and put on desktop, i.e.,
>> media resources, dial-peer, other customizations.  Don't type and memorize
>> things you can obtain from links copy from links and edit
>>
>> 1.) Configure the SW first and take what configure you can from there
>> and move onto R1.
>> 2.) Configure R1 and take configuration from there to R2 and edit and
>> add additional configuration.
>> 3.) Configure R2 including SRST/GK/Dial-peers/MVA/everything.  Move
>> configure from R2 and R1 to R3 and edit.
>> 4.) Configure R3/CUE/Presence/SRST using configuration from R1 and R2
>> that's reusable.
>> 5.) Don't type the same thing twice.
>> 5.) Now move to CUCM.  You should have a pretty good idea of what you
>> will need from reading lab.
>> 6.) Open browser to CUCM Pub, Sub, Unity.  Add ntp and any required
>> customizations
>> 7.) Configure CUCM moving from left to right, save phones for last.
>> 8.) Configure UNITY and all voicemail customization
>> 9.) Configure UCCX script and record prompts unless they are
>> pre-recorded for you.
>> 10.)Configure Presence if you have it on your lab.
>> 11.)Need at least three hours to test and validate.
>> 12.)Make every attempt to complete lab before lunch.
>> 13.)Feel good at lunch relax forget the lab
>> 14.)Get your score report that says "PASS".
>> 15.)Preform Troubleshooting as you are most comfortable with I saved
>> it for last.
>>
>> There was a guy walking down the street in NYC and he recognized a famous
>> pianist.  He stopped him and ask him "How do you get to Carnegie Hall.  The
>> pianist replied "Practice, Practice, 

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Josh Petro]

Thanks much to all who replied! Strategy seems to be key from what I'm
hearing here and elsewhere.

On Tue, Apr 2, 2013 at 4:45 PM,  wrote:

>  All testing after you finish the lab.  --ms
>
> ** **
>
> Michael Sears, CCIE(V)#38404
>
> Cisco Certified Unfied Communications Computing Systems Specialist
>
> Compucom Systems Western Region
>
> Infrastructure Solutions Consulting
>
> Office:   +1.720.344.6833
>
> Mobile: +1.303.328.5590
>
> Fax:+1.978.863.0740
>
> *[image: 3-2-2013 3-02-38 PM]***
>
> “Designing and Implementing Cisco Unified Communications on Unified
> Computing Systems”
>
> ** **
>
> *From:* Ramcharan Arya [mailto:ramcharan.a...@gmail.com]
> *Sent:* Tuesday, April 02, 2013 2:44 PM
> *To:* Sears, Michael (msears)
>
> *Cc:* ccie_voice@onlinestudylist.com
> *Subject:* Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy
>
> ** **
>
> Hi Mike,
>
> Thank you for sharing great information.
>
> Can you share some detail about approach and sequence to follow like
> Infrastructure, gateway configuration, QoS and SRST, Presence . Unity, UCCX
> etc.
>
> When did you do SRST testing in the middle or at the end of the lab.?
>
> Please share your experience.
>
> ** **
>
> Thanks & Regards,
> Ramcharan Arya
>
> CCIE # 28926 ( Routing & Switching)
>
> ** **
>
> On Tue, Apr 2, 2013 at 12:26 PM,  wrote:
>
> It took me 4 attempts to pass the lab.  Actually the first three attempts
> helped to develop a strategy for passing.  The proctor in RTP, David,
> thought me something, don't look at a no pass as a failure but a as
> learning experience.  After my third attempt I couldn't stand to see
> another "fail" on the score report.  I took 45 days, doing two labs a day
> following the same strategy.
>
> If your typing skills are below 70 words/minute or less or you are hunt
> and peck typist take a typing class "won't hurt" have to type fast.
>
> Briefly read the entire lab and absorb as much as possible 5 to 10 minutes
> maximum regarding CUCM and gateway, QoS, etc.
>
> Perform all your switch and gateway configurations first including
> everything so you don't have to revisit them.  Write all configuration for
> SW and Gateways in notepad prior to putting into devices and same to
> desktop, leave them there when leaving the lab.  Copy all the
> customization's you'll need and put in notepad and put on desktop, i.e.,
> media resources, dial-peer, other customizations.  Don't type and memorize
> things you can obtain from links copy from links and edit
>
> 1.) Configure the SW first and take what configure you can from there
> and move onto R1.
> 2.) Configure R1 and take configuration from there to R2 and edit and
> add additional configuration.
> 3.) Configure R2 including SRST/GK/Dial-peers/MVA/everything.  Move
> configure from R2 and R1 to R3 and edit.
> 4.) Configure R3/CUE/Presence/SRST using configuration from R1 and R2
> that's reusable.
> 5.) Don't type the same thing twice.
> 5.) Now move to CUCM.  You should have a pretty good idea of what you
> will need from reading lab.
> 6.) Open browser to CUCM Pub, Sub, Unity.  Add ntp and any required
> customizations
> 7.) Configure CUCM moving from left to right, save phones for last.
> 8.) Configure UNITY and all voicemail customization
> 9.) Configure UCCX script and record prompts unless they are
> pre-recorded for you.
> 10.)Configure Presence if you have it on your lab.
> 11.)Need at least three hours to test and validate.
> 12.)Make every attempt to complete lab before lunch.
> 13.)Feel good at lunch relax forget the lab
> 14.)Get your score report that says "PASS".
> 15.)Preform Troubleshooting as you are most comfortable with I saved
> it for last.
>
> There was a guy walking down the street in NYC and he recognized a famous
> pianist.  He stopped him and ask him "How do you get to Carnegie Hall.  The
> pianist replied "Practice, Practice, Practice".
>
> Michael Sears, CCIE(V)#38404
> Cisco Certified Unfied Communications Computing Systems Specialist
> E911 Specialist
> "Designing and Implementing Cisco Unified Communications on Unified
> Computing Systems"
>
>
>
> ___
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
> Are you a CCNP or CCIE and looking for a job? Check out
> www.PlatinumPlacement.com
>
> ** **
>
> ___
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
> Are you a CCNP or CCIE and looking for a job? Check out
> www.PlatinumPlacement.com
>
<>___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Michael.Sears]

All testing after you finish the lab.  --ms

Michael Sears, CCIE(V)#38404
Cisco Certified Unfied Communications Computing Systems Specialist
Compucom Systems Western Region
Infrastructure Solutions Consulting
Office:   +1.720.344.6833
Mobile: +1.303.328.5590
Fax:+1.978.863.0740
[3-2-2013 3-02-38 PM]
"Designing and Implementing Cisco Unified Communications on Unified Computing 
Systems"

From: Ramcharan Arya [mailto:ramcharan.a...@gmail.com]
Sent: Tuesday, April 02, 2013 2:44 PM
To: Sears, Michael (msears)
Cc: ccie_voice@onlinestudylist.com
Subject: Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

Hi Mike,
Thank you for sharing great information.

Can you share some detail about approach and sequence to follow like 
Infrastructure, gateway configuration, QoS and SRST, Presence . Unity, UCCX etc.
When did you do SRST testing in the middle or at the end of the lab.?
Please share your experience.

Thanks & Regards,
Ramcharan Arya
CCIE # 28926 ( Routing & Switching)

On Tue, Apr 2, 2013 at 12:26 PM, 
mailto:michael.se...@compucom.com>> wrote:
It took me 4 attempts to pass the lab.  Actually the first three attempts 
helped to develop a strategy for passing.  The proctor in RTP, David, thought 
me something, don't look at a no pass as a failure but a as learning 
experience.  After my third attempt I couldn't stand to see another "fail" on 
the score report.  I took 45 days, doing two labs a day following the same 
strategy.

If your typing skills are below 70 words/minute or less or you are hunt and 
peck typist take a typing class "won't hurt" have to type fast.

Briefly read the entire lab and absorb as much as possible 5 to 10 minutes 
maximum regarding CUCM and gateway, QoS, etc.

Perform all your switch and gateway configurations first including everything 
so you don't have to revisit them.  Write all configuration for SW and Gateways 
in notepad prior to putting into devices and same to desktop, leave them there 
when leaving the lab.  Copy all the customization's you'll need and put in 
notepad and put on desktop, i.e., media resources, dial-peer, other 
customizations.  Don't type and memorize things you can obtain from links copy 
from links and edit

1.) Configure the SW first and take what configure you can from there and 
move onto R1.
2.) Configure R1 and take configuration from there to R2 and edit and add 
additional configuration.
3.) Configure R2 including SRST/GK/Dial-peers/MVA/everything.  Move 
configure from R2 and R1 to R3 and edit.
4.) Configure R3/CUE/Presence/SRST using configuration from R1 and R2 
that's reusable.
5.) Don't type the same thing twice.
5.) Now move to CUCM.  You should have a pretty good idea of what you will 
need from reading lab.
6.) Open browser to CUCM Pub, Sub, Unity.  Add ntp and any required 
customizations
7.) Configure CUCM moving from left to right, save phones for last.
8.) Configure UNITY and all voicemail customization
9.) Configure UCCX script and record prompts unless they are pre-recorded 
for you.
10.)Configure Presence if you have it on your lab.
11.)Need at least three hours to test and validate.
12.)Make every attempt to complete lab before lunch.
13.)Feel good at lunch relax forget the lab
14.)Get your score report that says "PASS".
15.)Preform Troubleshooting as you are most comfortable with I saved it for 
last.

There was a guy walking down the street in NYC and he recognized a famous 
pianist.  He stopped him and ask him "How do you get to Carnegie Hall.  The 
pianist replied "Practice, Practice, Practice".

Michael Sears, CCIE(V)#38404
Cisco Certified Unfied Communications Computing Systems Specialist
E911 Specialist
"Designing and Implementing Cisco Unified Communications on Unified Computing 
Systems"


___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com<http://www.ipexpert.com>

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com<http://www.PlatinumPlacement.com>

<>___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Ramcharan Arya]

Hi Mike,

Thank you for sharing great information.

Can you share some detail about approach and sequence to follow like
Infrastructure, gateway configuration, QoS and SRST, Presence . Unity, UCCX
etc.

When did you do SRST testing in the middle or at the end of the lab.?

Please share your experience.

Thanks & Regards,
Ramcharan Arya
CCIE # 28926 ( Routing & Switching)



On Tue, Apr 2, 2013 at 12:26 PM,  wrote:

> It took me 4 attempts to pass the lab.  Actually the first three attempts
> helped to develop a strategy for passing.  The proctor in RTP, David,
> thought me something, don't look at a no pass as a failure but a as
> learning experience.  After my third attempt I couldn't stand to see
> another "fail" on the score report.  I took 45 days, doing two labs a day
> following the same strategy.
>
> If your typing skills are below 70 words/minute or less or you are hunt
> and peck typist take a typing class "won't hurt" have to type fast.
>
> Briefly read the entire lab and absorb as much as possible 5 to 10 minutes
> maximum regarding CUCM and gateway, QoS, etc.
>
> Perform all your switch and gateway configurations first including
> everything so you don't have to revisit them.  Write all configuration for
> SW and Gateways in notepad prior to putting into devices and same to
> desktop, leave them there when leaving the lab.  Copy all the
> customization's you'll need and put in notepad and put on desktop, i.e.,
> media resources, dial-peer, other customizations.  Don't type and memorize
> things you can obtain from links copy from links and edit
>
> 1.) Configure the SW first and take what configure you can from there
> and move onto R1.
> 2.) Configure R1 and take configuration from there to R2 and edit and
> add additional configuration.
> 3.) Configure R2 including SRST/GK/Dial-peers/MVA/everything.  Move
> configure from R2 and R1 to R3 and edit.
> 4.) Configure R3/CUE/Presence/SRST using configuration from R1 and R2
> that's reusable.
> 5.) Don't type the same thing twice.
> 5.) Now move to CUCM.  You should have a pretty good idea of what you
> will need from reading lab.
> 6.) Open browser to CUCM Pub, Sub, Unity.  Add ntp and any required
> customizations
> 7.) Configure CUCM moving from left to right, save phones for last.
> 8.) Configure UNITY and all voicemail customization
> 9.) Configure UCCX script and record prompts unless they are
> pre-recorded for you.
> 10.)Configure Presence if you have it on your lab.
> 11.)Need at least three hours to test and validate.
> 12.)Make every attempt to complete lab before lunch.
> 13.)Feel good at lunch relax forget the lab
> 14.)Get your score report that says "PASS".
> 15.)Preform Troubleshooting as you are most comfortable with I saved
> it for last.
>
> There was a guy walking down the street in NYC and he recognized a famous
> pianist.  He stopped him and ask him "How do you get to Carnegie Hall.  The
> pianist replied "Practice, Practice, Practice".
>
> Michael Sears, CCIE(V)#38404
> Cisco Certified Unfied Communications Computing Systems Specialist
> E911 Specialist
> "Designing and Implementing Cisco Unified Communications on Unified
> Computing Systems"
>
>
> ___
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
> Are you a CCNP or CCIE and looking for a job? Check out
> www.PlatinumPlacement.com
>
___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Michael.Sears]

It took me 4 attempts to pass the lab.  Actually the first three attempts 
helped to develop a strategy for passing.  The proctor in RTP, David, thought 
me something, don't look at a no pass as a failure but a as learning 
experience.  After my third attempt I couldn't stand to see another "fail" on 
the score report.  I took 45 days, doing two labs a day following the same 
strategy. 

If your typing skills are below 70 words/minute or less or you are hunt and 
peck typist take a typing class "won't hurt" have to type fast.

Briefly read the entire lab and absorb as much as possible 5 to 10 minutes 
maximum regarding CUCM and gateway, QoS, etc.

Perform all your switch and gateway configurations first including everything 
so you don't have to revisit them.  Write all configuration for SW and Gateways 
in notepad prior to putting into devices and same to desktop, leave them there 
when leaving the lab.  Copy all the customization's you'll need and put in 
notepad and put on desktop, i.e., media resources, dial-peer, other 
customizations.  Don't type and memorize things you can obtain from links copy 
from links and edit

1.) Configure the SW first and take what configure you can from there and 
move onto R1.
2.) Configure R1 and take configuration from there to R2 and edit and add 
additional configuration.
3.) Configure R2 including SRST/GK/Dial-peers/MVA/everything.  Move 
configure from R2 and R1 to R3 and edit.
4.) Configure R3/CUE/Presence/SRST using configuration from R1 and R2 
that's reusable.
5.) Don't type the same thing twice.
5.) Now move to CUCM.  You should have a pretty good idea of what you will 
need from reading lab.  
6.) Open browser to CUCM Pub, Sub, Unity.  Add ntp and any required 
customizations 
7.) Configure CUCM moving from left to right, save phones for last.
8.) Configure UNITY and all voicemail customization
9.) Configure UCCX script and record prompts unless they are pre-recorded 
for you.
10.)Configure Presence if you have it on your lab.
11.)Need at least three hours to test and validate.
12.)Make every attempt to complete lab before lunch.
13.)Feel good at lunch relax forget the lab
14.)Get your score report that says "PASS".
15.)Preform Troubleshooting as you are most comfortable with I saved it for 
last.

There was a guy walking down the street in NYC and he recognized a famous 
pianist.  He stopped him and ask him "How do you get to Carnegie Hall.  The 
pianist replied "Practice, Practice, Practice".

Michael Sears, CCIE(V)#38404
Cisco Certified Unfied Communications Computing Systems Specialist
E911 Specialist
"Designing and Implementing Cisco Unified Communications on Unified Computing 
Systems"


___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Bill]

Look for CCIE VOICE Alchemy by Kevin Wallace it would be very helpful and I 
took this with ipexpert last year but don't see it now.

Sent from my iPad

On Apr 2, 2013, at 6:06 AM, Josh Petro  wrote:

> Hi everyone
> Im just now near the end of lab 5 and Im going to attempt to do a full day of 
> labs 1-5 to check my speed and memory on past labs. 
> My question to the group is where the device based approach came from and 
> where I can find more info on it. Is this something they teach in the week 
> boot camp, or something Vik said in a VoD I missed :).
> My other question is that in reading everyone else's replies, it seems like 
> notepad is the place to get your speed. I can see that helping and I've 
> started down that path, but how can it help in the lab (particularly in the 
> IOS config if you get a lab like IPExpert had with an MGCP GW, one CME and a 
> H323 gateway?). I can see notepad being beneficial with css and partition 
> building for sure. I can also see things like SRST, voice class codec 
> configs, etc, but does it help that much? 
> Im not trying to say you're all wrong by any means, Im just trying to figure 
> out the thought process. Sorry for being long winded!
> Josh
> 
> On Mar 28, 2013 3:49 PM, "Barrera, Hugo"  wrote:
>> What has been the turning corner for me regarding speed is don’t “run around 
>> the tree”. What I mean by this is when you come across something in the lab 
>> try to plan ahead and pre-configure as much as you can.
>> 
>>  
>> 
>> For example when you go thru call routing in cucm don’t just set up 
>> partitions and css’s…pre-build your RP’s, RL’s, RG’s, AAR grp’s, calling 
>> party TP’s, TP’s…
>> 
>>  
>> 
>> Really try to nail things and pre-config when you hit any section in the 
>> lab. What has also helped me is drilling notepad for IOS configurations as 
>> well.
>> 
>>  
>> 
>> HTH
>> 
>>  
>> 
>> Regards,
>> 
>> Hugo
>> 
>>  
>> 
>> From: ccie_voice-boun...@onlinestudylist.com 
>> [mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of CCIEing
>> Sent: Thursday, March 28, 2013 12:44 AM
>> To: Jamie Parr (jamparr)
>> Cc: ccie_voice@onlinestudylist.com
>> Subject: Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy
>> 
>>  
>> 
>> Hi Jamie,
>> 
>>  
>> 
>> Would you please explain this more :
>> 
>>  
>> 
>> "  You have to setup most devices with little or no prior configuration, 
>> there are things that cannot change. Know these things and practice them 
>> over and over so you do not have to think about them "
>> 
>>  
>> 
>> Thanks in advance 
>> 
>>  
>> 
>>  
>> 
>>  
>> 
>> On Wed, Mar 27, 2013 at 9:00 PM, Jamie Parr (jamparr)  
>> wrote:
>> 
>> First attempt I was very slow – did not use the device based approach, did 
>> not finish all tasks. Second I was much faster – using the device based 
>> approach, finished with 3 hours to test. Third attempt I finished with more 
>> than 3 hours to test and pick up the issues – Passed
>> 
>>  
>> 
>> My advice:
>> 
>> · I found the more I practiced the faster I got, practice practice 
>> practice
>> 
>> · Use notepad to write all your device configs first, you can copy 
>> and paste large sections of config saving a lot of time
>> 
>> · Do not be so strict to the device based approach, use it as a base 
>> and create your own hybrid
>> 
>> · You have to setup most devices with little or no prior 
>> configuration, there are things that cannot change. Know these things and 
>> practice them over and over so you do not have to think about them
>> 
>> · Persevere, it’s not easy and it sucks most of the time but you 
>> will get there
>> 
>>  
>> 
>> Hope this helps
>> 
>>  
>> 
>> Jamie Parr
>> 
>> CCIE #38633 (voice)
>> Engineer - IT
>> jamp...@cisco.com
>> Phone: +44 20 8824 2641
>> Mobile: +44 7590622049
>> 
>>  
>> 
>> From: ccie_voice-boun...@onlinestudylist.com 
>> [mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Dane Warner
>> Sent: 26 March 2013 23:41
>> To: ccie_voice@onlinestudylist.com
>> Subject: [OSL | CCIE_Voice] Lab Exam Speed Strategy
>> 
>>  
>> 
>> To All,
>> 
>>  
>> 
>> I took my second attempt on Monday, March 25 and did not pass.
>> 
>> I was ho

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Kamran Ahsanullah]

as far as the device based approach, here it is
http://ciscovoiceguru.com/1878/device-based-lab-strategy/

use notepad to practise your speed even without access to routers, 5
minutes here or there, it all helps.



On 2 April 2013 14:06,   wrote:
> Send CCIE_Voice mailing list submissions to
> ccie_voice@onlinestudylist.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://onlinestudylist.com/mailman/listinfo/ccie_voice
> or, via email, send a message with subject or body 'help' to
> ccie_voice-requ...@onlinestudylist.com
>
> You can reach the person managing the list at
> ccie_voice-ow...@onlinestudylist.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of CCIE_Voice digest..."
>
>
> Today's Topics:
>
>1. Re: (no subject) (Jeff McHugh)
>2. HQ as ntp master Required (Vikky Kumar)
>3. Re: Lab Exam Speed Strategy (Josh Petro)
>
>
> --
>
> Message: 1
> Date: Tue, 2 Apr 2013 02:00:52 -0700 (PDT)
> From: Jeff McHugh 
> To: dmazzucco , cyuen ,  james
> amenta ,"GA Viner, Jonathan 
> Lawrenceville"
> ,  ccie voice
> ,   Bryan Totten 
> ,
> Pamela Savago 
> Subject: Re: [OSL | CCIE_Voice] (no subject)
> Message-ID:
> <1364893252.98140.yahoomail...@web181005.mail.ne1.yahoo.com>
> Content-Type: text/plain; charset="us-ascii"
>
> http://www.willohboutique.com/includes/likeit.php?xtxlvdorf722znehzv
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ***
> If you took all the students that fell asleep in class and laid them end to 
> end, they'd be a lot more comfortable.
> -- next part --
> An HTML attachment was scrubbed...
> URL: 
>
> --
>
> Message: 2
> Date: Tue, 2 Apr 2013 13:47:32 +0300
> From: Vikky Kumar 
> To: "ccie_voice@onlinestudylist.com" 
> Subject: [OSL | CCIE_Voice] HQ as ntp master Required
> Message-ID:
> 
> Content-Type: text/plain; charset="iso-8859-1"
>
> hi,
> If hq-router is ntp reference for branches AND hq router has some external
> ntp reference.
>
> should you configure ntp master on HQ router
>
> Thanks,
>
> Vikky
> -- next part --
> An HTML attachment was scrubbed...
> URL: 
>
> --
>
> Message: 3
> Date: Tue, 2 Apr 2013 07:06:56 -0400
> From: Josh Petro 
> To: "Barrera, Hugo" 
> Cc: "ccie_voice@onlinestudylist.com" 
> Subject: Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy
> Message-ID:
> 
> Content-Type: text/plain; charset="windows-1252"
>
> Hi everyone
> Im just now near the end of lab 5 and Im going to attempt to do a full day
> of labs 1-5 to check my speed and memory on past labs.
> My question to the group is where the device based approach came from and
> where I can find more info on it. Is this something they teach in the week
> boot camp, or something Vik said in a VoD I missed :).
> My other question is that in reading everyone else's replies, it seems like
> notepad is the place to get your speed. I can see that helping and I've
> started down that path, but how can it help in the lab (particularly in the
> IOS config if you get a lab like IPExpert had with an MGCP GW, one CME and
> a H323 gateway?). I can see notepad being beneficial with css and partition
> building for sure. I can also see things like SRST, voice class codec
> configs, etc, but does it help that much?
> Im not trying to say you're all wrong by any means, Im just trying to
> figure out the thought process. Sorry for being long winded!
> Josh
> On Mar 28, 2013 3:49 PM, "Barrera, Hugo"  wrote:
>
>>  What has been the turning corner for me regarding speed is don?t ?run
>> around the tree?. What I mean by this is when you come across something in
>> the lab try to plan ahead and pre-configure as much as you can. 
>>
>> ** **
>&g

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Josh Petro]

Hi everyone
Im just now near the end of lab 5 and Im going to attempt to do a full day
of labs 1-5 to check my speed and memory on past labs.
My question to the group is where the device based approach came from and
where I can find more info on it. Is this something they teach in the week
boot camp, or something Vik said in a VoD I missed :).
My other question is that in reading everyone else's replies, it seems like
notepad is the place to get your speed. I can see that helping and I've
started down that path, but how can it help in the lab (particularly in the
IOS config if you get a lab like IPExpert had with an MGCP GW, one CME and
a H323 gateway?). I can see notepad being beneficial with css and partition
building for sure. I can also see things like SRST, voice class codec
configs, etc, but does it help that much?
Im not trying to say you're all wrong by any means, Im just trying to
figure out the thought process. Sorry for being long winded!
Josh
On Mar 28, 2013 3:49 PM, "Barrera, Hugo"  wrote:

>  What has been the turning corner for me regarding speed is don’t “run
> around the tree”. What I mean by this is when you come across something in
> the lab try to plan ahead and pre-configure as much as you can. 
>
> ** **
>
> For example when you go thru call routing in cucm don’t just set up
> partitions and css’s…pre-build your RP’s, RL’s, RG’s, AAR grp’s, calling
> party TP’s, TP’s…
>
> ** **
>
> Really try to nail things and pre-config when you hit any section in the
> lab. What has also helped me is drilling notepad for IOS configurations as
> well. 
>
> ** **
>
> HTH 
>
> ** **
>
> *Regards,***
>
> *Hugo *
>
> ** **
>
> *From:* ccie_voice-boun...@onlinestudylist.com [mailto:
> ccie_voice-boun...@onlinestudylist.com] *On Behalf Of *CCIEing
> *Sent:* Thursday, March 28, 2013 12:44 AM
> *To:* Jamie Parr (jamparr)
> *Cc:* ccie_voice@onlinestudylist.com
> *Subject:* Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy
>
> ** **
>
> Hi Jamie,
>
> ** **
>
> Would you please explain this more :
>
> ** **
>
> "  *You have to setup most devices with little or no prior configuration,
> there are things that cannot change. Know these things and practice them
> over and over so you do not have to think about them* "
>
> ** **
>
> Thanks in advance 
>
> ** **
>
> ** **
>
> ** **
>
> On Wed, Mar 27, 2013 at 9:00 PM, Jamie Parr (jamparr) 
> wrote:
>
> First attempt I was very slow – did not use the device based approach, did
> not finish all tasks. Second I was much faster – using the device based
> approach, finished with 3 hours to test. Third attempt I finished with more
> than 3 hours to test and pick up the issues – Passed
>
>  
>
> My advice:
>
> · I found the more I practiced the faster I got, practice
> practice practice
>
> · Use notepad to write all your device configs first, you can
> copy and paste large sections of config saving a lot of time
>
> · Do not be so strict to the device based approach, use it as a
> base and create your own hybrid
>
> · You have to setup most devices with little or no prior
> configuration, there are things that cannot change. Know these things and
> practice them over and over so you do not have to think about them
>
> · Persevere, it’s not easy and it sucks most of the time but you
> will get there
>
>  
>
> Hope this helps
>
>  
>
> *Jamie Parr*
>
> CCIE #38633 (voice)
> Engineer - IT
> jamp...@cisco.com
> Phone: *+44 20 8824 2641*
> Mobile: *+44 7590622049*
>
>  
>
> *From:* ccie_voice-boun...@onlinestudylist.com [mailto:
> ccie_voice-boun...@onlinestudylist.com] *On Behalf Of *Dane Warner
> *Sent:* 26 March 2013 23:41
> *To:* ccie_voice@onlinestudylist.com
> *Subject:* [OSL | CCIE_Voice] Lab Exam Speed Strategy
>
>  
>
> To All,
>
>  
>
> I took my second attempt on Monday, March 25 and did not pass.
>
> I was hoping for some insight on concrete suggestions to get faster. 
>
> I didn’t get hung up on any one task, I seemed to keep moving forward and
> tried to type as fast as I could, using CLI shortcuts, etc.
>
> I used the device-based methodology and I feel pretty confident of my
> technical knowledge.
>
> Yet I didn’t even get to many tasks at all, I would have needed another
> 2-3 hours to complete all tasks.
>
> I hear of candidates completing all tasks in 6-7 hours, which means I
> would need to become twice as fast as m

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Barrera, Hugo]

What has been the turning corner for me regarding speed is don't "run around 
the tree". What I mean by this is when you come across something in the lab try 
to plan ahead and pre-configure as much as you can.

For example when you go thru call routing in cucm don't just set up partitions 
and css's...pre-build your RP's, RL's, RG's, AAR grp's, calling party TP's, 
TP's...

Really try to nail things and pre-config when you hit any section in the lab. 
What has also helped me is drilling notepad for IOS configurations as well.

HTH

Regards,
Hugo

From: ccie_voice-boun...@onlinestudylist.com 
[mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of CCIEing
Sent: Thursday, March 28, 2013 12:44 AM
To: Jamie Parr (jamparr)
Cc: ccie_voice@onlinestudylist.com
Subject: Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

Hi Jamie,

Would you please explain this more :

"  You have to setup most devices with little or no prior configuration, there 
are things that cannot change. Know these things and practice them over and 
over so you do not have to think about them "

Thanks in advance



On Wed, Mar 27, 2013 at 9:00 PM, Jamie Parr (jamparr) 
mailto:jamp...@cisco.com>> wrote:
First attempt I was very slow - did not use the device based approach, did not 
finish all tasks. Second I was much faster - using the device based approach, 
finished with 3 hours to test. Third attempt I finished with more than 3 hours 
to test and pick up the issues - Passed

My advice:

* I found the more I practiced the faster I got, practice practice 
practice

* Use notepad to write all your device configs first, you can copy and 
paste large sections of config saving a lot of time

* Do not be so strict to the device based approach, use it as a base 
and create your own hybrid

* You have to setup most devices with little or no prior configuration, 
there are things that cannot change. Know these things and practice them over 
and over so you do not have to think about them

* Persevere, it's not easy and it sucks most of the time but you will 
get there

Hope this helps

Jamie Parr
CCIE #38633 (voice)
Engineer - IT
jamp...@cisco.com<mailto:jamp...@cisco.com>
Phone: +44 20 8824 2641
Mobile: +44 7590622049

From: 
ccie_voice-boun...@onlinestudylist.com<mailto:ccie_voice-boun...@onlinestudylist.com>
 
[mailto:ccie_voice-boun...@onlinestudylist.com<mailto:ccie_voice-boun...@onlinestudylist.com>]
 On Behalf Of Dane Warner
Sent: 26 March 2013 23:41
To: ccie_voice@onlinestudylist.com<mailto:ccie_voice@onlinestudylist.com>
Subject: [OSL | CCIE_Voice] Lab Exam Speed Strategy

To All,

I took my second attempt on Monday, March 25 and did not pass.
I was hoping for some insight on concrete suggestions to get faster.
I didn't get hung up on any one task, I seemed to keep moving forward and tried 
to type as fast as I could, using CLI shortcuts, etc.
I used the device-based methodology and I feel pretty confident of my technical 
knowledge.
Yet I didn't even get to many tasks at all, I would have needed another 2-3 
hours to complete all tasks.
I hear of candidates completing all tasks in 6-7 hours, which means I would 
need to become twice as fast as my last attempt.
It almost sounds insurmountable. Do I need to take typing classes?

Any recommendations that don't break the NDA would be greatly appreciated.

Regards,

Dane Warner, CCVP
Sr. Network Engineer
Epoch Universal, Inc.
(909)226-0755
dwar...@epochuniversal.com<mailto:dwar...@epochuniversal.com>
[Epoch_Logo_Smaller_Transparent]

___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com<http://www.ipexpert.com>

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com<http://www.PlatinumPlacement.com>

<>___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[CCIEing]

Hi Jamie,

Would you please explain this more :

"  ***You have to setup most devices with little or no prior configuration,
there are things that cannot change. Know these things and practice them
over and over so you do not have to think about them* "

Thanks in advance




On Wed, Mar 27, 2013 at 9:00 PM, Jamie Parr (jamparr) wrote:

>  First attempt I was very slow – did not use the device based approach,
> did not finish all tasks. Second I was much faster – using the device based
> approach, finished with 3 hours to test. Third attempt I finished with more
> than 3 hours to test and pick up the issues – Passed
>
> ** **
>
> My advice:
>
> **· **I found the more I practiced the faster I got, practice
> practice practice
>
> **· **Use notepad to write all your device configs first, you can
> copy and paste large sections of config saving a lot of time
>
> **· **Do not be so strict to the device based approach, use it as
> a base and create your own hybrid
>
> **· **You have to setup most devices with little or no prior
> configuration, there are things that cannot change. Know these things and
> practice them over and over so you do not have to think about them
>
> **· **Persevere, it’s not easy and it sucks most of the time but
> you will get there
>
> ** **
>
> Hope this helps
>
> ** **
>
> *Jamie Parr*
>
> CCIE #38633 (voice)
> Engineer - IT
> jamp...@cisco.com
> Phone: *+44 20 8824 2641*
> Mobile: *+44 7590622049*
>
> ** **
>
> *From:* ccie_voice-boun...@onlinestudylist.com [mailto:
> ccie_voice-boun...@onlinestudylist.com] *On Behalf Of *Dane Warner
> *Sent:* 26 March 2013 23:41
> *To:* ccie_voice@onlinestudylist.com
> *Subject:* [OSL | CCIE_Voice] Lab Exam Speed Strategy
>
> ** **
>
> To All,
>
> ** **
>
> I took my second attempt on Monday, March 25 and did not pass.
>
> I was hoping for some insight on concrete suggestions to get faster. 
>
> I didn’t get hung up on any one task, I seemed to keep moving forward and
> tried to type as fast as I could, using CLI shortcuts, etc.
>
> I used the device-based methodology and I feel pretty confident of my
> technical knowledge.
>
> Yet I didn’t even get to many tasks at all, I would have needed another
> 2-3 hours to complete all tasks.
>
> I hear of candidates completing all tasks in 6-7 hours, which means I
> would need to become twice as fast as my last attempt.
>
> It almost sounds insurmountable. Do I need to take typing classes?
>
> ** **
>
> Any recommendations that don’t break the NDA would be greatly appreciated.
> 
>
> ** **
>
> Regards,
>
> ** **
>
> *Dane Warner, CCVP*
>
> *Sr. Network Engineer*
>
> *Epoch Universal, Inc.*
>
> *(909)226-0755*
>
> *dwar...@epochuniversal.com  *
>
> *[image: Epoch_Logo_Smaller_Transparent]*
>
> ___
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
> Are you a CCNP or CCIE and looking for a job? Check out
> www.PlatinumPlacement.com
>
<>___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Jamie Parr (jamparr)]

First attempt I was very slow - did not use the device based approach, did not 
finish all tasks. Second I was much faster - using the device based approach, 
finished with 3 hours to test. Third attempt I finished with more than 3 hours 
to test and pick up the issues - Passed

My advice:

* I found the more I practiced the faster I got, practice practice 
practice

* Use notepad to write all your device configs first, you can copy and 
paste large sections of config saving a lot of time

* Do not be so strict to the device based approach, use it as a base 
and create your own hybrid

* You have to setup most devices with little or no prior configuration, 
there are things that cannot change. Know these things and practice them over 
and over so you do not have to think about them

* Persevere, it's not easy and it sucks most of the time but you will 
get there

Hope this helps

Jamie Parr
CCIE #38633 (voice)
Engineer - IT
jamp...@cisco.com<mailto:jamp...@cisco.com>
Phone: +44 20 8824 2641
Mobile: +44 7590622049

From: ccie_voice-boun...@onlinestudylist.com 
[mailto:ccie_voice-boun...@onlinestudylist.com] On Behalf Of Dane Warner
Sent: 26 March 2013 23:41
To: ccie_voice@onlinestudylist.com
Subject: [OSL | CCIE_Voice] Lab Exam Speed Strategy

To All,

I took my second attempt on Monday, March 25 and did not pass.
I was hoping for some insight on concrete suggestions to get faster.
I didn't get hung up on any one task, I seemed to keep moving forward and tried 
to type as fast as I could, using CLI shortcuts, etc.
I used the device-based methodology and I feel pretty confident of my technical 
knowledge.
Yet I didn't even get to many tasks at all, I would have needed another 2-3 
hours to complete all tasks.
I hear of candidates completing all tasks in 6-7 hours, which means I would 
need to become twice as fast as my last attempt.
It almost sounds insurmountable. Do I need to take typing classes?

Any recommendations that don't break the NDA would be greatly appreciated.

Regards,

Dane Warner, CCVP
Sr. Network Engineer
Epoch Universal, Inc.
(909)226-0755
dwar...@epochuniversal.com<mailto:dwar...@epochuniversal.com>
[Epoch_Logo_Smaller_Transparent]
<>___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[chase mergenthal]

When I have lab time on weekends, I go through each section and makes notes of 
the start and end time.
Looking at my times from about 10 months ago, its a big difference...

-Chase Mergenthal
--
If winners never quit and quitters never win, then who coined the phrase, "Quit 
while you’re still ahead."?



 

Date: Tue, 26 Mar 2013 22:39:04 -0500
From: niels...@gmail.com
To: amccar...@cciequest.com
CC: ccie_voice@onlinestudylist.com
Subject: Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

I would definitely recommend practicing in notepad too.

As you figure what you have to do for each device, create separate notepads for 
each device. Then you have it all there. I am starting again with my studies 
and am working on my speed. I can have HQ done in less than 5 minutes. Then it 
is just copy and paste.


Even create a notepad for all of your partitions in CUCM.

"J"

On Tue, Mar 26, 2013 at 7:45 PM, Amp  wrote:

Hey Dane,In my humble opinion one of the things that can help with speed is 
practicing in notepad and not thinking about it. 

Amp

Sent from an awesome iPad!
On Mar 26, 2013, at 7:40 PM, Dane Warner  wrote:


To All,
 I took my second attempt on Monday, March 25 and did not pass.
I was hoping for some insight on concrete suggestions to get faster. 
I didn’t get hung up on any one task, I seemed to keep moving forward and tried 
to type as fast as I could, using CLI shortcuts, etc.
I used the device-based methodology and I feel pretty confident of my technical 
knowledge.
Yet I didn’t even get to many tasks at all, I would have needed another 2-3 
hours to complete all tasks.
I hear of candidates completing all tasks in 6-7 hours, which means I would 
need to become twice as fast as my last attempt.
It almost sounds insurmountable. Do I need to take typing classes?
 Any recommendations that don’t break the NDA would be greatly appreciated.
 Regards,
 Dane Warner, CCVP
Sr. Network EngineerEpoch Universal, Inc.
(909)226-0755
dwar...@epochuniversal.com  

___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com


Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com
___


For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com



Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com



___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com ___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[nielsenj]

I would definitely recommend practicing in notepad too.

As you figure what you have to do for each device, create separate notepads
for each device. Then you have it all there. I am starting again with my
studies and am working on my speed. I can have HQ done in less than 5
minutes. Then it is just copy and paste.

Even create a notepad for all of your partitions in CUCM.

"J"

On Tue, Mar 26, 2013 at 7:45 PM, Amp  wrote:

> Hey Dane,
> In my humble opinion one of the things that can help with speed is
> practicing in notepad and not thinking about it.
>
> Amp
>
> Sent from an awesome iPad!
>
> On Mar 26, 2013, at 7:40 PM, Dane Warner 
> wrote:
>
> To All,
>
> ** **
>
> I took my second attempt on Monday, March 25 and did not pass.
>
> I was hoping for some insight on concrete suggestions to get faster. 
>
> I didn’t get hung up on any one task, I seemed to keep moving forward and
> tried to type as fast as I could, using CLI shortcuts, etc.
>
> I used the device-based methodology and I feel pretty confident of my
> technical knowledge.
>
> Yet I didn’t even get to many tasks at all, I would have needed another
> 2-3 hours to complete all tasks.
>
> I hear of candidates completing all tasks in 6-7 hours, which means I
> would need to become twice as fast as my last attempt.
>
> It almost sounds insurmountable. Do I need to take typing classes?
>
> ** **
>
> Any recommendations that don’t break the NDA would be greatly appreciated.
> 
>
> ** **
>
> Regards,
>
> ** **
>
> *Dane Warner, CCVP*
>
> *Sr. Network Engineer*
>
> *Epoch Universal, Inc.*
>
> *(909)226-0755*
>
> *dwar...@epochuniversal.com  *
>
> **
>
> ___
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
> Are you a CCNP or CCIE and looking for a job? Check out
> www.PlatinumPlacement.com
>
>
> ___
> For more information regarding industry leading CCIE Lab training, please
> visit www.ipexpert.com
>
> Are you a CCNP or CCIE and looking for a job? Check out
> www.PlatinumPlacement.com
>
___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Re: [OSL | CCIE_Voice] Lab Exam Speed Strategy

[Amp]

Hey Dane,
In my humble opinion one of the things that can help with speed is practicing 
in notepad and not thinking about it. 

Amp

Sent from an awesome iPad!

On Mar 26, 2013, at 7:40 PM, Dane Warner  wrote:

> To All,
>  
> I took my second attempt on Monday, March 25 and did not pass.
> I was hoping for some insight on concrete suggestions to get faster.
> I didn’t get hung up on any one task, I seemed to keep moving forward and 
> tried to type as fast as I could, using CLI shortcuts, etc.
> I used the device-based methodology and I feel pretty confident of my 
> technical knowledge.
> Yet I didn’t even get to many tasks at all, I would have needed another 2-3 
> hours to complete all tasks.
> I hear of candidates completing all tasks in 6-7 hours, which means I would 
> need to become twice as fast as my last attempt.
> It almost sounds insurmountable. Do I need to take typing classes?
>  
> Any recommendations that don’t break the NDA would be greatly appreciated.
>  
> Regards,
>  
> Dane Warner, CCVP
> Sr. Network Engineer
> Epoch Universal, Inc.
> (909)226-0755
> dwar...@epochuniversal.com 
> 
> ___
> For more information regarding industry leading CCIE Lab training, please 
> visit www.ipexpert.com
> 
> Are you a CCNP or CCIE and looking for a job? Check out 
> www.PlatinumPlacement.com
___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

[OSL | CCIE_Voice] Lab Exam Speed Strategy

[Dane Warner]

To All,

I took my second attempt on Monday, March 25 and did not pass.
I was hoping for some insight on concrete suggestions to get faster.
I didn't get hung up on any one task, I seemed to keep moving forward and tried 
to type as fast as I could, using CLI shortcuts, etc.
I used the device-based methodology and I feel pretty confident of my technical 
knowledge.
Yet I didn't even get to many tasks at all, I would have needed another 2-3 
hours to complete all tasks.
I hear of candidates completing all tasks in 6-7 hours, which means I would 
need to become twice as fast as my last attempt.
It almost sounds insurmountable. Do I need to take typing classes?

Any recommendations that don't break the NDA would be greatly appreciated.

Regards,

Dane Warner, CCVP
Sr. Network Engineer
Epoch Universal, Inc.
(909)226-0755
dwar...@epochuniversal.com
[cid:image001.png@01CE2A3E.DCEEA790]
<>___
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com