Time Range ACL query

Hi all

I also would like some more clarification on the below post.
In some workbooks I have seen that for times between 9am and 5pm weekdays,
its: periodic weekdays 09:00 to 16:59

Does anyone know for certain, whether in the lab you indeed use: periodic
weekdays 09:00 to 17:00, even though strictly speaking this is not correct?

I've been marked as incorrect for using 17:00 by ASET's grading engine.

Then again, this is always a question Id ask the proctor when the time
came...

2009/8/5 Darby Weaver <ccie.weaver_at_gmail.com>

> I'll be spending Thursday with the Lab Designers - I can ask the question
> and argue the validity of the next minute or other value to get their
> input/insight on the matter on more time and perhaps use your example if
> you
> like.
>
> Some say the lab is all about the wording and I'll agree it is all about
> the
> wording. If the labs do a task such as (WRITE IT THIS WAY), then I'm going
> to (WRITE IT THIS WAY). Nada mas y nada menos, claro. No more and not a
> letter less.
>
>
>
> On Tue, Aug 4, 2009 at 8:23 PM, Darby Weaver <ccie.weaver_at_gmail.com>
> wrote:
>
> > I feel ya. I asked this one to the lab designer at Cisco Live.
> >
> > The answer is simple - do what the lab says to do.
> >
> > Thus... if it says 1600 to 1800 for example...
> >
> > The grading script is going to be looking for those values and not
> anything
> > else.
> >
> > Anyone else can argue the semantics and how the command works. The lab
> is
> > not quite that ornate on wording - if they ask for a certain value,
> chances
> > are they want EXACTLY/VERBATIM what they are asking for.
> >
> > Or at least that is what the script is going to look for.
> >
> > Let's put it this way:
> >
> > Guys who pass never know what they passed on.
> >
> > Guys who fail do get a score report that might be vague but might not be
> > too vague if the math is correct. If one gets 100% in a section and uses
> a
> > certain nomenclature then there is a possibility that it stands to be
> > correct.
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > On Tue, Aug 4, 2009 at 6:42 PM, Fernando Maura <fermaura_at_gmail.com>
> wrote:
> >
> >> Hi guys, I believe that you have already discuss this topic several
> times,
> >> but since I'm new here i have to ask you again, since I have encounter
> >> differents opinion about this.
> >> the question is about the values when using time-range, TCP intercept
> and
> >> some other similar values, here is the thing, I have been study from
> >> different vendors IE, netmasterclass and the use different in their
> guides.
> >>
> >> example 1: an exercise say configure you router to start closing TCP
> >> session after they have EXCEEDED 1000 and if the ammount of connections
> fall
> >> BELOW 500 start accepting connections again.
> >>
> >> in this case for me the keywords are EXCEEDED and BELOW, the value for
> >> exceeded is 1001 and the value for BELOW is 499, but in the guides are
> 1000
> >> and 500 straigth
> >>
> >> Example 2: block traffic from HTTP from 8 AM to 5 PM.
> >>
> >> i this case with the use of TIME-RANGE acl, the start time will be 08:00
> >> and the end time will be 16:59 (when you press the ? the help says that
> the
> >> en time is the begin of the next minute). but once more i find in the
> guides
> >> that their using 08:00 and 17:00 values.
> >>
> >> I now that this could be find "LAME questions" but I will take the LAB
> in
> >> 15 days and dont whant to loose point cause of this.
> >>
> >> Recomendations of what values to use?
> >>
> >> Best Regards
> >>
> >>
> >> Blogs and organic groups at http://www.ccie.net
> >>
> >> _______________________________________________________________________
> >> Subscription information may be found at:
> >> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
Regards
Roy
Blogs and organic groups at http://www.ccie.net