Administrator Guide

Dell(conf)# load-balance flexhash ipv4/ipv6 ip-proto <protocol number> <description string>
offset1 <offset1 value> [offset2 <offset2 value>]
To delete the configured flex hash setting, use the no version of the command.
LACP Fast Switchover
LACP Fast Switchover causes the physical ports to be aggregated faster when configured in a port-channel on both the nodes that are
members of a port-channel.
When LACP ‘fast-switchover’ is enabled on the system, two optimizations are performed to the LACP behavior:
• The wait-while timer is not started in the ‘waiting’ state of the MUX state machine. The port moves directly to the ‘attached’ state.
• The local system moves to the ‘collecting’ and ‘distributing’ states on the port in a single step without waiting for the partner to set
the ‘collecting’ bit.
Configuring LACP Fast Switchover
To configure the optimized booting time functionality, perform the following step:
• The lacp fast-switchover command applies to dynamic port-channel interfaces only. When applied on a static port-channel,
this command has no effect. If you configure the optimized booting-time capability and perform a reload of the system, the LACP
application sends PDUs across all the active LACP links immediately. INTERFACE (conf-if-po-number) mode
Dell(conf-if-po-
number)#lacp fast-switchover
LACP
LACP Fast Switchover
When LACP ‘fast-switchover’ is enabled on the system, two optimizations are performed to the LACP behavior:
• The wait-while timer is not started in the ‘waiting’ state of the MUX state machine. The port moves directly to the ‘attached’ state.
• The local system moves to the ‘collecting’ and ‘distributing’ states on the port in a single step without waiting for the partner to set
the ‘collecting’ bit.
RDMA Over Converged Ethernet (RoCE) Overview
Remote direct memory access (RDMA) is a technology that a virtual machine (VM) uses to directly transfer information to the memory of
another VM, thus enabling VMs to be connected to storage networks. With RDMA over converged Ethernet (RoCE), RDMA enables data
to be forwarded without passing through the CPU and the main memory path of TCP/IP. In a deployment that contains both the RoCE
network and the normal IP network on two different networks, routable RoCE (RRoCE) combines the RoCE and the IP networks and
sends the RoCE frames over the IP network. RRoCE transmission results in the encapsulation of RoCE packets in IP packets.
RRoCE packets are received and transmitted on specific interfaces called lite-subinterfaces. These interfaces are similar to the normal
Layer 3 physical interfaces except for the extra provisioning that they offer to enable the VLAN ID for encapsulation.
You can configure a physical interface or a Layer 3 Port Channel interface as a lite subinterface. When you configure a lite subinterface,
only tagged IP packets with VLAN encapsulation are processed and routed. All other data packets are discarded.
To provide lossless service for RRoCE, the QoS service policy must be configured in the ingress and egress directions on lite
subinterfaces.
A normal Layer 3 physical interface processes only untagged packets and makes routing decisions based on the default Layer 3 VLAN ID
(4095).
To enable routing of RRoCE packets, the VLAN ID is mapped to the default VLAN ID of 4095 using VLAN translation. After the VLAN
translation, the RRoCE packets are processed in the same way as normal IP packets that a Layer 3 interface receives and routes in the
egress direction. At the egress interface, the VLAN ID is appended to the packet and transmitted out of the interface as a tagged packet
with the dot1Q value preserved.
When a storage area network (SAN) is connected over an IP network, the following conditions must be satisfied:
• Faster Connectivity: QoS for RRoCE enables faster and lossless nature of disk input and output services.
Flex Hash and Optimized Boot-Up
355