Cluster I/O Protocols (CIP) Configuration and Management Manual (H06.16+, J06.05+)

Managing the Configuration Database on the NonStop Host System
Save your configuration database before configuring CIP for the first time and record the name
and date of the saved database. This saved configuration database can be used if higher RVUs
of CIP are incompatible with the CIP records residing in the system configuration database. If a
new RVU of CIP is incompatible with the data stored in the configuration database, you can restore
the saved configuration database and reconfigure CIP. This SCF command saves the current
configuration database file in a new file located at $SYSTEM.ZYSCONF.CONF0104:
> SAVE CONFIGURATI0N 01.04
The SCF SAVE command is documented in the SCF Reference Manual for J-Series and H-Series
RVUs.
CAUTION: The configuration database stores all SCF commands that you issue to modify your
CIP environment. If you use startup scripts to start your CIP subsystem, you should compare your
configuration database to those startup files to ensure that the startup files reflect these additional
modifications to the environment. For more detailed procedures and specific migration
considerations, see Chapter 6: IP CIP Migration, Compatibility and Operational Differences.
Managing Persistence on the NonStop Host System
You can add a generic process to the system configuration database and define that generic
process in such a way that the persistence manager restarts the generic process whenever the
generic process abends, is stopped through TACL, or the system is reloaded. To define the generic
process this way, set the STARTMODE to SYSTEM.
If you add the CIPMAN, CIPMON, or CIPSAM (IP CIP only) process as a generic process configured
in this way, these processes start automatically upon system reload and subsequently restores their
stored and subordinate objects. Alternatively, when you add the CIPMAN, CIPMON, or CIPSAM
process as a generic process to the system configuration database, you can choose to configure
it using STARTMODE MANUAL; this method requires that you start $ZZKRN.#ZZCIP manually by
using an SCF START command to the NonStop Kernel subsystem.
The persistence manager restarts persistent generic processes whenever they are stopped by the
TACL STOP command (if the generic process is configured with STARTMODE SYSTEM) in addition
to starting those generic processes when the system is reloaded. Hence, if CIPMAN, CIPMON, or
CIPSAM is a generic, persistent process (AUTORESTART > 0), any time you issue a TACL STOP
command to the CIP subsystem, CIPMAN, CIPMON, or CIPSAM gets restarted by the persistence
manager. To avoid this behavior and stop a persistent, generic, CIPMAN, CIPMON, or CIPSAM
process, issue the ABORT command to the NonStop Kernel subsystem as in this example:
> ABORT PROCESS $ZZKRN.#ZZCIP
> ABORT PROCESS $ZZKRN.#CIPMON
> ABORT PROCESS $ZZKRN.#CIPSAM
For more information about generic processes and the persistence manager, see the SCF Reference
Manual for the Kernel Subsystem.
Managing the CLIM Configuration Preservation
HP recommends that you store the CLIM configurations any time you change them. Two TACL
scripts are provided for this practice: one for backing up and one for restoring the CLIM
configuration.
NOTE: You must be logged on as a super group user to run these commands.
climbkup and climrstr Command Synopsis
{climbkup | climrstr} {clim-name | ip-address | hostname}
[file-name | volume | volume.subvolume | subvolume.filename | volume.subvolume.filename]
114 CIP Configuration and Management