TCP/IPv6 Configuration and Management Manual (G06.29+, H06.03+, J06.03+)

Manage the NonStop TCP/IPv6 Subsystem

HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012

6-14

Managing the System Configuration Database

The system configuration database (CONFIG) is part of the NonStop Kernel subsystem

on NonStop S-series servers and Integrity NonStop NS-series servers. The

conventional TCP/IP subsystem (NonStop TCP/IP) does not participate in the system

configuration database, but NonStop TCP/IPv6 does. When you configure NonStop

TCP/IPv6 for the first time, the MON, ROUTE, ENTRY, and SUBNET objects are

added to the system configuration database and any alterations to those objects also

update the configuration of those objects in the system configuration database. The

system configuration database stores your subsystem configuration and can be

accessed at any time to restore the subsystem to its last configuration. However, the

TCP6SAM process is not stored in the system configuration database. So, you must

always start TCP6SAM processes using the TACL RUN command.

The TCP6MAN, when started, either by the persistence manager or by a TACL RUN

command, starts any subordinate objects that are stored in the system configuration

database.

Configuration Database Management

Save your configuration database before configuring NonStop TCP/IPv6 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 NonStop TCP/IPv6 are incompatible with the

NonStop TCP/IPv6 records residing in the system configuration database. If a new

RVU of NonStop TCP/IPv6 is incompatible with the data stored in the configuration

database, you can restore the saved configuration database and reconfigure NonStop

TCP/IPv6. This SCF command saves the current configuration database file in a new

file located at $SYSTEM.ZYSCONF.CONF0104:

->SAVE CONFIGURATI0N 01.04

The full explanation of the SCF SAVE command is documented in SCF Reference

Manual for G-Series RVUs and the SCF Reference Manual for H-Series RVUs.

Note. No dynamically created entries or routes are recorded in the system configuration

database.

Caution. The configuration database stores all SCF commands that you issue to modify your

NonStop TCP/IPv6 environment. If you use startup scripts to start your NonStop TCP/IPv6

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 the TCP/IPv6 Migration Guide.