Search <book_title>...

Storage Foundation for Oracle® RAC 7.4.1 Administrator's Guide - Linux

Last Published: 2019-10-17

Product(s): InfoScale & Storage Foundation (7.4.1)

Platform: Linux

Section I. SF Oracle RAC concepts and administration
1. Overview of Storage Foundation for Oracle RAC
2. Administering SF Oracle RAC and its components
Section II. Performance and troubleshooting
Section III. Reference
1. Appendix A. List of SF Oracle RAC health checks
2. Appendix B. Error messages

Refreshing registration keys on the coordination points for server-based fencing

Replacing keys on a coordination point (CP server) when the SF Oracle RAC cluster is online involves refreshing that coordination point's registrations. You can perform a planned refresh of registrations on a CP server without incurring application downtime on the SF Oracle RAC cluster. You must refresh registrations on a CP server if the CP server agent issues an alert on the loss of such registrations on the CP server database.

The following procedure describes how to refresh the coordination point registrations.

To refresh the registration keys on the coordination points for server-based fencing

Ensure that the SF Oracle RAC cluster nodes and users have been added to the new CP server(s). Run the following commands:
```
# cpsadm -s cp_server -a list_nodes
```
```
# cpsadm -s cp_server -a list_users
```
If the SF Oracle RAC cluster nodes are not present here, prepare the new CP server(s) for use by the SF Oracle RAC cluster.
See the Storage Foundation for Oracle RAC Configuration and Upgrade Guide for instructions.
Ensure that fencing is running on the cluster in customized mode using the coordination points mentioned in the /etc/vxfenmode file.
If the /etc/vxfenmode.test file exists, ensure that the information in it and the /etc/vxfenmode file are the same. Otherwise, vxfenswap utility uses information listed in /etc/vxfenmode.test file.
For example, enter the following command:
```
# vxfenadm -d
```
```
================================
Fencing Protocol Version: 201
Fencing Mode: CUSTOMIZED
Cluster Members:
* 0 (sys1)
1 (sys2)
RFSM State Information:
node 0 in state 8 (running)
node 1 in state 8 (running)
```
List the coordination points currently used by I/O fencing :
```
# vxfenconfig -l
```
Copy the /etc/vxfenmode file to the /etc/vxfenmode.test file.
This ensures that the configuration details of both the files are the same.

Run the vxfenswap utility from one of the nodes of the cluster.

The vxfenswap utility requires secure ssh connection to all the cluster nodes. Use -n to use rsh instead of default ssh.

For example:

# vxfenswap [-n]

The command returns:

VERITAS vxfenswap version <version> <platform>
The logfile generated for vxfenswap is
/var/VRTSvcs/log/vxfen/vxfenswap.log.
19156
Please Wait...
VXFEN vxfenconfig NOTICE Driver will use customized fencing
- mechanism cps
Validation of coordination points change has succeeded on
all nodes.
You may commit the changes now.
WARNING: This may cause the whole cluster to panic
if a node leaves membership before the change is complete.

You are then prompted to commit the change. Enter y for yes.
The command returns a confirmation of successful coordination point replacement.
Confirm the successful execution of the vxfenswap utility. If CP agent is configured, it should report ONLINE as it succeeds to find the registrations on coordination points. The registrations on the CP server and coordinator disks can be viewed using the cpsadm and vxfenadm utilities respectively.
Note that a running online coordination point refreshment operation can be canceled at any time using the command:
```
# vxfenswap -a cancel
```