uc434s.f.00_stu.part2.pdf

Use of this material to deliver training without prior written permission from HP is prohibited.

Accelerated SAN Essentials

UC434S F.00

Student guide2 of 2

Use of this material to deliver training without prior written permission from HP is prohibited.

Student guide


UC434S F.00

2 of 2

Copyright 2010 Hewlett-Packard Development Company, L.P.

The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

This is an HP copyrighted work that may not be reproduced without the written permission of HP. You may not use these materials to deliver training to any person outside of your organization without the written permission of HP.

Microsoft, Windows, Windows XP, and Windows Vista are U.S. registered trademarks of Microsoft Corporation.

UNIX is a registered trademark of The Open Group.

Export Compliance Agreement

Export Requirements. You may not export or re-export products subject to this agreement in violation of any applicable laws or regulations.

Without limiting the generality of the foregoing, products subject to this agreement may not be exported, re-exported, otherwise transferred to or within (or to a national or resident of) countries under U.S. economic embargo and/or sanction including the following countries:

Cuba, Iran, North Korea, Sudan and Syria.

This list is subject to change.

In addition, products subject to this agreement may not be exported, re-exported, or otherwise transferred to persons or entities listed on the U.S. Department of Commerce Denied Persons List; U.S. Department of Commerce Entity List (15 CFR 744, Supplement 4); U.S. Treasury Department Designated/Blocked Nationals exclusion list; or U.S. State Department Debarred Parties List; or to parties directly or indirectly involved in the development or production of nuclear, chemical, or biological weapons, missiles, rocket systems, or unmanned air vehicles as specified in the U.S. Export Administration Regulations (15 CFR 744); or to parties directly or indirectly involved in the financing, commission or support of terrorist activities.

By accepting this agreement you confirm that you are not located in (or a national or resident of) any country under U.S. embargo or sanction; not identified on any U.S. Department of Commerce Denied Persons List, Entity List, US State Department Debarred Parties List or Treasury Department Designated Nationals exclusion list; not directly or indirectly involved in the development or production of nuclear, chemical, biological weapons, missiles, rocket systems, or unmanned air vehicles as specified in the U.S. Export Administration Regulations (15 CFR 744), and not directly or indirectly involved in the financing, commission or support of terrorist activities.

Printed in USA

Accelerated SAN EssentialsStudent guide December 2010

UC434S F.00 2010 Hewlett-Packard Development Company, L.P. i

Contents

Module 8 - iSCSI Objectives ................................................................................................. 8 - 1 IP storage .................................................................................................. 8 - 2 IP storage protocols .................................................................................... 8 - 4 Overview of iSCSI protocol .......................................................................... 8 - 6

iSCSI maps SCSI onto a network............................................................ 8 - 7 Overview of iSCSI protocol ................................................................... 8 - 8

iSCSI/FC SAN..........................................................................................8 - 10 iSCSI Stack ...............................................................................................8 - 12 iSCSI encapsulation ...................................................................................8 - 13 iSCSI Packet..............................................................................................8 - 14 iSCSI Host Driver .......................................................................................8 - 15 iSCSI initiators...........................................................................................8 - 16 iSCSI Name Support..................................................................................8 - 17 iSCSI Name Structure (1 of 2) .....................................................................8 - 19 iSCSI Name Structure (2 of 2) .....................................................................8 - 21 iSCSI name examples ............................................................................... 8 - 22 iSNS........................................................................................................8 - 23 iSCSI target discovery ............................................................................... 8 - 25 iSCSI target discovery example ...................................................................8 - 26 iSCSI operations........................................................................................8 - 27 iSCSI authentication.................................................................................. 8 - 28 iSCSI CHAP examples............................................................................... 8 - 29 IP Security ............................................................................................... 8 - 30 iSCSI advantages & disadvantages..............................................................8 - 31

P4000 HP StorageWorks iSCSI SAN.....................................................8 - 32 HP StorageWorks iSCSI SAN Recommended architecture........................ 8 - 33 Centralized Management Console (CMC) ............................................. 8 - 34 CMC Navigation ............................................................................... 8 - 35 Hierarchical Structure.......................................................................... 8 - 36 HP StorageWorks SAN Concepts ..........................................................8 - 37 Network RAID data mirroring .............................................................. 8 - 38 Configuring an HP StorageWorks SAN................................................. 8 - 40 Discovering Storage Nodes..................................................................8 - 41 Creating a Management Group............................................................8 - 42 Creating a Cluster .............................................................................. 8 - 43 Creating a Volume ............................................................................. 8 - 44 Creating a Server............................................................................ 8 - 45 Connecting a Volume to a Server ......................................................... 8 - 46 Final Result .........................................................................................8 - 47

Lab activity .............................................................................................. 8 - 48


ii 2010 Hewlett-Packard Development Company, L.P. UC434S F.00

Module 9 - SAN extension Objectives ................................................................................................. 9 - 1 What is SAN extension? ............................................................................. 9 - 2 Why extend the SAN? ................................................................................ 9 - 3 HP Supported SAN extension technologies .................................................... 9 - 4 SAN extension distance summary .............................................................. 9 - 5 Long Wave Transceivers .............................................................................. 9 - 6 Coarse Wave Division Multiplexing ............................................................. 9 - 8 Dense Wave Division Multiplexing................................................................ 9 - 9 FCIP......................................................................................................... 9 - 11 FCIP Protocol Mapping............................................................................9 - 12 Fibre Channel over IP.................................................................................9 - 13 Fibre Channel over IP.................................................................................9 - 14 FCIP performance......................................................................................9 - 16 Network speeds ........................................................................................9 - 18 Basic SCIS WRITE OPERATION...................................................................9 - 21 Brocade Fastwrite ......................................................................................9 - 23 Brocade FCIP Fastwrite + Tape pipelining.................................................... 9 - 25 Cisco Write Acceleration ............................................................................9 - 27 FCIP Compression .................................................................................... 9 - 29 IP network considerations .......................................................................... 9 - 30 IP network best practices ............................................................................9 - 31 FCIP Security.............................................................................................9 - 32 FCIP encryption ........................................................................................ 9 - 33 FCIP advantages ...................................................................................... 9 - 35 FCIP hardware ......................................................................................... 9 - 36 Fibre Channel routing overview ...................................................................9 - 37 Fabric and VSAN independence ................................................................ 9 - 39 SAN scaling .............................................................................................9 - 41 Fabric services limits ................................................................................. 9 - 43 Scaling by Routing.................................................................................... 9 - 45 Fibre Channel routing implementations........................................................ 9 - 46 B-Series and C-Series routing differences ..................................................... 9 - 48 Basic MP Router configuration.....................................................................9 - 49 Fibre Channel routing techniques H-Series switch ....................................... 9 - 50 Routing through an IP network.....................................................................9 - 51 Five-fabric configuration with FC-IP...............................................................9 - 52 SAN island consolidation ...........................................................................9 - 53 Integration of Fibre Channel routing and FCIP ...............................................9 - 55 Six-fabric configuration.............................................................................. 9 - 56 Tape backup consolidation .........................................................................9 - 57 Broadcast Zones....................................................................................... 9 - 58

Contents

UC434S F.00 2010 Hewlett-Packard Development Company, L.P. iii

Module 10 - FCoE/CEE Objectives ................................................................................................10 - 1

