emc vnx series - dell emc russia · pdf fileemc®vnx® series release 8.1 managing...

EMC®VNX® SeriesRelease 8.1

Managing Statistics for VNX®P/N 300-014-339 Rev 01

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-91031-508-435-1000

www.EMC.com

Copyright © 1998 - 2013 EMC Corporation. All rights reserved.

Published August 2013

EMC believes the information in this publication is accurate as of its publication date. Theinformation is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." EMC CORPORATIONMAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TOTHE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires anapplicable software license.

For the most up-to-date regulatory document for your product line, go to the TechnicalDocumentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks onEMC.com.

All other trademarks used herein are the property of their respective owners.

Corporate Headquarters: Hopkinton, MA 01748-9103

2 Managing Statistics for VNX 8.1

Contents

Preface.....................................................................................................5

Chapter 1: Introduction...........................................................................7System requirements...............................................................................................8User interface choices.............................................................................................8Related information................................................................................................8

Chapter 2: Concepts...............................................................................9Performance statistics summaries.......................................................................10Performance statistics tables................................................................................12

Chapter 3: Managing............................................................................15Display performance statistics summaries........................................................16

Display a summary of system statistics...................................................17Display a summary of CIFS protocol statistics.......................................20Display a summary for NFS protocol statistics.......................................21Display a summary statistics for caches...................................................22

Display performance statistics sets.....................................................................23Display network device statistics..............................................................24Display basic volume statistics..................................................................26Display meta volume or file system statistics.........................................28Display CIFS operations statistics.............................................................29Display NFS operations statistics..............................................................30

Display Correlated Statistics Information.........................................................30View Correlated Statistics Information....................................................32Display Correlated Statistics list for CIFS................................................34

Managing Statistics for VNX 8.1 3

Display NFS statistics correlated by filesystem and NFSoperation attributes...............................................................................35

Display NFS statisitics correlated by a single filesystem.......................38Display NFS statistics correlated by a specific filesystem and a

specific client..........................................................................................39Display NFS statistics correlated by filesystem for a specific

client and operation...............................................................................40Monitor CIFS Client Statistics....................................................................41Monitor NFS Client Statistics.....................................................................43Monitor CIFS User Statistics......................................................................44Monitor CIFS Server Statistics...................................................................45Monitor File system Statistics....................................................................47Monitor NFS User Statistics ......................................................................50Monitor Store Volume Statistics................................................................52Display NFS User Information..................................................................53Monitor NFS Group Statistics....................................................................54Monitor NFS Export Statistics...................................................................55Monitor files per Quota Tree statistics......................................................57Monitor NFS VDM Client Statistics..........................................................63Monitor NFS VDM User Statistics............................................................65Monitor NFS VDM Group Statistics.........................................................66Monitor NFS VDM Export Statistics.........................................................67The -noresolve option.................................................................................69

Display statistics for Continuous Monitoring...................................................71Configure CPU utilization policy, memory utilization

notification policy, and average response time for NFSoperations policy...................................................................................71

Restart the alert daemon process..............................................................73Sort by field name..................................................................................................74

Chapter 4: Troubleshooting..................................................................75EMC E-Lab Interoperability Navigator..............................................................76VNX user customized documentation...............................................................76Error messages.......................................................................................................76EMC Training and Professional Services...........................................................77

Glossary..................................................................................................79

Index.......................................................................................................81


Contents

Preface

As part of an effort to improve and enhance the performance and capabilities of its product lines,EMC periodically releases revisions of its hardware and software. Therefore, some functions describedin this document may not be supported by all versions of the software or hardware currently in use.For the most up-to-date information on product features, refer to your product release notes.

If a product does not function properly or does not function as described in this document, pleasecontact your EMC representative.


Special notice conventions

EMC uses the following conventions for special notices:

Note: Emphasizes content that is of exceptional importance or interest but does not relate to personalinjury or business/data loss.

Identifies content that warns of potential business or data loss.

Indicates a hazardous situation which, if not avoided, could result in minor ormoderate injury.

Indicates a hazardous situation which, if not avoided, could result in death orserious injury.

Indicates a hazardous situation which, if not avoided, will result in death or seriousinjury.

Where to get help

EMC support, product, and licensing information can be obtained as follows:

Product information—For documentation, release notes, software updates, or forinformation about EMC products, licensing, and service, go to EMC Online Support(registration required) at http://Support.EMC.com.

Troubleshooting—Go to EMC Online Support at http://Support.EMC.com. Afterlogging in, locate the applicable Support by Product page.

Technical support—For technical support and service requests, go to EMC CustomerService on EMC Online Support at http://Support.EMC.com. After logging in, locatethe applicable Support by Product page, and choose either Live Chat or Create a servicerequest. To open a service request through EMC Online Support, you must have avalid support agreement. Contact your EMC sales representative for details aboutobtaining a valid support agreement or with questions about your account.

Note: Do not request a specific support representative unless one has already been assigned toyour particular system problem.

Your comments

Your suggestions will help us continue to improve the accuracy, organization, and overallquality of the user publications.

Please send your opinion of this document to:

[email protected]


Preface

http://Support.EMC.com



1

Introduction

This document provides an overview of the performance statistics facilityused to monitor system statistics for VNX for file. Monitoring performance,protocol, and system statistics are essential to ensure the optimumperformance of VNX for file. Use the performance statistics facility togather and display statistical information in an easy-to-use format thatcan be customized for your needs. Statistics can be viewed as a summaryor as a detailed table that can be customized. Chapter 2 provides moredetails about VNX performance statistics and features.

This document is part of the VNX documentation set and is intended forus by system administrators and support engineers familiar with thecommand line interface. These procedures presume a basic knowledge ofVNX for file.

Topics included are:◆ System requirements on page 8◆ User interface choices on page 8◆ Related information on page 8


System requirements

Table 1 on page 8 describes the EMC® VNX® software, hardware, network, and storageconfigurations.

Table 1. System requirements

VNX 8.1 or laterSoftware

No specific hardware requirementsHardware

No specific network requirementsNetwork

No specific storage requirementsStorage

User interface choices

This document describes how to configure performance statistics by using the CommandLine Interface (CLI). You cannot use other VNX management applications to configureperformance statistics.

Related information

Specific information related to the features and functionality described in this document areincluded in the following documents:

◆ EMC VNX Command Line Interface Reference for File

◆ VNX for File man pages

◆ Parameters Guide for VNX for File

EMC VNX documentation on EMC Online Support

The complete set of EMC VNX series customer publications is available on EMC OnlineSupport. To search for technical documentation, go to http://Support.EMC.com. Afterlogging in to the website, click Support by Product and type VNX series in the Find aProduct text box. Then search for the specific feature required.

VNX wizards

Unisphere software provides wizards for performing setup and configuration tasks. TheUnisphere online help provides more details on the wizards.


Introduction


2

Concepts

The performance statistics facility gathers and displays statisticalinformation in an easy-to-use format that can be customized. Thisinformation can be used to diagnose performance issues affecting VNX.

You can view performance statistics as a:

◆ Summary of basic, CIFS, NFS, or cache statistics◆ Default table for each specified statistic◆ Table, where the format of the information displayed can be modified

When you view performance statistics as a table, idle rows (where noneof the values have changed from the previous sample) are not displayedin a sample output. However, the summary termination of a table willdisplay all rows, including idle ones.

Topics included are:◆ Performance statistics summaries on page 10◆ Performance statistics tables on page 12


Performance statistics summaries

Summary statistics provide an overview of high-level system statistics. The four choices fora summary report are basic, CIFS, NFS, and caches. For each summary, you can specify:

◆ Number of output samples by using the -count option◆ Number of seconds between intervals by using the -interval option◆ Appearance of a termination summary by using the -terminationsummary option◆ Print format by using the -format option◆ Sorted Sets based on field values by using the -sort option◆ Sorted Sets in ascending or descending order by using the -order option◆ Limited Set statistics of line output by using the -lines option◆ Display types by using the -type option◆ Table titles by using the -titles option

An overall summary is provided for every command. The default time interval for eachdisplay is 15 seconds. The interval can be changed by using the -interval option. The numberof polls can be changed by using the -count option.

The term kibibytes comes from the kilo binary and stands for 1024 in the ISO for InternationalSystem of Units.

The server_stats command

-list: The -list option in the server_stats command displays all defined statistics startingwith the statgroup names followed by statpaths and their types.

-info: The -info option displays the statgroup and statpath information.

-monitor [-action]: Enables, disables, or queries the state of the stats collection.

-monitor {statpath_name|statgroup_name}: Takes a comma-separated list of statpathand statgroup names. In cases where stats are available for multiple elements, the usercan specify an element name or use 'ALL-ELEMENTS' to refer to all elements at once.

Any duplicate statpath or statgroup names is consolidated and reported once. The optionsbelow are only applicable to Set and Correlated Set statpath names:

◆ [-sort <field_name>]: Sorts a Set based on <field_name> values.

◆ [-order {asc|desc}]: Sorted Sets can be ordered in ascending or descending order.

◆ [-lines <lines_of_output>]: Sets output can be limited to display the Set statistics<lines_of_output> lines.

Set statistics is not sorted if none of the above three options are specified. If some of theseoptions are specified with a Set statpath name, the omitted options default as follows:


Concepts

◆ -sort defaults to the element name

◆ -lines defaults to all

◆ -order default value depends on the .sort field. If the Set is being sorted on a numericfield, -order defaults to desc order; otherwise, it defaults to asc order. For sortingbased on the Set element name, -order always defaults to asc order.

Each Correlated Set comes defined with a default sort field and order. If some of theseoptions are specified with a Set statpath name, the omitted options default as follows:

◆ -sort default field is unique for each Correlated Set

◆ -lines always defaults to 20 for all Correlated Sets

◆ -order default value depends on the -sort field. If the Correlated Set is being sortedon a numeric field, -order defaults to desc order; otherwise, it defaults to asc order.Correlated Sets cannot be sorted on non numeric fields, including the Correlated Setelement ID.

-noresolve: The -noresolve option is a new server_stats option that prevents any idresolution of any kind. This includes: FS IDs, Volume IDs, MetaVolume IDs, Quota TreeIDs, IP Addresses, UIDs, and GIDs.

The nas_stats command

The nas_stats command allows the user to manage Statistics Groups. There are two typesof Statistics Groups: System-defined and User-defined groups. System-defined statisticsgroups are created as part of the installation (or upgrade) process. It creates a statisticsgroup and specifies what statpath names it includes. It also allows the nesting ofstatgroups by adding existing statgroups to new statgroups. Statgroup names can beused with the -info request. A statgroup name is limited to 255 characters. Space, slash,backward slash, quote, double quote, and comma are the illegal characters in it.

Basic statistics

The basic collection displays the CPU utilization for the time interval and the networkkibibytes sent, received, read, and written. The basic collection provides a simple pulseor health check of the system.

CIFS statistics

The cifs collection displays a summary of the CIFS protocol statistics, including read andwrite operations and active connections.

NFS statistics

The nfs collection displays a summary of the NFS protocol statistics, including read andwrite operations and active threads.

Performance statistics summaries 11

Concepts

