Skip to main content
Delphix

Network Interface Name Changes After Upgrade to 6.0.17.0 or Later (KBA9922)

 

 

KBA

KBA# 9922

 

Issue

Depending on the previous Delphix Engine version, the Ethernet Network Interface name may change, from eth# to enx<INTERFACE MAC ADDRESS> following an upgrade.

No addressing or other reachability issues are encountered in this condition.

Prerequisites

This behavior is only expected to occur on Engines deployed in Amazon Web Services (AWS) EC2.

Applicable Delphix Versions

Click here to view the versions of the Delphix engine to which this article applies
Date Release
Feb 13, 2023 8.0.0.0
Jan 12, 2023 7.0.0.0
Releases Prior to 2023
Major Release All Sub Releases
6.0

6.0.0.0, 6.0.1.0, 6.0.1.1, 6.0.2.0, 6.0.2.1, 6.0.3.0, 6.0.3.1, 6.0.4.0, 6.0.4.1, 6.0.4.2, 6.0.5.0, 6.0.6.0, 6.0.6.1, 6.0.7.0, 6.0.8.0, 6.0.8.1, 6.0.9.0, 6.0.10.0, 6.0.10.1, 6.0.11.0, 6.0.12.0, 6.0.12.1, 6.0.13.0, 6.0.13.1, 6.0.14.0, 6.0.15.0, 6.0.16.0, 6.0.17.0, 6.0.17.1, 6.0.17.2

5.3

5.3.0.0, 5.3.0.1, 5.3.0.2, 5.3.0.3, 5.3.1.0, 5.3.1.1, 5.3.1.2, 5.3.2.0, 5.3.3.0, 5.3.3.1, 5.3.4.0, 5.3.5.0, 5.3.6.0, 5.3.7.0, 5.3.7.1, 5.3.8.0, 5.3.8.1, 5.3.9.0

5.2

5.2.2.0, 5.2.2.1, 5.2.3.0, 5.2.4.0, 5.2.5.0, 5.2.5.1, 5.2.6.0, 5.2.6.1

5.1

5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0, 5.1.10.0

5.0

5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1, 5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4

Explanation

Ultimately, this behavior is by-design.  As a result of changes in infrastructure when EC2 virtual machines are migrated between instances, the topology of the virtual hardware interface may change, resulting in the legacy ens# adapter identifiers in Delphix to change unexpectedly, and causing confusion.

In order to mitigate this behavior, Delphix versions 6.0.17.0 and later have updated their behavior to create a more predictable, and consistent, naming convention for when these toplology changes occur. The MAC address of the virtual adapter will remain consistent.

When this behavior is observed, no Support engagement is required and no functional difference should be observed; network interface addressing and routing should be consistent with that applied prior to upgrade.

 

 


Related Articles

The following articles may provide more information or related information to this article:

  • N/A