Figure 3-2 LU Access Conflict
Fail-Over
Failure of shared NIC service might not be detected (depends on the timing
failure occurring when using MSCS/MSFC). Switching from Active server to
Standby server would not be executed if the failure is not detected.
Table 3-3 Failure Detected Location
Location of Failure
Switching Server
Guest OS
Switchable
LPAR manager
Hyper Visor
Switchable
FC Sharing Service
Switchable
NIC Sharing Service
Un-switchable case exists
1
Notes:
1
.
All applied NICs for the Guest OS become unusable if a failure occurs in the shared
NIC service. In this case, the Guest OS cannot access network at all, though the
other functions work normally. So the Guest OS not releases Quorum disk.
Therefore the Active State of server cannot be switched to the Standby server which
cannot obtain the Quorum disk.
Guest OS has to be shut-down from management PC by using remote console
function when a failure occurred in the shared NIC service.
3-8
High Reliability Functions
Hitachi Compute Blade 500 Series Logical partitioning manager User's Guide
Содержание CB 520A A1
Страница 238: ...6 6 LPAR manager backup Hitachi Compute Blade 500 Series Logical partitioning manager User s Guide ...
Страница 376: ...8 6 LPAR manager Dump Collection Hitachi Compute Blade 500 Series Logical partitioning manager User s Guide ...
Страница 530: ...C 4 Console Types Hitachi Compute Blade 500 Series Logical partitioning manager User s Guide ...
Страница 536: ...D 6 LPAR manager use Port numbers Hitachi Compute Blade 500 Series Logical partitioning manager User s Guide ...
Страница 542: ...E 6 System Configuration Hitachi Compute Blade 500 Series Logical partitioning manager User s Guide ...
Страница 557: ...Hitachi Compute Blade 500 Series Logical partitioning manager User s Guide ...