HP-UX Containers (SRP) A.03.01 Administrator's Guide

• If you want to use the Serviceguard network failover capability, then Serviceguard

must control the management of the network interface.

IMPORTANT: Unlike HP-UX Containers, Serviceguard does not support the system

network configuration files /etc/rc.config.d/netconf and netconf-ipv6.

Therefore, a Serviceguard package during startup can unknowingly use container

assigned network interfaces which are not active when the package is started, but

are configured in /etc/rc.config.d/netconf or netconf-ipv6 for a

container’s use. When the container with the conflicting network interface is started,

the active Serviceguard package can fail or result in loss of network connectivity. As

a rule, a Serviceguard managed container and a non-Serviceguard managed

container on the system must not share the same physical network interface.

3. Create the container

When you create a container that will use Serviceguard, you must indicate in the Container

Manager or the command line interface to support the desired Serviceguard behavior as

follows:

Add IP address to netconf file? [yes]

Press Enter to instruct HP-UX Containers to control network interface management.

Enter no to defer control of network management to Serviceguard.

NOTE: If you use the srp command for configuration, you can use the variable

assign_ip=yes|no to specify the behavior.

This option informs HP-UX Containers whether or not the container controls the starting and

stopping of the assigned network interface. Either option may be used with Serviceguard,

but selecting “no” allows Serviceguard to control the interface, allowing support of network

interface failover.

Autostart SRP container at system boot? [yes]

Press Enter for the classic model.

Enter no for the container package model.

NOTE: If you use the srp command for configuration, you can use the variable

autostart=yes|no to specify the behavior.

For Serviceguard network failover capability, you need to create a secondary (failover)

container. To create a secondary container, you can use the export and import features to

clone the container on a secondary system. See 6.9 Copying containers by exporting and

importing for more details.

The sharing of container home directory (using Serviceguard volume) between cloned

containers in different physical systems is only supported for workload containers and is not

supported for system containers.

13.3 Adapting Serviceguard scripts for the classic model

The example in this section demonstrates the classic model approach to modify an existing

Serviceguard script to work with HP-UX Containers. If you want Serviceguard to manage or monitor

the applications executing within the managed container, use the srp_su command to let