H9p97s.a.00 Lab

Managing HP 3PAR
StoreServ III
Lab guide
Use of this material to deliver training without prior written permission from HP is prohibited.
H9P97S A.00
 Copyright 2015 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice. The only warranties for HP
products and services are set forth in the express warranty statements accompanying such products and
services. Nothing herein should be construed as constituting an additional warranty. HP shall not be
liable for technical or editorial errors or omissions contained herein.
This is an HP copyrighted work that may not be reproduced without the written permission of HP. You
may not use these materials to deliver training to any person outside of your organization without the
written permission of HP.
Microsoft®, Windows®, Windows NT® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
All other product names mentioned herein may be trademarks of their respective companies.
Export Compliance Agreement
Export Requirements. You may not export or re-export products subject to this agreement in violation of
any applicable laws or regulations.
Without limiting the generality of the foregoing, products subject to this agreement may not be
exported, re-exported, otherwise transferred to or within (or to a national or resident of) countries under
U.S. economic embargo and/or sanction including the following countries:
Cuba, Iran, North Korea, Sudan and Syria.
This list is subject to change.
In addition, products subject to this agreement may not be exported, re-exported, or otherwise
transferred to persons or entities listed on the U.S. Department of Commerce Denied Persons List; U.S.
Department of Commerce Entity List (15 CFR 744, Supplement 4); U.S. Treasury Department
Designated/Blocked Nationals exclusion list; or U.S. State Department Debarred Parties List; or to parties
directly or indirectly involved in the development or production of nuclear, chemical, or biological
weapons, missiles, rocket systems, or unmanned air vehicles as specified in the U.S. Export
Administration Regulations (15 CFR 744); or to parties directly or indirectly involved in the financing,
commission or support of terrorist activities.
By accepting this agreement you confirm that you are not located in (or a national or resident of) any
country under U.S. embargo or sanction; not identified on any U.S. Department of Commerce Denied
Persons List, Entity List, US State Department Debarred Parties List or Treasury Department Designated
Nationals exclusion list; not directly or indirectly involved in the development or production of nuclear,
chemical, biological weapons, missiles, rocket systems, or unmanned air vehicles as specified in the U.S.
Export Administration Regulations (15 CFR 744), and not directly or indirectly involved in the financing,
commission or support of terrorist activities.
Printed in US
Managing HP 3PAR StoreServ III

Lab guide
May 2015
Contents
Lab 1 – Setting Up the Lab Environment ............................................................... L1-1

Objective .............................................................................................. L1-1
Introduction ........................................................................................... L1-1
Accessing the HP Virtual Labs .................................................................. L1-2
Shadowing a user .................................................................................. L1-6
Mapping the shared Y: drive ................................................................... L1-7
Identifying your port WWNs using the QCC GUI from Qlogic .................... L1-9
Configuring MPIO ................................................................................. L1-11
Lab 2 – Space Explained ................................................................................... L2-1

Introduction ........................................................................................... L2-1
Lab 1 – Installing the GUI and CLI ........................................................... L2-3
Lab 2 – Identifying space ....................................................................... L2-8
Lab 3 – Reclaiming space ..................................................................... L2-27
Lab 3 – Adaptive Optimization ...........................................................................L3-1

Introduction ...........................................................................................L3-1
Lab 1 – Installing the GUI and CLI ........................................................... L3-3
Lab 2 – Creating the AO configuration .................................................... L3-7
Lab 3 – Analyzing reports ..................................................................... L3-21
Lab clean-up ....................................................................................... L3-37
Answers ............................................................................................. L3-38
Lab 4 – Performance ........................................................................................ L4-1

Introduction .......................................................................................... L4-1
Lab 1 – Generating an I/O load ............................................................ L4-3
Lab 2 – CLI performance monitoring ........................................................ L4-9
Lab 3 – SR CLI performance monitoring .................................................. L4-16
Lab 5 – Rebalancing .........................................................................................L5-1

Introduction ...........................................................................................L5-1
Lab 1 – Preparing the CPG .................................................................... L5-2
Lab 2 – Preparing the volume ................................................................. L5-4
Lab 3 – Tuning and rebalancing using the CLI (preview) ............................. L5-5
Lab 4 – Tuning and rebalancing using the GUI (preview) ........................... L5-6
Lab 5 – Tuning and rebalancing ............................................................. L5-8
H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. i

Lab 6 – Upgrading .......................................................................................... L6-1

Introduction .......................................................................................... L6-1
Lab 1 – Using the HP Customer Self Repair Services Media
Library (optional)................................................................................... L6-2
Lab 2 – Verifying the Service Processor Software Level from SPMAINT ......... L6-3
Lab 3 – Verifying the HP 3PAR OS Software Level ..................................... L6-8
Lab 7 – Alerts ................................................................................................... L7-1

Introduction ........................................................................................... L7-1
Lab 1 – Viewing alerts (MC GUI) ............................................................. L7-2
Lab 2 – Viewing alerts (CLI) .................................................................... L7-4
Lab 3 – Viewing events (MC GUI) ........................................................... L7-6
Lab 4 – Viewing events (CLI) ................................................................... L7-8
Lab 5 – Internal System Reporter alerts .................................................... L7-10
Lab 6 – SNMP traps ............................................................................. L7-12
Lab 7 – SMI-S/CIM monitoring .............................................................. L7-14
Lab 8 – SPOCC email notifications ......................................................... L7-21
ii © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

Setting Up the Lab Environment
Lab 1
Objective
After completing this lab, you should be able to describe how to access the lab
equipment in the HPVL.
Introduction
In this lab, you are required to look at space, and two students will be accessing one
array simultaneously. Be aware that the space seen will be the cumulative space created
for both students.
Always use a unique name for any objects that you create in the lab.
Please only use the equipment allocated for your lab group.
On the landing page make a note of:
 Hosts names and IP address
 Array name and IP address
Note
Each team member can use their own Windows host (A or B). Please decide
within your teams.
The lab should be run on a clean array, so please confirm this is the case.
Should there be any objects created, other than the defaults, please remove them before
you start.
The screen shots in the lab guide are for illustration purposes only; do not use any names
or IP addresses displayed.
Always use a unique name for the objects you create; for example, TeamA-FCR1-full-10G
/ TeamAHostA.
H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. L1 – 1

Accessing the HP Virtual Labs

To get access to remote equipment using the HP Virtual Labs (HPVL):
1. Open a browser and go to http://www.hp.com/go/hpvl.
2. Select the Access Virtual Lab Environment link.
Note
Any HPVL access issues are detailed on the right. If you have access
problems, read the HPVL Access Notes carefully.
3. Enter the user name and password assigned to you by your instructor and click
Logon.
4. Note your login information here:
User name ........................................................................................................................
Password ..........................................................................................................................
L1 – 2 © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

5. Select HPVL Access – Windows user RDP web client or HPVL Access - Mac/Linux
Java client depending on how you are connecting to the HPVL.
6. A list of available lab groups appears. Select the lab group assigned to you by your
instructor (screen shot is for illustration only).

7. The launch page appears with Team A and Team B assigned equipment.
The left side of the screen displays pictures of the specific equipment assigned to
your team (screen shot is for illustration only).
The right side of the screen displays an explanation of the information, along with
the associated login user name and passwords, detailed as follows:
 Team A is the top 3PAR array with its assigned A and B hosts.
 Team B is the bottom 3PAR array with its assigned A and B hosts.
 Team A is the upper lab as shown in the screen shot.

8. To use a system link, click the drop-down box and select the resolution that you
want for your system RDP window.

Shadowing a user
In some instances, lab equipment will be shared. When this is done, one student may use
the Shadow User Session to “shadow” or observe the work done by another student. To
shadow another student:
1. Scroll down on the equipment page to locate the Shadow User Session information.
2. Click the Shadow User Session link.
3. Locate the session ID for that user. The session ID is located at the top of the Lab
Group page.
Enter the user name of the user to shadow. You will then be prompted to enter the
session ID. Enter the Session ID to complete the shadow operation.
(When you are finished for the day, you can use the EXIT LAB button to close your
lab session.)

Mapping the shared Y: drive

1. To map a drive called Y, select the Map network drive icon from My Computer and
select Y:.

2. Enter a path name \\192.168.XXX.250\hp3par\h9p97s.a

Where XXX is the third octet of your host/IP address “118.”
For example if your host IP = 192.168.118.187
You now see the contents of the Y: drive.

Identifying your port WWNs using the QCC GUI from Qlogic
1. Launch the QCC GUI desktop icon and then click Connect.
2. Click the “+” signs next to Port 1 and Port 2. Write down each of their port WWNs.
3. Launch the 3PAR Management Console desktop icon.

4. Select Hosts, and in Common Actions, click Create Host.
5. Use a unique naming format for your host, such as “TeamAHostA.”

6. Select the relevant host OS and WWNs from the lists and create the host.

Configuring MPIO
1. To set up and configure MPIO, open a command prompt window and run the
following commands:
dism /online /enable-feature /featurename:MultipathIo
Note
The “M” and last “I” in “MultipathIo” must be in uppercase.
mpclaim –n –i –a
Note
You might get a message:
Failed to update the registry for MSDSM support for the
device. Exiting…
The system cannot find the file specified.
Success, reboot required.
Disregard this message.
2. Enter mpclaim -e

3. Under the Target H/W Identifier column, you should see any HP 3PAR VLUNs
identified with “3PARdataVV.”
Note
The MPIO-ed column should display NO because a reboot is required to complete the
MPIO setup.
4. Reboot the server from the command prompt using the shutdown –r command.
5. Log on to the system.
6. Open a new command prompt window.
7. Enter the mpclaim –e command and view the results.
Note
The MPIO-ed column should display YES showing that MPIO is set up.

8. To reboot your Windows 2012 host, hover your mouse at the bottom right-hand
side of the screen until the “Cog” settings icon appears.
9. Select the Power icon and select restart to restart the host.
Installing iometer on Linux

Preparation
Enter yum install kernel-headers.x86_64 kernel-devel.x86_64

Enter yum install gcc.x86_64 gcc-c++.x86_64
Enter yum install libaio-devel.x86_64
Compiling iometer
Enter cd /tmp
Enter mkdir newiometer
Enter cd newiometer
Enter cp -pr /depot/iometer/iometer-1.1.0-src.tar.bz2./
Enter bzip2 –d iometer-1.1.0-src.tar.bz2
Note
In the preceding command, “–d” must include a dash. Copying and pasting converts
it incorrectly.
Enter tar –xvf iometer-1.1.0-src.tar

Enter cd iometer-1.1.0/src
Enter make -f Makefile-Linux.x86_64 all
Using iometer
Enter ./dynamo ? to get the options you want.


Space Explained
Module 2 Lab
Introduction
This lab coincides with the presentation for the “Space Explained” module. As you go
through the labs, keep the following in mind:
 Carefully read all of the steps in the guide to ensure your lab runs correctly.
 Concentrate on tasks that will help maximize your experience identifying and
differentiating space utilization.
 As two students will be sharing a lab the space seen will be cumulative space.
Objectives
After completing this module, you should be able to:
 Install both the 3PAR GUI and CLI
 Describe system space
 Identify physical disk chunklet space
 Differentiate raw and usable space
 Use Windows 2012 Unmap
 Describe the difference between allocated, failed, and free space
 Create volumes and define Adm, Snp, Usr, and Total space

Requirements
The following are the requirements for performing the lab:
 HP 3PAR StoreServ Storage Array
 HP 3PAR Management Console
 CLI or SSH access to 3PAR Array
 Approximately one hour for doing lab exercises
 HP 3PAR Command Line Interface Reference Guide
Lab procedures
! Important
The files you access on the system during this lab might also be used by other
classes. Please do not alter the information in any way.
If at any time you experience problems, please notify your instructor immediately.
Note:
Each team member can use their own Windows host (A or B) decide between you.
We want to run this Lab on a clean Array so please confirm this is the case.
Should there be any objects created, other than the defaults, please remove them before
you start.
If there are any hardware errors on the array the information displayed will not be
accurate, please let your instructor know.
The screen shots in the Lab guide are for illustration purposes only, do not use names or
IP address displayed.
Always use a unique name for the objects you create. E.g. TeamA-FCR1-full-10G or TeamAHostA
etc.

Space Explained
Lab 1 – Installing the GUI and CLI

Objectives
After completing this lab, you should be able to:
 Install the GUI and CLI
 Add a host using the QCC GUI
 Install MPIO on the host
Each team will perform their tasks individually.
Install the GUI and CLI

Log in to your assigned host in your team (A or B).
1. Install both the 3PAR Management Console Software and the 3PAR CLI, if not
preinstalled. This software can be found on the Z: drive.
You should find a shortcut to this drive on your desktop.
2. Open a session to the 3PAR CLI to your array.
Use only your assigned IP address and the following credentials to access your
array:
 Default user name: 3paradm
 Default password: 3pardata
If you are unable to remotely access your 3PAR array, please inform your instructor.
Remember to access the help system if you have difficulty or questions about any of
the commands you execute as part of this lab.
3. Open a session to the Management Console of your array.
array:
Adding a host using the QCC GUI

1. Use the QCC GUI icon on the desktop to find the WWNs for your host.

2. Launch the QCC GUI desktop icon and click Connect.

3. Click the “+” signs next to Port 1 and Port 2, and write down each of their port
WWNs.
4. Launch the 3PAR Management Console desktop icon.

5. Select Hosts, and in Common Actions, click Create Host.
6. Use a unique naming format for your host, such as “TeamAHostA.”

7. Select the relevant host operating system and WWNs from the lists and create the
host.

Space Explained
Installing MPIO on the host

