The following post
briefly details how to demonstrate QoS on NetApp Clustered ONTAP 8.2. A cluster
called cluster1 has been configured, along with a CIFS enabled Vserver with
volume and share. The demonstration is run from a Windows Server 2012 Domain
Controller in the lab.
1) Map a drive
to the CIFS volume
net use V: \\vserver1\vs1_vol1
2) Iometer
Setup
Download iometer from http://www.iometer.org
and install.
i) Run Iometer
ii) Select the
server (in this case ADDC1010)
iii) ‘Disk
Targets’ tab, tick V
only, and configure:
Maximum Disk Size = 20000
Starting Disk Sector = 0
No. of Outstanding IOs = 16
Image: Configuring
Iometer 1 - ‘Disk Targets’ tab
iv) ‘Access
Specifications’ tab, choose “4K;
50% Read; 0% random”
Image: Configuring
Iometer 2 - ‘Access Specifications’ tab
v) ‘Test Setup’
tab
Test Description = QoS Test
Ramp Up Time = 4 seconds
Record Results = none
Image: Configuring
Iometer 3 - ‘Test Setup’ tab
vi) ‘Results
Display’ tab
Change ‘Update
Frequency’ to 4 seconds, and click the Green flag to start.
Image: Configuring
Iometer 4 - ‘Results Display’ tab
NOTE: Iometer
creates at 80’000KB (20’000 x 4KB) file called iobw.tst in the V drive.
3) QoS
Configuration
NOTE: PuTTY output
from this step is in the APPENDIX B.
i) Login as admin
to the Cluster Management IP of cluster1
ii) Run these
commands:
cluster1::> QoS
cluster1::qos>
policy-group
show
cluster1::qos>
statistics
performance show -iterations 4
NOTE: The IOPS you
see here should be close to what Iometer is showing.
cluster1::qos>
policy-group
create -policy-group pg_vserver1 -vserver vserver1 -max-throughput 1000iops
cluster1::qos>
policy-group
show
cluster1::qos>
vserver
modify -vserver vserver1 -qos-policy-group pg_vserver1
cluster1::qos>
statistics
performance show -iterations 4
NOTE: The IOPS you
see now should be close to the policy-group setting.
iii) Notice that
the IOPs as registered by Iometer are declining
iv) Stop Iometer
APPENDIX A: QoS
Test Output
cluster1::>
QoS
cluster1::qos>
policy-group show
This
table is currently empty.
cluster1::qos>
cluster1::qos>
statistics performance show -iterations 4
Policy
Group IOPS
Throughput Latency
--------------------
-------- --------------- ----------
-total- 4709
18.02MB/s 2.71ms
User-Best-Effort 4581 17.89MB/s 2.78ms
_System-Best-Effort 93
141.86KB/s 535.00us
_System-Background 35 0KB/s 0ms
-total- 4424
17.13MB/s 2.67ms
User-Best-Effort 4366 17.04MB/s 2.68ms
_System-Background 35 0KB/s 0ms
_System-Best-Effort 23
87.90KB/s 4.85ms
-total- 4934
19.10MB/s 2.86ms
User-Best-Effort 4881 19.06MB/s 2.85ms
_System-Background 35 0KB/s 0ms
_System-Best-Effort 18
42.70KB/s 9.61ms
-total- 4356
16.85MB/s 2.96ms
User-Best-Effort 4314 16.84MB/s 2.96ms
_System-Background 35 0KB/s 0ms
_System-Best-Effort 7
12.11KB/s 18.13ms
cluster1::qos>
policy-group create -policy-group pg_vserver1 -vserver vserver1 -max-throughput
1000iops
cluster1::qos>
policy-group show
Name Vserver Class Wklds Throughput
----------------
----------- ------------ ----- ------------
pg_vserver1 vserver1
user-defined - 0-1000IOPS
cluster1::qos>
vserver modify -vserver vserver1 -qos-policy-group pg_vserver1
cluster1::qos>
statistics performance show -iterations 4
Policy
Group IOPS Throughput Latency
--------------------
-------- --------------- ----------
-total- 1099
4.10MB/s 15.24ms
pg_vserver1 1047 4.08MB/s 16.00ms
_System-Background 30 0KB/s 0ms
_System-Best-Effort 22
14.87KB/s 283.00us
-total- 1100
4.09MB/s 15.21ms
pg_vserver1 1044 4.06MB/s 16.02ms
_System-Background 28 0KB/s 0ms
_System-Best-Effort 28
25.13KB/s 111.00us
-total- 1109 4.08MB/s 15.05ms
pg_vserver1 1043 4.07MB/s 16.00ms
_System-Background 35 0KB/s 0ms
_System-Best-Effort 31
12.56KB/s 99.00us
-total- 1096
4.09MB/s 15.35ms
pg_vserver1 1051 4.09MB/s 16.01ms
_System-Background 35 0KB/s 0ms
_System-Best-Effort 10 0KB/s 0ms
APPENDIX B: Some
Useful Space Reporting Commands
cluster1::> volume show
cluster1::> volume show
-vserver vserver1 -volume vs1_vol1 -field space-guarantee,space-guarantee-enabled
cluster1::> volume
show-space -vserver vserver1 -volume vs1_vol1
cluster1::> volume
show-footprint -vserver vserver1 -volume vs1_vol1
cluster1::> volume
show-space vs1_vol1
NOTE: The above
commands provide tons of information such as how to find - Inodes, Inodes
Percent, Filesystem Metadata size... and on and on...
Comments
Post a Comment