Вы находитесь на странице: 1из 30
SMB remote file protocol (including SMB 3.0) Jose Barreto, Microsoft

SMB remote file protocol (including SMB 3.0)

Jose Barreto, Microsoft

SNIA Legal Notice

The material contained in this tutorial is copyrighted by the SNIA unless otherwise noted. Member companies and individual members may use this material in presentations and literature under the
Member companies and individual members may use this material in presentations and literature under the following conditions:The material contained in this tutorial is copyrighted by the SNIA unless otherwise noted.

Any slide or slides used must be reproduced in their entirety without modificationpresentations and literature under the following conditions: The SNIA must be acknowledged as the source of

The SNIA must be acknowledged as the 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. Neither the author nor the
any document containing material from these presentations. This presentation is a project of the SNIA Education This presentation is a project of the SNIA Education Committee.
Neither the author nor the presenter is an attorney and nothing in this presentation is intended to be, or should be construed as legal advice or an opinion of counsel. If you need legal advice or a legal opinion please contact your attorney. presentation is a project of the SNIA Education Committee. The information presented herein represents the author's
The information presented herein represents the author's personal opinion and current understanding of the relevant issues involved.The author, the presenter, and the SNIA do not assume any responsibility or liability for damages arising out of any reliance on or use of this information. NO WARRANTIES, EXPRESS OR IMPLIED. USE AT YOUR OWN RISK.as legal advice or an opinion of counsel. If you need legal advice or a legal

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

22

Abstract and Learning Objectives

Title: SMB remote file protocol (including SMB 3.0)Abstract and Learning Objectives Abstract The SMB protocol has evolved over time from CIFS to SMB1

AbstractTitle: SMB remote file protocol (including SMB 3.0) The SMB protocol has evolved over time from

The SMB protocol has evolved over time from CIFS to SMB1 to SMB2, with implementations by dozens of vendors including most major Operating Systems and NAS solutions. The SMB 3.0 protocol, announced at the SNIA Storage Developers Conference in September 2011, is expected to have its first commercial implementations by Microsoft, NetApp and EMC by the end of 2012 (and potentially more later). This SNIA Tutorial describes the basic architecture of the SMB protocol and basic operations, including connecting to a share, negotiating a dialect, executing operations and disconnecting from a share. The second part of the tutorial covers improvements in the version 2 of the protocol, including a reduced command set, support for asynchronous operations, compounding of operations, durable and resilient file handles, file leasing and large MTU support. The final part covers the latest changes in the SMB 3.0 version, including persistent handles (SMB Transparent Failover), active/active clusters (SMB Scale-Out), multiple connections per sessions (SMB Multichannel), support for RDMA protocols (SMB Direct), snapshot-based backups (VSS for Remote File Shares) opportunistic locking of folders (SMB Directory Leasing), and SMB encryption.Title: SMB remote file protocol (including SMB 3.0) Abstract Objectives Understand the basic architecture of the

Objectivesof folders (SMB Directory Leasing), and SMB encryption. Understand the basic architecture of the SMB protocol

Understand the basic architecture of the SMB protocol family(SMB Directory Leasing), and SMB encryption. Objectives Enumerate the main capabilities introduced with SMB 2.0

Enumerate the main capabilities introduced with SMB 2.0Understand the basic architecture of the SMB protocol family Describe the main capabilities introduced with SMB

Describe the main capabilities introduced with SMB 3.0Enumerate the main capabilities introduced with SMB 2.0 SMB remote file protocol (including SMB 3.0) ©

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

3

Summary

Summary Basics and History Remote file protocol A brief history of CIFS, SMB, SMB2 and SMB3

Basics and History

Remote file protocolSummary Basics and History A brief history of CIFS, SMB, SMB2 and SMB3 SMB implementers The

A brief history of CIFS, SMB, SMB2 and SMB3Summary Basics and History Remote file protocol SMB implementers The basics of SMB SMB 2.0 SMB

SMB implementersfile protocol A brief history of CIFS, SMB, SMB2 and SMB3 The basics of SMB SMB

The basics of SMBA brief history of CIFS, SMB, SMB2 and SMB3 SMB implementers SMB 2.0 SMB 2.1 SMB

SMB 2.0CIFS, SMB, SMB2 and SMB3 SMB implementers The basics of SMB SMB 2.1 SMB 3.0 SMB

SMB 2.1SMB2 and SMB3 SMB implementers The basics of SMB SMB 2.0 SMB 3.0 SMB Transparent Failover

and SMB3 SMB implementers The basics of SMB SMB 2.0 SMB 2.1 SMB 3.0 SMB Transparent

SMB 3.0

SMB Transparent FailoverSMB implementers The basics of SMB SMB 2.0 SMB 2.1 SMB 3.0 SMB Scale-Out SMB Witness

SMB Scale-Outof SMB SMB 2.0 SMB 2.1 SMB 3.0 SMB Transparent Failover SMB Witness SMB Multichannel SMB

SMB Witness2.0 SMB 2.1 SMB 3.0 SMB Transparent Failover SMB Scale-Out SMB Multichannel SMB Direct SMB Directory

SMB MultichannelSMB 3.0 SMB Transparent Failover SMB Scale-Out SMB Witness SMB Direct SMB Directory Leasing SMB Encryption

SMB DirectFailover SMB Scale-Out SMB Witness SMB Multichannel SMB Directory Leasing SMB Encryption VSS for Remote File

SMB Directory LeasingSMB Scale-Out SMB Witness SMB Multichannel SMB Direct SMB Encryption VSS for Remote File Shares SMB

SMB EncryptionWitness SMB Multichannel SMB Direct SMB Directory Leasing VSS for Remote File Shares SMB remote file

VSS for Remote File SharesMultichannel SMB Direct SMB Directory Leasing SMB Encryption SMB remote file protocol (including SMB 3.0) ©

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

4

Remote file protocol

Remote (not Local)Remote file protocol Access file across the wire (LAN,WAN) File (not Block) Different semantics Protocol Well-defined

Remote file protocol Remote (not Local) Access file across the wire (LAN,WAN) File (not Block) Different

Access file across the wire (LAN,WAN)

File (not Block)Remote (not Local) Access file across the wire (LAN,WAN) Different semantics Protocol Well-defined and documented

