HP Capacity Advisor 7.2 User Guide

scenario is created with systems having imagined names. When this occurs, the scenario change
record (Undo/Edit/View screen) indicates an error; the scenario is corrupted and cannot be
repaired. Suggested action: Create a new scenario, replacing the no-longer-unique “what-if” systems
with new, uniquely named systems. Delete the corrupted scenario.
Note that this naming corruption can also occur when using “what-if” workloads or “what-if”
VMware DRS clusters in a scenario. The problem and remedy are the same in each case.
Want to reuse a system name but seeing a name duplication error
Name duplication errors can occur in these situations:
• when trying to create a “what-if” system using the same name as an existing system.
You cannot reuse an existing system name.
• when trying to create a “what-if” system using the same name as a “what-if” system already
in use in the same scenario.
Suggested action: Edit the system attributes of the original “what-if” system (What-If Action→Edit
System...)
This remedy will not be sufficient if you have defined the original “what-if” system to have no
power calibration, and then decide that you want the system to have power calibration. The
Edit System screen does not provide the opportunity to edit power settings. Where it is important
to reuse the system name and add power calibration, do the following:
◦ Select the original “what-if” system and remove it from scenario. (Edit→Remove Systems)
◦ Delete both the “create system” and “remove system” actions from the scenario change
record. (What-If Action→Undo/Edit/View Applied What-If Actions)
◦ Re-create the system using the same name, but with new attributes, including power
calibration. (What-If Action→Create Systems...)
Workloads no longer available in a scenario
With the 6.0 release, monitored workloads on Linux were no longer supported or recognized.
This means that scenarios that still contain representative Linux systems that once had monitored
workloads will be broken. Suggested action: Remove these systems from the scenario (Edit→Remove
Systems...), and then re-add them Edit→Add Existing Systems...).
A profile viewer has error message and no profile graph
The error message that you would see in this situation:
Unable to write the following file: I/O error writing PNG file!
This occurs when a profile viewer is unable to write temporary files to the CMS storage space.
Suggested action: Check that permissions are correct for writing to the storage space, and check
to see if the storage space is full.
Working with power
Data collection method for Linux systems affects access to automatic power
management
Utilization data for Linux systems are obtained using a native collection method that is automatically
assigned to managed Linux systems by the Insight managed system setup wizard.
Working with power 169