Cache statistics

The caches collection displays a summary of statistics that are affecting cache, such asthe Directory Name Lookup Cache (DNLC) ratio, the open file cache hit, and the kernelbuffer cache hit ratio.

Performance statistics tables

When using the set option, statistics are presented in tabular format either by default modeor in a modifiable display. Multiple tables can be displayed by specifying table collectionsin a comma-separated list. Available table collections are:

◆ Network device statistics (netDevices-std)◆ Basic volume statistics (diskVolumes-std)◆ Metavolume or file system statistics (metaVolumes-std)◆ cifsOps-std◆ nfsOps-std

Each statistics group displays statistics relative to the network, volume, or operation asspecified. For each table, you can specify the:

◆ Number of lines of output, by using the -count option◆ Number of seconds between intervals, by using the -interval option◆ Appearance of a termination summary, by using the -terminationsummary option◆ Print format, by using the -format option◆ Display types, by using the -type option◆ Statistic titles, by using the -titles option

An overall summary is provided for every command. The time interval for each display is15 seconds by default, but can be changed by using the -interval option. The number of pollscan be changed by using the -count option.

Network device statistics (netDevices-std)

The network device statistics reported for each interval are the name of the device, thenetwork kibibytes and packets sent and received per second, and the input and outputerrors encountered.

Basic volume statistics (diskVolumes-std)

The basic volume statistics reported for each interval are the name and queue depth ofthe disk volume, the number of kibibytes read and sent per second, and the number andsize of read and write operations.


Concepts

Metavolume or file system statistics (metaVolumes-std)

The mounted file systems statistics reported for each interval are the name and associatedmetavolume, and the number, average size, and percentage of total metavolume readand write requests.

Per Operation CIFS Statistics (cifsOps-std)

The per operation CIFS statistics reported for each interval are the name of the CIFSoperation, the number of calls to this operation, the percent total, and the average timein microseconds consumed by the call.

Per Operation NFS statistics (nfsOps-std)

The per operation NFS statistics reported for each interval are the name of the NFSoperation, the number of calls to this operation, the percent total, and the average timein microseconds consumed by the call.

Performance statistics tables 13

Concepts


Concepts

3

Managing

The tasks to manage performance statistics are as follows:◆ Display performance statistics summaries on page 16◆ Display performance statistics sets on page 23◆ Display Correlated Statistics Information on page 30◆ Display statistics for Continuous Monitoring on page 71◆ Sort by field name on page 74


Display performance statistics summaries

Summary statistics can be reported for basic system statistics (default), CIFS, NFS, or cache.You can specify how the statistics are reported by using the -count, -interval,-terminationsummary, -format, or -titles options.

The tasks to display performance statistics summaries include:

◆ Display a summary of system statistics on page 17◆ Display a summary of CIFS protocol statistics on page 20◆ Display a summary for NFS protocol statistics on page 21◆ Display a summary statistics for caches on page 22◆ Display NFS statistics correlated by filesystem and NFS operation attributes on page 35◆ Display NFS statisitics correlated by a single filesystem on page 38◆ Display NFS statistics correlated by a specific filesystem and a specific client on page 39◆ Display NFS statistics correlated by filesystem for a specific client and operation on page

40


Managing

Display a summary of system statistics

A basic health check displays CPU utilization, the number of network kibibytes sent andreceived, and the number of system kibibytes read and written.

Action

To display the basic-std group, use this command syntax:

$ server_stats <movername> -monitor basic-std -interval <seconds> -count<count> -type {rate|diff|accu}

where:

<movername> = name of the Data Mover

<seconds> = number of seconds in each interval

<count> = number of reports

Example:

To display the basic-std group by indicating the rate of change since the previous sample, type:

$ server_stats server_2 -monitor basic-std -interval 5 -count 5 -type rate

Output

server_2 CPU Network Network dVol dVolTimestamp Util In Out Read Write

% KiB/s KiB/s KiB/s KiB/s02:53:09 33 88618 729 9988 8973002:53:11 61 142057 1087 18632 16707602:53:13 29 98110 762 8976 7859902:53:15 46 109783 836 14288 12571702:53:17 34 111847 886 10652 95719

server_2 CPU Network Network dVol dVolSummary Util In Out Read Write

% KiB/s KiB/s KiB/s KiB/sMinimum 29 88618 729 8976 78599Average 41 110083 860 12507 111368Maximum 61 142057 1087 18632 167076

Note

Column definitions:Timestamp - Time the poll was taken.CPU Util - CPU utilization in percentage in this interval.Network In KiB/s - Network kibibytes received over all network interfaces.Network Out KiB/s - Network kibibytes sent over all network interfaces.dVol Read KiB/s - Storage kibibytes received from all server-storage inter-faces.dVol Write Kib/s - Storage kibibytes sent to all server-storage interfaces.

Display performance statistics summaries 17

Managing

Action



where:




Example:

To display the basic-std group by indicating the change in value since the previous sample, type:

$ server_stats server_2 -monitor basic-std -interval 5 -count 5 -type diff

Output

server_2 CPU Network Network dVol dVolTimestamp Util In KiB Out KiB Read KiB Write

% diff diff diff KiB diff02:53:29 46 267660 2136 26128 23265402:53:31 38 200668 1543 23144 21118202:53:33 46 226761 1749 26488 23055802:53:35 48 246921 1876 28720 25595702:53:37 40 212353 1673 23016 210573

server_2 CPU Network Network dVol dVolSummary Util In KiB Out KiB Read KiB Write

% diff diff diff KiB diffMinimum 38 200668 1543 23016 210573Average 44 230873 1795 25499 228185Maximum 48 267660 2136 28720 255957

Note

Column definitions:Timestamp - Time the poll was taken.CPU Util % - CPU Utilization utilized in percentage in this interval.Network In KiB diff - Network kibibytes received over all network interfacesper differential value.Network Out KiB diff - Network kibibytes sent over all network interfacesper differential value.dVol Read KiB diff - Storage kibibytes received from all server-storageinterfaces per differential value.dVol Write KiB diff - Storage kibibytes sent to all server-storage inter-faces per differential value.

Action



Managing

Action


where:




Example:

To display the basic-std group by indicating the change in value since the first sample, type:

$ server_stats server_2 -monitor basic-std -interval 5 -count 5 -type accu

Output

server_2 CPU Network Network dVol dVolTimestamp Util In Out Read Write

% KiB KiB KiB KiB02:53:48 42 236257 1880 25504 22483202:53:50 54 505640 3983 55760 50053802:53:52 29 686282 5377 74096 66249402:53:54 46 922765 7183 101704 90881302:53:56 41 1125518 8777 126640 1134362

server_2 CPU Network Network dVol dVolSummary Util In Out Read Write

% KiB KiB KiB KiBMinimum 29 236257 1880 25504 224832Average 42 695293 5440 76741 686208Maximum 54 1125518 8777 126640 1134362

Note

Column definitions:Timestamp - Time the poll was taken.CPU Util - CPU utilization in percentage in this interval.Network In KiB - Network kibibytes received over all network interfacesper accumulated value.Network Out KiB - Network kibibytes sent over all network interfaces peraccumulated value.dVol Read KiB - Storage kibibytes received from all server-storage inter-faces per accumulated value.dVol Write KiB - Storage kibibytes sent to all server-storage interfacesper accumulated value.


Managing

Display a summary of CIFS protocol statistics

Action

To display a summary of CIFS protocol statistics, use this command syntax:

$ server_stats <movername> cifs-std -interval <seconds> -count <count>

where:




Example:

To display a summary of CIFS protocol statistics for five counts every 3 seconds, type:

$ server_stats server_2 cifs-std -interval 3 -count 5

Output

server_2 CIFS CIFS CIFS CIFS CIFS CIFS CIFS CIFS CIFSAvg Avg

Timestamp Total Read Read Read Write Write Write Connections OpenSize Size Files

Ops/s Ops/s KiB/s Bytes Ops/s KiB/s Bytes09:57:15 1687 0 0 0 1586 6344 4096 2 209:57:18 1588 0 0 0 1487 5949 4096 2 209:57:21 1611 0 0 0 1510 6041 4096 2 209:57:24 1536 0 0 0 1435 5740 4096 2 209:57:27 1642 0 0 0 1541 6163 4096 2 2

Note

Column definitions:Timestamp — Time the poll was takenCIFS Total Ops/s — Total number of operationsCIFS Read Ops/s — CIFS read operations per second in the intervalCIFS Read KiB/s – CIFS read data response in kibibytes per secondCIFS Avg Size Read Bytes — Average read data response during the sampleCIFS Write Ops/s — CIFS write operations per secondCIFS Write KiB/s – CIFS write data response in kibibytes per secondCIFS Avg Write Size Bytes — Average write data size during the sampleCIFS connections — Number of CIFS protocol connections at the time of thesampleCIFS Open Files — Number of open CIFS files at the time of the sample


Managing

Display a summary for NFS protocol statistics

Action

To display five iterations of the summary for NFS protocol statistics, use this command syntax:

$ server_stats <movername> -monitor nfs-std -i <seconds> -c <count>

where:




Example:

To display five iterations of the summary for NFS protocol statistics with a three second interval, type:

$ server_stats server_2 -monitor nfs-std -i 3 -c 5

Output

server_2 Total NFS NFS NFS Avg NFS NFS NFS Avg NFSTimestamp NFS Read Read Read Size Write Write Write Size Active

Ops/s Ops/s KiB/s Bytes Ops/s KiB/s Bytes Threads02:55:00 441 0 0 - 446 231457 531727 2002:55:03 466 0 0 - 476 237714 511420 002:55:06 465 0 0 - 478 244053 522826 002:55:09 463 0 0 - 475 244736 527229 1002:55:12 456 0 0 - 469 244565 534356 44

server_2 Total NFS NFS NFS Avg NFS NFS NFS Avg NFSSummary NFS Read Read Read Size Write Write Write Size Active

Ops/s Ops/s KiB/s Bytes Ops/s KiB/s Bytes ThreadsMinimum 441 0 0 - 446 231457 511420 0Average 458 0 0 - 469 240505 525512 15Maximum 466 0 0 - 478 244736 534356 44

Note

Column definitions:Timestamp - Time the poll was taken.Total NFS Ops/s - Total number of operations per second.NFS Read Ops/s - NFS read operations per second in the interval.NFS Read KiB/s - NFS read data response in kibibytes per second.NFS Avg Read Size Bytes - Average read data response.NFS Write Ops/s - NFS write operations per second.NFS Write KiB/s - NFS write data response in kibibytes per second.NFS Avg Write Size Bytes - Average write data size.NFS Active Threads - Number of NFS active threads.


Managing

Display a summary statistics for caches

Action

To display iterations of the summary statistics for caches, use this command syntax:

$ server_stats <movername> -monitor caches-std -i <seconds> -c <count>

where:




Example:

To display five iterations of the summary statistics for caches with a three second interval, type:

$ server_stats server_2 -monitor caches-std -i 3 -c 5

Output

server_2 DNLC OF Cache BufferTimestamp Hit Hit Cache

