DOCSLIB.ORG

Performance Analysis of Iscsi Over TCP Versus SCTP

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Performance Analysis of Iscsi Over TCP Versus SCTP Performance Analysis of iSCSI Over TCP versus SCTP THESIS Submitted to the Faculty of Graduare Srudies In Partial FulfrILment of the Requirements for the Degree of MASTER OF SC/ENCE Department of Electrical and Computer Engineering, University of Manitoba Dong Zhang December 2001 THE UNTVERSITY OF MANITOBA FACULTY OF G*RADUATE STUDIES COPYRIGHT PERMISSION Performance Analysis of iSCSI Over TCP versus SCTP BY Dong Zhang A ThesislPracticum submitted to the Faculty of Graduate Studies of The University of Manitoba Ín partial fulfillment of the requirement of the degree MASTER OF SCIENCE Doug Zhang@ 2007 Permission has been granted to the University of Manitoba Libraries to lend â copy of this thesis/practicum, to Library and Archives Canada (LAC) to lend a copy of this thesis/practicum, and to LAC's agent (UMVProQuest) to microfilm, sell copies and to publish an abstract of this thesis/practicum. This reproduction or copy of this thesis has been made available by authority of the copyright owner solely for the purpose of private study and research, and may only be reproduced and copied as permitted by copyright laws or with express written authorization from the copyright owner. Abstract IP SANs (storage area networks) have become increasingly common in today's storage industry. Internet SCSI (iSCSI) [21] is a block level protocol defined by the IP Storage work group of IETF (in RFC3720). iSCSI encapsulates SCSI commands and Data for transfer over an IP network and thereby takes advantage of the investment in existing IP networks to facilitate and extend SANs. iSCSl-based IP SANs allow us ro reduce initial cosrs and the management costs of storage. Conceptually, iSCSI is designed to run over TCP/IP that provides Layer 3/4 network transport. SCTP (Stream Control Transmission Protocol) [23] is a relatively new IETF stan- dard transport protocol. SCTP was originally developed to transport Public Switched Tele- phone Network (PSTN) signaling messages over IP networks, but it has emerged as a general- purpose transport protocol. SCTP is a reliable message oriented protocol that combines certain desirable qualities of TCP and UDP and provides additional services unavailable from TCP (or UDP) as well. Attractive features of SCTP such as multistreaming and multihoming make it an alternative to TCP for many applications. In this thesis, we focus primarily on a performance study comparing SCTP and TCP as the underlying transport layer protocol for iSCSI using ns2 simulation. The results of simulation and performance analysis indicate that iSCSI over SCTP has advantages over TCP in the scenarios investigated. Acknowledgments First of all, I would like to thank my adviso¡ Dr. Robert D. Mcleod for his guidance and support throughout the entirety of my work on this subject. Our discussions helped me overcome many obstacles that came up. I would also like to thank Sajid who helped me a lot. I feel lucky for having the chance to work with him. Many thanks go also to committee members: Dr. Peter Graham and Dr. Jun Cai, for their valuable comments and suggestions. Finally, I want to thank my lovely wife, Yu, my sister, Cong, and my parent for their support during all these years. Also my daughter, Kyleen, who is and will always be a source of inspiration for me. Contents Glossary I Introduction r0 iSCSI 13 2.1 Protocol Model l3 2.2 Session Management l3 2.2.1 Login 15 2.2.2 Full Feature Phase 15 2.2.3 Shutdown 17 2.3 Sequencing l7 2.3.1 CommandNumbering t7 2.3.2 Status Numbering l8 2.3.3 Data Numbering l8 2.4 Name and Address l9 2.5 PDU Format . 19 2.5.1 Basic Header Segment (BHS) 20 2.6 Message Framing 20 2.6.1 Fixed Interval Markers 2l 2.6.2 Marker PDU Aligned Framing 22 2.7 Error Handling and Recovery 22 2.8 Summary 23 Tiansport Protocols 24 3.1 The Transport Layer in the OSI Model 24 3.2 User Datagram Protocol (UDP) 26 3.3 Transmission Control Protocol (TCP) 27 3.3.1 Header Format 27 3.3.2 Flow Control and Congestion Control 29 3.4 Stream Control Transmission Protocol (SCTP) 3t 3.4.1 Packets 3l 3.4.2 Association Establishment 32 3.4.3 Multihoming... 35 1.4.4 Multistreaming 36 3.4.5 Flow and Congestion Control 37 3.5 Comparison between Transport Layer Protocols 38 3.6 Summary 38 Simulation Design and Implementation 40 4.1 Network Simulator (ns2) 40 4.2 iSCSI Implementation 4l 4.2.1 Overview of iSCSI Classes 42 4.2.2 Write Command Simulation 44 4.2.3 Read Command Simulation 46 4.3 Introduction to the SCTP Implementation 46 4.3.1 MultihomingSimulation 47 4.4 iSCSI Over TCP Simulation Component Implemenration 48 4.4.1 Agent V/rapper and Message Boundaries Simulation 48 4.4.2 Tcl Script: iSCSI-MPA-TCP . 49 4.5 iSCSI Over SCTP Simulation Component Implementation 50 4.6 Summary 52 5 Performance Analysis 53 5.1 Performance Metrics and Variables 53 5.2 Command Completion Time (no loss) 55 5.3 Throughput in a Lossy Network 56 5.3.1 Head-of-LineBlocking 56 ' 5.3.2 Throughput vs. Loss Rate 56 5.4 Reliability 58 5.5 Security 61 5.6 Summary 62 6 Related Work 7 Conclusions and Future Work 65 7.1 Conclusions 65 1.2 Future Work 66 List of Figures 2.1 iSCSI protocol layering model. l4 2.2 Text Operational Keys r6 2.3 Basic Header Segment (48 Bytes). 20 2.4 List of opcodes 21 3.1 OSI reference model. 25 3.2 UDP datagram. 26 3.3 TCP three-way handshake. 2l 3.4 TCP segment. 28 3.5 SCTP packet format. 32 3.6 SCTP chunk types and description. JJ 3.7 SCTP association establishment. 34 3.8 SCTP's multihoming feature 35 3.9 SCTP's multistreaming feature 36 4.1 Application Class 42 4.2 The class hierarchy of the iSCSI simulation classes. 43 4.3 iSCSI'Write (a) and Read (b) command execurion. 45 4.4 Simulation of iSCSVMPA/TCP in ns2. 49 4.5 A simulation script of iSCSVMPA/TCP. 50 4.6 Parameters of the SCTP-aware application data. 5l 4.7 Simulation of iSCSI over SCTP (singlehomed) in ns2. 51 4.8 Simulation of iSCSI over SCTP (multihomed) in ns2. 5l 5.1 Comparison of UDP, TCP, and SCTP. 53 5.2 The command completion time for various command sizes under no loss net- work 55 5.3 TCP's Head-Of-Line blocking problem and SCTP's multisrreaming feature 57 5.4 Throughput performance in loss network 57 5.5 Default value of parameters for failover system. 58 5.6 iSCSI over SCTP with Multihoming (a) 59 5.7 iSCSI over SCTP with Multihoming (b) 60 5.8 iSCSI over SCTP with Multihoming (c) 60 5.9 iSCSI over SCTP with Multihoming (d) 61 5.r0 Protection against DoS attacks by four way handshake 62 6 Glossary The list of acronyms and other related terms are described here. ACK Acknowledgement ADU Application Data Unit AHS Additional Header Segment BHS Basic Header Segment CmdSN Command Sequence Number CRC Cyclic Redundancy Check DataSN Data Sequence Number DDP Direct Data Placement EDTL Expected Data Transfer Length EMSS Effective Maximum Segment Size ExpCmdSN Expected Command Sequence Number ExpDataSN Expected Data Sequence Number ExpStatSN Expected Status Sequence Number FC Fibre Channel FCIP Fibre Channel over Internet Protocol FFP full-Feature Phase FFPO Full-Feature Phase Only FIM Fix Interval Marker FPDU Framing Protocol Data Unit Gbps Gigabit per second iFCP Internet Fibre Channel Protocol UO Input/Output IO Initialize Only IP Internet Protocol ips IP storage IPsec/IPSec Internet Protocol Security rqn iSCSI qualified name iSAN iSCSI-based Storage Area Network iSER iSCSI Extension for RDMA iSCSÌ SCSI over IP ISID Initiator Session ID I-T Initiator-Target I_TI Initiator-TargetIUN ITN iSCSI Target Node or iSCSI Target Name I1"T Initiator Task Tag LAN Local A¡ea Network LBA Logical Block Address LO leading Only LONP Login Operational Negotiation Phase LU Logical Unit LUN Logical Unit Number MAN Metropolitan Area Network MaxCmdSN Maximum Command Sequence Number MC/S Multiple Connections per Session MD-5 Message Digest version 5 MPA Markers PDU Aligned MSS Maximum Segment Size MTU Maximum Transfer Unit NA Not Applicable NAS Network Attached Storage NFS Network File System NIC Network Interface Card NOP No Operation NSG Next Stage OS Operating System PDU Protocol Data Unit R2T Ready to Transfer R2TSN Ready to Transfer Sequence Number RDMA Remote Direct Memory Access RFC Request for Comments SAM SCSI Architectural Model SAM2 SCSI Architectural Model 2 SAN Storage Area Network SCSI Small Compurer Systems Inrerface SCTP Stream Transmission Control Protocol SID Stream ID SN Sequence Number SNACK sequence Number Acknowledgement or selective Negative Ac- knowledgement SSID Session ID SSN Stream Sequence Numbers StatSN Status Sequence Number TCB Task Control Block TCP Transmission Control Protocol TOE TCP/IP Offload Engineer TSID Target Session ID TSIH Target Session Identifying Handle TSN Transmission Sequence Number TUF TCP Upper-Level-Protocol Framing TTT Target Transfer Tag UDP User Datagram Protocol ULP Upper Level Protocol or Upper Layer Protocol ULPDU Upper Layer Protocol Data Unit URL Uniform Resource Locator URN Uniform Resource Name UTF Universal Transform ati on Format VPN Virtual Private Network WAN Wide Area Network WG Working Group Chapter 1 Introduction A Storage Area Network (SAN) is a network dedicated to transporting data for storage and retrieval. SANs have been proven to increase the performance and availability of corporate storage resources. A SAN can be deployed in two ways: using Fiber Channel or IP.
Load more

