HP StorageWorks XP Performance Advisor Software v4.6 User and Troubleshooting Guide (T1789-96094, June 2010)

14 Troubleshooting issues for resources
associated with applications
This chapter discusses the following topics:
• “Introduction” on page 277
• “Associating applications with hosts” on page 278
• “Viewing performance data for resources” on page 284
• “Viewing variations in LDEVs response time” on page 289
• “Searching for applications associated with resources” on page 283
• “Plotting charts” on page 290
• “Example troubleshooting scenarios” on page 291
Introduction
XP Performance Advisor provides a one-stop location to identify bottlenecks in the performance of
applications residing on hosts that use XP arrays for storing their data. These hosts are identified using
their World Wide Names (WWN).
NOTE:
The term Hosts here refers to systems on which an application resides. They can be hosts that are
completely independent of hosts on which XP Performance Advisor is installed.
An application's response to user requests is determined by the performance of all the associated
LDEVs, which is attributed to the time taken by LDEVs to process requests. Higher response time from
LDEVs leads to increased response time from applications to user requests. Further, an LDEV’s response
time is determined by the performance of the following resources associated with the LDEV:
• Ports (Frontend resources)
• CLPRs (Cache)
• RAID groups (Backend resources)
The performance data for LDEVs, ports, CLPRs, and RAID groups is displayed on the Troubleshooting
screen (“Troubleshooting screen” on page 285) shows the Troubleshooting screen). It is displayed for
a prominent set of metrics that XP Performance Advisor supports. In addition, you can also select
additional metrics and view the performance data for these resources. Analyzing performance metrics
of LDEVs and associated resources helps identify the resource that is actually leading to the application's
high response time. It also enables you to take the necessary corrective action, like load balancing
across resources. For example, one of the reasons for an application's high response time can be
attributed to the heavy IOPS on the port that is servicing requests to multiple LDEVs, which are
associated with different applications.
HP StorageWorks XP Performance Advisor Software User Guide 277