HP Serviceguard Storage Management Suite A.03.02 Release Notes (March 2012)

5. Remove the node details from the RAC-MNP configuration file and re-apply it using the
cmapplyconf -P <RAC-MNP pkg config file> command (This step is not necessary,
unless a RAC-MNP is configured).
6. Remove the node details from the OC-MNP configuration file and re-apply it using the
cmapplyconf -P <OC-MNP pkg config file> command (This step is not necessary,
unless an OC-MNP is configured).
7. Disable AUTOSTART_CMCLD in /etc/rc.config.d/cmcluster on the node that is being
deleted, by setting AUTOSTART_CMCLD to zero: (AUTO_START_CMCLD=0)
8. Run cmhaltnode -f <node name> to halt the node that is being removed from the cluster.
The -f option will halt all the packages that are running on the node that is being deleted.
9. Delete a node from a Mount Point (MP) package using the cfsmntadm modify delete
command.
If you are using Improved CFS Mount Point and Disk Group Integration, follow these steps to
delete the node from the Modular Disk Group and Mount Point Packages:
a. Edit the package configuration file and remove the node that is being deleted:
• node_name : node1
• cfs_activation_options : “node1=sw”
• cfs_mount_options : “node1= cluster”
b. Re-apply the package configuration using the cmapplyconf command: cmapplyconf
-P package.ascii
NOTE: Step 9a, and 9b should repeated for each of the CFS Mount point and Disk Group
packages. Then proceed to step 12.
10. Delete a node from a Disk Group (DG) package configuration using the cfsdgadm modify
<DG name> delete <node name> command.
11. Repeat step #9 for all MP packages and repeat step #10 for all DG packages.
12. Remove a node from the cluster by removing the node name from the cluster configuration
file - then re-apply the configuration using the cmapplyconf –C <config file name>
command.
13. Run the cmviewcl command to verify that node has been removed from the cluster.
SCSI-3 Persistent Reservations Support Not Required on Storage Devices
The Veritas Cluster Server (VCS) relies on support of SCSI-3 Persistent Reservations on storage
devices - this is part of the Veritas split brain prevention mechanism. HP Serviceguard uses a
different and more robust method to prevent split brain - storage devices do not need to support
SCSI-3 Persistent Reservations in an HP Serviceguard environment.
Oracle Disk Manager (ODM) with VxFS and LVM
Oracle Disk Manager (ODM) for VxFS file systems on LVM volumes is not supported. Oracle Files
that need ODM capability must reside on a VxFS file system created on a VxVM or CVM volume.
Oracle Disk Manager (ODM) Limitation for CFS Oracle Bundles
Single instance Oracle databases are not permitted outside of Serviceguard packages in
environments using HP Serviceguard Storage Management Suite T2773DB, T2774DB, T2777DB,
T8684DB, T8686DB, T8687DB, T8694DB, T8696DB and T8697DB bundles. If there are any
Oracle instances not controlled by Serviceguard packages, a halt of the system multi-node package
SG-CFS-pkg could bring down the node or cluster. Place all Oracle single instances in
Serviceguard packages when deploying these bundles. In addition, single instance Oracle packages
using VxFS and VxVM, or CVM/CFS, must have a direct dependency on the system multi-node
package SG-CFS-pkg.
44 HP Serviceguard Storage Management Suite Version A.03.02 for HP-UX 11i v3 Release Notes