storage networking 8

8/14/2019 Storage Networking 8

http://slidepdf.com/reader/full/storage-networking-8 1/51

Storage Networking 101SAN Solutions

David J. MossinghoffDirector, Storage Solutions

Forsythe Solutions GroupJune, 2006

Overview

The focus of this session is architecting networkedstorage for the enterprise and will include tips onimplementing a tiered network storageinfrastructure for both local and remote access…

In this session you will learn:• The current state of networked storage protocols, how they relate to

disk technologies and where these SNW technologies will merge anddiverge.

• How to best utilize file or block based storage for Fibre Channel, IPprotocols and for your storage network.

• What are the areas of “storage intelligence” in networked storagetoday, and what might the future hold?

• Factors to consider when building a total cost of ownershipcomparison between the different technologies and protocols.

Agenda

• Information Management: the Big Picture

• Today’s Storage Challenges

• Introduction to Storage NetworkingArchitectures

• The “6 Levels of Storage Networking”

• Virtualization- with focus on SAN

• Q & A

The Big Picture

Main Focustoday is on storage

networking technology

Today’s Storage Challenges

• Selecting the right mix of storagetechnology

• Streamlining the process of managing

resources• Improving availability of data, with

adequate protection/security• Providing for your company’s current and

future storage needs• Delivering cost effective solutions that

meet the business needs

Value of Storage Networking

• Key enabler for server/storage consolidation,“tiering”, and virtualization • More effective and efficient data availability

– High operational availability

– Enhanced Backup & Recovery– Enhanced Disaster Recovery & Restart

• Improved scalability, provisioning, utilization ofstorage capacity

• Improved application performance• Improved data/file sharing• Enabler for significant TCO savings for data &

storage management

Proof points

* Source: IDC IT Management Survey - 2005

• Top reasons for deploying a SAN*

– Improved back-up & recovery 46%– Server and storage consolidation 40%– On-going demands for additional capacity 37%– Improved application performance 31%– Improved disaster recovery 27%

– New project or application deployment 23%

Networked Storage TechnologiesSAN

Storage areane tworks

NASNetwork-attached

s torage

CASContent-addressed

s torage

Type oftransport

Fibre Channel (FCP,FICON);IP (iSCSI, FCIP,iFCP)

IP (front end),Optional-FC(backend)

Type of data Block File Object,fixed content

Keyrequirement

High Operationalavailability,Deterministicperformance

Multi-protocolFile sharing

Long term retention,integrity assurance

Typicalapplications

OLTP, datawarehousing, ERP

Software and productdevelopment;fileserverconsolidation

ContentManagement,Compliant storageand retrieval

Storage & SNW Technology Alternatives

ApplicationServer

FileSystem

JBOD orBasic Disk

FC,ATA

NAS/CAS

File System

TCP/IP EthernetSwitch

ApplicationServer

FCPSwitch/Director

ApplicationServer

iSCSI/IP EthernetSwitch

FileSystem

High cost-of-ownership-utilization,managementInflexibleSneaker-netmanagement

Transmission optimized forI/O block data movementSeparates LAN and SANFC SAN is matureiSCSI is “emerging” and

viable

Transmission optimizedfor file or “Objectoriented” transactions IO traffic travels overEthernetFor NAS – May also use

gateway into FC SAN

SAN Characteristics

• Service level “enablers”

– Operational availability

– Reliability and serviceability– Performance (response time and throughput)

– Scalability (with performance)

– Provisioning ability for new ports/connections

SAN Characteristics

• Related key characteristics– Viability of manufacturer/market share

– Quality of partnership with your company

– Quality of service and support

– Certified support of required servers/OS levels

– Efficient and effective SAN manageability

• Total cost sensitivity (Price = Cost)

Key Priorities: An example

Similar for other "Key Charactertics"Priority Legend:

Very HighHigh

MediumLow

Lowest

F C D i r e c t o r

C o l l a p s e d C o r e

S A N E x t e n s i o n

F C C o r e < > E

D i r e c t o r + S w i t c h

F C S w i t c h

I P S A N

Typical Storage Tier Supported: Tier 1 Tier 1 Tier 1, 2 Tier 2,3 Tier 3 Tier 3, 4Storage Connectivity Service

Levels/Characteristics

Relative

Priority

Relative

Priority

Relative

Priority

Relative

Priority

Relative

Priority

Relative

PriorityService levels

AvailabilityReliability/Servicability

PerformanceScalability

Provisioning

Price Sensitivity

Economics - Storage Connectivity

Connectivity Server Path Mgt Cost of Type Image Size Software Connect.

(not included)FC Director/Collapsed Core Very Large Probable 12,400$

SAN Ext. (Bridge/Router) N/A N/A 8,000$