Different semanticsAccess file across the wire (LAN,WAN) File (not Block) Protocol Well-defined and documented Examples NFS, SMB2,

Protocolthe wire (LAN,WAN) File (not Block) Different semantics Well-defined and documented Examples NFS, SMB2, SMB3,WebDAV

wire (LAN,WAN) File (not Block) Different semantics Protocol Well-defined and documented Examples NFS, SMB2, SMB3,WebDAV

Well-defined and documented

ExamplesDifferent semantics Protocol Well-defined and documented NFS, SMB2, SMB3,WebDAV SMB remote file protocol (including

semantics Protocol Well-defined and documented Examples NFS, SMB2, SMB3,WebDAV SMB remote file protocol (including

NFS, SMB2, SMB3,WebDAV

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

5

A brief history of CIFS, SMB, SMB2 and SMB3

SMB - 1980sA brief history of CIFS, SMB, SMB2 and SMB3 PC-DOS – 1984 LAN Manager – 1988

PC-DOS – 1984A brief history of CIFS, SMB, SMB2 and SMB3 SMB - 1980s LAN Manager – 1988

LAN Manager – 1988of CIFS, SMB, SMB2 and SMB3 SMB - 1980s PC-DOS – 1984 Implemented on Unix and

Implemented on Unix and other operating systems (part of the OS or as a suite like Samba)and SMB3 SMB - 1980s PC-DOS – 1984 LAN Manager – 1988 CIFS - 1996 Windows

CIFS - 1996operating systems (part of the OS or as a suite like Samba) Windows NT 4.0 –

Windows NT 4.0 – 1996(part of the OS or as a suite like Samba) CIFS - 1996 IETF draft –

IETF draft – Common Internet File System – 1997as a suite like Samba) CIFS - 1996 Windows NT 4.0 – 1996 SNIA Technical Specification

SNIA Technical Specification – 1999– 1996 IETF draft – Common Internet File System – 1997 Back to SMB - 2000

Back to SMB - 2000File System – 1997 SNIA Technical Specification – 1999 Windows 2000 Extensions – 2000 Extensions for

Windows 2000 Extensions – 2000SNIA Technical Specification – 1999 Back to SMB - 2000 Extensions for other implementations of SMB

Extensions for other implementations of SMB– 1999 Back to SMB - 2000 Windows 2000 Extensions – 2000 SMB 2.0 (or SMB2)

SMB 2.0 (or SMB2) - 2008 SMB 2.1 (or SMB2.1) - 2010 SMB 3.0 (or SMB3) - 2012
SMB 2.1 (or SMB2.1) - 2010 SMB 2.0 (or SMB2) - 2008 SMB 3.0 (or SMB3) - 2012
SMB 3.0 (or SMB3) - 2012SMB 2.0 (or SMB2) - 2008 SMB 2.1 (or SMB2.1) - 2010

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

6

CIFS as a generic term for SMB

CIFS means SMB as it existed in Windows NT 4CIFS as a generic term for SMB However, the term “CIFS” is commonly used incorrectly to

However, the term “CIFS” is commonly used incorrectly to refer to more recent versions of SMB like SMB2, SMB2.1 or SMB3term for SMB CIFS means SMB as it existed in Windows NT 4 CIFS is sometimes

CIFS is sometimes used as a marketing term to identify specific products, independent of the SMB version implementedto more recent versions of SMB like SMB2, SMB2.1 or SMB3 Using the term “CIFS” to

Using the term “CIFS” to refer to SMB 2.0 or SMB 3.0 is the equivalent toproducts, independent of the SMB version implemented Using POP to refer to IMAP (in e-mail protocols)

Using POP to refer to IMAP (in e-mail protocols)to refer to SMB 2.0 or SMB 3.0 is the equivalent to Using WEP to refer

Using WEP to refer to WPA (in wireless security)to Using POP to refer to IMAP (in e-mail protocols) SMB remote file protocol (including SMB

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

7

Negotiating SMB dialects

SMB 3.0

SMB 2.1

SMB 2.0

SMB 1.0

SMB 3.0 SMB 2.1 SMB 2.0 SMB 1.0

SMB 3.0

SMB 2.1

SMB 2.0

SMB 1.0

SMB 2.1

SMB 2.1

SMB 2.0

SMB 1.0

SMB 2.0

SMB 2.0

SMB 2.0

SMB 1.0

SMB 1.0

SMB 1.0

SMB 1.0

SMB 1.0

Any references to CIFS usually mean SMB 1.0, but could be other versions.

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

8

Protocol negotiation

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights
SMB remote file protocol (including SMB 3.0)
© 2012 Storage Networking Industry Association. All Rights Reserved.

As pictured in the SMB2/SMB3 protocol documentation (see link later in this deck)

9

SMB implementers (alphabetical order)

AppleSMB implementers (alphabetical order) MacOX X 10.2 Jaguar – CIFS/SMB 1 (via Samba) MacOS X 10.7

MacOX X 10.2 Jaguar – CIFS/SMB 1 (via Samba)SMB implementers (alphabetical order) Apple MacOS X 10.7 Lion – SMB 1 (via Apple’s SMBX) EMC

MacOS X 10.7 Lion – SMB 1 (via Apple’s SMBX)order) Apple MacOX X 10.2 Jaguar – CIFS/SMB 1 (via Samba) EMC Older versions – CIFS/SMB

EMC(via Samba) MacOS X 10.7 Lion – SMB 1 (via Apple’s SMBX) Older versions – CIFS/SMB

Older versions – CIFS/SMB 1Samba) MacOS X 10.7 Lion – SMB 1 (via Apple’s SMBX) EMC EMC VNX / EMC

EMC VNX / EMC Isilon – SMB 3 (pre-release)SMB 1 (via Apple’s SMBX) EMC Older versions – CIFS/SMB 1 Microsoft Microsoft LAN Manager –

Microsoft– CIFS/SMB 1 EMC VNX / EMC Isilon – SMB 3 (pre-release) Microsoft LAN Manager –

Microsoft LAN Manager – SMB1 EMC VNX / EMC Isilon – SMB 3 (pre-release) Microsoft Windows NT 4.0 – CIFS

