M10-SAN Storage Area Network

SAN

Module 10

Data ONTAP 8.0 7-Mode Administration

© 2009 NetApp. All rights reserved.

Module Objectives

By the end of this module, you should be able to:Explain the purpose of a SANIdentify supported SAN configurationsDistinguish between FC and iSCSI protocolsDefine a LUN and explain LUN attributesUse the lun setup command and NetApp®

System Manager to create iSCSI-attached LUNs

Access and manage a LUN from a Windows® host

Define SnapDrive® and its features


SAN Overview


Unified Storage

SANNAS

NetApp FAS

NFS

CIFSCorporateLAN

iSCSI

FCoEFC


SAN Protocols

TCP/IP Network

WAFL® Architecture

Block Services

Network InterfacesFC Ethernet

Encapsulated SCSI Encapsulated SCSI

SAN ProtocolsFC iSCSI FCoE

Fibre Channel Network


SAN Components


Initiator and Target

Host

SCSI Driver

File System

Application

WAFLSAN Services

LUN

Target

Initiator

Controller


SAN Types

A SAN may be implemented using either:– Fibre Channel (FC)

Referred to as FC SAN Uses Fibre Channel Protocol (FCP) to communicate

Uses Fibre Channel over Ethernet (FCoE) to communicate

– Internet Protocol (IP) Uses Internet SCSI (iSCSI) to communicate

Ethernet IP TCP iSCSI SCSI

Ethernet FCoE FC Frame SCSI

Physical Data FC Frame SCSI


Ports

Target

Initiator

SCSI Driver

File System

Application

WAFLSAN Services

Ethernet Port Fibre Channel Port orConverged Network Adapter (CNA)

FC driveriSCSI driverTCP/IP driver

FC driveriSCSI driverTCP/IP driver

LUN


Node and Port Names in Fibre Channel

SCSI Driver

File System

Application

20:00:00:2b:34:26:a6:56

50:0a:09:80:86:f7:c7:86

21:00:00:2b:34:26:a6:56

50:0a:09:81:86:f7:c7:86

Worldwide Node Name (WWNN) Worldwide Port Name (WWPN)

WAFLSAN Services

LUN FC SAN

IPSAN

Target

Initiator


Node and Portals in iSCSI

SCSI Driver

File System

Application

Local Network Connection

Target Portal Group (TPG)

iqn.1999-04.com.a:system

iqn.1998-02.com.netapp:ss1

Portals Worldwide Node (WWN)

WAFLSAN Services

LUN FC SAN

IPSAN

Target

Initiator


Connectivity Between Initiator and Target

SCSI Driver

File System

Application

WAFLSAN Services

LUN FC SAN

Directly Connected

Connected via a Switch

IPSAN

Target

Initiator


Set up a SAN


Set 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 then associate the igroup to the LUN.


Review Questions

How do you license the appropriate SAN protocol on the storage system?– Use the license add command from a

storage system– Use NetApp System Manager from a host

How do you create a volume or qtree for a LUN?– Use the vol create command from a storage

system– Use the qtree create command from a

storage system– Use NetApp System Manager from a host


Managing FCP or iSCSI

After licensing, the FCP or iSCSI service can be activated

To manage the FCP or iSCSI protocols:– Using the CLI

FCPfcp [subcommand]Example: fcp start or fcp status

iSCSIiscsi [subcommand]Examples: iscsi start or iscsi status


System Manager: iSCSI Setup

The iSCSI license

Notice the newcategories

To configure licenses


System Manager: iSCSI Setup

To configure iSCSI

Storage system’sWWN


Configuring the Initiator

Only the initiator(s) identified in the LUN igroup can access the LUN through the protocol specified

There are different methods for setting up the initiator depending on:– Host operating system– SAN protocol used– Method of connection (HBA or software initiator)

NOTE: This is a simple configuration example, please see the SAN Administration course for more details


iSCSI Software Initiator

Windows Server 2003 example showed


iSCSI Software Initiator (Cont.)

To persist the connectionacross reboots


iSCSI Software Initiator (Cont.)

The target’s node namewill appear if persisted


Creating LUNs

Create LUNs using one of the following methods:– The CLI:

lun createlun setup

– NetApp System Manger– SnapDrive– Provisioning Manager

