UNSOLVED

cadencep45

updated

12 years ago

C

cadencep45

4 Apprentice

318 Posts

0

1918

July 16th, 2014 04:00

VNX CIFS WAN Performance

I know its an oxymoron talking about WAN and performance in the same sentence, however looking at a CIFS server being written to from a remote ( WAN ) client, a couple of things;

1. Can I determine if the session is SMB 1,2,2.1 or 3 ?

2. If it is SMB 3, and there is a single NIC on the VNX on the WAN network, how can I confirm that it is supporting multiple parallel tcp/ip sessions to speed up data transfer ? I Have read about Receive Side Scaling (RSS), but on looking at

server_param server_2  -facility tcp -list

server_2 :

param_name                       facility  default     current   configured

dosfeatureoptionset                  tcp          0          0

ackpush                              tcp          0          0

dosattackadminoptionset              tcp          0          0

dosattackautorecoveryoptionset       tcp          0          0

strictsource                         tcp          0          0

pcbHashLock                          tcp          0          0

maxhalfopenconnections               tcp      65535      65535

dosattackadminrecoveryoptionset      tcp          0          0

do_sack                              tcp          1          1

fastRTO                              tcp          0          0

sndcwnd                              tcp          0          0

dosmonitortimeoutvalue               tcp          5          5

dosattackautodefenseoptionset        tcp          0          0

std_slowstart                        tcp          0          0

backlog                              tcp        100        100

dossynreceivedtimeoutvalue           tcp         35         35

do_newreno                           tcp          1          1

maxStreams                           tcp      65535      65535

not sure where to look.

Tks,

-Bob

  • cadencep45

    4 Apprentice

    318 Posts

    1259

    0

    Posted July 16th, 2014 07:00

    ok, I have figured out the first part;

    running server_cifs server_2 -option audit,full | grep SMB

    will give me that. So the question that is outstanding is there CIFS WAN Specific optimization that can be done, assuming a SMB 2.1 client.

  • Rainer_EMC

    6 Operator

    8645 Posts

    1259

    0

    Posted July 16th, 2014 10:00

    None that I am aware of

    You could look at BranchCache if your environment supports it - see the EMC white paper

  • cadencep45

    4 Apprentice

    318 Posts

    1259

    0

    Posted July 16th, 2014 23:00

    alas BranchCache will not resolve the issue, as the remote servers being used are quite sensitive to performance degrading issues. Our concern is when we compare a windows CIFS cluster against a VNX, the performance of the windows cluster is very significently better. Our understanding is the we are seeing the main difference in the TCP/IP stack, which leads us to ask is there a CIFS WAN performance tuning document somewhere ?

  • XURI

    5 Posts

    1259

    0

    Posted April 26th, 2015 14:00

    Hello,

    I have the same issue. Did you solve the performance problem?  Have done some testing against VNX and Windows server through the WAN and we almost double the performance with the Windows file Server. It seems to be that is needed some tuning with congestion control and TCP Window scaling.

    Regards,

    Sergio

  • cadencep45

    4 Apprentice

    318 Posts

    1259

    1

    Posted April 27th, 2015 01:00

    The answer is this was not a logical use case so we did not progress this.

  • 1259

    0

    Posted April 27th, 2015 03:00

    This post is helpful as we were planning to migrate the CIFS servers from Windows to the VNX-File.

    Good insight from the bandwidth and performance perspective to review.

  • cadencep45

    4 Apprentice

    318 Posts

    1259

    0

    Posted April 27th, 2015 03:00

    its fine in a LAN environment, but do a Proof of Concept before commiting to a WAN environment. CIFS is not engineered to work optimally in a WAN environment and branchcache etc are engineering ways of reducing the impact, but its plaster ( although a nicely designed plaster ) to the problem.