storage networking standards: recent developments · storage networking standards: recent...

Storage Networking Standards: Recent Developments © 2008 Storage Networking Industry Association. All Rights Reserved.

Storage Networking Standards: Recent Developments

David L. Black, EMC CorporationMember, SNIA Technical Council

Storage Networking Standards: Recent Developments © 2008 Storage Networking Industry Association. All Rights Reserved. 2

SNIA Legal Notice

The material contained in this tutorial is copyrighted by the SNIA. Member companies and individuals may use this material in presentations and literature under the following conditions:

Any slide or slides used must be reproduced without modificationThe SNIA must be acknowledged as source of any material used in the body of any document containing material from these presentations.

This presentation is a project of the SNIA Education Committee and the SNIA Technical Council


Abstract

Storage Networking Standards: Recent DevelopmentsInteroperability standards play a vital role in customer adoption and advancement of storage networking technologies and systems. Storage networking is based on a broad spectrum of standards (developed by multiple standards organizations) in areas such as

Fibre

Channel (INCITS T11), SCSI (INCITS T10), iSCSI (IETF), and storage management (SNIA, IETF). The current state and future direction

of

standards development can provide useful insights into technology developments. This tutorial covers storage networking standards

and

the role that the resulting standardized interfaces and functionality play in networked storage infrastructure. The tutorial presenter is a member of the SNIA Technical Council who is actively involved in

development of many storage networking standards.


About the Author

David L. BlackDistinguished Engineer, EMC CorporationMember, SNIA Technical CouncilChair, T11 FC-SP-2 (Fibre Channel Security-2) Working GroupPast Chair, IETF IP Storage (IPS) Working GroupChair, IETF Internet and Management Support for Storage

(IMSS) Working GroupCo-Chair, SNIA Fixed Content Aware Storage (FCAS) Technical

Working Group


Overview

Interoperability standards for storageConnect products from different vendors

Standards can provide technology insightEmerging technologyEvolution of existing technology

This talk: Standards developments and directionsImplications for technology vendors and users


Standards: End User Benefits

Protect technology investmentEnsure a base level of interoperabilityProvide choice among productsEnsure continuing innovationCommonality leads to less training, simpler deployment


Storage Networking Standards

Data ProtocolsSCSI (T10)Fibre Channel (T11)ATA and SATA (T13)NAS (IETF, Microsoft)IP Storage (IETF)

ManagementSMI-S (SNIA)

Uses CIM (DMTF)

SNMP (IETF)Web (IETF, W3C)

Stored DataRAID Layout (SNIA)Encryption (IEEE)Fixed Content (SNIA)


Storage Protocol Classes

Network CommunicationFibre Channel FabricIP Storage (iSCSI, FCIP, iFCP)Network Attached Storage (NAS)

Drive InterfaceFC-AL (Arbitrated Loop)Parallel SCSI and Serial Attach SCSI (SAS)ATA and Serial ATA (SATA)

StorageNetwork


Fibre Channel 1: Security (T11 FC-SP)

Fibre Channel (FC) Fabric access and config controlsControl fabric structure and what can join the fabric

In-band AuthenticationSecret (CHAP, DH-CHAP)

CHAP = Challenge Handshake Authentication ProtocolDH-CHAP = Diffie-Hellmann CHAP (adds a DH exchange)

Public Key (FCAP) and Password (FCPAP)FCAP = Fibre Channel Authentication ProtocolFCPAP = Fibre Channel Password Authentication Protocol

Secure communication channelsAdaptation of IPsec subset to Fibre Channel

FC-SP-2 project underway: updates to FC-SPAuthentication methods beyond CHAP


CHAP Authentication Protocol

Authenticate with a shared secret, random challengeBased on a secure hash, usually MD5

SecretSecret Challenge

Hash

= ?Response

Hash

Can be outsourced to RADIUS server

Host Storage


Fibre Channel 2: Inter-Fabric Routing

FC Routers inter-connect FC Storage Area Networks (SANs)Particularly useful for isolated SANs (SAN islands)

Storage and servers omitted for clarity

Connection through a fabric

Direct Router to Router Connection Router function embedded in switch

