text stringlengths 0 4.63k |
|---|
NVIDIA Base Command Manager 11
Administrator Manual
Revision: ad7ef59df
Date: Mon Oct 13 2025
|
©2025 NVIDIA Corporation & affiliates. All Rights Reserved. This manual or parts thereof may not be
reproduced in any form unless permitted by contract or by written permission of NVIDIA Corporation.
Trademarks
Linux is a registered trademark of Linus Torvalds. PathScale is a registered trademark of Cray, Inc.
Red Hat a... |
Table of Contents
Table of Contents
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
0.1
Quickstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
0.2
About This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... |
4
Table of Contents
2.5.5
Advanced cmsh Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
65
2.6
Cluster Management Daemon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
78
2.6.1
Managing And Inspecting The Cluster Management Daemon . . . . . . . . . . . .
78
2.6.2
Confi... |
Table of Contents
5
3.8.3
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
3.8.4
Managing DPU Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
3.9
Configuring Switches And PDUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... |
6
Table of Contents
3.20.3 Making All Nodes Function Differently From Normal Cluster Behavior With
FrozenFile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
3.20.4 Adding Functionality To Nodes Via An initialize Or finalize Script . . . . . . 209
3.20.5 Examples Of Configuring Node... |
Table of Contents
7
5.4.6
Checking Partitions, RAID Configuration, Mounting Filesystems . . . . . . . . . . 265
5.4.7
Synchronizing The Local Drive With The Software Image . . . . . . . . . . . . . . . 266
5.4.8
Writing Network Configuration Files
. . . . . . . . . . . . . . . . . . . . . . . . . . 271
5.4.9
Creating A L... |
8
Table of Contents
6.4.4
Logging The Actions Of CMDaemon Users . . . . . . . . . . . . . . . . . . . . . . . 329
6.4.5
Creation Of Certificates For Nodes With cm-component-certificate
. . . . . . . 329
7
Workload Management
333
7.1
Workload Managers Choices
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... |
Table of Contents
9
8.2.1
The ScaleServer Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
8.2.2
Resource Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
8.2.3
Time Quanta Optimization
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... |
10
Table of Contents
9.6
Creating A Custom Software Image
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
9.6.1
Creating A Base Distribution Archive From A Base Host . . . . . . . . . . . . . . . 533
9.6.2
Creating The Software Image With cm-create-image . . . . . . . . . . . . . . . . . 535
9.6.3
Con... |
Table of Contents
11
10.5.3 The measurable Submode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
10.5.4 The setup Submode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
10.5.5 The standalone Submode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60... |
12
Table of Contents
12 Monitoring: Job Accounting
661
12.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
12.2 Labeled Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
12.2.1 Dataproducers For Labeled Entities... |
Table of Contents
13
14.2 Getting Support With BCM Issues, And Notifications For Release Updates . . . . . . . . . 705
14.2.1 The Support Portal For BCM
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
14.2.2 Reporting Cluster Manager Diagnostics With cm-diagnose . . . . . . . . . . . . . . 707
14.2.3 R... |
14
Table of Contents
15.1.3 Services In BCM HA Setups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
15.1.4 Failover Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
15.1.5 Shared Storage
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... |
Table of Contents
15
16.5.3 Running Jupyter Kernels With Two Factor Authentication . . . . . . . . . . . . . . 811
16.5.4 Running Jupyter Kernels With Kubernetes . . . . . . . . . . . . . . . . . . . . . . . 812
16.5.5 Running Jupyter Kernels Based On NGC Containers
. . . . . . . . . . . . . . . . . 812
16.5.6 Running ... |
16
Table of Contents
D.7 Example: Logical Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
D.8 Example: Logical Volume Manager With RAID 1 . . . . . . . . . . . . . . . . . . . . . . . . 911
D.9 Example: Diskless . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .... |
Table of Contents
17
G.2 Health Checks And Their Parameters
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
G.2.1
Regular Health Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
G.2.2
GPU Health Checks
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... |
Preface
Welcome to the Administrator Manual for the NVIDIA Base Command Manager 11 (BCM) environment.
0.1
Quickstart
For readers who want to get a cluster up and running as quickly as possible with NVIDIA Base Com-
mand Manager, there is a quickstart installation guide in Chapter 1 of the Installation Manual.
0.2
About... |
20
Table of Contents
The manuals constantly evolve to keep up with the development of the BCM environment and the
addition of new hardware and/or applications. The manuals also regularly incorporate feedback from
administrators and users, who can submit comments, suggestions or corrections via the website
https://enter... |
1
Introduction
1.1
NVIDIA Base Command Manager Functions And Aims
NVIDIA Base Command Manager (often shortened to BCM) contains tools and applications to facilitate
the installation, administration, and monitoring of a cluster. In addition, BCM aims to provide users
with an optimal environment for developing and runnin... |
22
Introduction
1.2.2
Configuration, Management, And Monitoring Via BCM Tools And Applications
The administrator normally deals with the cluster software configuration via a front end to BCM. This
can be GUI-based (Base View, section 2.4) or shell-based (cmsh, section 2.5). Other tasks can be handled
via special tools pr... |
1.3 Outside The Direct Scope Of The Administrator Manual
23
1.3
Outside The Direct Scope Of The Administrator Manual
The following supplementary resources can deal with issues related to this manual, but are outside its
direct scope:
• Use by the end user: This is covered very peripherally in this manual. The user norm... |
2
Cluster Management With
NVIDIA Base Command
Manager
This chapter introduces cluster management with NVIDIA Base Command Manager. A cluster running
BCM exports a cluster management interface to the outside world, which can be used by any application
designed to communicate with the cluster.
Section 2.1 introduces a nu... |
26
Cluster Management With NVIDIA Base Command Manager
• Power Distribution Unit
• Rack Sensor Kit
• Generic Device
A device can have a number of properties (e.g. rack position, hostname, switch port) which can be
set in order to configure the device. Using BCM, operations (e.g. power on) may be performed on a
device. T... |
2.1 Concepts
27
2.1.3
Node Categories
Reasons For Categories
The collection of settings in BCM that can apply to a node is called the configuration of the node. The
administrator usually configures nodes using the Base View (section 2.4) or cmsh (section 2.5) front end
tools, and the configurations are managed internally ... |
28
Cluster Management With NVIDIA Base Command Manager
2.1.4
Node Groups
A node group consists of nodes that have been grouped together for convenience. The group can consist
of any mix of all kinds of nodes, irrespective of whether they are head nodes or regular nodes, and
irrespective of what category they are in. A ... |
2.2 Modules Environment
29
Multiple configuration overlays can be set for a node. A priority can be set for each configuration
overlay, so that a configuration overlay with a higher priority is applied to its associated node instead of
a configuration overlay with a lower priority. The configuration overlay with the highest... |
30
Cluster Management With NVIDIA Base Command Manager
The exact versions used can be selected using tab-completion. In most cases, specifying version
numbers explicitly is typically only necessary when multiple versions of an application are installed
and available. When there is no ambiguity, module names without a f... |
2.2 Modules Environment
31
Whenever users now carry out a bash login, these modules are loaded.
2. Instead of placing the modules directly in a script under profile.d like in the preceding
item, a slightly more sophisticated way is to set the modules in the meta-module /cm/shared/
modulefiles/default-environment. For e... |
32
Cluster Management With NVIDIA Base Command Manager
Switching For The Head Node
For example, for the head node:
Example
[root@basecm11 ~]# cat /etc/sysconfig/modules/lmod/cm-lmod-init.sh
export ENABLE_LMOD=1
In the preceding example, LMod is enabled, and TMod is disabled because $ENABLE_LMOD is set to 1.
Example
[ro... |
2.3 Authentication
33
Note: if this cluster has a high-availability setup with 2 head
nodes, be sure to run this script on both head nodes.
Change password for root on head node? [y/N]: y
Changing password for root on head node.
Changing password for user root.
New password:
Retype new password:
passwd: all authenticat... |
34
Cluster Management With NVIDIA Base Command Manager
node as well as on the regular node, so that by default a passwordless login works from the head
node to the regular nodes, as well as from the regular nodes to the head node.
• For the root user, an ssh passwordless login should always work from the head node to t... |
2.4 Base View GUI
35
If the administrator certificate and key are replaced, then any other certificates signed by the original
administrator certificate must be generated again using the replacement, because otherwise they will no
longer function.
Certificate generation in general, including the generation and use of non-a... |
36
Cluster Management With NVIDIA Base Command Manager
Base View should run on more up-to-date versions of the browsers in the table without issues.
Base View should run on other recent browsers without issues too, but this is not supported. Browsers
that run on mobile devices are also not supported.
2.4.1
Installing T... |
2.4 Base View GUI
37
NVIDIA Base Command Manager Base View Login Window
Figure 2.2 shows the login dialog window for Base View.
Figure 2.2: Base View Login via https://<host name or IP address>:8081/base-view
NVIDIA Base Command Manager Base View Default Display On Connection
Clicking on the Login button logs the admin... |
38
Cluster Management With NVIDIA Base Command Manager
2.4.2
Navigating The Cluster With Base View
Aspects of the cluster can be managed by administrators using Base View (figure 2.3).
Navigating The Cluster With Base View: Getting Around
The resource tree, displayed on the left side of the window, consists of represent... |
2.4 Base View GUI
39
Navigating The Cluster With Base View: A Tree Map Of Locations From The Cluster Resource
The tabs within the Cluster resource window are mapped out in the tree figure displayed next, and the
tree is followed by a brief description of its items:
Cluster
|
|-- Overview
|
|
|
|-- Cluster Utilization
|
... |
40
Cluster Management With NVIDIA Base Command Manager
|
|-- Nodes
|
|-- Accelerators
|
|-- Building Management System Integration
|
|-- Leak Detection
|
|-- NMX Manager
|
|-- Inter-node Memory Exchange (IMEX) Management
|
|-- GB200 Rack Management
|
|-- GB200 Firmware Management
|
|-- Power Reservation Steering
|
|-- ... |
2.4 Base View GUI
41
|
|
|-- Management network
|
|
`-- No zero conf
|
|
|
|-- Default category
|
|
|-- Default category
|
|
`-- ArchOS
|
|
|
|-- Sign installer certificates
|
|
`-- Sign installer certificates
|
|
|
|-- Failover
|
|
`-- Failover
|
|
|
|-- Failover groups
|
|
`-- Failover groups
|
|
|
|-- Notes
|
|
`-- ... |
42
Cluster Management With NVIDIA Base Command Manager
|
|-- Inter-node Memory Exchange (IMEX) Management
|
|-- GB200 Rack Management
|
|-- GB200 Firmware Management
|
|-- Power Reservation Steering
|
|-- Run:ai
|
|-- Autonomous Hardware Recovery
|
`-- Autonomous Job Recovery
|-- System Information
|
|-- Type
|
|-- Mem... |
2.4 Base View GUI
43
• Cluster Utilization graphs, which includes Occupation rate (page 949).
• The number of devices in various states (UP, DOWN ...) and their total number. Devices states are
covered in sections 5.5.3 and 5.5.4.
• The number of resources (Cores, DPUs, and GPUs) in various states (UP, DOWN, ...) and t... |
44
Cluster Management With NVIDIA Base Command Manager
Run Command
The Run command tab window allows a specified command to be run on a selected node of the cluster.
License Information
The License Information section of the License Information tab window shows some further infor-
mation to do with cluster licensing; it... |
2.5 Cluster Management Shell
45
2.5.1
Invoking cmsh
From the head node, cmsh can be invoked as follows:
Example
[root@mycluster ~]# cmsh
[mycluster]%
By default it connects to the IP address of the local management network interface, using the de-
fault BCM port. If it fails to connect as in the preceding example, but ... |
46
Cluster Management With NVIDIA Base Command Manager
alias lv device list virtualnode
Besides defining aliases in dotfiles, aliases in cmsh can also be created with the alias command. The
preceding example can be run within cmsh to create the lv alias. Running the alias command within
cmsh lists the existing aliases.
A... |
2.5 Cluster Management Shell
47
[mycluster]% device
[mycluster->device]% alias | egrep '(tablelist|dfh)'
alias dfh run /root/.cm/cmsh/dfh.cmsh
alias tablelist run /root/.cm/cmsh/tablelist.cmsh
[mycluster->device]% list
Type
Hostname (key)
MAC
Category
Ip
---------------------- ---------------- ------------------ ------... |
48
Cluster Management With NVIDIA Base Command Manager
Options Usage For cmsh
The options usage information for cmsh is obtainable with cmsh -h:
Usage:
cmsh [options] [hostname[:port]]
cmsh [options] -c <command>
cmsh [options] -f <filename>
Options:
--help|-h
Display this help
--noconnect|-u
Start unconnected
--contro... |
2.5 Cluster Management Shell
49
Specify alternative private key
Arguments:
hostname
The hostname or IP to connect to
command
A list of cmsh commands to execute
filename
A file which contains a list of cmsh commands to execute
Examples:
cmsh
run in interactive mode
cmsh -c 'device status'
run the device status command a... |
50
Cluster Management With NVIDIA Base Command Manager
alias ......................... Set aliases
category ...................... Enter category mode
cert .......................... Enter cert mode
cloud ......................... Enter cloud mode
color ......................... Manage console text color settings
confi... |
2.5 Cluster Management Shell
51
Usage:
run [OPTIONS] <filename> [<filename2> ...]
Options:
-x, --echo
Echo all commands
-q, --quit
Exit immediately after error
[myheadnode]%
In the general case, invoking help at any mode level or within an object, without an argument,
provides two lists:
• Firstly, under the title of T... |
52
Cluster Management With NVIDIA Base Command Manager
• The path command at any mode depth displays a string that can be used as a path to the current
mode and object, in a form that is convenient for copying and pasting into cmsh. The string can be
used in various ways. For example, it can be useful to define an alias... |
2.5 Cluster Management Shell
53
<mode> <cmd> <arg> ...<arg>; ...; <mode> <cmd> <arg> ...<arg>
where <mode> and <arg> are optional. 1
Example
[basecm11->network]% device status basecm11; list
basecm11 ............ [
UP
]
Name (key)
Type
Netmask bits
Base address
Domain name
Ipv6
------------- --------- ------------- ---... |
54
Cluster Management With NVIDIA Base Command Manager
...continued
Command
Description
refresh
Undo local changes done to the object
list
List all objects at current level
sort
Sort the order of display for the list command
format
Set formatting preferences for list output
foreach
Execute a set of commands on several ... |
2.5 Cluster Management Shell
55
[mycluster->category]% device remove node100
[mycluster->category]% device
[mycluster->device*]% commit
Successfully removed 1 Devices
Successfully committed 0 Devices
[mycluster->device]%
add:
The add command creates an object within its associated mode, and in cmsh the prompt drops
int... |
56
Cluster Management With NVIDIA Base Command Manager
image (section 2.1.2). The -w|--wait option to the commit command works around this issue
by waiting for any associated background task, such as the cloning of a software image, to be
completed before making the prompt available.
remove:
The remove command removes ... |
2.5 Cluster Management Shell
57
The “+” entry in the State column in the output of the modified command in the preceding example
indicates the object is a newly added one, but not yet committed. Similarly, a “” entry indicates an ob-
ject that is to be removed on committing, while a blank entry indicates that the obje... |
58
Cluster Management With NVIDIA Base Command Manager
property is then changed using the set command. Using get confirms that the value of the property
has changed, and the modified command reconfirms that node101 has local uncommitted changes.
The refresh command undoes the changes made. The modified command then confir... |
2.5 Cluster Management Shell
59
Running the list command with no argument uses the current format string for the mode. Running
the list command with the -f option, and without specifying a size for the column keeps the column 20
characters wide.
Running the format command without arguments displays the current format s... |
60
Cluster Management With NVIDIA Base Command Manager
Here a node called largenamefornode is truncated to 14 characters, with the + replacing the 14th
character.
The parameters to be viewed can be chosen from a list of valid fields by running the format command
without any options, as shown earlier.
The format command ... |
2.5 Cluster Management Shell
61
[basecm11->device]% list -f type:15,hostname:15,mac
type
hostname (key)
mac
--------------- --------------- --------------------
HeadNode
basecm11
08:0A:27:BA:B9:43
PhysicalNode
log001
52:54:00:DE:E3:6B
PhysicalNode
node002
00:00:00:00:00:00
[basecm11->device]% sort mac hostname
[basecm1... |
62
Cluster Management With NVIDIA Base Command Manager
indicating a dependency of apc01 on itself. If the device is to be removed, then the 2 references to it first
need to be removed, and the device also first has to be brought to the CLOSED state (page 276) by using
the close command.
Example
[mycluster->device]% usedb... |
2.5 Cluster Management Shell
63
Default gateway metric
0
Switch ports
Interfaces
<1 in submode>
Static routes
<0 in submode>
GPU Settings
<0 in submode>
BMC Settings
<submode>
...
Working With Objects: assign, unassign
The assign and unassign commands are analogous to add and remove. The difference between assign
and a... |
64
Cluster Management With NVIDIA Base Command Manager
[basecm11->device[node001]->roles]% import
<TAB><TAB>
backup
etcd::host
pbsproclient
boot
failover
pbsproserver
...
...and other available roles including slurmclient...
[basecm11->device[node001]->roles]% import --overlay slurm-client slurmclient
[basecm11->device... |
2.5 Cluster Management Shell
65
Relay Host
Externally visible IP
0.0.0.0
Time zone
Europe/Amsterdam
BMC Settings
<submode>
SNMP Settings
<submode>
DPU Settings
<submode>
SELinux Settings
<submode>
Access Settings
<submode>
Provisioning Settings
<submode>
ZTP settings
<submode>
ZTP new switch settings
<submode>
NetQ set... |
66
Cluster Management With NVIDIA Base Command Manager
This history is saved in the file .cm/.cmshhistory in the cmsh user’s directory. The timestamps in
the file are in unix epoch time format, and can be converted to human-friendly format with the standard
date utility.
Example
[root@mycluster ~]# tail -2 .cm/.cmshhisto... |
2.5 Cluster Management Shell
67
the commands can be run with the redirection operator as:
Example
[root@mycluster ~]# cmsh < runthis
device
get node001 ip
10.141.0.1
Running the file with the -f option avoids echoing the commands
Example
[root@mycluster ~]# cmsh -f runthis
10.141.0.1
The ssh Command
The ssh command is r... |
68
Cluster Management With NVIDIA Base Command Manager
The watch Command
The watch command within cmsh is a simplified version of the standard unix watch command.
The watch command takes as its argument a second command that is to be executed within cmsh.
On execution of the watch command, the second command is executed... |
2.5 Cluster Management Shell
69
– -n|--nodes,
-g|--group,
-c|--category,
-r|--rack,
-h|--chassis,
-e|--overlay,
-l|--role, -m|--image, -u|--union, -i|--intersection
– -t|--type chassis|fabricresourcebox|fabricswitch|genericdevice|litenode|cloudnode|
dpu|physicalnode|headnode|powerdistributionunit|racksensor|switch|unma... |
70
Cluster Management With NVIDIA Base Command Manager
– Overriding the default heuristics for IP address allocation: The default heuristics for IP
address allocation choose the next free IP address if, among other conditions, the same base
name is used for the clone. Thus, if the base name used differs from the origin... |
2.5 Cluster Management Shell
71
Example
[myheadnode->device]% foreach * (get ip; status)
10.141.253.1
switch01 ............ [
DOWN
]
10.141.255.254
myheadnode .......... [
UP
]
10.141.0.1
node001 ............. [ CLOSED ]
10.141.0.2
node002 ............. [ CLOSED ]
[myheadnode->device]%
Another example that lists all th... |
72
Cluster Management With NVIDIA Base Command Manager
– example: rack[1-2]node0[1-3]
which is: rack1node01,rack1node02,rack1node03,rack2node01,
rack2node02,rack2node03
Essentially the same as the previous one, but for nodes that were named more verbosely.
• sequential exclusion (negation):
example: node001..node005,-n... |
2.5 Cluster Management Shell
73
The range Command
The range command provides an interactive option to carry out basic foreach commands over a group-
ing of nodes. When the grouping option has been chosen, the cmsh prompt indicates the chosen range
within braces ({}).
Example
[basecm11->device]% range -n node0[01-24]
[b... |
74
Cluster Management With NVIDIA Base Command Manager
Commands can be run inside a range. However, running a pexec command inside a range is typi-
cally not the intention of the cluster administrator, even though it can be done:
Example
[basecm11->device]% range -n node[001-100]
[basecm11->device{-n node[001-100]}]% p... |
2.5 Cluster Management Shell
75
-
home;
[mycluster->device[node001]]% home
[mycluster]% goto
[mycluster->device[node001]]% goto -
[mycluster]% goto
[mycluster->device[node001]]% bookmark dn1
[mycluster->device[node001]]% goto -
[mycluster]% goto dn1
[mycluster->device[node001]]%
Saving bookmarks, and making them persis... |
76
Cluster Management With NVIDIA Base Command Manager
then 2 digits are used for each number suffix, in order to match the size of the last number.
String formatting can be used to specify the number of digits in the padded number field:
Example
[basecm11->device]% rename node[001-003] test%04d
Renamed: node001 to test0... |
2.5 Cluster Management Shell
77
Using CMDaemon Environment Variables In Scripts
Within device mode, the environment command shows the CMDaemon environment variables (sec-
tion 3.3.2 of the Developer Manual) that can be passed to scripts for particular device.
Example
[mycluster->device]% environment node001
Key
Value
-... |
78
Cluster Management With NVIDIA Base Command Manager
"mac": "FA:16:3E:95:80:9F",
"status": "[
UP
]"
}
]
[basecm11->device]%
The color off setting is needed to remove the default console coloring. If the command is to run
from the bash shell, the same output can be achieved with:
Example
[root@basecm11 ~]# cmsh --colo... |
2.6 Cluster Management Daemon
79
The cluster management daemon can be restarted on all regular nodes that are up:
Example
[root@mycluster ~]# pdsh -a "systemctl restart cmd; systemctl is-active cmd"
node001: active
node002: active
node003: active
[root@mycluster ~]#
This uses pdsh, the parallel shell command (section 1... |
80
Cluster Management With NVIDIA Base Command Manager
2.6.2
Configuring The Cluster Management Daemon
Many cluster configuration changes can be done by modifying the cluster management daemon config-
uration file. For the head node, the file is located at:
/cm/local/apps/cmd/etc/cmd.conf
For regular nodes, it is located in... |
2.6 Cluster Management Daemon
81
[root@basecm11 ~]# cmdaemonctl -h
cmdaemonctl [OPTIONS...] COMMAND ...
Query or send control commands to the cluster manager daemon.
-h --help
Show this help
Commands:
debugon
Turn on CMDaemon debug
debugoff
Turn off CMDaemon debug
...
[root@basecm11 ~]# cmdaemonctl debugon
CMDaemon deb... |
82
Cluster Management With NVIDIA Base Command Manager
2.6.5
Configuration File Modification, And The FrozenFile Directive
As part of its tasks, the cluster management daemon modifies a number of system configuration files.
Some configuration files are completely replaced, while other configuration files only have some sections... |
2.6 Cluster Management Daemon
83
2.6.7
CMDaemon Lite
Introduction
As an alternative to the regular CMDaemon, BCM provides a lightweight CMDaemon, called CMDae-
mon Lite. This is intended as a minimal alternative to the regular CMDaemon for nodes that are not
managed by CMDaemon. CMDaemon Lite is contained in the packag... |
84
Cluster Management With NVIDIA Base Command Manager
After register_node is run, CMDaemon running on the head node is able to see the certificate request.
Depending on the network that the CMDaemon Lite on the lite node is connected to, the certificate will
be automatically issued, just like it is for regular BCM nodes... |
2.6 Cluster Management Daemon
85
The ZTP settings should be configured from ztpsettings mode, and a username and password
must be set within the accesssettings mode for the Cumulus switch. Further details on configuring
Cumulus switches are given in section 3.10.
Even Lighter Than CMDaemon Lite: Configuring A Device As A ... |
3
Configuring The Cluster
After the NVIDIA Base Command Manager software has been installed on the head node, the cluster
must be configured. For convenience, the regular nodes on the cluster use a default software image
stored on the head node. The image is supplied to the regular nodes during a process called provision... |
88
Configuring The Cluster
This is because the front ends are usually analogous enough to each other when carrying out a
configuration procedure, so that describing the procedure for the other front end in detail as well is
mostly wasteful. If the procedures differ significantly, then guidance is typically given on the di... |
3.1 Main Cluster Configuration Settings
89
• Time zone: Default value: Specified during installation (figure 3.8 in Chapter 3 of the Installation
Manual).
• BMC settings: This allows BMC and related settings to be managed.
The following objects already exist by default on a new cluster, and can have their settings modi-
fi... |
90
Configuring The Cluster
3.1.2
Cluster Configuration: Some Network-Related Settings
The following network-related settings are also described in the context of external network settings for
the cluster object, in section 3.2.3, as well as in the quickstart in Chapter 1 of the Installation Manual.
Nameserver And Search ... |
3.1 Main Cluster Configuration Settings
91
Example
[basecm11]% partition
[basecm11->partition[base]]% get searchdomains
example.com:1
domain.test:6
If an index is set for one search domain, then setting indices for all search domains is recommended.
Search domains without indices are handled automatically by CMDaemon.
C... |
92
Configuring The Cluster
Example
[basecm11]% partition use base
[basecm11->partition[base]]% set timezone america/los_angeles
[basecm11->partition*[base*]]% commit
A time zone setting can also be applied at the level of a node, category, edge site, and cloud region.
As is usual in the BCM hierarchy, the value set for ... |
3.1 Main Cluster Configuration Settings
93
SMTP Relay Host Mailserver Setting
The head node uses Postfix as its SMTP server. The default base distribution configuration is a minimal
Postfix installation, and so has no value set for the SMTP relay host. To set its value:
• in Base View: the Relay Host field, with the navigat... |
94
Configuring The Cluster
• Cluster > Settings > Default burn configuration
This allows the Default burn configuration for a node burn run to be modified.
• Cluster > Settings > Burn configs
This lists the possible burn configuration settings in a subwindow, and allows changes to some of
their properties of each item of ... |
3.1 Main Cluster Configuration Settings
95
As is usual in BCM, the node-level setting overwrites the category-level setting.
Setting FIPS compliance on the head node itself via CMDaemon is not allowed. This is because
FIPS GRUB configuration could, in some unusual cases, result in an unbootable head node. The clus-
ter a... |
96
Configuring The Cluster
Depending what is running on the server, and the load on it, the administrator may wish to increase
the resource limit values.
A very rough rule-of-thumb that may be useful as a first approximation to set file-max optimally is
suggested in the kernel source code. The suggestion is to simply mul... |
3.2 Network Settings
97
External
Head
node001
node002
node003
node004
node005
node006
Internal
Network
Network
= Network Interface
Figure 3.2: Network Settings Concepts
The configuration of network settings is completed when, after having configured the general net-
work settings, specific IP addresses are then also assi... |
98
Configuring The Cluster
Figure 3.3: Networks
In the context of the OSI Reference Model, each network object represents a layer 3 (i.e. Network
Layer) IP network, and several layer 3 networks can be layered on a single layer 2 network (e.g. routes
on an Ethernet segment).
Opening up the subwindow for a network such as... |
3.2 Network Settings
99
erties to be changed (figure 3.5).
Figure 3.5: Network Settings
The properties of figure 3.5 are introduced in table 3.1:
Property
Description
Name
Name of this network.
Domain Name
DNS domain associated with the network.
Type
Menu options to set the network type. Options are Internal, External,
T... |
100
Configuring The Cluster
...continued
Property
Description
Lock down dhcpd
Enabling means new nodes are not offered a PXE DHCP IP address from
this network, i.e. DHCPD is “locked down”. A DHCP “deny unknown-
clients” option is set by this action, so no new DHCP leases are granted to
unknown clients for the network. U... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.