How to run VCF-Verify (VCFV) tool in VCF on VxRail environment
search cancel

How to run VCF-Verify (VCFV) tool in VCF on VxRail environment

book

Article ID: 419624

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

  • VCF-Verify (VCFV) is a healthcheck tool for VCF clusters, which is run from SDDC Manager
  • VCF-Verify runs VMware health checks from SDDC Manager and automatically launches the VCF-Verify healthcheck tool on each VxRM before summarising all the results in a single table

Environment

VCF on VxRail

Resolution

  1. Download the latest VCF-Verify package from Dell Solutions > VCF-Verify
  2. Copy the .zip file to the SDDC Manager to /home/vcf directory.
  3. To execute the tool, follow the Dell KB - VCF on VxRail: How to Run the VCF-Verify Tool

NOTE: In the above KB /tmp/vcfv folder is set as working directory which might not work correctly hence ensure to use /home/vcf as working directory

VCF-Verify tool should be run on the SDDC Manager. It will detect all the Vxrail Manager appliance VMs managing the Workload and Management Domain. The output will show Addressable, Expected and Resolved.

Contact Dell Technical support for assistance.

Additional Information

Sample output

Categorized the items and their respective VxRail clusters they reference by Addressable, Expected, or Resolved.
Addressable - warnings which need to be addressed for the cluster 'occurrence'.
Expected - warnings that are expected for the type of system.
Resolved - warnings which were found and resolved from the vcf-verify pre-check.
 
_______________________________________________________
Resolved items:

_Fixed: tcserver: Radar ownership corrected for 10 files

 (Dell KB: 000302543 - VxRail: health-check warning for "tcserver")

 > This checks the files in the /mystic/radar directory to verify they have ownership set to user: tcserver and group: pivotal.  If not, it will change the ownership of the files.

Occurrences for MGMT: vxverify_vxrailmanager01txt | vxverify_vxrailmanager02.txt | vxverify_vxrailmanager03.txt | vxverify_vxrailmanager04.txt | vxverify_vxrailmanager05.txt

Occurrences for WLD: vxverify_vxrailmanagerWLD01.txt | vxverify_vxrailmanagerWLD02.txt | vxverify_vxrailmanagerWLD03.txt | vxverify_vxrailmanagerWLD04.txt | vxverify_vxrailmanagerWLD05.txt | vxverify_vxrailmanagerWLD06.txt

_Fixed: hx_fix: hostd+vpxa restarted for esx01, esx02

 (Dell KB: 000205179 - Dell VxRail: health-check 'ism_fix' or 'rac_fix' correcting iSM and iDRAC issues)

 > this checks for ism service issues and restarts the respective services to resolve.

Occurrences MGMT: NONE

Occurrences for WLD: vxverify_vxrailmanagerWLD01.txt | vxverify_vxrailmanagerWLD02.txt

 

Expected items:

    Warning: vcf_type: VCF-VxRail without lcm-bundle datastore

 (Dell KB: 000182445 - VCF on VxRail: VxRM Health-check Fails For vcf_type)

 > VCF is present, which must be considered for the upgrade procedure.  Alternatively, the cluster was originally a VxRack and iDRAC is uses vmk0 (instead of the default vmk1).

 > The warning does not indicate a potential fault, but is there to make it clear that VCF upgrade procedures must be used, not standard VxRail.       

Occurrences for MGMT: vxverify_vxrailmanager01txt | vxverify_vxrailmanager02.txt | vxverify_vxrailmanager03.txt | vxverify_vxrailmanager04.txt | vxverify_vxrailmanager05.txt

Occurrences for WLD: vxverify_vxrailmanagerWLD01.txt | vxverify_vxrailmanagerWLD02.txt | vxverify_vxrailmanagerWLD03.txt | vxverify_vxrailmanagerWLD04.txt | vxverify_vxrailmanagerWLD05.txt | vxverify_vxrailmanagerWLD06.txt

 

Warning: vibsx: NSX VIB nsx-host found; use NSX upgrade procedures

 (Dell KB: 000043126 - VxRail: Node health-check fails for test 'vibsx')

 > vib found that must be considered in the upgrade procedure (such as NSX)

 > the nsx vib is expected for VCF.     

Occurrences for MGMT: vxverify_vxrailmanager01txt | vxverify_vxrailmanager02.txt | vxverify_vxrailmanager03.txt | vxverify_vxrailmanager04.txt | vxverify_vxrailmanager05.txt

Occurrences for WLD: vxverify_vxrailmanagerWLD01.txt | vxverify_vxrailmanagerWLD02.txt | vxverify_vxrailmanagerWLD03.txt | vxverify_vxrailmanagerWLD04.txt | vxverify_vxrailmanagerWLD05.txt | vxverify_vxrailmanagerWLD06.txt

 

Addressable items:

Warning: vs_util: What if the most consumed host fails

 (Dell KB: 000217640 - Dell VxRail: health-check fails for tests with 'vs_util')

 > VxVerify found at least one 'Yellow' result from the vSAN health output.

 > Reference Broadcom KB: https://knowledge.broadcom.com/external/article?legacyId=2108743 

 > Check for unused VMs, old snapshots, and files on vSAN datastore to clear space.

Occurrences for MGMT: vxverify_vxrailmanager01.txt

Occurrences for WLD: NONE

 

Warning: kube_diff: Kubectl Client data mismatch found

 Dell KB: 000212809 - VxRail: Kubectl Commands Return: You Must be Logged in to the Server Unauthorized)

 > rke2 service has been running for over 1 year the $HOME/.kube/config is expired.

 > Contact Dell to resolve.  Reference Dell KB: 000212809 - VxRail: Kubectl Commands Return: You Must be Logged in to the Server Unauthorized

Occurrences for MGMT: vxverify_vxrailmanager01.txt | vxverify_vxrailmanager02.txt | vxverify_vxrailmanager03.txt | vxverify_vxrailmanager04.txt

Occurrences for WLD: vxverify_vxrailmanagerWLD01.txt | vxverify_vxrailmanagerWLD02.txt | vxverify_vxrailmanagerWLD03.txt

 

Warning: vxm_cert: Modulus mismatch between server.crt and server.key.

 (Dell KB: 000198406 - VxRail: Health Check Fails For Test 'vxm_cert')

 > VxRail Manager certificate issues found. See Cause section below.

 > There are steps in the KB to check and run to resolve this issue.

 > You can request assistance from Dell to resolve.

Occurrences for MGMT: vxverify_vxrailmanager01.txt | vxverify_vxrailmanager02.txt

Occurrences for WLD: vxverify_vxrailmanagerWLD01txt