Deployment and migration scenarios for CP server
Prev About administering the coordination point server Next

Deployment and migration scenarios for CP server

Table: CP server deployment and migration scenarios describes the supported deployment and migration scenarios, and the procedures you must perform on the VCS cluster and the CP server.

Table: CP server deployment and migration scenarios

Scenario

CP server

VCS cluster

Action required

Setup of CP server for a VCS cluster for the first time

New CP server

New VCS cluster using CP server as coordination point

On the designated CP server, perform the following tasks:

  1. Prepare to configure the new CP server.

  2. Configure the new CP server.

  3. Prepare the new CP server for use by the VCS cluster.

On the VCS cluster nodes, configure server-based I/O fencing.

See the Cluster Server Installation Guide for the procedures.

Add a new VCS cluster to an existing and operational CP server

Existing and operational CP server

New VCS cluster

On the VCS cluster nodes, configure server-based I/O fencing.

See the Cluster Server Installation Guide for the procedures.

Replace the coordination point from an existing CP server to a new CP server

New CP server

Existing VCS cluster using CP server as coordination point

On the designated CP server, perform the following tasks:

  1. Prepare to configure the new CP server.

  2. Configure the new CP server.

  3. Prepare the new CP server for use by the VCS cluster.

See the Cluster Server Installation Guide for the procedures.

On a node in the VCS cluster, run the vxfenswap command to move to replace the CP server:

See Replacing coordination points for server-based fencing in an online cluster.

Replace the coordination point from an existing CP server to an operational CP server coordination point

Operational CP server

Existing VCS cluster using CP server as coordination point

On the designated CP server, prepare to configure the new CP server manually.

See the Cluster Server Installation Guide for the procedures.

On a node in the VCS cluster, run the vxfenswap command to move to replace the CP server:

See Replacing coordination points for server-based fencing in an online cluster.

Enabling fencing in a VCS cluster with a new CP server coordination point

New CP server

Existing VCS cluster with fencing configured in disabled mode

Note:

Migrating from fencing in disabled mode to customized mode incurs application downtime on the VCS cluster.

On the designated CP server, perform the following tasks:

  1. Prepare to configure the new CP server.

  2. Configure the new CP server

  3. Prepare the new CP server for use by the VCS cluster

See the Cluster Server Installation Guide for the procedures.

On the VCS cluster nodes, perform the following:

  1. Stop all applications, VCS, and fencing on the VCS cluster.

  2. To stop VCS, use the following command (to be run on all the VCS cluster nodes):

    # hastop -local

  3. Stop fencing using the following command:

    # /etc/init.d/vxfen.rc stop

  4. Reconfigure I/O fencing on the VCS cluster.

    See the Cluster Server Installation Guide for the procedures.

Enabling fencing in a VCS cluster with an operational CP server coordination point

Operational CP server

Existing VCS cluster with fencing configured in disabled mode

Note:

Migrating from fencing in disabled mode to customized mode incurs application downtime.

On the designated CP server, prepare to configure the new CP server.

See the Cluster Server Installation Guide for this procedure.

On the VCS cluster nodes, perform the following tasks:

  1. Stop all applications, VCS, and fencing on the VCS cluster.

  2. To stop VCS, use the following command (to be run on all the VCS cluster nodes):

    # hastop -local

  3. Stop fencing using the following command:

    # /etc/init.d/vxfen.rc stop

  4. Reconfigure fencing on the VCS cluster.

    See the Cluster Server Installation Guide for the procedures.

Enabling fencing in a VCS cluster with a new CP server coordination point

New CP server

Existing VCS cluster with fencing configured in scsi3 mode

On the designated CP server, perform the following tasks:

  1. Prepare to configure the new CP server.

  2. Configure the new CP server

  3. Prepare the new CP server for use by the VCS cluster

See the Cluster Server Installation Guide for the procedures.

Based on whether the cluster is online or offline, perform the following procedures:

For a cluster that is online, perform the following task on the VCS cluster:

For a cluster that is offline, perform the following tasks on the VCS cluster:

  1. Stop all applications, VCS, and fencing on the VCS cluster.

  2. To stop VCS, use the following command (to be run on all the VCS cluster nodes):

    # hastop -local

  3. Stop fencing using the following command:

    # /etc/init.d/vxfen.rc stop

  4. Reconfigure I/O fencing on the VCS cluster.

    See the Cluster Server Installation Guide for the procedures.

Enabling fencing in a VCS cluster with an operational CP server coordination point

Operational CP server

Existing VCS cluster with fencing configured in disabled mode

On the designated CP server, prepare to configure the new CP server.

See the Cluster Server Installation Guide for this procedure.

Based on whether the cluster is online or offline, perform the following procedures:

For a cluster that is online, perform the following task on the VCS cluster:

For a cluster that is offline, perform the following tasks on the VCS cluster:

  1. Stop all applications, VCS, and fencing on the VCS cluster.

  2. To stop VCS, use the following command (to be run on all the VCS cluster nodes):

    # hastop -local

  3. Stop fencing using the following command:

    # /etc/init.d/vxfen.rc stop

  4. Reconfigure fencing on the VCS cluster.

    See the Cluster Server Installation Guide for the procedures.

Refreshing registrations of VCS cluster nodes on coordination points (CP servers/ coordinator disks) without incurring application downtime

Operational CP server

Existing VCS cluster using the CP server as coordination point

On the VCS cluster run the vxfenswap command to refresh the keys on the CP server:

See Refreshing registration keys on the coordination points for server-based fencing.
Prev Up Next
Refreshing registration keys on the coordination points for server-based fencing Home About migrating between disk-based and server-based fencing configurations