From: James Matrisciano (jmatrisciano@kenttech.com)
Date: Mon Sep 19 2005 - 10:50:46 GMT-3
Sort of jumpping in late on this, but wanted to throw something out...
Bugs in IOS and Hardware problems in the lab. You will be told from the
proctor that you need to troubleshoot an IOS problem to your fullest
extent, if not resolved you may addess this problem to the proctor.
They will ask you what you did to troubleshoot. If they are satisfied
with the your troubleshooting prowless, then they will troubleshoot as
well. They will keep track of the time that they worked on the problem,
if it is indeed a hardware problem, it will be identified and your time
will be given back to you, if they find that it is a configuration error
on your behalf, they will inform you that it is not a hardware problem,
and all time that they used is wasted and marked against you, meaning,
you aint getting that time back.
I have run into a couple problems in the past, informed the problems to
the proctor, it was a configuration error on my behalf, they never
trouble shot for me, they just said, it is not a hradware configuration
problem (then smiled), so I knew it was something I fat fingered, and
yes, I fixed it.
I do not see any bugs being problems in the lab, you have to remember,
these labs get used everyday and are really put through the ringer in
their own internal group, but as we all know, Cisco is like fly tape,
there are bugs for everything, but I do not believe you will ever see
them in a core requirement but you never know.
jm
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Bill.McKenzie@bisys.com
Sent: Monday, September 19, 2005 9:24 AM
To: Lee Donald
Cc: ccielab@groupstudy.com; Ralph; nobody@groupstudy.com
Subject: RE: RE : Encap Failed "Router on a Stick"
The problem I ran into was never solved per requirement . I rebooted the
devices and started from a fresh configuration and still no luck. If I
would have just got it to work I would have lost the points on that
section but gotten points in later sections because I would have had
connectivity, but if I left the required configuration in I would have
lost those points plus later points.
"Exceeding Client Expectations"
Lee Donald
<Lee.Donald@t-sys
tems.co.uk>
To
Sent by: Ralph <Mandela@myrealbox.com>,
nobody@groupstudy ccielab@groupstudy.com
.com
cc
Subject
09/19/2005 09:13 RE: RE : Encap Failed "Router on
a
AM Stick"
Please respond to
Lee Donald
<Lee.Donald@t-sys
tems.co.uk>
Ralph,
I have pondered the same question many times and the think the answer is
as follows, by the time you get into the lab you should have come across
most of the bugs and be able to spot them so you can reload the box very
quickly.
For instance if you are in the middle of configuring a route-map, and
you type " set ip next hop ", something you know is a correct command
inside a route-map, the router says " wrong agument/ invalid syntax"
reload straight away, it's a bug.
It may not be very fair but that's how it is.
Regards
Lee.
-----Original Message-----
From: Ralph [mailto:Mandela@myrealbox.com]
Sent: 19 September 2005 14:00
To: ccielab@groupstudy.com
Subject: RE : Encap Failed "Router on a Stick"
Guys:
I'm just wondering what is the recommended approach to resolving issues
like in the LAB. Do we need to inform the Proctor about what we suspect
to be a bug in the IOS? what about the time wasted trying to
troubleshoot a bug-related problem, will lost time be credited back?
How are issues like this generally taken care of? What about the real
victim of this problem - the candidate - the induced psychological
stress this may have caused him/her. Is it okay to just move on to the
next TASK, what if the buggy task is a core task? There has to be a
formal procedure in place to resolve problems like this, that will
hopefully(?), be fair to all parties concerned.
Just wondering!
Ralph.
From: Bill.McKenzie@bisys.com < Bill.McKenzie@bisys.com>
Date: Sep 19, 2005 7:19 AM
Subject: RE : Encap Failed "Router on a Stick"
To: Richard Dumoulin <Richard.Dumoulin@vanco.fr >
Cc: ccielab@groupstudy.com, Lee Donald <Lee.Donald@t-systems.co.uk>
I removed the native reference on both R6 and the SW1 and I was able to
ping to and from R6 now. Is this a version bug?
Making the native vlan 263 was actually the requirement and the
configuration I posted was the actual solution, which was demonstrated
to work.
Thanks everyone.
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:15 GMT-3