beautypg.com

HP XP Performance Advisor Software User Manual

Page 59

background image

NOTE:

If you plot performance graphs when the configuration data collection is in progress,

there are gaps in the data points. These gaps indicate that the performance data is not collected
during the configuration data collection time interval.

While creating a performance data collection schedule, you can select a command device
that is mapped through two different ports.

While creating performance data collection schedules, you cannot split the components
available in the respective component type lists into two schedules. For example, if you create
two performance data collection schedules, the components that you select from the DKC,
Port, and RG component type lists for the first schedule cannot be included in the second
schedule.

If you create two performance data collection schedules in HP XP7 Performance Advisor
v5.5 and split the components, when you upgrade to HP XP7 Performance Advisor v6.0
and modify a schedule, the following message is displayed when you click Edit:

nl

This is a split schedule with the same component types added in

two schedules. HP recommends that you delete split schedules and

recreate schedules with the similar component types.

nl

After modifying a split performance data collection schedule, if you click Save, the
components that are split are removed, and the remaining components are saved in the
schedule. For information on scenarios related to split performance data collection
schedules, see

“Example use cases” (page 61)

.

If you split the components into two performance data collection schedules, then while
displaying the performance data of the components, HP XP7 Performance Advisor v6.0:

stores the last updated schedule time.

displays the performance data of the components included in the last updated
schedule.

For example, consider that the ThP components are split into two schedules. The available
ThPs are 0, 1, 2, 3, 4, 5, 6, and 7. The first schedule contains the 0, 1, 2, and 3 ThPs
with a collection frequency of four minutes and start time as 4:00 PM. The second schedule
contains the 4, 5, 6, and 7 ThPs with a collection frequency of five minutes and start time
as 4:00 PM. When both schedules start data collection at the scheduled time, you can
view all pools listed on the Array View - Pools screen. When the data collection completes
for the first schedule, you can view the performance data and ThP V-Vols data on the
Array View - Pools screen. When the data collection completes for the second schedule,
you can view the performance data and ThP V-Vols data of the second schedule on the
Array View - Pools screen. However, when the performance data of the second schedule
is updated on the Array View - Pools screen, the performance data of the first schedule
becomes unavailable.

In a multipathing environment, ensure that a command device is not exposed to a host from
two different ports. It stops the current performance data collection, as the schedule configured
to obtain the collection is automatically deleted.

HP

recommends that you set the data collection rate to one hour or less because of management

station

performance and field rollover. HP XP7 Performance Advisor collects performance

data

on all LDEVs in the XP and the XP7 disk arrays that communicate with the management

station

through their respective hosts. The hosts that display their status as Received under the

Host

Information tab constitute the superset of the mapped LDEVs. The performance data

collection

is not limited to the number of LDEVs that the host agent is mapped to use. If you

set

the collection rate too narrow (less than 5 minutes), it results in reduced responsiveness

from

the management station.

Collecting performance data

59