Upgrading Logical Servers to HP Insight Dynamics 6.0

To correct these problems, you may have to reset you
r hosts after an upgrade. The following
sections provide links to more information.
Upgrading an imported Virtual Connect logical server with an
unassigned network becomes inoperable
If you are upgrading your CMS from Insight Dynamics - VSE 4.1 to Insight Dynamics 6.0 or 6.0
Update 1, a Virtual Connect logical server that was imported (not created) in version 4.1 and
contains an unassigned network will be inoperable after the upgrade.
If this occurs, perform the following steps.
1. Unmanage the inoperable logical server using Delete -> Unmanage Logical Server….
2. Re-import the server blade as a logical server using Tools -> Logical Servers -> Import….
Host reset configuration
After an upgrade, an existing logical server may not be reactivated on its pre-upgrade assigned
host. If this occurs, you may need to reset the ESX or Hyper-V or Virtual Connect hosts in your HP SIM
environment.
For information about resetting ESX hosts, see:
HP Insight Control virtual machine management 6.0 User Guide
For information about resetting Microsoft Hyper-V hosts, see:
Windows Server 2008 and Windows Server 2008 R2 Technical Library
For information about resetting Virtual Connect hosts, see:
HP Virtual Connect Enterprise Manager User Guide
After reconfiguring your host, if the logical server is still not activated, unmanage the logical server,
then reimport it.
Unmanage and reimport a logical server
If the steps in the preceding section do not reset your logical server, and your logical server has
an installed operating system, try unmanaging and then reimporting the logical server.
9