No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

What Are the Similarities and Differences in Load Balancing Between the Mainstream Versions Running on ME60s?

Publication Date:  2013-01-07 Views:  40 Downloads:  0
Issue Description

What are the similarities and differences in load balancing between the mainstream versions running on ME60s?

Handling Process

The similarities are listed as follows:

All versions running on ME60s support:

Network-side route load balancing: The source and destination IP addresses are used as the hash keys.

Network-side trunk load balancing: The left-most bits of the source and destination IP addresses are rotated and the newly generated results are XORed.

Network-side two-level hash: Trunk traffic is first load balanced using a hash algorithm based on the load balancing table. This traffic is load balanced a second time using a hash algorithm based on the trunk forwarding table. Because the two load balancing processes use different hash algorithms, traffic forwarding is balanced.

The differences are listed as follows:

1.         ME60 V100R005C02B01B

User-side trunk load balancing: The CIR value is hashed.

2.         ME60 V100R006C05SPC600

User-side trunk load balancing: The CIR value is hashed.

3.         ME60 V600R002C02SPC700

Network-side trunk load balancing: This mode can be implemented using a hash algorithm with the CIR value or the user number as the hash key.

MA5200G supports the hash algorithm for load balancing as follows:

1.         MA5200G V300R003C01

Network-side route load balancing: The left-most bits of the source and destination IP addresses are rotated and the newly generated results are XORed.

Network-side trunk load balancing: The source and destination IP addresses are used as the hash keys.

User-side trunk load balancing: The user source and destination IP addresses are used as the hash keys.

Network-side two-level hash: Trunk traffic is first load balanced using a hash algorithm based on the load balancing table. This traffic is load balanced a second time using a hash algorithm based on the trunk forwarding table. Because the two load balancing processes use different hash algorithms, traffic forwarding is balanced.

2.         MA5200G V300R003C02

Network-side route load balancing: The left-most bits of the source and destination IP addresses are rotated and the newly generated results are XORed.

Network-side trunk load balancing: The source and destination IP addresses are used as the hash keys.

Network-side trunk load balancing: This mode is implemented using a hash algorithm with the user number as the hash key that is delivered by the FIB table.

Network-side two-level hash: Trunk traffic is first load balanced using a hash algorithm based on the load balancing table. This traffic is load balanced a second time using a hash algorithm based on the trunk forwarding table. Because the two load balancing processes use different hash algorithms, traffic forwarding is balanced.

Root Cause
N/A
Solution
N/A
Suggestions
When V100R005 or V100R006 running on ME60s is upgraded to V600R002, user-side trunk load balancing can be modified using the bas-load-balance { flow-mode | user-mode } command.

END