HP Serviceguard Locallanfailoverallowed, Monitoredsubnetaccess, Clusterinterconnectsubnet

local_lan_failover_allowed

This parameter is used to control whether a package fails or not when a primary LAN card fails on a cluster node and its IP addresses are transferred to a standby LAN card. This parameter requires the corresponding subnet to be monitored. Subnet monitoring can be enabled using the monitored_subnet parameter in the package ascii file or cluster_interconnect_subnet parameter on SGeRAC clusters.

Legal values are yes and no. Default is yes.

If local_lan_failover_allowed is set to 'yes', the package continues to run.

If local_lan_failover_allowed is set to 'no', but a subnet configured on the primary LAN is not monitored, when a LAN switch occurs the package continues to run.

If local_lan_failover_allowed is set to 'no', the package behaves such that:

•in case of failover packages, the package will failover to an adoptive node

•in case of multi-node packages, the package fails

monitored_subnet

A LAN subnet that is to be monitored for this package. Replaces legacy SUBNET which is still supported in the package configuration file for legacy packages; see “Configuring a Legacy Package” (page 302).

You can specify multiple subnets; use a separate line for each.

If you specify a subnet as a monitored_subnet the package will not run on any node not reachable via that subnet. This normally means that if the subnet is not up, the package will not run. (For cross-subnet configurations, in which a subnet may be configured on some nodes and not on others, see monitored_subnet_access below, ip_subnet_node (page 243), and “About Cross-Subnet Failover” (page 154).)

Typically you would monitor the ip_subnet, specifying it here as well as in the ip_subnet parameter (see below), but you may want to monitor other subnets as well; you can monitor any subnet that is configured into the cluster (via the STATIONARY_IP or HEARTBEAT_IP parameter in the cluster configuration file).

If any monitored_subnet fails, Serviceguard will switch the package to any other node specified by node_name which can communicate on the monitored_subnets defined for this package. See the comments in the configuration file for more information and examples.

monitored_subnet_access

In cross-subnet configurations, specifies whether each monitored_subnet is accessible on all nodes in the package’s node list (see node_name (page 235)), or only some. Valid values are PARTIAL, meaning that at least one of the nodes has access to the subnet, but not all; and FULL, meaning that all nodes have access to the subnet. The default is FULL, and it is in effect if monitored_subnet_access is not specified.

See also ip_subnet_node (page 243) and “About Cross-Subnet Failover” (page 154).

New for modular packages. For legacy packages, see “Configuring Cross-Subnet Failover” (page 309).

cluster_interconnect_subnet

Can be configured only for a multi-node package in a Serviceguard Extension for Real Application Cluster (SGeRAC) installation.

Choosing Package Modules 241