Windows NT 4.0 – CIFSSMB 3 (pre-release) Microsoft Microsoft LAN Manager – SMB Windows 2000 – SMB 1 Windows Server

Windows 2000 – SMB 1Microsoft LAN Manager – SMB Windows NT 4.0 – CIFS Windows Server 2003 or Windows XP

Windows Server 2003 or Windows XP – SMB 1– SMB Windows NT 4.0 – CIFS Windows 2000 – SMB 1 Windows Server 2008 or

Windows Server 2008 or Windows Vista – SMB 22000 – SMB 1 Windows Server 2003 or Windows XP – SMB 1 Windows Server 2008

Windows Server 2008 R2 or Windows 7 – SMB 2.1XP – SMB 1 Windows Server 2008 or Windows Vista – SMB 2 Windows Server 2012

Windows Server 2012 or Windows 8 – SMB 3– SMB 2 Windows Server 2008 R2 or Windows 7 – SMB 2.1 NetApp Older versions

NetApp7 – SMB 2.1 Windows Server 2012 or Windows 8 – SMB 3 Older versions –

Older versions – CIFS/SMB 1SMB 2.1 Windows Server 2012 or Windows 8 – SMB 3 NetApp Data ONTAP 7.3.1 –

Data ONTAP 7.3.1 – SMB 2or Windows 8 – SMB 3 NetApp Older versions – CIFS/SMB 1 Data ONTAP 8.1 –

Data ONTAP 8.1 – SMB 2.1Older versions – CIFS/SMB 1 Data ONTAP 7.3.1 – SMB 2 Data ONTAP 8.2 – SMB

Data ONTAP 8.2 – SMB 3 (pre-release)1 Data ONTAP 7.3.1 – SMB 2 Data ONTAP 8.1 – SMB 2.1 Samba (Linux or

Samba (Linux or others)ONTAP 8.1 – SMB 2.1 Data ONTAP 8.2 – SMB 3 (pre-release) Older versions – CIFS/SMB

Older versions – CIFS/SMB 1ONTAP 8.2 – SMB 3 (pre-release) Samba (Linux or others) Samba 3.6 – SMB 2 (some

Samba 3.6 – SMB 2 (some SMB 2.1)Samba (Linux or others) Older versions – CIFS/SMB 1 Samba 4.0 – SMB 3 (pre-release) And

Samba 4.0 – SMB 3 (pre-release)versions – CIFS/SMB 1 Samba 3.6 – SMB 2 (some SMB 2.1) And many others… Most

And many others…– SMB 2 (some SMB 2.1) Samba 4.0 – SMB 3 (pre-release) Most widely implemented remote

Most widely implemented remote file protocol in the world, available in ~every NAS and File Server2.1) Samba 4.0 – SMB 3 (pre-release) And many others… Information on this slide gathered from

Information on this slide gathered from publicly available information as of October 2012. Please contact the implementers directly to obtain the accurate, up-to-date information on their SMB implementation.

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

10

The basics of SMB

Connecting to a shareThe basics of SMB Negotiating a dialect Executing operations Disconnecting from a share SMB remote file

Negotiating a dialectThe basics of SMB Connecting to a share Executing operations Disconnecting from a share SMB remote

Executing operationsThe basics of SMB Connecting to a share Negotiating a dialect Disconnecting from a share SMB

Disconnecting from a shareto a share Negotiating a dialect Executing operations SMB remote file protocol (including SMB 3.0) ©

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

11

DIR \\FS.EXAMPLE.COM\SHARE1

From

To

Packet

CL

FS

SMB:C NEGOTIATE, Dialect = (Dialect List)

FS

CL

SMB2:R NEGOTIATE (0x0), GUID={8E4F0109-0E04-FD9C-434A-05881428984C}, Mid = 0

CL

FS

SMB2:C SESSION SETUP (0x1), Mid = 1

FS

CL

SMB2:R SESSION SETUP (0x1) ,SessionFlags=0x0, Mid = 1

CL

FS

SMB2:C TREE CONNECT (0x3), Path=\\fs.example.com\IPC$, Mid = 2

FS

CL

SMB2:R TREE CONNECT (0x3), TID=0x1, Mid = 2

CL

FS

DFS:Get DFS Referral Request, FileName: \fs.example.com\share1, MaxReferralLevel: 4

FS

CL

SMB2:R , Mid = 3 - NT Status: System - Error, Code = (412) STATUS_FS_DRIVER_REQUIRED Not a DFS Namespace, just a file share

CL

FS

SMB2:C TREE CONNECT (0x3), Path=\\fs.example.com\share1, Mid = 4

FS

CL

SMB2:R TREE CONNECT (0x3), TID=0x5, Mid = 4

CL

FS

SMB2:C CREATE (0x5), Context=DHnQ, Context=MxAc, Context=QFid, Mid = 5

FS

CL

SMB2:R CREATE (0x5), Context=MxAc, Context=QFid, FID=0xFFFFFFFF00000001, Mid = 5

CL

FS

SMB2:C QUERY INFO (0x10), FID=0xFFFFFFFF00000001, InformationClass=Query FS Volume Info, FID=0xFFFFFFFF00000001, Mid = 6

FS

CL

SMB2:R QUERY INFO (0x10), Mid = 6

CL

FS

SMB2:C CREATE (0x5), Context=DHnQ, Context=MxAc, Context=QFid, Mid = 8

FS

CL

SMB2:R CREATE (0x5), Context=MxAc, Context=QFid, FID=0xFFFFFFFF00000005, Mid = 8

CL

FS

SMB2:C CLOSE (0x6), FID=0xFFFFFFFF00000001, Mid = 11

FS

CL

SMB2:R CLOSE (0x6), Mid = 11

CL

FS

SMB2:C QUERY INFO (0x10), FID=0xFFFFFFFF00000005, InformationClass=Query FS Full Size Info, FID=0xFFFFFFFF00000005, Mid = 12

FS

CL

SMB2:R QUERY INFO (0x10), Mid = 12

CL

FS

SMB2:C TREE DISCONNECT (0x4), TID=0x1, Mid = 13

FS

CL

SMB2:R TREE DISCONNECT (0x4), Mid = 13

CL

FS

SMB2:C TREE DISCONNECT (0x4), TID=0x5, Mid = 14

FS

CL

SMB2:R TREE DISCONNECT (0x4), Mid = 14

CL

FS

SMB2:C LOGOFF (0x2), Mid = 15

FS

CL

SMB2:R LOGOFF (0x2), Mid = 15

Note: CL= SMB Client, FS= SMB File Server

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

12

SMB 1.0

CIFS as in the 1997 IETF draftSMB 1.0 Windows improvements (over time) Kerberos authentication Shadow copy Server to server copy Signing –

Windows improvements (over time)SMB 1.0 CIFS as in the 1997 IETF draft Kerberos authentication Shadow copy Server to server

Kerberos authenticationas in the 1997 IETF draft Windows improvements (over time) Shadow copy Server to server copy

Shadow copyWindows improvements (over time) Kerberos authentication Server to server copy Signing – MD5 Non-Windows

Server to server copyimprovements (over time) Kerberos authentication Shadow copy Signing – MD5 Non-Windows improvements (over time)

Signing – MD5Kerberos authentication Shadow copy Server to server copy Non-Windows improvements (over time) Improvements proposed

Non-Windows improvements (over time)Shadow copy Server to server copy Signing – MD5 Improvements proposed and/or implemented by communities

Improvements proposed and/or implemented by communities using CIFS/SMB on other operating systems including Unix and MacOS. Not part of any official standard.copy Signing – MD5 Non-Windows improvements (over time) SMB remote file protocol (including SMB 3.0) ©

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

13

SMB 2.0

First major redesign of SMBSMB 2.0 Increased file sharing scalability Improved performance Improved request compounding (reduced round trips)

Increased file sharing scalabilitySMB 2.0 First major redesign of SMB Improved performance Improved request compounding (reduced round trips) Asynchronous

Improved performancemajor redesign of SMB Increased file sharing scalability Improved request compounding (reduced round trips)

Improved request compounding (reduced round trips)SMB Increased file sharing scalability Improved performance Asynchronous operations (multiple packets in flight) Larger

Asynchronous operations (multiple packets in flight)Improved request compounding (reduced round trips) Larger reads/writes (more data in each packet)

Larger reads/writes (more data in each packet)trips) Asynchronous operations (multiple packets in flight) Security-related changes Much smaller command set (from 75

Security-related changesin flight) Larger reads/writes (more data in each packet) Much smaller command set (from 75 to

Much smaller command set (from 75 to just 19)(more data in each packet) Security-related changes SMB Durability provide limited network fault tolerance

SMB Durability provide limited network fault tolerancechanges Much smaller command set (from 75 to just 19) Signing – Uses HMAC SHA-256 instead

Signing – Uses HMAC SHA-256 instead of old MD519) SMB Durability provide limited network fault tolerance SMB remote file protocol (including SMB 3.0) ©

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

