| United States-English |
|
|
|
![]() |
HP XC System Software: Installation Guide > Chapter 2 Installing Software on the Head NodeTask 4: Install Additional Software from Local Distribution Media |
|
Perform this task only if you need to install additional HP software products, third-party software products, or other software that is required for the applications or HP XC environment. Otherwise, bypass this task.
If you have a copy of the distribution media in your possession, install the software now before the system is configured so that the software is transparently propagated to all nodes during the initial image synchronization. You can install additional software now only if the software is locally available. The remainder of this section provides information about installing and using additional software products on an HP XC system. The following topics are addressed: This section lists several prominent HP software products that you can integrate into an HP XC system. You might require some of these products depending upon how you plan to configure the HP XC system software environment. You must purchase and license these products from HP. See your HP representative or the product documentation for more information. HP Serviceguard is the service availability tool recommended for use on an HP XC system. If you intend to use Serviceguard as the availability tool, you must have in your possession the Serviceguard license, distribution media, and product documentation. Use the Serviceguard documentation to install the product and configure it for use now. The documentation is available from the following Web site: http://www.docs.hp.com/en/ha.html The HP XC System Software has been tested with the following versions of Serviceguard; install the RPMs in the following order:
The quorum server RPM, qs-A.02.00.03-0.product.redhat, is required only if you plan to configure a quorum server. If your particular configuration uses lock LUNs exclusively, you do not install the quorum server RPM. The HP Serviceguard software contains two modules that are built against the kernel. After installing the Serviceguard software, proceed to “Deciding on the Method to Achieve Quorum for Serviceguard Clusters” to define and configure the method to achieve quorum. Deciding on the Method to Achieve Quorum for Serviceguard Clusters. In a Serviceguard configuration, each availability set becomes its own two-node Serviceguard cluster, and each Serviceguard cluster requires some form of quorum. The quorum acts as a tie breaker in the Serviceguard cluster running on each availability set. If connectivity is lost between the nodes of the Serviceguard cluster, the node that can access the quorum continues to run the cluster and the other node is considered down. The quorum can be either a quorum server or a lock LUN; you must configure one or the other on every availability set. You can configure a lock LUN as the tie breaker only if the head node and the other node in the availability set are both connected to the same shared storage (for instance, an MSA) and both are able to access the same partition. Configuring a Quorum Server. You can select any node in the HP XC system that is not participating in any availability set to serve as the quorum server, even a compute node. You can use the same quorum server for one or more availability sets. If you configure a quorum server, you must have previously installed the qs-A.02.00.03-0.product.redhat.ia64.rpm RPM. Later, the cluster_config utility prompts you to supply the node name of the quorum server; there is nothing you need to do now. Configuring a Lock LUN. If you intend to use a lock LUN instead of a quorum server to achieve quorum, enter the following command to create the lock LUN now, before running the cluster_config utility later in the system configuration process. In the following command, /dev/sdb is the full path to the disk on the MSA, and partition 1 on that disk is configured as the lock LUN:
When you run the cluster_config utility, it prompts you to supply the name of the lock LUN, and you must supply the full path with partition (for example, /dev/sdb1, where 1 is the partition number). The HP Scalable Visual Array (SVA) is a scalable visualization solution that brings the power of parallel computing to bear on many demanding visualization challenges. SVA can be a specialized, standalone system consisting entirely of visualization nodes, or it can be integrated into a larger HP Cluster Platform system such as HP XC and share a single interconnect with the compute nodes and a storage system. If SVA was not installed at the factory, and you want to integrate SVA into the HP XC system, you must have the SVA distribution media in your possession. Install the RPMs now by following the instructions in the SVA documentation: An HP XC system supports the use of several third-party software products. Use of these products is optional; the purchase and installation of these components is your decision depending on the software requirements. Potentially important software that is not bundled with the HP XC software includes the Intel Fortran and C compilers, The Portland Group PGI compiler, and the TotalView Debugger. HP recommends that you install additional software components now before the system is configured (the procedure described in Chapter 3) so that the software is propagated to all nodes during the initial image synchronization. This chapter does not contain product-specific information for third-party software products; see the documentation supplied by the vendor for product-specific information. The following sources contain more information about optional software products that are available for use with HP XC systems:
The XC software does not bundle or resell Intel or PGI compilers. You are responsible for purchasing and licensing them from the third-party vendors. There may be run-time licensing issues (for running the resulting applications) separate from licensing the compiler itself. You can install additional compilers on HP XC systems, such as those from Intel or PGI, after the initial system installation by using the installation instructions supplied by their kits and by distributing the software to all nodes as described in the HP XC System Software Administration Guide, so that the supplied libraries are visible to distributed applications. During the compiler installation process, use the default locations suggested by the installation process, if possible. If you change the installation directory and modules are being used, you must edit the corresponding modulefile to point to their new location or create a corresponding symbolic link. Modulefiles are located in the /opt/module/modulefiles directory. In some cases, it might be desirable to install the compiler in other than the default installation location, for example:
Go to the following Web sites for more information about the supported compilers:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||