VxRail and VxRack: Dial-home Event MYSTIC01001F/VXR01001F - Network Connectivity Lost

Summary: Dial-home event code: MYSTIC01001F/VXR01001F - Network Connectivity lost

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.

Symptoms

This mystic code is generated when the VxRail Manager (or VxRack) detects a failure to communicate on a VxRail Node, even if the indicated host's NIC may not be faulted. This alert shows up in the 'Events' view on the VxRail Manager's Web client and may cause the VxRail to dial home and generate a Service Request if Secure Remote Services is connected and enabled. Maintenance that involves switch configuration or hardware (like changing cables) and similar activities can trigger these alerts. They may also come up due to network outages, accidental impacts to network components, or failures of networking hardware or software. Customers may be able to identify and resolve network issues on their own or can engage VxRail Support when troubleshooting assistance or replacement of faulty hardware may be required.

Cause

Note: This information is written pertaining to VxRail events, with similar information for VxRack.

The following situations may cause this alert to trigger:

  • Failure of network cables
  • Network cables disconnected
  • Failure of the physical network card
  • Failure of other network components (switches, ports, SFPs, and so forth)
  • Network connectivity that is lost on Distributed Virtual Ports 
  • Network connectivity that is lost on the Virtual-Distributed Switch (VDS or DVS)

Resolution

Known networking issues or maintenance should be handled based on the specific circumstances. If maintenance is concluded without any known issues that are resolved, a Support engagement may not be necessary, and any dial-home generated Service Request may be able to be closed "without incident." Customers may still elect to engage VxRail Support to verify the cluster and VxRail Manager are healthy following an outage, a maintenance activity done without suppressing cluster monitoring, or other known events as needed. For dial-home SRs opened automatically by the VxRail Manager through Secure Remote Services, customers should inform VxRail Support of any known maintenance or incidents and let Support know if assistance is needed or if SR can otherwise be closed.

Note: Engage VxRail Support, if needed, for assistance with the below steps. If possible, collect and upload logs and provide a timeline of any known events at the time of SR creation.
For information on collecting the host logs see: Collecting diagnostic information for VMware ESXi using vSphere ClientThis hyperlink is taking you to a website outside of Dell Technologies.
For information on collecting a TSR for the host see: VxRail: How to collect TSR logs on Dell's 14G PowerEdge Servers.

For unexpected/unknown issues, check on the status of the host networking by doing the following:

  1. Log in to the vCenter web client (or host's vSphere client) and select the host indicated with the VxRail Manager alert. A host with a network fault may not be available in vCenter and might show 'Not Available' or 'Disconnected'. In this case, you may still be able to connect to the node through a vSphere client (open a web browser to the individual node) and should still have access to the host through the Baseboard Management Controller (BMC) for Quanta or the IDRAC for Dell nodes.
  2. Under 'Monitor', check the Hardware Status of the host's NICs to see if a failure is indicated here. 
  3. If it shows that network cards (NICs) have failed, then engage VxRail Support. For Quanta platforms, the node may need to be replaced. For Dell platforms, hardware troubleshooting (including replacement of any faulty components identified) is done. Logs must be collected and uploaded to the SR, including a VxRail Manager log bundle, hardware logs (Support Assist or TSR) for Dell, and VMware logs (vm-support from host if needed).

If the NICs are not shown to be failed in the Hardware Status, then the rest of the network environment should be investigated. Check the following for issues:

  • The physical connection of the VMNIC specified in the alert including attached wires and adapters
  • The configuration of the attached network switch (and any available logs or monitoring tools that report faults)

If you need any assistance on troubleshooting the issues above, contact Dell EMC Technical Support or your Authorized Service Representative, and quote this Knowledge Base Article ID.

Affected Products

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