R


FC Inter-Fabric Routing Properties

Routing interconnects physical and

virtual fabricsVirtual fabrics can be in the same or different physical SANRoutes can pass through existing fabrics and switches

The interconnected fabrics do not mergePrevents some disruption propagation (e.g., RSCN)

RSCN = Registered State Change Notification

Translation of FC addresses required (unlike IP routing)

Routing is transparent to servers and storageZoning, name service, etc. continue to work

Routing function packaging:In a separate router or combined with a fabric switch

Check out SNIA Tutorial:

Fibre Channel


Fibre Channel 3: Communication Media

4 Gbit/sec Fibre Channel speedCompatible upgrade, shorter distance limitsNext speed upgrade will be to 8 Gbit/sec

Limited inter-switch use of 10 Gbit/sec FC

OM3 multimode optical fiber (50μ)2 Gbit/sec FC reach: 300m on OM2 fiber4 Gbit/sec FC reach: 150m on OM2 fiber, 300m+ on OM38 Gbit/sec FC reach: 300m on OM3 requires new “linear”

transceiver

FC Base-T: Fibre Channel over copper twisted pair cablesFibre Channel (and only FC) over copper Ethernet cablesUnlikely to be implemented, see FCoE instead


Fibre Channel 4: FCoE

FCoE = Fibre Channel over EthernetMotivation: Consolidated server I/O over Ethernet

Server racks (e.g., blades) –

cost, space, power considerationsEthernet access to Fibre Channel storage infrastructure (SAN)

FCoE: Encapsulate Fibre Channel frames in Ethernet framesRequires at least baby jumbo (2.5k) Ethernet frames

Anticipate Ethernet enhancements to eliminate frame dropsBack-propagation of Ethernet Pause across switchesPer-Priority Pause (separate priorities for FC vs. IP traffic)

Discovery protocol precedes fabric loginAssociates FCoE server VN_Port with fabric VF_Port Also sets up addressing, checks jumbo frame support


FCoE





StorageNetwork


IP Storage Developments

RFC specifications have publishediSCSI (RFC 3720), FCIP (RFC 3821), iFCP (RFC 4172)

iSCSI Corrections and Clarifications RFC publishedMinor corrections and clarifications (RFC 5048)

RDMA for iSCSI (iSER)RDMA = Remote DMA over a TCP/IP network (iWARP)iSER = iSCSI Extensions for RDMA (RFC 5046)

InfiniBand: iSER is an alternative to SRP for storage gateways to FCSRP = SCSI RDMA Protocol

Fibre Channel Pseudo-Wire over MPLSBeing jointly developed by IETF and T11MPLS: Multi-Protocol Label Switching

Telecommunications carrier infrastructure technology


NAS and iSCSI





StorageNetwork


Network Attached Storage (NAS)

Two primary file serving protocols:1.

NFS, primarily for Unix clients (IETF)

Transition to NFSv4 is underwayParallel NFS (pNFS): SAN filesystem support

Parallel (e.g. striped) access across NFS servers

RDMA (iWARP) for NFSDraft of NFS 4.1 specification:

draft-ietf-nfsv4-minorversion1-21.txtSessions, directory delegations and pNFS

2.

CIFS, primarily for Windows clients (Microsoft) Please ask Microsoft


NAS & iSCSI


Parallel NFS - pNFS

NFS file naming, management, and administration Parallel high bandwidth file access (via Storage Network)

StorageNetwork NFS Server

Data Network - LAN pNFS Data

pNFS Control





StorageNetwork


Drive Interface Developments

ATA drives: Serial ATA (SATA)Replacing Parallel ATA

SCSI drives: Serial Attached SCSI (SAS)Replacing Parallel SCSIConnection-based protocol (not packet switched)SAS Can carry SATA traffic, attach to SATA drivesSAS-2 functionally complete, includes:

SAS Zoning for shared SAS infrastructure and shared SAS storage6 Gbit/sec interface speed

Fibre Channel drives: FC-AL4 Gbit/sec drives availableFATA/FC-LC: ATA-class disk with FC-AL interfaceFC-SATA standard for FC-attached SATA drives


