Qos And Link Bundling; Qos For Pos Link Bundling; Layer 3 Load Balancing On Link Bundles - Cisco ASR 9000 Series Configuration Manual

Configuring Modular QoS on Link Bundles

Layer 3 Load Balancing on Link Bundles

By default, load balancing on Layer 2 link bundles is done based on the MAC SA/DA fields in the packet
header. Layer 3 load balancing for link bundles is done on Ethernet Flow Points (EFPs) and is based on the
IPv4 source and destination addresses in the packet.When Layer 3 service-specific load balancing is configured,
all egressing bundles are load balanced based on the IPv4 source and destination addresses. When packets do
not have IPv4 addresses, default load-balancing is used.
Layer 3 load balancing for link bundles is enabled globally, using the following command:
hw-module load-balance bundle l2-service l3-params

QoS and Link Bundling

All Quality of Service (QoS) features, currently supported on physical interfaces and subinterfaces, are also
supported on all Link Bundle interfaces and subinterfaces. QoS is configured on Link Bundles in the same
way that it is configured on individual interfaces. However, the following points should be noted:
• When a QoS policy is applied on a bundle (ingress or egress directions), the policy is applied at each
• If a QoS policy is not applied to a bundle interface or bundle VLAN, both the ingress and egress traffic
• Link bundle members may appear across multiple Network Processing Units and linecards. The shape
Example 1
policy is applied to all interfaces that are members of the Ethernet link bundle.
Example 1 Applying a Traffic Policy to an Ethernet Link Bundle
interface Bundle-Ether bundle-id
service-policy input policy-1
end

QoS for POS link bundling

For POS link bundles, percentage-based bandwidth is supported for policers and output queues. Time-based
queue limit is supported for output queues.
Input QoS Policy setup
For input QoS, queuing is not supported and thus bandwidth is used for policer only. As a member link is
added or removed from a bundle with input QoS configured, the aggregate bundle bandwidth for that affected
member interface. Any queues and policers in the policy map (ingress or egress directions) will be
replicated on each bundle member.
will use the per link members port default queue.
rate specified in the bundle policymap is not an aggregate for all bundle members. The shape rate applied
to the bundle will depend on the load balancing of the links. For example, if a policy map with a shape
rate of 10 Mbps is applied to a bundle with two member links, and if the traffic is always load-balanced
to the same member link, then an overall rate of 10 Mbps will apply to the bundle. However, if the traffic
is load-balanced evenly between the two links, the overall shape rate for the bundle will be 20 Mbps.
shows how a traffic policy is applied on an Ethernet link bundle, in the ingress direction. The
Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide, Release 6.1.x
Layer 3 Load Balancing on Link Bundles
229