Document navigation

Problem description

After a Kylin V10 SP2 ARM compute node is upgraded to MLNX_OFED 5.8 LTS, the NIC interface naming rules may change. Interface names are determined jointly by the operating system udev, kernel, and firmware naming mechanisms. Therefore, NIC names after the node restarts may differ from those before the upgrade.

If the bridge, management network, or storage network configuration continues to reference the original interface names, the related network configuration may need to be reconfirmed and adjusted.

Symptoms

  • After the MLNX_OFED driver is upgraded and the compute node restarts, an original NIC name no longer exists or has changed.
  • ip link shows Mellanox physical NIC names that differ from those before the upgrade.
  • Bridges, management networks, or storage networks that use the original interface names may fail to start properly.

Impact

NIC name changes may affect management network, service network, or storage network configurations that depend on fixed interface names. The interface mapping and network status must be reconfirmed after the driver upgrade and restart.

Workaround

  1. Before the upgrade, record the MAC address, PCI address, current interface name, and network purpose of each Mellanox NIC.
  2. Back up the compute node network configuration and schedule a maintenance window for the node.
  3. Configure persistent interface naming rules according to the NVIDIA documentation for the corresponding MLNX_OFED version and the Kylin operating system specifications.
  4. After the upgrade, verify the mapping between NIC names and MAC/PCI addresses before restoring bridges and service networks.
  5. Exit maintenance mode only after confirming that the management, storage, and service networks are operating properly.

If interface names have changed, create udev persistent naming rules based on the MAC/PCI information saved before the upgrade. The specific rules must be confirmed by technical support based on the server BIOS, Kylin version, and driver version. Directly copying rules from another environment is not recommended.

Affected products

  • Environments running ZStack Cloud 4.8.x, 5.4.x, or 5.5.x that use Kylin V10 SP2 ARM compute nodes and upgrade the Mellanox NIC driver to MLNX_OFED 5.8 LTS.
  • Other combinations of operating systems, CPU architectures, and MLNX_OFED versions are outside the confirmed scope of this article. Validate interface naming behavior separately before upgrading.

Fix status

  • Current status: Confirmed; a workaround is available.
  • Fixed version: No separate fixed version.
  • Related patch/fix package: None. Mitigate the issue through pre-upgrade checks and persistent NIC naming rules.
NIC names may change after upgrading the Mellanox driver in a Kylin ARM environment | 产品已知问题 · KB | ZStack Resource Center