SAS & SATA


Desktop, Nearline

and Enterprise HDDs


SCSI Command Set Developments

SCSI Command Sets are used for:Storage Networks (e.g., FC Fabric, iSCSI)Disk and Tape drives (e.g., FC-AL, SAS)

Tape Commands for encrypting tape drivesSSC-3 standard (SCSI Stream Commands)

Security FrameworksEncrypt portions of commands (e.g., tape encryption key)Cryptographic capability-based access control (CbCS)

OSD security applied to other SCSI command setsOSD = Object-based Storage Device

SPC-4 standard (SCSI Primary Commands)


SCSI Security





Uses CIM (DMTF)




Management Application

–

Platform IndependentDistributedAutomated DiscoverySecurityLockingObject Oriented

SMI-SInterface

CIM/WBEMTechnology

Tape Library Switch Array Many Other

Vendor UniqueFunction

MOF MOF MOF MOF

StandardObject Model perDevice

Auto-generation of infrastructure

constructs

Integration Infrastructure Object Model Mapping

SMI-S: Model-Based Management


SNIA SMI-Specification

V1.0-V1.1Bluefin

Contribution to SNIA

SNIA SMI-SV1.2-V1.3

SNIA SMI-SV1.4-V1.5

& MF SpecsSNIA CTP SNIA CTP Provider TestsProvider Tests

SMISMI--Lab providerLab providervalidationvalidation

Client EnablementClient Enablement(e.g., Management Frameworks)(e.g., Management Frameworks)

Health/Fault ManagementHealth/Fault Management

Secure StorageSecure Storage

SMISMI--Lab clientLab clientvalidationvalidation

SNIA CTP SNIA CTP Client TestsClient Tests

SMI-S Ecosystem Road Map

Software ProjectsSoftware Projects

Tools:Tools:ProtocolProtocolMIFGenMIFGen

Expanded CTP Expanded CTP Provider TestsProvider Tests Ease of DeploymentEase of Deployment

Release ThemesRelease Themes--MonitoringMonitoring

--HealthHealth--SecuritySecurity

Performance Performance ManagementManagement

Expanded CTP Expanded CTP Client TestsClient Tests

20032002 2004 2005 2006 2007 2008 2009 2010 2011 2012

SNIA SMI-SV1.6-V1.7

& MF Specs

Functional CoverageFunctional Coverage(Vendor Extensions)(Vendor Extensions)

mailto:[email protected]


SMI-S Protocol Developments

Web Services (OASIS): increasing interestTwo management stacks (WSDM, WS-Management)

Convergence whitepaper has been published

WS-Management support for SMI-S: Version 1.4 or later

IPv6 deploymentUS government IPv6 requirements profiles:

DISA = Defense Information Systems AgencyNIST = National Institute of Standards and Technology

IPv4 to IPv6 transition: Mostly transparent to SMI-S

CIM over SCSI: SCSI commands for SMI-SEnables inband management over storage interfaceBUT –

Work on CIM over SCSI has stalled


SMI-S





Uses CIM (DMTF)




SNIA Disk Data Format (DDF)

DDF -

Data structures describing how data is distributed across the drives in a RAID implementation.Primary intended scope: RAID controllers for internal and direct attach storage.Does not standardize operating system/RAID controller interface or create a single driver

SNIA Shared Storage Model

File/record layer

Block layer

Database (dbms)

Storage devices (disks, …)

Application

Block aggregation

Host

Network

Device

DDF Scope

Serv

ices

File system (FS)


IEEE P1619 : Encrypt Stored Data at Rest

Threat: Move encrypted blocksAttacker may know location of data, even if it’s encrypted

Disks: No visible room for additional integrity checks“Tweaked”

Encryption modes prevent block swapping

Two keys used: encryption key and tweak keyIf encrypted blocks moved: Decryption produces gibberish

P1619 disk encryption: XEX tweakXTS-AES mode: XTS = XEX Tweak + ciphertext Stealing128-bit and 256-bit key sizes (2 keys needed)


IEEE P1619.1: Tape Encryption

Tapes have room for additional integrity checksCombined modes: 256-bit AES key