FC Core<> Edge Large Probable 4,700$

FC Switch Large,Med Potential 3,700$

FC Switch Med N/A 1,850$

IP Switch/FC Bridge Med,Small Potential 1,600$

IP Switch Med,Small Potential 1,130$IP Switch/FC Bridge Small N/A 765$

IP Switch Small N/A 565$

Includes director, switch, HBA, cabling costs over 3 yrs.

6 Levels of Storage Networking

Direct AttachedStorage(DAS)

Levels of Data Availability

Problem: Stranded Storage

• Poor use of disk capacity• Inadequate data protection – may lead to

artificial server growth

• Minimal-to-no disk storage management• Difficult to share data between applications• Major inhibitor: cost of FC SAN connectivity

may be higher than server cost!

Gigabit/100Mb - Ethernet / IP

Servers with d irec t- at tached s torage

FC SANSwitchBased(Local)

FC SAN-Switch Design

1Gb,2Gb, 4Gb Switch 1Gb,2Gb, 4Gb Sw itch

ServersSingle or Dual

FC HBA’s

Fibre ChannelGigabit/100Mb Ethernet / IP

F-port

F-port F-port

F-port

N-ports

Node (N) port

Fabric (F) Port

FC SAN with FC Switches

• Simple design• Low cost relative to other FC SAN

alternatives

• Scales well from a few to 100 usable ports• Simple to manage• Universally supported / certified

• Multiple manufacturer / HBA provideroptions• Larger environments may have multiple

“SAN Islands”

FC SAN-Switch Design-Mesh

1 Gb,2Gb, 4Gb Sw itches1 Gb,2Gb, 4Gb Sw itches

ServersSingle or Dual

FC HBA’s

Scales up to 100 usable ports

ISL’s (“hops”)

E-ports usedTo link Switches

& Create ISL’s

E-Ports

IP StorageNetworks(Local orDistance)

(NAS, iSCSI)

$1,000

$1,500

$2,000

$2,500

$3,000

2005 2006 2007 2008

iSCSI Marke t

WW Market

Source: IDC- 2006

• Data growth, sharing, and server proliferation can beexpensive and cumbersome to manage

• Scalability, data availability, and sharing can be amajor problem with a DAS environment

• Over-provisioning and data protection complexity

make DAS increasingly expensive• Applications may require a block based (DAS or a

SAN) solution• Other applications may benefit from a file based (NAS)

solution• Cost, complexity and lack of expertise can prohibittraditional Fibre Channel SAN implementation

• IP storage networking (iSCSI & NAS) can addressthese challenges

IP Storage – Why the ―Buzz?

Advantages of IP Networking• Common and well proven technology

– Low acquisition costs– Standards-based solutions– Commodity economics– Ethernet in every corporation

• Low management costs– Familiar network technology and management tools– Proven reliable/interoperable transport infrastructure

• Local area and wide area networkconnectivity

– WAN enables remote data replication and disaster recovery

• Long-term viability– Large R&D investment profile, strong roadmap– 10Gb Ethernet emerging – significant for IP storage

Why iSCSI is Important

• NAS has proven IP storage networking viability• iSCSI software initiators included with major

operating systems eases to deployment of IPSANs

• Networking capabilities can simplify IP SANmanagement

• Lower cost infrastructure broadens reach of IPSAN solutions

• Leveraging IP networking investments andknowledge base lowers total cost of ownership

iSCSI is a viable IP-SAN solution today!

(for the right applications)

iSCSI Building Blocks

• iSCSI is SCSI-3 command framesencapsulated in IP packets (Typically over GbE)– IETF standard documented RFC3720

• HOST/INITIATOR– iSCSI Software Initiator (NIC)

– TCP Off-load Engine (TOE)– iSCSI Host Bus Adapter (HBA) (some support remote

boot)• DISK ARRAY/TARGET

– Handled by iSCSI compatible storage array• iSCSI software target driver• Standard NIC connectivity• iSCSI to FC-SAN bridges available from multiple

manufacturers

Solution —iSCSI Integration

• Connects servers via iSCSI to existing fibre channel SAN– Low cost per server connection

• Leverages existing IP network/skills• Improved usage and flexibility of storage assets to

applications

• Improved ability for centralized data protection

Storage consolida ted on SAN

Servers connec tedto SAN v ia iSCSI

iSCSI toFC SAN Br idge

iSCSI Disk A rray(iSCSI - Tape is als o po ss ible)

FC SANF1/F2

Proof Points -Performance

Enterprise Strategy Group Validation study (4/04) – http://www.netapp.com/tech_library/ftp/analyst/ar1023.pdf

Proof Points - Performance

Throughput(TPM)

DAS iSCSI FC

