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 Hash Algorithms Are Used for MA5200G and ME60 Trunk Load Balancing?

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

What hash algorithms are used for MA5200G and ME60 Trunk load balancing?

Handling Process

1.         ME60 V100R005C02B01B

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.

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

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. Two-level hash may fail on versions earlier than ME60 SPC028.

2.         ME60 V100R005C05

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.

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

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.

3.         ME60 V600R002C02

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 trunk load balancing: This mode can be implemented using a hash algorithm with the CIR value or the user number as the hash key.

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.

4.         MA5200 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.

5.         MA5200 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 to 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

N/A

END