PowerProtect DD and IDPA: After Upgrading, ethVX Fails to Communicate

Summary: After upgrading IDPA example model dp4400, ethVX fails to communicate, failing either backups or replication or cyber replication.

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

Run the below command to list the network interfaces in the command line: 

#net show settings

In the example below, ethV3 is up and running but it cannot communicate or ping:

dd# net ping 192.168.x.x interface ethV3
PING 192.168.x.x (192.168.x.x) from 192.168.x.x ethV3: 56(84) bytes of data.
^C
--- 192.168.x.x ping statistics ---

6 packets transmitted, 0 received, 100% packet loss, time 6ms

This issue only affects IDPA systems with an ESXi. 

Cause

The ESXi layer has failed to initialize the networker adapter. 

Resolution

To address this issue to get the interface to ping and communicate again, follow these steps:

  1. Log in to ESXi UI and go to Virtual Machines > DDVE > Edit Settings.
  2. Scroll down to the NICs, clear the Connect box for the Network Adapter that is failing to communicate, and click Save. 
  3. Log in to the Data Domain CLI and Disable the Interface failing to communicate. 
Example: 
net disable ethV3
  1. Go back to the ESXi UI and check the Network Adapter and click Save. 
  2. Go back to DDOS and Enable the Interface. 
net enable ethV3

If there is still no ping, try again and reverse the steps. If that fails as well, open a case with Dell Support. 

Affected Products

Data Domain, PowerProtect Data Protection Appliance, Data Protection Suite Series, Integrated Data Protection Appliance Family, Integrated Data Protection Appliance Software
Article Properties
Article Number: 000441994
Article Type: Solution
Last Modified: 25 مارس 2026
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.