iSCSI performance is close to FC4000 SQL us ers AND 4000 Notes User s AND 8 SAS Queries

Throughput Improvem ent: N/A 33% 44%Response Time Improvement: N/A 63% 88%

Enterprise Strategy Group Validation study (4/04) – http://www.netapp.com/tech_library/ftp/analyst/ar1023.pdf

FC SAN-DirectorBased ,Dual Fabric(Local)

Direct AttachedStorage(DAS)IP Storage

Networks(Local orDistance)

(NAS, iSCSI)

FC Director Design Options

2 and/or 4 Gb FC linkTrunking

256 Por t

Director

140 Por t

Director

64 po rtDirector

F1 F2 F2F1

ISL/HopISL/Hop

Tape and/orVirtual Tape

Subsystem(s)

Required Connectivity to eachDirector and Fabric

FC SAN “Core<> Edge”

Or “Collapsed Core” Multi-Fabric

(Local)

FCSANSwitchBased

(Local)FC SAN-DirectorBased,Dual Fabric(Local)

Large SAN Connectivity Concern

• Inter-switch links (ISLs) used to link switches and/ordirectors to build larger SANs• Multiple ISLs are typically required for performance• Server/storage ports go down; effective price goes up• ISL traffic is static; links may be under-utilized

ISL’s

S e r v e r s

10% ISL usage30%60%90%

Solution Trunking

Solution —Trunking(with Automatic Load Balancing)

• Fabric-data traffic more evenly distributed among ISLs• All ISLs share bandwidth• Overall bandwidth improved• Network design and administration is simplified

e r v e r s

~50% usage~50% usage~50% usage~50% usage

What is a ―Fan -in-Ratio? • When using a “core<>edge” design, it is

important to consider the “fan in ratio” • Measure of the relative incoming “max

bandwidth” to the available ISL bandwidth intothe core

• Example:– Servers have 1 Gb FC HBA’s coming into 32 -port FC switches

(2Gb capable)– Switches are connected via ISL’s to core directors (which are

also 2 Gb capable -presume ISL Trunking is enabled)

– If (3) 2Gb ISL’s per switch are used, the “Fan -in- Ratio” is: • 32 ports – 3 ports = 29 ports * 1 Gb @ = 29 Gb• (3) ISL’s * 2 Gb = 6Gb • 29 Gb/6Gb = 5:1 (approx) “fan -in- ratio” … (good R.O.T)

Director / Switch Scalability

Up to 64

64 to 256

256 to >1,000

LeastComplexity

Highest Availability

Lowest

AcquisitionCost

Number ofHosts

SwitchesSwitchesSwitches

Switches

Director

Switches

Director

Switches

Director

Advantages of Core:Edge

• Scalability - Up to (16) switch domains can beattached to each director fabric– Director “E - Ports” are auto -sensing

• Scalability example of usable ports (non-ISL) – (2) 64-port directors+edge switches = 650 u-ports– (2) 140 – port directors+edge switches = 1,100 u-ports– (2) 256-port directors+edge switches = 1,326 u-ports

• The effective cost per port is reduced vs. an alldirector solution– Due to lower cost per port of FC Switches– Scalability within a fabric is increased more economically

• If designed properly– No single points of failure in the SAN (for dual path servers)

– Performance scales with port count

SAN overDistance

(Replication,Remote Tape,Extended SAN)

Gigaman, OCx,DWDM

iFCP, FCiP

Bridging/Routing

FC SAN-DirectorBasedDual Fabric(Local)

(Local)

(NAS, iSCSI)

Extending the SAN over Distance

• Gateway-to-gateway protocol– either FCP, FCIP or iFCP

• Supports direct Fibre Channel connection tostorage• Provide either server<> Storage and/or

Array<>Array connectivity

IP routingE_Port terminationE_Port termination

Fibre Channeldir/switch

FCPgateway

Fibre Channeldir/switch

MAN /WAN

• High “metro optical network” bandwidth (DWDM)

• SAN extension through ISLs creates large set of fabrics• Propagation of faults across entire fabric• Service disruptions from fabric changes impacts all fabrics

• Custom network configurations supported with SONET or ATM

Fibre ChannelDWDM link

MON(dark Fibre)

Remote/Repl icat ion s i teExis t ing SAN

SANF1/F2

FCP/DWDMGateway

• SAN extension through ISLs creates large set of fabrics• Propagation of faults across entire fabric

• Service disruptions from fabric changes impacts all fabrics• Custom network configurations supported with SONET or ATM

• Optional data compression and fast write features can resultin higher throughput and lower network costs

Fibre ChannelGigabit Ethernet / IP

Remote/Repl icat ion s i teExis t ing SAN

FCiPGateway

IPNetwork

SANF1/F2

iFCP Solution

