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?
Thanks, Ian Dotson