Serviceguard Extension for RAC Version A.11.18 Release Notes, 2nd Edition, December 2007
Table Of Contents
- Serviceguard Extension for RAC Version A.11.18 Release Notes Second Edition
- Table1 Printing History
- Announcements
- What’s in this Version
- Support for Cluster Interconnect Subnet Monitoring
- Support for Veritas CFS and CVM
- Support for Oracle 9i RAC on CFS and CVM
- Support for Oracle 10gR2 RAC on CFS and CVM
- Support for the SGeRAC Toolkit
- Support for 8192 Oracle Server Processes for Oracle 9i RAC
- Serviceguard Extension for RAC does not support Mixed Clusters
- About Device Special Files (DSFs)
- What Manuals are Available for This Version
- Further Reading
- Compatibility Information and Installation Requirements
- Types of Releases and Patches
- Serviceguard Extension for RAC Compatibility with HP-UX and Oracle Releases
- Port Requirements
- Installing Serviceguard Extension for RAC
- Adding Serviceguard Extension for RAC to an Existing Cluster
- Removing SGeRAC
- Removing Serviceguard Extension for RAC Without Removing Serviceguard
- Troubleshooting Tips
- Patches and Fixes in this Version
- Known Problems and Workarounds
- Software Availability in Native Languages
Serviceguard Extension for RAC Version A.11.18 Release NotesWhat’s in this VersionChapter 1 11Support for Cluster Interconnect Subnet MonitoringIn SGeRAC, the Cluster Interconnect Subnet Monitoring feature is usedto monitor cluster communication subnets. This feature requires the useof a package configuration parameter known as theCLUSTER_INTERCONNECT_SUBNET. It can be set up to monitor certainsubnets used by applications that are configured as Serviceguardmulti-node packages with the following restrictions:• Cluster Interconnect subnet monitoring can support up to 4 nodes.•Only one CLUSTER_INTERCONNECT_SUBNET can be specified permulti-node package.The CLUSTER_INTERCONNECT_SUBNET parameter works similar to theexisting SUBNET package configuration parameter. The most notabledifference is in the failure handling of the subnets monitored using theseindividual parameters. While the failure of subnets monitored usingSUBNET package configuration parameter is handled by halting theinstance of the package on the node where the subnet has failed, thefailure of subnets monitored using CLUSTER_INTERCONNECT_SUBNETpackage configuration parameter is handled by ensuring at least oneinstance of the package remains running in the cluster.NOTE A package with the CLUSTER_INTERCONNECT_SUBNET parameter isavailable for both Modular and Legacy packages. A package with thisparameter can be configured only when all nodes of the cluster arerunning SGeRAC version A.11.18 or higher. For more information, seethe Managing Serviceguard Fifteenth Edition user’s guide athttp://docs.hp.com -> High Availability -> Serviceguard.