{"id":453,"date":"2016-06-01T10:44:48","date_gmt":"2016-06-01T14:44:48","guid":{"rendered":"http:\/\/ybontap.tynsoe.org\/wordpress\/?p=453"},"modified":"2016-06-01T10:44:48","modified_gmt":"2016-06-01T14:44:48","slug":"display-big-talkers-clients-on-cdot","status":"publish","type":"post","link":"https:\/\/ybontap.tynsoe.org\/?p=453","title":{"rendered":"Display \u00ab\u00a0big talkers\u00a0\u00bb clients on cDOT"},"content":{"rendered":"

It is a common request from customer that wants to know who are the most active clients to a system. Though not hard to obtain, there is no obvious menu that lets you do that, so there it is :<\/p>\n

First of all, you need to be in advanced mode and start statistics collection for the \u00ab\u00a0client\u00a0\u00bb object :<\/p>\n

netapptest2::*> set advanced\nWarning: These advanced commands are potentially dangerous; use them only when directed to do so by NetApp personnel.\nDo you want to continue? {y|n}: y\n\nnetapptest2::*> statistics start -object client<\/code><\/pre>\n
Then you let it run for some time, and you can start looking at who the most active clients are :\n netapptest2::*> statistics show -object client -instance !Cluster* -sort-key nfs3_ops -counter nfs3_ops -tab\n\nntap2_vs1: client: 5\/31\/2016 23:59:26\n\ninstance nfs3\n name ops\n ---------------------- ----\n ntap2_vs1:10.20.245.11 31\n ntap2_vs1:10.20.45.95 0\n ntap2_vs1:10.20.45.67 0\n ntap2_vs1:10.20.45.60 0\n ntap2_vs1:10.20.45.58 0\n ntap2_vs1:10.20.45.43 0\n ntap2_vs1:10.20.45.40 0\n ntap2_vs1:10.20.45.39 0\n ntap2_vs1:10.20.45.37 0\n ntap2_vs1:10.20.45.33 0\n ntap2_vs1:10.20.45.235 0\n ntap2_vs1:10.20.45.234 0\n ntap2_vs1:10.20.45.226 0\n ntap2_vs1:10.20.45.225 0\n ntap2_vs1:10.20.45.223 0\n ntap2_vs1:10.20.45.221 0\n ntap2_vs1:10.20.45.218 0\n ntap2_vs1:10.20.45.195 0\n ntap2_vs1:10.20.45.19 0\n ntap2_vs1:10.20.45.183 0\n ntap2_vs1:10.20.45.18 0\n ntap2_vs1:10.20.45.158 0\n ntap2_vs1:10.20.45.157 0\n ntap2_vs1:10.20.45.156 0\n ntap2_vs1:10.20.45.134 0\n ntap2_vs1:10.20.45.133 0\n ntap2_vs1:10.20.45.132 0\n ntap2_vs1:10.20.45.124 0\n ntap2_vs1:10.20.45.120 0\n ntap2_vs1:10.20.45.118 0\n ntap2_vs1:10.20.45.114 0\n ntap2_vs1:10.20.45.113 0\n ntap2_vs1:10.20.45.108 0\n ntap2_vs1:10.20.45.100 0\n 34 entries were displayed.<\/pre>\n
You can use another field instead of nfs3_ops, just use \u00ab\u00a0?\u00a0\u00bb character to get a list of available fields when you get to that part of the command line.<\/p>\n
Here are the options available at this time, you can also use multiple fields by using a comma \u00ab\u00a0,\u00a0\u00bb separator.<\/p>\n
\u00a0\u00a0cifs_ops \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 cifs_read_ops\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 cifs_read_size \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 cifs_write_ops \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 cifs_write_size\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 instance_name\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 instance_uuid\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 local_ops\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 mount_ops\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 nfs2_ops \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 nfs3_ops \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 nfs4_ops \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 node_name\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 node_uuid\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 process_name \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 remote_ops \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 rx_data\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 rx_packets \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 total_ops\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 tx_data\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 tx_packets \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 vserver_id \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\n\u00a0 vserver_name<\/pre>\n","protected":false},"excerpt":{"rendered":"
It is a common request from customer that wants to know who are the most active clients to a system. Though not hard to obtain, there is no obvious menu that lets you do that, so there it is : First of all, you need to be in advanced mode and start statistics collection for […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3,8],"tags":[],"_links":{"self":[{"href":"https:\/\/ybontap.tynsoe.org\/index.php?rest_route=\/wp\/v2\/posts\/453"}],"collection":[{"href":"https:\/\/ybontap.tynsoe.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ybontap.tynsoe.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ybontap.tynsoe.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ybontap.tynsoe.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=453"}],"version-history":[{"count":0,"href":"https:\/\/ybontap.tynsoe.org\/index.php?rest_route=\/wp\/v2\/posts\/453\/revisions"}],"wp:attachment":[{"href":"https:\/\/ybontap.tynsoe.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=453"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ybontap.tynsoe.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=453"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ybontap.tynsoe.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=453"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}