FRF.12

HI

In case of this questing.

HQ link to SB has 400K. Configure FRF.12 with 10MS sampling rate.

After cheking ISDN QoS this is my solution to enable FRF.12

 

(400*10)/8=500bytes (Maximun size of packet fragmented)

 

HQ
map-class frame-relay SB
frame-relay fragment 500


interface serial 0/0/1:0.1 point-to-point
frame-relay interface-dlci 101
class SB

SB
map-class frame-relay HQ
frame-relay fragment 500


interface serial 0/0/1:0.1 point-to-point
frame-relay interface-dlci 101
class HQ

 

Is this correct? would I have to apply any FRTS policy inside of map-class?

 

Thank you

Best Regards

 

Comments

  • I think that's right. One hundredth of the bandwidth for 10 msec and divide by 8 to get bytes.

  • For fragmentation to work you MUST enable traffic shaping in one form or another..... you can either do this on the interface itself or class based.

     

    If you are only attempting to configure fragmentation on the interface it is sufficient to enable traffic shaping on the interface itself.

  • Hi

    OK thanks,

    So in case they not say anything about the interface.

     

    HQ

    policy-map MRQ-to-SB
    class class-default
    shape average 360000 3600 0

    map-class frame-relay SB
    service-policy output MRQ-to-SB
    frame-relay fragment 500


    interface serial 0/0/1:0.1 point-to-point
    frame-relay interface-dlci 101
    class SB

    SB

    policy-map MRQ-to-HQ
    class class-default
    shape average 360000 3600 0


    map-class frame-relay HQ
    service-policy output MRQ-to-HQ
    frame-relay fragment 500


    interface serial 0/0/1:0.1 point-to-point
    frame-relay interface-dlci 101
    class HQ

    is this ok?

  • If you try it in your lab what happens?

     

    You seem to be very direct which is not how you want to be studying for you ccie lab exam. You need to be solid on the topics vs. very specific items. I would strongly suggest you watch Marks VODs on L3 QoS at this point as it should clear up the confusion you may have here.

  • No yet.

    I have reviewed the Mark's deep dive videos and check the QoS SRND Pdf many times. And I'm asking because is dificult to me undertand this.

    All documents they talk about LLQ + MQC-FRTS or Legacy FRTS + FRF.12.

    But you said: For fragmentation to work you MUST enable traffic shaping in one form or another. Ok. But don't why, the same with LLQ.

    Anyway, I will check FRF.12 and MQC-FRTS + FRF.12 and LLQ + MQC-FRTS + FRF.12 and I will compare the outputs of the shows.

     

    UPDATE

    I have checked the deep dives again and this is my definitly configuraion. It has to work

     

    HQ

    class-map match any RTP
    match ip dscp ef

    class-map match any SIG
    match ip dscp cs3

    policy-map voice
    class RTP
    priority 109 (if they don't ask for LLQ I'll make up the valor)
    class SIG
    bandwidth 16 (if they don't ask for signal I'll make up the valor)

    policy-map MRQ-to-SB
    class class-default
    shape average 360000 3600 0
    service-policy voice

    map-class frame-relay SB
    service-policy output MRQ-to-SB
    frame-relay fragment 500


    interface serial 0/0/1:0.1 point-to-point
    frame-relay interface-dlci 101
    class SB


    SB

    class-map match any RTP
    match ip dscp ef

    class-map match any SIG
    match ip dscp cs3

    policy-map voice
    class RTP
    priority 109 (if they don't ask for LLQ I'll make up a valor)
    class SIG
    bandwidth 16 (if they don't ask for signal I'll make up a valor)
    class class-default
    fair-queue

    policy-map MRQ-to-HQ
    class class-default
    shape average 360000 3600 0
    service-policy voice

    map-class frame-relay HQ
    service-policy output MRQ-to-HQ
    frame-relay fragment 500


    interface serial 0/0/1:0.1 point-to-point
    frame-relay interface-dlci 101
    class HQ

     

    I hope this would be usefull and in case I'd have similar question on the Lab Proctor doesn't expect "Legacy Frame Realy Traffic Shaping" configured [:S]

     

    Thank you.

     

    Best regards

     

Sign In or Register to comment.