--- Sjoerd Hooft's InFormation Technology ---

User Tools

Site Tools



Would you like to sponsor this site?
Or buy me a beer?:

Recently Changed Pages:

View All Pages
View All Q Pages

View All Tags

Sign up for Q to post comments.

WIKI Disclaimer: As with most other things on the Internet, the content on this wiki is not supported. It was contributed by me and is published “as is”. It has worked for me, and might work for you.
Also note that any view or statement expressed anywhere on this site are strictly mine and not the opinions or views of my employer.

Terms And Conditions for Q users

Pages with comments

2019/06/22 10:36 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 1 Comment
2019/03/15 16:02 3 Comments
2017/04/20 15:28 1 Comment
2017/04/20 15:23 1 Comment
2017/04/19 14:44 1 Comment
2017/04/17 20:10 1 Comment
2017/04/17 20:07 1 Comment
2017/04/17 19:58 1 Comment
2017/04/17 19:52 1 Comment

View All Comments


NetApp Storage


This is a page intended to give a small summary on creating usable storage on a NetApp SAN. Topics covered are:

  • Terminology
  • Create a volume
  • Create a LUN
  • Create an initiator group
  • Create a mapping between an initiator group and a LUN
  • References



Aggregates are containers that capture all the physical aspects of storage such as disks and RAID groups. An aggregate can contain one or more flexible volumes or a single traditional volume. You cannot mix volume types on an aggregate.
Consider this caveat when you're creating aggregates.


There are two types of volumes on a NetApp:

  • Traditional volumes

Traditional volumes combine the physical layer of storage (the disk and RAID properties) with the logical layer of the file system (the volumes and any other containers that are used to store files and directories).

  • Flexible volumes (also called FlexVol volumes)

Flexible volumes allow you to manage the logical layer of the file system independently of the physical layer of storage. Multiple flexible volumes can exist within a single separate, physically defined aggregate structure of disks and RAID groups. Flexible volumes contained by the same aggregate share the physical storage resources, RAID configuration, and plex structure of that aggregate.

Note that in this article we'll work with flexible volumes only.


The Logical Unit (LUN) is a unit of storage on a storage system that is accessed by clients.

Initiator group and mapping

An initiator group (igroup) specifies which initiators can have access to a LUN. When you map a LUN on a storage system to the initiator group, you grant all the initiators in that group access to that LUN. If a host is not a member of an igroup that is mapped to a LUN, that host does not have access to the LUN.

In the case of iSCSI clients, hosts are identified in an initiator group by their node names. In the case of FCP clients, hosts are identified in an initiator group by their World Wide Port Names (WWPNs).


A Snapshot copy is a read-only image of the entire Data ONTAP file system. It reflects the state of the file system at the time the Snapshot copy is created.

See free space on a NetApp

Go into the filer, click on aggregates, click manage and you can see how many free space there is on each aggregate: netappstorage-aggregatefreespace.jpg

Create a volume

Go into the filer, click on volumes and click add. A new window pops up, displaying a wizard for making a new volume. Follow the directions but keep the following configurations in mind: netappstorage-volumetypeselection.jpg
Choose to create a flexible volume. netappstorage-volumeparameters.jpg
Give an appropriate name, select POSIX as language and enable UTF-8. netappstorage-volumeparameters2.jpg
Select the correct aggregate and keep the space guarantee on volume. netappstorage-volumesize.jpg
These setting should be according to your needs and environment. I don't use snapshots, which makes me select these settings.

Modify the created volume

After creating the volume you'll need to modify some of the settings. To modify a volume go into the filer, click on volumes and click manage. Then click the volume you want to modify. This will get you into the properties of the volume. Then click modify, which will get you another wizard to modify the volume. Follow the directions and modify what you want to modify: netappstorage-volumemodifyunicode.jpg

  • Enable Convert To Unicode because this will save conversion time and facilitate file sharing.


  • Enable Minimal Read Ahead if the accessing clients will be ESX clients. In almost any other case leave this disabled.
  • Disable Update Access Time because this will prevent a lot of minor writes in the filesystem.

Because I don't wanna use snapshots I also modify the snapshots settings. To do so, go into the filer, click on volumes, click on snapshots and select the correct volume. Then disable Scheduled Snapshots: netappstorage-volumemodifysnapshot.jpg

Create a LUN

Go into the filer, click on LUNs and click add: netappstorage-luncreate.jpg

  • Give a nice name, something descriptive would be nice.
  • Also give the correct LUN protocol type. It's very important to select the correct type. For me, in this case it's VMware, other possibilities include AIX, linux and NetWare.
  • If you give a wrong size you'll receive this error:


  • If you click manage when you're done you'll see the new created LUN in the list:


Create an initiator group

Go into the filer, click on LUNs, click on Initiator Groups and click on add. netappstorage-igcreate.jpg
This is with Fibre Channel. netappstorage-igmodify.jpg
This is with iSCSI.

Create a mapping between an initiator group and a LUN

If you go back to managing LUNs, to the originally created lun you can create a mapping between an initiator group and a LUN id: netappstorage-lunmanage.jpg
Click the “No Maps” button on the right, and click the “Add Groups to Map” button in the right top corner: netappstorage-lunmapaddgroup.jpg
Select the just created group. netappstorage-lunmapaddlunid.jpg
Determine the correct LUN id. You can make up the LUN id, there's just one restriction. For the clients connecting to the storage it has to be an unique LUN id. Which means, if the clients already have a few luns you should make a LUN id not in use yet.

Using the created LUN


You could leave a comment if you were logged in.
netappstorage.txt · Last modified: 2013/01/26 21:11 by sjoerd