CSCwk74954

On Cisco UCS C245 M6 servers, if Cisco IMC crashes, the IP Type field in the Preboot Execution Environment (PXE) Boot configuration might change to None even though it is configured as IPv4. When this occurs, Intersight may show Out of Sync on the Server Profile > Boot Order policy.

This issue is resolved.

4.2(3h)

6.0(2.260205)

CSCwv93860

On Cisco UCS C220 M8 servers in Intersight Standalone Mode, after a Redfish PATCH request is used to configure one-time Preboot Execution Environment (PXE) boot, the request may complete successfully but return the previous boot values in the response body. The boot setting is updated successfully, but the PATCH response body may not show the updated state. A follow-up GET request shows the correct PXE boot state.

This issue is resolved.

4.3(2.260007)

6.0(2.260205)

CSCww03146

On Cisco UCS C225 M8 servers in Intersight Standalone Mode, a Redfish PATCH request for boot override settings may return a success response for invalid payloads. This condition can occur when an invalid enum value or an incorrect data type is sent for boot override fields. When this occurs, no error information may be returned, and the server state remains unchanged.

This issue is resolved.

4.3(2.260007)

6.0(2.260205)

CSCwv66245

CSCwv82952

On Cisco UCS C-Series C245 M8 servers with AMD EPYC 9xx5 processors, the default Auto selection for the xGMI Link configuration was previously setting 3 xGMI links between processors instead of the intended 4 xGMI links.

This issue has been resolved. The default Auto option now configures a 4xGMI link configuration. Additionally, BIOS token options are provided to revert to the previous configuration, along with the corresponding link speed selection. This change has no observable impact on the operating system environment.

4.3(6.250040)

6.0(2.260205)

CSCwn42410

A partial failure of one of the M.2 drives on a Cisco UCS-M2-HWRAID controller may cause the affected drive to be reported incorrectly and may degrade the RAID 1 virtual drive.

In this condition, the drive can appear in PhyDriveInfo with no valid device data visible, while the reported link speed is reduced to 1.5 GB.

Additional drive attributes such as power-on hours, power cycle count, percentage life, wear status days, and temperature may all appear as 0.

Product ID and firmware fields may also be blank even though the drive is still shown as online.

In some cases, the messages log may incorrectly report the affected drive as having 0% life remaining by generating an SSD LIFE TIME LAPSE fault.

This issue has been observed on systems using the Cisco UCS-M2-HWRAID M.2 storage controller with M.2 drives configured in a RAID 1 virtual drive.

This issue is resolved.

4.3(2.230207)

B-Series: 6.0(1.260031)

C-Series M8, M7, M6 servers: 6.0(2.260143)

C-Series M8, M7, M6 servers: 4.3(6.260054)

C-Series: 4.3(2.260020)

CSCwt57564

On Cisco UCS X210c M8 servers with Cisco UCS Virtual Interface Card (VIC) adapters, VMware ESXi may display a Purple Screen of Death (PSOD) with a Peripheral Component Interconnect (PCI) bus error. The error message may indicate an undiagnosed PCI bus error and an event received for a port with no Downstream Port Containment (DPC) driver. This issue occurs when the posted value in the ring registers does not increment as expected, preventing the software from detecting that an indirect transaction has arrived.

This issue is resolved.

X-Series M8 (X215c): 5.3(0.240016)

X-Series M8 (X210c): 5.4(0.250037)

X-Series M8 (X410c): 6.0(2.260040)

X-Series M8 (X410c, X215c, X210c): 6.0(2.260143)

X-Series M8 (X215c, X210c): 5.4(0.260044), 5.4(0.260049)

CSCwt65289

On Cisco UCS C-Series, X-Series, or XE-Series servers with Non-Volatile Memory Express (NVMe) drives, Fault History may report NVMe disk inoperable events during a host firmware upgrade. In this condition, the firmware upgrade completes successfully, and the reported messages are cleared after the host reboots following the firmware update process. The drive inoperable messages can be safely ignored during the host firmware upgrade.

This issue is resolved.

6.0(2.260044)

X-Series: 6.0(2.260143)

XE-Series: 6.0(2.260143)

CSCwt73073

On Cisco UCS X210c M7 servers, after a Basic Input/Output System (BIOS) upgrade to release 6.0(2.260040), an inventory fault may be reported for an unknown Peripheral Component Interconnect Express (PCIe) card on a riser. When this condition occurs, the adapter on the affected riser may not be detected after the upgrade.

This issue is resolved.

6.0(2.260040)

X-Series: 6.0(2.260143)

CSCwn42410

A partial failure of one of the M.2 drives on a Cisco UCS-M2-HWRAID controller may cause the affected drive to be reported incorrectly and may degrade the RAID 1 virtual drive.