Ratio % Ratio % Hit %02:55:26 - 100 7102:55:29 - 100 7202:55:32 - 100 7302:55:35 - 100 7302:55:38 - 100 72

server_2 DNLC OF Cache BufferSummary Hit Hit Cache

Ratio % Ratio % Hit %Minimum - 100 71Average - 100 72Maximum - 100 73

Note

Column definitions:Timestamp - Time the poll was taken.DNLC Hit Ratio % - Directory Name Lookup Cache (DNLC) hit ratio.OF Cache Hit Ratio % - Open file cache hit ratio.Buffer Cache Hit % - Kernel buffer cache hit ratio.


Managing

Display performance statistics sets

The tasks to display performance statistics sets include:

◆ Display network device statistics on page 24◆ Display basic volume statistics on page 26◆ Display meta volume or file system statistics on page 28◆ Display CIFS operations statistics on page 29◆ Display NFS operations statistics on page 30

Display performance statistics sets 23

Managing

Display network device statistics

The netDevices-std reports the Network devices statistics table. The table output can bealtered using the –sort, -lines, or –order table options.

Action

To display a table of network statistics, use this command syntax:

$ server_stats <movername> -monitor netDevices-std -interval <seconds> -count<count>

where:


<seconds> = number of seconds for each interval


Example:

To display the netDevices-std statistics group with a three second interval, type:

$ server_stats server_2 -monitor netDevices-std -i 3 -c 3

Output

server_2 device Network Network Network Network Network NetworkTimestamp In In In Out Out Out

Pkts/s Errors/s KiB/s Pkts/s Errors/s KiB/s02:55:52 mge0 2 0 0 1 0 0

mge1 17 0 23 9 0 1cge0 3593 0 26566 2289 0 203cge1 6912 0 50206 4444 0 378cge2 3637 0 25570 2342 0 209

02:55:55 mge0 0 0 0 0 0 0mge1 7 0 9 4 0 0cge0 3444 0 24744 2252 0 204cge1 7415 0 53354 4721 0 400cge2 3913 0 27796 2502 0 222

02:55:58 mge0 2 0 0 2 0 0mge1 32 0 39 19 0 2cge0 4029 0 29334 2594 0 230cge1 7461 0 54030 4791 0 406cge2 3902 0 27319 2505 0 223


Managing

Output

server_2 device Network Network Network Network Network NetworkSummary In In In Out Out Out

Pkts/s Errors/s KiB/s Pkts/s Errors/s KiB/sMinimum mge0 0 0 0 0 0 0

mge1 7 0 9 4 0 0cge0 3444 0 24744 2252 0 203cge1 6912 0 50206 4444 0 378cge2 3637 0 25570 2342 0 209cge3 0 0 0 0 0 0

Average mge0 1 0 0 1 0 0mge1 19 0 24 11 0 1cge0 3689 0 26882 2378 0 213cge1 7263 0 52530 4652 0 395cge2 3817 0 26895 2450 0 218cge3 0 0 0 0 0 0

Maximum mge0 2 0 0 2 0 0mge1 32 0 39 19 0 2cge0 4029 0 29334 2594 0 230cge1 7461 0 54030 4791 0 406cge2 3913 0 27796 2505 0 223cge3 0 0 0 0 0 0

Note

Column Definition:Timestamp - Time the poll was taken.Device - Name of the network device.Network In Pkts/s - Network packets received per second.Network In Errors/s - Network input errors encountered per second.Network In KiB/s - Network kibibytes received per second.Network Out Pkts/s - Network packets sent per second.Network Out Errors/s - Network output errors encountered per second.Network Out KiB/s - Network kibibytes sent per second.


Managing

Display basic volume statistics

-diskVolumes-std reports the Basic Volumes table. The table output can be altered using-sort, -lines, or -order table options.

Action

To display the diskVolumes-std statistics group, use this command syntax:

$ server_stats <movername> -m diskVolumes-std -interval <seconds> -count<count> -terminationsummary {no|yes|only}

where:




Example:

To display the diskVolumes-std statistics group without the summary and with a five second interval, type:

$ server_stats server_2 -m diskVolumes-std -i 5 -c 3 -te no

Output

server_2 dVol Queue Read Read Avg Read Write Write Avg Write Util%Timestamp Depth Ops/s KiB/s Size Ops/s KiB/s Size

Bytes/s Bytes/s02:58:09 NBS1 0 0 3 8192 1 7 6827 0

root_ldisk 0 0 0 - 461 490 1090 47d7 0 113 904 8192 530 19619 37881 83d11 0 249 1995 8192 431 11640 27634 91d8 0 68 547 8192 372 11472 31607 79d12 33 424 3389 8192 609 20045 33705 99d9 0 36 291 8192 592 20339 35161 67d13 0 333 2664 8192 347 11925 35158 93d10 0 24 189 8192 385 11896 31668 63d14 36 573 4581 8192 454 20173 45468 100

02:58:12 root_ldisk 0 0 0 - 401 462 1182 44NBS6 0 0 0 - 1 3 3072 0d7 0 78 624 8192 388 13851 36523 7011 0 216 1728 8192 470 11147 24268 84d8 0 51 411 8192 333 10672 32850 85d12 0 301 2408 8192 483 14411 30531 98


Managing

Output

server_2 dVol Queue Read Read Avg Read Write Write Avg Write Util%Timestamp Depth Ops/s KiB/s Size Ops/s KiB/s Size

Bytes/s Bytes/sd9 0 24 192 8192 422 14285 34691 50d13 0 290 2317 8192 340 10920 32856 87d10 0 19 152 8192 346 10944 32389 70d14 47 407 3259 8192 342 14288 42822 100

02:58:15 NBS1 0 0 0 - 3 1 512 0root_ldisk 0 0 0 - 409 454 1135 43NBS5 0 0 0 - 9 83 9070 1d7 0 122 976 8192 471 20179 43839 90d11 1 144 1149 8192 225 6608 30118 94d8 2 33 261 8192 229 6515 29131 48d12 41 424 3395 8192 666 20632 31722 93d9 0 44 355 8192 577 20848 36999 82d13 2 185 1483 8192 201 6768 34423 93d10 0 13 101 8192 238 6789 29252 36d14 0 583 4667 8192 521 21131 41505 95

Note

Column Definition:Timestamp - Time the poll was taken.dVol - Name of the disk volume.Queue Depth - Queue depth of the disk volume.Read Ops/s - Number of read operations per second.Read KiB/s - Kibibytes read per second.Avg Read Size Bytes - Average size in bytes of read requests per second.Write Ops/s - Number of write operations per second.Write KiB/s - Kibibytes written per second.Avg Write Size Bytes - Average size in bytes for write requests per second.Util % - Disk utilized in percetage.


Managing

Display meta volume or file system statistics

metaVolumes-std reports the Meta Volumes statistics table. The table output can be alteredusing the -sort, -lines, or -order options.

Action

To display the metaVolumes-std statistics group without the summary, use this command syntax:

$ server_stats <movername> -m metaVolumes-std -interval <seconds> -count<count> -terminationsummary {no|yes|only}

where:




Example:

To display the metaVolumes-std statistics group without the summary and with a five second interval, type:

$ server_stats server_2 -m metaVolumes-std -i 5 -c 3 -te no

Output

server_2 MetaVol Read Read Avg Read Read Write Write Avg Write WriteTimestamp Requests/s KiB/s Size Ops/s KiB/s Size Ops/s

Bytes Requests/s Bytes02:58:37 ufs_2 347 2776 8192 347 140 3544 172208 140

ufs_0 315 2517 8192 315 148 1427 147916 148ufs_1 654 5229 8192 654 313 5512 148895 313

02:58:40 ufs_2 396 3166 8192 396 195 27326 143200 195ufs_0 431 3446 8192 431 187 29574 162161 187ufs_1 408 3262 8192 408 159 27782 178784 159

02:58:43 ufs_2 522 4174 8192 522 219 35546 166238 219ufs_0 492 3933 8192 492 222 33356 153886 222ufs_1 467 3736 8192 467 188 31955 173819 188

Note

Column Definition:MetaVol - Name of the meta volume associated with the file system.Read Request/s - Number of read requests per second to this volume.Read KiB/s - Kibibytes read per second.Avg Read Size Bytes - Average size for read requests to this volume.Read Ops/s - Number of read operations per second.Write Requests/s - Number of write requests per second.Write KiB/s - Number of kibibytes written per second to this volume.Avg Write Size Bytes - Average size in bytes for write requests.Write Ops/s - Number of write operations per second.


Managing

Display CIFS operations statistics

The cifsOps-std reports the CIFS operations statistics table. The table output can be alteredusing the –sort, -lines, or –order table options.

Action

To display the cifsOps-std statistics group without the summary, use this command syntax:

$ server_stats <movername> -m cifsops-std -interval <seconds> -count <count>-terminationsummary {no|yes|only}

where:




Example:

To display the cifsOps-std statistics group without the summary and with a five second interval, type:

$ server_stats server_2 -m cifsops-std -i 5-c 3 -te no

Output

server_2 SMB Operation Op Min Max AvgTimestamp Calls/s uSec uSec uSec/call02:57:24 SMB1_Close 56 45 552768 25299

SMB1_WriteX 1360 29 1618776 161125SMB1_CreateNTX 46 51 458090 971

02:57:27 SMB1_Close 130 45 568291 16814SMB1_WriteX 1627 29 1618776 182622SMB1_CreateNTX 147 51 458090 276

02:57:30 SMB1_Close 50 45 568291 29992SMB1_WriteX 1615 29 1618776 151924SMB1_CreateNTX 37 51 458090 2850


Managing

Display NFS operations statistics

-nfsOps-std reports the NFS operations statistics table. The table output can be altered using-sort, -lines, or -order table options.

Action

To display the nfsOps-std statistics group, use this command syntax:

$ server_stats <movername> -m nfsops-std -interval <seconds> -count <count>-terminationsummary {yes|no}

where:




Example:

To display the nfsOps-std statistics group without the summary and with a five second interval, type:

$ server_stats server_2 -m nfsops-std -i 5 -c 3 -te no

Output

server_2 NFS Op NFS NFS NFS NFS Op %Timestamp Op Op Op

Calls/s Errors/s uSec/call03:18:21 v3Read 23442 0 63846 50

v3Write 23372 0 99156 5003:18:24 v3Read 23260 0 65756 50

v3Write 23243 0 101135 5003:18:27 v3Read 23385 0 66808 50

v3Write 23323 0 102201 50

Note

Column Definition:Timestamp - Time the poll was taken.NFS Op - Name of the NFS operation.NFS Op Calls/s - Number of calls to this NFS operation per second.NFS Op Errors/s - Number of times the NFS operation failed per second.NFS Op uSec/Call - Average time in microseconds consumed per call.NFS Op % - Percent of total NFS calls attributed to this operation.

Display Correlated Statistics Information

The tasks to display correlated statistics information include:

◆ View Correlated Statistics Information on page 32


Managing