14

SMB 2.0 reduced command set

Protocol negotiation, user auth and share accessSMB 2.0 reduced command set NEGOTIATE, SESSION_SETUP, LOGOFF, TREE_CONNECT,TREE_DISCONNECT File, directory and volume

command set Protocol negotiation, user auth and share access NEGOTIATE, SESSION_SETUP, LOGOFF,

NEGOTIATE, SESSION_SETUP, LOGOFF, TREE_CONNECT,TREE_DISCONNECT

SESSION_SETUP, LOGOFF, TREE_CONNECT,TREE_DISCONNECT File, directory and volume access CANCEL, CHANGE_NOTIFY,

File, directory and volume accessSESSION_SETUP, LOGOFF, TREE_CONNECT,TREE_DISCONNECT CANCEL, CHANGE_NOTIFY, CLOSE, CREATE, FLUSH, IOCTL, LOCK,

CANCEL, CHANGE_NOTIFY, CLOSE, CREATE, FLUSH, IOCTL, LOCK, QUERY_DIRECTORY, QUERY_INFO, READ, SET_INFO,WRITEFile, directory and volume access Other ECHO, OPLOCK_BREAK SMB remote file protocol (including

LOCK, QUERY_DIRECTORY, QUERY_INFO, READ, SET_INFO,WRITE Other ECHO, OPLOCK_BREAK SMB remote file protocol (including

OtherLOCK, QUERY_DIRECTORY, QUERY_INFO, READ, SET_INFO,WRITE ECHO, OPLOCK_BREAK SMB remote file protocol (including SMB

ECHO, OPLOCK_BREAKQUERY_DIRECTORY, QUERY_INFO, READ, SET_INFO,WRITE Other SMB remote file protocol (including SMB 3.0) © 2012 Storage

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

15

SMB 2.1

File leasing improvementsSMB 2.1 File Leasing replaces Opportunistic Locking (oplocks) Improves performance when frequently updating metadata Uses

File Leasing replaces Opportunistic Locking (oplocks)SMB 2.1 File leasing improvements Improves performance when frequently updating metadata Uses local metadata caching, some

Improves performance when frequently updating metadataFile Leasing replaces Opportunistic Locking (oplocks) Uses local metadata caching, some forms of shared leases

Uses local metadata caching, some forms of shared leasesImproves performance when frequently updating metadata Large MTU support Large message support increases

Large MTU supportUses local metadata caching, some forms of shared leases Large message support increases throughput. Specially

Large message support increases throughput.caching, some forms of shared leases Large MTU support Specially relevant for high bandwidth networks like

Specially relevant for high bandwidth networks like 10GbEMTU support Large message support increases throughput. Peer Content Caching and Retrieval Implemented as

Peer Content Caching and RetrievalSpecially relevant for high bandwidth networks like 10GbE Implemented as BranchCache in Windows Open source

Implemented as BranchCache in Windowsnetworks like 10GbE Peer Content Caching and Retrieval Open source implementation in Prequel from Red Hat

Open source implementation in Prequel from Red HatCaching and Retrieval Implemented as BranchCache in Windows SMB remote file protocol (including SMB 3.0) ©

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

16

SMB 3.0

AvailabilitySMB 3.0 SMB Transparent Failover SMB Witness SMB Multichannel Performance SMB Scale-Out SMB Direct (RDMA) SMB

SMB Transparent FailoverSMB 3.0 Availability SMB Witness SMB Multichannel Performance SMB Scale-Out SMB Direct (RDMA) SMB Multichannel Directory

SMB WitnessSMB 3.0 Availability SMB Transparent Failover SMB Multichannel Performance SMB Scale-Out SMB Direct (RDMA) SMB

SMB MultichannelSMB 3.0 Availability SMB Transparent Failover SMB Witness Performance SMB Scale-Out SMB Direct (RDMA) SMB Multichannel

PerformanceSMB Transparent Failover SMB Witness SMB Multichannel SMB Scale-Out SMB Direct (RDMA) SMB Multichannel Directory

SMB Scale-OutFailover SMB Witness SMB Multichannel Performance SMB Direct (RDMA) SMB Multichannel Directory Leasing

SMB Direct (RDMA)SMB Witness SMB Multichannel Performance SMB Scale-Out SMB Multichannel Directory Leasing BranchCache™V2 Backup

SMB MultichannelSMB Multichannel Performance SMB Scale-Out SMB Direct (RDMA) Directory Leasing BranchCache™V2 Backup VSS for SMB File

Directory LeasingPerformance SMB Scale-Out SMB Direct (RDMA) SMB Multichannel BranchCache™V2 Backup VSS for SMB File Shares Security

BranchCache™V2SMB Direct (RDMA) SMB Multichannel Directory Leasing Backup VSS for SMB File Shares Security SMB Encryption

Backup(RDMA) SMB Multichannel Directory Leasing BranchCache™V2 VSS for SMB File Shares Security SMB Encryption – AES-CCM

VSS for SMB File SharesSMB Multichannel Directory Leasing BranchCache™V2 Backup Security SMB Encryption – AES-CCM Signing - AES-CMAC

SecurityLeasing BranchCache™V2 Backup VSS for SMB File Shares SMB Encryption – AES-CCM Signing - AES-CMAC Management

SMB Encryption – AES-CCMBranchCache™V2 Backup VSS for SMB File Shares Security Signing - AES-CMAC Management PowerShell™ over WS-Man

Signing - AES-CMACVSS for SMB File Shares Security SMB Encryption – AES-CCM Management PowerShell™ over WS-Man SMI-S File

ManagementSecurity SMB Encryption – AES-CCM Signing - AES-CMAC PowerShell™ over WS-Man SMI-S File SMB remote file

PowerShell™ over WS-ManSMB Encryption – AES-CCM Signing - AES-CMAC Management SMI-S File SMB remote file protocol (including SMB

SMI-S FileSigning - AES-CMAC Management PowerShell™ over WS-Man SMB remote file protocol (including SMB 3.0) © 2012

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

17

SMB Transparent Failover

Failover transparent to applicationSMB Transparent Failover SMB Server and SMB client handle failover gracefully Zero downtime – small IO

SMB Server and SMB client handle failover gracefullySMB Transparent Failover Failover transparent to application Zero downtime – small IO delay during failover Supports

Zero downtime – small IO delay during failoverSMB Server and SMB client handle failover gracefully Supports planned and unplanned failovers Hardware or

Supports planned and unplanned failoversgracefully Zero downtime – small IO delay during failover Hardware or Software Maintenance Hardware or Software

Hardware or Software Maintenanceduring failover Supports planned and unplanned failovers Hardware or Software Failures Load Rebalancing Resilient for

Hardware or Software Failuresand unplanned failovers Hardware or Software Maintenance Load Rebalancing Resilient for both file and directory

Load Rebalancingor Software Maintenance Hardware or Software Failures Resilient for both file and directory operations Requires:

Resilient for both file and directory operationsMaintenance Hardware or Software Failures Load Rebalancing Requires: SMB Server in a Failover Cluster SMB Server

Requires:Rebalancing Resilient for both file and directory operations SMB Server in a Failover Cluster SMB Server

SMB Server in a Failover ClusterResilient for both file and directory operations Requires: SMB Server and SMB client must implement SMB

SMB Server and SMB client must implement SMB 3.0operations Requires: SMB Server in a Failover Cluster Shares enabled for ‘Continuous Availability’ Impact to

Shares enabled for ‘Continuous Availability’Cluster SMB Server and SMB client must implement SMB 3.0 Impact to SMB before 3.0 Older

Impact to SMB before 3.0SMB 3.0 Shares enabled for ‘Continuous Availability’ Older clients can connect, but without the Transparent

Older clients can connect, but without the Transparent Failover capabilityfor ‘Continuous Availability’ Impact to SMB before 3.0 1 2 3 Normal operation Failover share -

1
1
2 3
2
3

Normal operation

Failover share - connections and handles lost, temporary stall of IO

Connections and handles auto-recovered Application IO continues with no errors

Server Application 1 3 \\fs1\share \\fs1\share 2 File Server Cluster File Server File Server Node
Server Application
1
3
\\fs1\share
\\fs1\share
2
File Server Cluster
File Server
File Server
Node A
Node B

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

SMB Scale-Out

Targeted for server app storageSMB Scale-Out Example:Virtualization and Databases Increase available bandwidth by adding cluster nodes Key capabilities:

Example:Virtualization and DatabasesSMB Scale-Out Targeted for server app storage Increase available bandwidth by adding cluster nodes Key capabilities:

Increase available bandwidth by adding cluster nodesfor server app storage Example:Virtualization and Databases Key capabilities: Active/Active file shares Fault tolerance

Key capabilities:Increase available bandwidth by adding cluster nodes Active/Active file shares Fault tolerance with zero downtime

Active/Active file sharesbandwidth by adding cluster nodes Key capabilities: Fault tolerance with zero downtime Fast failure recovery

Fault tolerance with zero downtimecluster nodes Key capabilities: Active/Active file shares Fast failure recovery Impact to SMB before 3.0 SMB

Fast failure recoveryActive/Active file shares Fault tolerance with zero downtime Impact to SMB before 3.0 SMB 2.x clients

Impact to SMB before 3.0Fault tolerance with zero downtime Fast failure recovery SMB 2.x clients can connect, but without the

SMB 2.x clients can connect, but without the failover capabilityzero downtime Fast failure recovery Impact to SMB before 3.0 SMB1 clients not supported Application Cluster

SMB1 clients not supported2.x clients can connect, but without the failover capability Application Cluster Data Center Network Single Logical

Application Cluster

capability SMB1 clients not supported Application Cluster Data Center Network Single Logical File Server (\\FS\Share)
Data Center Network
Data Center Network
Single Logical File Server (\\FS\Share) Single File System Namespace Cluster File System
Single Logical File Server (\\FS\Share)
Single File System Namespace
Cluster File System

File Server Cluster

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

SMB Direct (SMB over RDMA)

AdvantagesSMB Direct (SMB over RDMA) Scalable, fast and efficient storage access High throughput with low latency

Scalable, fast and efficient storage accessSMB Direct (SMB over RDMA) Advantages High throughput with low latency Minimal CPU utilization for I/O

High throughput with low latencyRDMA) Advantages Scalable, fast and efficient storage access Minimal CPU utilization for I/O processing Load balancing,

Minimal CPU utilization for I/O processingefficient storage access High throughput with low latency Load balancing, automatic failover and bandwidth aggregation

Load balancing, automatic failover and bandwidth aggregation via SMB Multichannelwith low latency Minimal CPU utilization for I/O processing Scenario High performance remote file access for

Scenariofailover and bandwidth aggregation via SMB Multichannel High performance remote file access for application servers

High performance remote file access for application servers like Virtualization and Databasesand bandwidth aggregation via SMB Multichannel Scenario Required hardware RDMA-capable network interface (R-NIC)

Required hardwarefor application servers like Virtualization and Databases RDMA-capable network interface (R-NIC) Three types: iWARP,

RDMA-capable network interface (R-NIC)servers like Virtualization and Databases Required hardware Three types: iWARP, RoCE and Infiniband Impact to SMB

Three types: iWARP, RoCE and InfinibandRequired hardware RDMA-capable network interface (R-NIC) Impact to SMB before 3.0 Older clients can connect, but

Impact to SMB before 3.0interface (R-NIC) Three types: iWARP, RoCE and Infiniband Older clients can connect, but without the RDMA

Older clients can connect, but without the RDMA capabilitytypes: iWARP, RoCE and Infiniband Impact to SMB before 3.0 SMB Client SMB Server Application User

SMB Client SMB Server Application User Kernel SMB Client SMB Server Local Network w/ Network
SMB Client
SMB Server
Application
User
Kernel
SMB Client
SMB Server
Local
Network w/
Network w/
File
RDMA
RDMA
Sy
support
support
ste
m
Disk

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

SMB Multichannel

Full Throughput t

Bandwidth aggregation with multiple NICsSMB Multichannel Full Throughpu t Multiple CPUs cores engaged when NIC offers Receive Side Scaling (RSS)

Multiple CPUs cores engaged when NIC offers Receive Side Scaling (RSS)Full Throughpu t Bandwidth aggregation with multiple NICs Automatic Failover SMB Multichannel implements end-to- end

Automatic Failovercores engaged when NIC offers Receive Side Scaling (RSS) SMB Multichannel implements end-to- end failure detection

SMB Multichannel implements end-to- end failure detectionNIC offers Receive Side Scaling (RSS) Automatic Failover Leverages NIC teaming if present, but does not

Leverages NIC teaming if present, but does not require itSMB Multichannel implements end-to- end failure detection Automatic Configuration SMB detects and uses multiple paths

Automatic ConfigurationLeverages NIC teaming if present, but does not require it SMB detects and uses multiple paths

SMB detects and uses multiple pathsif present, but does not require it Automatic Configuration Impact to SMB before 3.0 Older clients

Impact to SMB before 3.0Automatic Configuration SMB detects and uses multiple paths Older clients can connect, but without the Multichannel

Older clients can connect, but without the Multichannel capabilitySMB detects and uses multiple paths Impact to SMB before 3.0 Single 10GbE RSS-capable NIC SMB

Single 10GbE RSS-capable NIC SMB Client NIC 10GbE Switch 10GbE NIC 10GbE SMB Server
Single 10GbE
RSS-capable
NIC
SMB Client
NIC
10GbE
Switch
10GbE
NIC
10GbE
SMB Server

Sample Configurations

Multiple 1GbE NICs SMB Client NIC NIC 1GbE 1GbE Switch Switch 1GbE 1GbE NIC NIC
Multiple 1GbE NICs
SMB Client
NIC
NIC
1GbE
1GbE
Switch
Switch
1GbE
1GbE
NIC
NIC
1GbE
1GbE
SMB Server
Multiple 10GbE in NIC team SMB Client NIC Team NIC NIC 10GbE 10GbE Switch Switch
Multiple 10GbE
in NIC team
SMB Client
NIC Team
NIC
NIC
10GbE
10GbE
Switch
Switch
10GbE
10GbE
NIC
NIC
10GbE
10GbE
NIC Team
SMB Server
Multiple RDMA NICs SMB Client NIC NIC 10GbE/IB 10GbE/IB Switch Switch 10GbE/IB 10GbE/IB NIC NIC
Multiple RDMA NICs
SMB Client
NIC
NIC
10GbE/IB
10GbE/IB
Switch
Switch
10GbE/IB
10GbE/IB
NIC
NIC
10GbE/IB
10GbE/IB
SMB Server
10GbE/IB 10GbE/IB NIC NIC 10GbE/IB 10GbE/IB SMB Server SMB remote file protocol (including SMB 3.0) ©

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

SMB Directory Leasing

Reduces roundtrips from client to serverSMB Directory Leasing Metadata is retrieved from longer lived directory cache Directory cache coherency is maintained

Metadata is retrieved from longer lived directory cacheDirectory Leasing Reduces roundtrips from client to server Directory cache coherency is maintained due to the

Directory cache coherency is maintained due to the implementation of directory leasesMetadata is retrieved from longer lived directory cache Client gets notified if directory information on server

Client gets notified if directory information on server changesis maintained due to the implementation of directory leases Targeted at HomeFolder (read/write with no sharing)

Targeted atgets notified if directory information on server changes HomeFolder (read/write with no sharing) scenarios

HomeFolder (read/write with no sharing) scenariosif directory information on server changes Targeted at Publication (read-only with sharing) scenarios Metadata

Publication (read-only with sharing) scenariosat HomeFolder (read/write with no sharing) scenarios Metadata cache Directory handles Directory metadata Impact

Metadata cachescenarios Publication (read-only with sharing) scenarios Directory handles Directory metadata Impact to SMB before

Directory handles(read-only with sharing) scenarios Metadata cache Directory metadata Impact to SMB before 3.0 Older clients

Directory metadatawith sharing) scenarios Metadata cache Directory handles Impact to SMB before 3.0 Older clients connect, but

Impact to SMB before 3.0Metadata cache Directory handles Directory metadata Older clients connect, but without the Directory Leasing

Older clients connect, but without the Directory Leasing capabilityhandles Directory metadata Impact to SMB before 3.0 {K 1 ,0} \users {K {K 11 ,K

{K 1 ,0} \users {K {K 11 ,K 1 } 12 ,K 1 } \users\bob
{K 1 ,0}
\users
{K
{K
11 ,K 1 }
12 ,K
1 }
\users\bob
\users\alex
{K 111 ,K 11 }
{K 112 ,K 11 }
\users\bob\b.tx
\users\bob\a.txt
t

Lease breaks when directory metadata is updated11 } {K 112 ,K 11 } \users\bob\b.tx \users\bob\a.txt t Creation of new children Rename of

Creation of new childrent Lease breaks when directory metadata is updated Rename of immediate child file/directory

Rename of immediate child file/directorywhen directory metadata is updated Creation of new children Deletion/Modification of immediate children (manifests when

Deletion/Modification of immediate children (manifests when handle is closed)of new children Rename of immediate child file/directory Lease breaks when directory handle itself gets a

Lease breaks when directory handle itself gets a sharing conflictof immediate children (manifests when handle is closed) Another conflicting open to directory Rename/deletion of a

Another conflicting open to directorybreaks when directory handle itself gets a sharing conflict Rename/deletion of a parent directory SMB remote

Rename/deletion of a parent directorya sharing conflict Another conflicting open to directory SMB remote file protocol (including SMB 3.0) ©

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

23

SMB Encryption

End-to-end encryption of data in flightSMB Encryption Protects data from eavesdropping/snooping attacks on untrusted networks Configured per share or for the

Protects data from eavesdropping/snooping attacks on untrusted networksSMB Encryption End-to-end encryption of data in flight Configured per share or for the entire server

Configured per share or for the entire serverfrom eavesdropping/snooping attacks on untrusted networks Used in scenarios where data traverses untrusted networks

Used in scenarios where data traverses untrusted networksnetworks Configured per share or for the entire server Application workload over unsecured networks Branch Offices

Application workload over unsecured networksUsed in scenarios where data traverses untrusted networks Branch Offices over WAN networks Low deployment costs

Branch Offices over WAN networksnetworks Application workload over unsecured networks Low deployment costs No IPSec required No Public Key

Low deployment costsover unsecured networks Branch Offices over WAN networks No IPSec required No Public Key Infrastructure (PKI)

No IPSec requiredBranch Offices over WAN networks Low deployment costs No Public Key Infrastructure (PKI) required No specialized

No Public Key Infrastructure (PKI) requiredover WAN networks Low deployment costs No IPSec required No specialized hardware required Impact to SMB

No specialized hardware requiredIPSec required No Public Key Infrastructure (PKI) required Impact to SMB versions before 3.0 If encryption

Impact to SMB versions before 3.0(PKI) required No specialized hardware required If encryption is turned on, older clients get “Access

If encryption is turned on, older clients get “Access Denied” errorshardware required Impact to SMB versions before 3.0 Client Server SMB Encryption Algorithm AES CCM 128

Client Server SMB Encryption
Client
Server
SMB Encryption
“Access Denied” errors Client Server SMB Encryption Algorithm AES CCM 128 bit No algorithm negotiation

Algorithm

AES CCM 128 bitDenied” errors Client Server SMB Encryption Algorithm No algorithm negotiation capability Will sign AND encrypt in

No algorithm negotiation capabilityClient Server SMB Encryption Algorithm AES CCM 128 bit Will sign AND encrypt in the same

Will sign AND encrypt in the same step (independent of SMB Signing setting)AES CCM 128 bit No algorithm negotiation capability AES acceleration provided by most new processors aids

AES acceleration provided by most new processors aids in performancein the same step (independent of SMB Signing setting) Some CPUs that provide AES hardware acceleration.

Some CPUs that provide AES hardware acceleration.provided by most new processors aids in performance SMB remote file protocol (including SMB 3.0) ©

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

VSS for SMB File Shares

Supports backup and restore scenarios for application servers like Virtualization and DatabasesVSS for SMB File Shares Application consistent shadow copies for server application data stored on SMB

Application consistent shadow copies for server application data stored on SMB 3.0 file sharesfor application servers like Virtualization and Databases Full integration with Microsoft’s Volume Shadowcopy

Full integration with Microsoft’s Volume Shadowcopy Services (VSS) infrastructurefor server application data stored on SMB 3.0 file shares Implemented by at least one vendor

Implemented by at least one vendor besides MicrosoftVolume Shadowcopy Services (VSS) infrastructure Backup Server G Read from Shadow Copy Backup Share A

Backup Server

by at least one vendor besides Microsoft Backup Server G Read from Shadow Copy Backup Share
G
G
Read from Shadow Copy Backup Share A File Share Shadow Copy Agent E Request Shadow
Read from
Shadow Copy
Backup
Share
A
File Share Shadow Copy Agent
E Request Shadow Copy
Backup Agent
Volume Shadow Copy Service
B Coordinate Shadow Copy
F
Create Shadow Copy
Volume Shadow Copy Service
Create Shadow Copy
C
VSS Providers
D
File Share Shadow Copy Provider
Relay
\\fs\foo
\\fs\foo@t1
Shadow
Data volume
Shadow Copy

Application Server

Copy

request

File Server

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

SMB Management

WMI objects introduced (accessible via WS-Management)SMB Management Manages SMB shares, file server sessions and settings, client connections and settings Aimed at

Manages SMB shares, file server sessions and settings, client connections and settingsWMI objects introduced (accessible via WS-Management) Aimed at both System Administrator and Developers Covers

Aimed at both System Administrator and Developerssessions and settings, client connections and settings Covers both standalone and clustered file server and shares

Covers both standalone and clustered file server and sharessettings Aimed at both System Administrator and Developers Main objects and associated methods SMB Share: Get,

Main objects and associated methodsCovers both standalone and clustered file server and shares SMB Share: Get, New, Set and Remove

SMB Share: Get, New, Set and Removefile server and shares Main objects and associated methods SMB Share Access: Get, Grant, Revoke, Block

SMB Share Access: Get, Grant, Revoke, Block and Unblockand associated methods SMB Share: Get, New, Set and Remove SMB Session: Get and Close SMB

SMB Session: Get and CloseSMB Share Access: Get, Grant, Revoke, Block and Unblock SMB Open File: Get and Close SMB

SMB Open File: Get and CloseGrant, Revoke, Block and Unblock SMB Session: Get and Close SMB Configuration: Get and Set for

SMB Configuration: Get and Set for Server and ClientSMB Session: Get and Close SMB Open File: Get and Close SMB Network Interfaces: Get for

SMB Network Interfaces: Get for Server and ClientClose SMB Configuration: Get and Set for Server and Client SMB Connection: Get for Connection, Get

SMB Connection: Get for Connection, Get for Multichannel Connectionand Client SMB Network Interfaces: Get for Server and Client SMB Mappings: Get, New and Remove

SMB Mappings: Get, New and RemoveGet for Connection, Get for Multichannel Connection SMB Multichannel Constraints: Get, New and Remove SMI-S File

SMB Multichannel Constraints: Get, New and RemoveMultichannel Connection SMB Mappings: Get, New and Remove SMI-S File Main WMI objects mapped to SMI-File

SMI-S Fileand Remove SMB Multichannel Constraints: Get, New and Remove Main WMI objects mapped to SMI-File object

Main WMI objects mapped to SMI-File object modelSMB Multichannel Constraints: Get, New and Remove SMI-S File Initial support by Microsoft, NetApp and EMC

Initial support by Microsoft, NetApp and EMCSMI-S File Main WMI objects mapped to SMI-File object model SMB remote file protocol (including SMB

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

WMI = Windows Management Instrumentation, implementation of DMTF standards (WBEM, CIM) on the Windows Platform.
WMI = Windows
Management
Instrumentation,
implementation of
DMTF standards
(WBEM, CIM) on the
Windows Platform.
WS-Management = Web
Services Management.
DMTF open standard
for SOAP-based
protocol for server
management.
SMI-S = Storage
Management Initiative
– Specification. SNIA
Storage Management
Standard.

26

Links to protocol documentation

Specification

Description

[MS-CIFS]: Common Internet File System (CIFS) Protocol Specification

Specifies the Common Internet File System (CIFS) Protocol, a cross-platform, transport- independent protocol that provides a mechanism for client systems to use file and print services made available by server systems over a network.

[MS-SMB]: Server Message Block (SMB) Protocol Specification

Specifies the Server Message Block (SMB) Protocol, which defines extensions to the existing Common Internet File System (CIFS) specification that have been implemented by Microsoft since the publication of the [CIFS] specification.

[MS-SMB2]: Server Message Block (SMB) Protocol Versions 2 and 3 Specification

Specifies the Server Message Block (SMB) Protocol Versions 2 and 3, which support the sharing of file and print resources between machines and extend the concepts from the Server Message Block Protocol.

[MS-SMBD]: SMB Remote Direct Memory Access (RDMA) Transport Protocol Specification

Specifies the SMB Remote Direct Memory Access (RDMA) Transport Protocol, a wrapper for the existing SMB protocol that allows SMB packets to be delivered over RDMA-capable transports such as iWARP or Infiniband while utilizing the direct data placement (DDP) capabilities of these transports. Benefits include reduced CPU overhead, lower latency, and improved throughput.

[MS-SWN]: Service Witness Protocol Specification

Specifies the Service Witness Protocol, which enables an SMB clustered file server to notify SMB clients with prompt and explicit notifications about the failure or recovery of a network name and associated services.

[MS-FSRVP]: File Server Remote VSS Provider Protocol Specification

Specifies the File Server Remote VSS Protocol, an RPC-based protocol used for creating shadow copies of file shares on a remote computer, and for facilitating backup applications in performing application-consistent backup and restore of data on SMB shares.

Note: Protocols published by Microsoft, but available to anyone to implement in non-Windows platforms.

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

27

Plugfest

SMB/SMV2/SMB3Plugfest PlugFest happens every year side-by-side with the Storage Developer Conference (SNIA SDC) in September Intense

PlugFest happens every year side-by-side with the Storage Developer Conference (SNIA SDC) in September Intense week of interaction across operating systems and SMB implementations.Plugfest SMB/SMV2/SMB3 Participants of the 2012 edition of the SNIA SMB/SMB2/SMB3 Plugfest. Santa Clara, CA –

across operating systems and SMB implementations. Participants of the 2012 edition of the SNIA SMB/SMB2/SMB3

Participants of the 2012 edition of the SNIA SMB/SMB2/SMB3 Plugfest. Santa Clara, CA – September 2012

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

28

Review

Review Objectives Understand the basic architecture of the SMB protocol family Enumerate the main capabilities introduced

Objectives

Understand the basic architecture of the SMB protocol familyReview Objectives Enumerate the main capabilities introduced with SMB 2.0 Describe the main capabilities introduced with

Enumerate the main capabilities introduced with SMB 2.0Understand the basic architecture of the SMB protocol family Describe the main capabilities introduced with SMB

Describe the main capabilities introduced with SMB 3.0Enumerate the main capabilities introduced with SMB 2.0 SMB remote file protocol (including SMB 3.0) ©

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

29

Attribution & Feedback

The SNIA Education Committee would like to thank the following individuals for their contributions to this Tutorial.

Authorship History

Jose Barreto / September 2012

Updates:

Jose Barreto / October 2012

Additional Contributors

SW Worth Christopher Hertel

Please send any questions or comments regarding this SNIA Tutorial to tracktutorials@snia.org

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

3030

Thank you!

SMB remote file protocol (including SMB 3.0) © 2012 Storage Networking Industry Association. All Rights Reserved.

31