VxRail Software

This document highlights minimum, recommended, and latest code versions for Dell Technologies Enterprise and Data Center Infrastructure products. Dell carefully evaluates and monitors code deployment data to ensure that product releases meet our stringent expectations to provide our customers with reliable products and solutions.

A guide to Dell customers on how to prepare for an upgrade of their VxRail cluster with the Remote Proactive Support Team.

Event code: VXR508PWR205 This event code indicates "The Server Performance Over Power Redundancy (SPOPR) feature cannot be enabled because the Extended Power Performance is enabled."

Event code: VXR508PWR2270 This event code indicates "The Intel Management Engine has encountered a Health Event."

Event code: VXR508PWR216 This event code indicates "Unable to enable Extended Power Performance, because Redundancy Policy is set to Grid Redundancy or No Redundancy."

Event code: VXR508PSU8512 This event code indicates "Unable to update the firmware for the PSU in slot <slot number>. Error=0x<error number> (<error string>)"

Dell VxRail remediation is available for multiple security vulnerabilities that could be exploited by malicious users to compromise the affected system.

Event code: VXR508PWR223 This event code indicates "Cannot perform a 110V AC operation because the Extended Power Performance (EPP) feature is enabled."

Health check fails for test 'rcs_conn'.

Health-check returns an event indicating that VxVerify found an issue with vCenters Fully Qualified Domain Name (FQDN) in VxRail Manager configuration set.

Health-check returns an event indicating that VxVerify found an issue with the vCenter VMware Certificate Authority (VMCA) mode.

Event code: VXR508PWR2255 This event code indicates "The Chassis Management Controller (CMC) is configured in Max Power Conservation Mode and is unable to grant power on permission to the server."

Event code: VXR508PWR2252 This event code indicates "Unable to turn on the server because an NDC or Mezzanine card is incompatible with the I/O Module or PCIe subsystem."

Event code: VXR508PSU8513 This event code indicates "Unable to complete the PSU slot <number> firmware update. Error=0x<error number>."

The Health-check returns an event indicating that VxVerify found a mismatch in the Network Time Protocol (NTP) settings.

Event code: VXR508PWR203 This event code indicates "Unable to set the System Input Power Cap value to less than or equal to 13300 W (45381 BTU/h), because the Extended Power Performance feature is enabled."

Event code: VXR508PWR2256 This event code indicates "Unable to allocate power for servers to turn on because the Chassis Management Controller (CMC) is initializing chassis infrastructure components."

When attempting to upgrade to VxRail 8.0.x, VxRail Clusters that have nodes with an active Trusted Platform Module (TPM) 1.2 module will either fail the LCM precheck or give a warning.

VxRail upgrade fails during the VxRail Manager post-upgrade stage with "Failed to reconfig the backup schedule" when an empty vxmbackup.json exists on VxRail Manager.

VxRail vLCM update from version 8.0.330 to 8.0.380 failed during the “Scan Components” stage.

Deployment is unable to validate due to a previous attempt that failed.

Event code: VXR508PWR2253 This event code indicates "Unable to turn on the server because a PCIe card or Mezzanine card is not installed."

VxRM cluster upgrade pre-check to make sure cluster not having self-signed certificate when vLCM enabled.

The intent of this KB is to provide the proper course of action to take when the notified mystic code MYSTIC014062/VXR014062 takes place.

User Guide for VxRail Troubleshooting Toolbox (VTT)

This article provides instruction on how to view, generate, replace, and manage the VxRail Manager certificate. This information is current as of VxRail 8.0.380; UI options may be limited or missing in earlier versions. NOTE: This does NOT apply to VCF clusters or environments.

During an upgrade to 8.0.380, the upgrade may fail during Platform Service queries after its reboot and upgrade of the Platform Service VIB to 8.0.380.29572188. In 8.0.380 the iSM VIB is removed, with the Platform Service taking over the tasks that iSM previously handled. Please DO NOT install the iSM VIB on hosts after they upgraded to 8.0.380. This issue can also be observed on versions lower than 8.0.380 that are utilizing STIG.

During an upgrade from 8.0.370 to 8.0.380, the upgrade hangs at the end for many hours without progress or failure.

How to enable Unified Data Transport (UDT) traffic on Day2 environment.

This article will cover troubleshooting VxRail disk/drive issues using the vxtii output.