> Source: [sk185133](https://support.checkpoint.com/results/sk/sk185133)

# sk185133 - Cloud Firewall Gateway port names change after a power cycle or migration in KVM-based platforms

| Property | Value |
|----------|-------|
| Solution ID | sk185133 |
| Date Created | 2026-07-12 |
| Last Modified | 2026-07-19 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82 |
| OS | Gaia |
| Platform | OpenStack, KVM, Huawei, Tencent, Proxmox, Qemu |

## Symptoms

- * On KVM-based platforms, Gaia network port names change after one of these events: a Virtual Machine (VM) power cycle, a VM migration, a network port attach, or a network port detach.
* A Cluster High Availability (HA) deployment does not operate correctly. Stable network port names are necessary for correct ClusterXL topology, IP address assignment, and Cloud Firewall Gateway configuration.
* Network ports become misaligned after a power cycle. For example, ports that were named `eth2`, `eth3`, and `eth4` change to different `eth` names.
* Some network ports show temporary or conflict names after a power cycle, such as `_rename_ren`.
* Deployments with more than 10 network ports show an incorrect port order. For example, the system processes `eth10` before `eth2`.

## Cause

On KVM-based platforms, Gaia network port naming depends on the Peripheral Component Interconnect (PCI) or bus ID mapping and on the Gaia-generated `udev` rules.  

The cloud platform does not make sure that the PCI or bus IDs stay the same during VM lifecycle events. These events include VM migration, port attach, port detach, and power cycle. As a result, Gaia can map a different operating system device to an existing `eth` name.
The only stable identifier that KVM and the Gaia guest operating system share is the MAC address.  

In addition, the Gaia services that generate network port naming rules read `/sys/class/net` in lexicographic order. On systems with more than 10 network ports, the services can process `eth10` before `eth2`. This order causes an incorrect port-to-device assignment.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content