FCoE (Fibre Channel over Ethernet) .......................................................10 - 2 CEE (Converged Enhanced Ethernet ......................................................10 - 2

FCoE/CEE................................................................................................10 - 4 FCoE .......................................................................................................10 - 7 FcoE Terminology ......................................................................................10 - 9 FCoE integrated with FC San fabric ........................................................... 10 - 10 OSI, FCoE and FC stacks...........................................................................10 - 11 FCoE encapsulation ................................................................................. 10 - 12 Lossless Ethernet ...................................................................................... 10 - 14 HP Converged network switches offerings ................................................... 10 - 15 Converged Network Adapters (CANs) ....................................................... 10 - 18 Ethernet Overview ...................................................................................10 - 20 CEE Map ...............................................................................................10 - 22 DCBX (Data Center Bridging eXchange Protocol).........................................10 - 23 VLAN Membership ..................................................................................10 - 25 Minimum CEE configuration to allow FCoE traffic flow .................................10 - 27 FCIP, ISCSI & FCoE ..................................................................................10 - 29 Storage Support ...................................................................................... 10 - 31 Operating System Support ........................................................................10 - 32

Module 11 - SAN Management SAN Management .................................................................................... 11 - 1 Objectives ................................................................................................ 11 - 1 Storage management tasks ......................................................................... 11 - 2 Storage Resource Management ................................................................... 11 - 5 SAN management categories ..................................................................... 11 - 6 SAN management ..................................................................................... 11 - 8 SAN performance management .................................................................. 11 - 9 Storage capacity management................................................................... 11 - 11 SMI-S ......................................................................................................11 - 13 Implementing SMI-S ..................................................................................11 - 14 Storage Essentials .....................................................................................11 - 17 Storage Essentials Enterprise Edition plug-ins ................................................11 - 19 Storage Essentials Enterprise Edition home page ......................................... 11 - 20 Description of base components .................................................................11 - 21 System Manager ..................................................................................... 11 - 22 Capacity Manager .................................................................................. 11 - 23 Performance Manager ............................................................................. 11 - 24 Application Viewer .................................................................................. 11 - 25 Policy Manager ....................................................................................... 11 - 26 Event Manager ....................................................................................... 11 - 27 Report Optimizer ..................................................................................... 11 - 28 Description of plug-ins for both editions ...................................................... 11 - 30


iv 2010 Hewlett-Packard Development Company, L.P. UC434S F.00

Database Viewer......................................................................................11 - 31 Exchange Viewer..................................................................................... 11 - 32 File System Viewer ................................................................................... 11 - 33 Backup Manager..................................................................................... 11 - 34 HP StorageWorks Fabric Manager ............................................................ 11 - 35 Key features and functions (1 of 2) ............................................................. 11 - 37 Key features and functions (2 of 2)............................................................. 11 - 39 Graphical user interface ............................................................................11 - 41 Firmware upgrade ................................................................................... 11 - 43 Configuration upload and download ......................................................... 11 - 45 HP Data Center Fabric Manager (DCFM) ................................................... 11 - 46 Utilize Administration Time........................................................................ 11 - 47 Cisco Fabric Manager overview ................................................................ 11 - 49 Fabric Manager ...................................................................................... 11 - 50 Device Manager ......................................................................................11 - 51 Lab activity ............................................................................................. 11 - 54

Module 12 - SAN Security Objectives ................................................................................................12 - 1 Security in a SAN......................................................................................12 - 2 Basic security model ..................................................................................12 - 3 Security domains .......................................................................................12 - 5 Attacks and exposures ...............................................................................12 - 7 Mitigation of risk .......................................................................................12 - 8 SAN security access points ....................................................................... 12 - 10 Storage security model ..............................................................................12 - 11 Data security........................................................................................... 12 - 12 Management security............................................................................... 12 - 19

Local Authentication on a switch .........................................................12 - 22 Role-Based Access Control (RBAC) B-Series........................................... 12 - 23 Role-Based Access Control (RBAC) C-Series .......................................... 12 - 26

RADIUS Authentication............................................................................. 12 - 27 SAN security practices .............................................................................12 - 29 Planning SAN security prevention ..............................................................12 - 30 Data path and management path security in practice .................................. 12 - 31 Storage security in an enterprise environment.............................................. 12 - 32 Security in practice ..................................................................................12 - 35 Authentication .........................................................................................12 - 36 FCIP encryption and Data encryption at rest................................................12 - 38 Lab activity ............................................................................................. 12 - 41

Module 13 - Data protection Objectives ................................................................................................13 - 1 Data Protection..........................................................................................13 - 2 Challenges in Data Protection .....................................................................13 - 3

Contents

UC434S F.00 2010 Hewlett-Packard Development Company, L.P. v

Not all data are equal ...............................................................................13 - 4 Recovery operations...................................................................................13 - 5 Protection and recovery methods .................................................................13 - 6 Data Protection Technologies ......................................................................13 - 7 Direct backup tape..................................................................................13 - 9 Centralized server backup ........................................................................ 13 - 10 Automated centralized backup ...................................................................13 - 11 Centralized SAN backup.......................................................................... 13 - 12 Tape libraries .......................................................................................... 13 - 13 Zoning for backup ................................................................................... 13 - 14 Backup performance considerations........................................................... 13 - 16 Virtual Tape Libraries ............................................................................... 13 - 18 VTL in practice ........................................................................................13 - 20 Disk to Tape............................................................................................ 13 - 22 Data replication ...................................................................................... 13 - 23 Split-mirror backup concept ...................................................................... 13 - 24 Snapshot backup concept......................................................................... 13 - 26 De-Duplication ........................................................................................ 13 - 27 How hash based chunking works .............................................................. 13 - 32 How hash-based chunking performs restores ...............................................13 - 34

Pros & Cons of HP Dynamic Deduplication........................................... 13 - 36 Enterprise Deployment with replication across remote and branch offices back to data centers .......................................................................... 13 - 37 Hp Storage Works Disk to Disk and Virtual Library portfolio with de-duplication...................................................................................13 - 38

Remote replication ................................................................................... 13 - 39 HP StorageWorks Continuous Access EVA (CA EVA) ....................................13 - 40 Synchronous replication (1 of 2) ................................................................ 13 - 41 Synchronous replication (2 of 2) ................................................................ 13 - 42 Asynchronous replication (1 of 2)...............................................................13 - 43 Asynchronous replication (2 of 2) ..............................................................13 - 44 Comparing replication modes ................................................................... 13 - 45 HP StorageWorks Storage Mirroring .......................................................... 13 - 47 SWSM mirroring full..............................................................................13 - 48 SWSM mirroring file difference............................................................... 13 - 49 Lab activity .............................................................................................13 - 50

Module 14 - Performance Objectives ................................................................................................14 - 1 SAN performance objectives.......................................................................14 - 2 Performance factors ...................................................................................14 - 4 Response time ...........................................................................................14 - 7 Bus utilization............................................................................................14 - 8 Device utilization .......................................................................................14 - 9 SAN performance Considerations...............................................................14 - 11


vi 2010 Hewlett-Packard Development Company, L.P. UC434S F.00

Latencies ................................................................................................ 14 - 13 ISL oversubscription.................................................................................. 14 - 15 Hop latency............................................................................................ 14 - 17 Data Priority Quality of Service............................................................... 14 - 19 Device attachment points .......................................................................... 14 - 21 Place fastest switches in the core................................................................ 14 - 22 Distance considerations............................................................................ 14 - 24 Maintaining performance in an extended SAN beyond 5 or 10km ................ 14 - 25 Distributed fabrics.................................................................................... 14 - 26 Long distance link modes ......................................................................... 14 - 27 Extended distance topology...................................................................... 14 - 28 Performance Guidelines within the SAN ..................................................... 14 - 29 Determining the required bandwidth ..........................................................14 - 30 Drive selection and performance ............................................................... 14 - 32 RAID and RAID selection ..........................................................................14 - 34 RAID level efficiency................................................................................. 14 - 36 Disk Performance..................................................................................... 14 - 37 Planning a disk system .............................................................................14 - 38 Data caching technologies ....................................................................... 14 - 41 Write-back caching .................................................................................14 - 43 Write-back cache benefits ........................................................................ 14 - 45 Effects of cache ....................................................................................... 14 - 47 Application effects on performance............................................................ 14 - 49 Environment profiling ...............................................................................14 - 50 Large sequential read environment............................................................. 14 - 51 Server Application ................................................................................... 14 - 52 Improving performance ............................................................................ 14 - 56 Comparing VRAID1 and VRAID5 .............................................................. 14 - 57 Safe IOPs calculator for production disk group ............................................ 14 - 59 Safe IOPs calculator Microsoft version.................................................... 14 - 61 EVAPerf.................................................................................................. 14 - 62 End to End monitoring.............................................................................. 14 - 65 Top talker ...............................................................................................14 - 66 Lab activity .............................................................................................14 - 68

UC434S F.00 2010 Hewlett-Packard Development Company, L.P. 8 -1

iSCSI Module 8

Objectives


8 -2 2010 Hewlett-Packard Development Company, L.P. UC434S F.00

IP storage

IP storage IP storage can combine the following functions on a single

enterprise network:StorageData sharingWeb accessDevice management using SNMPE-mail Voice and video transmission

With many of the benefits that Fibre Channel SANs already give to us.

The amount of data stored has been doubling every year and this has been attributed to the phenomenal growth in software applications, such as on-line transactions, e-mail, and the development of complex e-commerce applications. The Internet and corporate intranets drive this growth to an extent where there is an almost mandatory requirement for continuous availability of information in the corporate e-business world. The net effect of this trend has been the duplication of on-line copies of this monumental quantity of data. This increasing appetite to consume disk storage has been met by the disk drive industry to double the capacity of hard disk drives and to reduce the price of storage.

The pervasiveness of the Internet Protocol (IP) through the unprecedented growth of the Internet and the increasing demand of disk storage has led to the question as to whether or not it is possible to use TCP/IP, the networking technology of Ethernet LANs and the Internet, for use in disk storage.

Such an approach can facilitate a single network:

Storage

Data sharing

Web access

Device management using SNMP

E-mail

Voice and video transmission

iSCSI


IP networking is based on design considerations different from those of storage concepts. While the TCP/IP protocol is software-based and geared towards unsolicited packets, storage protocols are hardware-based and are centered on solicited packets. A storage networking protocol must leverage the TCP/IP stack without any modification and maintain high performance. The goal is to merge the two concepts and provide the performance of a specialized storage protocol like SCSI. This amalgamation of storage area networks (SANs) and IP is the driving force for using IP-based networks to transport block storage traffic and is referred to as IP storage.

Benefits IP storage has emerged in recent years as networked storage requirements have grown and IP has become firmly established as the predominant general purpose networking protocol. The following are some benefits provided by IP storage:

Addresses the difficulties of managing burgeoning storage resources.

Facilitates the storing, accessing, protection, and management of mission-critical data.

Provides protection of data by allowing redundant paths between host and storage devices.

Enables remote mirroring solutions for disaster recovery.

Allows backups to be performed over the IP storage with minimal impact on application servers or the host network.

Allows storage to be consolidated, which reduces management complexity.

Centralized management of a consolidated storage pool can be more efficient than managing separate direct-attached storage subsystems.

With an ever-growing development base behind IP, the existing quality of service, link prioritization, and security protocols that are available for IP networks continues to drive technology.

IP is relatively inexpensive, because it runs over commodity sub-networking technologies such as Ethernet.

Enables block storage over IP-based networks and provides easy access to storage over long distances.

A single networking technology for the LAN and SAN is compelling such that IT departments do not have to maintain equipment, technical staff, and expertise in both the IP and FC technologies.



IP storage protocols

IP storage protocols

Devices

iSCSI iFCP FCIP

Fabric Services

Understanding IP storage protocols An appreciation of the IP protocol is necessary in order to understand IP storage protocols. The network layer protocol which lies below the transport layer is known as the Internet Protocol (IP). It is responsible for transferring data from one host to another, using various routing algorithms. Layers above the network layer fragment a data stream into chunks of a predetermined size, known as packets or datagrams. The datagrams are then sequentially passed to the IP network layer.

The purpose of the IP layer is to route such packets to the target destination. IP packets comprise an IP header, together with the higher level TCP protocol and the application datagram. IP knows nothing about the TCP and datagram contents. Prior to transmitting data, the network layer could further subdivide the data into smaller packets to facilitate transmission. On receipt at the destination, the packets are reassembled into the original datagram by the network layer.

The transfer of block-level storage data across a networked topology is not a new concept and is achieved currently through SANs using the Fibre Channel technology. Transferring data through the use of IP is not a new concept. Protocols such as Common Internet File System (CIFS) and Network File System (NFS) have been used to access storage data over IP networks for several years. The difference between these existing protocols and the IP storage protocols lie in their respective approach to the means of accessing data. CIFS and NFS access data at the file-level while IP storage protocols access data at the block-level.

iSCSI


The following three IP storage encapsulation protocols have been defined:

iSCSI iSCSI is defined as a SCSI network transport protocol that operates with TCP as the underlying layer to provide a reliable transport with guaranteed in-order delivery. iSCSI encapsulates SCSI protocols into a TCP/IP frame, so that storage controllers can be attached to IP networks.

Fibre Channel over TCP/IP The purpose of the Fibre Channel Over TCI/IP (FCIP) protocol is to transport Fibre Channel frames over an IP infrastructure. FCIP provides the mechanisms facilitating islands of Fibre Channel SANs to be interconnected over IP-based networks to form a single, unified Fibre Channel SAN fabric or separate managed Fibre Channel SANs. The extended Fibre Channel SAN fabric continues to use standard Fibre Channel addressing. IP tunnels are set up between FCIP end points. Once these tunnels are in place, Fibre Channel devices view these extended links as standard Fibre Channel links and use Fibre Channel addressing.

FCIP tunnels FCIP tunnels are used to pass Fibre channel I/O through an IP network. FCIP tunnels are built on a physical connection between two peer switches or blades.

VE_ports and VEX_ports VE_ports and VEX_ports are virtual E_ports. VE_Ports are used to create interswitch links (ISLs). If VE_Ports are used on both ends of an FCIP tunnel, the fabrics connected by the tunnel are merged. VEX_Ports enable interfabric links (IFLs). If a VEX_Port is on one end of an FCIP tunnel, the fabrics connected by the tunnel are not merged. The other end of the tunnel must be defined as a VE_Port. VEX_Ports cannot be used in pairs

Internet Fibre Channel Protocol Internet Fibre Channel Protocol (iFCP) encapsulates Fibre Channel frames to be sent over the IP infrastructure just like the FCIP protocol. Both protocols use a common Fibre Channel encapsulation format. The principal difference between the two protocols lies in the addressing schemes. The FCIP protocol establishes point-to-point tunnels that can be used to connect two Fibre Channel SANs together using Ethernet to create a single, larger SAN. In contrast, iFCP is a gateway-to-gateway protocol that combines Fibre Channel and IP addressing to allow the Fibre Channel frames to be routed to the appropriate destination address. Unlike the addressing scheme of the FCIP protocol, the current iFCP addressing scheme allows each interconnected SAN to retain its own independent name space.



Overview of iSCSI protocol

Overview of iSCSI protocol What is it?

iSCSI is an IETF SCSI transport protocol for mapping of block-oriented storage data over TCP/IP networks.

The iSCSI protocol enables universal access to storage devices and Storage Area Networks (SANs) over standard Ethernet-based TCP/IP networks

These networks may be dedicated networks or may be shared with traditional Ethernet applications.

What is it? iSCSI is an IETF SCSI transport protocol for mapping of block-oriented storage data over TCP/IP networks.

The iSCSI protocol enables universal access to storage devices and Storage Area Networks (SANs) over standard Ethernet-based TCP/IP networks

These networks may be dedicated networks or may be shared with traditional Ethernet applications.

iSCSI


iSCSI maps SCSI onto a network

SCSI is a long-established protocol for connecting disks to computers. All common operating systems contain drivers and logic for SCSI devices. By replacing the SCSI hardware driver with a SAN initiator, iSCSI creates a connection into the target SAN system. The user system sees the iSCSI connection as if it was a normal SCSI disk, so no further modifications are required to the accessing system or applications.



Overview of iSCSI protocol

Overview of iSCSI protocol Why was it created? The SCSI protocol has been mapped over various

transports, including Parallel SCSI, IPI, IEEE-1394 (firewire) and Fibre Channel. These transports are I/O specific and have limited distance capabilities.

The iSCSI protocol is a means of transporting of the SCSI packets over TCP/IP, providing for an interoperable solution which can take advantage of existing Internet infrastructure, Internet management facilities and address distance limitations.

Why was it created?

The SCSI protocol has been mapped over various transports, including Parallel SCSI, IPI, IEEE-1394 (firewire) and Fibre Channel. These transports are I/O specific and have limited distance capabilities.

The iSCSI protocol is a means of transporting of the SCSI packets over TCP/IP, providing for an interoperable solution which can take advantage of existing Internet infrastructure, Internet management facilities and address distance limitations.

The iSCSI protocol uses TCP/IP for its data transfer. Unlike other network storage protocols, such as Fibre Channel (which is the foundation of most SANs), it requires only the simple and ubiquitous Ethernet interface (or any other TCP/IP-capable network) to operate. This enables low-cost centralization of storage without all of the usual expense and incompatibility normally associated with Fibre Channel storage area networks.

Critics of iSCSI expect worse performance than Fibre Channel due to the overhead added by the TCP/IP protocol to the communication between client and storage. However new techniques like TCP Offload Engine (TOE) help in reducing this overhead. Tests have shown excellent performance of iSCSI SANs, whether TOEs or plain Gigabit Ethernet NICs were used. In fact, in modern high-performance servers, a plain NIC with efficient network driver code can outperform a TOE card because fewer interrupts and DMA memory transfers are required. Initial iSCSI solutions are based on a software stack. The iSCSI market is growing steadily, and should improve in performance and usability as more organizations deploy Gigabit and 10 Gigabit networks, and manufacturers integrate iSCSI support into their operating systems,

iSCSI


SAN products and storage subsystems. iSCSI became even more interesting once Ethernet started to support higher speeds than Fibre Channel.



iSCSI/FC SAN

iSCSI/FC SAN

Server with IPstorage adapter

Storage device Server with IPstorage adapter

Server with FCstorage adapter

Storage device

Storage deviceServer with IPstorage adapter

Storage device

Fibre Channel has provided the principal means for building SANs because of the rich features of high performance, connectivity, and ability to support block-oriented storage protocols. The high throughput is achieved by assigning much of the protocol processing to hardware. Fibre Channel overcomes several scalability issues inherent in SCSI by creating a switched network fabric infrastructure that extends Fibre Channel operating distance between 10 and 20km and overcomes device count limitations.

IT managers are concerned about sharing storage traffic and data traffic within a common IP network backbone. The principal concern is that such sharing could lead to congestion bottlenecks. While combining both messaging and storage traffic on a single network is possible, a more practical solution is to segment the IP network infrastructure and move storage and data traffic via different paths. This approach enables customers to protect the investment in IP networking and maximize the efficiencies of moving both types of traffic over a common infrastructure.

The common IP storage network technology for both iSCSI and Fibre Channel connected devices provides the following capabilities and benefits:

Universal storage access across an IP network regardless of the interconnect (for example, iSCSI and Fibre Channel)

Access to existing Fibre Channel SANs and a migration path to an IP environment

Use of Fibre Channel end systems with proven performance and relative stability

iSCSI


High-end storage and SAN expansion for iSCSI servers

Pooling iSCSI SANs, Fibre Channel SANs, and network attached storage (NAS) resources over a common IP network for a viable long-term storage strategy

Improved storage manageability and high availability of storage resources

A core SAN fabric that is IP-based

These environments can provide application support for:

Local and remote backup over an IP network.

Storage virtualization across a common pool of heterogeneous storage resources.

Peer-to-peer copy.

Disaster recovery and high availability.

Mirroring across heterogeneous SANs.



iSCSI Stack

iSCSI Stack

IP

SCSI Applications (File Systems,

Databases)SCSI Block Commands

TCP

SCSI Commands, Data, and Status

SCSI Device-Type Commands

SCSI Generic Commands

SCSI Transport Protocols

Application

PresentationSession

Network

iSCSI

Transport

Data Link

PhysicalEthernet

iSCSIOSI Model

iSCSI uses TCP/IP for reliable data transmission over potentially unreliable networks. The iSCSI layer interfaces to the operating system standard SCSI set and includes encapsulated SCSI commands, data and status reporting capability. When the operating system or application requires a data write operation, the SCSI CDB must be encapsulated for transport over a serial gigabit link and delivered to the target. The iSCSI protocol monitors the block data transfer and validates completion of the I/O operation. This occurs over one or more TCP connections between initiator and target. In practical applications, an initiator can have multiple target resources over an IP network and consequently, multiple concurrent TCP connections are active.

The iSCSI protocol maps the SCSI Remote Procedure Call model to the TCP/IP protocol and provides a conceptual layer completely independent of the SCSI CDB information. SCSI commands are transported by iSCSI request and SCSI response and status are handled by iSCSI responses. iSCSI protocol tasks are then carried by this same iSCSI request and response mechanism. Following the pattern of the SCSI protocol, iSCSI employs the concepts of initiator, target, and communication messages called protocol data units (PDUs). Likewise, iSCSI transfer direction is defined respectively to the initiator. As a means to improve performance, iSCSI allows a phase collapse that provides a command or response and its associated data to be sent in a single iSCSI PDU.

iSCSI


iSCSI encapsulation

iSCSI encapsulation

Physical addressing information

Layer 2(Ethernet)

IPHeader

TCPHeader

iSCSIHeader SCSI Commands and Data

Provides error-correction, sequencing of packet, and

identifies application using the service

Network address and routing information used in routing the packet

Indicates how to extract SCSI commands and data

The iSCSI standard stipulates that the protocol must not require modification to the current IP and Ethernet infrastructure to support storage traffic. The iSCSI protocol standard must allow implementations to equal or improve on the current state of the art for SCSI interconnects. The iSCSI protocol:

Must provide low delay communications.

Must provide high bandwidth and bandwidth aggregation.

Must have low host CPU utilizations, equal to or better than current technology.

Must be possible to build I/O adapters handling the entire SCSI task.

Must permit zero-copy memory architectures.

Must not impose complex operations on host software.

Must be cost competitive with alternative storage networking technologies.



iSCSI Packet

iSCSI Packet

46 1500 bytes

TCP Header

Ethernet header

CRCDataTCPIPTypeSourceDestinationPreamble

Options and padding

Urgent pointerChecksum

WindowFSRPAUReservedOffset

Acknowledgment Number

Sequence Number

Destination PortSource Port

iSCSI3260

http80

smtp25

telnet23

ftp21

Well known TCP ports

iSCSI Protocol Data Unit (PDU)

Data Field

Opcode Specific Fields

Initiator Task Tag

LUN or Opcode-specific fields

OpcodeI Opcode Specific FieldsF

Header Length

Data Segment Length

The basic system model for iSCSI is that of an extended virtual cable, connecting a SCSI initiator device to a SCSI target device. Both the iSCSI initiator and iSCSI target are identified by their IP addresses which are carried within the iSCSI packet header.

iSCSI


iSCSI Host Driver

iSCSI Host Driver

ApplicationsApplications

File SystemFile System

Block DeviceBlock Device

SCSI GenericSCSI Generic

Adapter DriverAdapter Driver

SCSI Adapter(HBA)

SCSI Adapter(HBA)

TCP/IP StackTCP/IP Stack

NIC DriverNIC Driver

iSCSI Driver

NIC AdapterNIC Adapter

IP Network

Directconnect

orSAN

SCSI/TCP ServerSCSI/TCP Server

TCP/IP DriverTCP/IP DriverGigE NICGigE NIC

SCSI DriverSCSI DriverFC HBAFC HBA

HOST

FC/iSCSI bridge

Direct Attached Storage

Array

Resides on the host and provides host-to-storage connectivity over an IP network

Uses the hosts existing TCP/IP stack, network drivers and network interface card(s) (NIC) to provide the same functions as native SCSI drivers and Host Bus Adapter (HBA) cards

Functions as a transport for SCSI commands and responses between the host and the iSCSI target on an IP network.

ARRAY

Resides on the host and provides host-to-storage connectivity over an IP network

Uses the hosts existing TCP/IP stack, network drivers and network interface card(s) (NIC) to provide the same functions as native SCSI drivers and Host Bus Adapter (HBA) cards

Functions as a transport for SCSI commands and responses between the host and the iSCSI target on an IP network.



iSCSI initiators

iSCSI initiators

Good Better Best

The IP host or iSCSI Initiator uses an iSCSI Driver to enable target resource recognition & attachment to the iSCSI target over IP.

The iSCSI initiator is configured with the Gigabit Ethernet IP address of the iSCSI port on the iSCSI target to transport SCSI requests and responses.

The iSCSI initiator sees the storage resources (LUNs) as if they were local block-level drives attached directly to the server.

iSCSI


iSCSI Name Support

iSCSI Name Support iSCSI names are:

used for identificationused for authenticationenable iSCSI resources to be managed regardless or

location Each iSCSI initiator (and iSCSI target) must have an iSCSI

name. iSCSI names:

can be up to 223 bytes in lengthare globally uniquedo not imply a location or address

May be registered with iSNS

iSCSI Name Support iSCSI implements a client-server model between disk targets and initiating hosts and adheres to the SCSI Architectural Model (SAM-2). Because both iSCSI targets and initiators are elements on an IP network, the clients and servers have a Network Entity identity that is equivalent to assigned IP addresses. It is possible for the Network Entity to contain one or more iSCSI Nodes.

The iSCSI Node object uniquely identifies a SCSI device within a Network Entity that is accessible through the network. The Network Portal is an amalgamation of the Node IP address and the TCP port number. The Network Entity object allows for multiple iSCSI Nodes because a Network Entity might represent a gateway fronting multiple initiators or targets. Each iSCSI Node is identified by a unique iSCSI name that can be up to 255 bytes in length. A Domain Name Server (DNS) or other resource locator implementations can parse this identifier. The 255-byte name length also ensures globally unique names that can be formatted as required by the storage administrator.

iSCSI names are:

used for identification

used for authentication

enable iSCSI resources to be managed regardless or location



Each iSCSI initiator (and iSCSI target) must have an iSCSI name.

iSCSI names:

can be up to 223 bytes in length

are globally unique

do not imply a location or address

May be registered with iSNS

iSCSI


iSCSI Name Structure (1 of 2)

iSCSI Name Structure (1 of 2) The iSCSI name structure is fairly rigid and contains two parts: a type

designation followed by a unique name string. The two type designators for iSCSI are:

iqn. iSCSI qualified nameeui. IEEE EUI-64 identifier in ACSII-encoded hexadecimal

An example of the iqn string is shown below:Iqn.2003-02.com.hp:server3

This designator type consists of the following:The string iqn followed by a dot (.)A date code, in yyyy-mm format followed by another dot (.)A reverse domain name, andOptional colon (:) prefixed by string

iSCSI Name Structure The combination of IP address and a TCP port generates a unique network address for an iSCSI device. The separation of iSCSI names and iSCSI addresses ensures that a storage device will have a unique identity in the network regardless of its location in the network. Although the IP address plus the TCP port number will necessarily change if a device is moved onto a different network segment, the iSCSI name will travel with the device, allowing it to be rediscovered.

The iSCSI naming convention is meant to assist the discovery process and validate device identity during iSCSI login between initiator and target. The potentially very long 255-byte iSCSI name is not used for routing, which would place an unreasonable burden on network parsing engines. Instead, after the IP address and TCP port number are established for a specific iSCSI Node, only the IP address and TCP port combination is required for storage transactions.



The iSCSI name s tructure is fairly rigid and contains two parts : a type designationfollowed by a unique name s tring.

The two type des ignators for iSCSI are:

iqn. iSCSI qualified nameeui. IEEE EUI-64 identifier in ACSII- encoded hexadecimal

An example of the iqn s tring is shown below:

Iqn.2003-02.com.hp:server3

This designator type consis ts of the following:

The s tring iqn followed by a dot (.) A date code, in yyyy-mm format followed by another dot (.) A reverse domain name, and Optional colon (:) prefixed by s tring

iqn: specifies the use of the iSCSI qualified name as the authority.

Date Code: 2003-02 is the year and month on which the naming authority acquired the domain name used in this iSCSI name. This is used to ensure that when domain names are sold or transferred to another organization, iSCSI names generated by these organizations will be unique.

com.hp is a reversed DNS name, and defines the organizational naming authority. The owner of the DNS name hp.com has the sole right of use of this name as this part of an iSCSI name, as well as the responsibility to keep the remainder of the iSCSI name unique.

server3 was picked arbitrarily by hp.com to identify the server hosting the iSCSI device. The owner of "hp.com" is responsible for keeping this structure unique

iSCSI


iSCSI Name Structure (2 of 2)

iSCSI Name Structure (2 of 2) There are also special rules that must be followed: For those using only ASCII characters (U+0000 to

U+007F), the following characters are allowed:ASCII dash character ('-' = U+002d) ASCII dot character ('.' = U+002e)ASCII colon character (':' = U+003a)ASCII lower-case characters ('a'..'z' =

U+0061..U+007a)ASCII digit characters ('0'..'9' = U+0030..U+0039)

Underscores are NOT allowed

No special characters, other than ASCII colons, dots and dashes, or white spaces are allowed. The fully qualified name format enables storage administrators to assign meaningful names to storage devices and manage devices more easily. The unique identifier component can be a combination of department, application, manufacturer name, serial number, asset number, and any tag useful for recognizing and managing a storage resource.



iSCSI name examples

iSCSI name examples

# cat /etc/initiatorname.iscsi## DO NOT EDIT OR REMOVE THIS FILE!## If you remove this file, the iSCSI daemon will not start.## If you change the InitiatorName, existing access control lists## may reject this initiator. The InitiatorName must be unique## for each iSCSI initiator. Do NOT duplicate iSCSI InitiatorNames.## InitiatorName=iqn.1987-05.com.cisco:01.4f38fd6e357InitiatorName=iqn.1987-05.com.cisco:01.rh3u5.Rack20-02

Windows

Linux

iSCSI name examples:

iSCSI


iSNS

iSNS An iSNS implementation provides four primary services:

Name Registration and Storage Resource Discovery Discovery Domains and Login Control State Change Notification Bidirectional Mappings Between Fibre Channel and

iSCSI Devices

iSNS Discovery using iSCSI names can be performed using the Internet Storage Name Service (iSNS) or other resource locator. As implied by the structure of iSCSI names, either a distributed or centralized DNS-type look up facilitates mapping of iSCSI names required for iSCSI log in to actual iSCSI network addresses.

Name Registration and Storage Resource Discovery iSNS implementations allow all entities in a storage network to register and query an iSNS database. Both targets and initiators can register with the iSNS database, and each entity can inquire about other initiators and targets. For example, a client initiator can obtain information about target devices from an iSNS server.

Discovery Domains and Login Control Administrators can use the Discovery Domains to divide storage nodes into manageable, non-exclusive groups. By grouping storage nodes, administrators are able to limit the login process of each host to the most appropriate subset of targets registered with the iSNS, which allows the storage network to scale by reducing the number of unnecessary logins and by limiting the amount of time each host spends establishing login relationships.

Each target is able to use Login Control to delegate their access control and authorization policies to an iSNS server. Such delegation is intended to promote centralized management.



State Change Notification The State Change Notification (SCN) service allows an iSNS Server to issue notifications about each event that affects storage nodes on the managed network. Each iSNS client may register for notifications on behalf of its storage nodes, and each client is expected to respond according to its own requirements and implementation.

Bidirectional Mappings between Fibre Channel and iSCSI Devices Because the iSNS database stores naming and discovery information about both Fibre Channel and iSCSI devices, iSNS servers are able to store mappings of Fibre Channel devices to proxy iSCSI device images on the IP network. These mappings may also be made in the opposite direction, allowing iSNS servers to store mappings from iSCSI devices to proxy WWNs.

iSCSI


iSCSI target discovery

iSCSI target discovery Discovery allows the iSCSI initiator to find (discover) targets to which it

has access. Discovery Methods

iSCSI targets are configured on the initiator Initiator would use a config file containing Target info

iSCSI initiator queries the Target A SendTargets is issued to request a list of targets

Initiator uses Service Location Protocol (SLP) To locate iSCSI targets or SNS without configuring addresses

Initiator queries a Storage Name Server (SNS, iSNS) To locate iSCSI targets without configuring addresses

Discovery allows the iSCSI initiator to find (discover) targets to which it has access. The following discovery methods are valid in an iSCSI environment:

iSCSI targets are configured on the initiator

Initiator would use a config file containing Target info

iSCSI initiator queries the Target

A SendTargets request is issued asking for a list of targets

Initiator uses Service Location Protocol (SLP)

To locate iSCSI targets or SNS without configuring addresses

Initiator queries a Storage Name Server (SNS, iSNS)

To locate iSCSI targets without configuring addresses



iSCSI target discovery example

iSCSI target discovery example

# cat /etc/iscsi.conf...# --------------------------# Discovery Address Category# --------------------------#DiscoveryAddress=33.33.66.66# or#DiscoveryAddress=10.4.100.1:3260# or#DiscoveryAddress=scsirouter1#

Linux

Windows

iSCSI Discovery examples:

iSCSI


iSCSI operations

iSCSI operations

iSCSI initiator iSCSI target

iSCSI login request to initiate iSCSI session over TCP

This persistent session now allows authentication and the exchange of certificates

iSCSI initiator iSCSI target

Multiple sessions may be active to aggregate bandwidth and improve performance

iSCSI is a connection-oriented command and response protocol. An iSCSI session begins with an iSCSI initiator connecting to an iSCSI target (typically, using TCP) and performing an iSCSI login. This login creates a persistent state between initiator and target, which can include initiator and target authentication, session security certificates, and session option parameters.

Once this login has been successfully completed, the iSCSI session continues in full feature phase. The iSCSI initiator can issue SCSI commands encapsulated by the iSCSI protocol over its TCP connection, which are executed by the iSCSI target. The iSCSI target must return a status response for each command over the same TCP connection, consisting of both the completion status of the actual SCSI target device and its own iSCSI session status. An iSCSI session is terminated when its TCP session is closed.



iSCSI authentication

iSCSI authentication iSCSI authentication provides a mechanism to authenticate

iSCSI initiators requesting access to storage devices (Targets)

Challenge Handshake Authentication Protocol (CHAP) is one authentication method to pass user name and password information between initiator and targets.

iSCSI authentication iSCSI authentication provides a mechanism to authenticate iSCSI initiators

requesting access to storage devices (Targets)

Challenge Handshake Authentication Protocol (CHAP) is one authentication method to pass user name and password information between initiator and targets.

iSCSI


iSCSI CHAP examples

iSCSI CHAP examples

# cat /etc/iscsi.conf..

-----------------------# AUTHENTICATION SETTINGS# -----------------------# To globally configure a CHAP username and password for initiator# authentication by the target(s), uncomment the following lines:##OutgoingUsername=mpx100-user#OutgoingPassword=igotasecret# # The maximum length for both the password and username is 256 characters.

iSCSI CHAP examples:

Windows

Linux



IP Security

IP Security Security

IKE IPSEC Authentication processesKerberos v.5 CHAP Radius SPKM -1 and SPKM -2

IP security The maturity of IP based security makes SOIP attractive:

IKE

IPSEC

Authentication processes

Kerberos v.5

CHAP

Radius

SPKM -1 and SPKM -2

iSCSI


iSCSI advantages & disadvantages

iSCSI advantages & disadvantagesDisadvanatges Higher overhead per packet than Fibre

Channel jumbo frames can be used to alleviate this issue

iSCSI exposes data to the network create a dedicated, secured network for all block level transmissions

iSCSI increases network load and could lead to congestion assign a dedicated subnet for all iSCSI traffic

iSCSI protocol is not as widely tested as SCSI or Fibre Channel

iSCSI places a higher load on the host CPU use a dedicated iSCSI host adapters for initiators

Advantages Shorter learning curve then Fibre

Channel for network and server administrators

High data availability built into the TCP specification

Able to leverage other Ethernet and TCP innovations and standards, such as QoS, IPSec and IP Trunking

Low cost compared to Fibre Channel, as software initiators are available for most operating systems

Consolidation of storage and centralized backups and management

It has to be noted that iSCSI is an affordable means to integrate a lower performing storage in to a 1Gbit/sec Ethernet providing shared storage for departmental use. At 10 Gbit/sec, iSCSI loses much of its publicized cost advantage. By using a 10Gbit/ sec Ethernet implies that the applications being hosted require high reliability and performance. At 1Gbit/sec standard NICs can be used, however when implementing on 10Gbit/sec network server performance is enhanced by the use of iSCSI cards which utilize auxiliary components like TOE (TCP off-load Engine) or iSER (iSCSI Extensions for RDMA), which helps to avoid multiple memory copies of SCSI data between the interface and application memory. These types of cards (TOE and/or iSER) can add significant cost per attached server compared to an 8Gbit/sec FC HBA, and could undermine the value proposition of iSCSI at 1 Gbit/sec.



P4000 HP StorageWorks iSCSI SAN

P4000 is HP StorageWorks SAN which is a low-cost but high-capability SAN based on HP server hardware. All communications with the SAN, both SAN data and management commands, are transferred over normal LAN connections.

The SAN generally includes a collection of StorageWorks SAN servers, called Storage Nodes. Control software (SAN/iQ) runs on the Storage Nodes and handles all communication and data management on the Storage Nodes. Administrators access the SAN from a management system running the Centralized Management Console (CMC) software.

iSCSI


HP StorageWorks iSCSI SAN Recommended architecture

Unlike a fibre-channel SAN, all data transfers in an iSCSI SAN go over normal LAN lines. Because of the heavy volume of data transferred in and out of Storage Nodes, HP strongly recommends designing your network with isolated business LAN and storage LAN segments.

In the diagram above, business traffic between user workstations and application servers runs on a corporate LAN. All SAN traffic runs on a separate storage LAN. The application servers connect to both LAN segments, making them accessible to both users and the SAN.

Because the CMC must communicate directly with Storage Nodes, it cannot be located only on the business LAN. There are two common configuration choices: either dedicate a management system to CMC use, and connect the system directly to the storage LAN (as shown above); or install the CMC software on one of the application servers, and access it remotely from any system on the business LAN. The first solution offers better security, and the second solution is more flexible and convenient.



Centralized Management Console (CMC)

The CMC is the primary interface for configuring and managing the Storage Nodes in the SAN. This slide shows the areas of interest in the CMC interface.

The Launch Pad opens in the Content Pane when you run the Centralized Management Console (CMC) for the first time. The Launch Pad offers several Wizards to simplify the SAN setup process. For example, you can select the Find Nodes Wizard in the Content Pane to locate the Storage Nodes available on your network.

iSCSI


CMC Navigation

The CMC displays different entities such as Management Groups, Storage Nodes, Clusters, and Volumes in the Navigation Pane. Entities also have sub-entities or attributes that allow you to configure the entities.

Simply expand the navigation tree by clicking on the + next to an entity this opens the entity and, if appropriate, logs you in.



Hierarchical Structure

The Navigation Pane displays the objects and configuration options you will use to set up the SAN. In this slide you can see a Management Group (called MG1) that contains several configuration options and a cluster (C1) with two Storage Nodes. Select any of these objects to open and edit them.

iSCSI


HP StorageWorks SAN Concepts

SAN/iQ is the control software running on the Storage Nodes. It controls all low-level data management such as disk striping, data replication across Storage Nodes, and communication with the application servers. You do not normally interact directly with SAN/iQ, but it controls all operations in the SAN.

CMC is the management interface you will use to communicate with SAN/iQ and configure the SAN. When you first run CMC, you will tell CMC to find the available Storage Nodes in your network. CMC will add them into an Available Nodes pool.

You will then create Management Groups, which collect Storage Nodes into an entity where they can be managed.

Within the Management Group you will create Clusters, which contain a subset of the Storage Nodes in the Management Group. Clusters distribute data across all Storage Nodes for increased performance and data protection.

You carve out Volumes (LUNs) from the space in a Cluster. Once you have created your desired Volumes you can present them to remote application servers, snapshot them (make point-in-time images available for later access), and do other operations on them.



Network RAID data mirroring

This slide illustrates one form of data distribution and protection used in HP StorageWorks SAN: volume mirroring. This function is called Network RAID because it operates very much like RAID in a disk controller, but using Storage Nodes instead of individual disks.

The first example above uses Network RAID-0. In hardware RAID, RAID-0 stripes data across multiple disks for higher performance. In the same way, Network RAID-0 stripes data blocks across multiple storage nodes. Block B1 goes onto the first Storage Node, block B2 goes onto the second node, and so on.

Hardware RAID-0 provides no protection against data loss, and the same is true for Network RAID-0. You can instead use Network RAID-10, which provides varying levels of data replication across the SAN. The second example above uses Network RAID-10 with 2-way mirroring. Each block is written to two separate Storage Nodes, so any single Storage Node can fail without loss of data. SAN/iQ supports 2-way mirroring with no performance penalty, since it writes to two Storage Nodes simultaneously.

SAN/iQ also supports 3-way mirroring (as shown in the third example) and 4-way mirroring. 4-way mirroring is particularly useful for high-availability multi-site installations. You can configure the SAN to have two copies of each data block at each of two different geographical locations. Thus you could lose access to one of the sites, and even lose one of the Storage Nodes at the remaining site, without losing access to your data.

iSCSI


SAN/iQ also supports network RAID with parity, called Network RAID-5 and Network RAID-6. Network RAID-5 writes 4 blocks of data and 1 block of parity across a minimum of 5 Storage Nodes, and can survive the loss of any single Storage Node. Network RAID-6 writes 4 blocks of data and 2 copies of parity blocks across a minimum of 6 Storage Nodes, and can survive the loss of any two nodes.



Configuring an HP StorageWorks SAN

The steps above will configure the SAN and present volumes to target application servers.

These steps are explained in detail in the following slides.

iSCSI


Discovering Storage Nodes

After launching the CMC, you must find the Storage Nodes in your network. CMC has several methods to accomplish this.



Creating a Management Group

When your CMC has found your Storage Nodes, you can collect them into Management Groups. Management Groups have several functions that are beyond the scope of this example. You just need to create a Management Group so you can allocate some of your storage into Volumes.

iSCSI


Creating a Cluster

Management Group is created by using a Wizard interface. This Wizard also steps you through creating your first Cluster and Volume. The main operation in Cluster creation is to choose which Storage Nodes are to be included in the Cluster.



Creating a Volume

The Wizard next steps you into creating the first Volume. At this point the name and size of the Volume, and the Cluster in which its storage resides is specified.

At this point you can also specify the data protection level (Network RAID) for the Volume, and whether the Volume is Thin Provisioned or Fully Provisioned. A Thin-Provisioned volume consumes only enough space in the Cluster to hold the data currently in the Volume. The Volume grows as needed as new data is written to the Volume, up to the maximum size specified at Volume creation time.

iSCSI


Creating a Server

SAN/iQ uses objects called Servers to represent the connection between a Volume and its target application server(s). After a volume is created, a server object is created which is used to specify the application server that is allowed to connect to it.



Connecting a Volume to a Server

Now that you have created both the Server and the Volume, you can connect to them by choosing either the Server or the Volume, that completes the SAN configuration.

At this point you must go to the application server and configure the iSCSI Initiator to point to the SAN Volume. Once the iSCSI Initiator connects to the Volume, the Volume becomes visible to the server OS. Mount the volume, using the appropriate process for your OS, and you are ready to access the SAN from your applications.

iSCSI


Final Result



Lab activity

37 uc434s c.01 2009 Hewlett-Packard Development Company, L.P.37 uc434s c.01 2009 Hewlett-Packard Development Company, L.P.

Labactivity

Module 8, Lab 1 - iSCSI LUN Mapping


SAN extension Module 9

Objectives

Objectives Discuss SAN extension technologies and implementations

Describe FCIP and its role in SAN extension FCIP performance FCIP security

Explain Fibre Channel routing implementations in a SAN



What is SAN extension?

What is SAN extension? SAN Extension is an ISL connection between two Fibre

Channel switches over extended distances Extended distances are considered to be

75m for 8Gb/s Fibre Channel ISLs150m for 4Gb/s Fibre Channel ISLs300m for 2Gb/s Fibre Channel ISLs500m for 1Gb/s Fibre Channel ISLsAny distance between a pair of Fibre Channel over IP

products

What is a SAN extension? With the advent of extension technologies specifically developed for the transport of data, you can consolidate, simplify, manage, and integrate storage in Fibre Channel SAN fabrics within the enterprise to further exploit networking investments and lower the cost to manage global storage.

A SAN extension is considered an inter-switch link (ISL) connection between two Fibre Channel switches over extended distances. Extended distances are considered to be:

150m for 4Gb/s Fibre Channel ISLs



Any distance between a pair of Fibre Channel over IP products

Whether it is called SAN Extension or SAN Bridging, HP seamlessly integrates these new technologies into the benefits of HP Fibre Channel SANs.

SAN extension


Why extend the SAN?

Why extend the SAN? The growing need for storage data Available bandwidth Distance IP technologies extend the leverage of installed SAN to

new constituents Stranded remote serversFile-based storage applications (NAS/SAN fusion)Uniting SAN islands

IP technologies extend control of the IT infrastructureShared tools Integrated solutions

The growing need for storage data that is permeating the business community, coupled with the available bandwidth afforded by IP networks or wave division multiplexing (WDM), for example, are making SAN extension an increasingly attractive option to grow the storage network. With SAN extension, users can connect to data centers at opposite ends of a campus, metropolitan, and wide-area environment. The challenge is to do so at full-wire speed, with the same reliability and availability as the storage traffic within each data center.

IP technologies extend the leverage of installed SAN to new constituents for the following:

Stranded remote servers

File-based storage applications (NAS/SAN fusion)

Uniting SAN islands

IP technologies extend control of the IT infrastructure by utilizing:

Shared tools

Integrated solutions



HP Supported SAN extension technologies

HP Supported SAN extension technologies Fibre Channel long distance technologies

Long wave transceiversDWDMCWDM

IP data protocol technologiesFCIP iFCP iSCSI

HP Supported SAN extension technologies HP supports the following technologies for Fibre Channel ISL SAN extension:

Fibre Channel long distance technologies

Long-wave transceivers

Dense Wavelength division multiplexing (DWDM)

Coarse Wave Division Multiplexing (CWDM)

IP data protocol technologies

FCIP

iFCP

iSCSI

SAN extension


SAN extension distance summary

SAN extension distance summary

FC over CWDM

Data center Campus Metro Regional National

Increasing distanceIncreasing distance

FCIP

FC over Dark Fiber

FC over DWDM

FC over SONET/SDH ONS15454

250km 256 BB_Credits at

2Gb/s

500km 256 BB_Credits at

1Gb/s

~100km

~320km

~100km~2800km(1G)

~1400km(2G)~500km

Global

~20,000km(1G)

Opt

ical

IP

200 km HP limit

FCIP upper distance measure is approximately way around the globe.

The term dark fiber typically refers to fiber optic cabling that has been laid, but remains unlit or unused. This is the simplest, but not necessarily the most cost effective or scalable method for extending SANs over distance.



Long Wave Transceivers

Long Wave TransceiversLong Wavelength SFP 1550nm 2Gb/s 110km maximum distanceApplication: GbE and 1 & 2Gb/s Fibre Channel

Long Wavelength XFP 1550nm 10Gb/s 80km maximum distanceApplication: SONET, 10G Ethernet, 10G Fibre Channel

Optical Small Form-factor Pluggable (SFP) transceivers are available in short- and long-wavelength versions. The 4 Gb/s and 2 Gb/s transceivers are known as small form-factor pluggables (SFPs) and use LC style connectors. The 1 Gb/s transceivers can be LC SFPs or gigabit interface converters (GBICs), which use SC style connectors

Short wavelength transceivers transmit at 850 nm and are used with 50 or 62.5 m multimode fiber cabling. For fiber distances greater than several hundred meters long-wavelength transceivers are used with 9 m single-mode fiber, and typically operate in the 1310 or 1550 nm range.

Optical transceivers often provide monitoring capabilities that can be viewed through FC switch management tools, allowing some level of diagnostics of the actual optical transceiver itself.

The 8 Gbps sfp require a license this applies to the Brocade 300, 5100, and 5300 switches. Without this 8G license even if the correct 8G sfp is installed the maximum speed the port would operate will be 4Gbps. If a license has been obtained and installed on the switch, the commands portdisable and portenable on the individual ports or a switchdisable and switchenable command to enable all the ports will have to be performed to enable the 8 Gbps functionality on the ports.

SAN extension


HP supports the following long-wave transceivers:

10km GBIC

100km GBIC

10km SFP

35km SFP

100km course wave division multiplexing (CWDM) SFP

Long-wave transceivers are supported on HP B-Series, HP C-Series, and HP M-Series product lines. B-Series Fibre Channel switch products support 10km and 100km GBICs (certain switch models), 10km and 35km SFPs, and 100km Coarse Wave Division Multiplexing (CWDM) SFPs. The B-Series MP Router supports 10km and 35km SFPs. C-Series Fibre Channel switch products support 10km SFPs and 100km CWDM SFPs. M-Series Fibre Channel switch products support 10km and 35km SFPs.



Coarse Wave Division Multiplexing

CWDM is much less costly than DWDM because the channel spacing is only 20nm and much less precise.

CWDM provides 8 channels between two CWDM Multiplexers over a single fiber pair.

CWDM Multiplexers are usually un-powered devices containing a very accurate prism to multiplex 8 separate wavelengths of light along a single fiber pair. Max distance is approx 100Km.

HP offers a CWDM technology solution that involves concepts similar to Dense Wave Division Multiplexing (DWDM) but is less expensive, less expandable (maximum eight channels) and works over a distance of 100km. CWDM allows up to eight 1Gbps or 2Gbps channels (or colors) to share a single fiber pair. Each channel uses a different color or wavelength transceiver. These channels are networked with a variety of wavelength specific add-drop multiplexers to enable an assortment of ring or point-to-point topologies.

Note: HP supports the use of all CWDM products as Fibre Channel ISLs provided the CWDM equipment is configured to 1Gbps or 2Gbps data rates this can give distances up to 100KM, or 4Gb/s to a distance of 40KM. Hp does not implement time division multiplexing or any additional conversion method that alter the data links other than multiplexing different wavelengths.

SAN extension


Dense Wave Division Multiplexing

A single fiber pair connecting two FC switches together through an ISL provides a single channel (wavelength of light) between the two switches.

DWDM enables up to 80 channels to share a single fiber pair by dividing the light up into discrete wavelengths or lambdas separated by approx 1nm spacing around the 1550nm wavelength.

Wavelength Division Multiplexing devices can be used to extend the distance between two Fibre Channel switches. These devices are transparent to the switches themselves and do not count as an additional hop. The only consideration that should be made to accommodate these devices is to have enough buffer-to-buffer

Adding dense or coarse wavelength division multiplexing (DWDM/CWDM) to basic Fibre Channel allows greater distances between sites than long-distance GBICs and SFPs. The difference between WDM and basic fiber configurations is the addition of a multiplex unit on both sides of the intersite link.

When using WDM, consider the following:

Always ensure WDM installation conforms to vendor specifications, and performance is affected by distance and/or limited buffer-to-buffer credits on the Fibre Channel switch. Switch vendors may limit the maximum distance between sites and apply additional configuration rules for WDM configurations:

Connecting the switch to the WDM unit typically requires one switch-to-WDM interface cable per wavelength of multimode fiber.

Note: Switches may require an Extended Fabric license.



Time Division Multiplexing (TDM) takes multiple client-side data channels, such as FC, and maps them onto a single higher-bit-rate channel for transmission on a single wavelength. TDM is used in conjunction with a WDM solution provides additional scalability and bandwidth utilization. However because TDM sometimes relies on certain FC primitives to maintain synchronization, it may require enhanced configuration when the extended fabrics are enabled. By default, Extended Fabrics E_Ports use ARB primitives (specific to Virtual Channels) as fill words between frames. The Majority of TDM devices require idles as fill words. Configuring a B-

uc434s.f.00_stu.part2.pdf

Documents

Transcript of uc434s.f.00_stu.part2.pdf