m11 San Final

7/29/2019 m11 San Final

1/40

SAN

Module 11

Data ONTAP 7.3 Fundamentals

7/29/2019 m11 San Final

2/40

2008 NetApp. All rights reserved. 2

Module Objectives

By the end of this module, you should be able to:

Explain the purpose of a SAN

Identify supported SAN configurations

Distinguish between FC and iSCSI protocols

Define a LUN and explain LUN attributes

Use the lun setup command and FilerView

to create iSCSI LUNs

Access and manage a LUN from a Windowshost

Define SnapDrive and its features

7/29/2019 m11 San Final

3/40


SAN Overview

7/29/2019 m11 San Final

4/40


What is a SAN?

Storage Area Network (SAN)

NAS(Files)

SAN(Blocks)

EthernetFC

iSCSI

NetApp FAS

Corporate

LAN

7/29/2019 m11 San Final

5/40


SAN Protocols

TCP/IP NetworkFibre ChannelNetwork

WAFL Architecture

Block Services

Network InterfacesFC Ethernet

Encapsulated SCSI Encapsulated SCSI

SAN Protocols

FCP iSCSI

7/29/2019 m11 San Final

6/40


SAN Components

7/29/2019 m11 San Final

7/40 2008 NetApp. All rights reserved. 7

SAN Components

Hosts

Supported platforms are Windows, Solaris,

AIX,HP-UX, Linux, NetWare, VMware

Referred to as initiators

Connectivity Direct-attach

NetworkNetwork can be fabric (FCP) or IP

(iSCSI)

Storage system

Allocates blocks to an initiator group (igroup)

Referred to as targets

7/29/2019 m11 San Final


FC Components

Host bus adapter (HBA)

Storage systems and hosts have HBAs withone or more ports.

The HBA is identified by a Worldwide Node

Name (WWNN). Each port on the HBA is identified by a

Worldwide Port Name (WWPN), which is usedto create igroups.

HBA WWNN20:00:00:2b:34:26:a6:54

HBA WWPN21:00:00:2b:34:26:a6:54

22:00:00:2b:34:26:a6:54

7/29/2019 m11 San Final


iSCSI Components

A host is configured with one of the following:

Software initiators with a standard NIC

TCP Offload Engine (TOE) with a softwareinitiator

iSCSI HBA

A host initiator is identified by a WWNN, suchas the following:

iqn.1998-02.com.netapp:sn12345678

eui.1234567812345678 A storage system is configured with either:

iSCSI HBA

Standard NIC

7/29/2019 m11 San Final


Initiator/Target Relationship

Host (Initiator) Controller (Target)

Direct-Attached Storage

Fabric/Network

SCSI over FC

SCSI over TCP/IP

(iSCSI)

FC

Driver

SCSI

Driver

File

System

Application

SCSI Adapters

Windows or UNIXFC HBAs

Data ONTAP

LUN

Ethernet NICs

SCSI over TCP/IP

(iSCSI)

iSCSI HBAs

Storage System

FC or SATA

Attached

TCP

/IP

iSCSI

Driver

iSCSI

Driver

TCP

/IP

SAN ServicesFC

Driver

WAFL

RAID

7/29/2019 m11 San Final


LUN Overview

A LUN (Logical Unit Number) is:

A logical representation of storage

Configured as a single disk

Appears as a local disk on the host

Centrally stored, but managed by a host at the

block level

7/29/2019 m11 San Final


Setting Up a SAN

7/29/2019 m11 San Final


Setting Up a SAN

To set up a SAN:

1. License the appropriate SAN protocol on the

storage system.

2. Create a volume or qtree where the LUN will

reside (apply quotas when appropriate).3. Verify the SAN protocol driver is on.

4. Configure the host initiator.

5. Create the LUN and igroup, and thenassociate the igroup to the LUN.

7/29/2019 m11 San Final


Review Questions

How do you license the appropriate SANprotocol on the storage system?

