分类：
2006-03-12 01:00:23
HACMP V5 works with pSeries and iSeries servers in a "no-single-point-of-failure" server configuration.
HACMP V5 supports the pSeries, Cluster 1600, RS/6000, and iSeries models that are designed for server applications and that meet the minimum requirements for internal memory, internal disk, and I/O slots. The following pSeries, iSeries, and RS/6000 models and their corresponding upgrades are supported in HACMP V5.2 and V5.3:
Note: Heartbeat network is only supported with serial port 3 or 4 on the Model 6Fx.
Notes
Additional requirements and specifications are detailed at
Any supported pSeries or RS/6000 server can be joined with any other supported pSeries or RS/6000 server in an HACMP V5 configuration. Models with fewer than three slots can be used in the HACMP V5 server configuration, but due to slot limitations, a single point-of-failure is unavoidable in shared-disk or shared-network resources.
HACMP V5.2 and V5.3 support concurrent access configuration with all supported external storage systems.
Certain non-IBM RAID systems can operate in concurrent I/O access environments. IBM will not accept Authorized Program Analysis Reports (APARs) if the non-IBM RAID offerings do not work properly with HACMP V5.
The minimum configuration of each machine is highly dependent on the user's database package and other applications.
Actual configuration requirements are highly localized according to the required function and performance needs of individual sites. In configuring a cluster, particular attention must be paid to:
Whenever a process takes over resources after a failure, consideration must be given to work partitioning. For example, if node A is expected to take over for failed node B and continue to perform its original duties, A must be configured with enough resources to perform the work of both.
HACMP V5.2 and V5.3 device support
HACMP supports client users on a LAN using TCP/IP. HACMP monitors and performs IP address switching for the following TCP/IP-based communications adapters on cluster nodes:
At this time, the following adapters are supported in the HACMP V5 environment. Refer to individual hardware announcements for the levels of AIX 5L supported.
Communications adapters
PCI/ISA
MCA
Storage adapters
PCI
MCA
For compatibility with subsystems not listed in the following section, refer to the individual hardware announcements.
External storage subsystems
Tape drive support
Router support
This router can be used in cluster configurations where the router is used to provide communications to client systems. This router is not supported in the communications path between nodes in an HACMP cluster.
Rack-mounted storage subsystems
The following table shows the SCSI-2 Single-Ended, SCSI-2 Differential, and SSA cabling that HACMP V5 supports.
Maximum
number of
enclosures
Type Adapter Enclosure per bus
SCSI-2 Differential 6209 7131-105 2
(16-bit) 7137-413 2
7137-414 2
7137-415 2
7137-513 2
7137-514 2
7137-515 2
SCSI Single-Ended 2415 7027-HSC 1
6208
SCSI-2 Differential 2420 7137-413 2
(8-bit) 7137-414 2
7137-415 2
7137-513 2
7137-514 2
7137-515 2
SCSI-2 Differential 2416 7027-HSD 1
(16-bit) or 2412 7131-105 2
7137-413 2
7137-414 2
7137-415 2
7137-513 2
7137-514 2
7137-515 2
7204-317 14
7204-325 14
7204-339 14
SSA 6214 7133-020 96 disks
or 6216 7133-600 96 disks
7133-D40 96 disks
7133-T40 96 disks
7131-405 4
SCSI-2 Differential disk cabling for HACMP
The cabling configurations in the following tables assume the processors are at the end of the bus (just before each terminator) and the storage devices are connected to the bus between two of the processors.
The first table lists the available y-cables. Y-cables have three legs that are called base, long leg, and short leg. The first table shows what you can connect to each leg. The cables listed under the long leg and short leg columns can be found in the subsequent table under the cable name column, except for the terminator, which is supplied with the y-cable.
Y-Cable
feature Base to Long leg to Length
number adapter device cable Short leg (m) Notes
2114 6209 7131-105 Terminator, .94 16-bit
7137-413 System-to-
7137-414 System Cable
7137-415
7204-339
2422 2420 7137-413 Terminator, .765 8-bit
7137-414 System-to-
7137-415 System Cable
7137-513
7137-514
7137-515
7204-339
Y-Cable
feature Base to Long leg to Length
number adapter device cable Short leg (m) Notes
2426 2416 7027-HSD Terminator, .94 16-bit
or 2412 7131-105 System-to-
7137-413 System Cable
7137-414
7137-415
7137-513
7137-514
7137-515
7204-317
7204-325
7204-339
Cable
Cable/Device feature Length
From To number (m) Cable name
Y-cable Y-cable 2423 2.5 System-to-System Cable
(8-bit)
Y-cable Y-cable 2424 0.6 System-to-System Cable
(16-bit)
Y-cable Y-cable 2425 2.5 System-to-System Cable
(16-bit)
Y-cable 7204-317 2845 0.6 7204 16-bit Cable
7204-317 7204-317
Y-cable 7204-325
7204-325 7204-325
Y-cable 7204-329
7204-329 7204-329
Y-cable 7204-317 2846 2.5 7204 16-bit Cable
7204-317 7204-317
Y-cable 7204-325
7204-325 7204-325
Y-cable 7204-329
7204-329 7204-329
Y-cable 7131-105 2882 1.0 7131-105 Cable
7131-105 7131-105
Y-cable 7131-105 2.5 7131-105 Cable
7131-105 7131-105
Y-cable 7131-105 2885 4.5 7131-105 Cable
7131-105 7131-105
Y-cable 7131-105 2870 12.0 7131-105 Cable
7131-105 7131-105
Y-cable 7131-105 2869 14.0 7131-105 Cable
7131-105 7131-105
Y-cable 7131-105 2868 18.0 7131-105 Cable
7131-105 7131-105
Cable
Cable/Device feature Length
From To number (m) Cable name
Y-cable 7131-105 9158 1.0 7131-105 Cable
Y-cable 7131-105 9132 2.5 7131-105 Cable
Y-cable 7131-105 9161 4.5 7131-105 Cable
Y-cable 7131-105 9146 12.0 7131-105 Cable
Y-cable 7131-105 9145 14.0 7131-105 Cable
Y-cable 7131-105 9144 18.0 7131-105 Cable
2415 7027-HSC 3133 3.0 7027-HSC Cable
2415 7027-HSC 3134 6.0 7027-HSC Cable
6208 7027-HSC 3133 3.0 7027-HSC Cable
6208 7027-HSC 3134 6.0 7027-HSC Cable
Y-cable 7027-HSD 3137 12.0 7027-HSD Cable
Y-cable 7027-HSD 3138 18.0 7027-HSD Cable
Y-cable 7137-413 2002 4.0 7137 Cable (8-bit
7137-414 to 16-bit)
7137-513
7137-514
7137-515
Y-cable 7137-413 2014 2.0 7137 Cable (16-bit)
(2426) 7137-414
7137-415
7137-513
7137-514
7137-515
Cable
Cable/Device feature Length
From To number (m) Cable name
7137-413 7137-413 3001 2.0 7137 System-to-
7137-414 7137-414 System Cable
7137-415 7137-415
7137-513 7137-513
7137-514 7137-514
7137-515 7137-515
SSA Disk Cabling for HACMP V5
HACMP 5.2 and 5.3 support all of the announced SSA cables and Fiber Optics Channel Extenders. Refer to the appropriate system manuals for cabling information.
Other hardware
Other hardware supported in the previous release of HACMP V5 and still covered under IBM warranty service remains supported in this release of HACMP unless otherwise noted.
The specific requirements for AIX 5L are:
Note: HACMP V5.3 is not supported on AIX 5L V5.1. HACMP V5.2 continues to support AIX 5L V5.1 with the 5100-08 Recommended Maintenance package (or later modification levels).
Note: Refer to the section for APARs required for POWER5 support.
PSSP V3.5 is also required on RS/6000 SP (9076) systems.
The RSCT file sets delivered with AIX 5L must be installed at the following minimum levels. They are:
In addition, specific requirements for RSCT include:
Each node within a high availability server complex requires the licensed program HACMP V5 to be installed. Except during the upgrade process from earlier releases of HACMP V4, it is recommended that all nodes in the HACMP server complex be at the same AIX 5L operating system level, including PTFs and maintenance upgrades.
Some of the devices supported in HACMP V5 may require a later release level of the AIX 5L operating system; refer to the specific hardware announcement for the AIX 5L release levels required by the hardware.
APARs are required for support of DLPAR, CUoD, and CBU, as follows:
The HAView facility requires the installation of Tivoli NetView for AIX 5L (5697-NVW).
To use C-SPOC with VPATH disks, SDD 1.3.1.3, or later, is required.
To use HACMP Online Planning Worksheets, AIX 5L Java™ Runtime Environment is required.
HACMP V5 supports use of AIX 5L V5.2 MPIO for multipath access to disk subsystems.
HACMP/XD requires:
Note: It is assumed that the command line interface is installed in its default location, /opt/ibm/ESScli.
HACMP Smart Assist requires:
HACMP Smart Assist supports the following applications or later modification levels of these applications:
Note: If migrating from HACMP V5.2 to V5.3, WebSphere Application Server V5.0 will continue to be supported.
Compatibility: HACMP V5.3 supports dynamic upgrade from HACMP 4.5, 5.1, and 5.2, and static upgrades from all prior versions:
Note: Although HACMP V4 and V5 can coexist in a cluster temporarily, the Version Compatibility function is intended to ease migration from prior releases of HACMP V4 and is not intended to provide long-term compatibility between versions of the product in a cluster.
Limitations: HACMP provides high availability for the applications and resources executing on the nodes in the HACMP cluster. HACMP does not provide availability beyond the realm of the cluster nodes. A high availability implementation requires that there be no single points-of-failures (for example, primary and backup HACMP's in LPAR partitions within a single server frame).
Specific limitations of HACMP
HACMP can be run in LPARs to which processors or memory are added through CUoD or DLPAR (refer to Hardware Announcement , dated October 8, 2002) or CBU (refer to Hardware Announcement , dated October 14, 2003.) Care must be taken to ensure that sufficient capacity and appropriate procedures are in place to support these features.
Adjusting the hardware configuration (adding or removing processors or memory) of an HACMP node will, under many circumstances, put a significant additional temporary load on that system. This can cause HACMP to interpret that system as having failed. HACMP does not currently have a supported mechanism that will automatically deal with this in all cases. Customers who want to take advantage of these features should run tests and perform adequate benchmarking of their environments to determine the timing implications under varying workload conditions. IBM is not responsible for failures due to incorrect settings of these values, as these tuning parameters are unique for every customer environment.
Specific limitations of HACMP/XD
Note: For additional information regarding these GLVM limitations, refer to Software Announcement , dated March 15, 2005.
For additional information regarding IP-based mirroring, refer to the IBM HAGEO/GeoRM Software Announcement , dated October 8, 2002.
Specific limitations of HACMP Smart Assist
Environmental conditions that affect the use of HACMP
Performance considerations: HACMP 5.3.0 cluster performance can be measured and reported in many ways. In a mutual takeover/partitioned workload cluster environment, the user's applications and data are spread across two to 32 nodes in a cluster. Data management and application management can be placed under the control of a single node for efficiency, or on each node for performance. In this partitioned environment, minimal interaction between nodes in a cluster derives high efficiency in each node. When a failover occurs and the backup node takes over for a failed node, performance is degraded for that period of time when the node is down.
In data sharing, LAN and file system overhead and data contention can reduce processor efficiency. Where data must be shared, the concurrent access configuration can be utilized, but less efficiently than a single system because distributed locks must be maintained between cluster nodes and processors.
Customer responsibilities: Customers who purchase two or more HACMP licenses may replicate the contents of the following file sets throughout their enterprise:
Installability
Conversion utilities: HACMP 5.3.0 includes conversion utilities to help you convert your configuration from earlier releases of HACMP without installing each intervening version.
All of these conversions can be done while your cluster is not operational; for information regarding node conversion while maintaining cluster operation, refer to the section.
The following conversions are provided for converting existing configurations of HACMP V4 (HAS, ES, CRM, or ESCRM) or HACMP V5 to HACMP V5.3:
HACMP 5.3.0 includes conversion utilities to help you migrate your configuration between products in the HACMP family.
Packaging
The announced program uses the security and auditability features of AIX 5L V5.2 and V5.3 for servers. The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.