The traffic load balance along the threads of an Ether Trunk is not optimally balanced by default, therefore, traffic characteristics must be taken into account deeply.
There are 2 ways to configure it, it can be for a simple load balance, based on:
- dst-ip: based on destination IP addresses
- dst-mac: based on destination MAC addresses
- src-ip: based on source IP addresses
- src-mac: based on source MAC addresses
- src-dst-ip: based on the Exclusive-Or result of source and destination IP addresses
- src-dst-mac: based on the Exclusive-Or result of source and destination MAC addresses
This is configured in the trunk itself, or a higher level load balance, which is configure by using a load balance profile for details in the l2 field, or ipv4, ipv6 or mpls.
For it, we must decide the criteria for which the balancing will be performed and would be done as follows:
System-view
Load-balance-profile name
l2 field [ dmac | l2-protocol | smac | sport | vlan ]
or
ipv4 field [ dip | l4-dport | l4-sport | protocol | sip | sport | vlan ] *
or
ipv6 field [ dip | l4-dport | l4-sport | protocol | sip | sport | vlan ] *
or
mpls field [ 2nd-label | dip | dmac | sip | smac | sport | top-label | vlan ] *
and implement in the Ehter trunk:
load-balance enhanced profile name