From: Anthony Sequeira (Anthony_Sequeira@skillsoft.com)
Date: Sat Jun 28 2008 - 15:56:42 ART
I would be very specific in my configuration. Always be as specific as
possible to meet the exact task requirement. In fact, that is one of the
reasons that the proctor is there; to clarify a task if the wording is
unclear or grammatically unsound.
Being very specific in your configuration is a skill that comes from
knowing all possible configuration options. The whole point of the task
might be to see if you know there are many ways to do a particular
thing. "Know thy options" is one of the mantras over at NetMasterClass.
With all this said, it is good news that a human will examine your
configs if you are close to passing. This can get you points in the rare
case that you actually deserve marks for attaining the desired result
even though you took a path that varied from the grading script.
So a quick and obvious example here:
Task 3.1 Ensure the 172.16.30.0/24 route carries a tag value of 200.
I would not tag all the routes that this router is sending - I would be
sure to build a route-map that tags the specific route.
Anthony J. Sequeira
#15626
www.freeiestuff.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
David Chances
Sent: Saturday, June 28, 2008 12:53 PM
To: ccielab@groupstudy.com
Subject: Default Seed-Metric + the "Script"
I have read many times now that
"over config" is fine, on the condition it does not break or interfere
with anything else. But, what about under-config, speaking with a view
that
one
command fits all. Let me try and explain with another question.
When
redistributing from one protocol to another, we can "tag" (for
want of a better word) the metric onto the end of redistribute
<protocol>
command, or use the default-metric command within the receiving
protocol.
So my second question is, what are the rules; if any that govern what is
preferred over the other? Both will yield the same result technically
from
what
I see. Of course the latter will set the "default" for all protocols
coming in - hence, under config? But, other than that are there any
reasons to
pick
the former?
We
are marked, one assumes by a script for
the most part, but how tolerant is it when it comes to choices like
this?
Without giving too much away, something I saw on the Cisco Assesor lab
that
made me quetion this. Anyone
care to opine?
This archive was generated by hypermail 2.1.4 : Tue Jul 01 2008 - 06:23:23 ART