◆ Display Correlated Statistics list for CIFS on page 34◆ Monitor CIFS Client Statistics on page 41◆ Monitor NFS Client Statistics on page 43◆ Monitor CIFS User Statistics on page 44◆ Monitor CIFS Server Statistics on page 45◆ Monitor File system Statistics on page 47◆ Monitor NFS User Statistics on page 50◆ Monitor Store Volume Statistics on page 52◆ Display NFS User Information on page 53◆ Monitor NFS Group Statistics on page 54◆ Monitor NFS Export Statistics on page 55◆ Monitor files per Quota Tree statistics on page 57◆ The -noresolve option on page 69

Display Correlated Statistics Information 31

Managing

View Correlated Statistics Information

Action

To view Correlated Statistics information for CIFS, use this command syntax:

$ server_stats movername-i cifs.user

where:


Example:

To view Correlated Statistics information for CIFS, type:

$ server_stats server_2 -i cifs.user

Output

server_2 :name = cifs.userdescription = Per CIFS client statisticstype = Correlated Setmember_stats = cifs.user.ALL-ELEMENTS.totalCalls,cifs.user.ALL-ELE-MENTS.readCalls,

cifs.user.ALL-ELEMENTS.writeCalls,cifs.user.ALL-ELE-MENTS.suspectCalls,

cifs.user.ALL-ELEMENTS.totalBytes,cifs.user.ALL-ELE-MENTS.readBytes,

cifs.user.ALL-ELEMENTS.writeBytes,cifs.user.ALL-ELE-MENTS.avgTime,

cifs.user.ALL-ELEMENTS.server,cifs.user.ALL-ELE-MENTS.clientmember_elements =member_of =

Action

To view Correlated Statistics information for NFS, use this command syntax:

$ server_stats movername -i nfs.user

where:

movername = name of the Data Mover

Example:

To view Correlated Statistics information for NFS, type:

$ server_stats server_2 -i nfs.user


Managing

Output

server_2 :name = nfs.userdescription = Per NFS client statisticstype = Correlated Setmember_stats = nfs.user.ALL-ELEMENTS.totalCalls,nfs.user.ALL-ELE-MENTS.readCalls,

nfs.user.ALL-ELEMENTS.writeCalls,nfs.user.ALL-ELEMENTS.sus-pectCalls,

nfs.user.ALL-ELEMENTS.totalBytes,nfs.user.ALL-ELE-MENTS.readBytes,

nfs.user.ALL-ELEMENTS.writeBytes,nfs.user.ALL-ELEMENTS.avg-Timemember_elements =member_of =

Action

To view Correlated Statistics information for Store Volume, use this command syntax:

$ server_stats movername -i store.volume

where:


Example:

To view Correlated Statistics information for Store Volume, type:

$ server_stats server_2 -i store.volume

Output

server_2 :name = store.volumedescription = Disk Volume statistics correlated by File Systemtype = Setmember_stats = store.volume.ALL-ELEMENTS.fileSystemmember_elements = store.volume.d21.fileSystem,store.volume.d15.fileSys-tem,store.volume.d38.fileSystemmember_of =

Action

To view Correlated Statistics information for Store Volume, use this command syntax:

$ server_stats movername -i store.volume.ALL-ELEMENTS.fileSystem

where:


Example:

To view Correlated Statistics information for Store Volume, type:

$ server_stats server_2 -i store.volume.ALL-ELEMENTS.fileSystem


Managing

Output

server_2 :name = store.volume.ALL-ELEMENTS.fileSystemdescription = Per file system tree statisticstype = Correlated Setmember_stats = store.volume.ALL-ELEMENTS.fileSystem.ALL-ELEMENTS.total-Blocks,

store.volume.ALL-ELEMENTS.fileSystem.ALL-ELEMENTS.read-Blocks,

store.volume.ALL-ELEMENTS.fileSystem.ALL-ELEMENTS.write-Blocks,

store.volume.ALL-ELEMENTS.fileSystem.ALL-ELEMENTS.total-Bytes,

store.volume.ALL-ELEMENTS.fileSystem.ALL-ELEMENTS.read-Bytes,

store.volume.ALL-ELEMENTS.fileSystem.ALL-ELEMENTS.write-Bytesmember_elements =member_of = store.volume

Display Correlated Statistics list for CIFS

Action

To display a list of Correlated Statistics for CIFS user, use this command syntax:

$ server_stats movername -info cifs.user

where:


Example:

To display a list of Correlated Statistics for CIFS user, type:

$ server_stats server_2 -info cifs.user

Output

server_2 :

name = cifs.userdescription = Per CIFS user statisticstype = Correlated Setmember_stats = cifs.user.ALL-ELEMENTS.totalCalls,cifs.user.ALL-ELE-MENTS.readCalls,cifs.user.ALL-ELEMENTS.writeCalls,cifs.user.ALL-ELEMENTS.sus-pectCalls,cifs.user.ALL-ELEMENTS.totalBytes,cifs.user.ALL-ELEMENTS.read-Bytes,cifs.user.ALL-ELEMENTS.writeBytes,cifs.user.ALL-ELEMENTS.avgTimemember_elements =member_of = cifs


Managing

Display NFS statistics correlated by filesystem and NFS operation attributes

Action

To display five iterations of the nfs.filesystem statistics, use this command syntax:

$ server_stats <movername> -i <seconds>-c <count> -m nfs.filesystem

where:




Example:

To display five iterations of the summary for NFS filesystem statistics with a one second interval, type:

server_stats server_2 -i 1 -m nfs.filesystem


Managing

Output


Managing

Output

server_2 Filesystem Client NFS Op NFS Op NFSTimestamp Avg Op

uSecs/Call Calls/s16:50:42 ufs_5 id=10.103.11.18 v3Write 522 116:50:4316:50:44 ufs_5 l18.perf1.com v3Lookup 13 1116:50:45 ufs_5 l18.perf1.com v3Write 1810 17

v3Read 49 133v3Lookup 10 180

ufs_4 l17.perf1.com v3Write 1311 18v3Read 47 115v3Lookup 10 220

16:50:46 ufs_5 l18.perf1.com v3Write 7026 137v3Read 52 248

ufs_4 l17.perf1.com v3Write 6347 131v3Read 121 354

ufs_3 id=10.103.11.16 v3Write 297 122v3Read 91 390

16:50:47 ufs_5 l18.perf1.com v3Write 6701 161ufs_4 l17.perf1.com v3Write 4754 159

v3Read 47 39ufs_3 l16.perf1.com v3Write 129 160

v3Read 123 38

server_2 Filesystem Client NFS Op NFS Op NFSSummary Avg Op

uSecs/Call Calls/sMinimum ufs_5 l18.perf1.com v3Write 522 1



ufs_1ufs_2ufs_0ufs_3 l16.perf1.com v3Write 129 122

v3Read 91 38root_fs_commonroot_fs_2

Average ufs_5 l18.perf1.com v3Write 4015 79v3Read 50 190v3Lookup 12 95




Maximum ufs_5 l18.perf1.com v3Write 7026 161v3Read 52 248v3Lookup 13 180

ufs_4 l17.perf1.com v3Write 6347 159


Managing

Output




Note

Column definitions:Timestamp — Time the poll was takenFile system — Name of the file systemClient — Name of the clientNFS Op — Name of the NFS operationNFS Op uSecs/Call — Average time in microseconds consumed per callNFS Op Calls/s — Number of calls to this NFS operation per second

Display NFS statisitics correlated by a single filesystem

Action

To display a summary of NFS filesystem statistics, use this command syntax:

$ server_stats <movername> -m nfs.filesystem.ufs_4

where:


Example:

To display a summary of NFS filesystem statistics, type:

$ server_stats server_2 -m nfs.filesystem.ufs_4


Managing

Output


uSecs/Call Calls/s02:46:00 ufs_4 l23.perf1.com v3Write 2569 132

v3Create 38 002:46:15 ufs_4 l23.perf1.com v3Write 3313 132


uSecs/Call Calls/sMinimum ufs_4 l23.perf1.com v3Write 2569 132

v3Create 38Average ufs_4 l23.perf1.com v3Write 2941 132

v3Create 38 0Maximum ufs_4 l23.perf1.com v3Write 3313 132

v3Create 38 0123 390

Note


Display NFS statistics correlated by a specific filesystem and a specificclient

Action

To display a summary of NFS filesystem statistics correlated by a specific filesystem and specific client, use this commandsyntax:

$ server_stats <movername> -i<seconds> -mnfs.filesystem.ufs_4.client.10.103.11.23

where:



Example:

To display a summary of NFS filesystem statistics correlated by a specific filesystem and specific client, with two secondsinterval, type:

$ server_stats server_2 -i 2 -m nfs.filesystem.ufs_4.client.10.103.11.23


Managing

Output


uSecs/Call Calls/s02:41:36 ufs_4 l23.perf1.com v3Write 2083 12002:41:38 ufs_4 l23.perf1.com v3Write 4318 13202:41:40 ufs_4 l23.perf1.com v3Write 2660 116


uSecs/Call Calls/sMinimum ufs_4 l23.perf1.com v3Write 2083 116Average ufs_4 l23.perf1.com v3Write 3020 123Maximum ufs_4 l23.perf1.com v3Write 4318 132

Note


Display NFS statistics correlated by filesystem for a specific client andoperation

Action

To display a summary of NFS filesystem statistics for a specific client and operation, use this command syntax:

$ server_stats <movername> -i<seconds> -mnfs.filesystem.ufs_4.client.10.103.11.23.op.v3Write

where:



Example:

To display a summary of NFS filesystem statistics for a specific client and operation, use this command syntax:

$ server_stats server_2 -i 2 -m nfs.filesystem.ufs_4.client.10.103.11.23.op.v3Write


Managing

Output


uSecs/Call Calls/s02:42:39 ufs_4 l23.perf1.com v3Write 2335 12302:42:41 ufs_4 l23.perf1.com v3Write 4836 13402:42:43 ufs_4 l23.perf1.com v3Write 5093 14202:42:45 ufs_4 l23.perf1.com v3Write 2129 142server_2 Filesystem Client NFS Op NFS Op NFSSummary Avg Op

uSecs/Call Calls/sMinimum ufs_4 l23.perf1.com v3Write 2129 123Average ufs_4 l23.perf1.com v3Write 3598 135

Maximum ufs_4 l23.perf1.com v3Write 5093 14

Note


Monitor CIFS Client Statistics

The cifs.client statistics provide cifs read and write statistics by call and bytes correlated toCIFS users.

Action

To monitor CIFS client statistics, use this command syntax:

$ server_stats movername -i interval-m cifs.client -l interval

where:


Example:

To monitor CIFS client statistics, type:

$ server_stats server_2 -i 2 -m cifs.client -l 10


Managing

Output

server_2 IP address CIFS CIFS CIFS CIFS CIFS CIFS CIFSCIFS

Timestamp Total Read Write Suspi- Total Read WriteAvg

ciousOps/s Ops/s Ops/s Ops KiB/s KiB/s KiB/s

uSecs/call09:46:49 id=10.103.11.105_20107 28 0 28 0 1627 0 162733106

id=10.103.11.105_20363 27 0 27 0 1533 0 153327774

id=10.103.11.105_18571 26 0 26 0 1470 0 147029917

id=10.103.11.105_13707 25 0 25 0 1439 0 143938483

