From: joshua lauer (jslauer@hotmail.com)
Date: Mon Sep 19 2005 - 19:50:13 GMT-3
If you feel it's really a bug in the IOS software then you need to
troubleshoot the problem out and present to the proctor why you feel (with
debugs, etc...) this problem is possibly related to a bug. Unless you can
positively prove that something is not right with debugs and other
diagnostic tools I would say it's a configuration problem unless proven. Not
to say that things dont happen, Keeping yourself in tune with the proctor
and showing him/her what is going on and being able to prove things can work
wonders in your favor. I can say that through practice, reading release
notes, etc...I should have most bugs and things worked out prior to arriving
from the lab. In fact, I do look for posted bugs in the releases just in
case something odd might occur. Just my way of providing insurance....
josh
----- Original Message -----
From: "Ralph" <Mandela@myrealbox.com>
To: <ccielab@groupstudy.com>
Sent: Monday, September 19, 2005 8:16 AM
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.
>
> Bill
This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:15 GMT-3