Setting Up Failover › Establishing the Configuration › Step 3: Copying and Importing the Configuration File to the Primary and Secondary Hosts

Step 3: Copying and Importing the Configuration File to the Primary and Secondary Hosts

The import routine adds new records to an existing database and replaces objects that have the same name and type. This action may not be what you intend. We recommend that you backup the default configuration database file (rename or copy to a different name) before importing the edited text file.

Do not copy the configuration database as this leaves the old definitions in place. Any import of records which already exist in the configuration database will fail.

To import a file

1. Run the configuration editor.
2. Pull down the File menu.
3. Choose the Import... menu item.
4. Enter the name of the file to import in the Selection field.
5. Click OK to accept the file. The file is then imported.
6. To make the changes active, you must reconfigure Console Manager (see the chapter “Managing Console Manager.”)

After you modify the default configuration database, review the changed objects. When you are satisfied with the results, reconfigure Console Manager to activate the changes you have made. For more information on activating you changes, see the section Activating Your Configuration Database Changes.

See the section Using the Command Line Interface to the Configuration Editor for instructions on how to do this process using the command line interface.

Step 4: Configure Console Manager Failover for IPv6

If you would like failover to communicate using IPv6 addressing, you must use this configuration on OpenVMS:

Dual-stack environment

In a dual-stack environment, the default address family for Console Manager failover is IPv4. To enable IPv6 addressing, define the system logical CONSOLE$ENABLE_IPV6 with a value of 1, as in the following example:

$ define/system CONSOLE$ENABLE_IPV6 1

When this logical name is defined, Console Manager will attempt to resolve host names to either an IPv4 or an IPv6 address (whichever comes first) for the primary and secondary host.

Testing IPv6 addressing (For testing only)

To verify that your IPv6 CM connection is working properly, for your convenience you can define the following logical name on the primary and secondary nodes:

$ define/system CONSOLE$USE_IPV6_ONLY 1

When this logical name is defined, Console Manager attempts to resolve host names to an IPv6 address. If an IPv6 address is not available and an IPv4 address is available, the IPv4-mapped IPv6 address is used.

Note: For information on how to configure IPv6 using SSH, see the section "Configuring SSH".