According to the info that i have, if the conf is in the sub-interface, i have to apply the QoS in that sub-interface. I dont know if its another way to configure QoS to reach what i want. If you are sure that if i apply the service policy in the physical interface, the QoS will work, it would be great.

Thanks

Say for sure is danger, but I believe you can apply the policy-map on physical interface, so you don't need to have the parent level shaping. QOS might work differently per platform per software version, so it is safer to test it before you put in production.

Regards,

Lei Tian

Hey, i put the conf on the physical interface (g0/0), and i saw the "tagging" of the packets when i use the "show policy-map int g0/0", as i show below:

Router_Internet_MT#sh policy-map int  g0/0                              
  GigabitEthernet0/0

  Service-policy output: QoS_Internet

    Class-map: QoS_Web (match-any)
       49401 packets, 33752923 bytes
       5 minute offered rate 509000 bps, drop rate 0 bps
       Match: access-group name QoS_Web
         49401 packets, 33752923 bytes
         5 minute rate 509000 bps
       Queueing
         Output Queue: Conversation 265
         Bandwidth 25 (%)
         Bandwidth 10000 (kbps) Max Threshold 64 (packets)
         (pkts matched/bytes matched) 0/0
         (depth/total drops/no-buffer drops) 0/0/0

    Class-map: class-default (match-any)
       41778 packets, 6960776 bytes
       5 minute offered rate 123000 bps, drop rate 0 bps
       Match: any
Router_Internet_MT#

The bandwidth command its working now, its used in the g0/0 like this "badwidth 40000", because i have a 40 Mb ME and im giving 25 % to one web server. Quiestion: How cain i be really sure that the QoS policy im applying its working??

Thanks for answer...

Hi,

Sorry, I just noticed you are having sub-rate of the interface bandwidth. You will still need a parent level shaper on that case. The reason is without the parent level shaper, the CBWFQ/LLQ will not kick in until interface is congested; the interface doesn't know it can only transmit at 40Mbps, so it will not consider interface congested even transmit rate is way beyond 40Mbps. That will cause CBWFQ/LLQ never kicks in and traffic got dropped at the provider side.

You can still apply the policy-map on physical interface, but you need to use HQOS with parent level shape to 40M. To verify whether the qos is working properly, you can use a traffic generator to send out traffic in different classes, and check queueing behavior with/without congestion. There are also lot qos measurement tools available, but most of them are not free.

Please rate if that helps.

Regards,

Lei Tian

Hi, i really dont get what you're explaining just above. Do you have a conf example or something that can help me to see the issue better. Thanks for your help......

Im moving this question to Lan Switching and routing, so more people would help me, thanks

Hi,

The config should similar as what you had before, but instead of applying on sub-interface you can apply it on physical interface.

policy-map CBWFQ                              

class realtime

  priority

class signaling

  bandwidth 


...

policy-map 40M

class class-default


   shape average 40M


   service-policy CBWFQ

interface GigabitEthernetx

service-policy output 40M

Normally queuing only kicks in on GE interface when the traffic rate exceeds 1000 Mbps. However, you want the queuing kicks in when traffic exceeds 40 Mbps, so traffic will not be dropped at provider side. Therefore, you need to use HQoS. The first level policy shapes all traffic to 40 Mbps rate and attaches the 2nd level policy to the shaper.

Hope that explains better.

Lei Tian