Does anyone have any idea what the option cifs.max_mpx does. On a whitepaper from NetApp the option is referenced to be changed to 1124. I presently have it set at 32 and it was hidden.
I am reluctant to make the change without knowing what it does.
********************************************************************** This e-mail is intended only for the addressee named above. As this e-mail may contain confidential or privileged information, if you are not the named addressee, you are not authorised to retain, read, copy or disseminate this message or any part of it. ************************************************************************
"ZANGA, Michael, GCM" wrote:
Does anyone have any idea what the option cifs.max_mpx does. On a whitepaper from NetApp the option is referenced to be changed to 1124. I presently have it set at 32 and it was hidden.
Its very similiar to an NT equivalent read here :
http://support.microsoft.com/support/kb/articles/q191/3/70.asp
This tells the client how many operations can be pending on the filer at the same time. Do a cifs stat on your filer and look for Max Multiplex at the end of it.If you see a number above 32 ,you probably want to raise the option .For clients that make many operations ,specifically Terminal Servers,the recommended value is 1124.For other clients the recommended value is 253 but then again it might be too much above what you need.Setting the value higher that what you need consumes resources on the clients.I guess normally 50 should be enough.To find out what's good for you - run perfmon on the client consuming the most resources and look at the Redirector\current commands stat - Max_mpx should be set to a value above that number.
BTW ,changing this value will not affect active sessions.The number is passed on when we establish the session and once you change the value from 32 ,it would not be hidden anymore.
Hope this helps,
-Puneet ________
"ZANGA, Michael, GCM" wrote:
Does anyone have any idea what the option cifs.max_mpx does. On a whitepaper from NetApp the option is referenced to be changed to 1124. I presently have it set at 32 and it was hidden.
I am reluctant to make the change without knowing what it does.
It is a setting that allows you to increase the netapp equivalent of the MaxMpxCt in the NT server registry. This allows more simultaneous SMB connections. We used it when we ran into a problem with NT terminal servers having so many connections to the filer that the default MaxMpxCt of 50 was exceeded. We set it to 256 (the max) and it all worked very nicely. In the end a different solution was found and implemented by our NT team. But in our testing of solutions the cifs.max_mpx worked fine - we just weren't ready to move to becks at the time because of unrelated issues.
Graham
-
Graham C. Knight -
Puneet Anand -
ZANGA, Michael, GCM