> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/rms/llms.txt.

# RackManagerV2 types


Messages and enums in the `rack_manager_v2` protobuf package. Proto3 has no required fields, so a field that an RPC needs says so in its description. Refer to [Conventions](/rms/api-reference/conventions#node-identity) for how nodes are described.

## Messages

### ConfigureScaleUpFabricManagerRequest

ConfigureScaleUpFabricManagerRequest declaratively describes the desired scale-up fabric across a set of switches. RMS reconciles the switches toward this desired state, applying only the changes that are required (for example, it does nothing when the observed configuration matches this request and controller activation is verified). Direct switch requests use each node's host_endpoint for address and credentials.

| Field | Type | Description |
| --- | --- | --- |
| `nodes` | [`NodeSet`](/rms/api-reference/types/rack-manager#nodeset) | Without layout, RMS validates all nodes and configures only switches; other recognized node types are ignored. With layout, include every physical switch, even switches outside the requested fabrics, and compute trays for selection. At least one switch is required, and node IDs must be nonempty and unique. RMS uses NodeInfo.type when set to a value other than NODE_TYPE_UNSPECIFIED. Otherwise, RMS uses node_descriptor to identify the node's role. Every node must resolve to a supported type. With layout, only switch and compute nodes are accepted. The order of nodes does not determine which fabric they belong to. Each switch needs host_endpoint and credentials. With layout, each compute entry represents one tray and needs bmc_endpoint and credentials for reading its position. RMS reads compute BMCs for layout discovery; it does not configure compute hosts. Compute entries are required unless layout requests one fabric covering the full physical compute and switch capacity. For that layout, either omit all compute entries or include every compute tray. Omission avoids compute BMC reads. For other layouts, compute trays outside the requested fabrics may be omitted. |
| `primary_switch_node_id` | optional `string` | ID of the switch node that should run the fabric manager (the primary host). If absent, RMS selects the switch at the lowest position in the rack. |
| `domain` | optional `string` | Selects the CA and RMS client credentials for all switches in this request. If omitted, RMS uses --default-switch-domain. TLS server-name verification uses each endpoint's identity or the configured DNS override, not this value. |
| `config` | [`ScaleUpFabricConfig`](/rms/api-reference/types/rack-manager-v2#scaleupfabricconfig) | Desired scale-up fabric configuration to reconcile the switches toward. With layout, caller settings are shared by selected fabrics; managed static values can differ by fabric size. |
| `layout` | [`ScaleUpFabricLayout`](/rms/api-reference/types/rack-manager-v2#scaleupfabriclayout) | Optional arrangement of independent fabrics within the supplied inventory; fabric sizes may differ from the complete physical topology. Supply the complete desired fabric set in one call to coordinate shared links. Requires config and at least one fabric; primary_switch_node_id must be absent. One fabric matching the complete physical compute and switch capacity restores full connectivity and one controller cluster. Other layouts isolate unused capacity. When absent, one cluster is configured without changing managed link settings. |

### ConfigureScaleUpFabricManagerResponse

ConfigureScaleUpFabricManagerResponse returns the handle to the reconciliation job.

| Field | Type | Description |
| --- | --- | --- |
| `job_id` | `string` | ID of the asynchronous job that reconciles the scale-up fabric. Poll it via rack_manager.GetJobStatus. Read live fabric members and component status via rack_manager.InspectScaleUpFabrics. Successful no-layout jobs also return JSON-encoded rack_manager.ScaleUpFabricStatus in result_json. |
| `selected_fabrics` | repeated [`ScaleUpFabricMembers`](/rms/api-reference/types/rack-manager-v2#scaleupfabricmembers) | Empty without layout. With layout, identifies the nodes and primary selected for each requested fabric, in request order. Selection does not indicate that configuration has completed; use job_id to track execution. |

### NodeSystemValidationJobInfo

NodeSystemValidationJobInfo pairs a node with its async system validation job ID.

| Field | Type | Description |
| --- | --- | --- |
| `node_id` | `string` | Node identifier, as supplied in the request |
| `job_id` | `string` | System validation job ID returned for this node |

### ScaleUpFabricConfig

ScaleUpFabricConfig captures the desired scale-up fabric configuration in logical terms, so RMS can apply it regardless of which switch API it uses to configure the fabric manager.

| Field | Type | Description |
| --- | --- | --- |
| `topology_type` | `string` | Topology to be configured for the scale-up fabric (applied to the fabric manager). |
| `extra_static_configs` | repeated [`ScaleUpFabricStaticConfig`](/rms/api-reference/types/rack-manager#scaleupfabricstaticconfig) | Additional static configuration entries to apply to the fabric manager. This is a generic pass-through for any configuration not modeled by a dedicated field above; RMS applies each entry via the fabric manager's static-config API. Each (config_file_name, key) must be unique; duplicate keys are rejected. With layout, RMS supplies required static settings for each fabric size. Matching caller values are accepted; conflicts with required settings or removals are rejected. Omitted unmanaged keys remain unchanged. Without layout, all omitted static settings remain unchanged. |

### ScaleUpFabricLayout

Describes the fabrics to create from the nodes in the request. Supported sizes and placements depend on the server and physical topology. Physical positions are discovered from the supplied nodes, not specified by offsets.

| Field | Type | Description |
| --- | --- | --- |
| `fabrics` | repeated [`ScaleUpFabricSpec`](/rms/api-reference/types/rack-manager-v2#scaleupfabricspec) | Complete desired fabric set for the supplied inventory. Unresolved positions, ambiguous topology, or unsupported layouts fail admission. Selected node groups must not overlap. Unassigned capacity is isolated and controllers on unassigned switches are disabled. Results follow this list's order; node selection uses physical positions. |

### ScaleUpFabricMembers

Nodes and primary selected for one requested fabric, not observed configuration.

| Field | Type | Description |
| --- | --- | --- |
| `compute_node_ids` | repeated `string` | Selected compute tray IDs; empty when full-topology compute inventory is omitted. |
| `switch_node_ids` | repeated `string` | Selected switch tray IDs from the request's switch inventory. |
| `primary_switch_node_id` | `string` | Selected primary switch ID, which belongs to switch_node_ids. |

### ScaleUpFabricSpec

Target size of one independently managed fabric. RMS selects nonoverlapping node groups. The same inventory and layout produce the same selection; changing either may change the selected nodes.

| Field | Type | Description |
| --- | --- | --- |
| `compute_tray_count` | `uint32` | Positive total number of physical compute trays in this fabric. The requested size and placement must be supported by the server. |
| `switch_tray_count` | `uint32` | Positive total number of physical switch trays in this fabric. |
| `primary_switch_node_id` | optional `string` | Optional primary preference. The selected fabric must include this switch as primary. If absent, a primary is selected deterministically from this fabric's switches. |

### StartSystemValidationRequest

StartSystemValidationRequest identifies the nodes to scan. NVSSVT reaches each Device Under Test (DUT) over its BMC (required) and, when supplied, its host OS, so every node's bmc_endpoint must carry credentials.

| Field | Type | Description |
| --- | --- | --- |
| `nodes` | [`NodeSet`](/rms/api-reference/types/rack-manager#nodeset) | - |
| `config_override` | `string` | Passed through to NVSSVT as --config-override for every node's scan. Left unset, NVSSVT applies its own configuration defaults. RMS does not interpret or validate this value; NVSSVT rejects it if malformed. |

### StartSystemValidationResponse

StartSystemValidationResponse reports the launched scans' job handles, one per admitted node. The NVSSVT process id and log directory live on the launcher's side of the pod and are not addressable by callers, so they are reported in RMS's logs rather than here; each scan's log directory also appears in its job's result_json once it completes.

| Field | Type | Description |
| --- | --- | --- |
| `response` | [`NodeBatchResponse`](/rms/api-reference/types/rack-manager#nodebatchresponse) | response.job_id is the parent job ID for GetJobStatus |
| `jobs` | repeated [`NodeSystemValidationJobInfo`](/rms/api-reference/types/rack-manager-v2#nodesystemvalidationjobinfo) | Individual scan job ID per node |