HP-UX 11i Version 2 Release Notes (October 2003)

General System Administration
MC/ServiceGuard
Chapter 4
90
MC/ServiceGuard
MC/ServiceGuard (Multi-Computer/ServiceGuard) is a specialized facility for protecting
mission critical applications from a wide variety of hardware and software failures.
Summary of Change
MC/ServiceGuard version A.11.15.00 includes the following features:
Support for new Itanium-based hardware
ServiceGuard A.11.15.00 on HP-UX 11i v2 Itanium-based platform
Supports all ServiceGuard 11.15.00 (PA-RISC) features except maximum nodes,
which is 8
Rolling upgrade from SG11.14.01 (Itanium-based) to SG11.15.00 (Itanium-based)
Support for VxVM 3.5
Support for Quorum Server 2.00
Fully compatible with default settings for Bastille Sec10Host configuration. Any
Bastille configuration that invokes IPFilter must follow specific rules for using
IPFilter and ServiceGuard.
Using IPFilter and ServiceGuard require specific IPFilter rules to ensure proper
operation of ServiceGuard clusters. The rules for using IPFilter and ServiceGuard
are documented in the IPFilter Release Note, available at
http://www.docs.hp.com.
Support for ServiceGuard Manager 3.0
Support for SGeRAC (ServiceGuard Extension for RAC, formerly ServiceGuard
OPS)
MC/ServiceGuard A.11.15 supports up to 200 relocatable package IP addresses per
cluster. This can be a combination of IPv4 and IPv6 addresses
ServiceGuard A.11.15 supports IPv6, with the following restrictions:
The heartbeat IP address must be IPv4. Therefore, IPv6-only operation nodes or
IPv6-only nodes are not supported in a ServiceGuard environment.
The hostnames in a ServiceGuard configuration must be IPv4. ServiceGuard
does not recognize IPv6 hostnames.
Auto-configured IPv6 addresses are not supported in ServiceGuard as
STATIONARY_IP addresses. All IPv6 addresses that are part of a ServiceGuard
cluster configuration must not be auto-configured through router
advertisements, for example. They must be manually configured in
/etc/rc.config.d/netconf-ipv6.
Link-local IP addresses are not supported, either as package IPs or as
STATIONARY_IPs. Depending on the requirements, the package IP could be of
type site-local or global.