Using Serviceguard Extension for RAC, 9th Edition, September 2010

ManualsBrandsHP ManualsSoftwareHP Serviceguard Extension for RAC (SGeRAC)

NETWORK_INTERFACE lan2

STATIONARY_IP 10.142.2.4

STATIONARY_IP fec0::8e02:0:0:a8e:4

STATIONARY_IP 3ffe:1000:0:8e02::a8e:4

# CLUSTER_LOCK_LUN

# Route information

# route id 1: 16.89.114.145

# route id 2: 10.142.1.4

# route id 3: 10.142.2.4

# CAPACITY_NAME

# CAPACITY_VALUE

# Warning: There are no standby network interfaces for lan0.

# Possible standby Network Interfaces for lan1: lan3.

# Warning: There are no standby network interfaces for lan2.

# Cluster Timing Parameters (microseconds).

# The MEMBER_TIMEOUT parameter defaults to 14000000 (14 seconds).

# If a heartbeat is not received from a node within this time, it is

# declared dead and the cluster reforms without that node.

# A value of 10 to 25 seconds is appropriate for most installations.

# For installations in which the highest priority is to reform the cluster

# as fast as possible, a setting of as low as 3 seconds is possible.

# When a single heartbeat network with standby interfaces is configured,

# MEMBER_TIMEOUT cannot be set below 14 seconds.

# Note that a system hang or network load spike whose duration exceeds

# MEMBER_TIMEOUT will result in one or more node failures.

# The maximum value recommended for MEMBER_TIMEOUT is 60000000

# (60 seconds).

MEMBER_TIMEOUT 14000000

# Configuration/Reconfiguration Timing Parameters (microseconds).

AUTO_START_TIMEOUT 600000000

NETWORK_POLLING_INTERVAL 2000000

# The optional CONFIGURED_IO_TIMEOUT_EXTENSION parameter (microseconds) is used

# to increase the time interval after the detection of one or more node

# failures that all application activity including pending I/O on the

# failed node is guaranteed to have ceased. This parameter is required to

# be set for Extended Distance Clusters with iFCP interconnects between

# sites. See the manual 'Understanding and Designing Serviceguard

# Disaster Tolerant Architectures' for more information.

# CONFIGURED_IO_TIMEOUT_EXTENSION 0

# Network Monitor Configuration Parameters.

# The NETWORK_FAILURE_DETECTION parameter determines how LAN card failures are detected.

# If set to INONLY_OR_INOUT, a LAN card will be considered down when its inbound

# message count stops increasing or when both inbound and outbound

# message counts stop increasing.

# If set to INOUT, both the inbound and outbound message counts must

# stop increasing before the card is considered down.

NETWORK_FAILURE_DETECTION INOUT

# NETWORK_AUTO_FAILBACK

# When set to YES a recovery of the primary LAN interface will cause failback

# from the standby LAN interface to the primary.

# When set to NO a recovery of the primary LAN interface will do nothing and

# the standby LAN interface will continue to be used until cmmodnet -e lanX

# is issued for the primary LAN interface.

NETWORK_AUTO_FAILBACK YES

# The HOSTNAME_ADDRESS_FAMILY parameter specifies the Internet Protocol address

# family to which Serviceguard will attempt to resolve cluster node names and

# quorum server host names.

# If the parameter is set to IPV4, Serviceguard will attempt to resolve the names

# to IPv4 addresses only. This is the default value.

# If the parameter is set to ANY, Serviceguard will attempt to resolve the names

# to both IPv4 and IPv6 addresses. The /etc/hosts file on each node must contain

# entries for all IPv4 and IPv6 addresses used throughout the cluster including

# all STATIONARY_IP and HEARTBEAT_IP addresses as well as any other addresses

86 Serviceguard Configuration for Oracle 9i RAC