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 17This means that you are not required to migrate to agile addressingwhen you upgrade to 11i v3, though you should seriously consider itsadvantages (see the white paper The Next Generation Mass StorageStack under Network and Systems Management -> Storage AreaManagement at docs.hp.com).Migration involves modifying system and application configuration filesand scripts to use persistent device files and in some cases newcommands and options; the process is described in the white papersMigrating from HP-UX 11i v2 to HP-UX 11i v3 and LVM Migration fromLegacy to Agile Naming Model HP-UX 11i v3 at http://docs.hp.com.If you cold-install HP-UX 11i v3, sets of both legacy and persistent devicefiles are automatically created. In this case, by default the installationprocess will configure system devices such as the boot, root, swap, anddump devices to use persistent device files. This means that systemconfiguration files such as /etc/fstab and /etc/lvmtab will containreferences to persistent device files, but Serviceguard’s functioning willnot be affected by this.NOTE It is possible, though not a best practice, to use legacy DSFs on somenodes after migrating to agile addressing on others; this allows you tomigrate different nodes at different times, if necessary.CAUTION You cannot migrate to the agile addressing scheme during a rollingupgrade if you are using cluster lock disks as a tie-breaker, because thatinvolves changing the cluster configuration. But under certainconditions, you can migrate the cluster lock device file names to the newscheme without bringing the cluster down. For the requirements and aprocedure, see the section “Updating the Cluster Lock Configuration” inchapter 7 of the Managing Serviceguard Fifteenth Edition user’s guide.For more information about agile addressing, see following documents athttp://docs.hp.com:•the Logical Volume Management volume of the HP-UX SystemAdministrator’s Guide (in the 11i v3 -> System Administrationcollection)