> Source: [sk185241](https://support.checkpoint.com/results/sk/sk185241) # sk185241 - Sync bond in ElasticXL loses its subordinate interface "eth1-Sync" after installing the R82.10 Jumbo Hotfix Accumulator | Property | Value | |----------|-------| | Solution ID | sk185241 | | Date Created | 2026-08-05 | | Last Modified | 2026-08-17 | | Technical Level | General | | Products | Scalable Platforms | | Versions | R82.10 | | OS | Gaia | ## Symptoms - * After installing the R82.10 Jumbo Hotfix Accumulator on the ElasticXL and rebooting, an ElasticXL member comes up without its Sync interface. The interface "`eth1-Sync`" is missing in the output of the Gaia gClish command "`show interfaces`" and the Expert mode command "`ip link`". * The Gaia gClish command "`show bonding group `" still shows the physical interface "`eth1-Sync`". * The Expert mode command "`cat /proc/net/bonding/Sync`" does not show any subordinate interfaces. * The `/var/log/messages` file contains this line: `ifm: Can't set up primary interface eth1-Sync for bond Sync` * The Expert mode command "`asg monitor`" reports: `Cluster in sync loss! Sync between sites is lost.` * On the affected ElasticXL member, the "`$FWDIR/log/blade_config`" file repeatedly shows: `Skipping configuration pulling. SMO has different ISO version` * On the affected ElasticXL member, the "`cphaprob state`" command may show that the cluster state is "`DOWN`" because the Critical Device (Pnote) "`pull_config`" reports its status as "`problem`". * This issue affects only the following Check Point appliance models in the ElasticXL configuration with the R82.10 Jumbo Hotfix Accumulator installed: * 3980 * 3970 * 3950 * 3920 ## Cause On these appliance models, the interface names come from a fixed file with UDEV rules in `/etc/udev/rules.d/`. This file with UDEV rules contains the name "`eth1-Sync`" for the Sync bond subordinate interface that overrides the factory port name. The Jumbo Hotfix Accumulator installation rebuilds this file from the factory configuration, which restores the factory port name. ## Solution **Table of Contents:** * Checking whether an appliance is affected * 3950 and 3920 appliances * 3980 and 3970 appliances * Manual recovery procedure ### Checking whether an appliance is affected {#TOC01} 1. Connect to the command line on the Security Group. 2. If the default shell is Gaia gClish, then log in to the Expert mode: `expert` 3. Run this command to check all Security Group Members at the same time. **Note** - A Security Group Member, whose Sync bond is already broken cannot be reached this way. On such appliance, connect locally over the console port. `gexec -a -c 'echo "== $(hostname) =="; grep -H NAME= /etc/udev/rules.d/00-*.rules; ip -o link show | grep -i sync'` If the output does not show "`NAME="eth1-Sync"`" on a Security Group Member, then that Security Group Member is affected. Follow the applicable section below. Summary table with port names: |-----------------|-------------------|----------------------| | Appliance Model | Factory Port Name | Physical "Sync" Port | | 3980 | `Sync` | yes | | 3970 | `Sync` | yes | | 3950 | `eth11` | no | | 3920 | `eth9` | no | **Explanation** - The UDEV rules file is read only at boot. Therefore, an appliance on which the Jumbo Hotfix Accumulator was already installed, but it has not rebooted yet, still shows the correct interface at runtime. However, its UDEV rules file is already wrong. That appliance will lose its Sync interface during the next reboot. ### 3950 and 3920 appliances {#TOC02} On these appliance models, do **not** install an [R82.10 Jumbo Hotfix Accumulator](https://sc1.checkpoint.com/documents/Jumbo_HFA/R82.10/Default.htm) take lower than Take 36. Starting from Take 36, the interface name "`eth1-Sync`" is applied automatically after the UDEV rules file is rebuilt. If a take lower than Take 36 was already installed, then follow the "Manual recovery procedure" below. ### 3980 and 3970 appliances {#TOC03} Restoring to factory defaults is **not** required to recover from this issue. Until the required fix is integrated into the R82.10 Jumbo Hotfix Accumulator, you must follow the recovery steps described below. If you need to install the R82.10 Jumbo Hotfix Accumulator on these appliance models (and it still does not contain the required fix), then after **every** Jumbo Hotfix Accumulator installation, you must follow the Manual recovery procedure on **each** ElasticXL member. ### Manual recovery procedure {#TOC04} 1. Connect to the command line on the Security Group. 2. If the default shell is Gaia gClish, then log in to the Expert mode: `expert` 3. Show the UDEV rules file and the current port names: `gexec -a -c 'echo "== $(hostname) =="; grep -H NAME= /etc/udev/rules.d/00-*.rules'` The output shows the UDEV rules file path and each port name. Example for the 3920 model: `/etc/udev/rules.d/00-BT-91-00.rules:SUBSYSTEM==... KERNELS=="0002:00:05.0", NAME="eth9"` If the output shows `NAME="eth1-Sync"` on an ElasticXL member, then no change is needed on that specific ElasticXL member. 4. Restore the name of the Sync subordinate interface using the factory port name. 1. Refer to the UDEV rules file path from Step 3. 2. Refer to the summary table with port names above to get the factory port name. Example for the 3920 model: 1. The UDEV rules file is "`/etc/udev/rules.d/00-BT-91-00.rules`". 2. The factory port name is "`eth9`". Syntax: |-----------------|-------------------|---------------------------------------------------------------------------------| | Appliance Model | Factory Port Name | Command to Run (substitute \ with the correct file) | | 3980, 3970 | Sync | `sed -i 's/NAME="Sync"/NAME="eth1-Sync"/g' /etc/udev/rules.d/.rules` | | 3950 | eth11 | `sed -i 's/NAME="eth11"/NAME="eth1-Sync"/g' /etc/udev/rules.d/.rules` | | 3920 | eth9 | `sed -i 's/NAME="eth9"/NAME="eth1-Sync"/g' /etc/udev/rules.d/.rules` | 5. Confirm the change: `gexec -a -c 'echo "== $(hostname) =="; grep -H NAME= /etc/udev/rules.d/00-*.rules'` 6. Reboot the ElasticXL members that have lost their subordinate interface "`eth1-Sync`". Reboot these affected ElasticXL members one at a time: `reboot -b ` Notes: 1. You can immediately reboot the ElasticXL members with the cluster state "DOWN". 2. Reboot the SMO Security Group Member last. 7. After rebooting all affected Security Group Members, make sure the subordinate interface "`eth1-Sync`" appears correctly with these commands in the Expert mode: 1. Run: `ip -o link show | grep -i sync` This command must show: `eth1-Sync: ` `Sync: ` 2. Run: `cat /proc/net/bonding/Sync` This command must show: `Slave Interface: eth1-Sync` ` MII Status: up` 3. Run: `cphaprob -a if` This command must show: `Interface Name: Status:` ` Sync (S) UP` 4. Run: `cphaprob state` This command must show: 1. "`ACTIVE`" in the column "`State`" 2. `Active PNOTEs: None` 5. On the SMO Security Group Member, the command "`asg monitor`" must not report sync loss anymore. --- # 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