Managing HP Serviceguard for Linux, Tenth Edition, September 2012

Reporting Link-Level and IP-Level Failures
Any given failure may occur at the link level or the IP level; a failure is reported slightly
differently in the output of cmviewcl (1m) depending on whether link-level or IP
monitoring detects the failure.
If a failure is detected at the link level, output from cmviewcl -v will look like something
like this:
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY down (Link and IP) 0/3/1/0 eth2
PRIMARY up 0/5/1/0 eth3
cmviewcl -v -f line will report the same failure like this:
node:gary|interface:lan2|status=down
node:gary|interface:lan2|disabled=false
node:gary|interface:lan2|failure_type=link+ip
If a failure is detected by IP monitoring, output from cmviewcl -v will look like something
like this:
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY down (IP only) 0/3/1/0 eth2
PRIMARY up 0/5/1/0 eth3
cmviewcl -v -f line will report the same failure like this:
node:gary|interface:lan2|status=down
node:gary|interface:lan2|disabled=false
node:gary|interface:lan2|failure_type=ip_only
Package Switching and Relocatable IP Addresses
A package switch involves moving the package to a new system. In the most common
configuration, in which all nodes are on the same subnet(s), the package IP (relocatable
IP; see “Stationary and Relocatable IP Addresses and Monitored Subnets” (page 68))
moves as well, and the new system must already have the subnet configured and working
properly, otherwise the packages will not be started.
NOTE: It is possible to configure a cluster that spans subnets joined by a router, with
some nodes using one subnet and some another. This is called a cross-subnet
configuration. In this context, you can configure packages to fail over from a node on
one subnet to a node on another, and you will need to configure a relocatable address
for each subnet the package is configured to start on; see “About Cross-Subnet Failover”
(page 151), and in particular the subsection“Implications for Application Deployment”
(page 152).
When a package switch occurs, TCP connections are lost. TCP applications must reconnect
to regain connectivity; this is not handled automatically. Note that if the package is
dependent on multiple subnets (specified as monitored_subnets in the package
configuration file), all those subnets must normally be available on the target node before
the package will be started. (In a cross-subnet configuration, all subnets configured on
How the Network Manager Works 79