V-filer & ISCSI

[#1]

Dear all Commuities Members,

I would like know if there is specifics limitations regarding number of Iscsi Connection onVfiler?

If my FAS is able to host N iscsi connection

Can I use all the connections for a specific Vfiler?

Does the max possible connections is the sum off all VFiler & Filer0 Iscsi Connections?

From Filer0 am I able to have the sum off all Vfiler Iscsi Connections?

I have read the vfiler.pdf from DOT 8.0.1 but few questions still be pending

Regards

Christophe.

[#2]

hello,

i only know, that you can have 32 connections per session. you can change this value "options iscsi". i dont know if you can have this maximum of connection per vfiler.

[#3]

The iscsi max ios and connections per session options are available in vfiler0 and not in vfilers.  The setting in vfiler0 is for all vfilers.

[#4]

http://now.netapp.com/NOW/knowledge/docs/ontap/rel801/html/ontap/cmdref/man1/na_options.1.htm

VFILER CONSIDERATIONS

Each vfiler has its own set of options. Vfilers, however, recognize only a subset of the options recognized by a filer. The list of options recognized by a vfiler are:

Each vfiler has its own set of options. Vfilers, however, recognize only a subset of the options recognized by a filer. The list of options recognized by a vfiler are:

  cifs.audit.enable

  cifs.audit.file_access_events.enable

  cifs.audit.logon_events.enable

  cifs.audit.logsize

  cifs.audit.saveas

  cifs.bypass_traverse_checking

  cifs.comment

  cifs.guest_account

  cifs.home_dir_namestyle

  cifs.homedirs_public_for_admin

  cifs.idle_timeout

  cifs.max_mpx

  cifs.netbios_aliases

  cifs.netbios_over_tcp.enable

  cifs.nfs_root_ignore_acl

  cifs.oplocks.enable

  cifs.oplocks.opendelta

  cifs.perm_check_ro_del_ok

  cifs.perm_check_use_gid

  cifs.preserve_unix_security

  cifs.restrict_anonymous.enable

  cifs.save_case

  cifs.scopeid

  cifs.search_domains

  cifs.show_snapshot

  cifs.shutdown_msg_level

  cifs.sidcache.enable

  cifs.sidcache.lifetime

  cifs.snapshot_file_folding.enable

  cifs.symlinks.cycleguard

  cifs.symlinks.enable

  cifs.trace_login

  cifs.universal_nested_groups.enable

  dns.domainname

  dns.enable

  ndmpd.access

  ndmpd.authtype

  ndmpd.connectlog.enabled

  ndmpd.enable

  ndmpd.ignore_ctime.enabled

  ndmpd.password_length

  nfs.mount_rootonly

  nfs.per_client_stats.enable

  nfs.require_valid_mapped_uid

  nfs.tcp.enable

  nfs.udp.xfersize

  nfs.v2.df_2gb_lim

  nfs.v3.enable

  nfs.webnfs.enable

  nfs.webnfs.rootdir

  nfs.webnfs.rootdir.set

  nis.domainname

  nis.enable

  nis.group_update.enable

  nis.group_update_schedule

  nis.servers

  nis.slave.enable

  pcnfsd.enable

  pcnfsd.umask

  rsh.access

  rsh.enable

  security.passwd.rules.enable

  snapmirror.enable

  snapmirror.checkip.enable

  snapmirror.access

  snapvault.access

  snapvault.enable

  wafl.default_nt_user

  wafl.default_unix_user

  wafl.nt_admin_priv_map_to_root

  wafl.wcc_max_entries

  wafl.wcc_minutes_valid

These options only affect the operation of the concerned vfiler. When run in the context of a vfiler, (e.g. via the vfiler run command), the options command only prints the options recognized by a vfiler, and can only change these options.

[#5]

Hi Scott,

Thanks for your answer, I think I'm must clarify my question.

If I'm able to have a limitation of 256 Iscsi connections on a FAS.

Can I use all this connections for one Vfiler or I have a limitation per Vfiler (Dot 8.01.P5 FAS6240 HA)

regards

[#6]

I dont' see anything in the documentation other than it is a vfiler0 (physical FAS) limit.  It infers that the limit it on the physical system regardless of how it is split up across vfilers...so it should work on a single vfiler at that limit (but wouldn't have connections for other vfilers)... a physical system limit regardless of vfiler or not.  Maybe someone from engineering (or if I missed somewhere in a TR or documentation) can post on this to confirm.