System software and firmware status, Workload and performance history – HP ProLiant DL980 G7 Server User Manual
Page 67
To specify the catalog location, specify the local directory containing the HP catalog file
(hpsum.exe). This directory must be on the system where HP ESO is running. If that location also
contains HPSUM components, HP ESO will perform software discovery in local mode (comparing
all the components in the directory directly with the ones installed on the current system); otherwise,
HP ESO performs the software discovery in Web mode by connecting to an HP File Transfer Protocol
(FTP) site (ftp.hp.com) to obtain the latest catalog. This requires Internet connectivity.
NOTE:
The logged-in account for the current Microsoft Windows session must have access to
the specified local directory. Moreover, HP ESO only supports HPSUM version 5.3.5.0 or earlier.
NOTE:
If you specify a shared network drive, the software discovery fails by default. To work
around this issue, copy the catalog file to a non-networked drive (for example, C:).
If you must use a network drive, use SysinternalsSuite by Mark Russianovich (). PSEXEC is the only tool needed.
Perform the following steps:
1.
Open up a new command window and run: psexec -s cmd.exe
2.
Run the net use command or any other script to create the network drive.
Clicking the Software Discovery RUN button runs the system software discovery and updates.
Results are shown on the same page (in the Optimization section’s System page). Status of the
latest discovery also displays below this button.
System software and firmware status
This section of the page lists (from the Reference Catalog) the status of software and firmware
components, as shown in the example in
. The status information is displayed
after you run Software Discovery. The status table describes each component and indicates the
latest available version of the component and the component status (whether it is up to date or
needs to be upgraded).
Figure 57 System software and firmware status
Reports pages: Viewing workload/performance data and saving/restoring
SQL configurations
Reports pages include the Workload and Performance History page and the Save/Rollback
Configuration page.
Workload and Performance History
Use the Workload and Performance History page to select and view data collected by the data
collection process (the data collection process is described in
“Collecting data for analysis and
optimization recommendations” (page 31)
).
shows an example of a Workload
and Performance History report. You can view a graph of the data collected, save the data to a
file, and compare graphs of two different data collection sources.
Reports pages: Viewing workload/performance data and saving/restoring SQL configurations
67