In this condition, the drive can appear in PhyDriveInfo with no valid device data visible, while the reported link speed is reduced to 1.5 GB.

Additional drive attributes such as power-on hours, power cycle count, percentage life, wear status days, and temperature may all appear as 0.

Product ID and firmware fields may also be blank even though the drive is still shown as online.

In some cases, the messages log may incorrectly report the affected drive as having 0% life remaining by generating an SSD LIFE TIME LAPSE fault.

This issue has been observed on systems using the Cisco UCS-M2-HWRAID M.2 storage controller with M.2 drives configured in a RAID 1 virtual drive.

This issue is resolved.

4.3(2.230207)

C-Series: 6.0(2.260143), 4.3(6.260054)

CSCwt34870

Cisco UCS C-series servers running firmware version 6.0.2.260044 may experience Simple Network Management Protocol (SNMP) service becoming unresponsive when performing snmpget operations on private enterprise OIDs, subsequently causing snmpwalk requests to fail. If the service becomes unresponsive, it can be restored by rebooting the Baseboard Management Controller (BMC) or by disabling and re-enabling the SNMP service.

This issue is resolved.

C-Series: 6.0(2.260044)

C-Series: 6.0(2.260069)

CSCwt18924

After an upstream Cisco ACI fabric upgrade or reload, Cisco UCS VIC adapters may fail to bring vNICs online. The adapter physical interfaces come up, but the vNICs remain stuck in an initializing state and do not recover automatically. Adapter logs may show the adapter encountering out-of-memory conditions, followed by a reset. This issue is observed with 10GBase-T (10G-T-X) transceivers on Cisco UCS VIC 1400 Series and 15000 Series adapters and may be triggered during switch or server reload events when the transceiver holds the I2C bus, leading to a memory leak in the adapter.

This issue is resolved.

C-Series: 4.3(5.250030)

C-Series: 6.0(2.260069)

CSCwt42347

During the Host Firmware Package (HFP) upgrade from release 4.3(2) to 6.0(2), Cisco UCS X-Series servers with UCSX-X10C-RAIDF controller experience failure at the stage Preparing to check hardware configuration causing the Unified BIOS Management (UBM) upgrade to hang. The firmware update process does not complete, and BMC logs show the update process running indefinitely.

This issue is resolved.

X-Series: 6.0(2.260040)

X-Series: 6.0(2.260069)

CSCwt35920

Firmware updates may fail on certain RTX Pro 6000 GPUs shipped as spares, leaving them at an older firmware version. This issue is limited to specific spare units and does not affect the overall update process.

This issue is resolved.

X-series: 6.0(2.260040)

C-series: 6.0(2.260044)

X580p PCIe Node: 6.0(2.260043)

X-Series: 6.0(2.260069)

C-Series: 6.0(2.260069)

X580p PCIe Node: 6.0(2.260069)

CSCwr21671

On Cisco UCS B200 M5 servers with an LSI 12G RAID controller running Windows Server 2019 (megasas2 driver), an L2/L3 cache error may be detected on the RAID controller. This causes the storage controller to become inoperable, and Cisco IMC is unable to detect the controller.

This issue is resolved.

4.2(3e)

5.4(0.260011)

6.0(1.260012)

CSCws30219

Cisco UCS M7 servers may experience host lockups due to ECC errors during runtime. The BIOS fails to retrieve a variable properly, causing EFI to return an invalid parameter, which leads to the host freezing without any logs or Cisco IMC alerts.The host becomes unresponsive, and KVM input is not accepted.

This issue is resolved.

X-Series M7: 5.4(0.250048)

C-series M7: 4.3(6.250053)

X-Series M7: 6.0(2.260040)

C-Series M7: 6.0(2.260044)

CSCws62117

Cisco UCS C240-M8 server with LPe35002-M2 Emulex adapters connected to Brocade SAN switches and Dell storage arrays experience intermittent I_T NexusLoss errors, causing unstable connections and periodic LUN disconnections. Although FCP I/O completes without errors, the adapter repeatedly attempts to re-establish the connection by issuing LOGO and FLOGI commands, which temporarily restore connectivity before the issue recurs.

This issue is resolved.

4.3(6.250053)

6.0(2.260044)

CSCwr51315

On Cisco UCS X-series servers, NVMe drives UCS-NVMEG4-M7680 with firmware E2CS005 show an SSID of 5000 instead of the expected Cisco SSID 4800. This discrepancy causes compliance checks to fail, marking the disks as unclaimed.

This issue is resolved.

6.0(1.250120)

6.0(2.260040)

CSCwr73352

Multiple Cisco UCS x210C M7 servers experience Cisco IMC reboots triggered by BMC watchdog hard resets. This causes service profiles to become inaccessible temporarily during the reboot. This behavior may impact server management availability during the reset events.

