From: Gupta, Gopal (NWCC) (gopal.gupta@hp.com)
Date: Mon Jan 28 2008 - 19:21:51 ARST
Agreed
-----Original Message-----
From: James Wilson [mailto:netsurf@sersol.com]
Sent: Tuesday, January 29, 2008 02:35
To: Gupta, Gopal (NWCC); Darby Weaver; Bill Burns; Monica Belluci; Cisco
certification
Subject: RE: CCIE LAB - Troubleshooting
Actually I didn't think they were out to get us - I just took it as part
of the test; in the real world things break, sometimes team members make
changes you don't know about etc. Whether or not they did change it I
found that specific problem and fixed it. I didn't think twice about
it. It wasn't about blame - it just really looked that way. I missed
the lab because of another problem and running out of time; that glitch
didn't affect the lab either way. Personally I would consider it fair
game if they did make the change. Troubleshooting unexpected problems
is part of the job, right?
-- James D. Wilson Sr. Network/Security Engineer "non sunt multiplicanda entia praeter necessitatem" William of Ockham (1285-1347/49)-----Original Message----- From: Gupta, Gopal (NWCC) [mailto:gopal.gupta@hp.com] Sent: Monday, January 28, 2008 12:56 PM To: Darby Weaver; James Wilson; Bill Burns; Monica Belluci; Cisco certification Subject: RE: CCIE LAB - Troubleshooting
What I have heard from others and has happened to me is proctor goes with the candidates for lunch and comes back with them, so , if this is the case for every lab location, then I don't think the that any changes can be made by anyone at the time of lunch. But I personally felt that whenever my routes didn't show up in the routing table in the real lab, I always used to think whether proctor has done something wrong or is it my own fault, so this way we have to make ourself 100% sure that we have done right then start troubleshooting at other points whether proctor has done something ????
-----Original Message----- From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Darby Weaver Sent: Monday, January 28, 2008 07:46 To: James Wilson; Bill Burns; 'Monica Belluci'; 'Cisco certification' Subject: RE: CCIE LAB - Troubleshooting Importance: Low
Well...
Been to 4 labs so far and I think I can safely say "I failed on my own..." I did not require the assistance of the proctors to manage this task.
Now maybe others think the proctors hate them, but it seems to me that Howard (proctor 3x of my 4 attempts) is quite engaging and entertaining - so I don't think he hates us.
The troubleshooting in the lab either would be clearly stated or it is self-induced by candidates who are nervous, tired, ill-prepared or a combination of all three.
But we've heard this before that some believe the proctors are out to get them.
For VLAN assignments to disappear, I'd advise reading up on something called VTP Domains and ensuring that I know what the roles are and how they work.
Now if a person chooses to reboot the rack... or make last minute changes before lunch in haste and should mistakenly affect such things as VTP... yes, things might occur.
As far as someone messing with someone's rack... I guess you could secure your VTY lines, your aux ports, and your console port and watch it like a hawk...
But just be sure to put it back like you found it lest you violate that requirement and if a proctor cannot grade you then you get what he did grade... 0 aka nothing - I do not think they are required to peform password recovery for you.
But I guess if you came in wearing one of those cool t-shirts with CLI commands written upside down the proctors might take offense at that.
One thing every engineer must learn to do early on... perhaps most importantly...
Take responsibility for one's own actions real or perceived.
My favorite quote:
"Nothing has changed, Can you check it now?..."
Good luck and do whatever it takes to get rest the night before the lab... trust me you'll score a lot better.
--- James Wilson <netsurf@sersol.com> wrote:
> When I got back from lunch I found that someone (I assume a proctor) > removed vlan assignments on ports for three routers. > > -- > James D. Wilson > Sr. Network/Security Engineer > "non sunt multiplicanda entia praeter necessitatem" > William of Ockham (1285-1347/49) > > > > -----Original Message----- > From: nobody@groupstudy.com > [mailto:nobody@groupstudy.com]On Behalf Of Bill Burns > Sent: Friday, January 25, 2008 8:19 PM > To: 'Monica Belluci'; 'Cisco certification' > Subject: RE: CCIE LAB - Troubleshooting > > > Hi Monica, > > I would think that #7 is referring to a section later in the lab > workbook that might affect an earlier section. If you config XYZ in a
> section late in the day it could break section ABC that you configured
> early in the morning. You will get points for XYZ but you will lose > your points for ABC. > That is why Cisco tells you in tip #1 to read the whole lab. I would > doubt that any proctor would break your config while you are at lunch > unless you are wearing a Juniper shirt. : ) > > Thank you, > > Bill Burns > CCIE #12464, CCSI > Rack Time Rentals > www.racktimerentals.com > > > > -----Original Message----- > From: nobody@groupstudy.com > [mailto:nobody@groupstudy.com] On Behalf Of Monica Belluci > Sent: Thursday, January 24, 2008 8:52 AM > To: Cisco certification > Subject: CCIE LAB - Troubleshooting > > http://www.cisco.com/web/learning/le3/ccie/rs/lab_exam_tips.html > > *TEN TIPS FOR TAKING THE LAB EXAM* > > 1. Read the entire exam first and check for addressing issues. Do > not > skip any details or sections. > > 2. Manage your time. Make a plan to cover all the sections in the > time > provided. Work out how much time you will spend on each section, > keeping in > mind the point value of the questions. Don't forget to allow time > at the end > to verify your solutions. > > 3. Clarify the requirements of each question. > Don't assume > requirements that aren't mentioned in the question. During the lab,
> if you > are in any doubt, verify your understanding of the question with > the > proctor. > > 4. Do each question as a unit. Configure and verify before moving > to > the next question. You may want to redraw the topology with all the
> details > available. This will help you visualize and map the network. > > 5. Troubleshoot. You must know how to troubleshoot using the tools > available. Although troubleshooting is important, don't lose too > much time > working on a 2- or 3-point question. If you're caught off-guard by > an > unfamiliar topic, don't let it absorb too much time. Work on the > things you > are more comfortable with and go back to difficult items later. > > 6. Keep a list. During the exam, make notes on configurations and > settings as you move through the exam. Make a separate list for > items you > have not been able to address or where you have not achieved the > desired > result which you'll need to revisit. > > 7. Test your work. *Never rely on a configuration done in the early > hours of the exam.* *There is a possibility that an item you > configured a few sections earlier can become broken and > non-functional > *. Keep in mind that points are awarded for working configuration > only. > > 8. Save your configurations often. > > 9. Don't make any drastic changes in the last half hour of the > exam. > > 10. Speed is vital on the exam. Review and practice core material > the > week before the exam to ensure you can move quickly through the > less > challenging questions. > > > > Can anyone Understood what Cisco says on 7th tip > > Is it engage troubleshooting part which fashioned by CISCO ? > > People says you will analyze your configuration difference before > BREAK and AFTER break ? Is it ? > > I hope, by this email I am not going to break NDA rule......... > > ** > > *What you say?* > > > > Thanks > > Monica > ** > ** > >
This archive was generated by hypermail 2.1.4 : Fri Feb 01 2008 - 10:38:02 ARST