Multistore max_mpx

sjallabais — Thu, 05 Jun 2025 06:52:31 GMT

Hi!

I am trying to understand how the max_mpx setting should be handled when having multiple vfilers.

In a Citrix environment this should be increased, but it looks like the "Max Multiplex" from the "cifs stat"

command are higher than the cifs.max_mpx setting.

Are this somehow shared between vfilers, or do each vfiler have their own separate mecanism for this?

I have seen recomendations to set it high initially (1124) when running Citrix, and others wants to fine

tune..

Has vfiler0 max_mpx setting any influence on the vfilers?'

/Sjalla

Multistore max_mpx

scottgelb — Tue, 21 Jun 2011 20:19:22 GMT

The max_mpx setting is set separately per vFiler. The setting in vfiler0 does not affect non-default vfilers.

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

cifs.max_mpx This option controls how many simultaneous operations the filer reports that it can process. An "operation" is each I/O the client believes is pending on the filer including outstanding change notify operations. Clients such as Windows Terminal Server or IIS may require that this number be increased to avoid errors and performance delays.

CAUTION - The approved values for this parameter are 50, 126, 253, and 1124. The most accurate way to determine which number to use is to measure the Redirector-Current Commands statistic on the client with NT perfmon and to increase the number until Current Commands does not hit the negotiated limit. For more information see Microsoft Knowledge Base articles Q191370 and Q232890.

CAUTION - This number should only be changed while cifs is terminated.

CAUTION - Only use the approved values to avoid Q232890.

CAUTION - This value affects allocations in the clients. Use the smallest value necessary for correct behavior.

Default: 50

Values: 50, 126, 253, 1124

Effective: Immediately

Persistence: Remains in effect across system reboots

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:

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.

Multistore max_mpx

sjallabais — Wed, 06 Jul 2011 12:54:53 GMT

Thanks!

Now I see from the 8.0.1 Release notes that the default cifs.max_mpx value has changed to 255??

http://now.netapp.com/NOW/knowledge/docs/ontap/rel801/html/ontap/rnote/GUID-134FBB03-7323-474B-A0C5-3399CA43D737.html

How does this compute, are there also new rules for the default values?

How does this relate to vfilers (and vfiler0)?

Lots of questions 🙂

Regards

/Sjalla

topic Multistore max_mpx in Network and Storage Protocols

Multistore max_mpx

Multistore max_mpx

Multistore max_mpx