Index
Numerics
1-to-1 switchover configuration
example of hardware configuration (BladeSymphony (Basic mode)) (1 chassis)
example of hardware configuration (BladeSymphony (Basic mode)) (2 chassis)
example of hardware configuration (BladeSymphony (LPAR mode)) (1 chassis)
example of hardware configuration (BladeSymphony (LPAR mode)) (2 chassis)
example of hardware configuration (PC/AT-compatible system from another company)
A
B
C
changing settings and operations while HA Monitor and servers are running
changing settings and operations while HA Monitor and servers are running (command)
cluster hot-standby switchover configuration
command
configuration
connection interval and count,
D
E
F
failure
file descriptors for commands that are executed from HA Monitor
file system
function for controlling hot standby based on availability of LAN communication
function for controlling hot-standby switchover based on availability of LAN communication
G
H
HA Booster
HA Monitor
HA Monitor processing after detection of server failure (monitor mode)
handling failure in path to shared disk (if path to shared disk is made redundant)
host name
hot standby flow
hot standby operation
hot-standby configurations, checking settings and definitions between multiple
hot-standby switchover
hot-standby switchover in online serverless mode, [2], [3], [4]
K
L
load
M
methods of connection between failure management processor and reset path
monitor-mode program
monitoring in standby system
monitoring LAN
monitoring of disk for business use
monitoring paths
N
O
P
parameters that are passed based on change in server's status
planned hot-standby switchover and controlling switchover order after server failure in monitor mode
processing
processing flow
for connecting and disconnecting shared resources (resource server)
for hot-standby switchover in event of server failure (in server mode)
for starting a server (in case where active server is monitored in monitor mode)
for starting server (in case where monitoring is performed in standby system in monitor mode)
for terminating server (in case where active server is monitored in monitor mode)
hot standby error in event of host failure (monitor mode) (when releasing in reverse order)
hot standby error in event of host failure (server mode) (when releasing in reverse order)
hot standby error in event of server failure (monitor mode) (when releasing in reverse order)
hot standby error in event of server failure (server mode) (when releasing in reverse order)
hot standby processing in event of server failure (monitor mode) (when monitoring UAP)
hot standby processing in event of server failure (monitor mode) (when releasing in reverse order)
hot standby processing in event of server failure (server mode) (when releasing in reverse order)
hot standby processing in event of UAP failure (monitor mode) (when monitoring UAP)
start retries in event of failure on active server after hot standby processing (monitor mode)
terminating server (in case where monitoring is performed in standby system in monitor mode)
terminating servers (monitor mode) (when releasing in reverse order)
terminating servers (server mode) (when releasing in reverse order)
Q
query response message retry
R
S
SCSI reservation of shared disk (if LVM is not used)
SCSI reservation of shared disk (if LVM is used)
correspondence between start order and parent-child relationship
determining active or standby (when using multi-standby function)
parent (correspondence between start order and parent-child relation)
patrol (server failure monitoring time) (server definition statement)
ph_threshold (time when server monitoring history is to be obtained) (servers definition statement)
sby_actcommand (command executed when standby server starts)
sby_termcommand (command executed when standby server terminates)
that does not release reservation, dealing with (using SCSI reservation for shared disk)
server alias name
server start command
server termination command
service name
setting for delaying message output when standby server begins to wait for start of active server
setting whether to issue warning message when hot-standby switchover is impossible
setting whether to output message when server termination processing is completed and when grouped-system switchover processing is completed
setting whether to skip disconnection of volume groups
slowdown
specifying server information in active system that is to be inherited (command)
starting
status
system disk monitoring
T
terminating
U
UAP monitoring
V
W
when using hybrid fencing