Hitachi Compute Blade 500 Series User Manual page 108

Note:
• You MUST follow the above procedure. If not, serious failure might occur
due to duplication of WWN and MAC address.
Taking over LPAR manager firmware version when using N+M cold
standby
• The explanation about taking over LPAR manager firmware version when
using N+M cold standby is as follows.
1. When the LPAR manager firmware version which is being operated on
the active server blade is installed on the standby server blade, select the
LPAR manager firmware version on the standby server blade.
2. When the LPAR manager firmware version which is being operated on
the active server blade is not installed on the standby server blade, select
the newest LPAR manager firmware version in the upper-limit of
upgradable/updatable version on the standby server blade.
3. When the newest LPAR manager firmware version on the standby
server blade is older than the LPAR manager firmware version which is
being operated on the active server blade, N+M cold standby don't
succeed.
Time Setting in Switchover and Recovery with N+M Cold Standby
• This subsection describes the time setting in switchover and recovery with
N+M cold standby environment.
¢
¢
3-8
Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide
4. When you have the backup of configuration information, shut down
the LPAR manager, and then restore the configuration information.
Problem
Time difference may occur when switchover or recovery occurs in N
+M cold standby environment due to the difference for BIOS time in
specifications between the OS on a virtual platform and the OS on
Basic.
This problem may occur if all the following three conditions are
satisfied.
1. The Compute Blade System uses N+M cold standby function.
2. The following OS shown in (a) and (b) on Basic or on a virtual
platform are mixed in the same N+M cold standby group.
(a) OSs and virtual platforms that recognizes BIOS time as local time
- Windows with Hyper-V
- LPAR manager
- Red Hat Enterprise Linux with Local time as a setting value
- VMware ESX 3.5 with Local time as a setting value
(b) OSs and virtual platforms that recognize BIOS time as UTC
- VMware ESX 4 or later: VMware ESX 4.0; VMware ESX 4.1
- Red Hat Enterprise Linux with UTC as a setting value
- VMware ESX 3 with UTC as a setting value
High Reliability Functions