Use the license add command from astorage system

Use FilerView from a host

How do you create a volume or qtree for aLUN?

Use the vol create command from a storagesystem

Use the qtree create command from astorage system

Use FilerView from a host

7/29/2019 m11 San Final


Managing FCP or iSCSI

After licensing, the FCP or iSCSI drivers can

be activated

To manage the FCP or iSCSI protocols:

Using the CLI

FCPfcp [subcommand]

Example: fcp status

iSCSI

iscsi [subcommand]

Examples: iscsi start oriscsi status

Using FilerView

7/29/2019 m11 San Final


Configuring the Initiator

Only the initiator(s) identified in the LUN igroup

can access the LUN through the protocol

specified (FCP or iSCSI)

There are different methods for setting up the

initiator depending on: Host operating system

SAN protocol used (FCP or iSCSI)

Method of connection (HBA or software initiator)

7/29/2019 m11 San Final


iSCSI Software Initiator

7/29/2019 m11 San Final


iSCSI Software Initiator (Cont.)

7/29/2019 m11 San Final


Creating LUNs

Create LUNs using one of the following methods:

The CLI:

lun create

lun setup

FilerView

SnapDrive (covered later in this module)

7/29/2019 m11 San Final


The lun setup Command

system> lun setup

This setup will take you through the steps needed to create LUNsand to make them accessible by initiators. You can type ^C (Control-C)

at any time to abort the setup and no unconfirmed changes will be made

to the system.

Do you want to create a LUN? [y]: y

Multiprotocol type of LUN (image/solaris/windows/hpux/aix/linux) [image]: windows

A LUN path must be absolute. A LUN can only reside in a volume or

qtree root. For example, to create a LUN with name "lun0" in the

qtree root /vol/vol1/q0, specify the path as "/vol/vol1/q0/lun0".

Enter LUN path: /vol/winvol/tree1/lun0

A LUN can be created with or without space reservations being enabled.Space reservation guarantees that data writes to that LUN will never

fail.

Do you want the LUN to be space reserved? [y]: y

Size for a LUN is specified in bytes. You can use single-character

multiplier suffixes: b(sectors), k(KB), m(MB), g(GB) or t(TB).

Enter LUN size: 12g

You can add a comment string to describe the contents of the LUN.

Please type a string (without quotes), or hit ENTER if you don't

want to supply a comment.

Enter comment string: Windows LUN

7/29/2019 m11 San Final

22/40


The lun setup Command (Cont.)

The LUN will be accessible to an initiator group. You can use an

existing group name, or supply a new name to create a new initiatorgroup. Enter '?' to see existing initiator group names.

Name of initiator group: ?

Existing initiator groups:

Name of initiator group: salesigroup

Type of initiator group salesigroup (FCP/iSCSI) [FCP]: iscsi

An iSCSI initiator group is a collection of initiator node names.Each

node name can begin with either 'eui.' or 'iqn.' and should be in the

following formats: eui.{EUI-64 address} or iqn.yyyy-mm.{reversed domain

name}:{any string}

Eg: iqn.2001-04.com.acme:storage.tape.sys1.xyz or eui.02004567A425678DYou can separate node names by commas. Enter '?' to display a list of

connected initiators. Hit ENTER when you are done adding node names to

this group.

Enter comma separated nodenames: ?

Initiators connected on adapter iswta:

iSCSI Initiator Name Group

iqn.1991-05.com.microsoft:slu2-win.edsvcs.netapp.com

Adapter iswtb is running on behalf of the partner.Enter comma separated nodenames: iqn.1991-05.com.microsoft:slu2-win.edsvcs.netapp.com

Enter comma separated nodenames:

7/29/2019 m11 San Final

23/40


The lun setup Command (Cont.)

The initiator group has an associated OS type. The following are

currently supported: solaris, windows, hpux, aix, linux or default.OS type of initiator group "salesigroup" [windows]: windows

