Configuring server-based fencing on the new node
Prev Adding a node to a cluster Next

Configuring server-based fencing on the new node

This section describes the procedures to configure server-based fencing on a new node. Depending on whether server-based fencing is configured in secure or non-secure mode on the existing cluster, perform the tasks in one of the following procedures:

To configure server-based fencing in non-secure mode on the new node

  1. Log in to each CP server as the root user.
  2. Update each CP server configuration with the new node information:
    # cpsadm -s mycps1.symantecexample.com \
-a add_node -c clus1 -h saturn -n2

Node 2 (saturn) successfully added
  3. Verify that the new node is added to the CP server configuration:
    # cpsadm -s mycps1.symantecexample.com \
-a list_nodes

    The new node must be listed in the command output.

  4. Add the VCS user cpsclient@saturn to each CP server:
    # cpsadm -s mycps1.symantecexample.com \
-a add_user -e cpsclient@saturn \
-f cps_operator -g vx

User cpsclient@saturn successfully added

To configure server-based fencing with security on the new node

  1. Log in to each CP server as the root user.
  2. Update each CP server configuration with the new node information:
    # cpsadm -s mycps1.symantecexample.com \
-a add_node -c clus1 -h saturn -n2

Node 2 (saturn) successfully added
  3. Verify that the new node is added to the CP server configuration:
    # cpsadm -s mycps1.symantecexample.com -a list_nodes

    The new node must be listed in the output.

Prev Up Next
Configuring the ClusterService group for the new node Home Adding the new node to the vxfen service group