> This page is for version 11 (default). > For other versions, use one of these documentation indexes: > - 11 (default): https://docs.nvidia.com/base-command-manager/product-manuals/11/llms.txt > - 10: https://docs.nvidia.com/base-command-manager/product-manuals/10/llms.txt > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.nvidia.com/base-command-manager/product-manuals/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/base-command-manager/product-manuals/_mcp/server. # 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 running applications that require extensive computational resources. ## 1.2 The Scope Of The Administrator Manual (This Manual) The *Administrator Manual* covers installation, configuration, management, and monitoring of BCM, along with relevant background information to help understand the topics covered. ### 1.2.1 Installation Installation can generally be divided into parts as follows, with some parts covered by the *Administrator Manual*, some by the [*Installation Manual*](/installation/introduction), and some by other manuals: * **Initial installation of BCM:** This is covered in the [*Installation Manual*](/installation/introduction), which gives a short introduction to the concept of a cluster along with details on installing BCM onto the head node. The [*Installation Manual*](/installation/introduction) is therefore the first manual an administrator should usually turn to when getting to work with BCM for the first time. The *Administrator Manual* can be referred to as the main reference resource once the head node has had BCM installed on it. * **Provisioning installation:** This is covered in the *Administrator Manual*. After the head node has had BCM installed on it, the other, regular, nodes can (network) boot off it and provision themselves from it with a default image, without requiring a Linux distribution DVD themselves. The network boot and provisioning process for the regular nodes is described in detail in Chapter [5](/admin/provisioning). In brief, provisioning installs an operating system and files on a node. This kind of installation to a regular node differs from a normal Linux installation in several ways. An important difference is that content that is put on the filesystem of the regular node is normally overwritten by provisioning when the regular node reboots. * **Post-installation software installation:** The installation of software to a cluster that is already configured and running BCM is described in detail in Chapter [9](/admin/softwareimagemanagement) of this manual. * **Third-party software installation:** The installation of software that is not developed as part of BCM, but is supported as a part of BCM. This is described in detail in the [*Installation Manual*](/installation/thirdparty). * **[Cloudbursting](/cloudbursting/preface), and [Edge](/edge/preface)**: these are integrated as part of BCM in various ways. These have their own deployment procedures and have separate manuals. ### 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](/admin/clustermanagement#24-base-view-gui)) or shell-based (`cmsh`, section [2.5](/admin/clustermanagement#25-cluster-management-shell)). Other tasks can be handled via special tools provided with BCM, or the usual Linux tools. The use of BCM tools is usually recommended over standard Linux tools because cluster administration often has special issues, including that of scale. The following topics are among those covered in this manual: | **Chapter** | **Title** | **Description** | | :---------------------------------- | :-------------------------------------------------- | :--------------------------------------------------------------------------------------------------- | | [2](/admin/clustermanagement) | Cluster Management With NVIDIA Base Command Manager | Introduction to main concepts and tools of BCM. Lays down groundwork for the remaining chapters | | [3](/admin/configuring) | Configuring The Cluster | Further configuration and set up of the cluster after software installation of BCM on the head node. | | [4](/admin/power) | Power Management | How power management within the cluster works | | [5](/admin/provisioning) | Node Provisioning | Node provisioning in detail | | [6](/admin/usermanagement) | User Management | Account management for users and groups | | [7](/admin/workloadmanagement) | Workload Management | Workload management implementation and use | | [8](/admin/cm-scale) | The `cm-scale` Service | A BCM service to dynamically scale the cluster according to need | | [9](/admin/softwareimagemanagement) | Post-Installation Software Management | Managing, updating, modifying BCM software and images | | [10](/admin/monitoring) | Monitoring: Monitoring Cluster Devices | Device monitoring and conditional action triggers | | [11](/admin/monitoringjob) | Monitoring: Job Monitoring | Jobs resource consumption monitoring by the jobs | | [12](/admin/monitoringaccounting) | Monitoring: Job Accounting | Jobs resource consumption monitoring aggregated by user or similar groupings | | [13](/admin/monitoringchargeback) | Monitoring: Job Chargeback | Resource request monitoring, so that groups of users can be charged for their use | | [14](/admin/administration) | Day-To-Day Administration | Miscellaneous administration | | [15](/admin/ha) | High Availability | Background details and setup instructions to build a cluster with redundant head nodes | | [16](/admin/jupyter) | The Jupyter Notebook Environment Integration | Installing and using the Jupyter notebook environment | The appendices to this manual generally give supplementary details to the main text. The following topics are also logically a part of BCM administration, but they have their own separate manuals. This is because they have, or are eventually expected to have, many features or cover a special set of topics: * Cloudbursting ([*Cloudbursting Manual*](/cloudbursting/preface)) * Edge deployment ([*Edge Manual*](/edge/preface)) * Developer topics ([*Developer Manual*](/developer/preface)) * Containerization topics ([*Containerization Manual*](/containerization/preface)) * NVIDIA Mission Control topics ([*NVIDIA Mission Control Manual*](/nvidia-mission-control/preface)) ## 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 normally interacts with the cluster by logging into a custom Linux user environment to run jobs. Details on running jobs from the perspective of the user are given in the [*User Manual*](/user/preface). * **The NVIDIA Enterprise Support Portal** at [https://enterprise-support.nvidia.com/](https://enterprise-support.nvidia.com/) carries Knowledge Articles that often supplement the *Administrator Manual* with discussion of the following: * Obscure, or complicated, configuration cases * Procedures that are not really within the scope of BCM itself, but that may come up as part of related general Linux configuration. * **Further support options.** If the issue is not described adequately in the manuals, then section [14.2](/admin/administration#142-getting-support-with-bcm-issues-and-notifications-for-release-updates) describes how to get further support.