Refreshing keys or registrations on the existing coordination points for server-based fencing using the installer


Refreshing keys or registrations on the existing coordination points for server-based fencing using the installer
Prev	Setting up server-based I/O fencing using installer	Next

You must refresh registrations on the coordination points in the following scenarios:

When the CoordPoint agent notifies VCS about the loss of registration on any of the existing coordination points.
A planned refresh of registrations on coordination points when the cluster is online without having an application downtime on the cluster.

Registration loss might occur because of an accidental array restart, corruption of keys, or some other reason. If the coordination points lose registrations of the cluster nodes, the cluster might panic when a network partition occurs.

Warning:

Refreshing keys might cause the cluster to panic if a node leaves membership before the coordination points refresh is complete.

To refresh registrations on existing coordination points for server-based I/O fencing using the installer

Start the installer with the -fencing option.
```
# /opt/VRTS/install/installer  -fencing
```
The installer starts with a copyright message and verifies the cluster information.

Note the location of log files that you can access if there is a problem with the configuration process.
Confirm that you want to proceed with the I/O fencing configuration at the prompt.
The program checks that the local node running the script can communicate with the remote nodes and checks whether VCS 7.3 is configured properly.
Review the I/O fencing configuration options that the program presents. Type the number corresponding to the option that suggests to refresh registrations or keys on the existing coordination points.
```
Select the fencing mechanism to be configured in this
Application Cluster [1-7,q] 6
```
Ensure that the /etc/vxfentab file contains the same coordination point servers that are currently used by the fencing module.
Also, ensure that the disk group mentioned in the /etc/vxfendg file contains the same disks that are currently used by the fencing module as coordination disks.

Verify the coordination points.

For example,
Total number of coordination points being used: 3
Coordination Point Server ([VIP or FQHN]:Port):
      1. 10.198.94.146 ([10.198.94.146]:443)
      2. 10.198.94.144 ([10.198.94.144]:443)
SCSI-3 disks:
      1. emc_clariion0_61
Disk Group name for the disks in customized fencing: vxfencoorddg
Disk policy used for customized fencing: dmp

Is this information correct? [y,n,q] (y)

Updating client cluster information on Coordination Point Server
 IPaddress

Successfully completed the vxfenswap operation

The keys on the coordination disks are refreshed.

Do you want to send the information about this installation to us to help improve installation in the future? [y,n,q,?] (y).
Do you want to view the summary file? [y,n,q] (n).