Dmitry Yusupov wrote:
Hi Frank,
Hi Dimitri
May I also suggest an alternative for iSCSI target? We had a very good
experience with open-iscsi and NexentaStor [1]. At the beginning we had
problems with single-threaded traffic latency but the ultimate fix was
on Linux side to ensure
By default the filer has these iscsi (Ontap 7.3.1) values set
iscsi.enable on
iscsi.isns.rev 22
iscsi.max_connections_per_session use_system_default
iscsi.max_error_recovery_level use_system_default
jnantel wrote:
I use a netapp filer...where are these values
First i would ask why the hell ?
The netapp filer is a very good CIFS/SMB share server. Using it as an iSCSI
target -- which is not is primary
function (netapp filer are more NAS than SAN) -- will only create
limitations (unable to resize volume on the fly,
unable to use wafl attributes to store
benoit plessis wrote:
First i would ask why the hell ?
The netapp filer is a very good CIFS/SMB share server. Using it as an
iSCSI target -- which is not is primary
function (netapp filer are more NAS than SAN) -- will only create
limitations (unable to resize volume on the fly,
unable
I use a netapp filer...where are these values set? Host or Array?
iscsi.iswt.max_ios_per_session 64
iscsi.max_connections_per_session 16
iscsi.max_ios_per_session64
On Apr 14, 6:40 am, benoit plessis plessis.ben...@gmail.com wrote:
First i would ask why the hell ?
The netapp filer is a
On Tue, Apr 14, 2009 at 7:09 PM, Dmitry Yusupov dmitry_...@yahoo.com wrote:
NexentaStor also is very good candidate for CIFS workgroups/AD
environments with the whole SMB stack implemented in the kernel, which
boosts performance over the top. And as far as iSCSI target - I would
recommend to
