Service Policy Input or Output

[Gerard Gacusan]

Assuming I have the MQC in place and I applied it in the interface.

Interface s1/0

service-policy output QOS

class-map HTTP

  match protocol http

class-map VOICE

  match dscp ef

policy-map QOS

  class VOICE

   priority percent 18

  class HTTP

   bandwidth percent 10

     police 128000

I knew to the fact that the output is Outgoing and input is Incoming.

I'd like to clarify something. Does it mean that "service-policy output command" is effecting the Transmit Load (Tx Load)? And "service-policy input command" is effecting the Receive Load (Rx Load) of the Interface?

Browsing the Internet is pretty much a Download concept (Rx Load), correct? But, if you're making a voice call, it is a Transmitting Load (Tx Load)?

Serial1/0 is up, line protocol is up
  Hardware is GT96K Serial
  MTU 1500 bytes, BW 1536 Kbit/sec, DLY 20000 usec,
     reliability 255/255, txload 1/255, rxload 240/255

In this case, what is the problem why the rxload is High? Assuming a client was browsing or playing video streaming the Internet. A voice phone conversation was interrupted when the Rx Load was at peak.

I'm thinking a service-policy input and police HTTP traffic ?

Thanks in advance ...

[Gerard Gacusan]

Rate-Limiting or Policing HTTP traffic will reduce the RxLoad utilization. However, the HTTP traffic will be dropping frequently eventhough there's no Congestion. The notion that, let the HTTP traffic flow normally in a normal condition but when there's a period of congestion, then  HTTP is high drop probabilty and let prioritize traffic like Voice be in the first queue to process before anything else.

Appreciate any other inputs ... Thanks

[gerald.suiza]

at that time that voice choppy did have a look at the service policy if it was dropping on the priority queue? Also, i would suggest to look at  the service provider policy if there is one and see how they are setup. on the condtion RX was high, maybe someone was downloading something?

[milan.kulik]

Hi,

the issue is:

"service-policy input command" is NOT effecting the Receive Load (Rx Load) of the Interface too much.

As you are dealing with packet already received, i.e., the bandwidth on your line was consumed already by the packet incoming.

Don't forget, when running VoIP, you need QoS in both directions to have the bandwidth enough reserved for the voice traffic (you are talking but also listening).

You can configure  service-policy ouput to prioritize your voice - as you have done.

But to priroritize voice within the incoming traffic, you need the other side to configure a proper QoS, i.e., your router on the other site if you are running it over a private WAN or a provider router if you are connecting to the Internet or a provider backbone.

(To be precise: you need a proper QoS along the whole path between your  voice devices.)

In your case, I'm afraid whatever you configure for HTTP will have a minimal effect on the incoming traffic load.

You need to tell your provider to configure similar QoS on his router to prioritize voice traffic when sent to you (and restrict http traffic if necessary).

HTH,

Milan