sk181281 - "fwmultik_predefined_dispatching: BAD_MULTIK_TAG:got bad instance..." appears in /var/log/messages
"fwmultik_predefined_dispatching: BAD_MULTIK_TAG:got bad instance..." appears in /var/log/messages
Product
VSX (Traditional)
Version R80.40 (EOS), R81 (EOS), R81.10 (EOS), R81.20
Last Modified 2024-03-13
Symptoms
- This message is constantly appears in the
/var/log/messagesfile of a VSX gateway:
[DATE TIME] Host kernel: [fw4_0];fwmultik_predefined_dispatching: BAD_MULTIK_TAG::got bad instance 1 from multik tag, vsid: 0 caller fwmultik_dispatch_outbound
[DATE TIME] Host kernel: [fw4_0];fwmultik_predefined_dispatching: BAD_MULTIK_TAG::got bad instance 3 from multik tag, vsid: 0 caller fwmultik_dispatch_outbound
- There is no connectivity effect/impact.
Solution
This problem was fixed. The fix is included in:
- Jumbo Hotfix Accumulator for R81.20 starting from Take 43
- Jumbo Hotfix Accumulator for R81.10 starting from Take 131
- Jumbo Hotfix Accumulator for R81 starting from Take 89
- Jumbo Hotfix Accumulator for R80.40 starting from Take 211
If you choose not to upgrade, Check Point can supply a Hotfix. Contact Check Point 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 from the Security Management Server and Security Gateways involved in the case.
Hotfix installation instructions: Refer to sk168597 - How to install a Hotfix.
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 2023-07-21
Last Modified 2024-03-13