 |
» |
|
|
|
For additional information not included in the
online help and documentation for VSE Software, see Insight Dynamics VSE 4.1 Update 1 Documentation Addendum. Major Issues | |
The following are general
major issues for VSE software. Network Utilization May Be Unreliable Due To WMI Counter Rollover
When Using Agentless Data Collection on Windows Server 2003The performance counters that are queried during
agentless data collection are 32-bit values on Windows 2003 servers.
Windows 2003 servers that have high network utilization can cause
these performance counters to overflow. When this occurs, Virtualization
Manager may report a negative utilization value or a value sometimes
significantly lower than the actual utilization. In addition, “Collect Capacity Advisor Data" may display
the following warning: Warning: The Network I/O utilization values for system [hostname] may be inaccurate due to WMI performance counter rollovers. |
When this warning is displayed, one or more network I/O utilization
samples were invalidated and not used for calculating the 5-minute
averages for network utilization stored in the Capacity Advisor database. Workaround Lower the polling interval for the agentless data
collection service by using the SIM menu Configure->Configure
VSE Agentless Collection->Advanced Agentless Options. Depending
on the level of network utilization of the server, this workaround
may not completely eliminate the issue. Furthermore, lowering the
polling interval may impact the CMS's overall performance. ESX Hosts May Fail to Return Performance Data, Resulting in
Incorrect (Zero-Valued) Resource Metrics Reported in Capacity Advisor
and Visualization Tab MetersIn some cases, the VMware management agents running
on an ESX host may fail to return performance data to both HP Virtual
Machine Management (which is used by Virtualization Manager and Capacity
Advisor for collecting performance data for ESX hosts) and VMware
Virtual Center (the VMware Infrastructure Client). Indications of this issue: VMware Virtual Center/VMware
Infrastructure Client: The Performance tab for the ESX
host, and any guests configured on the host, will display the error “Performance data is currently not available for this entity”. Virtualization Manager: Visualization Tab meters will display 0 for all metrics (CPU, Memory,
Network and Disk utilization) for these ESX hosts and guests. Capacity Advisor: Profile Viewer will display 0 for all metrics (CPU, Memory, Network
and Disk utilization) for these ESX hosts and guests, for some period
of time.
Workaround | | | |  | NOTE: In other cases where Virtual Machine Manager may fail to collect
performance data from an x86 virtual machine host (either VMware ESX,
Microsoft Virtual Server or Microsoft Hyper-V), Virtualization Manager
will correctly display an error and Capacity Advisor will correctly
omit the data (indicated by gaps in data in the Profile Viewer) for
these hosts and their guests during these intervals. In any case
where data collection appears to be failing for extended periods of
time, rebooting the VM host (or following the procedure, above, in
the case of ESX) may remedy the situation. | | | | |
Minor Issues | |
Systems on the Workload Tab can Erroneously be Displayed as
Unlicensed After Initial HP SIM Discovery This occurs when systems initially get discovered
by HP SIM horizontally (for example, via the enclosure for a blade,
or via the management processor for a partitionable system). When
the system (blade, nPartition, VM guest, etc.) is later explicitly
added and fully discovered (hostname is now known), the Workload tab can lose the workload's association
with the proper host. As a result, utilization data will not be displayed
and the system will be incorrectly identified as not being licensed. Workaround Even though utilization data is not displayed
on the Workload tab, it is correctly displayed
on the Visualization tab. After an HP SIM restart,
data is properly displayed on the Workload tab
as well. Attempting to Migrate or Scan for HP-UX LTU's for Already
Licensed Systems Can Fail If a purchased permanent license is assigned to
an HP-UX node and you subsequently run the vselicense -m command on this node (or press the Scan for HP-UX Licenses button in the VSE Management for Integrity software license screen
or other variants), the command can fail because of the mix of purchased
and migrated licenses. Workaround If you wish to migrate or scan licenses from the
node, do not assign licenses from a purchased key. Some Messages from vselicense Command Point
to Old Licensing Menu Items When using the vselicense command,
certain error messages that should refer the user to the Deploy License Manager menu item in HP SIM, instead refer to the old menu items
(DeployVSE Management
for Integrity software...). Workaround Use the DeployLicense Manager menu. Running the vseassist Command Can “Lock” Capacity Advisor Consolidation Software licenses When an HP Insight Capacity Advisor Consolidation
Software license is assigned to a system, it should not be moved to
the “used” state until the Capacity Advisor product is
used to collect data from that node. Once Capacity Advisor is run
against the system, the license can no longer be unassigned and reassigned
to a different system; the license is locked to the system. Running the vseassist command
for a system in this state likewise has the side-effect of locking
the license to the system (and the clock starts ticking). Workaround Do not assign a Consolidation Software license
to a system until you are ready to use the license. A VM Guest that Migrates from an Unlicensed to a Licensed Host
while HP SIM is Running Will Not be Considered Licensed VM Guests are not explicitly licensed. Instead,
their license state is cascaded from their host. If, while HP SIM
is running and the user is using Virtualization Manager, a guest migrates
from an unlicensed to a licensed host, the license state of the guest
will not change until HP SIM is restarted. Workaround Restart HP SIM.
|
Printable version