Combined = encryption + cryptographic integrityAES-GCM (Galois Counter Mode) –

hardware friendly

AES-CCM (Counter with CBC-MAC) –

simpler

Other modes: 256-bit AES key + integrity key(s)AES-CBC with HMAC-SHA-(1, 256, or 512)XTS-AES with HMAC-SHA-512


New IEEE P1619 efforts

P1619.2: Wide Block encryption for disksWrite a disk block, make a small change, rewrite the blockAttacker compares old and new ciphertext

Change may be as small as 16 bytes (for 128-bit AES)Wide block AES modes: Change is at least 512 bytes

P1619.3: Key Management for protecting stored dataVery important: Loss of encryption key IS

Loss of dataInitial goal: keys for use with P1619-defined encryptionScope: All stored data, not just use of P1619 encryption

Includes storage, management and distribution of keys

P1619.2 and P1619.3 –

In early stages of work efforts


Purpose: Fixed Content Storage AccessStore content (data) that does not changeIndependent of location of storage system or data

Motivated by migration to new systems and technology

Vendor independent APILanguage independent functionality (+ mappings to Java and C)

Combine content & metadata into single “record”

(XSet)Multiple application and system metadata formatsSupport for unstructured metadata (e.g., thumbnails)Flat namespace for system scaling

Basic Query, Management and Security functionalityRest of functionality left to applications and/or other interfaces

XAM API for Fixed Content


SNIA: XAM API status

FCAS Technical WG (TWG) developing specsFCAS = Fixed Content-Aware Storage

XAM API specs are functionally completeArchitecture, language bindings to C and JavaC binding also for C++, but does not use C++ objects

Reference implementation under developmentXAM SDK (Software Development Kit) TWG


XAM





Uses CIM (DMTF)




Getting Involved in Standards

End users are always welcomeRemind participants why the standard mattersHelp make the end result usable and useful

Lots of opportunities to participateVoting or contributing memberObserver: Still very important

No Substitute for hallway conversations


National and International Standards

Standards Progression Path:1.

Development in standards body (e.g., T11 for Fibre Channel),2.

Becomes a national standard (e.g., ANSI)3.

Becomes an international standard (ISO)

INCITS: Umbrella Standards OrganizationUmbrella for T10 (SCSI), T11(FC), T13 (ATA) and SNIAShepherds completed standards to ANSI and ISOUsual path: Completed standard to INCITS to ANSI to ISO

Not all standards follow this pathIETF RFCs are internationally recognized without ISO approvalIndustry consortia standards (e.g., PCI)Vendor de-facto standards (e.g., CIFS)


Block Storage Communication Protocols

T10

T11

IETF

SCSI Architecture (SAM) & Commands (SCSI-3)

Any IPNetwork

iSCSITCPIP

IPFCIPiFCP

TCP

Any IPNetwork

Parallel SCSI &

SAS

SCSI & SAS Cables

Fibre Channel

FCP VI FICON IP (RFC 4338)

FC Fibers, Hubs, Switches

FC-1FC-2

FC-0


Storage-Related Standards Organizations

Storage Networking Industry Association (www.snia.org)Storage Management (SMI-S) and other topics

Distributed Management Task Force (www.dmtf.org)Systems Management

INCITS Technical CommitteesSCSI and SAS: T10 (www.t10.org)Fibre Channel: T11 (www.t11.org)ATA and SATA: T13 (www.t13.org)

IETF: Internet Engineering Task Force (www.ietf.org)IP and Internet-related protocols, including IP Storage and NFS

IEEE: Institute of Electrical and Electronics EngineersEncrypted Media: P1619 (ieee-p1619.wetpaint.com)


Q&A / Feedback

Please send any questions or comments on this presentation to SNIA: [email protected]

and the

SNIA Technical Council: [email protected]

Many thanks to the following individuals for their contributions to this tutorial.

SNIA Education Committee

David L. Black Steven WilsonMark Carlson Bill DawkinsZoran Cakeljic SW WorthEric Hibbard Walter Dey



storage networking standards: recent developments · storage networking standards: recent...

Documents