1. On the desktop, right-click My Computer and select Manage.
2. Click Add roles and features.
3. Under Features, select Multipath I/O.

4. Select Tools MPIO.

Space Explained
5. Click Add and type 3PARdataVV and then click OK.
6. A reboot is now required. Type Yes.
Note
An alternative method using commands at a command prompt can be found in Lab 1.

Lab 2 – Identifying space

Objectives
 Describe system space
 Identify physical disk chunklet space
 Differentiate raw and usable space
 Describe the difference between allocated, failed, and free space
 Create volumes and define Adm, Snp, Usr, and Total space
Describing system space

1. From the GUI, select the View drop-down menu and Preferences, and change the
unit display to GB from MB.
This lab uses an F200 3PAR Array with Controller Node 0 and 1.

Space Explained
2. From the GUI, select the Inserv link in the Systems navigation window and the
Capacity tab.
Note the following:

Total space .......................................................................................................................
Total allocated space .......................................................................................................
Total free space ...............................................................................................................
FC allocated space ...........................................................................................................
FC free space ....................................................................................................................
NL allocated space ...........................................................................................................
NL free space....................................................................................................................
This new system is already displaying allocated space. Why is this?
(Hint: Failure protection.)
..........................................................................................................................................
..........................................................................................................................................

3. From the GUI, select the Inserv link in the Provisioning tab and the Summary tab.
Notice the “System Internal” space allocated.

System internal ................................................................................................................
Free space ........................................................................................................................
Notice the display shows two fully provisioned base volumes. What are these
volumes? ..........................................................................................................................
4. Select CPGs, and notice all of the CPGs are showing empty.

Space Explained
5. Select Virtual Volumes.
The admin and .srdata volumes are created at initialization of the 3PAR array along
with the default CPGs. This makes up most of the internal capacity along with
preserved and logging LDs.
What is the RAW capacity of the admin volume? ............................................................
What determines the size of the .srdata volume? ..........................................................
6. Select the CPG Space tab; notice that the two volumes space is not indicated
because they are part of the internal system space.

7. Click the Layout Grid button. You can now see the chunklet layout for the admin and
.srdata volumes.
8. Explore the admin volume chunklet layout from the GUI.
9. Explore the .srdata volume chunklet layout from the GUI.
Note: Do not click on the actual VV name or the view will change, select the VV from
under the state column to avoid this.

Space Explained
10. Select the Virtual Volumes tab and the Raw Capacity drop-down to see the total
space consumed by these two volumes.
What is the raw reserved user size? ................................................................................
Identifying physical disk chunklet space

1. Click the Systems button and open the Physical Disks tab.
Notice that the disks are displayed by cage. How many disks of each technology are
in this array, and what are their sizes? ............................................................................
..........................................................................................................................................

2. Select the Chunklet Usage drop-down to see how many 256 MB chunklets exist per
disk.
FC disk chunklets 2234 X 256 = 571GB for a 600 GB FC disk.
How many NL chunklets per disk? ...................................................................................
Notice the “Normal Used OK” column. This indicates the chunklets allocated to
internal space so far.
What does “Normal Unused Free” indicate?....................................................................

Position C.M.D. is the cage magazine and disk number of each of the physical disks.

Space Explained
The following screen shot shows “Normal Unused Uninit.” This indicates that a
volume has been deleted and its associated chunklets are being initialized. This
space does not become available again until the chunklets have been initialized, and
this can take some time.
The following screen shot shows the spare chunklet assignment on the right side of
the screen.
sho
What is the total number of FC spare chunklets? ...........................................................

What is the total number of NL spare chunklets? ...........................................................

Using CLI commands to display system capacity

1. From the CLI enter >showpd –c
The output provides an overview of how chunklets are used by the system.
Fill in the missing information for your system:
Total number of disks ......................................................................................................
Total chunklets ................................................................................................................
Currently used ..................................................................................................................
Number allocated for spare chunklets ............................................................................
Number free for VV creation ............................................................................................

Space Explained
Examining total system space and how it is mapped

1. From the CLI enter > showsys –space
On your system note the following:

Total capacity MB .............................................................................................................
Total allocated MB ...........................................................................................................
Total allocated is a combination of the used chunklets and spare chunklets. What
was the used and the spare chunklet total? ...................................................................
System internal MB ..........................................................................................................
This is the used internally for admin, .srdata, logging, and preserved data.
For example, in this system, admin and .srdata (20480 +122880) = 143360MB or
560ch raw capacity leaving 118784 MB or 464ch for Logging and Preserved.
When a new system is configured, it creates an admin, the .srdata volume, some LDs
dedicated as a logging area for servicemag operations, and Preserved Data LDs
dedicated for write updates in case of multiple failures within the same RAID set.
Before you create any volumes, you look at the space consumed by the admin and
.srdata volume.

2. From the CLI enter the following commands and note the results.
>showvv
This gives you the name and usable space allocated to your volumes.
>showvv –r
This indicates the raw capacity consumed by the volumes.

>showvv –d
The date on the showvv –d admin output can be used to determine when a
system was first installed.
Note
Rsvd (MB) Usr is usable capacity (.srdata is 60 GB and admin is 10 GB R1 volume).
RawRsvd (MB) Usr is total consumed space. In both cases, this is the total VSize of
the volume. No copy space is reserved.

Space Explained
Examining logical disks

1. From the CLI enter the >showld command.
 V—Logical disk is used for a virtual volume.

 C,V—Logical disk is used for a virtual volume created from a CPG.
 P,F—First logical disk is used for preserved data.
 P—Logical disk is used for preserved data.
 C,SA—Logical disk is used for the Snapshot Administration space for a common
provisioning group
 C,SD—Logical disk is used for the Snapshot Data space for a CPG.
 log—Logical disk is used as a logging logical disk.
The admin and .srdata use write-back cache.
The Log and Preserved LDs use write-through.

2. From the CLI enter >showld –vv admin
To see the LD map for Node 0 of your admin volume, enter

>showldmap admin.usr.0 (1)
The LD space shows the raw capacity for Node 0 and 1.
Creating a fully provisioned volume without copy space

1. Create a fully provisioned virtual volume. This virtual volume should be 10 GB with
no copy space CPG. Create this using a Fast Class, RAID 1 CPG.
Use any unique name format for your volume, such as:
TeamX-FCR1-full-10G-YY
Where X is your team and YY are your initials.
For example: TeamA-FCR1-full-10G-CS

Space Explained
2. From the GUI, look at the space for this new FPVV.
What is the virtual size of the volume? ...........................................................................
What is the total raw capacity?........................................................................................
Why is there a difference? ...............................................................................................
3. Enter the following CLI commands to view the volume:
>showvv
>showld –vv TeamX-FCR1-full-10G (use your VV name)
>Showvv –r
>Showvv –s
Why does Rsvd MB for Adm and Snp space = 0 MB? .......................................................
..........................................................................................................................................
In the showld command, why is the size displayed as 5120 MB? ................................
..........................................................................................................................................
4. From the CLI enter >showcpg –r
What is the estimated raw total capacity on your system for the FC CPGs?
..........................................................................................................................................
..........................................................................................................................................

5. Let’s look again at the chunklet usage. From the CLI enter >showpd –c
What is the change in used chunklets?............................................................................

6. From the CLI enter >showsys -space
Note the change in volumes ............................................................................................

Note the change in CPGs ..................................................................................................

Space Explained
Examining CPG default growth assignments

1. From the CLI enter the following commands:
>showcpg –sag
>showcpg –sdg
What is the difference in the information displayed for these two commands?
-sag ................................................................................................................................
-sdg ................................................................................................................................
2. From the >showld command, you see the logical disks for the new volume.
What is log0.0/log1.0? .....................................................................................................

What is pdsld0? ................................................................................................................
Hint: Refer to the “Space Explained” module.
3. Set copy space for your FCR1 volume. From either the GUI or the CLI, edit the volume
and assign a copy CPG
>setvv -snp_cpg FC_r1 TeamA-FCR1-full-10G

4. From the CLI enter >showld
tp-0 is an LD associated with the newly created copy space.

What is the total “SizeMB” for SA space?............(8GB see cpg -sag)
What is the total “UsedMB” for SA space?..........(128GB)
What is the total “SizeMB” for SD space?...........(32GB see cpg –sdg)
What is the total “UsedMB” space?.....................(512GB) (we do not see Raw space)
5. From the CLI enter the following commands:
>showvv
>showvv –r
>showvv -s
Why is Adm RawRsvd = 384 MB? .....................................................................................

Why is Snp RawRsvd = 1024 MB? ....................................................................................
With copy space enabled, you now see MB space allocated for Adm and Snp. We also
see the VV as “cpvv base” volume now not as before a “full base” volume.

Space Explained
6. From the CLI enter >showcpg –r
What is the Usr RTotal space for your volume and why? ................................................
What is the Snp RTotal space for your volume and why? ...............................................
What is the Adm RTotal space for your volume and why? ..............................................
Hint: Snp (SD) used a R1 ssz 2, and Adm (SA) used a R1 ssz3
Creating a thinly provisioned virtual volume and exporting to host

This virtual volume should be 10 GB with copy space. Create this using a Fast Class, RAID
1 CPG for user and copy space. Again, use a unique name format for your volume, such as
TeamX-FCR1-thin-10G.
For example: TeamA-FCR1-thin-10G
If not configured, enable MPIO on your host and verify the VLUN is visible to your host
(this might require a reboot). Do not initialize the volume at this point; you will do this
later.
Do this from either the GUI or the CLI.
1. From the CLI enter the following command:
>showvv –r
Note the following information about the thin volume:

Usr RawRsvd ....................................................................................................................
Tot RawRsvd ....................................................................................................................
Tot VSize ..........................................................................................................................

2. Again, examine the raw space for your CPG and volumes. From the CLI enter
>showcpg –r
3. Compare the total CPG space with the total VV space from the showvv command.
Notice the showvv –r command shows space for the admin and .srdata volume.
The showcpg –r command only shows space for user-created volumes in the
display.

Space Explained
Lab 3 – Reclaiming space

Objectives
 Explain default Snp and Adm allocation space
 Differentiate between used space and free space
 Describe the Windows 2012 Unmap feature
1. From the CLI enter >showcpg FC-r1
Notice that Snp Total is 32256 MB of space allocated (16 GB of space per node,
which is the SD R1 default growth increment).
Snp Total also shows 512 MB of “Usr Used” space per VV. This 512 MB is the first
allocation of LDs to the Volumes, comprising two 256 MB LDs, one from each node.
Under Adm Total, you see 8192 MB; this is the default SA space allocated. Of this,
only 128 MB is initially used to hold map pointer indexing information.

Examining space on the thin volume

1. From the CLI enter >showvv –s TeamX-FCR1-thin-10G
Where X is your team (A or B).
Note the following for your volume:

Adm Rsvd MB....................................................................................................................
Snp Rsvd MB .....................................................................................................................
Usr Used MB .....................................................................................................................
VSize .................................................................................................................................
(128 + 512 +512 = 1152MB)
You will need to initialize and format your thin 10G volume, assigning a drive letter
to it.
2. Use the same VV name for the volume name in Windows.

Space Explained
3. Go back to the CLI and enter the showvv –s command to identify your volume.
>showvv –s TeamX-FCR1-thin-10G
Where X is your team (A or B).
As soon as you present the VV to a Windows server and format it, notice 54 MB of
space is used by Windows for the file system.
Next, you will copy some data to your thin volume.
4. From the shared drive (Z:) on your host, copy the “Zero” folder to your 10G thin
volume.
This is about 1.9 GB in size, so it is fine for this example.

5. Go back and look at the CLI. From the CLI enter >showcpg FC_r1
Notice the Usr Total increased as the Snp Total decreased. Why? .................................
Hint: Initial allocated SD space .
6. Examine the thin volume. Enter >showvv –s TeamA-FCR1-thin-10G
Note the following for your volume:

Usr Rsvd MB......................................................................................................................
Usr Used MB .....................................................................................................................
7. Permenently delete the “Zero” folder from within the thin volume.
Notice Usr Used capacity decreases immediately but space has not been reclaimed
to the CPG yet.
Windows 2012 Unmap automaticallys unmap the used space from the volume.
Be patient. Reclamation can take some time to reduce the Usr Rsvd capacity
(3584MB), which indicates the space has been reclaimed back to the free pool.
Note
When the Usr Rsvd grows above 4 GB per node, reclaim will not reduce it below this
threshold.
8. Clean up your lab: Unexport and remove any LUNs and volumes you have created.

Adaptive Optimization
Module 3 Lab
Introduction
This lab coincides with module 3, “Understanding Adaptive Optimization Region Density
Reports.”
As you go through the labs, keep the following in mind:
 This Lab is completed in two separate components, Lab prep and the Analyze.
 Read and perform all of the steps that you can in the allowable time.
 Concentrate on those tasks that will help maximize your experience with using HP
3PAR Adaptive Optimization.
Objectives
After completing this lab, you should be able to perform the following tasks:
 Analyze region density reports to determine which Polices are a good fit for AO, and
which are not
 Create and schedule an Adaptive Optimization Configuration based on the region
density report analysis

Requirements
The following are the requirements for performing the lab:
 HP 3PAR StoreServ Storage array
 Windows 2008 or Windows 2012 server
 Python 2.7
 Java
 HP 3PAR Management Console
 CLI or SSH access to 3PAR array
 Approximately two hours for doing lab exercises
 HP 3PAR Command Line Interface Reference Guide
Lab procedures
! Important
The files you access on the system during this lab might also be used by other
classes. Please do not alter the information in any way.
If at any time you experience problems, please notify your instructor immediately.
Note
To reduce the potential from script failure, this lab is best run on a clean array.

