6.3.5 Procedures for changing settings
If you change the settings at the primary server after you have started operation in the cluster system, you must apply the changes to the secondary server so that the system is synchronized. If the system is not synchronized, secondary server operation may not match primary server operation in the event of a failover.
Change settings at both the primary and the secondary servers in the following cases.
- Organization of this subsection
(1) Changing settings in files
If you have edited the files listed below and used the jbssetcnf command to apply the settings, you must copy the common definition information from the primary server to the secondary server:
-
Automated action environment definition file (action.conf.update)
-
Communication environment definition file (console.conf.update)
-
Settings file for the maximum number of status change events (evhist_warn_event_xxx.conf)
-
Settings file for completed-action linkage function (action_complete_xxx.conf)
-
Definition file for automatic delete mode of status change event
-
Definition file for monitoring object initialization mode
-
Automatic backup and recovery settings file for monitoring object database (auto_dbbackup_xxx.conf)
-
Correlation event generation environment definition file
-
Definition file for on memory mode of status change condition
Copy the common definition information using the setup procedure described in 6.3.2(4) Copying the common definition information.
The common definition information contains settings for JP1/Base, JP1/IM - Manager, JP1/AJS, and JP1/Power Monitor (06-02 or later). If these products have been set up on the logical host, the settings are also copied.
(2) Using commands to change settings
If you have used the jcochafmode, jcochcefmode, or jcocmddef command to change settings, you must also specify the same settings at the primary and secondary servers.
-
When the jcochafmode command was executed
If you have changed the location of the event acquisition filter by specifying the -h option, you must copy the common definition information from the primary server to the secondary server.
Copy the common definition information using the setup procedure described in 6.3.2(4) Copying the common definition information.
-
When the jcochcefmode command is executed
If you have changed the operation mode for the common exclusion conditions by specifying the -h option, you must copy the common definition information from the primary server to the secondary server.
Copy the common definition information using the setup procedure described in 6.3.2(4) Copying the common definition information.
-
When the jcocmddef command was executed
If you have changed the settings at the primary server by specifying the -host option, you must also specify the same settings at the secondary server. You can execute the jcocmddef command even when the shared disk is not mounted.