Technical data

VSPEX Configuration Guidelines
VMware Horizon View 5.3 and VMware vSphere for up to 2,000 Virtual
Desktops Enabled by Brocade Network Fabrics, EMC VNX, and EMC Next-
Generation Backup
138
Brocade VDX Series switches support the transport of jumbo frames. This
solution recommends an MTU setting at 9216 (Jumbo frames) for efficient
NAS storage and migration traffic. Jumbo frames are enabled by default
on the Brocade ISL trunks. However, to accommodate end-to-end jumbo
frame support on the network for the edge systems, this feature can be
enabled under the vLAG interface. Please note that for end-to-end flow
control, Jumbo frames need to be enabled both on the host servers and
the storage with the same MTU size of 9216.
Configuring MTU
Note: This must be performed on all RBbridges where a given interface
port-channel is located. In this example, interface port-channel 44 is on
RBridge 21 and RBridge 22, so we will apply configurations from both
RBridge 21 and RBridge 22.
Example to enable Jumbo Frame Support on applicable VDX interfaces for
which Jumbo Frame support is required:
BRCD6740-RB21# configure terminal
BRCD6740-RB21(config)# interface Port-channel 44
BRCD6740-RB21(config-Port-channel-44)# mtu
(<NUMBER:1522-9216>) (9216): 9216
Ethernet Flow Control is used to prevent dropped frames by slowing traffic
at the source end of a link. When a port on a switch or host is not ready to
receive more traffic from the source, perhaps due to congestion, it sends
pause frames to the source to pause the traffic flow. When the congestion
is cleared, the port stops requesting the source to pause traffic flow, and
traffic resumes without any frame drop. It is recommended to enable Flow
Control on vLAG interfaces towards the VNX on the VDX 6740s, as shown:
Enable QOS Flow Control for both tx and rx on RB21 and RB22
BRCD6740-RB21# conf t
BRCD6740-RB21 (config)# interface Port-channel 33
BRCD6740-RB21 (config-Port-channel-33)# qos flowcontrol tx on rx
on
The Auto QoS feature introduced in NOS v4.1.0 automatically classifies
traffic based on either a source or a destination IPv4 address. Once the
traffic is identified, it is assigned to a separate priority queue. This allows a
minimum bandwidth guarantee to be provided to the queue so that the
identified traffic is less affected by network traffic congestion than other
traffic.