Using Serviceguard Extension for RAC, 6th Edition, April 2008

NOTE: For CVM without CFS, if you are adding a disk group to the cluster
configuration, make sure you also modify any package or create the package control
script that imports and deports this disk group. If you are adding a CVM disk group,
be sure to add the STORAGE_GROUP entry for the disk group to the package ASCII file.
For CVM with CFS, if you are adding a disk group to the cluster configuration, make
sure you also create the corresponding multi-node package. If you are adding a CVM
disk group, be sure to add to the packages that depend on the CVM disk group the
necessary package dependency.
If you are removing a disk group from the cluster configuration, make sure that you
also modify or delete any package control script that imports and deports this disk
group. If you are removing a CVM disk group, be sure to remove the STORAGE_GROUP
entries for the disk group from the package ASCII file.
When removing a disk group that is activated and deactivated through a multi-node
package, make sure to modify or remove any configured package dependencies to the
multi-node package.
Removing Serviceguard Extension for RAC from a System
If you wish to remove a node from Serviceguard Extension for RAC operation, use the
swremove command to delete the software. Note the following:
• The cluster service should not be running on the node from which you will be
deleting Serviceguard Extension for RAC.
• The node from which you are deleting Serviceguard Extension for RAC should
not be in the cluster configuration.
• If you are removing Serviceguard Extension for RAC from more than one node,
swremove should be issued on one node at a time.
NOTE: After removing Serviceguard Extension for RAC, your cluster will still have
Serviceguard installed. For information about removing Serviceguard, refer to the
Managing Serviceguard user’s guide for your version of the product.
Monitoring Hardware
Good standard practice in handling a high availability system includes careful fault
monitoring so as to prevent failures if possible or at least to react to them swiftly when
they occur. The following should be monitored for errors or warnings of all kinds:
• Disks
• CPUs
• Memory
• LAN cards
• Power sources
156 Maintenance and Troubleshooting