Lab 1 – Installing the GUI and CLI

Objectives
 Map a network drive
 Install the GUI and CLI
 Confirm the array is clean
Note
This is only run once, so you need to work with your partner to complete the AO
preparation. One student should share their desktop and one should observe.
Mapping a network drive

1. From your lab group, log in to your assigned Windows host.
2. Double-click the My Computer desktop icon (notice a Z: drive is already mapped).
3. Map a new drive called “Y:” and select the Map network Drive icon.

4. Enter the path name \\192.168.XXX.250\hp3par\h9p97s.a

Where XXX is the third octet of your Host’s IP address “118.”
For example, Host = 192.168.118.187.
5. If you are prompted for a user name and password, speak to your instructor.
You now see the contents of the “Y:” drive. You will use this later to access the
aotraining_final.zip and Python-2.7.amd64.msi.

Installing the GUI and CLI

1. Open a session to the 3PAR CLI to your array.
Use only your 3PAR array assigned IP address and the following credentials to
access your array:
array:

Confirming the array is clean

1. Determine whether the array is clean to reduce potential script problems. From the
GUI, select Provisioning and then AO Configuration.
2. Remove any existing or default AO configurations.
3. Select Virtual Volumes and confirm there are no volumes other than admin/.srdata.
If any volumes do exist, unmount them from the host and then unexport and
remove them from the GUI.
4. Do not remove your existing host. You will use it in this lab. Make a note of your host
name and confirm that MPIO is installed; if not, set it now.

Lab 2 – Creating the AO configuration

Objectives
 Identify correct licensing
 Install the AO configuration script
 Launch Python
 Create a workload
 Verify the configuration
Note
This is only run once, so you need to work with your partner to complete the AO
preparation. One student should share their desktop and one should observe.
Identifying correct licensing

1. Familiarize yourself with the CLI Help system.
a. Enter help and review the output.
b. Practice by using help to learn more about the following commands that you
will use in this lab:
 help showcpg
 help showaocfg
 help sr
2. Verify that the system has an Adaptive Optimization license.
a. Enter showlicense
b. If Adaptive Optimization is not listed, do not continue, and let your instructor
know immediately.

3. Verify the CPGs on your system from either the CLI or GUI. (>showcpg)
Note
Allocated capacity is 0% because no volumes have been created on the array yet.
Installing the AO configuration script

1. Create a new directory in C:\ called “Perf.”

2. Select your Y: drive and right-click the aotraining_final.zip file.
3. Select Extract All and browse to the desktop.

4. Extract the aotraining_final.zip file to your desktop.

5. Open the aotraining_final folder on the desktop, and copy and paste the contents
into the “C:\Perf” folder.
6. Open the 3PAR_CLI_CMDS text file from within the \Perf folder.

7. Edit the file and use your Windows host name from your existing host; for example,
set host TeamAHostA
8. Copy all the contents from the 3PAR_CLI_CMDS.txt file and paste this into the CLI.
9. The commands will run and create two CPGs, if they do not already exist. Next, this
process creates five volumes, adding them to five virtual volume (VV) sets. It
creates the VLUNs as it exports the volumes as LUN 10, 12, 15, 16, and 25. It sets
the quality of service (QOS) rules and creates your aocfg “primary.”
You can now use Windows Disk Management to rescan for the new disks on your
host.

10. Right-click the Computer icon on the desktop and select Manage. From Server
Manager, select Tools  Computer Management  Disk Management.
11. Select the Actions drop-down menu and rescan. You should see your five LUNs.
Do not touch your disks at this time.
Exit Computer Management and Server Manager.
Launching Python
1. Locate the Python 2.7 folder on the Y: drive and copy it to your desktop. Double-
click the install icon.
2. Run the installer, selecting the default directory.
3. Select Next and accept the defaults. Click Finish.

4. Open a command window. Navigate from C:\cd Perf and confirm the ao_training and
LabPerfTool directories exist in the \Perf directory.
5. Change directory to \LabPerfTool and locate “fiox_discover.”

6. Enter C:\Python27/python fiox_discover to see the devices found.
Note
When you start a workload, it will verify that all of the expected LUNS are present.
So, even if you miss something here, the tool will check for you.
If a disk is missing, verify it is presented correctly from the array. In some rare cases,
you might have to reboot the Windows server.
Creating a workload
Now you will use Python to start the workload. First you must change directory from the
LabPerfTool directory to the C:\Perf\ao_training directory.
1. From a command prompt, enter >cd c:\perf\ao_training
2. Enter C:\Python27/python C:\Perf\LabPerfTool\aotest
aotraining.txt
Python runs the “aotest” using the input from ao_training.txt.

The aotest is a python utility that wraps the Vesper tool kit, to allow you to run and
schedule multiple, distinct workloads from a host over a 24-hour period.
The configuration text file you supplied defines all of the parameters required.

The workload configuration file has three sections.

 AOFILE—Name of the file that has the region density reports from the Region
Density Reports tab of the helper spreadsheet.
 WORKLOAD—Defines workload parameters to supply to fiox, which in turn
run Vesper.
 GROUP—Defines entities and schedules to run workloads against them.
You should now see the test start to run and the following output.
If your workload does not start, close the session and try again.
The Current Time stamp is a good indicator that the tool is working correctly.
You can leave this to work the disks, but remember, you do not want to stop this
from running overnight. When you complete the prep, exit the host using the X in
the upper right-hand side of the screen. Do not sign out of your host to exit because
this might stop Python.

Verifying the configuration

1. Enter showcpg –sdg to verify the CPGs.
2. Enter showvv to confirm the volumes.
3. Enter showvvset to confirm the VV sets.
4. Enter showvlun to verify the VLUNs.

5. Enter showhost to verify the host.
6. From the GUI, select Performance and Reports and create a new PD Usage chart for
PDs to verify a workload is running.

7. Under Objects, select the All checkbox.
8. Confirm the physical disks are all busy; you will come back and look at these again
later.
Looking at an AO configurations region I/O density report, should you see anything
at this point?
Let’s create an AO region density report in the MC GUI and see.

9. In Performance and Reports, select Report  AO Configuration  Region I/O

Density.

10. Accept the defaults and select your aocfg “primary” from the drop-down list.
Leave this now to produce some region I/O density information to review later.
11. When you finish, do not log off your host. Use the X to close the room, or you might
stop the collection.

Lab 3 – Analyzing reports

Objectives
 Analyze region density reports to determine which polices are a good fit for AO, and
which are not
 Create and schedule an Adaptive Optimization Configuration based on the region
density report analysis
 Create a new AO region density report
 Create a space moved report
 Set the preference for displaying logical disk information
You may perform these tasks individually.
1. Log back in to your assigned lab group (see module 1 for instructions).
2. Connect to the 3PAR array using both the 3PAR CLI and MC interface.
a. Use only your allocated array I/P address.
b. Default user name: 3paradm
c. Default password: 3pardata
If you cannot remotely access your 3PAR array, please inform your instructor.
3. Launch the MC GUI and Schedule AO.
4. In Provisioning, right-click AO Configuration and select Schedule AO.

5. Using Run Now, you can get the information collected already from the overnight
run. Select the Run Now radio button and the “primary” AO configuration from the
drop-down.
6. Click OK to continue.
This might take some time to run, so you will come back and look at this again later.
7. Next you are going to look at the CLI. Launch a session to the CLI if you have not
done already so.
8. View the current AO configuration on the system.

9. Enter showaocfg
a. You should see your AO Policy called “primary.”
b. The mode should be “Balanced.”
10. View the current list of scheduled activities.
11. Enter showsched –all

This command lists all scheduled tasks on the system and their schedule. Tasks that
are scheduled during out of the box include:
 check_slow_disk
 remove_expired_vvs
 move_back_chunklet
 sample
 checkiperfserver

12. The following are some of the input parameters necessary to start an Adaptive
Optimization schedule using the startao command. Enter help startao to
find the answers to the following questions:
a. What is the purpose of the –btsecs option?
..........................................................................................................................................
b. What is the purpose of the –etsecs option?
..........................................................................................................................................
c. What is the purpose of the –maxrun option?
..........................................................................................................................................
d. What is the purpose of the –compact option?
..........................................................................................................................................
e. What is the purpose of the –dryrun option?
..........................................................................................................................................
Analyzing region density reports

HP 3PAR region density reports contain data that can be used to understand how HP
3PAR Adaptive Optimization affects the system. Understanding and interpreting these
reports is an important skill to master.
The following section provides several examples of how to review this information using
the HP 3PAR CLI. It shows output from HP 3PAR Management Console and some System
Reporter commands.
1. To analyze the existing VVs, enter the showvvcpg command.
Notice the volumes that have capacity assigned from more than one CPG.
2. Explore these other CLI commands: srcpgspace, srldspace,and
srvvspace
Use the Help system for additional information.

3. Generate a region density report by using srrgiodensity and aocfg name
4. Generate a region density report by using

Using the results from your command:
a. How many hours does the output report?
b. How much capacity does each of your CPGs consume in MiB?
c. What is the average acc/min reported?
5. Looking at the 8192 region access bucket for FC disks, identify the following:
MiB ....................................................................................................................................
Acc/min ............................................................................................................................
6. You can use the output from this command to estimate the average number of IOPS
that a given CPG is being asked to deliver. This can help you set expectations for
performance.
The equation to compute this is:
/ ∗
∗
Compute the average IOPS for one of your CPGs.

For example: To compute the average IOPS for FC-r5
Space GiB = (3070976 / 1024) = 2999 GiB
Average Acc/(GiB*min) = 28.43
2999 ∗ 28.43
1421 /
60
This allows you to quickly see that this FC_r5 CPG is not working very hard.

7. Use the equation given in the previous step to compute the IOPs for your FC CPG.
..........................................................................................................................................
..........................................................................................................................................
..........................................................................................................................................
8. Use the region density command to create a report for your volumes:
srrgiodensity –withvv primary
9. Identify the VV that you think is putting the highest load on the system.
a. Do you believe the VV would benefit from having an SSD tier?
b. Would database .12 be a good fit for an NL tier or an FC tier?
10. To see how the host is viewing performance, enter srstatvlun –groupby
VV_name -attime
11. Notice this “at time” report shows IOPS and service times for your VLUNs.
Looking at the System reporter output from your array, are the VLUNs being driven
hard?

12. View a report for both of your CPGs.

srrgiodensity –cgp <names of each of your cpgs> primary
By default, the steps between the buckets are x4. Using your CLI reference guide,
write down the command you can use to change this.
13. Enter the sraomoves and showaocfg commands to see the mode and what
has moved over the last 24-hour period.
a. Initial data was moved from which tier to which tier?

..........................................................................................................................................
c. Initial data was moved from which CPG to which CPG?
..........................................................................................................................................
d. Notice the mode. How can you change this to Performance?
..........................................................................................................................................

14. Enter the srrgiodensity –cumul primary command.
15. What is the total cumulative space for the NL CPGs? Add each bucket below to
confirm.

Creating a new AO schedule

From the CLI_CMDS script you can see the time set for your AO configuration.
In the real world, you would want to set the begin time and end time (btsec/etsec) to
meet particularly busy periods of I/O.
1. Use help to create a new AO schedule from the CLI called “primary2_schedule” using
the following information.
Starting every day at 6 pm, start before time=9hr end before time= 1hr, max run
time=4hr, minimum iops=50
Write the syntax on the line provided below.
..........................................................................................................................................
Use help to understand the correct syntax for this command.
2. Display the scheduled information.
What is the –min_iops option used for?

Creating a new AO region density report

1. From Performance and Reports in the GUI, create a new AO region density report.
2. Select the “primary” AO configuration.
You will look at the VV, Cumulative, and Percentage metrics later.

3. From the AO “primary” configuration, you can see two charts.
In the graph on the left, you see space in MiB; notice most of the capacity is made up
from NL disks.
On the right, you see the I/O per minute; notice the highest access per minute
buckets serve FC disks.
Note
Your display might not look like this yet. Review this report again later in the course.
Using the information discussed in the “Theory” section, discuss these two charts
with your partner.
4. Create another report, but now select the VV metric.

5. Hover over the graph to display specific VV information. This is the same
information you saw in the CLI with the srrgiodensity –withvv primary
command.
6. Select the Metric check box for Cumulative for your “primary” aocfg. You could also
select to see this in a percentage format.

7. Using the information discussed in the “Theory” section, discuss these two charts
with your partner.
a. What is the total cumulative space for the FC disks?

..........................................................................................................................................
b. What is the total cumulative I/O for the FC disks?
..........................................................................................................................................

Creating a space moved report

1. From Performance and Reports, create a space moved report.
Notice the graphs show this as both cumulative and noncumulative moves.
2. Analyze the movement of data between the two tiers, and compare this to the CLI
output.

3. After AO moves data, look at the physical disks again, and then go back and
compare it with what you saw earlier below.
Over time, as AO moves region data, if you look at the physical disk, you should see
a change in the distribution of the I/O load.

Setting the preference for displaying logical disk information

1. From the View drop-down menu, select Preferences and then the Advanced tab.
Check the box to Show logical disks and click Apply.

2. Select Provisioning and then Virtual Volume using the CPG Space tab. Notice the
volumes are distributed over two CPGs.
Which CPGs do you see displayed for VV application.25?

Look at the Logical Disks tab; notice application.25 has space on LDs from other
volumes.
Note
The tp-4-sb-0.0 object is a special “shared base” LD used in AO when creating
additional VV space.
Lab clean-up
Stop all schedules and remove your AO configuration. Unexport and remove any volumes
you have created.
Note
It will take some time for all the used chunklets to be initialized after the volumes
have been deleted.

