iSCSI on NetAPP as Target and Windows 2003 Software initiator

hi
we have an iSCSI protocol loaded on NetApp machine that holds several
Qtrees
we already configured a windows 2003 machine with iSCSI initiator and
recognized the iSCSI target on the NetApp Machine.
BUT how can i make the iSCSI space (allocated on the NetApp) not
beeing presented as an Image file but as a whole Vol(like
/vol/ShareName) ?

also , how can i enlarge the space already allocated WITHOUT
formating the windows 2003 partition(which is an iSCSI node) already
created ?

thanks a lot
m.b

On 5 Feb 2004 01:40:33 -0800, (Moshiko) wrote:

hi
we have an iSCSI protocol loaded on NetApp machine that holds several
Qtrees
we already configured a windows 2003 machine with iSCSI initiator and
recognized the iSCSI target on the NetApp Machine.
BUT how can i make the iSCSI space (allocated on the NetApp) not
beeing presented as an Image file but as a whole Vol(like
/vol/ShareName) ?

You can't. The documents state:

A LUN path must be absolute. A LUN can only reside in a
volume or qtree root. For example, to create a LUN with
the name "lun0" in the qtree root /vol/vol/q0, specify
the path as "/vol/vol1/q0/lun0".



also , how can i enlarge the space already allocated WITHOUT
formating the windows 2003 partition(which is an iSCSI node) already
created ?

Not sure about growing an iSCIS lun. If it can be done (I have no
iSCSI licenses and therefore no way to test) then Windows will be able
to grow dynamically as well. Windows Disk Manager is really just
sending commands to Veritas File System. It's been integrated in
Windows for a while now can be grown on the fly just fine.


~F

"Moshiko" wrote in message
om...
hi
we have an iSCSI protocol loaded on NetApp machine that holds several
Qtrees
we already configured a windows 2003 machine with iSCSI initiator and
recognized the iSCSI target on the NetApp Machine.
BUT how can i make the iSCSI space (allocated on the NetApp) not
beeing presented as an Image file but as a whole Vol(like
/vol/ShareName) ?

I don't think its possible, because the "LUN" created on the NetApp appears
as a huge file within NetApp filesystem. There is no way for the filer to
know what's inside that file, its not in the standard CIFS format in order
for you to share it. The LUN could be anything, meaning Windows, Unix,
Linux, AIX etc depending on which machine the LUN is attached to.

Having said that, for Windows, NetApp has a product called
SnapManager/SnapDrive that can present that LUN or a snapshot of it to
another Windows machine as a CIFS share (I think. Need to readup on it
further)

also , how can i enlarge the space already allocated WITHOUT
formating the windows 2003 partition(which is an iSCSI node) already
created ?
Again depends on what you used as the iSCSI initiator. M$ driver based
software initiator does not (yet) support dynamic drives on iSCSI.
I have sucessfully used hardware based iSCSI (Adaptec & Intel) to create
dynamic drives and expanded them on the fly without problems. Though
officially NetApp doesn't support it

-G

thanks a lot
m.b

"Faeandar" wrote in message
...
On 5 Feb 2004 01:40:33 -0800, (Moshiko) wrote:

hi
we have an iSCSI protocol loaded on NetApp machine that holds several
Qtrees
we already configured a windows 2003 machine with iSCSI initiator and
recognized the iSCSI target on the NetApp Machine.
BUT how can i make the iSCSI space (allocated on the NetApp) not
beeing presented as an Image file but as a whole Vol(like
/vol/ShareName) ?

You can't. The documents state:

A LUN path must be absolute. A LUN can only reside in a
volume or qtree root. For example, to create a LUN with
the name "lun0" in the qtree root /vol/vol/q0, specify
the path as "/vol/vol1/q0/lun0".

I think the OP's question was if he could share out that qtree
(/vol/vol1/q0/lun0) as a CIFS share. Am I correct??

Wouldn't that have been cool if we could do that?
-G



also , how can i enlarge the space already allocated WITHOUT
formating the windows 2003 partition(which is an iSCSI node) already
created ?

Not sure about growing an iSCIS lun. If it can be done (I have no
iSCSI licenses and therefore no way to test) then Windows will be able
to grow dynamically as well. Windows Disk Manager is really just
sending commands to Veritas File System. It's been integrated in
Windows for a while now can be grown on the fly just fine.


~F

Good to know. Thanks.

I imagine you can still cat 2 LUN's that have been presented into a
single drive? Or is that a dynamic disk thingy as well?

~F

On Fri, 06 Feb 2004 02:03:51 GMT, "Net Worker"
wrote:


Again depends on what you used as the iSCSI initiator. M$ driver based
software initiator does not (yet) support dynamic drives on iSCSI.
I have sucessfully used hardware based iSCSI (Adaptec & Intel) to create
dynamic drives and expanded them on the fly without problems. Though
officially NetApp doesn't support it

-G

thanks a lot
m.b

Not an Windows expert, but I think that option is only available for dynamic
disks.
-G

"Faeandar" wrote in message
...
Good to know. Thanks.

I imagine you can still cat 2 LUN's that have been presented into a
single drive? Or is that a dynamic disk thingy as well?

~F

On Fri, 06 Feb 2004 02:03:51 GMT, "Net Worker"
wrote:


Again depends on what you used as the iSCSI initiator. M$ driver based
software initiator does not (yet) support dynamic drives on iSCSI.
I have sucessfully used hardware based iSCSI (Adaptec & Intel) to create
dynamic drives and expanded them on the fly without problems. Though
officially NetApp doesn't support it

-G

thanks a lot
m.b

you can expand a lun if you create this lun with snapdrive.

On Fri, 06 Feb 2004 02:28:29 GMT, "Net Worker"
wrote:

Not an Windows expert, but I think that option is only available for dynamic
disks.
-G

"Faeandar" wrote in message
.. .
Good to know. Thanks.

I imagine you can still cat 2 LUN's that have been presented into a
single drive? Or is that a dynamic disk thingy as well?

~F

On Fri, 06 Feb 2004 02:03:51 GMT, "Net Worker"
wrote:


Again depends on what you used as the iSCSI initiator. M$ driver based
software initiator does not (yet) support dynamic drives on iSCSI.
I have sucessfully used hardware based iSCSI (Adaptec & Intel) to create
dynamic drives and expanded them on the fly without problems. Though
officially NetApp doesn't support it

-G

thanks a lot
m.b