HP XC System Software Installation Guide Version 3.2.1

Table 3-3 Information Required by the cluster_config Utility (continued)
Description and User ActionItem
You are prompted to supply the number of NFS daemons to be run on the head
node and on any other NFS server within the system to support the number of
NFS clients in the system. A default is provided based on the number of nodes
in the hardware configuration.
Number of NFS daemons
If you have configured improved availability with HP Serviceguard, you are
prompted to supply the name of a quorum server or the full path to the device
name of the lock LUN.
Quorum server or lock LUN
configuration for
Serviceguard clusters
One node in an HP XC system acts as an NTP server for all other nodes. By
default, this is the head node. All other nodes are NTP clients of this server,
which is known as the internal NTP server. All nodes in the system are
synchronized to the head node.
You have the option to specify up to four external time servers or to use the
default NTP server on the head node.
NTP server configuration
If you assigned the avail_node_management role to a node in an availability
set with the head node, you are prompted to specify how you want to handle
improved availability for the dbserver service. You can choose between no
improved availability or enabling improved availability through an availability
tool.
Improved availability of the
database server
For systems with a QsNet
II
interconnect, you are asked to supply the type of
network. The network type reflects the maximum number of ports the fabric
topology can support, and it is used to create the qsnet diagnostics database.
See Appendix H (page 217) for information about how to determine the QsNet
II
network type.
QsNet
II
network type
For systems with a QsNet
II
interconnect, you are asked to supply the number of
node-level and top-level switches in the configuration.
Enter the number of node level switches in your
configuration [1-32]:
Enter the number of top level switches in your configuration
[0-32]:
Number of QsNet
II
node-level and top-level
switches
If you modified the default role assignments and assigned a login role to one
or more nodes, you are prompted to enter an LVS alias. This is the host name
that users will use to log in to the HP XC system.
You have the option to decide whether you want the LVS director to act as a real
server, that is, a node that accepts login sessions:
Do you want the LVS director to act as a real server? (y/n)
If you answer yes, the LVS director is configured to act as a login session server
in addition to arbitrating and dispersing the login session connections.
If you answer no, the LVS director does not participate as a login session server;
its only function is to arbitrate and disperse login sessions to other nodes. This
gives you the flexibility to place the login role on the head node yet keep the
head node load to a minimum because login sessions are not being spawned.
The default is to configure the LVS director as a real server if LVS is not
configured with improved availability. If LVS is configured with improved
availability, the default is to arbitrate and disperse only.
If you assign the login role to nodes in an availability set, you are prompted
to specify how you want to handle improved availability for the lvs director
service. You can choose between no improved availability or enabling improved
availability through an availability tool.
LVS configuration
58 Configuring and Imaging the System