bundle-hash
To display the source and destination IP addresses for the member links, distributed by the load balancing feature, in a multilink interface bundle, use the bundle-hash command in .
bundle-hash {Bundle-Ether bundle-id}
Syntax Description
|
Bundle-Ether bundle-id |
Specifies an Ethernet bundle for which you want to calculate load balancing. Range is 1- 65535. |
|
ibundle-id |
Number from 1 to 65535 that identifies a particular bundle. |
Command Default
No default behavior or values
Command Modes
Command History
|
Release |
Modification |
|---|---|
|
Release 6.0 |
This command was introduced. |
Usage Guidelines
Bundle interface traffic is distributed over the various member links of a bundle according to a hash function. The bundle-hash command allows you to determine which bundle member link will carry a particular flow of traffic.
You can use the bundle-hash command to get these information:
- Which members are used for a specified source/destination address pair, such as 10.10.10.1 20.20.20.1
The bundle-hash command does not display all possible IP addresses in an entire series. It stops displaying addresses after all the addresses for all the members of the bundle have been displayed once.
The bundle-hash command invokes a utility that initially prompts you to select some options. Based on the options you select, the utility prompts you more options to select. The initial options to select are as follows:
- L3/3-tuple or L4/7-tuple
- Single pair or Range
- IPv4 or IPv6
The bundle-hash command utility prompts you for these options as follows:
- Specify load-balance configuration (L3/3-tuple or L4/7-tuple) (L3,L4):
- Single SA/DA pair (IPv4,IPv6) or range (IPv4 only): S/R [S]:
- Enter bundle type IP V4 (1) or IP V6 (2):
- Enter source IP V4 address:
- Enter destination IP V4 address:
- Compute destination address set for all members? [y/n]:
- Enter subnet prefix for destination address set:
- Enter bundle IP V4 address [10.10.10.10]:
You may also be prompted to make further option choices depending on your selections.
You can use the show bundle command to get IP address information.
The below table provides a general summary of the options and the information you need to provide for each selected option. The actual information that you need to provide depends on the selections you make and may vary from the information provided in the below table.
|
Option |
Information You Need to Provide |
|---|---|
|
L3/3-tuple |
L3 information:
|
|
L4/7-tuple |
L3 information:
L4 information:
Platform-related information:
|
|
Single pair |
Information for a single source port and destination port. The utility uses this information to calculate the hash and display the bundle load-balance distribution among the user-provided physical/bundle links. The default is single mode. While in single mode, you may receive the following prompt: |
|
Range |
Information for sets of source and destination addresses to generate a packet flow for each set. The utility uses this information to calculate the hash for the generated packet flows and display the user-provided egress member links/bundle interfaces and the number of packet flows on each link. |
|
IPv4 |
IPv4 addresses |
|
IPv6 |
IPv6 addresses |
Compute destination address set for all members [y|n]:
If you enter y(es), several sample IPv4 addresses in the destination subnet are generated, and the link is calculated for each sample address. During this calculation, the destination network address is derived from the destination IPv4 address and the subnet prefix.
Task ID
|
Task ID |
Operations |
|---|---|
|
bundle |
read |
Examples
The following example shows how to calculate load balancing across the members of a link bundle (bundle-ether 28) using the 3-tuple hash algorithm, a single source and destination, and IPv4 addresses:
RP/0/RP0/CPU0:router# bundle-hash bundle-ether 28
Specify load-balance configuration (L3/3-tuple or L4/7-tuple) (L3,L4): l3
Single SA/DA pair (IPv4,IPv6) or range (IPv4 only): S/R [S]: s
Enter bundle type IP V4 (1) or IP V6 (2): 1
Enter source IP V4 address: 10.12.28.2
Enter destination IP V4 address: 10.12.28.1
Compute destination address set for all members? [y/n]: y
Enter subnet prefix for destination address set: 8
Enter bundle IP V4 address [10.12.28.2]: 10.12.28.2
Link hashed to is HundredGigE0/6/0/7
Destination address set for subnet 10.0.0.0:
10.0.0.6 hashes to link HundredGigE0/1/0/0
10.0.0.8 hashes to link HundredGigE0/6/0/5
10.0.0.12 hashes to link HundredGigE0/6/0/6
10.0.0.2 hashes to link HundredGigE0/6/0/7
10.0.0.1 hashes to link HundredGigE0/1/0/1
The following example shows how to calculate load balancing across the members of a link bundle (bundle-ether 28) using the 3-tuple hash algorithm, a range of source and destinations, and IPv4 addresses:
RP/0/RP0/CPU0:router# bundle-hash bundle-ether 28
Specify load-balance configuration (L3/3-tuple or L4/7-tuple) (L3,L4): l3
Single SA/DA pair (IPv4,IPv6) or range (IPv4 only): S/R [S]: r
Maximum number of flows (num src addr * num dst addr): 65536
Enter first source IP address: 10.12.28.2
Enter subnet prefix for source address set: 8
Enter number of source addresses (1-245): 20
Enter source address modifier (1-12) [def:1]: 5
Enter destination IP address: 10.12.28.1
Enter subnet prefix for destination address set: 8
Enter number of destination addresses (1-245): 20
Enter destination address modifier (1-12) [1]: 5
Many to many (M) or simple pairs (S)? [M]: s
Calculating simple pairs...
Total number of hits 20
Member HundredGigE0/1/0/0 has 6 hits
Member HundredGigE0/6/0/5 has 2 hits
Member HundredGigE0/6/0/6 has 2 hits
Member HundredGigE0/6/0/7 has 9 hits
Member HundredGigE0/1/0/1 has 1 hits
The following example shows how to calculate load balancing across the members of a link bundle (bundle-ether 202) using the 7-tuple hash algorithm, a single source and destination, and IPv4 addresses:
RP/0/RP0/CPU0:router# bundle-hash bundle-ether 202
Specify load-balance configuration (L3/3-tuple or L4/7-tuple) (L3,L4): l4
Single SA:SP/DA:SP pair (IPv4,IPv6) or range (IPv4 only): S/R [S]: s
Enter bundle type IP V4 (1) or IP V6 (2): 1
Enter source IP V4 address: 172.20.180.167
Enter destination IP V4 address: 172.30.15.42
Ingress interface --
- physical interface format: [ TenGigE | HundredGigE]R/S/I/P
- bundle interface format: [ Bundle-Ether]bundle-id
Enter ingress interface: HundredGigE0/2/0/3
Enter L4 protocol (TCP,UDP,SCTP,L2TPV3,NONE): UDP
Enter src port: 1000
Enter destination port: 2000
Compute destination address set for all members? [y/n]: n
S/D pair 172.20.180.167:1000/172.30.15.42:2000 -- Link hashed to is HundredGigE0/3/0/6
Another? [y]: y
Enter bundle type IP V4 (1) or IP V6 (2): 1
Enter source IP V4 address [172.20.180.167]: 172.20.180.167
Enter destination IP V4 address [172.30.15.42]: 172.30.15.42
Ingress interface --
- physical interface format: [HundredGigE | TenGigE ]R/S/I/P
- bundle interface format: [ Bundle-Ether ]bundle-id
Enter ingress interface [HundredgigE0/2/0/3]: HundredGigE0/2/0/3
Enter L4 protocol (TCP,UDP,SCTP,L2TPV3,NONE) [udp]: UDP
Enter src port [1000]: 1000
Enter destination port [2000]: 2000
Compute destination address set for all members? [y/n]: y
Enter subnet prefix for destination address set: 24
Enter bundle IP V4 address [172.20.180.167]: 209.165.200.225
S/D pair 172.20.180.167:1000/172.30.15.42:2000 -- Link hashed to is HundredGigE0/3/0/6
Destination address set for subnet 172.30.15.0:
S/D pair 172.20.180.167:1000/172.30.15.1:2000 hashes to link HundredGigE0/3/0/6
S/D pair 172.20.180.167:1000/172.30.15.6:2000 hashes to link HundredGigE0/2/0/1
S/D pair 172.20.180.167:1000/172.30.15.3:2000 hashes to link HundredGigE0/2/0/2
S/D pair 172.20.180.167:1000/172.30.15.5:2000 hashes to link HundredGigE0/2/0/3
Another? [y]: n
Feedback