[ PCA 3.x ] VNIC Name Changed After Compute Instance Stopped and Started - The lspci Command Shows Different Slot Assigned (Doc ID 3049311.1)

Last updated on SEPTEMBER 26, 2024

Applies to:

Symptoms

Prior to PCA 3.0.2-M3.9, a Compute Instance Secondary Virtual Network Interface (VNIC) is assigned to a different slot when the instance is stopped and started from the Compute Enclave User Interface (CEUI) or Oracle Cloud Infrastructure Command Line Interface (OCI CLI).

This causes its internal name be changed by the operating system running in the Compute Instance - for example with Oracle Linux 9 (OL9) the interface that was previously discovered as "ens5" becomes "ens4".

If there is software dependent on the device name, such as Oracle Clusterware, it would have to be reconfigured to use the new device name.

Changes

 The instance had never previously been shutdown from CEUI / OCI CLI, only rebooted from within, e.g. with the "reboot" command.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.