HP 9000 Containers A.03.01 on HP Integrity Server Administrator Guide HP-UX 11i v3 (5900-3112, June 2013)

3. Log in to the target server and run the kernel parameter configuration script:

$ /opt/HP9000-Containers/bin/hp9000_conf_tunables \

The hp9000_conf_tunables script provides an option to choose between batch mode

and interactive mode. In the batch mode, a set of selected tunable parameters is updated

automatically. In the interactive mode, users can select the list of tunable parameters to be

updated based on the values on the PA-RISC server.

4. Review the data in the log file /var/opt/ HP9000-Containers/logs/

transition_tunables_<hostname>.log and make further changes as required. This

is required because the hp9000_conf_tunables script does not guarantee that all the

required changes are applied. The limitations of the script are as follows:

• It ignores parameters that do not have an impact on applications and are more related

to system administration.

• It does not modify tunable parameters, where there can be conflicts when moving from

multiple HP 9000 servers into containers.

• It does not handle inter-tunable dependencies. Hence, some of the attempted changes

might fail.

• It does not add up the values of parameters when creating additional containers.

5. Containers hosting environments earlier than HP-UX 11i v3 do not support large PID values.

This means that certain commands and applications within such containers fail when they

encounter value larger than 30000.

$ kctune process_id_max=30000

$ kctune nproc=30000

6. HP 9000 Containers does not support tunable base page size. Ensure that the kernel tunable

parameter base_pagesize is set to its default value of 4 KB.

$ kctune base_pagesize=4

7. If you migrate Java or other heavily multi-threaded applications, increase the value of the

parameter pa_maxssiz_32bit to 128 MB.

$ kctune pa_maxssiz_32bit=128MB

8. Currently, if legacy HP 9000 containers are hosted on a system, the name of the global host

cannot contain more than 8 characters. The workaround is to disable overflow error checking

using the command:

$ kctune uname_eoverflow=0

9. Reboot the server.

3.4 Choosing name for HP 9000 container

The container name is also used as its node name and host name. If the HP 9000 environment

being migrated does not support long node names (as is the case with HP-UX 11i v1), limit the

container name to less than or equal to 8 characters. Later, you can edit the container name to a

longer name when needed.

In the following chapters, the container name is referred as <srp_name>.

3.5 Creating file systems for the container

NOTE: Host the container root directories in separate file systems for better isolation and

management. By placing the home for each container in its own LUN, storage performance can

be optimized.

3.4 Choosing name for HP 9000 container 19