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

# sk181249 - "cannot access /sys/class/net/<interface>/queues: No such file or directory" error in mq_mng.elg file

| Property | Value |
|----------|-------|
| Solution ID | sk181249 |
| Date Created | 2023-07-17 |
| Last Modified | 2024-03-13 |
| Technical Level | General |
| Products | Security Gateway, Multi-Domain Security Management Server |
| Versions | R81.20, R81.10 (EOS), R81 (EOS), R81 (EOS), R81.10 (EOS), R81.20 |

## Symptoms

- * After a reboot, the Multi-Queue configuration is incorrect when Management Data Plane Separation (MDPS), VSX, or both are enabled.   
  **Notes** :
  * Multi-Queue is set to auto.
  * CoreXL instances and interfaces are affined to the same CPU cores.
* The *mq_mng.elg* file contains these errors:

  <br />

  `[INFO] mq_driver.py:181:apply_state(): ` Apply state [1] queues num [20] cores  
  [0, 24, 1, 25, 2, 26, 3, 27, 4, 28, 5, 29, 6, 30, 7, 31, 8, 32, 9, 33] no_reset[False]  
  [ERROR] mq_mng:46:<module>(): Error [ls: cannot access   
  /sys/class/net/<interface>/queues: No such file or directory
* Example output of the `mq_mng -o` command:

  `eth2-01 i40e Up Dynamic (2/2) 18-35,54-71`

## Cause

The affinity settings do not apply to namespaces, and the namespaces do not appear in the */sys/class/net* directory of the Virtual System (VS), Management Plane (mplane), and Data Plane (dplane).  

As a result, Multi-Queue might affine CoreXL instances and interface queries to the same CPU cores.

<br />

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 43
* [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 131
* [Jumbo Hotfix Accumulator for R81](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81/Default.htm) starting from Take 89
* [Jumbo Hotfix Accumulator for R80.40](https://sc1.checkpoint.com/documents/Jumbo_HFA/R80.40/Default.htm) starting from Take 211

If you choose not to upgrade, Check Point can supply a **Hotfix** . [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 the Hotfix.  
For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk168597).

<br />

---

# 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