Task 7.1

I have configured FRTS exactly as the task said and the study guide said on the spokes and did the same for the hub. I didn't get the points for applying the same config on R3 for each of the VC's. I don't know if the proctor is trying to confuse me or what. I thought having extra configuration does not cost you points.

Comments

  • <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">





    So the the output of 'show traffic-shap' note the values present for
    each pvc?



    I agree that you were shaping the same then for other pvc's which you
    weren't asked about.  If those PVC's were indeed unused though, I don't
    think there's anything in the wording that would make you care or not. 
    It's just more specific to do it per pvc!






     



    Scott Morris, CCIEx4
    (R&S/ISP-Dial/Security/Service Provider) #4713,

    JNCIE-M #153, JNCIS-ER, CISSP, et al.

    JNCI-M, JNCI-ER

    [email protected]



    Internetwork Expert, Inc.

    http://www.InternetworkExpert.com

    Toll Free: 877-224-8987

    Outside US: 775-826-4344



    Knowledge is power.

    Power corrupts.

    Study hard and be Eeeeviiiil......






    andreiarnautu wrote:

    I have configured FRTS exactly as the task said and the study
    guide said on the spokes and did the same for the hub. I didn't get the
    points for applying the same config on R3 for each of the VC's. I don't
    know if the proctor is trying to confuse me or what. I thought having
    extra configuration does not cost you points.







    Internetwork Expert - The Industry Leader in CCIE Preparation

    http://www.internetworkexpert.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx

  • Yes, they were showing the output values for each PVC, I haven't done it per interface, i have configure FRTS for each VC.  Exactly the same as in the SG, my only addition was the extra config on R3.

  • <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">





    Well, if ALL other pvc's were unused, I'd agree with you that it
    probably didn't make any difference.  No traffic = no shaping anyway. 
    But it is sloppier configuration.  As long as you are aware of that and
    the implications, I'd say "lesson learned".






     



    Scott Morris, CCIEx4
    (R&S/ISP-Dial/Security/Service Provider) #4713,

    JNCIE-M #153, JNCIS-ER, CISSP, et al.

    JNCI-M, JNCI-ER

    [email protected]



    Internetwork Expert, Inc.

    http://www.InternetworkExpert.com

    Toll Free: 877-224-8987

    Outside US: 775-826-4344



    Knowledge is power.

    Power corrupts.

    Study hard and be Eeeeviiiil......






    andreiarnautu wrote:

    Yes, they were showing the output values for each PVC, I haven't
    done it per interface, i have configure FRTS for each VC.  Exactly the
    same as in the SG, my only addition was the extra config on R3.







    Internetwork Expert - The Industry Leader in CCIE Preparation

    http://www.internetworkexpert.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx

  • No, what I meant is I DID NOT configured FTRS on all PVC's. I had only configured it for the PVC's as required in the task, and as found in the study guide.

     

    -Andrei

  • Here was the exact config:

    R5:
    map-class frame-relay DLC503
     frame-relay end-to-end keepalive mode bidirectional
     frame-relay cir 384000
     frame-relay bc 3840

     frame-relay be 3840
     frame-relay mincir 128000
     frame-relay adaptive-shaping becn
    interface Serial0/0
     no ip address
     encapsulation frame-relay
     no fair-queue

     frame-relay traffic-shaping
     frame-relay interface-dlci 503 ppp Virtual-Template1
      class DLC503

    R4:
    map-class frame-relay DLC403
     frame-relay cir 384000

     frame-relay bc 3840
     frame-relay be 3840
     frame-relay mincir 128000
     frame-relay adaptive-shaping becn
    interface Serial0/0
     no ip address
     encapsulation frame-relay

     no fair-queue
     frame-relay traffic-shaping
     frame-relay interface-dlci 403 ppp Virtual-Template1
      class DLC403


    Nothing sloppy here:) I think at least

    On Thu, Jul 16, 2009 at 2:50 PM, Scott Morris <[email protected]> wrote:
    Well, if ALL other pvc's were unused, I'd agree with you that it
    probably didn't make any difference.  No traffic = no shaping anyway. 
    But it is sloppier configuration.  As long as you are aware of that and
    the implications, I'd say "lesson learned".







     



    Scott Morris, CCIEx4
    (R&S/ISP-Dial/Security/Service Provider) #4713,

    JNCIE-M #153, JNCIS-ER, CISSP, et al.

    JNCI-M, JNCI-ER

    [email protected]



    Internetwork Expert, Inc.

    http://www.InternetworkExpert.com

    Toll Free: 877-224-8987

    Outside US: 775-826-4344



    Knowledge is power.

    Power corrupts.

    Study hard and be Eeeeviiiil......






    andreiarnautu wrote:

    Yes, they were showing the output values for each PVC, I haven't
    done it per interface, i have configure FRTS for each VC.  Exactly the
    same as in the SG, my only addition was the extra config on R3.








    Internetwork Expert - The Industry Leader in CCIE Preparation

    http://www.internetworkexpert.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx





    Internetwork Expert - The Industry Leader in CCIE Preparation

    http://www.internetworkexpert.com



    Subscription information may be found at:

    http://www.ieoc.com/forums/ForumSubscriptions.aspx

  • Task 7.1: You should always choose solution that best suits the task's requirements. The task asks you to resolve the problem with a large amount of packet drops on the link FROM the FR cloud to R3. Configuring FRTS on R3's S1/0 interface has nothing to do with solving this problem.
    You can only apply extra configuration which has no effect on the lab's results and requirements - like configuring aliases, adjusting terminal options, IGP timers etc.

Sign In or Register to comment.