Task Wording

I came across a task, and based on wording it threw me for a huge loop, but after some trial, I gave in and decided to just look at the config and explaination, it wasnt what I was expecting. 
So my question is: Are these workbook tasks worded like we should assume to expect in the exam? I'm meaning they can be very vague in some tasks, as well as "technically" correct in others.

My example of what I'm getting at:

EIGRP traffic engineering with metrics lab

  • Configure a metric manipulation on R7 so that traffic from R9 to R6's Loopback0 prefix transits the link between R3 and R7.

Whew...ok. So I'm thinking there must be some kind of way to filter using a prefix list on R7 to isolate just the loopback networks then use the metric tuning to have them route out the interface to R1. For the life of me I cannot figure out where to attach the prefix list. 

The answer was to just bump the metric on the g1.67 link so ALL traffic now goes to R1 instead of straight to R6. 

So "technically" the loopback traffic is now engineered using the metric, but now so are the 155.1.x.x networks also. The question said nothing about the 155.1.x.x network, just the 150.1.x.x. 

 

Comments

  • Hi,

    Metric manipulation is totally a different thing than prefix filtering is. As per your question, there is no ONLY keyword for R6's loopback, it says that traffic for that loopback should be routed through R1.

    Offset-lists could have been used for specific prefix traffic engineering.

    Sent from my iPhone

    On 16 Jul 2014, at 04:10, cstambaugh <[email protected]> wrote:

    I came across a task, and based on wording it threw me for a huge loop, but after some trial, I gave in and decided to just look at the config and explaination, it wasnt what I was expecting. 
    So my question is: Are these workbook tasks worded like we should assume to expect in the exam? I'm meaning they can be very vague in some tasks, as well as "technically" correct in others.

    My example of what I'm getting at:

    EIGRP traffic engineering with metrics lab

    • Configure a metric manipulation on R7 so that traffic from R9 to R6's Loopback0 prefix transits the link between R3 and R7.

    Whew...ok. So I'm thinking there must be some kind of way to filter using a prefix list on R7 to isolate just the loopback networks then use the metric tuning to have them route out the interface to R1. For the life of me I cannot figure out where to attach the prefix list. 

    The answer was to just bump the metric on the g1.67 link so ALL traffic now goes to R1 instead of straight to R6. 

    So "technically" the loopback traffic is now engineered using the metric, but now so are the 155.1.x.x networks also. The question said nothing about the 155.1.x.x network, just the 150.1.x.x. 

     




    INE - The Industry Leader in CCIE Preparation

    http://www.INE.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx
Sign In or Register to comment.