• iFCP protocol provides “fabric isolation” between sites • Prevents fault propagation / zone definition isolation• Optional data compression and fast write features can

result in higher throughput and lower network costs

iFCPGateway

IPNetwork

Fibre ChannelGigabit Ethernet / IP

Repl ica tion s i t eExis t ing SAN

iFCPGateway

SANF1/F2

SANF3/F4

SAN Cabling Considerations

SAN Cabling Considerations(Speed and Distance Matters)

Fiber Optic Glass PortSpeed

OperatingDistanceFilament Core

50 micron 1 Gb/s 500 m(multi-mode) 2 Gb/s 300 m

4 Gb/s 150 m62.5 micron 1 Gb/s 300 m

(multi-mode) 2 Gb/s 150 m

4 Gb/s 70 m9 micron 1 Gb/s 10 km

(single-mode) 2 Gb/s 10 km4 Gb/s 2 km

FC SAN-DirectorBasedDual Fabric(Local)

(Local)

SAN overDistance

(Replication,Remote Tape,Extended SAN)

Gigaman, OCx,DWDM

FCP, iFCP, FCiP

Bridging/Routing

(NAS, iSCSI)

Virtualization

Storage and SAN Virtualization

• Environment profile where this applies– Multiple, heterogeneous storage arrays– Multiple “SAN islands” – Volatile environment, rapid growth rates– “Multi - tenancy” (and potentially formal chargeback) is

important– Need for improved QoS for storage resources– Total cost of ownership sensitivity

• SAN is required for heterogeneous storagevirtualization– And the “storage - V” intelligence may exist in the SAN

• The SAN itself may be virtualized– VSAN’s (logical), SAN partitions (physical)

Virtualization –

Virtualization What Problems are we solving?

• Enables lower TCO and higher effectivenessand efficiency of the enterprise storageresources– Standardize and simplify the “storage operating

environments” – Common local replication– Common remote replication– Simplifies and speeds provisioning– May provide “concurrent data movement” in the storage

hierarchy (key for implementing ILM and tiered storage)– Single pane of glass storage management– SAN and storage “multi - tenancy” – Improved QoS and chargeback

SAN Based Storage Virtualization

2 and/or 4 Gb linkTrunking

Director

SAN Virtualizationengine

(Blade or Applianc e)

Required Connectivity to eachDirector and Fabric

VirtualizationControl Workstation

(Metadata)

Ethernet

All “virtualized” IO goes through theVirtualization EnginePrior to going to disk

SAN Virtualization

Dynamic Partitioning:• Partitioning enables a “virtual director”

• Each director fourpartitions (V-directors)

• Partitions own a subset ofthe ports on the system

• Partitions are managedindependently and

remain isolated fromother partitions

• Common SANmanagement console forall partitions Web

services

Financialapplication

Vi t l SAN (VSAN )

Virtual SANs (VSANs)

• Similar concept to partitioning– Defined logically (less physical segregation)– Up to (4) VSAN’s/director are logically defined

• Inter-VSAN Routing

– Allows sharing of centralized storage services, such astape libraries and disks, across VSANs

– Distributed, scaleable, and highly resilient architecture

– Transparent to third-party switches

• Quality-of-Service (QoS) Advanced TrafficManagement– Example: Prioritizing latency-sensitive OLTP transactions

over throughput-intensive data-warehousing or B/U traffic

Conclusion:

The focus of this session was architectingnetworked storage for the enterprise and includedtips on implementing a tiered network storageinfrastructure for both local and remote access…

In this session, (hopefully) you learned:• The current state of networked storage protocols, how they relate to

disk technologies and where these SNW technologies will merge anddiverge.

• How to best utilize file or block based storage for Fibre Channel, IP

protocols and for your storage network.• What are the areas of “storage intelligence” in networked storage

today, and what might the future hold?• Factors to consider when building a total cost of ownership

comparison between the different technologies and protocols.

Questions?

David J. Mossinghoff

Forsythe Solutions Group

(913) 323-6857

dmossinghoff@forsythe.com

storage networking 8

Documents

ibm storage networking san64b-6 switchibm storage networking...

dec-connectivity networking, communication & bulk storage

storage networking virtualization

metropolitan and wide area storage networking

describing fibre channel storage networking

storage networking standards: recent developments ·...

storage networking interfaces

storage networking i/o guide - asbis

storage networking

data networking and storage - poalimcm.com€¦ · data...

cloud storage for cloud computing - storage networking...

education storage networking standards: future...

cisco storage networking protect scale-simplify_dec_2016

storage networking industry association 2008 … networking...

storage networking strategic decision-making

networking and storage concepts in vmware

storage networking laboratory - in persian

storage networking industry association

3852 storage networking[1]

networking products server/storage racks · 2006. 8....