HP XC System Software Release Notes for Version 3.1

In an enclosure-based system, the discover command uses a sparse node numbering scheme.

This means that internal node names are assigned based on the enclosure in which the node is

located and the slot the node is plugged into.

For example, if a node is plugged into slot 10 of enclosure 1, the node is numbered n10. In a

configuration with two enclosures in which there might be 16 nodes in each enclosure, the node

in slot 10 in enclosure 2 is numbered n27.

Head Node Naming

The cluster_prep command prompts you to supply the maximum number of nodes in the

hardware configuration. When the hardware configuration does not contain (real) enclosures

and HP server blades, the cluster_prep command forms the head node name using the

number you specify. For example, if the maximum number of nodes allowed in your hardware

configuration is 128, the head node is node n128.

When the hardware configuration contains enclosures and HP server blades, you are not prompted

to enter the maximum number of nodes. This means that when the head node is an HP server

blade, the head node naming scheme is based on the node naming scheme described at the

beginning of this section.

If a non-server blade is the head node and the console port of the head node is not connected to

the Administration Network, the head node is numbered n0.

1.11 Enhancements to the cluster_config Utility

The cluster_config utility has been enhanced as follows:

• When the cluster_config utility process finds one or more entries in the

/opt/hptc/availability/availability_tool directory and the associated entry is

registered as an availability tool in the database, you are prompted to define availability

sets. An availability set creates an association of two nodes.

• When availability sets have been defined and roles have been assigned appropriately to the

nodes in an availability set, you are prompted on a service-by-service basis to specify how

you want to implement improved availability for the service.

• If the system is configured with a QsNet

interconnect, you are prompted to supply the

number of QsNet

switches.

• Two new command-line options have been added to the cluster_config utility:

--outfile file_name Exports configuration information into the named file.

--infile file_name Imports configuration information from the named file.

For more information about these command-line options, see cluster_config(8).

All new features are documented in the HP XC System Software Installation Guide and

cluster_config(8).

1.12 New Software Upgrade Types

A software upgrade to HP XC System Software Version 3.1 installs new versions of Linux and

HP XC RPMs on the current system. Two types of software upgrades have been introduced to

upgrade an HP XC system to Version 3.1.

As described in Table 1-1, the type of upgrade you perform depends on the version of Enterprise

Linux (EL) that is currently installed on the system and the version of EL that is delivered in the

new HP XC release.

22 New and Changed Features