Answers
-btsecs <secs>
Select the begin time in seconds for the report.
-etsecs <secs>
Select the end time in seconds for the report.
-maxrunh <hours>
Select the approximate maximum run time in hours
-min_iops <min_iops>
Do not execute the region moves if the average IOPS during the measurement interval is
less than <min_iops>.
-compact <mode>
Specify if and how CPGs should be compacted.
dryrun
Do not execute the region moves; only show which moves would be done.
-cmult 2|4|8
Select the step between histogram columns of the report.
Starting every day at 6 pm, start before time=9hr end before time= 1hr, max run
time=4hr, minimum iops=50
“startao -btsecs -9h –etsecs -1h -maxrunh 4 -min_iops 50
primary" "0 18 * * *" primary2_schedule

Performance
Module 4 Lab
Introduction
This lab coincides with module 4, “Understanding Performance.”
Objectives
 Use the GUI to create a host and export volumes
 Use the GUI to create two volumes to work with IOmeter
 Generate a workload and analyze performance.
Requirements
To complete this lab, you will need:
 HP 3PAR StoreServ system
 Microsoft Windows Host
 Management Console and GUI
Preparing the lab

1. Log in to your assigned host.
2. Install both the 3PAR Management Console Software and the 3PAR CLI, if not
already installed. This software can be found on the Z: drive.
You should find a shortcut to this drive on your desktop.
array:
If you cannot remotely access your 3PAR array, please inform your instructor.
Remember to access the Help system if you have difficulty or questions about any
of the commands you execute as part of this lab.

4. First we will create two new volumes:

 1 X 10G full volume from FC_r1 CPG called fpvv1_HostX. where X is your host
 1 X 10G full volume from NL_r6 CPG called fpvv2_HostX, where X is your host
5. Export both volumes to your host.

6. Rescan your host for your new volumes and format them assigning a drive letter to
each.
7. You will use these volumes later as workers for IOmeter to run some loads against.

Performance
Lab 1 – Generating an I/O load

Objectives
Use IOmeter to generate an I/O load to an HP 3PAR StoreServ system.
Requirements
To complete this lab, you will need:
 HP 3PAR StoreServ system
 Microsoft Windows Host
 IOmeter
Generating an I/O load

1. From the Z: shared drive, copy the IOmeter folder to the desktop.
2. Open the folder and run the IOmeter.exe, and then click Next.

3. Accept the License agreement and click Next. Accept all the defaults and click
Finish.
4. Click the Start Menu button on the bottom left of your 2012 Windows host.
5. Select the down arrow to get to the main menu page.

Performance
6. Find the IOmeter tool and double-click to run it.
7. Select Worker 1 and, in the Disk Targets tab, select your first volume and set the #
of Outstanding I/Os to 4.

8. Select the Access Specifications tab and create a new specification called 8KB; 50%
Read; 100% Random with the following settings.
9. Assign the new specification to the worker.

Performance
10. Select Worker 2 and, in the Disk Targets tab, select the second volume and set the #
of Outstanding I/Os to 2.
11. Select the Access Specifications tab and create a new specification called 512KB;
75% Read; 100% Random with the following settings.

12. Assign the new specification to the worker.
13. Click the green flag to start the test.

Performance
Lab 2 – CLI performance monitoring

Objectives
Use the CLI to monitor HP 3PAR StoreServ performance.
Requirements
To complete this lab, you need CLI access to the HP 3PAR StoreServ system.
HP 3PAR OS has a wealth of performance monitoring commands available from the CLI.
You can view live data using the stat* and hist* commands.
There are six layers to check:
 Host VLUNs
 Host ports
 Node cache
 Node volumes
 Disk ports
 Disks

Monitoring HP 3PAR StoreServ performance

1. Run statport -host -rw –ni to view the front end performance.
Note how the stat commands show the mean values over the sample period.
For example, if there were 4 x 4 KB I/Os each taking 1 ms and 1 x 1 MB I/O taking 20
ms in a sample period, the stat commands would say there were 5 x 208 KB I/Os
taking 4.8 ms, each even though no I/O was that size or took that long to complete.
Note
Screenshots are for illustration only.
cli% statport -host -rw –ni

21:50:03 05/27/2014 r/w I/O per second KBytes per sec SvtmsIOSz KB
Port D/C Cur Avg Max Cur Avg Max Cur Avg Cur AvgQlen
2:5:1 Data r 63 67 75 10995 14086 17726 5.20 5.36 173.5 208.9 -
2:5:1 Data w 38 46 51 5167 4805 6502 26.39 22.75 135.5 104.0 -
2:5:1 Data t 101 114 120 16162 18891 21414 13.16 12.44 159.2 166.2 1
2:5:2 Data r 65 67 73 13311 13932 15853 5.78 5.85 203.7 208.6 -
2:5:2 Data w 38 47 52 3119 4981 6541 26.15 22.85 82.9 106.2 -
2:5:2 Data t 103 114 121 16430 18913 21414 13.22 12.86 159.5 166.3 0
3:5:1 Data r 55 63 75 12211 13754 16643 7.53 5.39 220.2 217.6 -
3:5:1 Data w 47 50 54 3963 5138 6810 26.67 22.87 84.2 101.8 -
3:5:1 Data t 103 114 120 16174 18892 21414 16.31 13.15 157.8 166.2 1
3:5:2 Data r 57 64 74 11712 14312 17118 6.54 5.93 205.7 224.4 -
3:5:2 Data w 45 50 55 4458 4580 5786 26.09 22.44 98.9 91.7 -
3:5:2 Data t 102 114 120 16170 18892 21406 15.17 13.18 158.5 166.1 2
-------------------------------------------------------------------------------------
4 Data r 241 261 48229 56085 6.21 5.63 200.0 214.7 -
4 Data w 168 194 16708 19503 26.33 22.72 99.5 100.8 -
4 Data t 409 455 64936 75588 14.47 12.91 158.8 166.2 4
2. Run histport -host -rw -ni –prevto show how many I/Os were within
which service time and size buckets during the sample period.
cli% histport -host -rw -ni -prev
22:07:04 05/27/2014 ----------Time (millisec)----------- ------------Size (bytes)------------
Port D/C r/w 0.50 1 2 4 8 16 32 64 128 256 4k 8k 16k 32k 64k 128k 256k 512k 1m
2:5:1 data r 36 2 26 52 24 3 0 0 0 0 0 83 0 0 0 0 0 60 0
2:5:1 data w 1 0 0 0 35 41 12 0 0 0 0 79 0 0 0 0 0 10 0
2:5:1 data t 37 2 26 52 59 44 12 0 0 0 0 162 0 0 0 0 0 70 0
2:5:2 data r 28 9 29 36 24 8 0 0 0 0 0 86 0 0 0 0 0 48 0
2:5:2 data w 0 0 0 2 29 49 16 0 0 0 0 75 0 0 0 0 0 21 0
2:5:2 data t 28 9 29 38 53 57 16 0 0 0 0 161 0 0 0 0 0 69 0
3:5:1 data r 30 6 24 30 28 6 0 0 0 0 0 80 0 0 0 0 0 44 0
3:5:1 data w 1 0 0 0 25 68 15 0 0 0 0 82 0 0 0 0 0 27 0
3:5:1 data t 31 6 24 30 53 74 15 0 0 0 0 162 0 0 0 0 0 71 0
3:5:2 data r 24 7 17 41 27 5 0 0 0 0 0 71 0 0 0 0 0 50 0
3:5:2 data w 0 0 0 1 39 62 11 0 0 0 0 92 0 0 0 0 0 21 0
3:5:2 data t 24 7 17 42 66 67 11 0 0 0 0 163 0 0 0 0 0 71 0
---------------------------------------------------------------------------------------------
total data r 118 24 96 159 103 22 0 0 0 0 0 320 0 0 0 0 0 202 0
total data w 2 0 0 3 128 220 54 0 0 0 0 328 0 0 0 0 0 79 0
total data t 120 24 96 162 231 242 54 0 0 0 0 648 0 0 0 0 0 281 0
What does the –prev option do in this command?

Performance
3. The histogram commands can also show percentages instead of I/O counts.
histport -host -metric size -iter 1 –pct
cli% histport -host -metric size -iter 1 -pct

07:19:30 05/28/2014 ----------Size (bytes) %-----------
Port D/C 4k 8k 16k 32k 64k 128k 256k 512k 1m
2:3:1 data 0 0 0 0 0 0 0 0 0
2:3:2 data 0 0 0 0 0 0 0 0 0
2:5:1 data 0 68 0 0 0 0 0 32 0
2:5:2 data 0 67 0 0 0 0 0 33 0
3:3:1 data 0 0 0 0 0 0 0 0 0
3:3:2 data 0 0 0 0 0 0 0 0 0
3:5:1 data 0 68 0 0 0 0 0 32 0
3:5:2 data 0 67 0 0 0 0 0 33 0
-------------------------------------------------------
total data 0 67 0 0 0 0 0 33 0
4. Run statvlun -ni -sortcol 1 to show the per path front-end performance.
cli% statvlun -ni -sortcol 1

LunVVnameHost Port Cur Avg Max Cur Avg Max Cur Avg Cur AvgQlen
0 fpvv1myhost 2:5:1 t 75 75 75 611 611 611 12.55 12.55 8.2 8.2 0
0 fpvv1myhost 3:5:2 t 75 75 75 611 611 611 12.64 12.64 8.2 8.2 1
0 fpvv1myhost 2:5:2 t 74 74 74 607 607 607 13.80 13.80 8.2 8.2 2
0 fpvv1myhost 3:5:1 t 75 75 75 611 611 611 13.75 13.75 8.2 8.2 1
1 fpvv2myhost 2:5:1 t 35 35 35 18246 18246 18246 14.43 14.43 524.3 524.3 1
1 fpvv2myhost 3:5:2 t 36 36 36 18760 18760 18760 13.51 13.51 524.3 524.3 0
1 fpvv2myhost 2:5:2 t 35 35 35 18497 18497 18497 11.45 11.45 524.3 524.3 1
1 fpvv2myhost 3:5:1 t 36 36 36 18758 18758 18758 15.53 15.53 524.3 524.3 0
-----------------------------------------------------------------------------------------
8 t 439 439 76700 76700 13.36 13.36 174.6 174.6 6
5. Run histvlun -ni -prev -sortcol 1 to show the histograms of service

time and block size per path.
cli% histvlun -ni -prev -sortcol 1
22:21:34 05/27/2014 ----------Time (millisec)----------- ------------Size (bytes)------------
LunVVname Host Port 0.50 1 2 4 8 16 32 64 128 256 4k 8k 16k 32k 64k 128k 256k 512k 1m
0 fpvv1 myhost 2:5:1 32 2 6 29 43 43 6 0 0 0 0 161 0 0 0 0 0 0 0
0 fpvv1 myhost 3:5:2 29 5 7 18 46 51 5 0 0 0 0 161 0 0 0 0 0 0 0
0 fpvv1 myhost 2:5:2 29 8 9 19 44 41 9 0 0 0 0 159 0 0 0 0 0 0 0
0 fpvv1 myhost 3:5:1 35 0 5 23 48 40 7 1 0 0 0 159 0 0 0 0 0 0 0
1 fpvv2myhost 2:5:1 0 0 11 17 14 17 7 1 0 0 0 0 0 0 0 0 0 67 0
1 fpvv2myhost 3:5:2 0 0 13 21 12 12 7 1 0 0 0 0 0 0 0 0 0 66 0
1 fpvv2myhost 2:5:2 0 0 14 25 9 11 8 0 0 0 0 0 0 0 0 0 0 67 0
1 fpvv2myhost 3:5:1 0 0 9 18 11 19 10 0 0 0 0 0 0 0 0 0 0 67 0
-------------------------------------------------------------------------------------------------
total 125 15 74 170 227 234 59 3 0 0 0 640 0 0 0 0 0 267 0

6. Run statcmp to show the cache performance data.

cli% statcmp
07:14:38 05/28/2014 ---- Current ----- --------- Total ----------
Node Type Accesses Hits Hit% Accesses Hits Hit% LockBlk
0 Read 0 0 0 0 0 0 1
0 Write 0 0 0 0 0 0 3
1 Read 0 0 0 0 0 0 0
1 Write 0 0 0 0 0 0 172
Queue Statistics
Node Free Clean Write1 WriteNWrtSched Writing DcowPendDcowProcRcpyRev
0 31185 404457 0 0 0 0 0 0 0
1 31139 405195 0 0 0 0 0 0 0
Temporary and Page Credits

Node Node0 Node1 Node2 Node3 Node4 Node5 Node6 Node7
0 0 30897 --- --- --- --- --- ---
1 30179 0 --- --- --- --- --- ---
Page Statistics
---------CfcDirty--------- ------------CfcMax------------- -----------DelAck-----------
Node FC_10KRPM FC_15KRPM NL SSD FC_10KRPM FC_15KRPM NL SSD FC_10KRPM FC_15KRPM NL SSD
0 0 0 0 0 0 135064 10389 60259 0 69841 0 0
1 0 0 0 0 0 135064 10389 60259 0 310990 0 53768
00:14:42 04/10/2014 ---- Current ----- --------- Total ----------

Node Type Accesses Hits Hit% Accesses Hits Hit% LockBlk
0 Read 0 0 0 0 0 0 1
0 Write 4 0 0 4 0 0 3
1 Read 0 0 0 0 0 0 0
1 Write 0 0 0 0 0 0 172
Queue Statistics
Node Free Clean Write1 WriteNWrtSched Writing DcowPendDcowProcRcpyRev
0 31189 404457 0 0 0 0 0 0 0
1 31134 405195 0 0 0 0 0 0 0
Temporary and Page Credits