This issue is resolved.

5.2(1.240010)

6.0(2.260040)

CSCwq55604

DIMM_P2_H1 on all Cisco UCS C245 M8 integrated servers reports as inoperable, although all DIMMs function correctly with no memory errors. The issue triggers alerts indicating equipment inoperability and incompatible server firmware, despite the server being fully populated with supported identical DIMM models.

This issue is resolved.

4.3(5.250001)

6.0(2.260044)

CSCwq17020

After installing U3 Micron drives with capacities of 3.8TB or larger in JBOD mode behind the UCSX-X10C-RAIDF controller, Linux OS fails to boot due to BIOSerrors related to loading the EFI boot image. This issue occurs specifically on Cisco UCS X-Series M8 servers equipped with Intel® processors and affects multiple Linux distributions. The problem does not occur when the drives are configured in RAID 0. Microsoft Windows® and Linux OS boot successfully on smaller capacity drives or when using RAID 0.

This issue is resolved.

X210c: 5.4(0.250037)

X215c: 5.4(0.250035)

6.0(2.260040)

CSCwr82017

On Cisco UCS X210c M8, C220 M8, and C240 M8 servers, the system continuously reboots if you enable IntelSGX and set the Processor Reserved Memory Range Registers (PRMRR) size to an unsupported value in the system memory settings. This issue occurs only when an unsupported PRMRR size is configured.

This issue is resolved.

X-Series M8: 6.0(1.252114)

C-series M8: 6.0(1.250192)

X-Series M8: 6.0(2.260040)

C-series M8: 6.0(2.260044)

CSCwr82475

On Cisco Unified Edge servers UCSXE-130C-M8, after upgrading from firmware version 6.0(1.250003) to 6.0(1.251026) in UEFI-Secure boot mode, BMC boot may fail to transfer FIT4 records to the Secondary Service Processor (SSP) due to timing and race conditions. This prevents the required authentication handshake, causing the host system's POST to hang.

You will see a BIOS POST completion failed error, and log messages such as:

• peci command(0xa1) failed: 0x63

• peci rdpkgconfig command (0xa1) failed (result code: 0x63, addr: 0x30)

• ast2600-ssp ahb:secondary-service-processor: Kicking SSP vqid = 1

Workaround: Reboot the BMC to resolve the issue.

XE-Series M8: 6.0(1.250003)

XE-Series M8: 6.0(2.260042)

CSCwr05911

On Cisco Unified Edge servers, when the host is powered off, the IMM Inventory page displays the LOM-NIC-1 interfaces as up on eCMC:A, but asdownon eCMC:B. This inconsistency occurs only when the host is powered off. There is no functional impact due to this issue.

This issue is resolved.

XE-Series M8: 6.0(1.251030)

XE-Series M8: 6.0(2.260042)

CSCwr45526

Certain Cisco UCS servers experience boot interruptions caused by validation failures in the Secure Boot database. This issue affects specific server models during system startup, leading to potential boot interruptions and impacting system reliability. The problem arises from outdated certificates in the Secure Boot database that prevent successful secure boot processes.

This issue is resolved.

C-series: 4.3(6.260017)

B-series: 5.4(0.260011)

C-series: 6.0(2.260044)

B-series: 6.0(2.260040)

CSCws24234

On Cisco UCS XE130c M8 Compute Node, when the UCS-M2-HWRAID2 MINI STOR controller is missing but its carrier is installed, the system log is continuously flooded with unable to read fru information errors.

Upgrade the firmware to resolve this issue.

If the same errors persist post-upgrade, physically verify that both the M.2 controller and its carrier are properly seated and installed.

6.0(1.251030)

6.0(1.260001)

CSCws22743

On Cisco UCS XE130c servers, L4/L40S GPUs may experience a link downgrade to x8 width and GEN 1 speed due to a race condition. This can reduce GPU performance and typically occurs when the link is downgraded or lane width is reduced.

To recover from a link downgrade, a workaround has been implemented to return the device to normal operation.

6.0(2.250123)

6.0(1.260001)

CSCws30219

Cisco UCS M7 servers are susceptible to host lockups triggered by ECC (Error Correcting Code) memory events.

This issue is specifically related to how the server’s BIOS interacts with the EFI (Extensible Firmware Interface) during error conditions. During these events, the BIOS does not correctly retrieve a required variable, causing EFI to return an invalid parameter. As a result, the operating system is unable to continue normal operation and freezes without logging any errors. When this occurs, the host becomes unresponsive and KVM (keyboard, video, mouse) input is not accepted.

Single-bit ECC errors—while not logged due to DDR5 specifications—can trigger this condition, resulting in complete loss of host responsiveness.

