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

# sk181231 - Output of the "dynamic_split -p "command shows "Dynamic Split is currently off (Stopped due to State Verification failure") on a VSX Security Gateway 

| Property | Value |
|----------|-------|
| Solution ID | sk181231 |
| Date Created | 2023-07-10 |
| Last Modified | 2025-06-23 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82, R81.20, R81.10 (EOS), R81 (EOS) |

## Symptoms

- * The output of the "`dynamic_split -p`" command on the VSX Security Gateway shows "`Dynamic Split is currently off (Stopped due to State Verification faliure)`".

* The `$FWDIR/log/dsd.elg` file on the VSX Security Gateway contains these lines:

  `update_fwk_affinity_vsx: setting all VSs {0-39} affinity to cores {1 2 3 4 5 6 7 8 9 10 11 13 14 15 16 17 18 19 20 21 22 23 25 26 27 28 29 30 31 32 33 34 35 37 38 39 40 41 42 43 44 45 46 47 12 36} failure running command "fw ctl affinity -s -d -vsid 0-39 -cpu 1 2 3 4 5 6 7 8 9 10 11 13 14 15 16 17 18 19 20 21 22 23 25 26 27 28 29 30 31 32 33 34 35 37 38 39 40 41 42 43 44 45 46 47 12 36 -override t". `

  rc:9 update_fwk_affinity_vsx: failed running affinity command
  `
  `

  ds_post_change_updates: Failed changing all VS affinity
  `
  `

  ds_change: Failed running post change updates
  **Note**: The output can be slightly different based on the number of virtual devices and CPU cores.

## Cause

The zombie processes are interfering with the CPU affinity settings. This can prevent the affinity command from properly assigning CPU resources.

## 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 25
* [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 101
* [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 177

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