DOCSLIB.ORG

Linux on System Z: Iscsi Initiator Configuration

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Linux on System Z: Iscsi Initiator Configuration Linux on System z: iSCSI Initiator Configuration Linux on System z: iSCSI Initiator Configuration Note Before using this information and the product it supports, read the information in “Notices” on page 27. Contents Figures ...............v Discovering iSCSI targets using Send Targets . 12 Logging in to discovered targets .......13 About this publication ........vii Logging out from targets ..........13 Discovering and logging in to targets using YaST (SUSE-specific) .............13 Chapter 1. Introduction ........1 Logging out from iSCSI targets using YaST iSCSI initiators and targets..........1 (SUSE-specific) .............19 Generating an iSCSI qualified name ......2 Automatic iSCSI target discovery and login (persistent across subsequent reboots) .....22 Chapter 2. Setting up iSCSI at the Avoiding data corruption or loss .......23 Storwize V7000 clustered system ....3 Creating an iSCSI host on Storwize V7000 ....3 References .............25 Mapping iSCSI volumes to the iSCSI host on the Storwize V7000 system ...........8 Notices ..............27 Trademarks ..............29 Chapter 3. Setting up iSCSI initiator Terms and conditions ...........29 software on Linux on System z ....11 Installing iSCSI initiator software on Linux on Index ...............31 System z ...............11 Setting the iSCSI qualified name for the Linux host 12 © Copyright IBM Corp. 2013 iii iv Linux on System z: iSCSI Initiator Configuration Figures 1. iSCSI architecture ...........1 12. Volume mapped successfully.......10 2. iSCSI host connection to Storwize V7000 over 13. List of iSCSI volumes with updated Host Ethernet network ...........2 Mappings information .........10 3. No iSCSI host on Storwize V7000 .....4 14. iSCSI Initiator Overview window .....14 4. Create Host window ..........4 15. iSCSI Initiator Discovery window .....15 5. Entering host name details ........5 16. iSCSI Initiator Discovery ........16 6. Adding iSCSI ports ..........6 17. Select No Authentication ........17 7. Port definitions............7 18. Target is connected ..........18 8. Create Host window - host is successfully 19. Connected targets ..........19 completed .............8 20. Connected Targets ..........20 9. Overview .............8 21. Click Continue to confirm log out. .....21 10. Listed iSCSI volumes..........9 22. Successful logout...........22 11. Mapped volumes ...........9 © Copyright IBM Corp. 2013 v vi Linux on System z: iSCSI Initiator Configuration About this publication This white paper describes the basic configuration of Internet Small Computer Systems interface (iSCSI) initiator when Storwize® V7000 used as a iSCSI target. This white paper is written on the basis of SUSE Linux Enterprise 11 SP2 and Red Hat Enterprise Linux 6.4 results. To provide a more complete picture of the configuration used in this white paper the iSCSI setup at Storwize V7000 is also briefly described. The following IBM® storage products support iSCSI: v IBM Storwize V7000 v IBM XIV® Storage System v IBM System Storage® DS5000 Series v IBM System Storage DS5020 Express® v IBM System Storage DCS3700 v IBM Storwize V3700 v IBM System Storage v DS3500 Express Linux on System z® supports the following SCSI transports: v Fibre Channel Protocol (FCP), mapping of SCSI over Fibre Channel v iSCSI, mapping of SCSI over TCP/IP FCP provides faster and more reliable access as compared to the iSCSI transport. But iSCSI is more cost effective than FCP. Scope of this document Advanced topics such as iSCSI multipath and iSCSI security are out of the scope of this document Note: Although multipathing is not described in this document, it is strongly recommended for production environments. Author Deepak P Joshi Linux on System z Prerequisites v Red Hat Enterprise Linux 6 or SUSE Linux Enterprise Server 11 distribution installed on System z with the network configured. There must be connectivity between the Linux system and Storwize V7000. Linux on System z supports the following types of network connection: – Network connections through Open Systems Adapter (OSA) - works in Layer-2 or Layer-3 mode – HiperSockets © Copyright IBM Corp. 2013 vii – GuestLAN – Virtual Switch Even though the above network connections are supported, the network connection must be configured through OSA either in Layer-2 or Layer-3 mode for the iSCSI configuration. In the z/VM® environment the Virtual Switch network connection with rdev option enabled can also be used for the iSCSI configuration. HiperSockets™ and GuestLAN network connections cannot be used for the iSCSI configuration. For more information about network connections with Linux on System z, see Device Drivers, Features and Commands: – Reference for SUSE Linux Enterprise Server 11 SP2: http://www.ibm.com/developerworks/linux/linux390/documentation_suse.html#sles11sp2 – Reference for Red Hat Enterprise Linux 6.4: http://www.ibm.com/developerworks/linux/linux390/documentation_red_hat.html#rhel64 v Storwize V7000 already configured with iSCSI LUNs and iSCSI target (iSCSI host object) created and mapped with iSCSI LUNs. v The IP address of the iSCSI portal and IQN of iSCSI target (iSCSI host object) at Storwize V7000 Restrictions v Storwize V7000 supports only one iSCSI session between an initiator and target at a time v There is no support for ipl'ng from Linux on system z viii Linux on System z: iSCSI Initiator Configuration Chapter 1. Introduction A brief introduction to the architecture of the Internet Small Computer System Interface (iSCSI) standard. iSCSI is a standard for IP-based (TCP/IP) storage networking, which allows SCSI commands to be transferred over an IP-based network. It also facilitates the block-level transfer of SCSI commands over IP (TCP/IP) network. The architecture of iSCSI is similar to that of a client/server architecture, where an initiator acts as the client that issues an I/O request and the target (a device in the storage system) acts as a server. Distance extension can be achieved by this architecture when used over IP networks. There are two kinds of iSCSI initiators: v Software-based initiator v Hardware-based initiator The software-based initiator is a driver that pairs the network interface driver and the SCSI block-level driver together to handle the iSCSI requests. A hardware-based initiator is an iSCSI Host Bus Adapter (HBA), which is similar to Network Interface Controller (NIC) with an on-board Application-Specific Integrated Circuit (ASIC) to offload iSCSI work from the system CPU. System z uses the software-based iSCSI initiator which in turn means it does not support the offloading of iSCSI work. TCP/IP network iSCSI initiator iSCSI target Figure 1. iSCSI architecture iSCSI initiators and targets A Network Interface Controller (NIC) on System z attached to an IP (TCP/IP) network acts as an iSCSI initiator which initiates I/O requests to and receives responses from iSCSI target. In this case the target is Storwize V7000. iSCSI targets are the devices, which provide the response to iSCSI commands received from the iSCSI initiators over the IP (TCP/IP) Network. On Storwize V7000, one or both of its node Ethernet ports are configured to become iSCSI target. Initiators and targets are given a unique ASCII name with a size of 233 bytes known as iSCSI Qualified Name (IQN). IQN is worldwide unique name which is used to identify each initiator and target. © Copyright IBM Corp. 2013 1 Figure 2. iSCSI host connection to Storwize V7000 over Ethernet network Figure 2 courtesy of Storwize V7000 Information Development. For more information about Storwize V7000, see: http://pic.dhe.ibm.com/infocenter/storwize/ic/index.jsp Generating an iSCSI qualified name A unique iSCSI qualified name (IQN) can be generated by the utility iscsi-iname and it is generated every time you invoke iscsi-iname. This IQN can be used to configure iSCSI initiator and the iSCSI target. Note: The IQN should be the same at both the iSCSI initiator and iSCSI target. Example: # iscsi-iname iqn.2012-02.com.ibm.de.boeblingen:01:c5f446d488f4 2 Linux on System z: iSCSI Initiator Configuration Chapter 2. Setting up iSCSI at the Storwize V7000 clustered system The iSCSI setup at Storwize V7000 is briefly described for the completeness of this document. It is assumed that the storage administrator has already set up the Storwize V7000 clustered system. 1. Get the iSCSI Qualified Name (IQN) for the Linux host system and iSCSI portal IP address from the Storwize V7000 storage administrator. 2. Configure IPv4 or IPv6 addresses for the system Ethernet ports on the nodes that are in the I/O groups that use the iSCSI volumes. 3. Create iSCSI volumes on the Storwize V7000 system. 4. Create a host object on the Storwize V7000 system server that describes the iSCSI server initiator to which the volumes are to be mapped, see “Creating an iSCSI host on Storwize V7000.” 5. Map the volume to the host object in the Storwize V7000 system, see “Mapping iSCSI volumes to the iSCSI host on the Storwize V7000 system” on page 8. Considerations v Each connection between a host initiator and a Storwize V7000 system Ethernet port can use either IPv4 or Ipv6. Concurrent use of both IPv4 and Ipv6 is not supported. v Storwize V7000 Ethernet ports 1 and 2 can each be configured for both a cluster IP address and an iSCSI target IP address. v A different cluster IP address can be assigned to each system Ethernet port, thus providing a configuration with redundant Ethernet networks. v All service and configuration IP addresses associated with a clustered-system Ethernet port must be on the same subnet across all nodes. Each port can reside in its own subnet. v When the host object on the Storwize V7000 system side is created or recreated for an iSCSI host, you must log out of any existing sessions from that host and then log back in. Referenced from: http://pic.dhe.ibm.com/infocenter/storwize/ic/index.jsp Creating an iSCSI host on Storwize V7000 Create a host object on the Storwize V7000 system server that describes the iSCSI server target to which the volumes are to be mapped.
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]