QuickSpecs Changes

HP TruCluster Server V5.1B-2


October 23, 2009 - From Version 7 to 8
Removed
Removed all references to the MSA30 SWD storage array.
January 6, 2006 - From Version 6 to 7
Added
Storage Box Description
BA350 Single ended, narrow
BA356 Single ended, wide
DS-BA356 Ultra SCSI, SBB shelf
DS-SSL14-RS 4254 Storage Enclosure, dual bus, Ultra2
DS-SL13R-BA 4354 Storage Enclosure, dual bus, Ultra3


Storage Boxes NOT Currently Supported on Shared Bus
3R-A4075-AA (302969-B21) MSA30SB Single Bus (S/B) Rack Mountable
3R-A4076-AA (302970-B21) MSA30DB Dual Bus (D/B) Rack Mountable
August 16, 2004 - From Version 5 to 6
Changed
V5.1B-1 was changed to V5.1B-2 throughout the document. Several URLs were corrected.
July 26, 2004 - From Version 4 to 5
Changed
V5.1B-1 was changed to V5.1B-2 throughout the document.
December 8, 2003 - From Version 3 to 4
Changed/Added/Removed
V5.1B was changed to V5.1B-1 throughout the document.  Note the title change.
Features - TruCluster Server V5.1B-1
What's New for TruCluster Server Version 5.1B-1 TThe Cluster File System (CFS) load balancing daemon (cfsd) can monitor and analyze file system usage, make recommendations, and automatically relocate file systems. The daemon can be configured to automatically relocate file systems based on CFS memory usage, or during cluster transitions (when members join or leave the cluster), or when storage connectivity changes. In addition, the member that will serve a given file system can be specified when that file system is mounted.

To speed the process of upgrading the cluster, a rolling upgrade option has been introduced to allow an administrator to upgrade multiple cluster members in parallel.

Administrators looking for a quicker alternative to a rolling upgrade when installing patches now have the option of a new patch procedure that favors upgrade speed over cluster high availability. After the first member receives the patch, all remaining members of the cluster receive the patch at the same time, followed by rebooting the entire cluster as a single operation.

Administrators can now request that the cluster application availability (CAA) facility reevaluate the placement within the cluster of registered applications either at a regularly scheduled time, or any time at which they desire to manually balance applications by using the caa_balance command. Balancing decisions are based on the standard CAA placement mechanisms. Similarly, administrators can now request that CAA schedule an automatic failback of a resource for a specific time. This allows an administrator to benefit from CAA automatically moving a resource to the most-favored cluster member without the worry of the relocation occurring at a critical time. The caa_report utility can provide a report of availability statistics for application resources. Administrators can now have the output of CAA resource action scripts redirected so that the output is visible during execution. Lastly, it is now possible to add user-defined attributes to a resource profile and have them available to the action script upon its execution.

TruCluster Server now offers more flexible network configuration options. Cluster members do not need to have identical routing configurations. Administrators can use routing daemons such as gated or routed, or they can configure a cluster member to use only static routing.

Cluster File System The Cluster File System (CFS) load balancing daemon (cfsd) can monitor and analyze file system usage, make recommendations, and automatically relocate file systems. The daemon can be configured to automatically relocate file systems based on CFS memory usage, or during cluster transitions (when members join or leave the cluster), or when storage connectivity changes. In addition, the member that will serve a given file system can be specified when that file system is mounted.
Storage Hardware Requirements
Device Description
KGPSA-BC PCI-to-Fibre Channel host adapter
KGPSA-CA PCI-to-Fibre Channel host adapter
KGPSA-DA PCI-to-Fibre Channel host adapter
KGPSA-EA (302784-B21, FCA2384) 2Gb PCI or PCI-X to FibreChannel Host Bus Aadapter
HSG60 Array Controller
KGPSA-EA (302784-B21, LP9802) 2Gb FibreChannel Host Bus Aadapter
HSG80 Array Controller
HSV110 Array Controller
XP128/1024 Array Controller
XP512/48 Array Controller
MSA1000 (3R-A4328-AA, 201723-B22) Storage Works modular SAN array
Hardware Requirements
Supported Storage Boxes TruCluster Server supports the following storage boxes:
Storage Box Description
BA350 Single ended, narrow
BA356 Single ended, wide
DS-BA356 Ultra SCSI, SBB shelf
DS-SSL14-RS 4254 Storage Enclosure, dual bus, Ultra2
DS-SL13R-BA 4354 Storage Enclosure, dual bus, Ultra3
3R-A4075-AA (302969-B21) MSA30SB Single Bus (S/B) Rack Mountable
3R-A4076-AA (302970-B21) MSA30DB Dual Bus (D/B) Rack Mountable
Ordering Information
Software Licensing
The HP TruCluster Server license provides the right to use the software as described in this QuickSpecs, and is furnished under the licensing of HP Computer Corporation's Standard Terms and Conditions. The version of HP TruCluster Server described in this QuickSpecs qualifies as a minor version release. Licenses for prior versions must be updated to this version either through the purchase of a Service Agreement that includes the rights-to-use new versions, or through the purchase of Update Licenses. Each system in the TruCluster Server environment requires separate Tru64 UNIX and TruCluster Server licenses. Hard partitions of ES80, GS80, GS160, GS320, and GS1280 AlphaServers can be clustered together either across separate systems or within systems, and only one TruCluster license is required per system. For more information about the HP licensing terms and policies, contact your local HP representative or reseller.
This product supports the Tru64 UNIX License Management Facility (LMF). License units for the TruCluster Server product are allocated on an unlimited-system-use basis.
For more information on the License Management Facility, see the Tru64 UNIX Operating System QuickSpecs or the Tru64 UNIX operating system documentation.
September 5, 2003 - From Version 2 to 3
Changed
This Document was put into the new format.
March 31, 2003 - From Version 1 to 2
Changed
Significant changes occurred throughout the entire document.