HP XC System Software Installation Guide Version 3.1

F.3.11 NIS Server Role
The nis_server role is not enabled by default. Assigning this role to a node configures the node as a
NIS slave server. If you assign this role to a node, you are prompted to enter the name of the NIS master
server and NIS domain name during cluster_config processing.
Any node assigned with the nis_server role must also have an external Ethernet network connection
defined.
nis is the configuration and management database of the service provided by this role.
F.3.12 Node Management Role
Nodes with the node_management role run a number of services that help manage other nodes in the
system. This role is restricted to the head node; it cannot be removed.
The configuration and management database names of the services provided by this role are as follows:
• Console management facility master (cmf)
• Database server (dbserver)
• Dynamic Host Control Protocol (DHCP) server (dhcp)
• HPTC file system server (hptc_cluster_fs)
• License manager (hptc-lm)
• InfiniBand switch monitor (ibmon)
• Image server (imageserver)
• HP MPI interconnect setup (mpiic)
• Myrinet switch monitor (gmmon)
• NFS server (nfs_server)
• Network time protocol (ntp)
• Power daemon server (pwrmgmtserver)
• Quadrics switch monitor (swmlogger)
The configuration and management database, in which all management configuration information is
stored, runs on a node with this role.
The power manager service manages the powering on and off of nodes in the system.
The MPI interconnect settings are managed by nodes running this role.
The image server service provides images from the SystemImager tool to all client nodes.
The NTP server synchronizes the time on all nodes.
The license manager service enables some software components in the system when a valid license is
present.
F.3.13 Resource Management Role
Nodes with the resource_management role provide the services necessary to support SLURM and LSF.
On systems with fewer than 63 total nodes, this role is assigned by default to the head node. On large-scale
systems with more than 64 nodes, this role is assigned by default to the node with the internal node name
that is one less than the head node. For example, if the head node is n256, node n255 is assigned as the
resource manager. On large-scale systems, the resource_management role is exclusive; the node with
this role has no other roles assigned to it.
The configuration and management database names of the services provided by this role are as follows:
• LSF master node (lsf)
• SLURM central control service (slurm)
• Resource Management System (RMS) (rm)
You can assign this role to multiple nodes in the cluster to provide support for failover. Multiple nodes
may have this role defined, but only one is active at a time. If the SLURM central control service fails on
the active node, the daemon will be started on another node with the resource management role.
F.3 Role Definitions 141