Node Node0 Node1 Node2 Node3 Node4 Node5 Node6 Node7
0 0 30893 --- --- --- --- --- ---
1 30183 0 --- --- --- --- --- ---
Page Statistics
---------CfcDirty--------- ------------CfcMax------------- -----------DelAck-----------
Node FC_10KRPM FC_15KRPM NL SSD FC_10KRPM FC_15KRPM NL SSD FC_10KRPM FC_15KRPM NL SSD
0 0 0 0 0 0 135064 10389 60259 0 69841 0 0
1 0 0 0 0 0 135064 10389 60259 0 310990 0 53768
7. Run statvv -ni –rw to show the VV performance.

Why is there a difference between this and the statvlun output?
..........................................................................................................................................
cli% statvv -ni -rw

VVnameCur Avg Max Cur Avg Max Cur Avg Cur AvgQlen
fpvv1 r 114 114 114 933 933 933 6.95 6.95 8.2 8.2 -
fpvv1 w 161 161 161 1322 1322 1322 18.62 18.62 8.2 8.2 -
fpvv1 t 275 275 275 2254 2254 2254 13.79 13.79 8.2 8.2 3
fpvv2 r 46 46 46 23849 23849 23849 7.29 7.29 523.8 523.8 -
fpvv2 w 36 36 36 18682 18682 18682 29.97 29.97 517.1 517.1 -
fpvv2 t 82 82 82 42531 42531 42531 17.33 17.33 520.8 520.8 1
-------------------------------------------------------------------------------------
2 r 159 159 24781 24781 7.05 7.05 155.5 155.5 -
2 w 197 197 20004 20004 20.70 20.70 101.3 101.3 -
2 t 357 357 44786 44786 14.60 14.60 125.5 125.5 4

Performance
8. Run statld -ni –rw to show the LD performance. Note the difference in the
relationship between the LD and VV performance.
cli% statld -ni -rw

LdnameCur Avg Max Cur Avg Max Cur Avg Cur AvgQlen
fpvv1.usr.0 r 43 43 43 799 799 799 6.65 6.65 18.5 18.5 -
fpvv1.usr.0 w 81 81 81 648 648 648 18.87 18.87 8.0 8.0 -
fpvv1.usr.0 t 124 124 124 1447 1447 1447 14.62 14.62 11.6 11.6 0
fpvv2.usr.0 r 29 29 29 480 480 480 6.82 6.82 16.6 16.6 -
fpvv2.usr.0 w 48 48 48 9916 9916 9916 21.74 21.74 205.4 205.4 -
fpvv2.usr.0 t 77 77 77 10396 10396 10396 16.16 16.16 134.8 134.8 2
fpvv1.usr.2 r 41 41 41 750 750 750 6.69 6.69 18.4 18.4 -
fpvv1.usr.2 w 87 87 87 709 709 709 20.05 20.05 8.1 8.1 -
fpvv1.usr.2 t 128 128 128 1460 1460 1460 15.79 15.79 11.4 11.4 3
fpvv2.usr.1 r 22 22 22 375 375 375 7.92 7.92 16.7 16.7 -
fpvv2.usr.1 w 42 42 42 9655 9655 9655 22.88 22.88 228.2 228.2 -
fpvv2.usr.1 t 65 65 65 10030 10030 10030 17.70 17.70 155.0 155.0 0
-------------------------------------------------------------------------------------
4 r 135 135 2404 2404 6.91 6.91 17.8 17.8 -
4 w 259 259 20929 20929 20.46 20.46 80.9 80.9 -
4 t 394 394 23333 23333 15.81 15.81 59.2 59.2 5
9. Run statport -disk –ni to show the back-end performance.
cli% statport -disk -ni

Port D/C Cur Avg Max Cur Avg Max Cur Avg Cur AvgQlen
2:0:1 Data t 217200 217 9877 8377 9877 17.88 18.26 45.6 41.9 4
2:0:2 Data t 229204 232 9954 9165 10064 18.11 19.02 43.5 44.9 4
2:0:3 Data t 206193 214 9446 8798 9796 17.64 18.75 45.9 45.6 3
2:0:4 Data t 208193 208 9221 8709 10225 18.03 18.22 44.3 45.2 1
3:0:1 Data t 200198 213 8167 8277 9621 17.25 18.39 40.7 41.9 1
3:0:2 Data t 215200 215 9829 9098 10143 20.87 19.09 45.8 45.5 4
3:0:3 Data t 192190 197 9161 8701 9836 19.26 18.78 47.7 45.7 7
3:0:4 Data t 185191 207 8407 8616 10042 18.51 18.20 45.5 45.1 6
-----------------------------------------------------------------------------------
8 Data t 1652 15697406269741 18.25 18.67 44.0 44.3 30

10. Run histport -disk -metric time -timecols 3 13 -ni -iter 1

–pct to show the back-end performance histogram.
cli% histport -disk -metric time -timecols 3 13 -ni -iter 1 -pct

07:21:15 05/28/2014 ------------Time (millisec) %------------
Port D/C 0.062 0.125 0.25 0.50 1 2 4 8 16 32 64
2:0:1 data 0 0 1 0 2 13 47 29 7 2 0
2:0:2 data 0 0 0 0 6 15 44 27 6 2 0
2:0:3 data 0 0 0 0 5 13 55 21 5 1 1
2:0:4 data 0 0 0 0 2 15 52 24 6 0 0
3:0:1 data 0 0 1 0 3 12 47 30 7 0 0
3:0:2 data 0 0 0 0 3 11 46 33 7 1 0
3:0:3 data 0 0 0 0 4 10 45 34 7 0 0
3:0:4 data 0 0 0 0 3 18 38 31 9 1 0
-------------------------------------------------------------
total data 0 0 0 0 3 13 47 29 7 1 0
What does the –metric time option do in this command?

..........................................................................................................................................
11. Run statpd –ni to show the performance of the individual physical disks.
cli% statpd -ni

22:37:14 05/27/2014 r/w I/O per second KBytes per sec SvtmsIOSz KB Idle %
ID Port Cur Avg Max Cur Avg Max Cur Avg Cur AvgQlen Cur Avg
0 2:0:1 t 92 92 92 3372 3372 3372 9.20 9.20 36.7 36.7 2 49 49
1 3:0:1 t 62 62 62 2901 2901 2901 6.93 6.93 46.8 46.8 0 67 67
2 2:0:1 t 68 68 68 2822 2822 2822 8.46 8.46 41.8 41.8 0 58 58
3 3:0:1 t 81 81 81 3131 3131 3131 7.45 7.45 38.5 38.5 1 53 53
8 2:0:2 t 73 73 73 2959 2959 2959 7.76 7.76 40.5 40.5 0 59 59
9 3:0:2 t 63 63 63 3081 3081 3081 8.11 8.11 48.9 48.9 2 60 60
10 2:0:2 t 73 73 73 2946 2946 2946 7.07 7.07 40.1 40.1 0 60 60
11 3:0:2 t 82 82 82 3310 3310 3310 8.89 8.89 40.4 40.4 1 50 50
16 2:0:3 t 56 56 56 2755 2755 2755 7.93 7.93 49.6 49.6 1 65 65
17 3:0:3 t 78 78 78 3150 3150 3150 7.95 7.95 40.2 40.2 0 55 55
18 2:0:3 t 65 65 65 3230 3230 3230 7.11 7.11 50.1 50.1 2 66 66
19 3:0:3 t 75 75 75 3097 3097 3097 8.68 8.68 41.3 41.3 0 55 55
24 2:0:4 t 76 76 76 2845 2845 2845 7.13 7.13 37.2 37.2 0 57 57
25 3:0:4 t 76 76 76 2910 2910 2910 6.98 6.98 38.1 38.1 2 57 57
26 2:0:4 t 83 83 83 2985 2985 2985 7.87 7.87 36.0 36.0 0 53 53
27 3:0:4 t 71 71 71 2816 2816 2816 8.06 8.06 39.7 39.7 0 57 57
----------------------------------------------------------------------------------------
16 t 1174 1174 48312 48312 7.88 7.88 41.1 41.1 11 57 57

Performance
12. Run histpd to show the physical disk performance histogram. Drives with
problems might show as having high service times, such as disk ID 12 in this
example.
histpd -begin -metric time -timecols 7 17
cli% histpd -begin -metric time -timecols 7 17
10:24:43 05/30/2014 ----------------------------------Time (millisec)-----------------------------------
ID Port 1 2 4 8 16 32 64 128 256 512 1024
0 2:0:1 1040219 1392895 4067299 2757178 984548 302443 25925 827 67 6 7
1 3:0:1 1122139 1307977 3423012 2456079 806372 183864 13639 219 95 2 0
2 2:0:1 1007735 1127368 3169929 2366545 946025 233820 19296 868 84 4 0
3 3:0:1 949133 1047523 2838237 2072470 698932 156665 10281 157 82 1 0
4 2:0:1 236377 242713 994700 2069592 2144104 816707 136889 15494 2247 155 1
5 3:0:1 252 1298 2990 3743 3171 237 242 2 0 1 0
6 2:0:1 361107 284493 996177 2064123 2083380 762595 128421 14109 1862 180 1
7 3:0:1 232 1332 2946 3728 3206 262 225 4 0 1 0
8 2:0:2 1051677 1462750 4100316 2701323 923593 257723 18986 456 75 2 0
9 3:0:2 1054873 1306253 3373968 2422335 799063 187682 13787 212 60 1 0
10 2:0:2 1003054 1144904 3168218 2316856 927121 222431 16181 492 55 1 0
11 3:0:2 1018665 1024505 2828151 2073347 737502 178162 12236 167 71 1 0
12 2:0:2 225827 253337 997559 2103759 2295947 1005521 209611 36235 9466 2483 563
13 3:0:2 212 1372 2928 3717 3219 241 245 1 0 1 0
14 2:0:2 207482 261416 989367 2221532 2122266 728582 117343 11850 1503 84 0
15 3:0:2 221 1328 2916 3898 3078 243 248 2 1 1 0
16 2:0:3 930615 1025008 3181826 2065434 1003170 376687 41698 1186 208 34 3
17 3:0:3 969324 1003344 2802503 2090883 882572 235328 17895 623 199 37 1
18 2:0:3 993937 1056112 3241011 2092095 982181 331125 37219 1195 201 15 1
19 3:0:3 902457 969896 2924303 2088651 864549 215436 15621 608 280 36 3
20 2:0:3 246403 245539 979054 2079587 2074647 759260 125239 13960 1868 135 1
21 3:0:3 205 1349 2923 3861 3119 242 234 2 0 1 0
22 2:0:3 256111 258092 938556 2119629 2245540 844884 138018 15201 2155 148 4
23 3:0:3 231 1368 2900 3528 3394 269 241 4 0 1 0
24 2:0:4 1009471 1009702 3223415 2080333 1013668 352243 40046 1227 191 44 1
25 3:0:4 942933 958498 2791930 2085314 887026 251707 20231 667 334 59 6
26 2:0:4 937312 1072750 3206402 2059940 962558 312533 29377 930 126 6 0
27 3:0:4 903262 981929 2854549 2065019 861358 223842 16966 629 295 50 5
28 2:0:4 307156 264668 1016294 2137239 2030865 706681 117186 12954 1875 149 1
29 3:0:4 224 1362 2959 3638 3299 215 235 3 0 1 0
30 2:0:4 230027 268568 985463 2077706 2092737 770056 121769 12578 1690 99 1
--------------------------------------------------------------------------------------------------------
total 17908873 19979649 59112801 52693082 31392210 10417686 1445530 142862 25090 3739 599

Lab 3 – SR CLI performance monitoring

Performance data is also continuously captured by the on-node System Reporter
software. You can view this historical data using the sr* commands. Note that the “hi-
res” SR data is captured at five-minute sample intervals.
1. Run srstatport -btsecs -30m to view the port performance. Note how the
data is an average of all the front-end and back-end ports.
cli% srstatport -btsecs -30m
------IOPs/s------ --------KBytes/s-------- --Svctms--- -IOSzKBytes--
Time Secs Rd Wr Tot Rd WrTot RdWr Tot Rd Wr Tot QLenAvgBusy%
2014-05-27 22:05:00 BST 1401224700 868.5 795.1 1663.7 77279.9 51035.7 128315.6 6.9 12.0 9.3 89.0 64.2 77.1 8.0 43.8
2014-05-27 22:10:00 BST 1401225000 868.1 793.7 1661.8 77000.7 50971.1 127971.8 6.9 12.0 9.3 88.7 64.2 77.0 6.0 43.7
2014-05-27 22:15:00 BST 1401225300 868.6 790.2 1658.8 77306.2 50434.1 127740.3 6.9 12.0 9.4 89.0 63.8 77.0 5.0 43.6
2014-05-27 22:20:00 BST 1401225600 874.8 796.8 1671.6 78038.9 51162.3 129201.2 6.9 11.9 9.3 89.2 64.2 77.3 8.0 43.8
2014-05-27 22:25:00 BST 1401225900 857.8 780.7 1638.5 76706.0 50213.3 126919.2 7.1 12.1 9.5 89.4 64.3 77.5 7.0 43.6
2014-05-27 22:30:00 BST 1401226200 856.2 763.1 1619.2 78488.8 49343.6 127832.4 7.5 12.5 9.8 91.7 64.7 78.9 2.0 44.0
------------------------------------------------------------------------------------------------------------------------
6 865.7 786.6 1652.3 77470.1 50526.7 127996.8 7.0 12.1 9.4 89.5 64.2 77.5 6.0 43.8
2. Run srstatvlun -btsecs -30m to view the VLUN performance.

