VxRail: Hardware Troubleshooting Using VxRail Triage Reports VxTii
Summary: This article summarizes how to generate VxTii reports from a VxRail node.
Symptoms
The VxTii report is run as part of the health checks performed by the VxVerify minion. Configuration data is gathered from iDRAC and ESXi, and the results are also used to generate a VxTii report for each node.
For example, the HW-Inventory is downloaded from iDRAC and crosses referenced with ESXCLI data.
This report has the data that Support is most likely to need when diagnosing problems. For example, the health, driver and firmware levels of each Network Interface Card (NIC).
VxTii reports (vxtii.txt), can be found in the VxVerify folder after VxVerify has been run. This report contains reports for each node listed sequentially. Typically, these reports can be found in whichever folders were used to run the VxVerify tool on VxRM:
/tmp/vxv/vxtii.txt
/var/log/mystic/vxv/vxtii.txt
The detailed set of configuration and log data that is used to generate the report is saved as 'vxtii.json', in that same folder.
On the node, the report can be found at:
/tmp/vxtii.txtVxTii node report
After the VxVerify minion is run on a node, the vxtii.txt in the /tmp folder on that node, will only have that node's information. This could be run as part of the VxRail Manager health-checks.
========================================================================================================================
Dell VxTii report version 3.21.121 on VMware ESXi 7.0.2 build-18426014
========================================================================================================================
Product Tag Product_Serial# Report_Date_GMT Inventory_Date Hostname
------------------------------------------------------------------------------------------------------------------------
VxRail_E560F FP9P9T9 FP9P9T90000000 2022-11-22_09:17 2022-04-11_14:06 lab-12-esxi-02.any-lab.local
------------------------------------------------------------------------------------------------------------------------
Dell BIOS iDRAC Uptime CPU DIMM PCIE CLPD Manufacturer ____System_Board____
Gen. Vers. Vers. (days) Sockets Slots Slots Vers. Name Part# Serial#
------------------------------------------------------------------------------------------------------------------------
14G 2.11.2 4.40.40.00 224 2 24 3 1.0.2 Dell_Inc. 0PHYDRA00 CNIVC0000P1111
------------------------------------------------------------------------------------------------------------------------
RP4VM NSX GPU NTP Maint-mode Nameservers Unmap:Guest/Fairness Certificate: expiry & issuer
------------------------------------------------------------------------------------------------------------------------
No No No Yes No [172.99.0.11, 172.99.0.12] No / Yes 1586 days vmca@vmware.com
========================================================================================================================
Recommendations For Support
------------------------------------------------------------------------------------------------------------------------
No action items found <- Action plans for some faults can be found here, such as for MEM8000
========================================================================================================================
CPU ...
VxTii cluster report
When the VxTii report is downloaded to VxRM, along with the health-check data, then each node's report is merged with reports from the rest of the nodes and general cluster summary data.
########################################################################################################################
VxTii - VxRail 8.0.311 Triage Report from VxVerify
========================================================================================================================
Dell VxTii 4.50.117 report for VxRail Manager 8.0.311 at 2025-01-18 09:16 GMT (see vxtii.txt) .
Cluster Name: VxRail-Virtual-SAN-Cluster
Cluster_UID: 52f57a37-968e-0e20-b538-669ac2bd11b8 vSAN_Licence: Evaluation Mode
Deployment_Type: STANDARD LCM_Status: No Upgrade in progress
vCenter_FQDN: cluster101-vcsa.lab007.local EVC_Mode: intel-icelake
========================================================================================================================
VCSA Stretch VCF RP4VM vLCM NSX ELM GPU CHM AdvM Satt Health vCenter-Build Port VC-API_host .
Internal No No No Yes No No Yes Yes No No Healthy 8.0.3-24322831 443 vCenter_FQDN
========================================================================================================================
VxRM-Build VxRM_VM_UID MFID VM_Latest_boot VxRM_FQDN .
8.0.311-28839942 564dda19-3200-3c00-7800-6d0bfeeebf00 vm-24 2025-01-18_04:36 vxrm.lab007.local
========================================================================================================================
Plugin | Version (refer to KB 189279) .
VxRM (local) 9.5.0
hsm 7.0.410-27831806
========================================================================================================================
CHM: Cluster Health Monitoring ("No" means cluster suppressed; KB 195874). GPU: At least one node contains a GPU (KB 191633)?
Int/Ext: Whether vCenter is Internal or External (KB 45053). NSX: VIB for NSX present on nodes (KB 43126)?
RP4VM: RecoverPoint installed (KB 42295)? Stretch: vSAN witness present for stretched clusters (KB 66108)?
vLCM: vSphere Lifecycle Manager enabled? AdvM: Advanced mode enabled in LCM? Satt: Satellite nodes present?
########################################################################################################################
VxTii report for first node etc. ...
Cause
If the VxTii report (vxtii.txt) is not automatically generated when the VxVerify script has completed, one typical cause is related to those nodes not having iDRAC (such as Quanta or virtual nodes).
A large proportion of the VxTii node report is based on iDRAC data (cross-referenced with ESXi data), and so VxTii only supports iDRAC based nodes.
VxTii abbreviations for node report
Key VxTii heading definition
At_risk_obj Number of Objects that would have Redundancy Reduced if the node went offline
BIOS Vers Dell VxRail node Basic Input/Output System version
Certificate Certificate expiry date and issuer name
CLPD Complex programmable logic device (version found from iDRAC)
CPU sockets Number of CPU sockets in the VxRail node
Dell Gen. Dell PowerEdge product family Generation. E.g. 14G is the 14th Server Generation.
DIMM slots Number of Dual Inline Memory Modules in the node
DU_objects Number of Objects that would have Data Unavailability if the node went offline
ESA Enterprise Storage Architecture used for vSAN
Evacuation_Data Data that would need to be moved if the vSAN node was evacuated
GPU Graphics Processor Unit board present on the node
iDRAC Vers Integrated Dell Remote Access Controller version
Inventory_Date Date of the last iDRAC hardware inventory change
LACP Link Aggregation Control Protocol in use
Lockdown ESXi or iDRAC lockdown mode status
Maint-mode Maintenance Mode for ESXi server
Nameservers DNS nameservers listed in resolv.conf
NSX VMware Network Software X found on this node
NTP Network Time Protocol configured on this node
PCIe Slots PCIe sockets in this model of VxRail
Prediction Maintenance mode and evacuation outcome prediction
Product_Serial Serial number. If not present then only the Service Tag is being used.
Rack Node Height in Rack Units
RP4VM RecoverPoint for Virtual Machines bundle is present
SecurBoot Secure boot status
System_Board Part and serial numbers if the node motherboard
Tag Dell Service Tag for the node
TPM Trusted Platform Module status
TPM-vers Trusted Platform Module version
Unmap vSAN Guest and Fairness Unmap settings
Uptime Time in days since the last ESXi boot
VxVIB Version of VxRail vSphere Installation Bundle on this node
Resolution
If errors occur with generating VxTii reports from VxVerify, see article: Dell VxRail: VxVerify Troubleshooting Guide
The cause of the report not being saved will probably be listed in the minion.log, such as iDRAC not responding.