Choose the offer type
An Integrated System and a Certified Node have different software and support inclusions. Put the chosen type and orderable identity in the BOM.
Nutanix-oriented Integrated Systems and Certified Nodes are different offers.
Price, condition, availability and included options confirmed in the written quotation. The RFQ opens a request draft; it does not submit an order.

HX650 V3 is a hyperconverged product family rather than a generic rack server relabeled as HCI. The commercial and technical distinction between an Integrated System and a Certified Node must remain visible throughout the order.
Start an expansion request from the existing cluster: software version, licensed capacity, node identities and the desired failure tolerance. Match an approved node configuration to that environment instead of assuming any SR650-class server is an equivalent appliance.
Alternative maxima are not necessarily available together. Source links identify the documentation scope—not an inventory guarantee.
| Platform class | 2U ThinkAgile HX650 V3 |
|---|---|
| CPU family | 5th Generation Intel Xeon Scalable in the current product guide |
| Memory architecture | Up to 32 DDR5 DIMMs; model/population constraints apply |
| Integrated System | Validated hardware/firmware with licensed Nutanix software and the documented integrated support scope |
| Certified Node | Validated hardware/firmware; Nutanix software licenses and enhanced software support are not included |
| Cluster constraints | The current guide explicitly excludes two-node clusters for HX650 V3 |
| Storage topology | Storage-heavy, high-performance and SAP HANA variants differ |
An Integrated System and a Certified Node have different software and support inclusions. Put the chosen type and orderable identity in the BOM.
The reviewed guide excludes a two-node HX650 V3 cluster. Do not copy generic HCI sizing advice into this platform’s bill of materials.
Storage-heavy and other variants have distinct bay, controller and GPU limitations. Follow the specific model column rather than the broad base-server maximum.
These are procurement considerations, not an OEM-approved BOM. Final option part numbers and compatibility must be reviewed for the supplied system.

Agree the identity and condition first. Ask for current-unit views, the installed or supplied parts list, relevant test records and photographs of the completed packing.
Define the warranty provider and delivery scope in the quotation. A catalog photo, technical source or process illustration is not evidence that an offered unit has passed inspection.
Build an acceptance checklistNo. The current product guide explicitly excludes the software licenses and enhanced software support.
Not according to the reviewed guide, which excludes two-node HX650 V3 clusters.
These images illustrate a server-workbench environment. They are not verified views of this exact model or the offered unit; use the product specifications and shipment-specific photographs for identification.
Only server scenes use background monitors. The four screen styles follow the supplied visual references with heavy defocus. Exact chassis, drive layout, included options and test status must be confirmed separately. Read the image standard →
Attach a photo brief to the request for Lenovo ThinkAgile HX650 V3. This is a checklist to agree, not a record that inspection has already been performed.
Request a straight-on view with the bezel removed when appropriate. Record the populated bays, blanking panels and drive carriers against the offered chassis configuration.
Ask for both PSU labels, risers, network adapters and the rail kit. Confirm which visible parts are included in the offer rather than assuming the catalog picture defines the BOM.
Use an order-specific report for installed CPUs, DIMMs, storage and management access. A blurred background screen in an illustration is not a diagnostic result.
Check the current document revision before approving a configuration. Sources may cover a platform family or a selected machine type; the scope is recorded below.
Integrated System vs Certified Node; model-specific storage; licensing; cluster-size footnote
Reviewed 2026-09-09 · official HTML document reviewedKeep the media, backplane, controller and boot path in one specification.
Read the guideSpecify ports, software, support and deployment rights without hiding them inside a model name.
Read the guideTurn a condition label into a documented, agreed acceptance scope.
Read the guideShared requirements do not imply drop-in hardware compatibility.
Intel Xeon 6 compute with configuration-dependent memory and storage.
Expansion and pre-owned sourcing with a clearly stated lifecycle.
Installed-base workstation sourcing with machine-type-level checks.