Note how the data is an average of all the VLUNs.
cli% srstatvlun -btsecs -30m
-----IOPs/s------ -------KBytes/s-------- ---Svctms--- ---IOSzKBytes---
Time Secs Rd Wr Tot Rd Wr Tot Rd Wr Tot Rd Wr Tot QLenAvgBusy%
2014-05-27 22:15:00 BST 1401225300 266.7 194.7 461.4 56802.7 19579.5 76382.2 5.6 22.5 12.7 213.0 100.5 165.5 1.0 62.8
2014-05-27 22:20:00 BST 1401225600 267.7 196.4 464.1 57333.3 19891.4 77224.7 5.5 22.3 12.6 214.1 101.3 166.4 7.0 62.9
2014-05-27 22:25:00 BST 1401225900 263.7 192.0 455.7 56373.1 19508.3 75881.4 5.7 22.7 12.9 213.8 101.6 166.5 0 62.7
2014-05-27 22:30:00 BST 1401226200 255.5 186.9 442.4 55002.6 19168.3 74170.9 5.8 23.5 13.3 215.3 102.5 167.6 1.0 62.7
2014-05-27 22:35:00 BST 1401226500 264.7 196.4 461.1 56214.7 19861.2 76075.8 5.6 22.3 12.7 212.4 101.1 165.0 2.0 62.9
2014-05-27 22:40:00 BST 1401226800 260.0 192.3 452.3 55790.5 19584.8 75375.2 5.7 22.8 13.0 214.6 101.8 166.7 3.0 62.8
--------------------------------------------------------------------------------------------------------------------------
6 263.1 193.1 456.2 56252.8 19598.9 75851.7 5.6 22.7 12.9 213.9 101.5 166.3 2.3 62.8

Performance
3. Run srstatvlun -btsecs -30m -vv XXXX where XXXX is your VLUN name.
Note how the data is an average of all the VLUNs of the VV.
cli% srstatvlun -btsecs -30m -vv fpvv1
-----IOPs/s------ ------KBytes/s------ ---Svctms--- -IOSzKBytes-
Time Secs Rd Wr Tot Rd WrTot RdWr Tot Rd Wr Tot QLenAvgBusy%
2014-05-27 22:15:00 BST 1401225300 160.8 159.9 320.7 1317.7 1309.7 2627.4 4.7 19.9 12.2 8.2 8.2 8.2 0 78.6
2014-05-27 22:20:00 BST 1401225600 160.9161.0 321.9 1318.1 1318.6 2636.7 4.7 19.7 12.2 8.2 8.2 8.2 5.0 78.8
2014-05-27 22:25:00 BST 1401225900 158.6 157.2 315.9 1299.6 1287.9 2587.5 4.8 20.1 12.4 8.2 8.2 8.2 0 78.5
2014-05-27 22:30:00 BST 1401226200 153.0 152.7 305.8 1253.4 1251.3 2504.7 5.0 20.7 12.8 8.2 8.2 8.2 0 78.5
2014-05-27 22:35:00 BST 1401226500 160.0 161.0 321.0 1310.4 1319.1 2629.5 4.7 19.7 12.2 8.2 8.2 8.2 2.0 78.8
2014-05-27 22:40:00 BST 1401226800 156.0 157.4 313.4 1278.0 1289.4 2567.4 4.9 20.1 12.5 8.2 8.2 8.2 0 78.6
-------------------------------------------------------------------------------------------------------------------
6 158.2 158.2 316.4 1296.2 1296.0 2592.2 4.8 20.0 12.4 8.2 8.2 8.2 1.2 78.6
cli% srstatvlun -btsecs -30m -vv fpvv2

-----IOPs/s----- -------KBytes/s-------- ---Svctms--- ---IOSzKBytes---
2014-05-27 22:15:00 BST 1401225300 105.8 34.8 140.7 55485.0 18269.8 73754.8 7.0 34.6 13.8 524.3 524.3 524.3 1.0 46.9
2014-05-27 22:20:00 BST 1401225600 106.8 35.4 142.3 56015.2 18572.8 74588.0 6.8 34.1 13.6 524.3 524.3 524.3 2.0 47.0
2014-05-27 22:25:00 BST 1401225900 105.0 34.8 139.8 55073.5 18220.4 73293.9 7.0 34.7 13.9 524.3 524.3 524.3 0 46.9
2014-05-27 22:30:00 BST 1401226200 102.5 34.2 136.7 53749.2 17917.0 71666.2 7.1 35.6 14.2 524.3 524.3 524.3 1.0 47.0
2014-05-27 22:35:00 BST 1401226500 104.7 35.4 140.1 54904.3 18542.1 73446.3 7.0 34.3 13.9 524.3 524.3 524.3 0 47.1
2014-05-27 22:40:00 BST 1401226800 104.0 34.9 138.9 54512.5 18295.3 72807.8 7.0 34.7 14.0 524.3 524.3 524.3 3.0 46.9
-------------------------------------------------------------------------------------------------------------------------
6 104.8 34.9 139.8 54956.6 18302.9 73259.5 7.0 34.7 13.9 524.3 524.3 524.3 1.2 47.0
4. Run srstatcmp -btsecs -30m to view the cache performance.

Note how the data is an average of all the VLUNs.
cli% srstatcmp -btsecs -30m
---------------count/sec--------------- --hit%--- -----dack/sec------
Time Secsrhit whit r w r+wlockblk r w NL FC10 FC15SSD
2014-05-30 08:05:00 BST 1401433500 1431.3 0.1 1491.6 553.0 2044.6 0.2 96.0 20.4 0.0 0.0 106.5 0.0
2014-05-30 08:10:00 BST 1401433800 1419.4 0.2 1480.5 553.3 2033.8 0.1 95.9 24.6 0.0 0.0 327.6 0.0
2014-05-30 08:15:00 BST 1401434100 1440.3 0.2 1500.3 549.8 2050.0 0.1 96.0 11.5 0.0 0.0 235.6 0.0
2014-05-30 08:20:00 BST 1401434400 1409.4 0.1 1470.8 556.7 2027.5 0.1 95.8 35.1 0.0 0.0 155.4 0.0
2014-05-30 08:25:00 BST 1401434700 1401.6 0.2 1462.1 551.4 2013.6 0.1 95.9 51.3 0.0 0.0 293.6 0.0
2014-05-30 08:30:00 BST 1401435000 1411.9 0.2 1471.6 554.0 2025.5 0.2 95.9 57.8 0.0 0.0 266.5 0.0
5. Run srstatld -btsecs -30m to view the LD performance.

Note how the data is an average of all the LDs.
cli% srstatld -btsecs -30m
----IOPs/s----- ------KBytes/s------ ---Svctms---- -IOSzKBytes--
2014-05-30 13:30:00 BST 1401453000 55.4 82.0 137.5 994.9 7901.1 8896.0 17.1 63.4 44.7 17.9 96.3 64.7 0 7.1
2014-05-30 13:35:00 BST 1401453300 56.3 81.7 138.1 1006.2 7834.7 8840.9 17.2 63.1 44.4 17.9 95.8 64.0 0 7.1
2014-05-30 13:40:00 BST 1401453600 55.4 81.8 137.1 991.7 7875.5 8867.2 17.1 63.6 44.8 17.9 96.3 64.7 2.0 7.1
2014-05-30 13:45:00 BST 1401453900 55.5 82.0 137.5 995.5 7851.7 8847.1 16.9 63.3 44.6 17.9 95.7 64.3 0 7.1
2014-05-30 13:50:00 BST 1401454200 54.9 81.8 136.6 980.1 7837.0 8817.1 17.0 63.4 44.8 17.9 95.8 64.5 0 7.1
2014-05-30 13:55:00 BST 1401454500 54.9 81.8 136.7 982.1 7873.1 8855.2 17.1 63.4 44.8 17.9 96.2 64.8 0 7.1
-------------------------------------------------------------------------------------------------------------------
6 55.4 81.9 137.2 991.8 7862.2 8853.9 17.1 63.4 44.7 17.9 96.0 64.5 0.3 7.1

6. Run srstatpd -btsecs -30m to view the physical disk performance.

Note how the data is an average of all the PDs.
cli% srstatpd -btsecs -30m
-----IOPs/s------ -------KBytes/s-------- ---Svctms---- -IOSzKBytes--
2014-05-30 13:30:00 BST 1401453000 421.4 373.5 795.0 18662.4 17724.5 36386.9 17.5 20.3 18.8 44.3 47.5 45.8 10.0 21.5
2014-05-30 13:35:00 BST 1401453300 421.8 372.5 794.3 18527.0 17579.4 36106.3 17.4 20.2 18.7 43.9 47.2 45.5 10.0 21.5
2014-05-30 13:40:00 BST 1401453600 421.6 373.1 794.6 18631.5 17697.2 36328.7 17.5 20.2 18.8 44.2 47.4 45.7 3.0 21.5
2014-05-30 13:45:00 BST 1401453900 422.8 374.0 796.8 18573.3 17631.9 36205.2 17.3 20.1 18.7 43.9 47.1 45.4 2.0 21.5
2014-05-30 13:50:00 BST 1401454200 421.2 373.1 794.3 18534.1 17602.7 36136.8 17.4 20.2 18.7 44.0 47.2 45.5 3.0 21.5
2014-05-30 13:55:00 BST 1401454500 421.3 373.3 794.7 18546.2 17620.9 36167.2 17.4 20.2 18.7 44.0 47.2 45.5 16.0 21.4
------------------------------------------------------------------------------------------------------------------------
6 421.7 373.2 794.9 18579.1 17642.8 36221.9 17.4 20.2 18.7 44.0 47.3 45.6 7.3 21.5
There is no srstatvv command, so how could you compare the VLUN and VV
performance stats in the System Reporter CLI?
Use help to look at the srstatvlun command and see if you can work this out.
7. Run srstatvlun -attime -groupby vv_name
8. Run srstatvlun -attime -groupby lun
Compare the output.
9. Clean up your lab. Stop IOmeter, and unexport and remove any LUNs and volumes.

Rebalancing
Module 5 Lab
Introduction
This lab coincides with module 5, “Rebalancing.” In this lab, you create a CPG and VV that will be
used for a simulated scenario where disks are not equally alocated because new drives were
added after existing CPGs and VVs were created. Then you will analyze disk allocation level,
perform a preview of tuning from both interfaces, perform the rebalancing, and look at results.
Objectives
 Prepare an imbalanced CPG and VV
 Perform tuning tasks
 Analyze the tuning results

Lab 1 – Preparing the CPG

1. Go to Systems  <your 3PAR>  Physical Disks  FC. Check the current state. As
you can see, the disks are equally allocated.
2. Go to Provisioning and create a “half CPG” called TeamX_StudentY_Half_CPG.

(replace X and Y accordingly). For General settings, change the HA level to
“Magazine” and leave the rest as default.

Rebalancing
3. At the Disk Filter step, press the Filter link and change criteria by setting the Cage
property with Value = 0. Press Add and OK.
4. Now it should like the following screen shot. Click Finish.

Lab 2 – Preparing the volume

Create a fully provisioned 300 GB VV based on your previously created CPG.
Notes:
 You might need to adjust this size depending on number of students and available
space.
 The goal is to create a clear imbalance in space allocation between FC disks.
1. Go to Systems  <your 3PAR>  Physical Disks  FC. Check the current state. As
you can see, disks are not equally allocated. The bigger the size of VVs will be, the
bigger the imbalance will be.
2. Open the CLI and use setcpg -p -devtype FC <name of your CPG>.
Then verify with showcpg –sdg <name of your CPG> that the cage filter
(-cg 0) is no longer displayed. This is very important.
cli% setcpg -p -devtype FC TeamA_Student1_Half_CPG

cli% showcpg -sdg TeamA_Student1_Half_CPG
------(MB)------
Id Name Warn Limit Grow Args
5 TeamA_Student1_Half_CPG - - 32768 -p -devtype FC

Rebalancing
Lab 3 – Tuning and rebalancing using the CLI (preview)

1. Open the CLI and run a tunesys with the dry run option to determine whether your
array is balanced. You already know that it is not, but let’s check anyway. Use the
tunesys –dr command.
cli% tunesys -dr
Are you sure you want to tune this storage system?
select y=yes n=no: y
*********************************************************
** Storage system tuning started
*********************************************************
tunesys -dr
Parameter summary:
------------------
Task ID = none
Nodepct = 3
Chunkpct = 10
Diskpct = 10
Maxtasks = 2
Dry run flag = 1
Waittask mode = 0
Clean timeout = 120
System chunklet size = 256
cpgs = ALL
*********************************************************
* PD Analysis
*********************************************************
-------FC-------
-----------------Description------------------ 15K 10K 10K+15K NL SSD All
Number of Available PDs with free chunklets 16 0 16 16 0 32
Number of Available PDs with no free chunklets 0 0 0 0 0 0
-----------------------------------------------------------------------------
Total Number of Available PDs 16 0 16 16 0 32
-----------------------------------------------------------------------------
Maximum number free chunklets in a PD 1895 - - 6798 - 6798
Minimum number free chunklets in a PD 1287 - - 6798 - 1287
*
*********************************************************
* PD Node Balance Summary - Device type usage across nodes
*********************************************************
[…]
*********************************************************
* Phase 2: Performing Intra-node balance checks:
*********************************************************
*
*********************************************************
* Node 0 has 4 underallocated PDs and will be tuned
*********************************************************
*
*********************************************************
* Node 1 has 4 underallocated PDs and will be tuned
*********************************************************
*
*********************************************************
* Dry run - The following ND tunes would be
* performed:
*********************************************************
*
tunenodech -f -nocheck -dr -maxchunk 2 -chunkpct 10 -node 0
tunenodech -f -nocheck -dr -maxchunk 2 -chunkpct 10 -node 1
*
*********************************************************
* Phase 3: LD tuning will not be performed.
* Reason: No LD re-layout tunes needed.
*********************************************************
* Dry Run completed
*********************************************************

