Upgrading incompatible firmware modes and versions – HP Insight Management-Software User Manual
Page 28
Upgrading incompatible firmware modes and versions
If unsupported VC Domain firmware versions are detected at the end of a VCEM 7.2 upgrade, a
warning message similar to the following is displayed:
VCEM detected unsupported VC firmware. For information on how to upgrade
your firmware, run the Insight Software Advisor or refer to the VCEM
User Guide troubleshooting section.
Upgrade to a supported VC firmware by performing the following steps:
1.
Select the VC Domain with an incompatible status and click VC Domain Maintenance.
2.
Upgrade the managed VC Domains to the minimum VCEM supported VC firmware version.
See the
“Mixed VC firmware versions and compatibility in a VC Domain Group ” (page 20)
for the VCEM-supported VC firmware versions.
3.
Click Complete VC Domain Maintenance to close the operation.
4.
Upgrade the VC Domain Group firmware mode to the minimum VCEM-supported VC firmware.
For more information, see
“Upgrading VC Domain Group firmware mode” (page 83)
Installing VCEM in an HA-clustered CMS configuration in a Microsoft
Cluster Server cluster
VCEM can be installed in an HA clustered CMS configuration on an MSCS cluster. This installation
is described in Installing and Upgrading HP Insight Management 7.0 on Windows Server 2008
R2 Failover Clusters. This white paper is accessible in the HP Insight Management documentation
library at
By installing in a failover cluster configuration, the CMS can fail over to a backup cluster node if
the primary node needs maintenance or experiences a failure.
In preparation for a planned failover, ensure that no Insight Management jobs, tasks, requests, or
migration processes are running at the time of the failover. The configuration of the managed
environment should not be changed between powering off the CMS on the primary node and
resuming operations on the backup cluster node.
In the event of an unplanned failover, it is possible that manual intervention may be required to
restore full operations. If a VC Domain reports configuration mismatch or an out-of-sync occurrence
after recovering from an unplanned failover, the following actions are recommended.
•
Execute Mxsync in analysis mode (mysync) to determine the nature of the failure on the VC
Domain during the CMS recovery phase.
•
Execute Mxsync in execute mode (mxsync-e) during the CMS recovery phase, and follow
the Mxsync instructions until the VC Domains are synchronized.
•
If Mxsync detects and reports out-of-sync scenarios in additional subsystems, resolve them
according to instructions displayed, otherwise exit Mxsync.
NOTE:
Executing mxsync –e will help resolve VC Domain synchronization issues across multiple
VC domains.
28
Installing and configuring VCEM