VxRail Software

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

This article is an accumulation of questions, answers, and information relating to VxRail upgrades.

Event code: VXR500PST0192 This event code indicates "Shut-down test failed."

Event code: VXR500PST0144 This event code indicates "Unable to load required BIOS files."

Event code: VXR500PCI1300 This event code indicates "A front panel diagnostic interrupt was detected."

Event code: VXR500PCI5008 This event code indicates "The Chassis Management Controller (CMC) is unable to communicate with the PCIe switch board."

Event code: VXR500PDR1024 This event code indicates "Drive mismatch detected for drive <number> in disk drive bay <bay>."

Event code: VXR500PST0196 This event code indicates "Incorrect memory configuration."

Event code: VXR500PDR117 This event code indicates "The <PCIe solid state device name> has turned off because the critical temperature threshold is exceeded."

This article details how to check the system BIOS for enabled or disabled physical ports and enabled or disabled ports within the ESXi hypervisor.

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

This KB article provides a script download link for SolVe Procedure: Customize the default network IP address for RKE2. If you are not directed to this KB article from SolVe Procedure, then do not perform the actions in this article.

This article discusses an issue in which using Internet updates for any VxRail system fails to generate advisory reports.

This article describes how to fix the inability to create Virtual Storage Area Network (VSAN) disk groups. It also provides for issues adding disks to existing ones when there are abnormal conditions showing on the host. The specific conditions addressed in this article include "Ineligible" drives that should be available. You may also see an incorrect number of total drives on the host and/or additional disk groups that should not be there.

VxRail does not support the route based on IP hash load-balancing policy. The day2 node add validation fails if the management port group chooses that policy.

This KB article discusses how to enable TRIM/UNMAP on all ESXi hosts on the vSAN cluster to reclaim space on the vSAN datastore.

Event code: VXR500PST0128 This event code indicates "No memory is detected."

The Physical view is not working, or nodes are missing from the host page due to incorrect vmk layout.

Node health-check fails for test dcism. Test 'dcism' is a health-check that runs on each VxRail node to attempt to validate the status of the dcism service.

Unable to place any host in the cluster into maintenance mode or vMotion due to certificate issues.

The 'df_service' test checks the local Service datastore available capacity on each node.

Event code: VXR500PDR215 This event code indicates "Copyback task to <physical disk name> has failed."

Event code: VXR500PCI1312 This event code indicates "An EISA fail-safe time-out was detected."

Event code: VXR500PFM0001 This event code indicates "The value of <sensor name> is greater than the upper critical threshold."

Event code: VXR500PST0131 This event code indicates "System BIOS shadow failed."

This document describes the objects and equipment used by Customer Engineers (CEs) when on-site. Please check and prepare in advance.

The HTML 5 VxRail plugin was introduced in 4.7.100. Under certain circumstances, the VxRail plugin must be reinstalled. This article has the official attachments from VxRail Escalation Engineering for the VxRail 4.7.x, 7.x, and 8.x releases.

After VxRail Upgrade Completes. If vLCM is enabled on VxRail cluster, vSAN on-disk format must be upgraded manually after cluster upgrade completes.

Running VxVerify returns an error for "No IPv6 on management VMK."

Before upgrading to release 8.0.300 or above, it is essential to verify the availability of the new port numbers (39090, 35252, 35353, and 38008) within the environment.