HP Insight Dynamics 6.0 Release notes

Managing a CMS as a logical server is not supported
HP strongly recommends that systems running Central Management Server (CMS) software not
be managed as logical servers. This includes the Insight Dynamics CMS, as well as any other
CMS managed by the Insight Dynamics CMS.
Note that logical server management does not prevent you from managing a CMS as a logical
server. For example, Insight Dynamics will allow any managed node, including the CMS, to be
selected for moving or other logical server operations; doing so may result in unpredictable
results.
Moving a logical server from a Microsoft Hyper-V R2 host to a Hyper-V R1 host is not supported
A limitation from Microsoft prevents you from moving or reactivating a virtual machine logical
server from a Microsoft Hyper-V R2 host to a Hyper-V R1 host. An error message is displayed
if you attempt the operation.
You can move or reactivate a virtual machine logical server from a Hyper-V R1 host to a Hyper-V
R2 host.
NOTE: The Hyper-V host version is shown in the Platform column in the Available Target
Hosts table on the activate or move logical server target screen. The host is a Hyper-V R1 host
if the host version begins with 6.0 (for example, 6.0.6001 or 6.0.6002 in Windows 2008 Server –
Hyper-V SP1 or Windows 2008 Server – Hyper-V SP2). The host is a Hyper-V R2 host if the host
version begins 6.1 (for example, 6.1.7077 in Windows Server 2008 R2).
Suggested action Be certain that you want to move or reactivate the logical server from Microsoft
Hyper-V R1 to R2 before you complete the operation. After the operation completes, you cannot
move or reactivate the logical server back to Hyper-V R1.
Configure logical server storage for multiple storage ports before activation
If you modify a storage entry to add additional ports (to implement multi-pathing of storage)
and then attempt to reactivate its associated Virtual Connect logical server, the activation fails
with the error "No such fabric in VCEM” and the logical server can no longer be activated. This
issue occurs only if the storage entry is associated with a logical server, and the logical server
has been previously activated.
To avoid this problem, HP recommends configuring the logical server's storage for multiple
ports before activating the logical server, and using either SAN zoning or storage presentation
to limit the server's access to a single path as needed. If you configured the logical server with
one port, activated the logical server, and now need to add additional ports, perform the following
steps.
Suggested action
1. Ensure that the logical server's storage entry has been inserted into the storage pool. Pool
entries are listed in the Storage Pool Entries table viewable by selecting Modify→Logical
Server Storage Pools....
If you are unsure if the logical server's storage entry is a pool entry, select the logical server,
then use the Modify→Logical Server... menu selection and select the Storage tab. The
Storage Assignments table shows the storage entry for the logical server. If the Modify button
is not available (and only the View button is shown), then the storage entry is already in the
storage pool, and you can continue to step 2. If the Modify button is available, click Modify
to view the next screen. Check the "Insert Storage Entry into Pool" checkbox at the top of
the screen, and click Save.
2. Deactivate the logical server if it is currently active, using Tools→Logical
Servers→Deactivate....
Logical server management 29