Lab 4 – Tuning and rebalancing using the GUI (preview)

1. Go to Provisioning and select Tune System from Common Actions. Select the
Analyze only checkbox and click OK.

Rebalancing
2. Go to Tasks & Schedules, switch to the Tasks tab and highlight the System Tuning
task. The task has finished.
Again, the result is the same – array needs rebalancing.

Lab 5 – Tuning and rebalancing

1. Run the CLI or GUI based tuning. Use the previous settings, but this time skip dry
run/Analyze Only.
One person per team will perform this step for the entire storage array, so please
ask other members if they have finished previous steps.

Rebalancing
As you can see, a tuning task can run one or more subtasks that rebalance different
aspects of the array.
2. The tuning task can take 8 or more hours, so allow it to run over night. When you
come back, go to Systems  <your 3PAR>  Physical Disks  FC. You should see
that the disks are now allocated equally.


Upgrading
Module 6 Lab
Introduction
This lab coincides with module 6, “Upgrading 3PAR.” You will learn how to perform hardware
replacement procedures by watching video tutorials from HP Services Media Library (SML). You
will also verify Service Processor (SP) software level from SPMAINT, verify 3PAR OS version, and
perform an array health check. For technical reasons in the HPVL, and because we are sharing
the array, we will not perform the 3PAR OS update, but we will walk though preparation tasks.
To be able to work in parallel, the first student should do Lab 1, while the second student
should do Labs 2 and 3, and then switch.
Objectives
 Use the HP Customer Self Repair Services Media Library
 Verify the Service Processor Software Level from SPMAINT
 Verify the HP 3PAR OS Software Level

Lab 1 – Using the HP Customer Self Repair Services

Media Library (optional)
We do not have access to physical hardware, but if you want to practice, you can use
video tutorials to learn how to perform replacement procedures step by step.
1. On your local machine, browse to http://h20464.www2.hp.com/
2. In Media Selection, select Storage  3PAR StoreServ Storage  7000 or 1000
3PAR
3. Select Remove/Replace videos link and watch recorded procedures.

Upgrading
Lab 2 – Verifying the Service Processor Software Level

from SPMAINT
1. Access the SPMAINT command line by pressing the PuTTY to <IP> button for your
team.
2. For technical reasons in HPVL, you need to remove and then re-add the array to SP.
To remove it, select 3 ==> StoreServ Configuration Management, 4 ==> Remove
a StoreServ and then select the array to operate on and confirm with y.
SP0001310387
3.4 Delete StoreServ
Configured StoreServs
1 ==> inserv036 --> 1310387
0 ==> Abort Operation
Please select a StoreServ to operate on
X Exit

3. Wait until the process ends and press Enter. To re-add the array, select 2 ==> Add a
new StoreServ and enter the IP address of your 3PAR, and confirm with Enter.
SP0001310387
3.2 Add StoreServ

HP 3PAR Service Processor Menu
Transfer media: off Transfer status: SPtransfer is quiesced
SP - StoreServ Configuration Manipulation
Enter Control-C at any time to abort this process
This Service Processor was setup for StoreServ 1310387.

Please enter the IP address for StoreServ 1310387 to add it to this SP
-OR -
Enter QUIT to abort:
X Exit
4. Give your 3PAR credentials (3paradm: 3pardata), confirm with Enter, and wait.
When it finishes, press Enter again and select X Return to the previous menu.
SP0001310387
3 StoreServ Configs
SP - StoreServ Configuration Manipulation
1 ==> Display StoreServ information

2 ==> Add a new StoreServ
3 ==> Modify StoreServ config parameters
4 ==> Remove a StoreServ
X Return to the previous menu

Upgrading
5. Now you can start the actual exercise. The SP must be updated to the required SP
software. To verify the level of SP software running on the SP for the system you
are updating, log on to the SPMAINT utility to display the SP level.
SP0001310387
1 SP Main
1 ==> SP Control/Status
2 ==> Network Configuration
3 ==> StoreServ Configuration Management
4 ==> StoreServ Product Maintenance
5 ==> Local Notification Configuration
6 ==> Site Authentication Key Manipulation
7 ==> Interactive CLI for a StoreServ
X Exit
6. From the SPMAINT main menu, select: 1 ==> SP Control/Status then: 1 ==>
Display SP Version.
1.1 Display SP Version
SP Software Version
SP-4.2.0.GA-29
SP Base Image Version: Red Hat Enterprise Linux Server release 6.1 (Santiago)
SP Version: 4.2.0.GA-29
SP Patches:
HP 3PAR OS release (3.1.2): 3.1.2.278
HP 3PAR OS release (3.1.3): 3.1.3.230-MU1
More detail is available in the latest SPLOR or spconfig data.

7. Go back to the previous menu with X and select 13 ==> Display SP status.
1 SP CONTROL
[…]
1 ==> Display SP Version
2 ==> Reboot SP
3 ==> Halt SP
4 ==> Stop StoreServ related Processes
5 ==> Start StoreServ related Processes
6 ==> File Transfer Monitor
7 ==> SP File Transfer Trigger
8 ==> Reset Quiesce state in Transfer process
9 ==> Mount a CDROM
10 ==> Unmount a CDROM
11 ==> SP Date/Time/Geographical Location maintenance
12 ==> Manage NTP configuration
13 ==> Display SP status
14 ==> SP User Access Control
15 ==> SP Process Control Parameters
16 ==> Maintain SP Software
17 ==> SP File Maintenance
18 ==> RESERVED
19 ==> Request a SPLOR
20 ==> Request an MSPLOR
21 ==> Run SPCheckhealth
X Return to previous menu

Upgrading
8. The following output appears.

The following global procedures are running:
/sp/prod/code/csst/bin/SPcommctlr
/sp/prod/code/csst/bin/SPnetmon
/sp/prod/code/csst/bin/SPtransfer
/sp/prod/code/csst/bin/SPup2date
/sp/prod/code/csst/bin/STlogger
/sp/prod/code/csst/bin/spcollect
/sp/prod/code/csst/bin/spevent
/sp/prod/code/csst/bin/stAnalyze
/sp/prod/code/csst/bin/stBackDoor
/sp/prod/code/csst/bin/stGrpNot
/sp/prod/code/csst/bin/stMonitor
/sp/prod/code/csst/bin/stNotify
There are 10 httpd server processes running
spevent is running for the following clusters:

1310387 (inserv036)
spcollect processes are running as follows:

adlc for 1310387 (inserv036)
biosmsg for 1310387 (inserv036)
config for 1310387 (inserv036)
eeprom for 1310387 (inserv036)
environ for 1310387 (inserv036)
evtlog for 1310387 (inserv036)
memdata for 1310387 (inserv036)
perfdb for 1310387 (inserv036)
perform for 1310387 (inserv036)
status for 1310387 (inserv036)
Normally, this output is saved. You will need to compare it with the post-upgrade SP
status after you install the operating system.
Now, the SP software update would be performed (steps 1.16.2 [Update SP
Software Revision]) and then you would compare 1.1 (Display SP Version) and
1.13 (Display SP status) outputs before and after the update.
For an example of the basic list, see the table, “Example of Basic SP Processes” in
the HP 3PAR OS 3.x.x Upgrade Instructions document.
If the basic SP processes are running, you can now install the operating system on
the storage system.

Lab 3 – Verifying the HP 3PAR OS Software Level

The current HP 3PAR OS level must meet the supported update path requirements.
1. To verify the HP 3PAR OS level currently running on the storage system, open the
CLI and check the current 3PAR OS version with the showversion –a –b
command.
cli% showversion -a -b
Release version 3.1.3.230 (MU1)
Patches: None
Component Name Version

CLI Server 3.1.3.230 (MU1)
CLI Client 3.1.3.230
System Manager 3.1.3.230 (MU1)
Kernel 3.1.3.230 (MU1)
TPD Kernel Code 3.1.3.230 (MU1)
CIM Server 3.1.3.230 (MU1)
WSAPI Server 3.1.3.230 (MU1)
Console Menu 3.1.3.230 (MU1)
Event Manager 3.1.3.230 (MU1)
Internal Test Tools 3.1.3.230 (MU1)
LD Check Tools 3.1.3.230 (MU1)
Network Controller 3.1.3.230 (MU1)
Node Disk Scrubber 3.1.3.230 (MU1)
PD Scrubber 3.1.3.230 (MU1)
Per-Node Server 3.1.3.230 (MU1)
Persistent Repository 3.1.3.230 (MU1)
Powerfail Tools 3.1.3.230 (MU1)
Preserved Data Tools 3.1.3.230 (MU1)
Process Monitor 3.1.3.230 (MU1)
Rolling Upgrade Tools 3.1.3.230 (MU1)
Software Updater 3.1.3.230 (MU1)
TOC Server 3.1.3.230 (MU1)
VV Check Tools 3.1.3.230 (MU1)
SNMP Agent 1.7.0
SSH 5.5p1-6+squeeze1
Firmware Database 20140521
Drive Firmware 20140521
UEFI BIOS 14.05.23
MCU Firmware 4.23
Cage Firmware (DC1) 4.44
Cage Firmware (DC3) 08
Cage Firmware (DCS1) 3211
Cage Firmware (DCS2) 3211
Cage Firmware (DCN1) 3211
QLogic QLA4052C HBA Firmware 03.00.01.77
QLogic QLE8242 CNA Firmware 04.11.237
Emulex LP11002 HBA Firmware 02.82.x10
Emulex LPe12002 HBA Firmware 02.01.x14
Emulex LPe12004 HBA Firmware 02.01.x14
3PAR FC044X HBA Firmware 200A8
LSI 9201-16e HBA Firmware 17.11.00
LSI 9205-8e HBA Firmware 17.11.00

Upgrading
2. Go to SPMAINT and run a health check by selecting 4 ==> StoreServ Product

Maintenance and then 4 ==> Perform StoreServ Health Check. Select your system
and confirm with y.
SP0001310387
4.4.2 Perform Health Check on StoreServ

StoreServ Product Maintenance Menu
Confirmation
Are you sure you want to retrieve and transfer

the check health data for StoreServ inserv036?
Please wait a moment.

3. After the health check completes gathering the data, the SP displays a list of files to
view. Display all of them by selecting numbers 1 through 4. Normally, you would
review and correct any exceptions before performing an HP 3PAR OS update.
SP0001310387
4.4.2 Show latest health check status from StoreServ
Available files
1 ==> /sp/prod/data/files/1310387/status/150328.111324.all
2 ==> /sp/prod/data/files/1310387/status/150328.111324.det
3 ==> /sp/prod/data/files/1310387/status/150328.111324.err
4 ==> /sp/prod/data/files/1310387/status/150328.111324.sum
0 ==> Abort Operation
Please select a file to display
4. Select 0.
Now an actual 3PAR OS would take place. Refer to your student guide for a step-by-
step description. Please do not try to perform this procedure in HPVL.


Alerts
Module 7 Lab
Introduction
This lab coincides with module 7, “Alerts.” In this lab you will learn how to work with
different monitoring, alerting, and notification systems available on both HP 3PAR
storage array systems and Service Processor.
This lab can be performed by both students at the same time, but the first student
should do labs 1 through 5, while the second student does Labs 6 through 8, and then
switch. Please ask the other person if they are finished before switching.
Objectives
 View alerts from both the Management Console (MC) and the command line
interface (CLI)
 View events from the MC and CLI
 Work with internal System Reporter alerts
 Configure SNMP and SNMP traps
 Configure SMI-S/CIM monitoring
 Configure SPOCC email notifications

Lab 1 – Viewing alerts (MC GUI)

1. Go to Events & Alerts, select your system, and then select one of the alerts.
Tips
If you see no alerts, generate some. For example, you can create a common provisioning
group (CPG) or thinly provisioned virtual volume (TPVV) with a very strict or low space
allocation warning threshold that you can then exceed. Alternatively, you can set raw
space threshold alerts that can be quickly reached.
 To set a raw space alert for a storage system with nearline (NL) drives, enter:
setsys RawSpaceAlertNL <threshold>
 To set a raw space alert for a storage system with Fibre Channel (FC)drives, enter:
setsys RawSpaceAlertFC <threshold>
 To set a raw space alert for a storage system with Solid State Drives (SSDs), enter:
setsys RawSpaceAlertSSD <threshold>
Where <threshold> is an integer from 100 to 100,000 that represents the total
available space on the system in gigabytes.

Alerts
2. Look at the details and write down the answers to the following questions:
What is the severity of this alert? ....................................................................................
What is the type of this alert? ..........................................................................................
What is the content or message of this alert?.................................................................
What is the component that this alert has been generated for? ....................................
When was it generated?...................................................................................................
3. Right-click this alert and set it as Acknowledged.
Its state at both the list and details sections changed accordingly. When the problem
is solved, you can remove it using the same method.

Lab 2 – Viewing alerts (CLI)

You can perform the same actions from the CLI.
1. Open the CLI and use showalert –n to display only new alerts. Pick one and
answer the following questions.
cli% showalert -n
Id : 12
State : New
Message Code: 0x0270013
Time : 2015-03-27 08:12:41 EDT
Severity : Informational
Type : Raw space allocation user configured alert
Message : Total available NL raw space has reached threshold of 100000G
(27192G remaining out of 29800G total)
Id : 14
State : New
Time : 2015-03-27 10:01:41 EDT
Type : TP VV allocation size warning
Message : Thin provisioned VV tpvv has reached reserved allocation warning of
2G (20% of 10G)
Id : 9
State : New
Time : 2015-03-28 09:12:55 EDT
Severity : Major
Type : Authentication failure
Message : 16 authentication failures in 120 secs
3 alerts
What is the severity of this alert? ....................................................................................

