cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2173
Views
0
Helpful
5
Replies
cisco_lad2004
Contributor

CRS-1 Load balancing issue

Dear all,

I am using a simple load balacing based on static routing, running V 3.8.4.

Although checking route and cef details confirms load balancing is as it should be...load on interfaces is very much apart for outpout traffic (input looks fiine).

load interval and configuraion on each interface is exactely the same, no bundling used.

Any thoughts ?

TIA

Samir

5 REPLIES 5
Latchum Naidu
Engager

Hi Samir,

The below link is clearly explained the steps when bundle is not active.

http://www.cisco.com/en/US/docs/routers/crs/software/crs_r3.9/troubleshooting/guide/tr39balc.html

Hope this helps you.

Please rate the helpfull posts.

Regards,

Naidu.

Many thanks Naidu,

I am actually not using bundles, its a plain static route over 2 links / ports.

Samir

Bryan Garland
Cisco Employee

Samir,

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. 

Thanks,

Bryan

Many thanks Bryan,

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.

Many thanks again !

Samir

Samir,

Did you managed to find the root cause for this problem , i seem to have the same symtopms , is it a SW bug ?