Interactions between IP routing and QoS

One of my readers sent me an interesting question a while ago:

I reviewed one of your blog posts "Per-Destination or Per Packet CEF Load Sharing?" and wondered if you had investigated previously on how MQC QoS worked together with the CEF load-sharing algorithm (or does it interact at all)? For example, let's say I have two equal cost paths between two routers and the routing table (as well as CEF) sees both links as equal paths to the networks behind each router. On each link I have the same outbound service policy applied with a simple LLQ, BW, and a class-default queues. Does CEF check each IP flow and make sure both link's LLQ and BW queues are evenly used?

Unfortunately, packet forwarding and QoS are completely uncoupled in Cisco IOS. CEF performs its load balancing algorithm purely on source/destination information and does not take in account the actual utilization of outbound interfaces. If you have bad luck, most of the traffic ends on one of the links and the packets that would easily fit on the other link will be dropped by the QoS mechanisms.

You could use multilink PPP to solve the problem in low-speed environments. With MLPPP, CEF sends the traffic to a single output interface (the Multilink interface) and the queuing mechanisms evenly distribute packet fragments across the links in the bundle.

In high-speed environments, you can only hope that the number of traffic flows traversing the links will be so high that you’ll get a good statistical distribution (which is usually the case).


  1. I really don't have any live experience as of now but am experiencing with PfR/OER which could be an alternative to use in high speed environments. It would not result in a more even distribution of traffic than is allready achieved by statistical distribution, but it should additionally assure that each flow is routed on the path which can best accomodate its service level requirements.

  2. Hi Ivan

    I think also DS-TE can help in this point , by configruing queuing policy at headend and divide link bandwidths to sub-bools crossponding to classes and each sub-pool utilization statistics are propagated using same IGP extensions
  3. QoS mostly works on egress! so CEF have no relationship with QoS...
Add comment