Filter
Top Products
the L4 header to be used for hash calculation, and a meaningful description to associate the protocol
number with the name. This utility is supported on the S6000 platform.
Syntax
load-balance flexhash ipv4/ipv6 ip-proto <protocol number>
<description string> offset1 <offset1 value> [offset2 <offset2
value>]
To disable the Flex hash settings, use the no load-balance flexhash ipv4/
ipv6 ip-proto protocol number command.
Parameters
ipv4 Denotes whether Flex Hash needs to be enabled for IPv4
packets.
ipv6 Denotes whether Flex Hash needs to be enabled for IPv6
packets.
protocol
number
Represents the Outer IPv4 protocol field in case of IPv4
packets, and the Outer IPv6 next header field in case of IPv6
packets.
The ipv4/ipv6 keyword and the IP protocol value are used
as keys to identify if a duplicate flex hash configuration is
already present. Duplicate flex hash configuration is not
possible. To change an existing flex hash configuration, you
must delete the existing flex hash attribute and configure the
flex attribute afresh.
description
string
A description string is followed by the protocol number to
enable you to associate the protocol number with the
protocol name in an easily-identifiable way. For example, for
a protocol number of 254, you can specify the description as
RRoCE.
offset1 value Specify the byte offset from the start of the L4 header from
which the 2-byte data is extracted and be used in hash
computation. You must enter the offset as an even number.
The offset range is 0 – 30 bytes from start of L4 header.
offset2 value (Optional) Specify the additional 2 bytes that must be
extracted from the start of the L4 header to be used for hash
computation. You must enter the offset as an even number.
The offset range is 0 – 30 bytes from start of L4 header.
Default None
Command
Modes
CONFIGURATION mode
Command
History
Version 9.3(0.0) Introduced on the S6000 platform.
Usage
Information
With the introduction of various overlay technologies such as network virtualization
using generic routing encapsulation (NVGRE) segments and Routable Remote
Direct Memory Access (RRDMA) over Converged Ethernet (RRoCE), information
related to a traffic flow is contained in the L4 header. The fields in the L2 and L3
592
Flex Hash and Optimized Boot-Up