Cisco Systems OL-12518-01 manual Configuring TCP Parameters on CPE Cisco MDS, Configuring the MTU

Page 24

Chapter 4 FCIP over IP/MPLS Core

Testing Scenarios and Results

Figure 4-11 Cisco MDS 9216i Connection to GSR MPLS Core

GSR 12410

GSR 12410

Provider Core

Provider Core

GSR 12410

Provider Core

GSR 12410

PE

Gigabit

Serial/DS3/DS1Ethernet/POS/

GSR 12410

PE

 

Ethernet/POS/

Gigabit

Serial/DS3/DS1

 

10.10.10.1

11.11.11.1

132430

Configuring TCP Parameters on CPE (Cisco MDS 9216)

A simple ping command from the Cisco MDS 9000 CLI, provides the RTT between the two IP addresses. RTT is specified as part of the following configuration command. It may be specified in either microseconds (-us suffix) or in milliseconds (-ms suffix).

The following command shows RTT set for 20 milliseconds:

tcp max-bandwidth-mbps XXXX min-available-bandwidth-mbps xxxx round-trip-time-ms 20

Configuring the MTU

The MTU is the maximum payload the Gigabit Ethernet interface will handle. The default MTU for the Gigabit Ethernet interface is 1500, which does not include Ethernet headers and trailers.

The maximum Fibre Channel frame size including headers and trailers is 2148 bytes. Fibre Channel data frames in typical storage applications have a payload of 2048 bytes plus 36 bytes in headers and trailers, leaving a frame size of 2084 bytes. The Cisco MDS 9000 optionally adds two headers to the Fibre Channel frame. The EISL header is an eight-byte field carrying VSAN tagging information that is only added if the FCIP interface is defined as a TE_Port. If the EISL header is present, it is located immediately after the four-byte start-of-frame (SOF) sequence. There is also an optional header (up to 16 bytes) that is reserved for future use.

With the inclusion of EISL and optional headers, the maximum Fibre Channel frame size is 2172 bytes. An FCIP packet over Ethernet includes 94 to 98 bytes of headers, plus a four-byte Ethernet CRC32 trailer. When carrying the maximum size Fibre Channel frame, the maximum Ethernet frame size is 2274 bytes (2172 + 98 + 4 = 2274).

 

Data Center High Availability Clusters Design Guide

4-24

OL-12518-01

Image 24
Contents Overview A P T E RTypical Customer Requirements SAN Extension Through SP NetworkCompression Compression Support in Cisco MDS2shows a comparison of the Cisco compression solutions Compression Modes and RateCisco Compression Solutions SecurityCisco Encryption Solutions VPNSM-DES, 3DES MDS MPS-DES, 3DES, AES192Using Fcip Tape Acceleration Write AccelerationTCP Operations TCP ParametersTCP Window Size TCP Maximum BandwidthTCP Minimum Available Bandwidth Cisco Round Trip TimeIPS Module Cisco MDS Cisco FcipMultiprotocol Services Module CPE Selection-Choosing between the 9216iQoS Requirements in Fcip Applications Synchronous ReplicationAsynchronous Replication Service Offerings over Fcip Service Offering Scenario A-Disaster RecoveryService Offering Scenario B-Connecting Multiple Sites Fcip over SP IP/MPLS Core for Disaster Recovery SolutionsService Offering Scenario C-Host-based Mirroring SP MplsMpls VPN Core CPEUsing VRF VPNs Mpls VPN for Storage ArchitectureTesting Scenarios and Results Lab Setup and TopologyTest Objectives VPN VRF-Specific Configurations MP BGP Configuration-PE1Gigabit Ethernet Interface Configuration-PE1 VRF Configuration-PE1MP BGP Configuration-PE2 Gigabit Ethernet Interface Configuration-PE2VRF Configuration-PE2 Scenario 1-MDS 9216i Connection to GSR Mpls CoreConfiguring TCP Parameters on CPE Cisco MDS Configuring the MTUScenario 2-Latency Across the GSR Mpls Core ThroughputScenario 3-Cisco MDS 9216i Connection to Cisco 7500 PE/GSR P Scenario 4-Impact of Failover in the Core Scenario 5-Impact of Core Performance17shows the MDS Fcip and compression latency Application Requirements Compression Ratio ComparisonsRemote Tape-Backup Applications Conclusion