A bundle is a group of
one or more ports that are aggregated together and treated as a single link.
All QoS features currently supported on physical interfaces, are also supported
on all link bundle interfaces. Applying QoS on sub-interfaces is not supported.
link bundling is supported.
interface can only contain physical interface.
All links within
a single bundle must be configured either to run 802.3ad (LACP) or Etherchannel
(non-LACP). Mixed links within a single bundle are not supported.
is not supported on Ethernet link bundles.
of links supported in each link bundle is 64.
number of link bundles supported is 128.
function is a forwarding mechanism to distribute traffic over multiple links
based on Layer 3 routing information in the router. Per-destination load
balancing, where the router is allowed to distribute packets over one of the
links in the bundle, is the only supported load balancing in the
Cisco NCS 5500 Series Router. When the
per-destination load balancing is enabled, all packets for a certain
source-destination pair goes through the same link, though there are multiple
links available. In other words, per-destination load balancing can ensure that
packets for a certain source-destination pair could arrive in order.
Layer 3 Load
Balancing on Link Bundles
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 egress bundles are load
balanced based on the IPv4 source and destination addresses. When packets do
not have IPv4 addresses, default load-balancing (based on the MAC SA/DA fields
in the packet header) is used.
Configure QoS on
QoS is configured on
link bundles in the same way that it is configured on individual interfaces.
When a QoS
policy is applied on a bundle (ingress or egress direction), the policy is
applied at each member interface. Any queue or policer in the policy-map
(ingress or egress direction) is replicated on each bundle member.
If a QoS policy
is not applied to a bundle interface, both the ingress and egress traffic use
the default queue of the per link member port.
The shape rate
specified in the bundle policy-map is not an aggregate for all bundle members.
The shape rate applied to the bundle depends 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 applies to the bundle.
However, if the traffic is load-balanced evenly between the two links, the
overall shape rate for the bundle becomes 20 Mbps.
If a member is
deleted from a bundle, the total bundle statistics changes because the
statistics that belongs to the detached link is lost.
You have to
accomplish the following to complete the QoS configuration on link bundles:
policy-map and specifying the respective class-map
This example shows
how a traffic policy is applied on an Ethernet link bundle. The policy is applied to all interfaces that are members of the
Ethernet link bundle.
/* Policy-map */
set qos-group 1
set qos-group 2
set qos-group 3
set qos-group 4
set qos-group 5
set qos-group 6
/* Ether Bundle */
service-policy input ingress
service-policy output egress
ipv4 address 188.8.131.52 255.255.255.254
flow ipv4 monitor FMM-V4 sampler SM ingress
flow ipv6 monitor FMM-V6 sampler SM ingress
flow mpls monitor FMM-MPLS sampler SM ingress
ipv4 access-group IPV4ACL_101 ingress
ipv6 access-group IPV6ACL_101 ingress
Verify that the
bundle status is UP.
router# show bundle bundle-ether 1200
Wed Dec 16 19:55:49.974 PST
Local links <active/standby/configured>: 35 / 0 / 35
Local bandwidth <effective/available>: 3500000000 (3500000000) kbps
MAC address (source): ea3b.745f.c4b0 (Chassis pool)
Inter-chassis link: No
Minimum active links / bandwidth: 1 / 1 kbps
Maximum active links: 64
Wait while timer: 2000 ms
Load balancing: Default
Flap suppression timer: Off
Cisco extensions: Disabled
mLACP: Not configured
IPv4 BFD: Not configured
Port Device State Port ID B/W, kbps
-------------------- --------------- ----------- -------------- ----------
Hu0/4/0/0 Local Active 0x8000, 0x0009 100000000
Link is Active
Hu0/4/0/1 Local Active 0x8000, 0x000a 100000000
Link is Active
- - -
- - -
Hu0/4/0/35 Local Active 0x8000, 0x002b 100000000
Link is Active