X-Series M7: 5.4(0.250048)

C-series M7: 4.3(6.250053)

X-Series M7: 6.0(1.250179)

C-series M7: 6.0(1.250192)

CSCwi71153

On Cisco UCS C-Series M6 servers, BMC reset occurs due to watchdog reset caused by kernel scheduler null pointer dereference.

In addition, kernel panic might also occur in the server.

4.2(3b)

C-Series M6: 6.0(1.250192)

CSCwq61388

On Cisco UCS C-Series M6 servers running CIMC 4.3.5 or later, enabling VMD in BIOS with multiple NVMe drives can cause storage subsystem initialization to exceed 15 minutes, leading to Intersight Server Profile deployment failures.

The likelihood of encountering this issue increases with the number of drives installed.

Disabling VMD or reducing the number of drives can resolve the issue.

4.3(5.250001)

6.0(1.250162)

6.0(1.250174)

CSCwq74490

On the Cisco UCS C245 M8 platform with AMD EPYC 9655 processors, fully loaded NVIDIA L4 GPUs experience random PCIe link width downgrades on different slots when running the Linux Rebooter Stress test. The affected slots change after actions such as an AC power cycle or HUU update; for example, if slots 2 and 6 are downgraded initially, other slots may be downgraded after these actions. This results in GPUs operating at reduced speeds in the OS environment.

4.3(6.250053)

6.0(1.250162)

6.0(1.250174)

CSCwq01863

On Cisco UCS C225 or C245 M8 servers in standalone mode, configuring secure LDAP (LDAPS) on any port other than 636 results in the server attempting a standard LDAP connection instead of a secure one, causing LDAPS authentication to fail.

Always use port 636 for secure LDAP connections. Other ports will not work for LDAPS.

4.3(6.250044)

6.0(1.250162)

6.0(1.250174)

CSCwr24516

On Cisco UCS X210c M8, some servers may not power on or start up if they contain a hardware part (inductor) from a specific vendor. This issue causes a startup failure, and the server will remain off even when you try to turn it on. The problem is caused by a difference in how the new hardware part works, but it can be fully resolved by updating the board to the latest VR (Voltage Regulator) image, which is designed to support this new component.

Update the server with the latest VR image, clear any power on error, and turn the server off and on again. If the server still does not start, contact Cisco TAC for further assistance.

6.0(1.250126)

6.0(1.250162)

6.0(1.250174)

CSCwp91696

On Cisco UCS X215c M8 servers, when an E3.S NVMe drive is added to an empty slot while the server is already running, the drive connects at Gen 4 speed instead of Gen 5. This issue only occurs if the slot was empty during boot and the drive is hot inserted after the operating system has started.

Insert the drive into the slot before powering on the server. Drives added later will only operate at Gen 4 speed until the server is rebooted.

6.0(1.250065)

6.0(1.250162)

6.0(1.250174)

CSCwq01510

On Cisco UCS X215c-M8servers, hot plugging E3.S NVMe drives in slot 8 or slot 9 does not work in ESXi or Windows if those slots were empty when the operating system started. Drives added or removed after boot are not detected by the OS.

There is no workaround. Hot plugging in slots 8 and 9 will not function if the slots are empty during OS boot.

6.0(1.250086)

6.0(1.250162)

6.0(1.250174)

CSCwq93635

On Cisco UCS C240 M6 servers running CIMC 4.3.5 and later firmware, deployments with a large number of NVMe drives and VMD enabled in the BIOS may experience prolonged storage subsystem initialization times, taking up to 50 minutes. This delay can cause the Wait for storage subsystem initialization task to fail in Intersight Server Profile workflows, especially after the Wait for BIOS POST Completion step.

If possible, turn off VMD in the BIOS to avoid the delay. If VMD must stay on, try using fewer NVMe drives during the initial setup, since the more drives you have, the longer the initialization takes.

4.3(6.250077)

6.0(1.250162)

6.0(1.250174)

CSCwq58890

The firmware for the Cisco UCS VIC 15000 series adapters is updated to fix a rare, intermittently seen memory issue and to ensure more robust and consistent operation across diverse memory types and configurations.

X-series: 6.0(1.250120)

B-series: 6.0(1.250126)

C-series: 6.0(1.250127)

X-series: 6.0(1.250122)

B-series: 6.0(1.250127)

C-series: 6.0(1.250131)

CSCwn99720

On Cisco UCS C-Series M8 servers with Intel processors and an R1S CPU configured in a single-CPU setup on the 2-socket platform, Intel SGX remains disabled even after being enabled in the BIOS. This issue does not occur with a dual CPU configuration.

4.3(6.250039)

6.0(1.250127)

4.3(6.250044)