HP XP P9000 Performance Advisor Software - Manual (Page 60)

schedule. For information on scenarios related to split performance data collection
schedules, see
“Example use cases” (page 62) .
◦ If you split the components into two performance data collection schedules, then while
displaying the performance data of the components, HP XP P9000 Performance Advisor
v5.5.1:
– 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 XP P9000 Performance Advisor collects performance
data on all LDEVs in the XP and the P9000 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 station 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.
•
If you split the external RAID groups, RAID groups, ThP pools, and the snapshots into two
schedules, you cannot see the Total I/O, Total MB/s, and the Total Tracks fields in the LDEV
table.
•
If you split the journal LDEVs, external RAID groups, RAID groups, ThP pools, and the snapshots
into two schedules, and in charts, you select All from the LDEV drop-down box, the combined
data points from both the schedules are plotted on the chart. In addition, repeated time stamps
are displayed if the collection frequency for both the schedules is the same. As a result, incorrect
values are plotted on the graph.
For more information about charts, see “Plotting charts” (page 236) .
•
If you are collecting the performance data for the first time, it takes longer than usual for HP
XP P9000 Performance Advisor to collect the data. The subsequent performance data collection
is as per the time specified in the Frequency section.
•
If you have performed a one-time configuration data collection and later the XP or the P9000
disk array configuration is modified, HP recommends that you perform a fresh configuration
data collection, so that the performance data collected is for the latest configuration.
Initially, when performance data collection is not yet configured for the XP and the P9000 disk
arrays, the following details are displayed in the Performance Collection table, under the
Performance Collection tab:
60 Collecting configuration and performance data