Top
Abstract
The ThinkSystem Kioxia CM6-R Entry NVMe PCIe 4.0 x4 solid-state drives (SSDs) are high-performance self-encrypting drives (SEDs) that adhere to the Trusted Computing Group Opal/Ruby Security Subsystem Class cryptographic standards (TCG Opal/Ruby SSC). They use Kioxia NAND flash memory technology with a PCIe 4.0 x4 NVMe interface to provide an high-performance solution for secure read-intensive workloads.
This product guide provides essential presales information to understand the CM6-R NVMe SED offerings, their key features and specifications, components and options, and configuration guidelines. This guide is intended for technical specialists, sales specialists, sales engineers, IT architects, and other IT professionals who want to learn more about the SSDs and consider their use in IT solutions.
Withdrawn from marketing: The drives described in this product guide are withdrawn from marketing.
Change History
Changes in the July 31, 2023 update:
- The drives described in this product guide are withdrawn from marketing.
Introduction
The ThinkSystem Kioxia CM6-R Entry NVMe PCIe 4.0 x4 solid-state drives (SSDs) are high-performance self-encrypting drives (SEDs) that adhere to the Trusted Computing Group Opal/Ruby Security Subsystem Class cryptographic standards (TCG Opal/Ruby SSC). They use Kioxia NAND flash memory technology with a PCIe 4.0 x4 NVMe interface to provide an high-performance solution for secure read-intensive workloads.
Figure 1. ThinkSystem Kioxia CM6-R Entry NVMe PCIe 4.0 x4 SED SSD
Did you know?
Self-encrypting drives (SEDs) provide benefits by encrypting data on-the-fly at the drive level with no performance impact, by providing instant secure erasure thereby making the data no longer readable, and by enabling auto-locking to secure active data if a drive is misplaced or stolen from a system while in use. These features are essential for many businesses, especially those storing customer data.
The Kioxia CM6 drives have a PCIe 4.0 (Gen 4) host interface, where sequential performance is doubled over the PCIe 3.0 host interface. The drives are also fully compatible with a PCIe 3.0 host interface providing optimal performance and enabling compatibility across server families.
NVMe (Non-Volatile Memory Express) is a technology that overcomes SAS/SATA SSD performance limitations by optimizing hardware and software to take full advantage of flash technology. The use of NVMe drives means data is transferred more efficiently from the processor to the drives compared to the legacy Advance Host Controller Interface (AHCI) stack, thereby reducing latency and overhead. These SSDs connect directly to the processor via the PCIe bus, further reducing latency and TCO.
Part number information
The following table lists the part numbers and feature codes for ThinkSystem servers.
Withdrawn from marketing: The drives described in this product guide are withdrawn from marketing.
| Part number |
Feature code |
Description |
|---|---|---|
| 2.5-inch drives | ||
| 4XB7A38269 | BE2C | ThinkSystem U.3 Kioxia CM6-R 3.84TB Entry NVMe PCIe 4.0 x4 Hot Swap SSD SED |
| 4XB7A38270 | BE2D | ThinkSystem U.3 Kioxia CM6-R 7.68TB Entry NVMe PCIe 4.0 x4 Hot Swap SSD SED |
The part numbers include the following items:
- One 2.5-inch solid-state drive installed in a hot-swap tray
- Documentation
Features
Non-Volatile Memory Express (NVMe) is PCIe high performance SSD technology that provides high I/O throughput and low latency. NVMe interfaces remove SAS/SATA bottlenecks and unleash all of the capabilities of contemporary NAND flash memory. Each NVMe PCI SSD has direct PCIe x4 connection, which provides at significantly greater bandwidth and lower latency than SATA/SAS-based SSD solutions. NVMe drives are also optimized for heavy multi-threaded workloads by using internal parallelism and many other improvements, such as enlarged I/O queues.
The ThinkSystem Kioxia CM6-R Entry NVMe SSDs have the following features:
- Based on the Kioxia KCM61RUL drives (formerly Toshiba)
- 2.5-inch NVMe (U.3, which is backward compatible with U.2) hot-swap drive tray
- Compliant with TCG Opal and TCG Ruby specifications:
- TCG Storage Security Subsystem Class: Opal Version 2.01 Revision 1.00
- TCG Storage Security Subsystem Class: Ruby Version 1.00 Revision 1.00
- Supports Sanitize Cryptographic Erase
- 96-layer BiCS FLASH 3D TLC memory
- 1 drive-write-per-day (DWPD) SSD for read-intensive workloads
- PCIe 4.0 x4 host connection for each NVMe drive, resulting in up to 6.9 GBps overall throughput.
- Full Power-Loss-Protection and End-to-End Data Protection
- Low power consumption (maximum 20 W)
The TBW value assigned to a solid-state device is the total bytes of written data (based on the number of P/E cycles) that a drive can be guaranteed to complete (% of remaining P/E cycles = % of remaining TBW). Reaching this limit does not cause the drive to immediately fail. It simply denotes the maximum number of writes that can be guaranteed. A solid-state device will not fail upon reaching the specified TBW. At some point based on manufacturing variance margin, after surpassing the TBW value, the drive will reach the end-of-life point, at which the drive will go into a read-only mode.
Because of such behavior, careful planning must be done to use SSDs in the application environments to ensure that the TBW of the drive is not exceeded before the required life expectancy.
For example, the 3.84TB drive has an endurance of 7,008 TB of total bytes written (TBW). This means that for full operation over five years, write workload must be limited to no more than 3,840 GB of writes per day, which is equivalent to 1.0 full drive writes per day (DWPD). For the device to last three years, the drive write workload must be limited to no more than 6,400 GB of writes per day, which is equivalent to 1.7 full drive writes per day.
The benefits of drive encryption
Self-encrypting drives (SEDs) provide benefits in three main ways:
- By encrypting data on-the-fly at the drive level with no performance impact
- By providing instant secure erasure (cryptographic erasure, thereby making the data no longer readable)
- By enabling auto-locking to secure active data if a drive is misplaced or stolen from a system while in use
The following sections describe the benefits in more details.
Automatic encryption
It is vital that a company keep its data secure. With the threat of data loss due to physical theft or improper inventory practices, it is important that the data be encrypted. However, challenges with performance, scalability, and complexity have led IT departments to push back against security policies that require the use of encryption. In addition, encryption has been viewed as risky by those unfamiliar with key management, a process for ensuring a company can always decrypt its own data. Self-encrypting drives comprehensively resolve these issues, making encryption both easy and affordable.
When the self-encrypting drive is in normal use, its owner need not maintain authentication keys (otherwise known as credentials or passwords) in order to access the data on the drive. The self-encrypting drive will encrypt data being written to the drive and decrypt data being read from it, all without requiring an authentication key from the owner.
Drive retirement and disposal
When hard drives are retired and moved outside the physically protected data center into the hands of others, the data on those drives is put at significant risk. IT departments retire drives for a variety of reasons, including:
- Returning drives for warranty, repair, or expired lease agreements
- Removal and disposal of drives
- Repurposing drives for other storage duties
Nearly all drives eventually leave the data center and their owner's control. Corporate data resides on such drives, and when most leave the data center, the data they contain is still readable. Even data that has been striped across many drives in a RAID array is vulnerable to data theft because just a typical single stripe in today’s high-capacity arrays is large enough to expose for example, hundreds of names and bank account numbers.
In an effort to avoid data breaches and the ensuing customer notifications required by data privacy laws, companies use different methods to erase the data on retired drives before they leave the premises and potentially fall into the wrong hands. Current retirement practices that are designed to make data unreadable rely on significant human involvement in the process, and are thus subject to both technical and human failure.
The drawbacks of today’s drive retirement practices include the following:
- Overwriting drive data is expensive, tying up valuable system resources for days. No notification of completion is generated by the drive, and overwriting won’t cover reallocated sectors, leaving that data exposed.
- Methods that include degaussing or physically shredding a drive are expensive. It is difficult to ensure the degauss strength is optimized for the drive type, potentially leaving readable data on the drive. Physically shredding the drive is environmentally hazardous, and neither practice allows the drive to be returned for warranty or expired lease.
- Some companies have concluded the only way to securely retire drives is to keep them in their control, storing them indefinitely in warehouses. But this is not truly secure because a large volume of drives coupled with human involvement inevitably leads to some drives being lost or stolen.
- Professional disposal services is an expensive option and includes the cost of reconciling the services as well as internal reports and auditing. Transporting of the drives also has the potential of putting the data at risk.
Self-encrypting drives eliminate the need to overwrite, destroy, or store retired drives. When the drive is to be retired, it can be cryptographically erased, a process that is nearly instantaneous regardless of the capacity of the drive.
Instant secure erase
The self-encrypting drive provides instant data encryption key destruction via cryptographic erasure. When it is time to retire or repurpose the drive, the owner sends a command to the drive to perform a cryptographic erasure. Cryptographic erasure simply replaces the encryption key inside the encrypted drive, making it impossible to ever decrypt the data encrypted with the deleted key.
Self-encrypting drives reduce IT operating expenses by reducing asset control challenges and disposal costs. Data security with self-encrypting drives helps ensure compliance with privacy regulations without hindering IT efficiency. So called "Safe Harbor" clauses in government regulations allow companies to not have to notify customers of occurrences of data theft if that data was encrypted and therefore unreadable.
Furthermore, self-encrypting drives simplify decommissioning and preserve hardware value for returns and repurposing by:
- Eliminating the need to overwrite or destroy the drive
- Securing warranty returns and expired lease returns
- Enabling drives to be repurposed securely
Auto-locking
Insider theft or misplacement is a growing concern for businesses of all sizes; in addition, managers of branch offices and small businesses without strong physical security face greater vulnerability to external theft. Self-encrypting drives include a feature called auto-lock mode to help secure active data against theft.
Using a self-encrypting drive when auto-lock mode is enabled simply requires securing the drive with an authentication key. When secured in this manner, the drive’s data encryption key is locked whenever the drive is powered down. In other words, the moment the self-encrypting drive is switched off or unplugged, it automatically locks down the drive’s data.
When the self-encrypting drive is then powered back on, it requires authentication before being able to unlock its encryption key and read any data on the drive, thus protecting against misplacement and theft.
While using self-encrypting drives just for the instant secure erase is an extremely efficient and effective means to help securely retire a drive, using self-encrypting drives in auto-lock mode provides even more advantages. From the moment the drive or system is removed from the data center (with or without authorization), the drive is locked. No advance thought or action is required from the data center administrator to protect the data. This helps prevent a breach should the drive be mishandled and helps secure the data against the threat of insider or outside theft.
Technical specifications
The following table presents technical specifications for the ThinkSystem Kioxia CM6-R Entry NVMe SSDs.
| Feature | 3.84 TB drive | 7.68 TB drive |
|---|---|---|
| Host interface | PCIe 4.0 x4 | PCIe 4.0 x4 |
| Capacity | 3.84 TB | 7.68 TB |
| SED encryption | TCG Opal | TCG Opal |
| Endurance (total bytes written) | 7,008 TB | 14,016 TB |
| Endurance (drive writes per day for 5 years) | 1.0 DWPD | 1.0 DWPD |
| Data reliability (UBER) | < 1 in 1017 bits read | < 1 in 1017 bits read |
| MTBF | 2,500,000 hours | 2,500,000 hours |
| IOPS reads (4 KB blocks, PCIe 4.0) | 1,400,000 | 1,400,000 |
| IOPS writes (4 KB blocks, PCIe 4.0) | 170,000 | 170,000 |
| Sequential read rate (128 KB blocks, PCIe 4.0) | 6900 MBps | 6900 MBps |
| Sequential write rate (128 KB blocks, PCIe 4.0) | 4200 MBps | 4000 MBps |
| Latency (random read) | 90 µs | 90 µs |
| Latency (random write) | 20 µs | 20 µs |
| Maximum power | 19 W | 20 W |
Server support
The following tables list the ThinkSystem servers that are compatible.
| Part Number | Description | AMD V3 | 2S Intel V3/V4 | 4S 8S Intel V3 | Multi Node V3/V4 | GPU Rich | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SR635 V3 (7D9H / 7D9G) |
SR655 V3 (7D9F / 7D9E) |
SR645 V3 (7D9D / 7D9C) |
SR665 V3 (7D9B / 7D9A) |
ST650 V3 (7D7B / 7D7A) |
SR630 V3 (7D72 / 7D73) |
SR650 V3 (7D75 / 7D76) |
SR630 V4 (7DG8 / 7DG9) |
SR850 V3 (7D97 / 7D96) |
SR860 V3 (7D94 / 7D93) |
SR950 V3 (7DC5 / 7DC4) |
SD535 V3 (7DD8 / 7DD1) |
SD530 V3 (7DDA / 7DD3) |
SD550 V3 (7DD9 / 7DD2) |
SD520 V4 (7DFZ / 7DFY) |
SR670 V2 (7Z22 / 7Z23) |
SR675 V3 (7D9Q / 7D9R) |
SR680a V3 (7DHE) |
SR685a V3 (7DHC) |
SR780a V3 (7DJ5) |
||
| 4XB7A38269 | ThinkSystem U.3 Kioxia CM6-R 3.84TB Entry NVMe PCIe 4.0 x4 Hot Swap SSD SED | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N |
| 4XB7A38270 | ThinkSystem U.3 Kioxia CM6-R 7.68TB Entry NVMe PCIe 4.0 x4 Hot Swap SSD SED | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N |
| Part Number | Description | 1S V3 | Edge | Super Computing | 1S Intel V2 | 2S Intel V2 | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ST50 V3 (7DF4 / 7DF3) |
ST250 V3 (7DCF / 7DCE) |
SR250 V3 (7DCM / 7DCL) |
SE350 (7Z46 / 7D1X) |
SE350 V2 (7DA9) |
SE360 V2 (7DAM) |
SE450 (7D8T) |
SE455 V3 (7DBY) |
SC750 V4 (7DDJ) |
SD665 V3 (7D9P) |
SD665-N V3 (7DAZ) |
SD650 V3 (7D7M) |
SD650-I V3 (7D7L) |
SD650-N V3 (7D7N) |
ST50 V2 (7D8K / 7D8J) |
ST250 V2 (7D8G / 7D8F) |
SR250 V2 (7D7R / 7D7Q) |
ST650 V2 (7Z75 / 7Z74) |
SR630 V2 (7Z70 / 7Z71) |
SR650 V2 (7Z72 / 7Z73) |
||
| 4XB7A38269 | ThinkSystem U.3 Kioxia CM6-R 3.84TB Entry NVMe PCIe 4.0 x4 Hot Swap SSD SED | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | Y | Y |
| 4XB7A38270 | ThinkSystem U.3 Kioxia CM6-R 7.68TB Entry NVMe PCIe 4.0 x4 Hot Swap SSD SED | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N | Y | Y |
| Part Number | Description | AMD V1 | Dense V2 | 4S V2 | 8S | 4S V1 | 1S Intel V1 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SR635 (7Y98 / 7Y99) |
SR655 (7Y00 / 7Z01) |
SR655 Client OS |
SR645 (7D2Y / 7D2X) |
SR665 (7D2W / 7D2V) |
SD630 V2 (7D1K) |
SD650 V2 (7D1M) |
SD650-N V2 (7D1N) |
SN550 V2 (7Z69) |
SR850 V2 (7D31 / 7D32) |
SR860 V2 (7Z59 / 7Z60) |
SR950 (7X11 / 7X12) |
SR850 (7X18 / 7X19) |
SR850P (7D2F / 2D2G) |
SR860 (7X69 / 7X70) |
ST50 (7Y48 / 7Y50) |
ST250 (7Y45 / 7Y46) |
SR150 (7Y54) |
SR250 (7Y52 / 7Y51) |
||
| 4XB7A38269 | ThinkSystem U.3 Kioxia CM6-R 3.84TB Entry NVMe PCIe 4.0 x4 Hot Swap SSD SED | N | N | N | Y | Y | N | N | N | N | N | N | N | N | N | N | N | N | N | N |
| 4XB7A38270 | ThinkSystem U.3 Kioxia CM6-R 7.68TB Entry NVMe PCIe 4.0 x4 Hot Swap SSD SED | N | N | N | Y | Y | N | N | N | N | N | N | N | N | N | N | N | N | N | N |
| Part Number | Description | 2S Intel V1 | Dense V1 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ST550 (7X09 / 7X10) |
SR530 (7X07 / 7X08) |
SR550 (7X03 / 7X04) |
SR570 (7Y02 / 7Y03) |
SR590 (7X98 / 7X99) |
SR630 (7X01 / 7X02) |
SR650 (7X05 / 7X06) |
SR670 (7Y36 / 7Y37) |
SD530 (7X21) |
SD650 (7X58) |
SN550 (7X16) |
SN850 (7X15) |
||
| 4XB7A38269 | ThinkSystem U.3 Kioxia CM6-R 3.84TB Entry NVMe PCIe 4.0 x4 Hot Swap SSD SED | N | N | N | N | N | Y | Y | N | N | N | N | N |
| 4XB7A38270 | ThinkSystem U.3 Kioxia CM6-R 7.68TB Entry NVMe PCIe 4.0 x4 Hot Swap SSD SED | N | N | N | N | N | Y | Y | N | N | N | N | N |
Storage controller support
NVMe PCIe SSDs require a NVMe drive backplane and some form of PCIe connection to processors. PCIe connections can take the form of either an adapter (PCIe Interposer or PCIe extender/switch adapter) or simply a cable that connects to an onboard NVMe connector.
PCIe 3.0 support: The Kioxia CM6-R drives offer a PCIe 4.0 host interface, however they are backward compatible with a PCIe 3.0 host interface. Note however that servers with a PCIe 3.0 host interface will not see the same performance levels (especially sequential read and write rates). ThinkSystem NVMe switch adapters also provide a PCIe 3.0 host interface to attached drives.
Consult the relevant server product guide for details about required components for NVMe drive support.
Operating system support
The following table lists the supported operating systems.
Tip: This table is automatically generated based on data from Lenovo ServerProven.
| Operating systems | SR630 V2 |
SR650 V2 |
SR645 |
SR665 |
SR630 (Xeon Gen 2) |
SR650 (Xeon Gen 2) |
SR630 (Xeon Gen 1) |
SR650 (Xeon Gen 1) |
|---|---|---|---|---|---|---|---|---|
| Microsoft Windows Server 2016 | Y | Y | Y | Y | Y | Y | Y | Y |
| Microsoft Windows Server 2019 | Y | Y | Y | Y | Y | Y | Y | Y |
| Microsoft Windows Server 2022 | Y | Y | Y | Y | Y | Y | Y | Y |
| Microsoft Windows Server 2025 | Y | Y | Y | Y | N | N | N | N |
| Red Hat Enterprise Linux 6.10 | N | N | N | N | N | N | Y | Y |
| Red Hat Enterprise Linux 6.9 | N | N | N | N | N | N | Y | Y |
| Red Hat Enterprise Linux 7.3 | N | N | N | N | N | N | Y | Y |
| Red Hat Enterprise Linux 7.4 | N | N | N | N | N | N | Y | Y |
| Red Hat Enterprise Linux 7.5 | N | N | N | N | N | N | Y | Y |
| Red Hat Enterprise Linux 7.6 | N | N | Y 1 | Y 1 | Y | Y | Y | Y |
| Red Hat Enterprise Linux 7.7 | N | N | Y 1 | Y 1 | Y | Y | Y | Y |
| Red Hat Enterprise Linux 7.8 | N | N | Y 1 | Y 1 | Y | Y | Y | Y |
| Red Hat Enterprise Linux 7.9 | Y | Y | Y 1 | Y 1 | Y | Y | Y | Y |
| Red Hat Enterprise Linux 8.0 | N | N | N | N | Y | Y | Y | Y |
| Red Hat Enterprise Linux 8.1 | N | N | Y 1 | Y 1 | Y | Y | Y | Y |
| Red Hat Enterprise Linux 8.10 | Y | Y | Y | Y | N | N | N | N |
| Red Hat Enterprise Linux 8.2 | Y | Y | Y 1 | Y 1 | Y | Y | Y | Y |
| Red Hat Enterprise Linux 8.3 | Y | Y | Y | Y | Y | Y | Y | Y |
| Red Hat Enterprise Linux 8.4 | Y | Y | Y | Y | Y | Y | Y | Y |
| Red Hat Enterprise Linux 8.5 | Y | Y | Y | Y | Y | Y | Y | Y |
| Red Hat Enterprise Linux 8.6 | Y | Y | Y | Y | Y | Y | Y | Y |
| Red Hat Enterprise Linux 8.7 | Y | Y | Y | Y | Y | Y | Y | Y |
| Red Hat Enterprise Linux 8.8 | Y | Y | Y | Y | Y | Y | Y | Y |
| Red Hat Enterprise Linux 8.9 | Y | Y | Y | Y | Y | Y | N | N |
| Red Hat Enterprise Linux 9.0 | Y | Y | Y | Y | Y | Y | Y | Y |
| Red Hat Enterprise Linux 9.1 | Y | Y | Y | Y | Y | Y | Y | Y |
| Red Hat Enterprise Linux 9.2 | Y | Y | Y | Y | Y | Y | Y | Y |
| Red Hat Enterprise Linux 9.3 | Y | Y | Y | Y | Y | Y | N | N |
| Red Hat Enterprise Linux 9.4 | Y | Y | Y | Y | N | N | N | N |
| Red Hat Enterprise Linux 9.5 | Y | Y | Y | Y | N | N | N | N |
| SUSE Linux Enterprise Server 11 SP4 | N | N | N | N | N | N | Y | Y |
| SUSE Linux Enterprise Server 11 SP4 with Xen | N | N | N | N | N | N | Y | Y |
| SUSE Linux Enterprise Server 12 SP2 | N | N | N | N | N | N | Y | Y |
| SUSE Linux Enterprise Server 12 SP2 with Xen | N | N | N | N | N | N | Y | Y |
| SUSE Linux Enterprise Server 12 SP3 | N | N | N | N | N | N | Y | Y |
| SUSE Linux Enterprise Server 12 SP3 with Xen | N | N | N | N | N | N | Y | Y |
| SUSE Linux Enterprise Server 12 SP4 | N | N | N | N | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 12 SP4 with Xen | N | N | N | N | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 12 SP5 | Y | Y | Y | Y | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 12 SP5 with Xen | Y | Y | Y | Y | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 15 | N | N | N | N | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 15 SP1 | N | N | Y 1 | Y 1 | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 15 SP1 with Xen | N | N | Y 1 | Y 1 | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 15 SP2 | Y | Y | Y | Y | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 15 SP2 with Xen | Y | Y | Y | Y | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 15 SP3 | Y | Y | Y | Y | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 15 SP3 with Xen | Y | Y | Y | Y | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 15 SP4 | Y | Y | Y | Y | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 15 SP4 with Xen | Y | Y | Y | Y | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 15 SP5 | Y | Y | Y | Y | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 15 SP5 with Xen | Y | Y | Y | Y | Y | Y | Y | Y |
| SUSE Linux Enterprise Server 15 SP6 | Y | Y | Y | Y | N | N | N | N |
| SUSE Linux Enterprise Server 15 with Xen | N | N | N | N | Y | Y | Y | Y |
| Ubuntu 18.04.5 LTS | Y | Y | N | N | N | N | N | N |
| Ubuntu 20.04 LTS | Y | Y | N | N | N | N | N | N |
| Ubuntu 22.04 LTS | Y | Y | Y | Y | Y | Y | Y | Y |
| Ubuntu 24.04 LTS | Y | Y | Y | Y | N | N | N | N |
| VMware vSphere Hypervisor (ESXi) 6.7 U3 | Y | Y | N | N | N | N | N | N |
| VMware vSphere Hypervisor (ESXi) 7.0 U2 | Y | Y | N | N | N | N | N | N |
| VMware vSphere Hypervisor (ESXi) 7.0 U3 | Y | Y | Y | Y | Y | Y | Y | Y |
| VMware vSphere Hypervisor (ESXi) 8.0 | Y | Y | Y | Y | Y | Y | Y | Y |
| VMware vSphere Hypervisor (ESXi) 8.0 U1 | Y | Y | Y | Y | Y | Y | Y | Y |
| VMware vSphere Hypervisor (ESXi) 8.0 U2 | Y | Y | Y | Y | Y | Y | Y | Y |
| VMware vSphere Hypervisor (ESXi) 8.0 U3 | Y | Y | Y | Y | N | N | N | N |
1 The OS is not supported with EPYC 7003 processors.
IBM SKLM Key Management support
To effectively manage a large deployment of SEDs in Lenovo servers, IBM Security Key Lifecycle Manager (SKLM) offers a centralized key management solution. Certain Lenovo servers support Features on Demand (FoD) license upgrades that enable SKLM support.
The following table lists the part numbers and feature codes to enable SKLM support in the management processor of the server.
| Part number | Feature code | Description |
|---|---|---|
| Security Key Lifecycle Manager - FoD (United States, Canada, Asia Pacific, and Japan) | ||
| 00D9998 | A5U1 | SKLM for System x/ThinkSystem w/SEDs - FoD per Install w/1Yr S&S |
| 00D9999 | AS6C | SKLM for System x/ThinkSystem w/SEDs - FoD per Install w/3Yr S&S |
| Security Key Lifecycle Manager - FoD (Latin America, Europe, Middle East, and Africa) | ||
| 00FP648 | A5U1 | SKLM for System x/ThinkSystem w/SEDs - FoD per Install w/1Yr S&S |
| 00FP649 | AS6C | SKLM for System x/ThinkSystem w/SEDs - FoD per Install w/3Yr S&S |
The IBM Security Key Lifecycle Manager software is available from Lenovo using the ordering information listed in the following table.
| Part number | Description |
|---|---|
| 7S0A007FWW | IBM Security Key Lifecycle Manager Basic Edition Install License + SW Subscription & Support 12 Months |
| 7S0A007HWW | IBM Security Key Lifecycle Manager For Raw Decimal Terabyte Storage Resource Value Unit License + SW Subscription & Support 12 Months |
| 7S0A007KWW | IBM Security Key Lifecycle Manager For Raw Decimal Petabyte Storage Resource Value Unit License + SW Subscription & Support 12 Months |
| 7S0A007MWW | IBM Security Key Lifecycle Manager For Usable Decimal Terabyte Storage Resource Value Unit License + SW Subscription & Support 12 Months |
| 7S0A007PWW | IBM Security Key Lifecycle Manager For Usable Decimal Petabyte Storage Resource Value Unit License + SW Subscription & Support 12 Months |
The following tables list the ThinkSystem servers that are compatible.
| Part Number | Description | AMD V3 | 2S Intel V3/V4 | 4S 8S Intel V3 | Multi Node V3/V4 | GPU Rich | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SR635 V3 (7D9H / 7D9G) |
SR655 V3 (7D9F / 7D9E) |
SR645 V3 (7D9D / 7D9C) |
SR665 V3 (7D9B / 7D9A) |
ST650 V3 (7D7B / 7D7A) |
SR630 V3 (7D72 / 7D73) |
SR650 V3 (7D75 / 7D76) |
SR630 V4 (7DG8 / 7DG9) |
SR850 V3 (7D97 / 7D96) |
SR860 V3 (7D94 / 7D93) |
SR950 V3 (7DC5 / 7DC4) |
SD535 V3 (7DD8 / 7DD1) |
SD530 V3 (7DDA / 7DD3) |
SD550 V3 (7DD9 / 7DD2) |
SD520 V4 (7DFZ / 7DFY) |
SR670 V2 (7Z22 / 7Z23) |
SR675 V3 (7D9Q / 7D9R) |
SR680a V3 (7DHE) |
SR685a V3 (7DHC) |
SR780a V3 (7DJ5) |
||
| A5U1 | SKLM for System x w/SEDs - FoD per Install w/1Yr S&S | N | N | N | N | Y | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N |
| AS6C | SKLM for System x w/SEDs - FoD per Install w/3Yr S&S | N | N | N | N | Y | N | N | N | N | N | N | N | N | N | N | N | N | N | N | N |
| Part Number | Description | 1S V3 | Edge | Super Computing | 1S Intel V2 | 2S Intel V2 | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ST50 V3 (7DF4 / 7DF3) |
ST250 V3 (7DCF / 7DCE) |
SR250 V3 (7DCM / 7DCL) |
SE350 (7Z46 / 7D1X) |
SE350 V2 (7DA9) |
SE360 V2 (7DAM) |
SE450 (7D8T) |
SE455 V3 (7DBY) |
SC750 V4 (7DDJ) |
SD665 V3 (7D9P) |
SD665-N V3 (7DAZ) |
SD650 V3 (7D7M) |
SD650-I V3 (7D7L) |
SD650-N V3 (7D7N) |
ST50 V2 (7D8K / 7D8J) |
ST250 V2 (7D8G / 7D8F) |
SR250 V2 (7D7R / 7D7Q) |
ST650 V2 (7Z75 / 7Z74) |
SR630 V2 (7Z70 / 7Z71) |
SR650 V2 (7Z72 / 7Z73) |
||
| A5U1 | SKLM for System x w/SEDs - FoD per Install w/1Yr S&S | N | Y | Y | N | N | N | N | N | N | N | N | N | N | N | N | Y | Y | N | Y | Y |
| AS6C | SKLM for System x w/SEDs - FoD per Install w/3Yr S&S | N | Y | Y | N | N | N | N | N | N | N | N | N | N | N | N | Y | Y | N | Y | Y |
| Part Number | Description | AMD V1 | Dense V2 | 4S V2 | 8S | 4S V1 | 1S Intel V1 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SR635 (7Y98 / 7Y99) |
SR655 (7Y00 / 7Z01) |
SR655 Client OS |
SR645 (7D2Y / 7D2X) |
SR665 (7D2W / 7D2V) |
SD630 V2 (7D1K) |
SD650 V2 (7D1M) |
SD650-N V2 (7D1N) |
SN550 V2 (7Z69) |
SR850 V2 (7D31 / 7D32) |
SR860 V2 (7Z59 / 7Z60) |
SR950 (7X11 / 7X12) |
SR850 (7X18 / 7X19) |
SR850P (7D2F / 2D2G) |
SR860 (7X69 / 7X70) |
ST50 (7Y48 / 7Y50) |
ST250 (7Y45 / 7Y46) |
SR150 (7Y54) |
SR250 (7Y52 / 7Y51) |
||
| A5U1 | SKLM for System x w/SEDs - FoD per Install w/1Yr S&S | N | N | N | N | N | N | N | N | Y | Y | Y | Y | Y | Y | N | N | N | N | N |
| AS6C | SKLM for System x w/SEDs - FoD per Install w/3Yr S&S | N | N | N | N | N | N | N | N | Y | Y | Y | Y | Y | Y | N | N | N | N | N |
| Part Number | Description | 2S Intel V1 | Dense V1 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ST550 (7X09 / 7X10) |
SR530 (7X07 / 7X08) |
SR550 (7X03 / 7X04) |
SR570 (7Y02 / 7Y03) |
SR590 (7X98 / 7X99) |
SR630 (7X01 / 7X02) |
SR650 (7X05 / 7X06) |
SR670 (7Y36 / 7Y37) |
SD530 (7X21) |
SD650 (7X58) |
SN550 (7X16) |
SN850 (7X15) |
||
| A5U1 | SKLM for System x w/SEDs - FoD per Install w/1Yr S&S | Y | Y | Y | Y | Y | N | Y | N | N | N | N | N |
| AS6C | SKLM for System x w/SEDs - FoD per Install w/3Yr S&S | Y | Y | Y | Y | Y | N | Y | N | N | N | N | N |
Warranty
The Kioxia CM6-R Entry NVMe SSDs carry a one-year, customer-replaceable unit (CRU) limited warranty. When the SSDs are installed in a supported server, these drives assume the system’s base warranty and any warranty upgrades.
Solid State Memory cells have an intrinsic, finite number of program/erase cycles that each cell can incur. As a result, each solid state device has a maximum amount of program/erase cycles to which it can be subjected. The warranty for Lenovo solid state drives (SSDs) is limited to drives that have not reached the maximum guaranteed number of program/erase cycles, as documented in the Official Published Specifications for the SSD product. A drive that reaches this limit may fail to operate according to its Specifications.
Physical specifications
The Kioxia CM6-R Entry NVMe SSDs have the following physical specifications:
Dimensions and weight (approximate, without the drive tray):
- Height: 15 mm (0.6 in.)
- Width: 70 mm (2.8 in.)
- Depth: 100 mm (4.0 in.)
- Weight: 130 g (5.3 oz)
Operating environment
The Kioxia CM6-R Entry NVMe SSDs are supported in the following environment:
- Temperature:
- Operating: 0 to 70 °C (32 to 158 °F)
- Transport: -40 to 80 °C (-40 to 176 °F)
- Relative humidity: 5 to 95% (non-condensing)
- Maximum altitude:
- Operating: 5,486 m (18,000 ft)
- Non-operating: 12,192 m (40,000 ft)
- Shock: 1,000 G (Max) at 0.5 ms
- Vibration: 2.17 GRMS (5-800 Hz)
Agency approvals
The Kioxia CM6-R Entry NVMe SSDs conform to the following regulations:
- Underwriters Laboratories: UL60950-1
- Canada: CAN/CSA-C22.2 No.60950-1
- TUV: EN 60950-1
- BSMI (Taiwan): CNS 13438 (CISPR Pub. 22 Class B): D33003
- MSIP: KN22, KN24 (CISPR Pub. 22 Class B)
- Australia/New Zealand: AS/NZS CISPR32:2015 Class B
- Canada: ICES-003 Issue 6 Class B
- EMC: EN55022 (2015) Class B
- EMC: EN55035 (2017)
- RoHS 2011/65/EU: EN50581 (2012) Category 3
Trademarks
Lenovo and the Lenovo logo are trademarks or registered trademarks of Lenovo in the United States, other countries, or both. A current list of Lenovo trademarks is available on the Web at https://www.lenovo.com/us/en/legal/copytrade/.
The following terms are trademarks of Lenovo in the United States, other countries, or both:
Lenovo®
ServerProven®
System x®
ThinkSystem®
The following terms are trademarks of other companies:
AMD and Ruby™ are trademarks of Advanced Micro Devices, Inc.
Intel® and Xeon® are trademarks of Intel Corporation or its subsidiaries.
Linux® is the trademark of Linus Torvalds in the U.S. and other countries.
Microsoft®, Windows Server®, and Windows® are trademarks of Microsoft Corporation in the United States, other countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
