Documente Academic
Documente Profesional
Documente Cultură
TSI2598
Notice: This document is for informational purposes only, and does not set forth any warranty, expressed or implied, concerning any equipment or service offered
or to be offered by Hitachi Data Systems Corporation.
L-ii
Table of Contents
L-iii
Table of Contents
L-iv
Introduction
This Lab Guide includes Activities section. The instructions for the lab activities, although complete, do
not include much detail. We recommend that you attempt to perform the learning activities in this guide
using the instructions provided in the Activities section. If you would like additional details, then refer
the guides listed below for relevant details.
If you do not clearly understand the instructions, ask your instructor for assistance.
Reference Material
Several Hitachi reference manuals are available on the desktop of each Microsoft® Windows® host
system and possibly on a shared resource system:
Hitachi Command Suite Tuning Manager Agent Administration Guide
Hitachi Command Suite Tuning Manager CLI Reference Guide
Hitachi Command Suite Tuning Manager API Reference Guide
Hitachi Command Suite Tuning Manager Hardware Reports Reference
Hitachi Command Suite Tuning Manager User Guide
Lab Orientation
The Hitachi Tuning Manager software training involves a lot of time in the lab. To familiarize yourself
with our lab setup it is essential that you read the following lab instructions. The instructor will describe
the lab setup before the start of the lab.
Each lab group will be assigned one Microsoft Windows server (HCS Management server), at least one
more Microsoft Windows host server and possibly more host servers of different operating systems, as
available.
All the servers are SAN connected to a Hitachi enterprise storage system. Optionally, a Hitachi modular
storage system might also be configured.
For all configuration details, please refer to the Lab layout drawing appropriate to your Lab environment.
N ote : Log in to Hitachi Command Suite Device Manager to view all configuration details.
http:// <IP address of Device Manager Server>:22015/DeviceManager/
Userid: system
Password: manager
Important: Do not change any settings. The lab projects are written to match this setup.
L-v
Introduction
Lab Configuration for One Lab Group
L-vi
Introduction
Lab Configuration Outline
Host Group
Port LDEV LUN Emulation WWN
(Storage Domain Name)
L-vii
Introduction
Lab Configuration Outline
L-viii
Introduction
Lab Configuration Outline
3. Installed Agents
Which agents are installed?
4. Switch Configuration
Fill in the information below to reflect the switch configuration (if available).
Note: If you are unable to obtain any of the above information, ask your instructor for assistance.
L-ix
Introduction
Preparation for Labs
Notes
L-x
Activity
Objectives
Upon completion of the lab project, you will be able to:
Perform Agent Store management appropriate to conserve unrecallable historical data
Summary of Activity
Find which Agent Store types are installed
Validate the Agent for RAID is configured for Complete Storage Monitoring
Agent Store DB backup, migrate and restore
Agent Store Off-site analysis
Agent Hybrid Store backup, restore and migrate
References
Hitachi Command Suite Tuning Manager Agent Administration Guide
________________________________________________________________
5. Run the command jpcctrl list * and validate that the Agent instances show the status
“active”.
6. If not, start the services with the command jpcstart all.
7. Execute the command jpcdbctrl display.
8. Which types of Agent Store (Store version) are installed?
1
1. Agent Store Management Activity
Activity – Find which type of Agent Store are installed
___________________________________________________________________
9. Note the Agent Instance Name for the enterprise storage system.
____________________________________________________________________
______________________________________________________________________
13. If the Agent instance is not configured for communicating to the SVP of the enterprise storage
system, run the jpcinssetup agtd –inst <name of instance> command specifying the
correct options.
In case of problems, ask your instructor to validate correct Lab equipment setup.
2
Activity 1. Agent Store Management
Activity – Agent Store DB backup, migrate and restore
______________________________________________________________
______________________________________________________________
14. On the Management server HCS-1, stop the service of the SAN switch agent installed.
jpcstop agtw inst=<name of instance>
15. On HCS-2, stop ALL Agent services with the command jpcstop all.
16. Create an empty directory C:\backup on HCS-2.
17. From the “…jp1pc.tools” directory, run the following command
jpcconf host hostmode –mode alias -aliasname <Hostname of HCS-1>
3
1. Agent Store Management Activity
Activity – Agent Store off-Site analysis
-d C:\backup
18. Ensure successful execution.
19. Validate the Service ID name of the SAN Switch instance on HCS-2 has changed to the name
reflecting server HCS-1 (jpcctrl list*).
20. Run command jpcresto agtw C:\agtw_bkup_HSC-1 inst=<agtw instance name>.
21. Wait for successful finish of the restore process.
22. Run the command jpcconf host hostmode –mode hostname C:\backup.
23. Validate the Service ID name of the SAN Switch instance on HCS-2 has changed to the name of your
Host Server HCS-2.
24. Start all agent related services on HCS-2
25. Connect to Performance Reporter and run the same report as specified in step 12.
26. What are the date and time stamps of the first and last record displayed?
________________________________________________________________
The SAN Switch Agent instance is now running on HCS-2 holding the migrated data of the Store DB
originally capture back in time by the instance running on HCS-1.
4
Activity 1. Agent Store Management
Activity – Agent Hybrid Store backup, restore and migrate
Important: In case the jpcagt.ini file is the configuration file for a Hybrid Store type agent instance,
only change all occurrences of "Log=Y" for those appearing before the entries [API Data Management].
Do not change them for those appearing after [API Data Management]
5. Stop and restart the services of the SAN Switch instance you have just altered.
6. Connect to the Management Server HCS-1.
7. Start the services of the SAN Switch agent instance running on HCS-1.
8. Verify the agent is working correctly collecting metrics.
It will now take some time to be able to prove that the SAN Switch agent instance running on HCS-2
is not collecting metrics anymore.
9. After carrying on with the rest of the Lab 1 activities, display the same report from the SAN Switch
agent instance running on HCS-2 as in step 1.
10. In case the Message-ID KAVJS5001-I (PR1936) appears, click the Show Options button.
11. Alter the Settings for the report display period to display the past 6 hours with the Report
interval set to Minute.
12. Verify the last record date and time stamp proves that no new metrics were collected since the time
the jpcagt.ini file was edited and the services started.
.
___________________________
5
1. Agent Store Management Activity
Activity – Agent Hybrid Store backup, restore and migrate
_________________________________________________________________
11. Stop all of the agent services before restoring the Hybrid Store with the command:
htmsrv stop -all
12. Execute the restore of the Hybrid Store only to the specific Enterprise storage Agent instance you
have displayed the report from.
13. Which options are required to achieve the above?
_______________________________________________________________________
14. After successful restore operation, restart the agent services.
15. Back to Performance Reporter, run the same report as in step 6 above.
16. Prove for the successful restore operation is the Performance Reporter is displaying the report again.
17. In case of difficulties achieving the above, ask your instructor for assistance and troubleshoot the
issue before continuing.
6
2. Main Console and Performance Reporter
CLI
Overview
The primary objective of this lab project is to understand the format and execution mechanism of the
Main Console CLI as well as the Performance Reporter CLI.
Objectives
Upon completion of the lab project, you will be able to:
Execute Main Console CLI without any resource ID dependency
Execute Main Console CLI with resource ID dependency
Collect a list of user reports defined in Performance Reporter
Create new, and modify existing Performance Reporter reports
Run existing Performance Reporter reports
Summary of Activity
Common Components Commands
Main Console CLI execution
Performance Reporter CLI
References
Hitachi Command Suite Tuning Manager CLI Reference Guide
_____________________________________________________________
7. Are you still able to Login to Tuning Manager Server Mail Console? Y/N
8. Try to connect to Performance Reporter to run a report.
7
2. Main Console and Performance Reporter CLI Activity
Activity – Main Console CLI
______________________________________________________________________
8
Activity 2. Main Console and Performance Reporter CLI
Activity – Performance Reporter CLI
9
2. Main Console and Performance Reporter CLI Activity
Activity – Performance Reporter CLI
11. What is the style of the fields “User CPU %” and “Privileged CPU %” get displayed?
____________________________________________________________________
10
3. Import/Export Performance Reporter
Reports
Overview
The primary objective of this lab project is to export and import existing Performance Reporter reports
using Performance Reporter CLI and GUI.
Objectives
Upon completion of the lab project, you will be able to:
Export existing Performance Reporter reports to CSV-, and HTML format using CLI
Export Performance Reporter User Reports
Import Performance Reporter User Reports
Summary of Activity
Export and import Performance Reporter Reports
References
Hitachi Command Suite Tuning Manager CLI Reference Guide
Hitachi Command Suite Tuning Manager User Guide ; Chapter 4 - Working with reports from
Performance Reporter
11
3. Import/Export Performance Reporter Reports Activity
Activity – Export Performance Reporter to HTML using CLI
Trend">
<launch-options>
<indication-settings maximum-number-of-records="1440">
<report-interval>HOUR</report-interval>
<start-time>02 02 2016 00:00</start-time>
<end-time>02 02 2016 12:00</end-time>
</indication-settings>
</launch-options>
</report-definition>
</launch-report>
</pr-cli-parameters>
3. To create the output file Export-CLI-to-CVS.csv containing the metrics of the above specified report,
execute the command jpcrpt -o Export-CLI-to-CVS.csv export_csv.xml.
4. View the contents of Export-CLI-to-CVS.csv file created in HMTPR as a result of the command
execution.
12
Activity 3. Import/Export Performance Reporter Reports
Activity – Export/Import Performance Reporter reports using GUI
<html-output>
<show-graph>
<graph-options zoom-scale = "100">
<show-grid/>
<vertical-axis minvalue="0" maxvalue="100"/>
</graph-options>
</show-graph>
<show-table/>
</html-output>
</report-definition>
</launch-report>
</pr-cli-parameters>
2. To create the output file Export-CLI-to-HTML.htm with the above specified report definitions
execute the command jpcrpt -o Export-CLI-to-HTML export_htm.xml.
What type of output do you find in the directory HTMPR?
_________________________________________________________________
_________________________________________________________________
13
3. Import/Export Performance Reporter Reports Activity
Activity – Export/Import Performance Reporter reports using GUI
14
4. Ad-hoc Real-Time Reporting
Overview
Tuning Manager Performance Reporter reports provide performance metrics at a minimum interval of 10
seconds only. To monitor and analyze real-time metrics for troubleshooting intermittent performance
issues, Hitachi Tuning Manager (HTnM) provides a command to monitor critical storage performance
metrics at a minimum interval of 1 sec.
Objectives
Upon completion of the lab project, you will be able to:
Retrieve performance metrics at 1 second interval using the command jpctdraidperf
Summary of Activity
Execute the jpctdraidperf command
References
Hitachi Command Suite Tuning Manager CLI Reference Guide, Chapter 5 - Collection Manager
Commands and Agent Commands
____________________________________________________________________
7. Run the command with these options and investigate the output.
8. Which type of resources were accessed?
_______________________________________________________________________
15
4. Ad-hoc Real-Time Reporting Activity
Activity – Establish Ad hoc real time reporting
16
5. REST API
Overview
The jpcrpt command is available to collect performance data from HTnM Agents using XML file for
request parameter. REST API enables you to collect performance data from a client server by use of a
uniform interface (HTTP GET/PUT/POST/DELETE) platform and language independent from a client
server. REST API is available for Agent for RAID and Agent for NAS.
Objectives
Upon completion of the lab project, you will be able to:
Use the REST API to run the appropriate commands to retrieve target resource information
Execute REST commands using “curl”
Summary of Activity
Execute commands to get API information
Obtain the Agent list
Use curl to retrieve storage performance data
References
Hitachi Command Suite Tuning Manager API Reference Guide
1. Connect to your Host Server HCS-2 and create a new directory called curl on the C-Drive of it.
2. Download Curl from the Web and unzip it into this directory.
3. Ask your instructor for help if necessary.
4. To fetch API version information, open a web browser and type
http://10.67.77.154:22015/TuningManager/v1/configuration/Version
5. Save the result to a directory of your choice.
6. Open the output file and interpret the information.
7. Which API version is installed? ______________________________________
8. To obtain a list of all the REST API capable Agents installed use the web browser with
http://10.67.77.154:22015/TuningManager/v1/objects/Agents?agentType=ALL
9. Again save the output and open it for investigation of the information.
10. Which Agents are installed and what is the product version of the Agents?
_________________________________________________________________________
11. Open a command prompt and change to the curl directory.
12. Run the following commands.
17
5. REST API Activity
Activity – Execute REST API commands
13. Compare the information of output of the 2 commands executed with curl to the information in the
output files produced by the web browser in the steps above.
14. To fetch performance data collected by the Agent for RAID instance the options need to define
precisely what kind of information needs to be fetched .
15. Provide the following curl command line information:
curl -u system:manager -X GET
"http://10.67.77.154:22015/TuningManager/v1/objects/RAID_PI_CLPS?hostName=
HCSLAB4-B7&agentInstanceName=G1000_58078"
16. What type of metrics are presented as an output?
_________________________________________________________________________
17. Compare this information with the result of running the appropriate report from Performance
Reporter GUI.
18. More command options imply use of start time and end time as well as specific metrics specifications
like
curl -u system:manager -X GET "http://10.67.77.154:22015/TuningManager/v1
/objects /RAID_PI_LDS?hostName=HCSLAB4-B7&agentInstance Name=G1000_58078
&startTime=2016-02-04T12:00Z&endTime=2016-02-04T19:00Z&fields=
RECORD_TIME%1FLDEV_NUMBER %1FRANDOM_TOTAL_IO_RATE&LDEV_ NUMBER=00:06:00"
19. Refer to the Hitachi Command Suite Tuning Manager API Reference Guide for more information
and exercise until you are satisfied.
18
6. Performance Problem Troubleshooting
Overview
You will apply the troubleshooting methodology to first identify if the reported performance problems
require inside or outside the Storage system investigation.
If the decision is that further performance data from storage needs to be taken into account, key
metrics analysis presented in HCS together with direct links to Performance Reporter predefined Reports
will assist you in finding the possible cause of the issues.
Objectives
Upon completion of the lab project, you will be able to:
Use HCS software together with Tuning Manager software to troubleshoot and identify host and
storage system problems
Summary of Activity
This lab activity describes the process of identifying the cause of performance issues.
References
Hitachi Tuning Manager Users Guide
Scenario:
A server administrator reports a decrease in performance of a specific application running on the host
server HCS-2.
1. Connect to the Performance Reporter GUI and check if one of the set alarm triggered.
2. Use the Display Alarm Status function of the Agent instance in question.
3. Run the associated report and investigate the data.
4. Navigate back to Tuning Manager Main Console and use the Dashboard to link to HDvM.
5. Click the Analytics tab and select Hosts in the Analytics task column.
6. Expand All Hosts and select the host server reporting the performance problem.
7. Select all the resources of that host and run the Identify Performance Problems task.
8. Advance to the Target Selection window and select G1000/ DP Volume Internal in Step1.
9. Stay with “Select all” in Step2 and adjust the Time Period to Analyze to a time window covering
about 24 hours around the time the problem was reported.
10. Step through each of the available display windows investigating the presented metrics.
11. Note the time when the problem first occurred.
12. Adjust the Time to Analyze to cover an hour around the time the problem first occurred.
13. Investigate all the presented metrics again, realize that port, cache and MP metrics look normal.
19
6. Performance Problem Troubleshooting Activity
Activity – Identify Performance Problems
14. To find a possible cause of the Parity Group Busy well exceeding the set “Caution Threshold”,
close the Identify Performance Problem wizard.
15. Select the Enterprise Storage System from the Navigation pane of the Analytics tab.
16. From the All Storage Systems> Action dropdown list, run Storage Performance Analysis per
Host and adjust the time window to a time around the problem occurrence.
17. Select both Hosts and click Show Chart.
18. Add the metric IPOS to the same Analysis view.
19. Draw your own conclusions from the metrics presented.
20. Interpreting the graphs should lead to the conclusion that a heavy workload from Server HCS-1
started shortly before the performance bottleneck became visible on HCS-2.
21. A possible solution could be not to run those 2 applications at the same time or move the target
LDEVs to a different DP Pool (different Parity Groups)l.
To simulate workload differences between MP Blades, setup Iometer for this exercise as follows.
On your Management server HCS-1, Setup 1 Manager with 1 Worker
Disk Targets : Drive H:> trough Drive K:> (4 Basic Volumes attached to
the Host)
Access Specification: 512B, 100% Read/W; 50% Sequential / Random
Scenario:
We assume that Health Check reports indicate that one of the MP Blades has a much higher Busy Rate
that the other MPB(s). You will use the Analyze MP Blades/Units function to find the top busy
resources of the MPBs and simulate the effect of re-assigning LDEVs to different MPB(s). A script will be
generated to perform the re-allocation at a planned time. Use the raidcom command to execute that
script.
1. First find out which LDEVs are handled by which MP Blade.
2. Click the Analytics tab, select Host > Windows and your HCS-2 server.
3. Run the Identify Performance Problems Wizard against all the volumes of that server.
4. From the Target Selection screen, choose for the DP Volumes as “storage type/volume type’
5. Advance with clicking Next to screen number 4 “Volume”.
6. In the table Volumes, the column “MP Blade/Unit” shows the MP Blade – LDEV assignment.
7. Repeat the above for the basic volume assignments.
8. Close the Identify Performance Problems Wizard.
9. Select Storage Systems as a target for the Analytics function.
10. Choose the enterprise storage system registered to your lab.
11. In the dropdown list of the Actions button in the Information Summary Area, select the function
Analyze MP Blades/Units.
12. Which metrics are displayed?
________________________________________________________________________
IMPORTANT! Read the Introduction Information presented in the Guidance column. It explains the
purpose and the detailed functions and steps that can be performed with this feature.
20
Activity 6. Performance Problem Troubleshooting
Activity – Identify Performance Problems
13. Select the MP Blade with the highest Busy Rate % and move the “target line” over the spot with that
highest Busy Rate %.
14. Click on Choose as Target MP Blade/Unit. An additional Graph for the selected MPB opens.
15. From its Column Settings table, identify the LDEV with the highest Usage Rate.
16. Lock the LDEVs you do NOT want to move.
17. Now select the LDEV to be moved.
18. Select another MP Blade (less busy) from the table on top.
19. When you click the button “Choose as Destination MP Blade/Unit” another graph for the just
selected MP Blade is added.
20. Click the Move button and the Analyze MP Blades/Units function will simulate the effect of the re-
allocation of the previously selected LDEV.
21. Which changes can you spot in both Top Resources windows?
______________________________________________________________
22. Repeat the above steps to simulate re-allocating another LDEV with high Usage Rate.
23. Scroll down to the bottom of the screen and click the button Generate Script Commands.
24. Read the information on the screen presented.
25. Copy the script(s) to Notepad for later use and save the file.
26. Close the Analyze MP Blades/Units window and notice the information presented.
27. HORCM is used to run the raidcom command.
28. Ensure the product “ RAID Manager (HORCM)” is installed on HCS-1.
29. If it isn’t, ask your instructor for the software and install it on your Management server.
30. Use notepad to create the horcm100.conf file looking like the copy below (replace IP address and
CMD specification to match your HCS-1 server.
31. Save the file as horcm100.conf (not as text file) to the Windows root directory of HCS-1.
32. Open a command prompt on you HCS-1 Server and change directory to HORCM>etc>.
33. List all the command available.
34. Execute the command set horcminst=100.
35. Start the instance with the command horcmstart 100.
36. Run raidcom –login and provide login userid and password to the SVP of the enterprise storage.
(this should be a unique login user which you can create with the user administration functions of
the storage).
37. Copy the script produced earlier by the Analyze MP Blades/Units function to the command line to
execute the re-allocation script(s).
21
6. Performance Problem Troubleshooting Activity
Activity – Identify Performance Problems
38. After about 5 minutes, re-run the Analyze MP Blades/Units function and observe the result of
the LDEV re-allocation.
39. Verify the successful re-allocation after the script has finished.
Scenario:
To be able to take proactive measures for the case that storage system performance is changing
towards unwanted threshold, you decided to run scheduled Health Check Reports.
22
7. Sizing Tool
Overview
Objectives
Upon completion of the lab project, you will be able to:
Determine the size of Tuning Manager database and agent stores based on a given environment
configuration
Change the size of Tuning Manager database
Summary of Activity
Use the Hitachi Tuning Manager Server Sizing Tool for Windows and Linux
Use the Hitachi Tuning Manager Agent Sizing Tool
References
Hitachi Tuning Manager Sizing Tools
1. Open the provided Hitachi Tuning Manager 8 Server Sizing Tool file.
2. In case it is not already provided, select the link stated in References and download the files.
3. Investigate the options in the different excel files available.
It is important to know is the required capacity for HiRDB (Memory) and the Disk space required for
a given configuration.
4. Make yourself familiar with the information and setup in the file - Hitachi Tuning M anager 8
Server Sizing Tool for W indow s and Linux .
5. Click the tab worksheet and provide an active system configuration to obtain a required database
size in GBs as a result.
6. Follow the step by step procedure for expanding database capacity for Windows (Linux) by selecting
the appropriate Appendix xxxx tab of the Excel sheet.
Important to know is the capacity and disk space (Physical memory size) used for Agent instances
configured on a server.
23
Activity 7. Sizing Tool
Activity – Database Management
End of Labs
24