High CPU for SND cores due to MQ configuration issues on VSX environment

Product: VSX (Traditional)

Version: R80.30 (EOS), R80.40 (EOS), R81 (EOS), R81.10 (EOS), R81.20, R82

Last Modified: 2025-01-27

Symptoms

• After a reboot, the CPU 0 SND core shows high usage, while other SND cores show very low usage compared to CPU 0.
• Some of the interfaces have only CPU 0 assigned as SND core, while other interfaces have all SND cores assigned.
• The $FWDIR/log/mq_mng.elg file of the relevant VS shows these error messages:

    [INFO] mq_interfaces.py:194:_init_real_interfaces(): interfaces_list = []
    ```

[ERROR] mq_mng:43:(): Error [grep: this version of PCRE is compiled without UTF support
```

    cat: /conf/vsname: No such file or directory
    ```

executing: [/etc/profile.d/vsenv.sh; CTX=`vsget`; vsenv 0 > /dev/null; $FWDIR/scripts/fwaffinity_used_cpus -r;]
```

    ./etc/profile.d/vsenv.sh; vsenv $CTX > /dev/null;
    ```

## Cause

Multi-Queue Management failed to enforce configuration on interfaces which are Virtual Systems outside of the global context.

## Solution

This problem was fixed. The fix is included in:

- [Jumbo Hotfix Accumulator for R82](https://sc1.checkpoint.com/documents/Jumbo_HFA/R82/Default.htm) starting from Take 10
- [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 90
- [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 75
- [Jumbo Hotfix Accumulator for R81](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81/Default.htm) starting from Take 106
- [Jumbo Hotfix Accumulator for R80.40](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk165456) starting from Take 126
- [Jumbo Hotfix Accumulator for R80.30](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk153152) starting from Take 255

If you choose not to upgrade:

A temporary solution to the issue is to run _cpstop;cpstart s_ everal times.

#### NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

## Article Properties

**Access Level**: General  
**Status**: Approved by TAC  
**Date Created**: 2021-06-16  
**Last Modified**: 2025-01-27