HP Matrix Operating Environment Software - Manual (Page 165)

Edit Scenario window not visible
A couple situations can cause you to “lose” the Edit Scenario window.
•
The window can be blocked by a browser pop-up blocker when you initially try to open it.
Suggested action: Check that you have pop-up blockers turned off in the browser that you use
to control Capacity Advisor functions.
•
In the case where the Edit Scenario window is already open in Mozilla Firefox, but is hidden
beneath other windows when you create a new scenario, it is not obvious that the window
has refreshed with your new scenario information. Suggested action: set Firefox to allow
Javascript to raise or lower windows. Then, when you create a new scenario, the pre-existing
Edit Scenario window will rise to the forefront of the display.
Systems in scenario are not available due to licensing or authorization issues
When a scenario is first created, some systems may not yet be licensed; or over time, licensing on
an existing system may be removed or may have expired, making it impossible for Capacity
Advisor to access data or continue to use the system in a scenario. Suggested action: When this
occurs, the Edit Scenario screen will show a message that allows you to remove the system from
the scenario so that you can continue using the scenario without that system. You can either have
your system administrator apply a license to a system to make it usable in the scenario, or click
the links provided in the message to remove all systems having the problem (or to remove each
system individually).
In situations where you decide to remove the systems from the scenario, you will also want to check
the change record for any entries related to the system (What-If Action
→Undo/Edit/View Applied
What-If Actions). Delete any related entries to completely clean up the scenario so that other errors
will not be triggered by the unlicensed or unauthorized system entries in the change record.
TIP: When a scenario is newly created, it is unlikely that any changes will be recorded for
unlicensed or unauthorized systems in the change record.
A lack of user authorization on systems in a scenario can also affect the usefulness of the scenario
for planning. As above, you can obtain authorization to use the systems or remove them from the
scenario.
Systems in scenario no longer available — scenario seems corrupted
Because names for “what-if” systems must be unique (they do not match names for existing systems
on a real network), it is possible that real systems can be discovered with matching names after a
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.
I want to reuse a system name, but I'm 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
When working in the scenario editor 165