VxRail: Cluster Validation Fails when VLAN 3939 is Not Used for Node Discovery

Summary: Validation fails on VxRail 8.0.300 and later when the cached discovery VLAN 3939 is not in use which causes a mismatch error.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Observed Symptoms

The validation process aborts with an error related to VLAN 3939, even though that VLAN is not configured for discovery.

Error Messages

dayone.log
"2024-09-23 14:40:20,691" microservice.do-network "2024-09-23T14:40:19.831683014Z stderr F [2024-09-23 14:40:19,831: INFO/ForkPoolWorker-110] Creating  portgroup = vxraildiscovery, vlanId = 3939, activeNic = vmnic1, standbyNic = []."
"2024-09-23 14:40:20,691" microservice.do-network "2024-09-23T14:40:19.832190471Z stderr F [2024-09-23 14:40:19,832: INFO/ForkPoolWorker-110] target switch spec:(vim.host.VirtualSwitch.Specification) {"
"2024-09-23 14:40:20,691" microservice.do-network "2024-09-23T14:40:19.832201441Z stderr F    dynamicType = <unset>,"
"2024-09-23 14:40:20,691" microservice.do-network "2024-09-23T14:40:19.83220546Z stderr F    dynamicProperty = (vmodl.DynamicProperty) [],"
"2024-09-23 14:40:20,691" microservice.do-network "2024-09-23T14:40:19.832208825Z stderr F    numPorts = 128,"
"2024-09-23 14:40:20,691" microservice.do-network "2024-09-23T14:40:19.832211918Z stderr F    bridge = (vim.host.VirtualSwitch.BondBridge) {"
"2024-09-23 14:40:20,691" microservice.do-network "2024-09-23T14:40:19.832214719Z stderr F       dynamicType = <unset>,"
"2024-09-23 14:40:20,691" microservice.do-network "2024-09-23T14:40:19.832217474Z stderr F       dynamicProperty = (vmodl.DynamicProperty) [],"

UI displays a validation failure message indicating the VLAN 3939 error.

screenshot showing validation 3939 error

Cause

Root Cause

Discovery VLAN was modified via command line, but ESXi retained a cached reference to VLAN 3939. The validation routine reads the cached VLAN ID, causing a mismatch when the VLAN is not actually in use.

Contributing Factors

  • VLAN configuration change not propagated to the ESXi management layer.
  • Cache of VLAN 3939 persists in the ESXi UI after CLI update.
  • Validation logic in VxRail 8.0.300 and later queries the cached VLAN ID.

Resolution

Workarounds

CLI‑Based VLAN Update

  1. Restart hostd and vpxa services after changing the discovery VLAN. This forces VxRail to retrieve the updated VLAN information on the next validation attempt. Provide a JSON file that includes the correct discovery VLAN setting when running the cluster validation.
  2. Ensure the JSON file contains the updated vlan_id value for the discovery VLAN. 
        "network": {
        "nic_profile": "TWO_HIGH_SPEED",
        "vds": [
            {
                "portgroups": [
                    {
                        "type": "MANAGEMENT",
                        "vlan_id": 0
                    },
                    {
                        "type": "VSAN",
                        "vlan_id": 49
                    },
                     {
                        "type": "VXRAILDISCOVERY",
                        "vlan_id": 0
                    },
                    {
                        "type": "VMOTION",
                        "vlan_id": 50
                    }
                ]
            }
        ],

    Replace the vlan_id information with the correct vlan_id used by the discovery.

 

Note: You may have to run the validation twice for the workaround to take effect.

UI‑Based VLAN Update

If the discovery VLAN is updated through the ESXi UI, no additional steps are required. The validation succeeds using the UI‑configured VLAN.

 

Affected Products

VxRail, VxRail Appliance Series, VxRail G Series Nodes, VxRail D Series Nodes, VxRail D560, VxRail D560F, VxRail E Series Nodes, VxRail E560, VxRail E560F, VxRail E560N, VxRail E660, VxRail E660F, VxRail E660N, VxRail E665, VxRail E665F, VxRail E665N , VxRail G560, VxRail G560F, VxRail P Series Nodes, VxRail P570, VxRail P570F, VxRail P580N, VxRail P670F, VxRail P670N, VxRail P675F, VxRail P675N, VxRail S Series Nodes, VxRail S470, VxRail S570, VxRail S670, VxRail Software, VxRail V Series Nodes, VxRail V570, VxRail V570F, VXRAIL V670F, VxRail VD-4510C, VxRail VD-4520C, VxRail VD Series Nodes, VxRail VE-660, VxRail VE-6615, VxRail VE-670, VxRail VP-760, VxRail VP-7625, VxRail VP-770, VxRail VS-760 ...
Article Properties
Article Number: 000228813
Article Type: Solution
Last Modified: 06 آب 2026
Version:  7
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.