Creating LUNs on vFilers
Prerequisite for creating LUNs on vFilers
You must purchase a MultiStore licence to create vFilers. Then you can enable the iscsi license for each vFiler to manage LUNs (and igroups) on a per vFiler basis.
Note
SnapDrive can only connect to and manage LUNs on the hosting filer, not to vFilers.
Guidelines for creating LUNs on vFilers
Use the following guidelines when creating LUNs on vFilers.
- The vFiler access rights are enforced when the filer processes iSCSI host requests.
- LUNs inherit vFiler ownership from the storage unit on which they are created. For example, if /vol/vfstore/vf1_0 is a qtree owned by vFiler vf1, all LUNs created in this qtree are owned by vf1.
- As vFiler ownership of storage changes, so does ownership of the storage's LUNs.
Setting up vFilers with the iSNS service
To set up vFilers with the iSNS service, complete the following steps for each vFiler.
Step
|
Action
|
|
1 |
Set the IP address of the iSNS server.
|
|
2 |
Enter the following command to enable the service:
iscsi isns start
|
LUN subcommands available on vFilers
You can use the following LUN subcommands on vFiler LUNs:
attribute
|
help
|
online
|
show
|
clone
|
map
|
resize
|
snap
|
comment
|
maxsize
|
serial
|
stats
|
create
|
geometry
|
set
|
unmap
|
destroy
|
move
|
setup
|
|
df
|
offline
|
share
|
|
Note
You cannot use the lun rescan for vFiler LUNs.
Methods for issuing LUN subcommands on vFilers
You can issue LUN subcommands using the following methods:
- From the default vFiler (vfiler0) on the hosting filer, you can:
- From non-default vFilers, you can:
- Enter the vfiler run * lun
Creating LUNs on a vFiler
To create LUNs on a vFiler, complete the following step.
Step
|
Action
|
|
1 |
Enter the lun create command in the vFiler context that owns the storage, as follows:
vfiler run vfiler_name lun create -s 2g -t os_type /vol/vfstore/vf1_0/lun0
Example
The following command creates a LUN on a vFiler at /vol/vfstore/vf1_0:
vfiler run vf1 lun create -s 2g -t windows /vol/vfstore/vf1_0/lun0
Note If you omit the vfiler command and the context, an error message is displayed. Example
The following command omits the vfiler run command and the storage context (vf1).
lun create -s 2g -t windows /vol/vfstore/vf1_0/lun0
Result
The following error message is displayed:
lun create: Requested LUN path is inaccessible.
|
Displaying vFiler LUNs
To display LUNs owned by the vFiler context, complete the following step.
Step
|
Action
|
|
1 |
Enter the following command from the vFiler that contains the LUNs:
vfiler run * lun show
Result
The following information is an example of what is displayed.
==== vfiler0
/vol/vfstore/vf0_0/vf0_lun0 2g (21437483648) (r/w, online)
/vol/vfstore/vf0_0/vf0_lun1 2g (21437483648) (r/w, online)
==== vfiler1
/vol/vfstore/vf0_0/vf1_lun0 2g (21437483648) (r/w, online)
/vol/vfstore/vf0_0/vf1_lun1 2g (21437483648) (r/w, online)
|
How to manage vFiler LUNs
You use the available LUN commands by preceding them with the vfiler run vfiler_name * command.
Copyright © 1994-2003, Network Appliance, Inc. All rights
reserved.
Part No. 210-00571
File: c2cr-i9.htm
Last updated: 11/21/03 17:02:19