instl_adm.4 (2012 03)

i
instl_adm(4) instl_adm(4)
This example assumes _inc has been initialized to some value in the configuration file.
The
= operator overrides any prior global mod_kernel
assignments. The += operator adds to
any prior settings. Notice that
mod_kernel statements may also be associated with a
sw_sel
definition. The = operator does not have any effect on
mod_kernel assignments made in a
sw_sel.
Beginning with the B.11.23 release, the format for cplx_string arguments is enhanced. There are
additional formats:
mod_kernel += "tunable name value"
mod_kernel += "module name [state]"
The first performs the same as it did previously with the addition of the keyword
tunable. The
second describes how kernel modules are added to the client. The optional state argument has one of
four values:
static, auto, loaded and
best. No syntax checking is performed for this value.
See kcmodule (1M) for more information.
Actions involving
mod_kernel are performed before those for both
set_kernel and
rm_kernel.
Note: Spaces should only be used within strings associated with *kernel keywords. Tabs are not
acceptable characters.
set_kernel = cplx-string
set_kernel += cplx-string
Setting this keyword is the same for drivers as the mod_kernel keyword in that it adds the driver
to the kernel. For tunables it differs from mod_kernel in that it sets the tunable to an arbitrary
value as defined by cplx-string . No comparisons or checks are performed with prior or default
values. Actions involving set_kernel are performed after those for mod_kernel, but before
those for rm_kernel.
Note: Spaces should only be used within strings associated with *kernel keywords. Tabs are not
acceptable characters.
rm_kernel = cplx-string
rm_kernel += cplx-string
Setting this keyword removes the driver or tunable from the /stand/system
file. For drivers,
this implies that the driver is removed from the kernel. For tunables, this implies the tunable
reverts back to its default value. Actions involving
rm_kernel are performed after those for both
mod_kernel and set_kernel.
Note: Spaces should only be used within strings associated with *kernel keywords. Tabs are not
acceptable characters.
vxvm_hostid = cplx_string
Setting this identifier writes it to all VxVM disks on a client when they are first added to a disk
group. When a client starts, it looks at all the disks and compares its VxVM identifier to the
identifier stored in /etc/vx/volboot. For each disk that matches that identifier, the client
enables access.
vxvm_version = cplx_string
This keyword causes all VxVM disk groups on a client to be created with the on-disk data structures
for the VxVM version specified. The allowable values as well as the defaults in cases where this key-
word is not specified are defined as follows:
HP-UX release Default Allowed
B.11.11 3.5 3.5
B.11.23 3.5 3.5, 4.1, 5.0
B.11.31 4.1 4.1, 5.0
This keyword is applied globally and cannot be set on a per-disk group basis. Valid values for
vxvm_version currently are: "3.5", "4.1", and "5.0".
If
vxvm_version is encountered multiple times in a configuration during a cold install, the lowest
value of the keyword will be used as the global value.
The behaviour of this keyword is slightly different during a recovery. The
save_config command
creates the configuration file that describes any VxVM disk groups that will be recreated during a
recovery. This command sets vxvm_version to the highest VxVM version used to create a disk group
presented to the system it is running on.
24 Hewlett-Packard Company − 24 − HP-UX 11i Version 3: March 2012