Recommended publications
  • EMC Host Connectivity Guide for Oracle Solaris
    Dell EMC Host Connectivity Guide for Oracle Solaris P/N 300-000-607 REV 56 MAY 2020 Copyright © 2007 – 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.” DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE. Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the propertyof their respective owners. Published in the USA. Dell EMC Hopkinton, Massachusetts 01748-9103 1-508-435-1000 In North America 1-866-464-7381 www.DellEMC.com 2 Dell EMC Host Connectivity Guide for Oracle Solaris CONTENTS Preface ....................................................................................................................................... 13 Part 1 Connecting Solaris to Dell EMC Storage Chapter 1 Solaris Operating System Solaris operating system overview........................................................................ 20 Multipathing software ........................................................................................... 21 MPxIO/STMS ...............................................................................................
    [Show full text]
  • Fibre Channel and Iscsi Configuration Guide for the Data ONTAP® 8.0 Release Family
    Fibre Channel and iSCSI Configuration Guide for the Data ONTAP® 8.0 Release Family NetApp, Inc. 495 East Java Drive Sunnyvale, CA 94089 U.S. Telephone: +1 (408) 822-6000 Fax: +1 (408) 822-4501 Support telephone: +1 (888) 463-8277 Web: www.netapp.com Feedback: [email protected] Part number: 215-08164_A0 August 2013 Table of Contents | 3 Contents iSCSI configurations .................................................................................... 6 Single-network HA pair in an iSCSI SAN .................................................................. 6 Multi-network HA pair in an iSCSI SAN ................................................................... 7 Direct-attached single-controller configurations in an iSCSI SAN ............................ 8 VLANs for iSCSI configurations ................................................................................ 9 Static VLANs ................................................................................................ 10 Dynamic VLANs ........................................................................................... 10 Fibre Channel configurations .................................................................... 11 FC onboard and expansion port combinations .......................................................... 11 Fibre Channel supported hop count .......................................................................... 12 Fibre Channel supported speeds ................................................................................ 13 Fibre Channel switch
    [Show full text]
  • Iscsi Testing: What Are the Test Challenges Under the Hood of a 10 Gb Iscsi Storage Product Certification?
    iSCSI testing: What are the test Challenges Under the Hood of a 10 Gb iSCSI Storage Product Certification? Dr. M. K. Jibbe Distinguished Engineer Manager and Technical Lead of Test Architect and Product Certification in India LSI Corporation (Engenio Storage Group) Storage Developer Conference 2009 © 2009 Insert Copyright Information Here. All Rights Reserved. 1 Abstract iSCSI RAID Storage Testing The certification of a 10 Gb iSCSI RAID Storage System elicits a lot of challenges at the development level and the Test / Quality Assurance level. The challenges are due to the fact that a 10 Gb iSCSI is a newly deployed iSCSI host interface in the RAID Storage environment. As a result the size of a development module level test should be designed very carefully to establish a test coverage beyond basic implementation verification, standard RAID testing, or the iSCSI plug fest. These module level tests must tackle the test time windows associated with the following iSCSI characteristics: NIC vs. CNA Device discovery, 10 GB switch traffic control and congestion, Security mechanisms with different Operating systems, Operational parameters associated with I/O retries and recovery Management, Administration, and Integration with Storage products Design For Testability “DFT” mechanisms Diagnostics, problem Isolations IPV4 vs. IPV6 However a number of the module tests above can be leveraged from the certification a 1 Gb iSCSI RAID products. There are specific features such as backup, snapshot, remote mirroring, and cluster application compatibility that must be supported by the RAID product and must be verified during the testing of the RAID controller host interface. Storage Developer Conference 2009 © 2009 Insert Copyright Information Here.
    [Show full text]
  • Iscsi SAN Configuration Guide Update 2 and Later for ESX Server 3.5, ESX Server 3I Version 3.5, Virtualcenter 2.5 Iscsi SAN Configuration Guide
    iSCSI SAN Configuration Guide Update 2 and later for ESX Server 3.5, ESX Server 3i version 3.5, VirtualCenter 2.5 iSCSI SAN Configuration Guide iSCSI SAN Configuration Guide Revision: 20090313 Item: EN-000035-01 You can find the most up-to-date technical documentation on our Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected] © 2007–2009 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws. VMware products are covered by one or more patents listed at http://www.vmware.com/go/patents. VMware, the VMware “boxes” logo and design, Virtual SMP and VMotion are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc. Contents About This Book 7 1 Using ESX Server with a Storage Area Network 11 Understanding Virtualization 12 Network Virtualization 12 Storage Virtualization 12 Storage Area Network Concepts 15 Ports 16 Multipathing and Path Failover 17 Storage System Types 17 Target Compared to LUN Representations 17 iSCSI Naming Conventions 19 Overview of Using ESX Server with a SAN 20 Benefits of Using ESX Server with a SAN 20 Use Cases 21 Finding SAN Configuration Information 21 Basics of Using SAN Storage Systems with an ESX Server 22 Network Configuration and Authentication 22 Sharing a VMFS Across ESX Servers 22 Metadata Updates 24 Volume Display and Rescan 24 Levels of Indirection 24 Data Access: VMFS or RDM 25 Third‐Party Management Applications 26 Discovery, Authentication, and Access Control 26 Error Correction 27 Understanding VMFS and SAN Storage Choices 27 Choosing Larger or Smaller LUNs 27 Making LUN Decisions 28 Tips for Making LUN Decisions 29 VMware, Inc.
    [Show full text]
  • Oce14000 10Gbe and 40Gbe Converged Network Adapters And
    CONNECTCONNECT - DATA - DATA SHEET SHEET OCe14000OCe14000 10GbE 10Gb andand 40GbE40Gb ConvergedEthernet Network Network Adapters Adapters High Performance Networking for Enterprise Virtualization and the Cloud High Performance Networking for Enterprise Virtualization and the Cloud OneConnectOneConnect OCe14000 OCe14000 Family Family Overview Key benefits As theOverview fourth generation of the Emulex OneConnect product line, the OCe14000 Key benefits As the fourth generation of the Emulex OneConnect® product line, the OCe14000 n Maximizes server hardware ROI with high virtual family of Converged Network Adapters (CNAs) provides high performance 10Gb n Maximizes server hardware ROI with high family of Ethernet network adapters provides high performance 10Gb Ethernet machine density Ethernet (10GbE) and 40GbE connectivity delivering multiple benefits for the virtual machine density (10GbE) and 40GbE connectivity delivering multiple benefits for the enterprise enterprise cloud, including: n Simplifies deployment of secure, scalable multi- cloud, including: tenantn cloudSimplifies infrastructures deployment of secure, scalable multi- n Increasing data center IT agility and scalability through deployment of a secure n Increasing data center IT agility and scalability through deployment of a secure tenant cloud infrastructures multi-tenant cloud n multi-tenant cloud Minimizes TCO through deployment of heterogeneousn Accelerates workloads applications on Converged performance n Driving scalability and flexibility in converged infrastructures
    [Show full text]
  • Feature-Rich and Fast SCSI Target with CTL and ZFS
    Feature-rich and fast SCSI target with CTL and ZFS Alexander Motin <[email protected]> iXsystems, Inc. RuBSD'2014 CTL – CAM Target Layer Frontends Backends isp0 FC CAM target device CAM SCSI CAM SIM initiator block zvol CTL core ... file TCP ICL iSCSI iSCSI target ramdisk /dev/zero offload CTL functional improvements ... for intelligent performance ●I/O optimization for storage specifics ●Thin-/Resource-provisioning ●I/O offload CTL functional improvements Basic SCSI disk (CTL in early 2014): ●READ CAPACITY(10) ● Get block size and number of blocks ●READ ● Read range of blocks ●WRITE ● Write range of blocks # diskinfo -v /dev/da0 /dev/da0 512 # sectorsize 107374182400 # mediasize in bytes (100G) 209715200 # mediasize in sectors CTL functional improvements Advanced Format (512e) SCSI disks: ●READ CAPACITY(16) ● Get physical block size and offset # diskinfo -v /dev/da0 /dev/da0 512 # sectorsize 107374182400 # mediasize in bytes (100G) 209715200 # mediasize in sectors 8192 # stripesize 0 # stripeoffset CTL functional improvements Basic thin-provisioned disks: ●Logical Block Provisioning VPD VAAI TP Reporting ● Get Supported UNMAP commands ●Block Limits VPD page ● Get UNMAP block size ● Get UNMAP parameters limitations ●WRITE SAME with UNMAP ● Unmap sequential range of blocks ●UNMAP VAAI Unmap ● Unmap arbitrary list of blocks ●Proper overflow error reporting VAAI TP Stun CTL functional improvements Featured thin-provisioned disk: ●GET LBA STATUS ● Get provisioning status of specific block(s) Windows defrag CTL functional improvements Featured
    [Show full text]
  • The Rise & Development of Illumos
    Fork Yeah! The Rise & Development of illumos Bryan Cantrill VP, Engineering [email protected] @bcantrill WTF is illumos? • An open source descendant of OpenSolaris • ...which itself was a branch of Solaris Nevada • ...which was the name of the release after Solaris 10 • ...and was open but is now closed • ...and is itself a descendant of Solaris 2.x • ...but it can all be called “SunOS 5.x” • ...but not “SunOS 4.x” — thatʼs different • Letʼs start at (or rather, near) the beginning... SunOS: A peopleʼs history • In the early 1990s, after a painful transition to Solaris, much of the SunOS 4.x engineering talent had left • Problems compounded by the adoption of an immature SCM, the Network Software Environment (NSE) • The engineers revolted: Larry McVoy developed a much simpler variant of NSE called NSElite (ancestor to git) • Using NSElite (and later, TeamWare), Roger Faulkner, Tim Marsland, Joe Kowalski and Jeff Bonwick led a sufficiently parallelized development effort to produce Solaris 2.3, “the first version that worked” • ...but with Solaris 2.4, management took over day-to- day operations of the release, and quality slipped again Solaris 2.5: Do or die • Solaris 2.5 absolutely had to get it right — Sun had new hardware, the UltraSPARC-I, that depended on it • To assure quality, the engineers “took over,” with Bonwick installed as the gatekeeper • Bonwick granted authority to “rip it out if itʼs broken" — an early BDFL model, and a template for later generations of engineering leadership • Solaris 2.5 shipped on schedule and at quality
    [Show full text]
  • Using Oracle ZFS Storage Appliance Fibre Channel and Iscsi with Symantec Storage Foundation/DMP Quickstart Guide
    September 2014 Using Oracle ZFS Storage Appliance Fibre Channel and iSCSI with Symantec Storage Foundation/DMP Quickstart Guide Using Oracle ZFS Storage Appliance Fibre Channel and iSCSI with Symantec Storage Foundation / DMP Overview ............................................................................................. 3 Hardware and Software Requirements ............................................... 3 Configuring Oracle Solaris with Symantec Storage Foundation for Fibre Channel and iSCSI ............................................................... 4 Configuring Linux with Symantec Storage Foundation for Fibre Channel ...................................................................................... 5 Setting the Red Hat Compatible Kernel as Default ......................... 5 Loading the scsi_dh_alua Module During Boot on Linux ........... 5 Creating a UDEV Rule on Linux ...................................................... 6 Installing Required Storage Foundation Patches ................................ 6 Required Storage Foundation 5.x/6.x Patches ............................... 6 Required Storage Foundation Patch for Oracle Solaris and Red Hat Linux Operating Systems ......................................................... 6 Required Storage Foundation Patch for Microsoft Windows Operating Systems ................................................................................. 7 Required Storage Foundation 5.x/6.x ASL/APM Package .............. 7 Required Storage Foundation 5.x/6.x DMP Parameter Settings ....
    [Show full text]
  • Iscsi Will Still Be Widely Deployed for at Least the Next Few Years, but Its Growth Prospects Beyond That Are Very Unclear
    Widespread use and support mean iSCSI will still be widely deployed for at least the next few years, but its growth prospects beyond that are very unclear. By John F. Kim, Chair, SNIA Networking Storage Forum. What is iSCSI? iSCSI is a block storage protocol for storage networking. It stands for “Internet Small Computer Systems Interface” and runs the very common SCSI storage protocol across a network connection which is usually Ethernet with TCP. You can read more about iSCSI at the “What Is” section of the SNIA website. (The SCSI storage protocol is also used to access block storage as part of the SAS, SRP, and FCP protocols, which run over various physical connections.) Originally, the SCSI protocol was used only for local storage, meaning individual disk drives or direct-attached storage (DAS). Then around 1993, Fibre Channel came along and enabled SCSI to run the Fibre Channel Protocol (FCP) on top of a Fibre Channel Storage Area Network (FC-SAN). iSCSI was submitted as a standard in 2000 and grew in popularity as it was supported by more operating systems, first requiring dedicated iSCSI HBAs but later using a software iSCSI initiator that ran on top of any type of Ethernet NIC. The dedicated iSCSI HBAs gave iSCSI faster performance that was closer to Fibre Channel performance at the time, while the software iSCSI initiator made it easy to use iSCSI from many servers without buying special HBAs for each server. Probably the biggest boost to iSCSI adoption was when Microsoft Windows Server 2008 included a software iSCSI initiator 1/6 (starting in 2008, of course).
    [Show full text]
  • High Performance Iscsi at 40Gbe
    High Performance iSCSI at 40GbE Chelsio T5 iSCSI solution delivering 5M IOPS Executive Summary The demonstration shows Chelsio T5 cards enabling 5 million IOPS (input/output instructions per second) iSCSI performance for a cost-effective enterprise-class storage target solution built with volume, off-the-shelf hardware and software components. Showcasing the iSCSI hardware offload capabilities of the Chelsio T5 Unified Wire adapters, the demonstration shows how all-flash and hybrid storage array OEMs can easily enable such arrays with industry-leading iSCSI target performance. Fully compatible with the existing iSCSI ecosystem and seamlessly leveraging routable and reliable TCP/IP as a foundation, iSCSI allows highly scalable and cost effective installations using regular Ethernet switches. The Chelsio iSCSI Offload Solution The Terminator 5 (T5) ASIC from Chelsio Communications, Inc. is a fifth generation, high performance 4x10/2x40Gbps unified wire engine which offers storage protocol offload capability for accelerating both block (iSCSI, FCoE) and file (SMB, NFS) level storage traffic. Chelsio’s proven TCP Offload Engine (TOE), offloaded iSCSI over T5 enjoys a distinct performance advantage over regular NIC. The entire solution, which includes Chelsio’s iSCSI Offload software, the T5 adapter, and an off-the-shelf computer system – including a high end disk subsystem, provides industry leading performance, with both IOPS and bandwidth the highest available today. The resulting solution is highly competitive with special purpose systems and storage infrastructure currently on the market in both performance and cost. The Terminator 5 (T5) unified wire engine offers PDU iSCSI offload capability in protocol acceleration for both file and block‐level storage (iSCSI) traffic.
    [Show full text]
  • Iscsi-To-FC Bridge Ipbridge™ 2700 R/D
    Data Sheet iSCSI-to-FC Bridge iPBridge™ 2700 R/D The ATTO iSCSI to Fibre Channel bridge is a performance Technical Features tuned, highly manageable, intelligent protocol translator • Connects (4) Gigabit Ethernet iSCSI ports to (2) 4Gb Fibre Channel ports which allow iSCSI initiators to connect to FC targets • Windows®, Linux, Mac® (ATTO Xtend Performance Engineered SAN) iSCSI initiator compliance ATTO iPBridge™ products are engineered with an advanced architecture which provides • Gigabit iSCSI connectivity auto- high-performance by leveraging the latest hardware technology combined with ATTO’s negotiates to 10/100/1000 iSCSI intelligent bridging architecture. ATTO iPBridge products provide industry leading • MultiPath Director™ support available performance with value added features that have addressed customer connectivity needs for iSCSI and Fibre channel links for over 18 years. • Virtual LAN (VLAN) enhances security More than a Bridge while lessening the effort associated The iPBridge enables users to manage storage infrastructures with features not found in with managing larger networks direct connect technologies. Advanced read ahead and write cache algorithms in the • Access Control List (ACL) support to iPBridge give users the highest level of performance. Robust error processing enables the limit storage access to defined users iPBridge to manage disk and communication errors between targets and initiators. Email notification of errors and persistent error and trace logs assist troubleshooting in the field • Supports several device types including hard drives, tape drives and CD libraries to minimize downtime. Virtual Drive Response makes failed or incomplete tape backups a thing of the past. ACL and CHAP authenticate host machines at login, stopping • intelligent Bridging Architecture unauthorized users from accessing sensitive data.
    [Show full text]
  • The Netbsd Logical Volume Manager
    The NetBSD Logical Volume Manager Adam Hamsik The NetBSD Foundation [email protected] Abstract LVM is a method of allocating disk space on a disk storage devices. Which is more flexible than conventional ones. Logical Volume Manager can usually stripe, mirror or otherwise combine disk partitions to bigger virtual partitions which can be easily moved, resized or manipulated in different ways while in use. Volume Management is one form of disk storage virtualization used in Operating Systems. The NetBSD LVM has two parts user land tools and a kernel driver. Kernel driver is called device- mapper. User land part is based on Linux lvm tools developed by a community managed by Redhat inc. The Device-mapper driver can create virtual disk devices according to device table loaded to it. This table specifies which devices are used as a backend, on which offset on particular device virtual device starts. Device-mapper configuration is not persistent and must be loaded to kernel after each reboot by lvm the tools. 1 Introduction 2 Table of Contents 1. Introduction ........................................................................................................................................... 2 2. Background .......................................................................................................................................... 2 2.1. Volume Management Design .................................................................................................... 2 2.2. Volume Manager Features .......................................................................................................
    [Show full text]