Storage Foundation High Availability 51Word文件下载.docx

1、The table in the slide shows the upgrade paths between older versions of Storage Foundation running on various versions of Solaris SPARC and SF 5.1 on currently supported Solaris SPARC platforms. If no upgrade path exists, perform the following steps: 1 Uninstall the old version of SF. 2 .If necessa

2、ry, upgrade OS to at least Solaris 9 with update 8. 3 .Perform full SF 5.1 installation. Note that SF 5.1 is supported on the following Solaris SPARC operating system versions: Solaris 9 with update 8 （32 or 64 bit, SPARC） Solaris 10 with update 6 or later （64 bit only, SPARC）Solaris x64 upgrade mat

3、rix The table in the slide shows the upgrade paths between older versions of Storage Foundation on Solaris x64 and SF 5.1. Storage Foundation is only supported on Solaris 10 with update 6 or later on the Intel platform. If no upgrade path exists, perform the following steps:2 Perform full SF 5.1 ins

4、tallation.AIX upgrade matrix The table in the slide shows the upgrade paths between older versions of Storage Foundation running on various versions of AIX and SF 5.1 on supported versions of AIX.Note that SF 5.1 is supported on the following AIX operating system versions:AIX 5.3 TL7 with SP6 or lat

5、er; TL8 with SP4 or later if TL8 is presentAIX 6.1 TL0 with SP6 or later; TL1 with SP2 or later if TL1 is presentWhere necessary, the table includes the AIX operating system upgrades that are required to support the 5.1 version of Storage Foundation.RHEL5 upgrade matrixThe table in the slide shows t

6、he upgrade paths between older versions of Storage Foundation running on various versions of Red Hat Enterprise Linux （RHEL） and SF 5.1 on supported versions of RHEL.If no upgrade path exists, perform the following steps:1 Uninstall the old version of SF.2 Upgrade OS to at least RHEL 5 with update 3

7、.3 Perform full SF 5.1 installation.Note that SF 5.1 is supported on RHEL 5 with update 3 or later. Where necessary, the table includes the RHEL operating system upgrades that are required to support the 5.1 version of Storage Foundation.SLES10 upgrade matrixThe table in the slide shows the upgrade

8、paths between older versions of Storage Foundation running on various versions of SUSE Linux Enterprise Server （SLES） and SF 5.1 on SLES10 SP2 or later.2 Upgrade OS to SLES10 SP2, or SLES 11.Where necessary, the table includes the SLES operating system upgrades that are required to support the 5.1 v

9、ersion of Storage Foundation.SLES11 upgrade matrixThe table in the slide shows the upgrade paths between older versions of Storage Foundation running on various versions of SUSE Linux Enterprise Server （SLES） and SF 5.1 on SLES 11.2 Upgrade OS to SLES 11.3. I/O Fencing EnhancementsFencing configurat

10、ion differencesDefault nonfencing configurationIn VCS 5.1, when a cluster is configured by the CPI installer script, fencing is automatically configured and started in disabled mode. When you display cluster membership, port b for fencing contains all nodes specified during cluster configuration.Not

11、e:Fencing is also configured in disabled mode after installation of SFRAC 5.0. With VCS 5.1, the behavior is now the same as SFRAC.vxfentab differences In VCS 5.0, the /etc/vxfentab file was automatically generated by vxfen during startup and contained the paths to the coordinator disks. The paths t

12、o coordinator disks were discovered by way of the disk group specified in the /etc/vxfendg configuration file, which is created manually in order to configure fencing. This enables all paths to be rediscovered each time a system reboots. With VCS 5.1, the /etc/vxfendg is no longer present in customi

13、zed configurations （mixed disk and server coordination points）. Instead, the disk group is specified in the /etc/vxfenmode file.With the new support of a Coordination Point server to function as a coordination point （fulfilling the role of a coordinator disk）, you can configure fencing with some or

14、no disks. Therefore, you may not have a coordinator disk group as part of the configuration.With legacy disk-only based fencing configurations, the /etc/vxfendg is present and the fencing disk group is not listed in vxfenmode.The vxfentab file also has new directives, including: Security between CPS and client clusters CPS names or virtual IP addressesThe vxfenmode file is described in detail later in this lesson where the CP server and client cluster configurations are presented.