The LUN will be accessible to all the initiators in the

initiator group. Enter '?' to display LUNs already in use

by one or more initiators in group "salesigroup".

LUN ID at which initiator group "salesigroup" sees "/vol/winvol/tree1/lun0"[0]: 0

LUN Path : /vol/winvol/tree1/lun0

OS Type : windows

Size : 12.0g (12889013760)

Comment : Windows LUNInitiator Group : salesigroup

Initiator Group Type : iSCSI

Initiator Group Members : iqn.1991-05.com.microsoft:slu2-win.edsvcs.netapp.com

Mapped to LUN-ID : 0

Do you want to accept this configuration? [y]: y

Do you want to create another LUN? [n]: n

NetApp1> lun show -m

LUN path Mapped to LUN ID

-------------------------------------------------------------

/vol/winvol/tree1/lun0 salesigroup 0system>

7/29/2019 m11 San Final

24/40


Creating a LUN Using FilerView

7/29/2019 m11 San Final

25/40


Accessing a LUN

7/29/2019 m11 San Final

26/40


Accessing a LUN

7/29/2019 m11 San Final

27/40


Accessing a LUN (Cont.)

7/29/2019 m11 San Final

28/40



7/29/2019 m11 San Final

29/40



7/29/2019 m11 San Final

30/40



7/29/2019 m11 San Final

31/40



7/29/2019 m11 San Final

32/40


SnapDrive

7/29/2019 m11 San Final

33/40


SnapDrive

SnapDrive ensures consistent LUN Snapshots

and is available:

From NetApp to manage a LUN from a host

For the Windows, Solaris, Linux, AIX, and HP-

UX platforms SnapDrive can create an iSCSI LUN on the

storage system and automatically attach it to

the client host

NOTE: If SnapDrive is used to create a LUN, you must use

SnapDrive to manage that LUN. Do not use the CLI to delete,

rename, or otherwise manage a LUN created by SnapDrive.

7/29/2019 m11 San Final

34/40


SnapDrive for Windows

7/29/2019 m11 San Final

35/40


Other SAN Administration Resources

For more information about SAN administration, see the

SAN Administration on Data ONTAP 7.3 course.This advanced course covers:

Creating FCP and iSCSI LUNs from the CLI

Creating FCP and iSCSI LUNs from SnapDrive withWindows

Creating FCP and iSCSI LUNs from SnapDrive withSolaris

Configuring Solaris hosts for FCP and iSCSI

Configuring Windows hosts for FCP and iSCSI

Configuring other hosts, such as Linux, HP-UX, andAIX

SAN in a clustered storage system environment

SAN performance tuning

SAN troubleshooting

7/29/2019 m11 San Final

36/40


Module Summary

In this module, you should have learned to:

A SAN is a Storage Area Network

A LUN is a Logical Unit Number

The lun setup command and FilerView are

common ways to create LUNs

iSCSI is a simple but effective protocol to

connect to a LUN

To access a LUN from a Windows host, useDisk Management

SnapDrive creates a LUN and connects to that

LUN quickly and securely

7/29/2019 m11 San Final

37/40

Exercise

Module 11: SAN

Estimated Time: 45 minutes

7/29/2019 m11 San Final

38/40

Answers

Module 11: SAN

7/29/2019 m11 San Final

39/40


Check Your Understanding

What are the two protocols NetApp supports in

the SAN environment?

FCP

iSCSI

What are the functions of a LUN? Logical representation of storage

Configured as a single disk

Appear as local disks on the host Managed at the block level

7/29/2019 m11 San Final

40/40

Check Your Understanding (Cont.)

What are the methods of creating a LUN?

Using the lun create command from astorage system

Using the lun setup command from a storagesystem

Using FilerView from a host

Using SnapDrive from a host

Why would you use SnapDrive in a SANenvironment?

It is integrated with Microsoft ManagementConsole

It ensures a consistent LUN Snapshot

m11 San Final

Documents