What is the type of this alert? ..........................................................................................
What is the content or message of this alert?.................................................................
2. Feel free to experiment with other showalert options:
-a: Specifies that only acknowledged alerts are displayed.
-f: Specifies that only fixed alerts are displayed.
-all: Specifies that all customer alerts are displayed.

Alerts
3. You can perform the same alert-related operations from the CLI as you can from the
MC GUI.
To mark an alert as new, fixed, or acknowledged, use the setalert
new|fixed|ack <alert_ID> command, where <alert_ID> is the alert whose
status you want to change. Do so for one of the alerts you worked with in step 2.
Use showalert again to see the result.
You can also remove an alert. Enter the removealert <alert_ID> command,
where <alert_ID> is the alert you want to remove. Remember to leave some alerts
for other students.

Lab 3 – Viewing events (MC GUI)

1. Go to Events & Alerts, select your system, and switch to the Events tab. Click Get
Events. If the list is empty, increase the Last X days value and repeat.
2. Select one of the events and display details.
What is the severity of this event? ..................................................................................

What is the type of this event? ........................................................................................
What is the component that this event has been generated for? ..................................

Alerts
3. Find all the events related to authentication. Use the text filter.

Lab 4 – Viewing events (CLI)

The event log is long and always displays all the events that match specified conditions,
so you should use the showeventlog command together with cmore.
1. Go to the CLI and enter the cmore showeventlog command.
cli% cmore showeventlog
Time : 2015-02-02 13:20:39 EST
Type : Node booted
Message : Node 0 has booted
Time : 2015-02-02 13:20:39 EST

Type : Eagle link error
Message : Power detected on link 1 from node 0 to node 1-posted by node 0-Link 1
config reg [0x88000000] [PR_OK RE_EN]
Time : 2015-02-02 13:20:34 EST

Type : Node booted
Message : Node 1 has booted
Time : 2015-02-02 13:20:39 EST

Type : Eagle link error
Message : Power detected on link 2 from node 1 to node 0-posted by node 1-Link 2
config reg [0x88000000] [PR_OK RE_EN]
Time : 2015-02-02 13:20:54 EST

Type : Quorum Witness
Message : Node: 0 SysId: 32767 Quorum Announcer Registration
more? q=quit a=all <enter>=more:

Alerts
2. Display events only related to a certain component class, for example, ports. If you
do not know how, use the help showeventlog command. Remember to
combine it with cmore.
cli% cmore showeventlog -comp port
Time : 2015-02-02 13:21:25 EST
Type : Component state change
Message : Port 0:2:1 Normal (Online)
Time : 2015-02-02 13:21:25 EST

Time : 2015-02-02 13:21:25 EST

Time : 2015-02-02 13:21:25 EST

Time : 2015-02-02 13:21:25 EST

more? q=quit a=all <enter>=more:

Lab 5 – Internal System Reporter alerts

1. Check whether any SR alert criteria already exist with the showsralertcrit
command.
cli% showsralertcrit
No criteria listed
2. Add a new one. See the help createsralertcrit command output or your
student guide for details.
For example, create an alert criteria that will work when total number of IOPS
generated to a specific VV exceeds 50 (select one of your VVs or create a new one
for that task). The alert should be considered a minor problem. Note that the
following command is a single line:
cli% createsralertcrit vlun -vv tpvv -minor -hires total_iops>50 tpvv_workload_test
3. Verify that creation was successful.

cli% showsralertcrit
Name State Freq Severity Type Conditions
tpvv_workload_test enabled hires minor vlun -vv=tpvv,total_iops>50
4. Use IOmeter to generate a workload to this VV. Use the “all in one” workload
pattern, and allow it to run for about 10 minutes.
Feel free to proceed to the next exercise, but remember to return to this one
after at least 10 minutes.

Alerts
5. When you get back, go to the Events & Alerts section. You should find an alert
generated because of your previously created SR alert criteria.

Lab 6 – SNMP traps

1. You might need to add SNMP Managers. Use the showsnmpmgr command to
determine whether any managers are already added. You need to have 2 or more
managers. One will be your Windows host/client machine running SNMP Trap
Watcher, and the second will be the MGMT host running HP SIM. The third one will be
another Windows host added by another student. If the MGMT host has not been
added, please add it together with your Windows host.
cli% addsnmpmgr <IP of Windows host>
cli% addsnmpmgr <IP of MGMT host>
2. Verify with the showsnmpmgr command.
cli% showsnmpmgr
HostIP Port SNMPVersion User
192.168.118.182 162 2 --
192.168.118.184 162 2 --
3. This lab uses SNMP v2, but if you wanted to use v3, you would need to perform this
step as well. For learning purposes, create an SNMPv3 user with the
createsnmpuser command. For simplicity, use the same data as for the 3PAR
user. Verify with the showsnmpuser command.
cli% createsnmpuser -p 3pardata 3paradm
SNMP user successfully set.
cli% showsnmpuser
Username AuthProtocol PrivProtocol
3paradm HMAC-SHA-96 CFB128-AES-128

Alerts
4. Unzip and copy SNMP Trap Watcher from the Depot to your Windows host desktop
and run it.
5. To test communication between SNMP Agent and SNMP Managers, use the
checksnmp command. It generates and sends a test trap to all registered SNMP
Managers.
cli% checksnmp
Trap sent to the following managers:
192.168.118.182:162
192.168.118.184:162
SNMP trap has been received by SNMP Trap Watcher.
If you do not see any traps, double-check that you configured SNMP correctly. If so,
disable Windows Firewall.
Leave it open, and after you have finished all the labs, check whether you have
received any new traps.

Lab 7 – SMI-S/CIM monitoring

1. Use the showcim command to determine whether the CIM server is running. If it is
not running, enable it with the startcim command.
cli% showcim
-Service- -State-- --SLP-- SLPPort -HTTP-- HTTPPort -HTTPS- HTTPSPort PGVer CIMVer
Disabled Inactive Enabled 427 Enabled 5988 Enabled 5989 2.9.1 3.1.3
cli% startcim
CIM server will start in about 90 seconds
Now you are ready to add your 3PAR to HP SIM for monitoring.
2. Open Internet Explorer from your HPVL Windows host and browse to
http://mgmtvm:280/
If the MGMT server is not responding, power it up by using the VI client, which is
accessible from the main HPVL screen.

Alerts
3. Ignore the certificate warning. Use the following:

 Login: Administrator
 Password: hp credentials
4. Ignore the registration and First Time Wizard. Select Options  Discovery... from
the menu.

5. Click the New... button.
6. Switch to the Discover a single system option and specify the IP address for your
3PAR.

Alerts
7. Click the Credentials… button and use your 3paradm: 3pardata login and password.
8. Switch to the SNMP tab and use public for the read community string. 3PAR uses
it by default.
9. Press OK and then the Save button.

10. Select your discovery task and press the Run Now button.
It will take a few minutes; wait until it completes. If you see no progress, stop it,
cancel, and start again.
11. After the task has finished, browse to your discovered system (Systems  Shared
 Systems by Type  Storage Systems  All Storage Systems  <IP>)

Alerts
12. Look at the information gathered from 3PAR on the different tabs and answer the
following questions:
What is the version of 3PAR OS?......................................................................................
How many online FC N-ports do you have? .....................................................................
How many VVs do you have, and which one is the biggest? ...........................................
What is the total capacity?...............................................................................................

13. When you have finished, remove the array from HP SIM so other students can
perform the same lab.
a. From tree menu on the left, click Storage Systems  All Storage Systems.
b. Select the checkbox next to your array.
c. Select Delete and confirm with OK.

Alerts
Lab 8 – SPOCC email notifications

1. Log in to SPOCC either though Windows host and web browser, or directly from the
HPVL topology screen by clicking the SPOCC button.
2. Go to the Setup section and click Enable Local Notification if the current state is
“Disabled.”

3. Click the Configure Mailhost link.
4. For IP Address, use your MGMT host IP. For Mailhost Domain Name, use anything
NOT FROM *.local domain. You can use mailserver.somewhere.com for example.
Press Add Mailhost.

Alerts
5. You are ready to test whether everything has been configured correctly. Press the
Test Mailhost button and use 3par@hp.local for the email address. Press OK.
After a few seconds, you should see a SPOCC Maillog message that is similar to this.
Check Maillog:
Mar 27 11:40:37 inserv036spvm postfix/pickup[16288]: 905A0680B45: uid=48
from=<apache>
Mar 27 11:40:37 inserv036spvm postfix/cleanup[16578]: 905A0680B45: message-
id=<20150327154037.905A0680B45@inserv036spvm>
Mar 27 11:40:37 inserv036spvm postfix/qmgr[16289]: 905A0680B45:
from=<apache@mailserver.somewhere.com>, size=392, nrcpt=1 (queue active)
Mar 27 11:40:38 inserv036spvm postfix/smtp[16586]: 905A0680B45: to=<3par@hp.local>,
relay=192.168.118.184[192.168.118.184]:25, delay=0.94, delays=0.06/0.02/0/0.86,
dsn=2.0.0, status=sent (250 Queued (0.843 seconds))
Mar 27 11:40:38 inserv036spvm postfix/qmgr[16289]: 905A0680B45: removed
6. If you see no errors, log in to the MGMT host and launch Mozilla Thunderbird.

7. You should see a test email in your Inbox. If not, please check to make sure you
performed steps 2 through 4 correctly.
8. Click Notify Quick Setup.

Alerts
9. Type your name, local email address (3par@hp.local), category (Customer), and
company name, and press the Add User Profiles and Notification Record button.
As you can see below, this Quick Setup wizard added Notification and User Profile
positions. We keep defaults, but normally you might want to customize or add them
manually.
10. Before proceeding to the next step, test that everything has been properly
configured so far. Edit your User Profile.

11. Press Test Email/Page.
12. Go to the MGMT host and open the Thunderbird client again. You should see a new
email in the Inbox.

Alerts
By default, the customer is notified mostly about Thin Provisioning related events.
Experienced SPOCC administrators can change that in Setup  [Advanced
Configuration Menu] (next to Disable Local Notification)  3. Predefine
Symptoms
13. Accepting the default TPVV related notifications, now you need to generate such
notification.
Create a new 10 GB TPVV. Set its Allocation Warning for 10%, and then export it to
your Windows host.

14. Copy some files to fill it up and exceed 10% Allocation Warning. Go back to the
Thunderbird email client at the MGMT host and look for a new email.
As you can see, email notification has been successfully generated and delivered.
Return to the still opened SNMP Trap Watcher and check whether you can see any
new traps.
15. Please clean up the SP.
1. Go to the Notify section and select Quick Setup.
2. Go to the Setup section and click Configure Mailhost  Remove Mailhost.
3. Sign out from the SP.

H9p97s.a.00 Lab

Uploaded by

Copyright:

Available Formats

You might also like

H9p97s.a.00 Lab

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

H9p97s.a.00 Lab

Uploaded by

Copyright:

Available Formats

Managing HP 3PAR

Managing HP 3PAR StoreServ III

Lab 1 – Setting Up the Lab Environment ............................................................... L1-1

Lab 2 – Space Explained ................................................................................... L2-1

Lab 3 – Adaptive Optimization ...........................................................................L3-1

Lab 4 – Performance ........................................................................................ L4-1

Lab 5 – Rebalancing .........................................................................................L5-1

H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. i

Lab 6 – Upgrading .......................................................................................... L6-1

Lab 7 – Alerts ................................................................................................... L7-1

ii © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. L1 – 1

Accessing the HP Virtual Labs

2. Select the Access Virtual Lab Environment link.

L1 – 2 © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. L1 – 3

L1 – 4 © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. L1 – 5

L1 – 6 © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

Mapping the shared Y: drive

H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. L1 – 7

2. Enter a path name \\192.168.XXX.250\hp3par\h9p97s.a

You now see the contents of the Y: drive.

L1 – 8 © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

3. Launch the 3PAR Management Console desktop icon.

H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. L1 – 9

4. Select Hosts, and in Common Actions, click Create Host.

5. Use a unique naming format for your host, such as “TeamAHostA.”

L1 – 10 © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. L1 – 11

L1 – 12 © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

Installing iometer on Linux

Enter yum install kernel-headers.x86_64 kernel-devel.x86_64

Enter tar –xvf iometer-1.1.0-src.tar

Enter ./dynamo ? to get the options you want.

H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. L1 – 13

L1 – 14 © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. L2 – 1

L2 – 2 © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

Lab 1 – Installing the GUI and CLI

Install the GUI and CLI

Adding a host using the QCC GUI

H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. L2 – 3

2. Launch the QCC GUI desktop icon and click Connect.

4. Launch the 3PAR Management Console desktop icon.

6. Use a unique naming format for your host, such as “TeamAHostA.”

L2 – 4 © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

Installing MPIO on the host

3. Under Features, select Multipath I/O.

H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. L2 – 5

4. Select Tools MPIO.

L2 – 6 © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00

5. Click Add and type 3PARdataVV and then click OK.

6. A reboot is now required. Type Yes.

H9P97S A.00 © 2015 Hewlett-Packard Development Company, L.P. L2 – 7

Lab 2 – Identifying space

Describing system space

L2 – 8 © 2015 Hewlett-Packard Development Company, L.P. H9P97S A.00