This is where the server_stats command is your friend - the options and output change between DART 5.6, 6.0 and VNX, so be sure to use man server_stats, to see your options..  The CIFS ops/sec you see is the cumulative total of all CIFS operations primatives on your NX4.  The primatives include various operations to open files, lock them, change permissions, etc.  So, even the act of double-clicking to open a file causes multiple primatives on the backend - your Windows client sends more than one command for the open, which results in more than one CIFS operation to open the file from the NX4.  To see the same output, run the command server_stats server_2 -summary cifs - interval 5 -count 5 This shows you five instances of data for a 5-sec interval.  To see a breakdown of this output, run server_stats server_2 -table cifs -interval 5 -count 5 This shows you five instances of much more data for the same interval.  For more information, take a look at the document Managing Statistics on Celerra.  You'll see how you can list the available statistic paths (statpaths) to get much more granular details.  Let us know if this helps!  Karl
hi guys i'm migrating data from a netapp and have not moved everything as yet and i was check ing the CIFS performance on what has been moved and is now currently in use.  the CIFS op/sec are quite high at times and i was wondering can someone explain what the ops/sec really represents  i have attached a performance graph - i'm worried if i moved all the data over the nx4 will  not be able to handle it  i'm currently only using 1 CIFS server and both pool are archive pools using sas in one and sata in the other  Any suggestions would be greatly appreciated  Beag    [IMAGE]
nx4 cifs performance