id=10.103.11.105_17803 25 0 25 0 1466 0 146646276

id=10.103.11.105_13195 23 0 23 0 1340 0 134028742

id=10.103.11.105_16267 23 0 22 0 1277 0 127737569

id=10.103.11.105_16523 23 0 23 0 1340 0 134028957

id=10.103.11.105_17291 23 0 22 0 1277 0 127734895

id=10.103.11.105_19339 23 0 23 0 1313 0 131332875

09:46:51 p24.perf1.com_15499 27 0 27 0 1568 0 156827840

p24.perf1.com_16523 26 0 26 0 1507 0 150734868

p24.perf1.com_19595 26 0 26 0 1507 0 150727609

p24.perf1.com_20875 25 0 25 0 1441 0 144127752

p24.perf1.com_14987 25 0 25 0 1410 0 141034752

p24.perf1.com_15243 24 0 24 0 1348 0 134828965

p24.perf1.com_19083 23 0 23 0 1317 0 131739723

p24.perf1.com_19339 23 0 22 0 1256 0 125629662

p24.perf1.com_20619 23 0 23 0 1317 0 131733112

p24.perf1.com_13195 23 0 21 0 1194 0 119437954


Managing

Monitor NFS Client Statistics

Action

To monitor the NFS client statistics, use this command syntax:

$ server_stats movername -monitor nfs.client -te no -c seconds

where:


seconds = number of seconds in each interval

Example:

To monitor the NFS client statistics, type:

$ server_stats server_2 -monitor nfs.client -te no -c 2

Output

server_2 Client NFS NFS NFS NFS NFS NFS NFS NFSTimestamp Total Read Write Susp- Total Read Write Avg

Ops/s Ops/s Ops/s -cious KiB/s KiB/s KiB/s uSec/Ops call

15:44:04 10.103.11.7 531 0 526 0 269175 0 269175 3835client8 546 0 535 0 274057 0 274057 3482client9 181 0 181 0 92877 0 92877 35068

15:44:19 client8 2161 0 2145 0 1098225 0 1098225 3806client7 2198 0 2181 0 1116790 0 1116790 3770client9 376 0 376 0 192508 0 192508 49141


Managing

Monitor CIFS User Statistics

The cifs.user provides cifs read and write statistics by call and bytes correlated by cifs users. However, it is correlated to user as opposed to IP address.

The statistics contain the following information:

1. Total CIFS Ops/S

2. read Ops/S

3. write Ops/S

4. Suspicious Ops Diff

5. Total KiB/Sec

6. Read KiB/Sec

7. Write Ki B/Sec

8. avgTime

The Default sort field is Total Ops/S.

Action

To monitor CIFS user statistics, use this command syntax:

$ server_stats movername -i interval-m cifs.user

where:


Example:

To monitor CIFS user statistics, type:

$ server_stats server_2 -i 5 -m cifs.user


Managing

Output

server_2 User name CIFS CIFS CIFS CIFS CIFS CIFS CIFS CIFS CIFSCIFS

Timestamp Total Read Write Susp- Total Read Write Avg ServerClient

Op/s Op/s Op/s -cious KiB/s uSecs/ NameName

Ops call14:38:52 TESTDOMAIN\

admin 1 1 0 0 0 0 0 135 PITTA-P27

DM2-0

14:38:57 TESTDOMAIN\admin 11 11 0 0 1 1 0 2257 PITTA-

P27DM2-0

14:39:07 TESTDOMAIN\admin 0 0 0 0 0 0 0 22 PITTA-

P27DM2-0

server_2 User name CIFS CIFS CIFS CIFS CIFS CIFS CIFS CIFS CIFSCIFSTimestamp Total Read Write Susp- Total Read Write Avg ServerClient

Op/s Op/s Op/s -cious KiB/s uSecs/ NameName

Ops callMinimum TESTDOMAIN\

admin 0 0 0 0 0 0 0 22- -Average TESTDOMAIN\

admin 4 4 0 0 0 0 0 634- -Maximum TESTDOMAIN\

admin 11 11 0 0 1 1 0 2257- -

Monitor CIFS Server Statistics

The cifs.server displays same data as cifs.client does. However, it is correlated to CIFS servername as opposed to CIFS client's IP address for CIFS client.

This statistics provides the following information:

1. Total CIFS Ops/S

2. read Ops

3. write Ops


5. Total KiB/Sec


Managing

6. Read KiB/Sec

7. Write KiB/Sec

8. avgTime

Action

To monitor CIFS server statistics, use this command syntax:

$ server_stats movername-m cifs.server

where:


Example:

To monitor CIFS server statistics, type:

$ server_stats server_2 -m cifs.server

Output

server_2 Server name CIFS CIFS CIFS CIFS CIFS CIFS CIFS CIFS

Timestamp Total Read Write Susp- Total Read Write AvgOp/s Op/s Op/s -cious KiB/s uSecs/

Ops call

02:50:29 RAVEN-DM2-2 2176 0 1957 0 0 0 0 135

14:38:57 TESTDOMAIN\admin 11 11 0 0 1 1 0 2257

14:39:02

14:39:07 TESTDOMAIN\admin 0 0 0 0 0 0 0 22

14:39:22

server_2 Server name CIFS CIFS CIFS CIFS CIFS CIFS CIFS CIFS

Timestamp Total Read Write Susp- Total Read Write Avg

Op/s Op/s Op/s -cious KiB/s uSecs/

Ops call

Minimum TESTDOMAIN\admin 0 0 0 0 0 0 0 22

Average TESTDOMAIN\admin 4 4 0 0 0 0 0 634

Maximum TESTDOMAIN\admin 11 11 0 0 1 1 0 2257


Managing

Monitor File system Statistics

The fs.filesystem displays the most active files within each specified filesystem.

This statistic provides the following information:

1. Total KiB/Sec

2. readBytes

3. WrittenBytes

4. avgTime

5. readAvgTime

6. writeAvgTime

Note: File inodes will not be resolved until the filesystem is configured for file resolution using theserver_fileresolve command in the Command Line Interface Reference for File guide.

Action

To monitor fs.filesystem statistics, use this command syntax:

$ server_stats movername -i interval -m fs.filesystem.ufs_5 -c count

where:


<seconds> = time interval


Example:

To monitor fs.filesystem statistics, type:

$ server_stats server_2 -i 1 -m fs.filesystem.ufs_5 -count 1


Managing

Output

server_2 Filesystem File Total Read Written Average Read Write

Average AverageTimestamp KiB/s KiB/s KiB/s uSecs/Call uSecs/CalluSecs/Call

call03:52:01 ufs_5 /server_2/ufs_5/

dir00005/testdir/vsf_0000031711.tmp 12 8 4 73348 52583 114878

/server_2/ufs_5/dir00005/testdir/3TH_0000030114.tmp 12 8 4 118453 73745 207870

/server_2/ufs_5/dir00005/testdir/HaD_0000009345.tmp 12 8 4 37018 10757 89541

server_2 Filesystem File Total Read Written Average Read WriteAverage Average

Timestamp KiB/s KiB/s KiB/s uSecs/Call uSecs/CalluSecs/CallMinimum ufs_5 /server_2/ufs_5/

dir00005/testdir/3TH_0000030114.tmp 12 8 4 118453 73745 207870

/server_2/ufs_5/dir00005/testdir/APH_0000011168.tmp 12 4 8 60688 39023 71520

/server_2/ufs_5/dir00005/testdir/HaD_0000009345.tmp 12 8 4 37018 10757 89541

Average ufs_5 /server_2/ufs_5/dir00005/testdir/3TH_0000030114.tmp 12 8 4 118453 73745 207870

/server_2/ufs_5/dir00005/testdir/

APH_0000011168.tmp 12 4 8 60688 39023 71520


HaD_0000009345.tmp 12 8 4 37018 10757 89541Maximum ufs_5 /server_2/ufs_5/

dir00005/testdir/3TH_0000030114.tmp 12 8 4 118453 73745

207870/server_2/ufs_5/dir00005/testdir/

APH_0000011168.tmp 12 4 8 60688 39023 71520


HaD_0000009345.tmp 12 8 4 37018 10757 89541


Managing

Output

Note:

In order to have proper resolution, perform the following steps:

1. Start the service (server_fileresolve movername -service -start)

2. Register filesystem (server_fileresolve movername -add /filesystem_mount_path)

If, however, the service is running, but the filesystem is not registered with it, one can resolve thefilename manually:

server_fileresolve movername -lookup -filesystem ufs_2 -inode 38


Managing

Monitor NFS User Statistics

The nfs.user displays similar data that the nfs.client does. However, it is correlated to usersas opposed to IP address.

The statistics contains the following information:

1. Total NFS Ops/S

2. read Ops/S

3. write Ops/S


5. Total KiB/Sec

6. Read KiB/Sec

7. Write Ki B/Sec

8. avgTime

The default sort field is Total Ops/S

Action

To monitor NFS user statistics, use this command syntax:

$ server_stats movername -i interval-m nfs.user

where:


Example:

To monitor NFS user statistics, type:

$ server_stats server_2 -i 5 -m nfs.user


Managing

Output

server_2 User name NFS NFS NFS NFS NFS NFS NFSNFSTimestamp Total Read Write Suspicious Total Read WriteAvg

Ops/s Ops/s Ops/s Ops KiB/s KiB/s KiB/suSecs

/call14:38:52 TESTDOMAIN\admin 3 3 0 0 0 0 0405

14:38:57 TESTDOMAIN\admin 33 33 0 0 3 3 06771

14:39:02

14:39:07 TESTDOMAIN\admin 0 0 0 0 0 0 066

14:39:22

server_2 User name NFS NFS NFS NFS NFS NFS NFSNFS

Summary Total Read Write Suspicious Total Read WriteAvg

Ops/s Ops/s Ops/s Ops KiB/s KiB/s KiB/suSecs

/callMinimum TESTDOMAIN\admin 0 0 0 0 0 0 0

66Average TESTDOMAIN\admin 12 12 0 0 1 1 0

1902Maximum TESTDOMAIN\admin 33 33 0 0 3 3 0

6771


Managing

Monitor Store Volume Statistics

