Steve, This is an option that we currently set both server and client side.
http://filers.blogspot.com/2006/01/what-is-options-cifsmaxmpx.html
We saw the error message from the windows server client side. http://support.microsoft.com/kb/898468
The value we set on both sides was 1124.
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Steve Losen Sent: Tuesday, October 23, 2012 5:24 PM To: Ian Dotson Cc: toasters@teaparty.net Subject: Re: Max CIFS Multiplex
The online "Health Check" was telling us that:
sam.misconfig.badValue.cifsMaxMpx: Max Multiplex should not be near or
equal to the value of the option cifs.max_mpx. The value of cifs.max_mpx should be set higher. Please discuss what values are acceptable for this parameter with a NetApp technical support representative. Then, use "options set cifs.max_mpx ..." to set this option to a new value.
We're seeing unusually large high-water mark for cifs max multiplex --
up to 511 (from 'cifs stats -c') We do have some client IIS servers (Server
2003, IIS 6.0) that we suspect are the culprits. "cifs stat -h <ip>" doesn't display the max number of multiplexed cifs sessions requested for a host, only current stats. Is there a way to determine which client had asked for this huge number of multiplexed cifs sessions?
Hi Ian,
I think we ran into a similar situation when a bunch of CIFS clients were behind a firewall that NAT-ed all the clients to the same IP address (different TCP ports). The filer was on the public side of the firewall so all the CIFS sessions appeared to be coming from the same IP.
On second thought, maybe not. "muliplexed" probably means multiple CIFS sessions from the same IP and port. In our case it was the same IP but different ports due to NAT.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
_______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters