Cisco Systems OL-12518-01 TCP Window Size, TCP Maximum Bandwidth, TCP Minimum Available Bandwidth

Page 9

Chapter 4 FCIP over IP/MPLS Core

Using FCIP Tape Acceleration

TCP window size

TCP maximum bandwidth

TCP minimum available bandwidth

Round Trip Time (RTT)

TCP Window Size

TCP uses a sliding window to control the flow of data from end to end. The TCP maximum window size (MWS) is the maximum amount of data the sender allows to be outstanding without acknowledgment at one time. The minimum MWS is 14 KB; the maximum is 32 MB.

The sender can use a larger window size to allow more outstanding data and to make sure that the pipe remains full. However, sending too much data at once can overrun intermediate routers, switches, and end devices. The TCP congestion control manages changes to the window size.

You cannot configure the TCP window size directly. This value is automatically calculated from the product of the maximum bandwidth x RTT x 0.9375 + 4 KB. In SAN-OS 1.3 and later, the RTT can dynamically adjust up to four times the configured value in the FCIP profile according to network conditions. The TCP sender dynamically changes the maximum window size accordingly.

TCP Maximum Bandwidth

The TCP maximum bandwidth is the maximum amount of bandwidth an FCIP link consumes from the point of view of the TCP sender. The maximum bandwidth settings for an FCIP link can be asymmetric. Set the TCP maximum bandwidth to the maximum amount of bandwidth you want the FCIP link to consume. Set it no higher than the bandwidth of the slowest link in the FCIP link path. For example, if the FCIP link is mapped over a dedicated DS3 WAN link, set the maximum bandwidth to 45 Mbps.

The TCP maximum bandwidth value is used as the bandwidth value in the bandwidth-delayproduct calculation of the TCP MWS.

Observe the following guidelines when selecting a value for TCP maximum bandwidth:

Set the TCP maximum bandwidth value no higher than the maximum path bandwidth available to the FCIP.

If deploying FCIP over a shared link with critical traffic, lower the maximum bandwidth to a level that allows the other traffic to coexist with minimal retransmissions. Quality of service (QoS) should be considered in these situations.

When using the Cisco MDS 9000 software compression, set the maximum bandwidth value as though compression is disabled. The Cisco MDS 9000 uses a dynamic moving average feedback mechanism to adjust the TCP window size according to the compression rate.

TCP Minimum Available Bandwidth

The value should represent the minimum amount of bandwidth in the FCIP path that you expect to be always available. This value determines the aggressiveness of FCIP—a higher value is more aggressive, a lower value is less aggressive. A value that is too high can cause congestion and packet drops for any traffic traversing the shared network links.

Bandwidth allocation strongly favors the FCIP traffic when mixed with conventional TCP traffic, which recovers from drops more slowly. To cause FCIP to behave more fairly, use a lower value for the min-available-bwparameter. FCIP starts at a lower rate and increments the send rate every RTT, just like classic TCP slow-start.

Data Center High Availability Clusters Design Guide

 

OL-12518-01

4-9

 

 

 

Image 9
Contents A P T E R OverviewSAN Extension Through SP Network Typical Customer RequirementsCompression Support in Cisco MDS CompressionCompression Modes and Rate 2shows a comparison of the Cisco compression solutionsSecurity Cisco Compression Solutions VPNSM-DES, 3DES MDS MPS-DES, 3DES, AES192 Cisco Encryption SolutionsWrite Acceleration Using Fcip Tape AccelerationTCP Parameters TCP OperationsTCP Window Size TCP Maximum BandwidthTCP Minimum Available Bandwidth Cisco Round Trip TimeIPS Module Cisco Fcip Cisco MDSCPE Selection-Choosing between the 9216i Multiprotocol Services ModuleQoS Requirements in Fcip Applications Synchronous ReplicationAsynchronous Replication Service Offering Scenario A-Disaster Recovery Service Offerings over FcipFcip over SP IP/MPLS Core for Disaster Recovery Solutions Service Offering Scenario B-Connecting Multiple SitesSP Mpls Service Offering Scenario C-Host-based MirroringCPE Mpls VPN CoreMpls VPN for Storage Architecture Using VRF VPNsTesting Scenarios and Results Lab Setup and TopologyTest Objectives MP BGP Configuration-PE1 VPN VRF-Specific ConfigurationsVRF Configuration-PE1 Gigabit Ethernet Interface Configuration-PE1MP BGP Configuration-PE2 Gigabit Ethernet Interface Configuration-PE2Scenario 1-MDS 9216i Connection to GSR Mpls Core VRF Configuration-PE2Configuring the MTU Configuring TCP Parameters on CPE Cisco MDSThroughput Scenario 2-Latency Across the GSR Mpls CoreScenario 3-Cisco MDS 9216i Connection to Cisco 7500 PE/GSR P Scenario 5-Impact of Core Performance Scenario 4-Impact of Failover in the Core17shows the MDS Fcip and compression latency Compression Ratio Comparisons Application RequirementsConclusion Remote Tape-Backup Applications