 |
» |
|
|
|
Limitations The following limitations
exist for the online help: The Index of the iCAP Manager help volume is empty. The logical server management topics in the Virtualization
Manager help volume are not localized. These topics appear in the
Japanese help, but the content is English. The iCAP Manager help volume is not localized. This
volume appears in the Japanese help, but the content is English. The search controls in the Japanese help do not function
correctly. Search is available only in the English help. For Japanese
help, consider using the VSE Master Index in place of search.
Major Issues When installing VSE from
the Insight Control Management (ICM) onto a Windows CMS, the VSE installer
may detect that HP SIM is not fully up and running. This problem happens
intermittently and causes the following fatal error during the VSE
configuration process: Initial configuration failed. More information can be found in
C:\Program Files\HP\Virtual Server Environment\logs\vseinitconfig.log |
Then the VSE Uninstall process is displayed. Workaround. Cancel the VSE Uninstall process and then proceed
with the installation of the others ICM components. When the ICM installation
finishes, be sure that HP SIM is running, then run the following command
to install/configure VSE: vseinitconfig -a -x restart_sim=true |
Database Error on Windows Installation. Installing HP Insight Dynamics - VSE on Windows
may produce the following message in C:\Program Files\HP\Virtual
Server Environment\logs\gwlminitconfig.log.0:
SEVERE [17] Error performing database operation: CREATE DATABASE failed.
Some file names listed could not be created. Check related errors.
|
This message is typically displayed when there
are gWLM database files on the system from a previous install that
did not complete. Workaround. Delete the following files: C:\Program Files\Microsoft SQL Server\MSSQL\Data\gwlm.mdf C:\Program Files\Microsoft SQL Server\MSSQL\Data\gwlm_log.ldf If the files are not in that folder, check C:\Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\Data\ where n is some number. Re-install HP Insight Dynamics - VSE. If during the re-install, you get the following message:
ERROR: gWLM - Unable to create DB tables for gWLM.
gWLM init script is exiting with error.
|
as well as the following entry in gwlminitconfig.log.0:
SEVERE [32] Error performing database operation:
Cannot open database "gwlm" requested by the login. The login
failed.
|
use the following commands to remove the database and reinitialize
it: | | | |  | NOTE: NOTE: These commands delete all configuration and historical
data for all VSE components. | | | | |
# vseinticonfig --unconfig --clobber
# vseinitconfig --initconfig
|
If the time zone is not
set properly for the CMS and managed nodes (including issues related
to the change in the start/end of daylight savings time in the US),
VSE Management Software may collect, analyze, or display data incorrectly.
Please see http://www.hp.com/go/dst for information
and pointers to relevant daylight savings time changes needed for
your operating environment. On Windows Server
2003 this would include the need to install the update described by http://support.microsoft.com/kb/942763. When installing VSE from
the Insight Control Management (ICM) DVD onto a
Windows CMS, the VSE installer may detect that HP SIM has not yet
started. This causes the VSE installation to fail partially or completely.
It is also possible that the VSE installer cannot clean up the partial
installation. You must re-run the ICM integrated installer and start
the VSE installation again. If the integrated installer claims that
VSE is already installed, you must first uninstall VSE and then re-run
the ICM integrated installer. Perl version 5.6.1 is
not supported on an HP-UX CMS. You must update Perl to version 5.8.2
or later. By default, HP SIM automatically
performs a daily identify operation at 4:05 PM local time. This can
be disruptive to normal use of HP SIM because many tasks may be deferred
while the identify operation completes. Workaround. If you have a large number of managed systems
and daily identify takes a long time, HP recommends that you change
the scheduled time of the daily identify to a time that is convenient
for users of the system, as well as a time when most managed systems
will be active and can be identified. For more information, consult
the HP Systems Insight Manager User's Guide. Microsoft Virtual Server
(MSVS) guests (virtual machines) are not automatically discovered
when an MSVS host is added to HP SIM. You must manually add the guests.
They will be associated with their MSVS host if VMM is installed. If upgrading a Windows
CMS from an earlier version to this version: VMM, when removed from the CMS, does not clean its
database. So it is necessary to run a cleanup script (C:\Program
Files\HP\Virtual Machine Management Pack\bin\vmmcleandb.cmd) on the CMS after the new bits are installed, but before managed
nodes are re-added to SIM. VMM doesn't cleanly upgrade the VMM agents on
ESX and MSVS hosts from one version to another. Thus, it is necessary
to remove the agents by hand before trying to push out new ones via Deploy Deploy Drivers, Firmware and
AgentsInstall VMM AgentLinux/Windows. To remove the VMM agents from an ESX host, log in as an administrator
and execute rpm -qa | grep hpvmmagent | xargs rpm -e. To remove the VMM agent from an MSVS host, log in as administrator
and go to Add or Remove Programs to remove the “HP Virtual Machine Management Agent”.
VMware ESX Linux virtual
machines discovered prior to upgrading to SIM 5.2.1 (for example,
Linux virtual machines discovered by SIM 5.2.0) may not have the proper
Operating System Type (also known as “OS for Tool Filtering”) attribute set in the SIM System Properties for these virtual machines.
In this case, the result in VSE is: No Linux OS icon is displayed for these virtual machines
on the VSE Visualization tab. No utilization data (CPU, MEM, LAN and DISK meters)
are displayed for these virtual machines on the Visualization tab. No utilization data is collected for these virtual
machines in Capacity Advisor (OptimizeCapacity AdvisorCollect Capacity
Advisor Data... , etc.).
Workaround. To remedy this, perform either of the following
workarounds: (recommended) Edit the System Properties for these
virtual machines in SIM (from the Tools & Links tab of the System Page for these virtual machines in SIM), setting
the “Operating system for tool filtering” field to Linux. After upgrading to SIM 5.2.1, delete and rediscover
any ESX hosts (and all their guests) containing Linux virtual machines
that were discovered prior to upgrading to SIM 5.2.1.
VSE Unable to Manage Serviceguard Clusters and Systems Discovered
after VSE Startup. If you discover a Serviceguard cluster or additional
nodes which are further contained in an existing discovered cluster
in HP SIM after you have already used Virtualization Manager at least
one time in the past, you will not be allowed to create Serviceguard
cluster workloads for the affected cluster. Workaround. An HP SIM restart is required to update Virtualization
Manager's cached Serviceguard data. To create Serviceguard workloads
on these clusters, have HP SIM discover all the nodes in the cluster
and ensure the node's association to the cluster is also discovered,
and then restart HP SIM.
Minor Issues If you will be managing
systems that are Virtual Machines under VMware ESX Servers or MS Virtual
Servers, and/or blades running in Virtual Connect domains, then the
HP Insight Dynamics application may cause faster growth of the HP
SIM audit log. The rate at which the audit
log file grows will increase with the number of virtual machines and
blades you are managing. Workaround. If you are concerned with keeping backups of the
HP SIM audit log to retain an audit log history, then you will need
to monitor the growth of the audit log files and schedule your archiving
tasks to run more frequently to insure the HP SIM auditing data is
retained. You can also use the following information to
increase the size of the HP SIM audit log file to reduce how often
you need to archive it. By creating a file named log.properties under the <HPSIM install folder>\config directory with the following key, you can specify
the maximum size (default is 20 MB) of the log file. Once this limit
is reached, the logs will be rolled over. MX_LOG_FILESIZE = <audit
log size in MB> For example, to increase the file size to 40
MB: MX_LOG_FILESIZE=40 This property file also gives you more control
over the name of the HP SIM audit log file (mx.log) and the role-over filename (mx.log.old). MX_LOG_FILENAME — The base
name of the audit log file name (default “mx”). MX_LOG_FILEEXT — The audit
log extension file name (default “.log”). MX_LOG_ROLLFILEEXT — The
extension file name of the rolled-over audit log file name (default “.old”).
To relocate the log files location to make it
easier to back up, you can create a file named path.properties in the <HPSIM install folder>\config directory and specify the path using the LOG attribute (for example: LOG=C\:\\hpsimlogs). Certain VSE 4.0 components
are generating a large number of HP SIM logins, which are normally
recorded in the SIM audit log and which generate SIM events. A large
number of SIM events can overwhelm and slow down SIM, and a large
number of entries in the audit log will cause the log to roll over
on itself, effectively deleting audit information. Workaround. To resolve these issues: To prevent the large number of HP SIM events for logins:
access the OptionsSecuritySign-In Event Settings menu
and specify Only failed sign-in attempts. To avoid audit log file rolls, either: Create a Windows scheduled task to save copies of
the log before it rolls over. Configure the audit log size in the HP SIM log.properties file. See the topic “Configuring the audit log file” in HP SIM help.
If you see a noticeable
decrease in performance, including slower response times and long
durations of “barber poles”, check the mxdomainmgr process (using the Task Manager on Windows
and the top command on HP-UX). If the memory in
use by the mxdomainmgr process is more than
about 1.2 GB on a Windows CMS and 1.5 GB on an HP-UX CMS, this may
be causing the performance decline and, in rarer cases, out of memory
errors in the user interfaces or HP SIM logs. The increased amount of memory in use may be caused by a larger number
of managed nodes discovered on the CMS, in addition to accumulating
over time the number of times (greater than 30–40) users have
logged in to HP SIM and created browser sessions. Workarounds. Restart the HP SIM service. If VMM is in use on a
Windows CMS, it is also recommended that you restart the VMM service
after the HP SIM restart completes and it is fully up and running. Leaving an HP SIM user session open and logged in
over time, instead of frequent logging in and out, may help minimize
the performance issue.
In order to manage a Windows
CMS (that is, treat the CMS as a managed node in VSE), the WMI Mapper must be installed on the CMS. The WMI Mapper is installed
by default when installing HP SIM on Windows, however it can be deselected
in a custom install, or may be subsequently uninstalled from Add or Remove Programs in Windows. A host other than the
CMS may still be configured as the WMI Mapper Proxy in HP SIM (OptionsProtocol SettingsWMI Mapper Proxy...), however
the WMI Mapper must be installed on the CMS, in order to manage a
Windows CMS in VSE. Troubleshooting Tips for WMI Mapper Proxies. When configuring a WMI Mapper Proxy in HP SIM (OptionsProtocol SettingsWMI Mapper Proxy...), the
proxy host must be discovered in SIM with valid WBEM credentials (WBEM
credentials that are valid on the proxy host). This is required for
SIM to validate the WMI Mapper running on the proxy host. Adding a host in the WMI Mapper Proxy list in HP SIM will cause the host to be discovered in SIM. Therefore,
it may be necessary to configure WBEM credentials for this host (in
either the System Protocol Settings or Global Protocol Settings) after configuring a WMI Mapper
Proxy in SIM. One indication that HP SIM has correctly detected
a WMI Mapper on a Proxy host is by checking the System Protocol
Settings page for that host: if at least one line in the
WBEM credentials list (under the WBEM settings section) includes a port#, then a valid CIMom/WMI Mapper has been detected. After making any changes to the WMI Mapper
Proxy settings, re-identify all Windows hosts that will
use the WMI Mapper to ensure proper redisovery of WBEM connection
information.
When configuring WBEM/WMI credentials for Windows hosts: WBEM credentials configured for hosts that will use
the WMI Mapper Proxy (Windows hosts with no WMI Mapper installed)
must be valid credentials with Administrator privileges on the target
host. These credentials need not be valid on the WMI Mapper Proxy
host. WBEM credentials with Administrator privileges are not required for Windows hosts with a WMI Mapper installed.
See the Systems Insight Manager help and user guides
for more information on WMI Mapper Proxies. If an HP SIM node licensed
for VSE is deleted and re-added with a different name, its license
state will not be reused. This scenario also applies to undeploying
a system on a blade, and deleting the HP SIM node associated with
the blade (typically named by serial number at that point). Workarounds. Workarounds for this issue include: If undeploying and re-deploying an operating system
image on a blade, leave the HP SIM node associated with the blade
in HP SIM. This will allow HP SIM to later update (based on the serial
number of the blade) the license database with the new nodename/host
name when another image is deployed on the blade. For HP Integrity and HP 9000 systems, select the re-added
system and use the appropriate VSE Management for Integrity Licenses
menu option to migrate the license from the old node name to the new
one (by selecting the Show All Licensed Systems option). Change the preferred name of the re-added node to
its original name in the Edit System Properties dialog in HP SIM. This will make the system visible in Virtualization
Manager again. Reverting the name back to its recently added name
will now cause the license manager database to be properly associated
with the new name.
A
configuration change to any managed system that is licensed for VSE
Management Software may not be immediately visible in all the products,
such as Capacity Advisor. This information is updated every five minutes,
but there still can be a period of time when the information that
you can see in the Virtualization Manager Visualization tab may differ from that presented in Capacity Advisor. Workaround. To see a configuration change immediately in Capacity
Advisor, click to the Workload tab in the Virtualization Manager and
then click the Refresh data link on the far right
corner of the screen above the table that lists discovered workloads. Performing name changes
on already licensed systems can cause them to disappear from Virtualization
Manager. Workaround. Rediscover the system using OptionIdentify Systems. In order to perform operations
on active logical servers such as an SMP migration, you must select
the physical blade or VM system from the Physical and Virtual perspective.
Selecting items on the Logical Servers perspective and invoking tools
from the HP SIM tools menu will not function properly in this release. For any HP SIM event that
causes a per-node event to be generated for a virtual machine (like
creating or identifying a virtual machine), Virtualization Manager
can temporarily fail to display this virtual machine, and indicate
it is unlicensed in the error popup—even if its host is licensed. Workaround. Click the Refresh data icon. Performing an identify
of a VM Guest (virtual machine) can temporarily cause the VM Guest
to not be displayed in Virtualization Manager. Workaround. Click the Refresh data icon
in the Virtualization Manager tool bar to resolve the issue. Occasionally, an error
will appear in the mxdomainmgr.log file, beginning
with the following: 16:37:20,359 ERROR [[vmanview]] Servlet.service() for servlet vmanview threw exception
java.lang.IllegalStateException: Current state = FLUSHED, new state = CODING_END
... |
This error may be safely
ignored. It usually occurs when a connection from a web browser is
abruptly terminated during a transfer, such as when a user closes
the browser window while the page is being updated. Errors such as “Specified Vm Guest or Host [hostname]
does not exist within VMM” and/or “Could not initialize
collector for system [hostname]” may be reported when using the Virtualization Manager Visualization tab or the Capacity Advisor ToolsCollect Capacity Advisor Data... menu to collect utilization data for systems that have
been migrated from an ESX Virtual Machine to either Microsoft Virtual
Server (V2V) or to a physical/ProLiant system (V2P). These errors may be due to the "VMware ESX Guest" system
subtype attribute persisting in SIM after the migration. Workaround. In HP SIM, remove the “VMware ESX Guest” subtype for these systems. Open the System Page for the system in HP SIM (for
example, click the system name from the All Systems view), select
the Tools & Links tab, then click the Edit System Properties link. From the Edit System Properties page, change the “VMware ESX Guest” subtype to “<make selection>”(this will remove the subtype). | | | | | NOTE: Uncheck the “Prevent the Discovery, Identification and
Data Collection processes from changing these system properties” checkbox before clicking OK to save the change. | | | | |
Reidentify the system in HP SIM after the subtype
has been removed Use the Quick Launch link from the System Page or use the HP SIM OptionsIdentify Systems... menu. If a node licensed for VSE is deleted and re-added with a different
name, its license state will not be reused. Workarounds for this include: For HP Integrity and HP 9000 systems, select the re-added
system and use the appropriate VSE Management for Integrity
Licenses menu option to migrate the license from the old
node name to the new one. Do this by selecting the Show
All Licensed Systems option. For HP Integrity and HP 9000 systems, select the re-added
system and use the appropriate VSE Management for Integrity
Licenses menu option to migrate the license from the old
node name to the new one. Do this by selecting the Show
All Licensed Systems option.
|
Printable version
