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

# sk181229 - Policy installation causes network interruption after enabling Multi-Queue and rebooting the Security Gateway

| Property | Value |
|----------|-------|
| Solution ID | sk181229 |
| Date Created | 2023-07-24 |
| Last Modified | 2023-07-30 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R81.20, R81.10 (EOS), R81 (EOS) |

## Symptoms

- * When: -Bridge mode is configured - [sk101371](https://support.checkpoint.com/results/sk/sk101371),

  -Link State Propagation (LSP) is enabled - [sk108121](https://support.checkpoint.com/results/sk/sk108121),

  the output of the "*mq_mng --show*" command shows an incorrect amount of affined CPU cores:
  > Total 72 cores. Multiqueue 42 cores  
  > i/f type state mode cores  
  > ------------------------------------------------------------------------------------------------  
  > Mgmt igb Up Dynamic (8/8) 0,36,1,37,2,38,3,39  
  > **eth1-01 ixgbe Up Dynamic (10/16) 0,1,2,3,4,36,37,38,39,40**   
  > **eth1-02 ixgbe Up Dynamic (5/24) 0,1,2,3,4**
* These messages appear in the output of *dmesg*:

  > \[xx.xx.xx\] br1: port 1(eth1-01) entered blocking state  
  > \[xx.xx.xx\] br1: port 1(eth1-01) entered forwarding state  
  > \[xx.xx.xx\] ixgbe 0000:b3:00.0: removed PHC on eth1-01  
  > \[xx.xx.xx\] \[fw4_0\];fw_lsp_manual_propagate_link_if_needed: Link State Propagation mechanism: Link on interface eth1-02 is Up, Opening paired device eth1-01  
  > \[xx.xx.xx\] br1: port 1(eth1-01) entered disabled state

## Cause

**Note:** Link state propagation forces the configured interfaces to have the same link state at all times.  

During the booting sequence, the system assigns CPU cores to the network interfaces. This procedure causes the network interface to shut down and restart, leading its peer network interface to also shut down, thereby causing the system to incorrectly apply the CPU cores to the peer interface.  

The first policy installed after booting to the OS causes the system to reapply the Multi-Queue configuration. This causes the interface to restart again.

## Solution

[Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing it.  
For faster resolution and verification, collect these files:

1. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Management Server involved in the case.
2. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Security Gateway / each Cluster Member involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://support.checkpoint.com/results/sk/sk168597).

---

# 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