Changing the Permanent Cluster Configuration

If your network or LAN card configuration changes on the cluster, you may need to modify the basic cluster configuration. This can be done through SAM or with HP-UX commands. The basic process is as follows:

Halt packages.
Ensure that the OPS database is not active on either node.
Deactivate and unshare any shared volume groups.
Halt the cluster.
Change the LAN configuration as needed.
Using either SAM high availability options or HP-UX commands, create a new configuration file and propagate the new configuration to all the nodes in the cluster.
Start up the cluster to see if it forms successfully.
Reboot all nodes. The cluster should reform, and the OPS instances and packages should come up again.

When reconfiguring the cluster, use the following guidelines.

Before executing cmapplyconf, mark the cluster lock volume group non-shareable if the volume group is being used as a shared database volume group:
# vgchange -S n -c n VGName
Then activate it in normal mode:
# vgchange -a y VGName
You may now execute the cmapplyconf command.
Before running cmruncl or cmrunnode on the new cluster configuration, deactivate the cluster lock volume group:
# vgchange -a n VGName
After bringing the cluster up with cmrunnode or cmruncl, mark each database volume group (including the cluster lock volume group, if it is being used for OPS data) with the new cluster ID and make it shareable:
# vgchange -S y -c y VGName
Now the shared volume groups can be activated in shared mode:
# vgchange -a s -p VGName

For more details about creating the configuration file, see "Configuring the Cluster" in the chapter "Building an OPS Cluster Configuration."

Changing Lock Volume Group Configuration

If you decide to change the lock volume group in your configuration, you must issue the following commands on the lock volume group before reconfiguration will succeed:

# vgchange -S n -c n vg_ops 
# vgchange -a y vg_ops

This process is needed when you modify the lock volume group configuration, although you can use the commands to convert any shared, cluster-bound MC/LockManager volume group into a standard (non-shareable) LVM volume group.

Changing the Permanent Cluster Configuration

Technical documentation

» Table of Contents

» Index

Changing Lock Volume Group Configuration