The store.volume displays top File Systems per disk volume. To list filesystems for a specificdisk volume (for e.g. a volume named d19, run the following server_stats command:

$ server_stats server_2 -i 1 -m store.volume.d19


1. totalBlocks

2. readBlocks

3. writeBlocks

4. totalBytes

5. readBytes

6. writeBytes

The Default sort field is totalBlocks.

Action

To monitor Store Volume statistics, use this command syntax:

$ server_stats movername -i interval-m store.volume

where:


<seconds>= number of seconds for each interval

Example:

To monitor Store Volume statistics, type:

$ server_stats server_2 -i 1 -m store.volume.d19


Managing

Output

server_2 dVol Filesystem Total Read Written TotalRead WrittenTimestamp Blocks/s Blocks/s Blocks/s KiB/sKiB/s KiB/s

06:00:09 d19 ufs_1 7568 5584 1984 37842792 992

ufs_3 5488 3616 1872 27441808 936

ufs_5 4304 3104 1200 21521552 60006:00:10 d19 ufs_1 7088 5248 1840 35442624 920

ufs_5 5472 3920 1552 27361960 776

ufs_3 4608 3648 960 23041824 480

server_2 dVol Filesystem Total Read Written TotalRead Written

Summary Blocks/s Blocks/s Blocks/s KiB/sKiB/s KiB/s

Minimum d19 ufs_1 7088 5248 1840 35442624 920

ufs_3 4608 3616 960 23041808 480

ufs_5 4304 3104 1200 21521552 600

Average d19 ufs_1 7328 5416 1912 36642708 956

ufs_3 5048 3632 1416 25241816 708

ufs_5 4888 3512 1376 24441756 688

Maximum d19 ufs_1 7568 5584 1984 37842792 992

ufs_3 5488 3648 1872 27441824 936

ufs_5 5472 3920 1552 27361960 776

Display NFS User Information

Action

To display the NFS user information, use this command syntax:

$ server_stats movername -i seconds -m nfs.user

where:


name = optional name for the NFS export


Managing

Action

Example:

To display the NFS user information, type:

$ server_stats server_2 -i 5 -m nfs.user

Output


Timestamp Total Read Write Suspicious Total Read WriteAvg

Ops/s Ops/s Ops/s Ops KiB/s KiB/s KiB/suSecs/call14:38:52 src00000 3 3 0 0 0 0 0

40514:38:57 src00000 33 33 0 0 3 3 0

677114:39:02

14:39:07 src00000 0 0 0 0 0 0 066

14:39:22


Summary Total Read Write Suspicious Total Read WriteAvg

Ops/s Ops/s Ops/s Ops KiB/s KiB/s KiB/suSecs/callMinimum src00000 0 0 0 0 0 0 0

66Average src00000 12 12 0 0 1 1 0

1902Maximum src00000 33 33 0 0 3 3 0

6771

Monitor NFS Group Statistics

The nfs.group displays the same data as nfs.client does. However, it is correlated to NFSgroup ID (as opposed to the NFS client’s IP address).


1. Total NFS Ops/S

2. read Ops/S

3. write Ops/S


5. Total KiB/Sec


Managing

6. Read KiB/Sec

7. Write Ki B/Sec

8. avgTime

Action

To monitor NFS group statistics, use this command syntax:

$ server_stats movername -m nfs.group

where:


Example:

To monitor NFS group statistics, type:

$ server_stats server_2 -m nfs.group

Output

server_2 NFS Group NFS NFS NFS NFS NFS NFS NFS NFS NFS

Timestamp Total Read Write Susp- Total Read Write Avg

Op/s Op/s Op/s -cious KiB/s KiB/s KiB/s uSecs/Ops

call02:47:14 id=0 264 0 213 0 108919 0 108919 1683

DM2-002:47:29 id=0 416 0 416 0 212821 0 212821 2184

DM2-002:47:44 id=0 432 0 432 0 221252 0 221252 5206

server_2 NFS Group NFS NFS NFS NFS NFS NFS NFS NFS NFSTimestamp Total Read Write Susp- Total Read Write Avg

Op/s Op/s Op/s -cious KiB/s KiB/s KiB/suSecs/call

OpsMinimum id=0 264 0 213 0 108919 0 1089190 22

Average id=0 370 0 354 0 180998 0 180998 3024

Maximum id=0 432 0 432 0 221252 0 221252 5206

Monitor NFS Export Statistics

The nfs.export displays the same data as nfs.client does. However, it is correlated to NFSexport (as opposed to the NFS client’s IP address).


Managing


1. Total NFS Ops/S

2. read Ops

3. write Ops


5. Total KiB/Sec

6. Read KiB/Sec

7. Write Ki B/Sec

8. avgTime

Action

To monitor NFS export statistics, use this command syntax:

$ server_stats movername -m nfs.export

where:


Example:

To monitor NFS export statistics, type:

$ server_stats server_2 -m nfs.export


Managing

Output

server_2 NFS Export NFS NFS NFS NFS NFS NFS NFSNFS

Timestamp Total Read Write Susp- Total Read WriteAvg

Op/s Op/s Op/s -cious KiB/s KiB/s KiB/suSecs/call Ops

call02:48:14 /server_2/ufs_5/dir00005 157 0 157 0 80213 0 802136272

DM2-0/server_2/ufs_3/dir00003 139 0 139 0 71305 0 71305

462/server_2/ufs_4/dir00004 130 0 130 0 66662 0 66662

370002:48:29 /server_2/ufs_5/dir00005 158 0 158 0 80828 0 808283454

/server_2/ufs_3/dir00003 140 0 140 0 71646 0 7164629

/server_2/ufs_4/dir00004 133 0 133 0 68233 0 682333040

server_2 NFS Export NFS NFS NFS NFS NFS NFS NFSNFS

Timestamp Total Read Write Susp- Total ReadWrite Avg

Op/s Op/s Op/s -cious KiB/s KiB/sKiB/s uSecs/call

OpsMinimum /server_2/ufs_5/dir00005 157 0 157 0 80213 080213 3454

/server_2/ufs_3/dir00003 139 0 139 0 71305 071305 29

/server_2/ufs_4/dir00004 130 0 130 0 66662 066662 3040Average /server_2/ufs_5/dir00005 157 0 157 0 80521 080521 4863

/server_2/ufs_3/dir00003 140 0 140 0 71475 071475 246

/server_2/ufs_4/dir00004 132 0 132 0 67447 067447 3370Maximum /server_2/ufs_5/dir00005 158 0 158 0 80828 080828 6272

/server_2/ufs_3/dir00003 140 0 140 0 71646 071646 462

/server_2/ufs_4/dir00004 133 0 133 0 68233 068233 3700

Monitor files per Quota Tree statistics

Displays the most active files within each specified Qtree.


1. Total KiB/Sec


Managing

2. readBytes

3. WrittenBytes

4. avgTime

5. readAvgTime

6. writeAvgTime

Note: File inodes will not be resolved until the Quota Tree is configured for file resolution using theserver_fileresolve command in the Command Line Interface Reference for File guide.

Action

To monitor files per quota tree statistics, use this command syntax:

$ server_stats movername -i -c count interval -m fs.qtreefile

where:


seconds = time interval

count = number of reports

Example:

To monitor files per quota tree statistics, type:

$ server_stats server_2 -i 1 -c 2 -m fs.qtreefile


Managing

Output


Managing

Output

server_2 Quota Tree File File Total Read Written AverageRead Average Write Average

Timestamp KiB/s KiB/s KiB/s uSecs/CalluSecs/Call uSecs/Call

02:55:57 ufs_2:/dir00002 id=38:7339 512 0 512 438730 43873

id=38:10137 1024 0 1024 495570 49557

ufs_0:/dir00000 id=36:10769 1024 0 1024 261880 26188

id=36:11712 1024 0 1024 453770 45377

ufs_4:/dir00004 id=40:251 2560 0 2560 15380 1538

id=40:256 2560 0 2560 12800 1280

ufs_1:/dir00001 id=37:17393 1024 0 1024 542100 54210

id=37:17572 1024 0 1024 397080 39708

ufs_5:/dir00005 /server_2/ufs_5/dir00005/testdir/

iv9_0000055303.tmp 2560 0 2560 16230 1623

/server_2/ufs_5/dir00005/testdir/KRc_0000008199.tmp 2560 0 2560 1650

0 1650fs_3:/dir00003 id=39:237 2560 0 2560 30

0 30id=39:207 2560 0 2560 33

0 3302:55:58 ufs_2:/dir00002 id=38:10221 1024 0 1024 51350

0 51350id=38:9981 1024 0 1024 37275

0 37275ufs_0:/dir00000 id=36:10155 1024 0 1024 60618

0 60618id=36:10453 1024 0 1024 32847

0 32847ufs_4:/dir00004 id=40:183 2560 0 2560 3332

0 3332id=40:256 2560 0 2560 1391

0 1391ufs_1:/dir00001 id=37:17129 1024 0 1024 77310

0 77310id=37:17453 1024 0 1024 17741

0 17741ufs_5:/dir00005 /server_2/

ufs_5/dir00005/testdir/iv9_0000055303.tmp 2560 0 2560 1982

0 1982/server_2/ufs_5/dir00005/testdir/


Managing

Output

KRc_0000008199.tmp 2560 0 2560 20190 2019

ufs_3:/dir00003 id=39:243 2560 0 2560 260 26

id=39:248 2560 0 2560 290 29

server_2 Quota Tree File File Total Read Written AverageRead Average Write Average

Summary KiB/s KiB/s KiB/s uSecs/CalluSecs/Call uSecs/CallMinimum ufs_2:/dir00002 id=38:10063 1024 0 1024 32177

0 32177id=38:10066 1024 0 1024 18897

0 18897ufs_2:/dir00008ufs_2:/dir00014ufs_2:/dir00020ufs_2:/dir00026ufs_0:/dir00000 id=36:10151 1024 0 1024 42949

0 42949id=36:10155 1024 0 1024 60618


0 3332id=40:194 2560 0 2560 1488


0 533id=37:16235 1024 0 1024 2197

0 2197

ufs_1:/dir00007ufs_1:/dir00013ufs_1:/dir00019ufs_1:/dir00025ufs_5:/dir00005 /server_2/

ufs_5/dir00005/testdir/72n_0000028679.tmp 2560 0 2560 1580

0 1580/server_2/ufs_5/dir00005/testdir/74u_0000022535.tmp 2560 0 2560 1547


0 32id=39:174 2560 0 2560 29


Managing

Output

0 29ufs_3:/dir00009ufs_3:/dir00015ufs_3:/dir00021ufs_3:/dir00027

Average ufs_2:/dir00002 id=38:10063 1024 0 1024 321770 32177

id=38:10066 1024 0 1024 188970 18897

ufs_2:/dir00008ufs_2:/dir00014ufs_2:/dir00020ufs_2:/dir00026ufs_0:/dir00000 id=36:10151 1024 0 1024

42949 0 42949id=36:10155 1024 0 1024

60618 0 60618ufs_0:/dir00006ufs_0:/dir00012ufs_0:/dir00018ufs_0:/dir00024ufs_4:/dir00004 id=40:183 2560 0 2560

3332 0 3332id=40:194 2560 0 2560


533 0 533id=37:16235 1024 0 1024

2197 0 2197ufs_1:/dir00007ufs_1:/dir00013ufs_1:/dir00019ufs_1:/dir00025ufs_5:/dir00005 /server_2/ufs_5

/dir00005/testdir/72n_0000028679.tmp 2560 0 2560

1724 0 1724/server_2/ufs_5/dir00005/testdir/74u_0000022535.tmp 2560 0 2560


32 0 32id=39:174 2560 0 2560

29 0 29 0 1756ufs_3:/dir00009ufs_3:/dir00015ufs_3:/dir00021ufs_3:/dir00027

Maximum ufs_2:/dir00002 id=38:10063 1024 0 102432177 0 32177


Managing

Output

id=38:10066 1024 0 102418897 0 18897

ufs_2:/dir00008ufs_2:/dir00014ufs_2:/dir00020ufs_2:/dir00026ufs_0:/dir00000 id=36:10151 1024 0 1024

42949 0 42949id=36:10155 1024 0 1024


3332 0 3332id=40:191 2560 0 2560


533 0 533id=37:16235 1024 0 1024

2197 0 2197ufs_1:/dir00007ufs_1:/dir00013ufs_1:/dir00019ufs_1:/dir00025ufs_5:/dir00005 /server_2/

ufs_5/dir00005/testdir/72n_0000028679.tmp 2560 0 2560

1867 0 1867/server_2/ufs_5/dir00005/testdir/74u_0000022535.tmp 2560 0 2560


32 0 32id=39:168 2560 0 2560

29 0 29

Monitor NFS VDM Client Statistics

Displays the same data as nfs.client, but only for VDM.


1. Total NFS Ops/S

2. read Ops/S


Managing

3. write Ops/S


5. Total KiB/Sec

6. Read KiB/Sec

7. Write Ki B/Sec

8. avgTime

Action

To monitor NFS VDM client statistics, use this command syntax:

$ server_stats <movername> -i <seconds> -m nfs.vdm.*.client -c <count> -termi-nationsummary {no | yes | only}

where:




Example:

To monitor NFS VDM client statistics, type:

$ server_stats server_3 -i 1 -m nfs.vdm.*.client -c 5 -te no

Output

server_2 VDM name Client NFS NFS NFS NFS NFS NFS NFS NFS

Timestamp Total Read Write Suspicious Total Read WriteAvg

Ops/s Ops/s Ops/s Ops KiB/s KiB/s KiB/suSecs/call10:42:43 vdm_1 id=10.103.11.13 2 0 0 1 0 0 0 18857

vdm_2 id=10.103.11.14 7 0 1 0 0 0 0 1637810:42:44 vdm_1 id=10.103.11.13 2 0 0 1 0 0 0 7882

vdm_2 id=10.103.11.14 8 0 1 0 0 0 0 1178410:42:45 vdm_1 l13.perf1.com 2 0 0 1 0 0 0 9762

vdm_2 l14.perf1.com 7 0 1 0 0 0 0 1981310:42:46 vdm_1 l13.perf1.com 2 0 0 1 0 0 0 69773

vdm_2 l14.perf1.com 7 0 1 0 0 0 0 825710:42:47 vdm_1 l13.perf1.com 2 0 0 1 0 0 0 10473

vdm_2 l14.perf1.com 8 0 1 0 0 0 0 1835


Managing

Monitor NFS VDM User Statistics

Displays the same data as nfs.user, but only for VDMs.


1. Total NFS Ops/S

2. read Ops/S

3. write Ops/S


5. Total KiB/Sec

6. Read KiB/Sec

7. Write Ki B/Sec

8. avgTime

Action

To monitor NFS VDM user statistics, use this command syntax:

$ server_stats <movername> -i <seconds> -m nfs.vdm.*.user -c <count> -termina-tionsummary {no | yes | only}

where:



<count>= number of reports

Example:

To monitor NFS VDM user statistics, type:

$ server_stats server_3 -i 1 -m nfs.vdm.*.user -c 5 -te no

Output

server_2 VDM name NFS NFS NFS NFS NFS NFS NFS NFS NFSTimestamp User Total Read Write Suspicious Total Read Avg

Ops/s Ops/s Ops/s Ops KiB/s KiB/s Write uSecs/KiB/s call

10:43:20 vdm_1 id=0 2 0 0 1 0 0 0 18791vdm_2 id=0 5 0 1 0 0 0 0 6070

10:43:21 vdm_1 id=0 2 0 0 1 0 0 0 15574vdm_2 id=0 3 0 0 0 0 0 0 94

10:43:22 vdm_1 id=0 2 0 0 1 0 0 0 16976vdm_2 id=0 2 0 1 0 0 0 0 116061

10:43:23 vdm_1 id=0 2 0 0 1 0 0 0 38150vdm_2 id=0 5 0 1 0 0 0 0 19183

10:43:24 vdm_1 id=0 2 0 0 1 0 0 0 63362vdm_2 id=0 5 0 1 0 0 0 0 53115


Managing

Monitor NFS VDM Group Statistics

Displays the same data as nfs.group, but only for VDMs.


1. Total NFS Ops/S

2. read Ops/S

3. write Ops/S


5. Total KiB/Sec

6. Read KiB/Sec

7. Write Ki B/Sec

8. avgTime

Action

To monitor NFS VDM group statistics, use this command syntax:

$ server_stats<movername> -i <seconds>-m nfs.vdm.*.group-c <count> -termina-tionsummary {no | yes | only}

where:




Example:

To monitor NFS VDM group statistics, type:

$ server_stats server_3 -i 1 -m nfs.vdm.*.group -c 5 -te no

Output

server_2 VDM NFS NFS NFS NFS NFS NFS NFS NFS NFSTimestamp name Group Total Read Write Suspicious Total Read Avg

Write uSecs/Ops/s Ops/s Ops/s Ops KiB/s KiB/s KiB/s call

10:43:46 vdm_1 id=0 2 0 0 1 0 0 0 6381vdm_2 id=0 5 0 1 0 0 0 0 7557

10:43:47 vdm_1 id=0 1 0 0 0 0 0 0 10vdm_2 id=0 5 0 1 0 0 0 0 29440

10:43:48 vdm_1 id=0 1 0 0 1 0 0 0 198524vdm_2 id=0 6 0 1 0 0 0 0 5877

10:43:49 vdm_1 id=0 2 0 0 1 0 0 0 52406vdm_2 id=0 5 0 1 0 0 0 0 34691

10:43:50 vdm_1 id=0 2 0 0 1 0 0 0 13695vdm_2 id=0 5 0 1 0 0 0 0 2984


Managing

Monitor NFS VDM Export Statistics

Displays the same data as nfs.export, but only for VDMs.


1. Total NFS Ops/S

2. read Ops/S

3. write Ops/S


5. Total KiB/Sec

6. Read KiB/Sec

7. Write Ki B/Sec

8. avgTime

Action

To monitor NFS VDM export statistics, use this command syntax:

$ server_stats<movername> -i<seconds>-m nfs.vdm.*.export-c <count> -termina-tionsummary {no | yes | only}

where:




Example:

To monitor NFS VDM export statistics, type:

$ server_stats server_3 -i 1 -m nfs.vdm.*.export -c 5 -te no


Managing

Output

server_2 VDM NFS NFS NFS NFS NFS NFS NFS NFS NFS

Timestamp name Export Total Read Write Suspicious Total Read Write AvgOps/s Ops/s Ops/s Ops KiB/s KiB/s KiB/s uSecs/call

10:44:10 vdm_1 /demo_0 2 0 0 1 0 0 0 16975

vdm_2 /demo_1 5 0 1 0 0 0 0 475510:44:11 vdm_1 /demo_0 2 0 0 1 0 0 0 42104

vdm_2 /demo_1 5 0 1 0 0 0 0 7508310:44:12 vdm_1 /demo_0 2 0 0 0 0 0 0 18991

vdm_2 /demo_1 3 0 0 0 0 0 0 9610:44:13 vdm_1 /demo_0 2 0 0 1 0 0 0 14357

vdm_2 /demo_1 2 0 1 0 0 0 0 13877910:44:14 vdm_1 /demo_0 2 0 0 1 0 0 0 137153

vdm_2 /demo_1 5 0 1 0 0 0 0 9511


Managing

The -noresolve option

The server_stats provides the -noresolve option to disable element resolution. The outputis similar to the exception of the elements of a set, which are displayed as element IDs suchas FS IDs, IP addresses, other than the element names such as FS Names, client names. Thisoption may also be useful to the users who need to view data on element IDs, other than onelement names.

Action

To monitor the NFS client using the -noresolve option, use this command syntax:

$ server_stats movername -monitor nfs.client -te no -c seconds-noresolve

where:



Examples:

To monitor the NFS client using the -noresolve option, type:

$ server_stats server_2 -monitor nfs.client -te no -c 2 -noresolve

Output

server_2 Client NFS NFS NFS NFS NFS NFS NFSNFSTimestamp Total Read Write Suspi- Total Read WriteAvg

Ops/s Ops/s Ops/s -cious KiB/s KiB/s KiB/suSec/

Opscall15:44:04 id=10.103.11.7 531 0 526 0 269175 0 2691753835

id=10.103.11.8 546 0 535 0 274057 0 2740573482

id=10.103.11.9 181 0 181 0 92877 0 928773506815:44:19 id=10.103.11.8 2161 0 2145 0 1098225 0 10982253806

id=10.103.11.7 2198 0 2181 0 1116790 0 11167903770

id=10.103.11.9 376 0 376 0 192508 0 19250849141

Action

To monitor the NFS user using the -noresolve option, use this command syntax:

$ server_stats movername -i <seconds> -m nfs.user -noresolve

where:


Managing

Action



Example:

To monitor the NFS user using the -noresolve option, type:

$ server_stats server_2 -i 5 -m nfs.user -noresolve

Output

server_2 User name NFS NFS NFS NFS NFS NFS NFS NFSTimestamp Total Read Write Suspi- Total Read Write Avg

Ops/s Ops/s Ops/s -cious KiB/s KiB/s KiB/s uSecs/Ops call

14:38:52 id=54682 3 3 0 0 0 0 0 40514:38:57 id=54862 33 33 0 0 3 3 0 677114:39:02

14:39:07 id=54682 0 0 0 0 0 0 0 6614:39:22

server_2 User name NFS NFS NFS NFS NFS NFS NFS NFSSummary Total Read Write Suspi- Total Read Write Avg

Ops/s Ops/s Ops/s -cious KiB/s KiB/s KiB/s uSecs/call

Minimum id=54682 0 0 0 0 0 0 0 66Average id=54682 12 12 0 0 1 1 0 1902Maximum id=54682 33 33 0 0 3 3 0 6771

Action

To monitor the Store Volume using the -noresolve option, use this command syntax:

$ server_stats movername -i seconds -m store.volume -te no -noresolve

where:



Example:

To monitor the Store Volume using the -noresolve option, type:

$ server_stats server_2 -i 1 -m store.volume -te no -noresolve


Managing

Output

server_2 dVol Queue Read Read Avg Write Write Avg Write Util %Timestamp Depth Ops/s KiB/s Read Ops/s KiB/s Size Bytes

Size Bytes19:44:57 id=17 1 0 0 - 429 11216 26772 25

id=5 0 0 0 - 6 104 17749 219:44:58 id=5 0 0 0 - 130 3128 24639 6

Id=18 0 0 0 - 3 12 4096 0

Display statistics for Continuous Monitoring

The alerter daemon (nas_ alerterd) reads a policy configuration file and connects to activeData Movers. For each active Data Mover, for which you have configured a policy for CPUutilization, the CPU utilization is sampled once every minute. Similarly, for each active DataMover, for which you have configured policies for memory utilization and average responsetime for NFS operations, memory utilization and average response time for NFS operationsare sampled once every minute. When all samples meet the applicable policy for thepersistence period and the threshold condition, an alert is generated. As long as thesubsequent samples continue to meet the policy, no further notifications are sent. When asample fails to meet the policy threshold condition, the alert will be cleared and anothertrap or email notification will be generated. For more information on how to configure eventsand notifications, refer to the Configuring Events and Notifications on VNX for File technicalmodule.

The tasks to display continuous monitoring statistics include:

◆ Configure CPU utilization policy, memory utilization notification policy, and averageresponse time for NFS operations policy on page 71

◆ Restart the alert daemon process on page 73

Configure CPU utilization policy, memory utilization notification policy,and average response time for NFS operations policy

You can configure a CPU utilization notification policy, a memory utilization notificationpolicy, or an average response time for NFS operations policy by editing the policy file,/nas/site/nas_alerterd.conf.

The policy file uses comma-separated fields in the [POLICY] section in the following format:

$ <policy_name>,<data_mover_name>, <statpath_name>,<operator>,<threshold>,<persistence>

where:

<policy_name> = unique name within the policy file to identify the policy by name. The policyname is case-sensitive and should be limited to alphanumeric characters (with no whitespace).

Display statistics for Continuous Monitoring 71

Managing

<data_mover_name> = Data Mover name or ALL indicates all Data Movers for whichCPUutilization, memory utilization statistics, or the average response time per file systemper client per NFS operation will be monitored.

<statpath_name> = the pathname for CPU utilization statistics, memory utilization statistics,or average response time per file system per client per NFS operation. The different elementsin the pathname are separated by a period.

<operator> = comparison operator and must be one of the following:

◆ eq = equal to◆ gt = greater than (default)◆ ge = greater than or equal to◆ lt = less than◆ le = less than or equal to

<threshold> = percentage of CPU utilization or memory utilization, or for NFS operations,the average response time in microseconds per call.

<persistence> = number of minutes or quantity of times that the condition needs to be trueto generate an alert.

output_format = (optional) either csv or text.

<sampling_interval> = (optional) elapsed time between samples.

<sampling_duration> = (optional) length of time over which to take samples.

<statpath_names_to_collect> = (optional) comma-separated list of sampled statpath namesto collect as a result of a raised event.

You can also configure two additional items located in the [COMMON] section of the policyfile:

<stats_collection_dir> = a fully qualified directory path for the location of files containingthe result of server_stats sessions. If the stat_collection_dir option is not set, the server_statssession will not run for any policy requiring server_stats disposition.

allow_concurrent_collection = this option determines if multiple instances of server_statssessions may be concurrently running for the same policy/DataMover combination.

To generate an alert, the CPU utilization value needs to be greater than or equal to 90 percentfor at least 15 consecutive minutes. If an alert was generated and subsequently the CPUutilization sample drops to less than or equal to 90 percent, the alert is cleared. The followingpolicy for server_2 uses a ge operator, a 90 threshold, and a 15-minute persistence:

CPU_Server2,server_2,kernel.cpu.utilization.cpuUtil,ge,90,15

Additional policy file examples are as follows. In the following policy an alert is generated,if server_2 or server_3 or both have CPU utilizations of at least 80 percent for 5 minutes.The alert will clear when the CPU utilization drops below 80 percent:

CPU_Server2,server_2,kernel.cpu.utilization.cpuUtil,gt,80,5



Managing

The following policy illustrates that you can configure multiple policies for a single DataMover. An alert is generated for any Data Mover with a CPU utilization of at least 85 percentfor 15 minutes, and an alert is generated for server_2 if it reaches a CPU utilization of atleast 80 percent for 5 minutes. An alert is also generated for server_2 if it reaches a memoryutilization of at least 80 percent for 5 minutes. The alerts will clear when the CPU utilizationdrops below the threshold:

CPU_ALL,ALL,kernel.cpu.utilization.cpuUtil,ge,85,15


Memory_Server2,server_2,kernel.memory.util,gt,80,5

In the following policy an alert is generated for any DataMover with an average responsetime for NFS operations of at least 5000 microseconds per call for 1 minute. The outputformat will be in csv and the interval and duration of the sampling will be 15 seconds and120 minutes, respectively. The sampled statpaths names to collect as a result of a raisedevent will be nfs.client, nfs.user, nfs.group, nfs.export. The alert will clear when the averageresponse time drops below 5000 microseconds per call.

nfs_avgtime,ALL,nfs.filesystem.*.client.*.op.*.avgTime,ge,5000,1,csv,15,120,nfs.client,nfs.user,nfs.group,nfs.export

Restart the alert daemon process

After editing the CPU utilization policies or any of the other policies, you must restart thealerterd daemon.

To restart the nas_alerterd process, follow these steps:

1. # ps -ef |grep nas_alerterd

root 369 22600 0 Apr13 ? 00:00:11 /nas/sbin/nas_alerterdroot 9834 3586 0 07:31 pts/0 00:00:00 grep nas_alerterd

2. # killall -s SIGINT nas_alerterd

The daemon will restart automatically after being stopped.

Display statistics for Continuous Monitoring 73

Managing

Sort by field name

Action

To display the nfsOps-std statistics group sorted by the average time in microseconds, use this command syntax:

$ server_stats <movername> -m nfsops-std -sort <field_name> avgTime -order{asc|desc} -lines <lines_of_output> -interval <seconds> -count <count>-terminationsummary {no|yes|only}

where:


<field_name> = name of the output field

<lines_of_output> = number of output lines



Example:

To display the nfsOps-std statistics group sorted by the average time in microseconds used for the five second interval,in descending order, and including the three counts of data output, type:

$ server_stats server_2 -m nfsops-std -sort avgTime -order desc -lines 3 -i 5 -c 3-te no

Output

server_2 NFS Op NFS NFS NFS NFS Op %Timestamp Op Op Op

Calls/s Errors/s uSec/call04:09:39 v3Create 1 0 31657550 0

v3Write 610 0 6223366 10004:09:44 v3Write 607 0 6275942 98

v3Create 11 0 3978054 204:09:49 v3Write 574 0 6691264 93

v3Create 42 0 1073819 7


Managing

4

Troubleshooting

As part of an effort to continuously improve and enhance the performanceand capabilities of its product lines, EMC periodically releases new versionsof its hardware and software. Therefore, some functions described in thisdocument may not be supported by all versions of the software orhardware currently in use. For the most up-to-date information on productfeatures, refer to your product release notes.

If a product does not function properly or does not function as describedin this document, contact your EMC Customer Support Representative.

ProblemResolution Roadmap for VNX contains additional information aboutusing EMC Online Support and resolving problems.

Topics included in this chapter are:◆ EMC E-Lab Interoperability Navigator on page 76◆ VNX user customized documentation on page 76◆ Error messages on page 76◆ EMC Training and Professional Services on page 77


EMC E-Lab Interoperability Navigator

The EMC E-Lab™ Interoperability Navigator is a searchable, web-based application thatprovides access to EMC interoperability support matrices. It is available on EMC OnlineSupport at http://Support.EMC.com. After logging in, in the right pane under Product andSupport Tools, click E-Lab Navigator.

VNX user customized documentation

EMC provides the ability to create step-by-step planning, installation, and maintenanceinstructions tailored to your environment. To create VNX user customized documentation,go to: https://mydocs.emc.com/VNX.

Error messages

All event, alert, and status messages provide detailed information and recommended actionsto help you troubleshoot the situation.

To view message details, use any of these methods:

◆ Unisphere software:

• Right-click an event, alert, or status message and select to view Event Details, AlertDetails, or Status Details.

◆ CLI:

• Type nas_message -info <MessageID>, where <MessageID> is the messageidentification number.

◆ Celerra Error Messages Guide:

• Use this guide to locate information about messages that are in the earlier-releasemessage format.

◆ EMC Online Support:

• Use the text from the error message's brief description or the message's ID to searchthe Knowledgebase on EMC Online Support. After logging in to EMC Online Support,locate the applicable Support by Product page, and search for the error message.


Troubleshooting


https://mydocs.emc.com/VNX


EMC Training and Professional Services

EMC Customer Education courses help you learn how EMC storage products work togetherwithin your environment to maximize your entire infrastructure investment. EMC CustomerEducation features online and hands-on training in state-of-the-art labs conveniently locatedthroughout the world. EMC customer training courses are developed and delivered by EMCexperts. Go to EMC Online Support at http://Support.EMC.com for course and registrationinformation.

EMC Professional Services can help you implement your system efficiently. Consultantsevaluate your business, IT processes, and technology, and recommend ways that you canleverage your information for the most benefit. From business plan to implementation, youget the experience and expertise that you need without straining your IT staff or hiring andtraining new personnel. Contact your EMC Customer Support Representative for moreinformation.

EMC Training and Professional Services 77

Troubleshooting



Troubleshooting

Glossary

C

cacheTemporary storage used to retain frequently used data for faster access. For example, a memorycache may be used between a CPU and main memory.

Common Internet File System (CIFS)File-sharing protocol based on the Microsoft Server Message Block (SMB). It allows users toshare file systems over the Internet and intranets.

F

file systemMethod of cataloging and managing the files and directories on a system.

K

kibibytesKibibytes comes from kilo binary and stands for 1024 in the ISO International System of Units.Network performance is measured in kibibytes.

M

metavolumeOn a VNX for File, a concatenation of volumes, which can consist of disk, slice, or stripe volumes.Also called a hypervolume or hyper. Every file system must be created on top of a uniquemetavolume.

See also disk volume, slice volume, stripe volume, and volume.

N

networkCombination of devices, cabling, and software that makes up a communication infrastructure.


network file system (NFS)Network file system (NFS) is a network file system protocol that allows a user on a clientcomputer to access files over a network as easily as if the network devices were attached to itslocal disks.

P

packetIn communications, a fixed block of data transmitted as a single entity. In local area networks(LANs), the terms frame and packet are used synonymously.

See also frame.

portPhysical connection point to a network or a number used at the transport layer to trackhost-to-host virtual circuits.

T

threadSequential flow of control in a computer program. A thread consists of address space, a stack,local variables, and global variables.


Terminology

Index

Bbasic

volume statistics 12

CCIFS

statistics 13cifsOps-std 12correlated statistics

information 30count, for summary statistics 12CPU utilization 11

DDirectory Name Lookup Cache ratio 12diskVolumes-std 12display

CIFS statistics summary 20, 38, 39, 40file system statistics 28NFS statistics summary 21statistics for NFS file system 35volume statistics 26

DNLC 12

EEMC E-Lab Navigator 76error messages 76

Ffile system statistic table 28

format, for summary statistics 12

Iinterval, for summary statistics 12ISO International System of Units 10

Kkernel buffer cache hit ratio 12kibibytes 10

Mmessages, error 76metavolume or file system statistics 12metavolume/file system statistics (fsvol) 13metaVolumes-std 12

NnetDevices-std 12network device statistics 12NFS

statistic table 30nfsOps-std 12

Oopen file cache hit 12

Pperformance statistics

sets 23tables 12


print format 10, 12pulsehealth check 11

Rrequirements

system requirements 8

Ttable 12

tablesfile system statistics 28NFS statistics 30

termination summary, for summary statistics 12titles, for summary statistics 12troubleshooting 75


Index

emc vnx series - dell emc russia · pdf fileemc®vnx® series release 8.1 managing...

Documents