MQC – based FRTS

Hi, experts!

could someone tell me where I'm wrong?

I've read this link:

http://blog.ine.com/2008/08/26/understanding-the-shape-peak-command/

"Note that if you apply CBWFQ per-VC, the maximum avaiable bandwidth is based on minCIR settings for a VC, not the CIR."

 


but I didn't understand which config is correct. In the first one the value (25) came from de CIR and the last one the value (12) came from the MINCIR?

If I have only one subinterface in my serial interface which config I have to use ( 1 ou 2 )? and How can I identify?

 

config 1 ***********************


class-map match-all VOICE

 match ip dscp ef

!

!

policy-map CHILD

 class VOICE

  priority percent 40  <--------------------------------- 

 class class-default

  fair-queue

policy-map PARENT

 class class-default

  shape average 64000

  shape adaptive 32000

  service-policy CHILD

!

interface Serial0/0.102 point-to-point

 ip address 1.1.1.1 255.255.255.252

 snmp trap link-status

 frame-relay class FRTS       <---------------------------------------------

 frame-relay interface-dlci 102


 service-policy output PARENT

!

******************** result config 1 *************** sh policy-map***********

...


 Service-policy : CHILD

 

        Class-map: VOICE (match-all)

          0 packets, 0 bytes

          5 minute offered rate 0 bps, drop rate 0 bps

          Match: ip dscp ef (46)

          Queueing

            Strict Priority

            Output Queue: Conversation 24

            Bandwidth 40 (%)

            Bandwidth 25 (kbps) Burst 625 (Bytes)         <----------------------------------

     ...

*********************************************************************************


config 2 


class-map match-all VOICE

 match ip dscp ef

!

policy-map CHILD

 class VOICE

  priority percent 40  <--------------------------------- 

 class class-default

  fair-queue

policy-map PARENT

 class class-default

  shape average 64000

  shape adaptive 32000

  service-policy CHILD

!


interface Serial0/0.201 point-to-point

 ip address 19.19.15.242 255.255.255.252

 snmp trap link-status

 frame-relay interface-dlci 201

  class FRTS                                       <-------------------------------------

!

map-class frame-relay FRTS

 service-policy output PARENT

!

******************** result config 1 *************** sh policy-map***********

...


    Service-policy : CHILD

 

        Class-map: VOICE (match-all)

          0 packets, 0 bytes

          5 minute offered rate 0 bps, drop rate 0 bps

          Match: ip dscp ef (46)

          Queueing

            Strict Priority

            Output Queue: Conversation 24

            Bandwidth 40 (%)

            Bandwidth 12 (kbps) Burst 300 (Bytes)    <------------------------------------------

            (pkts matched/bytes matched) 0/0

            (total drops/bytes drops) 0/0


thank you very much






Comments


  • interface Serial0/0.102 point-to-point

     ip address 1.1.1.1 255.255.255.252

     snmp trap link-status

     frame-relay class FRTS       <---------------------------------------------

     frame-relay interface-dlci 102

     service-policy output PARENT

    To begin with just a side note, in the first case the above bold statement is accomplished nothing since you donot have any class FRTS defined. Also "service-policy output PARENT" is applied under an interface not for a specific dlci.

    In the first case, you are trying to use class based GTS for FRTS because you are applying "service-policy output PARENT" directly under the point to point sub-interface. This simply will not work because "shape adaptive" command does not work with class based GTS. Thats why its "priority percent" is giving unexpected result.

    In the second case, you are using MQC based FRTS because here you are appplying "service-policy output PARENT" under map-class first then this is being applied under a specific dlci "frame-relay interface-dlci 201". In this "shape adaptive" works fine and the argument "apply CBWFQ per-VC, the maximum avaiable bandwidth is based on minCIR settings for a VC, not the CIR." is hence valid with MQC based FRTS so here you are getting 12kbps bandwidth from "priority percent 40".

     

     

     

     

  • [I]dcancerian, thank you very much 

  • Dear friends,

     

    Does this solution do the same thing?  Would it be valid for this question?

    policy-map CBWFQ
     class VOICE
      priority percent 40
     class DATA
      bandwidth percent 35
     class class-default
      fair-queue

    map-class frame-relay QOS
     frame-relay cir 64000
     frame-relay mincir 32000
     frame-relay adaptive-shaping becn
     service-policy output CBWFQ

    interface serial0/0
     frame-relay traffic-shaping

    interface serial0/0.100 point-to-point
     frame-relay interface-dlci 100
      class QOS

    Thank you!

  • Yes, it looks good. Should be a valid solution as well.

  • Does this solution do the same thing?  Would it be valid for this question?

    policy-map CBWFQ
     class VOICE
      priority percent 40
     class DATA
      bandwidth percent 35
     class class-default
      fair-queue

    map-class frame-relay QOS
     frame-relay cir 64000
     frame-relay mincir 32000
     frame-relay adaptive-shaping becn
     service-policy output CBWFQ

    interface serial0/0
     frame-relay traffic-shaping

    interface serial0/0.100 point-to-point
     frame-relay interface-dlci 100
      class QOS

    This seems to be a valid configuratio. Its a MQC CBWQ based legacy FRTS since you are still using "frame-relay traffic-shaping" command on FR interface.

Sign In or Register to comment.