The load balancing algorithm used in CRS by default is based on L3, 3 tuple, hash. So if you don't have enough different l3 source/destination addresses you won't see as even distribution. Normally this is just fine. But depending on the traffic flows you have you may need to go to L4, 7 tuple, algorithm. This will then look deeper into the packets and use the L4 ports along with source and destinations addresses to balance out the flows.
To change this it's global config command "cef load-balancing fields l3/l4".
This will change the hashing algorithm used on the linecards for load balancing.
I have also evaluated going for L4 load balancing instead of current default. But this did not make much sense when I noticed I have 4 uplinks load balancing nicely. Whereas access facing links are about 40% out in terms of load balancing...
I am beginning to suspect a cosmetic bug which should be confirmed by getting readings from Customer own devices.
Introduction: The "external-out enable" command is available for
configuration under the "router ospf process" in case of the IOS-XR
operating system. This command basically enables advertisement of
intra-area routes on the device as external routes in th...
Introduction Basic configuration for netflow Scale parameters for
netflow Netflow support Architecture Packet flow for netflow Inside the
LC CPU Netflow Cache size, maintenance and memory Sample usage Cache
Size Aging Permanent cache Characteristics Which...