HP-UX Containers (SRP) A.03.01.003 Release Notes (5900-2312, May 2012)
10
1.8 Limitations for HP-UX Containers A.03.01.003
When the HP-UX Containers A.03.01.003 bundle is installed on the system, the following
features will not be available:
1. Installation from a remote network registered SD depot is not supported for software
installation. See the HP-UX Containers (SRP ) A.03.01 Administrator’s Guide for alternative
options.
2. Only the non-interactive command line interface (CLI) for the SD commands is supported
when one or more system containers are configured.
3. Creating a golden image using Ignite-UX with system containers configured is not
supported.
4. DRD clone and modifications with system containers configured is not supported.
1.9 Known issues in HP-UX Containers A.03.01.003
This section lists known issues and appropriate workarounds:
Add custom configuration tab of SRP GUI is not listing the same variables for
system and workload containers. System container is listing fewer variables
than workload.
Workaround:
SRP command line interface needs to be used to “add custom configuration" to system
container instead of SRP GUI interface.
The srp_su command does not initialize the TZ environment variable correctly
when the ‘-‘ option is omitted. Executing the srp_su(1M) command without the '-'
option does not update the TZ environment variable for the command or session in the
container based on the container /etc/TIMEZONE variable. The command or session uses
the TZ value set in the global view.
Workaround:
Use the '-' option or set the TZ variable manually when the srp_su command is used
without the '-' option.
The srp command does not support secondary IP address configuration for
the IPFilter and IPSec services. The srp command supports configuration of multiple IP
addresses for a container. However, the IPFilter and IPSec services for the container will be
configured only for primary IP address and not for secondary IP addresses.
Workaround:
1) Add and apply the IPFilter rules for secondary IP address directly to the
/etc/opt/ipf/ipf.conf file.