Mark,
iSCSI from Novell to NetApp should work just fine if you are only interested in presenting virtual disk Luns and not the NetApp filesystem.   In this mode the Novell server will treat the connection like any other hard disk or disk array connection.  You still will get many of DataOnTaps great features but at the level of NetApp filers presenting virtual disks/Luns.  
 
Functionally, you could do the same thing with a Fibre Channel interface between the Novell server and the "front" of a filer  This could be accomplished  if NetApp wrote some HBA drivers for Novell.  Don't hold your breath.
 
iSCSI "theoretically" solves many of these  Fibre Channel issues by using your existing network infrastructure and working with more open drivers that supplied by each vendor of each end device.  Novell writes Novell and NetApp writes only NetApp. 
 
The ideal environment for iSCSI is any environment that works well on a tranaction basis across a network.   This implies latency tolerance.   Unlike direct SCSI or FC/SCSI interfaces which have highly deterministic operating charactistics iSCSI hasn't yet achieved those characteristics, i.e. link failover timing issues, etc.  
 
Buy some cards on both ends and try it out in a controlled environment when all the pieces are out.
 
Good luck,
Hunter
----- Original Message -----
From: Mark McGilvray
To: toasters@mathworks.com
Sent: Wednesday, April 16, 2003 6:25 AM
Subject: RE: CIFS in Workgroup mode

 
Along the NetWare support lines, we are hoping that iSCSI will provide the support we need for Novell.  From what we understand the NetWare iSCSI initiator will ship in the NetWare 6.5 box in June.
 
Any thoughts?
 
Mark

>>> Alan McLachlan <amclachlan@asi.com.au> 04/16/03 12:17AM >>>
Robert,

One problem is that in workgroup mode NTFS security isn't available. In
fact, no real security is available...

There appear to be two options to using a filer in a Novell environment:

1) The "gateway" Novell server approach. This involves using a Novell server
running Novell NFS Services (with lots of CPU and RAM) with a direct
back-to-back link to the filer to act as an I/O path. Clients and
application hosts only see the Novell server, while the filer thinks the
Novell server is a Unix NIS server that also happens to be it's only client
:o). Security is a subset of Novell permissions as available by mapping Unix
permissions. The drawback here is that the Novell server itself will be an
I/O bottleneck.

2) eDirectory and Windows integration. For this you need a DC, as you have
identified. The Windows DC runs the Novell eDirectory client and the
security is synchronised with Novell Account Manager. All clients that need
to access the filer need to have the CIFS redirector running. Permissions
are mapped by Novell Account Manager.

An issue with approach 2 is that when passwords are changed by a helpdesk
directly in eDirectory, they may not be synchronised immediately. If anyone
has found a workaround for this please respond.

regards,

Alan.


-----Original Message-----
From: Robert Borowicz [mailto:rbaus@swbell.net]
Sent: Wednesday, 16 April 2003 6:26 AM
To: toasters@mathworks.com
Subject: CIFS in Workgroup mode


Does anybody run CIFS shares in workgroup mode? That is not
booted/authenticated with a PDC?

I have the joy of trying to make my machine work in a Novell environment
and no DC and would love to share ideas with other lucky souls like me....

TIA

-Bob Borowicz


**** ASI Solutions Disclaimer ****
The material transmitted may contain confidential and/or privileged
material and is intended only for the addressee.  If you receive this in
error, please notify the sender and destroy any copies of the material
immediately. ASI will protect your Privacy according to the 10 Privacy
Principles outlined under the new Privacy Act, Dec 2001.

This email is also subject to copyright.  Any use of or reliance upon this
material by persons or entities other than the addressee is prohibited.

E-mails may be interfered with, may contain computer viruses or other
defects.  Under no circumstances do we accept liability for any loss or
damage which may result from your receipt of this message or any
attachments.
**** END OF MESSAGE ****