This course focuses on lun setup and NetApp System Manager methods


lun setup Command

LUN creation, optionally igroup creation, and igroup and LUN mapping may be accomplished with a single command:– lun setup

A wizard-like command that prompts the user for relevant information

The result of the command is a newly created LUN mapped to a new or existing igroup


Creating a LUN with lun setup

system> lun setupThis setup will take you through the steps needed to create LUNs and 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 (solaris/windows/hpux/aix/linux/netware/vmware/windows_gpt/windows_2008/xen/hyper_v/solaris_efi/vld/openvms) [linux]: 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


Creating a LUN with lun setup (Cont.)

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



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 initiator group. Enter '?' to see existing initiator group names.Name of initiator group []: ?No existing initiator groups.Name of initiator group []: salesigroup

Type of initiator group iWIN_fcp (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 portnames: ?

Initiators connected on adapter ism_sw1:iSCSI Initiator Name Groupiqn.1991-05.com.microsoft:slu2-win.edsvcs.netapp.com



Enter comma separated portnames: iqn.1991-05.com.microsoft:slu2-win.edsvcs.netapp.comEnter comma separated portnames: <CR>

The initiator group has an associated OS type. The following are currently supported: solaris, windows, hpux, aix, linux, netware or vmware.OS type of initiator group "iWIN_fcp" [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 "iWIN_fcp".LUN ID at which initiator group "iWIN_fcp" sees "/vol/SAN/lun1" [0]: 0



LUN Path : /vol/winvol/tree1/lun0OS Type : windowsSize : 12.0g (12889013760)Comment : Windows LUNInitiator Group : salesigroupInitiator Group Type : iSCSIInitiator Group Members : iqn.1991-05.com.microsoft:slu2-win.edsvcs.netapp.comMapped to LUN-ID : 0

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

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



Verify the LUNsystem> lun show –mLUN path Mapped to LUN ID------------------------------------------------/vol/winvol/tree1/lun0 salesigroup 0


System Manager: LUN Setup

To configure LUNs


System Manager: LUN Setup (Cont.)

Recommended workflow creates FlexVol

®

container if possible(1X + autogrow, autodelete)



Items are filtered by free space according to

requested LUN size


System Manager: LUN Management

The newly createdLUN


System Manager: LUN Management (Cont.)

The newly createdigroup


Accessing a LUN


Accessing a LUN

Rescan ifLUN doesn’t

appear automatically

New LUN

Right-clickand Initialize


Accessing a LUN (Cont.)

Right-click and select New Partition....


Accessing a LUN (Cont.)


SnapDrive


SnapDrive

SnapDrive can create an iSCSI LUN on the storage system and automatically attach it to the client host

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

NOTE: If SnapDrive is used to create a LUN, you must useSnapDrive to manage that LUN. Do not use the CLI to delete,rename, or otherwise manage a LUN created by SnapDrive


Other SAN Administration Resources

For more information about SAN administration, see the SAN Administration course

This advanced course covers:– Configuring Solaris hosts for FCP and iSCSI– Configuring Windows hosts for FCP and iSCSI– Creating FCP and iSCSI LUNs from the CLI – Creating FCP and iSCSI LUNs from SnapDrive with

Windows and Solaris– SAN in a clustered storage system environment – SAN performance tuning– SAN troubleshooting


Module Summary

In this module, you should have learned to:Explain the purpose of a SANIdentify supported SAN configurationsDistinguish between FC and iSCSI protocolsDefine a LUN and explain LUN attributesUse the lun setup command and NetApp

System Manager to create iSCSI LUNsAccess and manage a LUN from a Windows

hostDefine SnapDrive and its features

Exercise

Module 10: SAN

Estimated Time: 45 minutes


Check Your Understanding

List the SAN protocols supported by NetApp.– FCP– FCoE– 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


Check Your Understanding (Cont.)

What are the methods of creating a LUN?– Using the lun create command from a

storage system– Using the lun setup command from a storage

system– Using NetApp System Manager from a host– Using SnapDrive from a host

Why would you use SnapDrive in a SAN environment?– It is integrated with Microsoft Management

Console– It ensures a consistent LUN Snapshot copy

M10-SAN Storage Area Network

Documents

Transcript of M10-SAN Storage Area Network