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

# sk167239 - FWM process consumes high CPU after enabling SmartEvent blade

| Property | Value |
|----------|-------|
| Solution ID | sk167239 |
| Date Created | 2020-06-05 |
| Last Modified | 2022-03-23 |
| Technical Level | General |
| Products | Security Management Server |
| Versions | R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- High CPU utilization by FWM process when SmartEvent is enabled on the Security Management Server.

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R81.10](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk175186) starting from Take 14
* [Jumbo Hotfix Accumulator for R81](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk170114) starting from Take 51
* [Jumbo Hotfix Accumulator for R80.40](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk165456) starting from Take 150
* [Jumbo Hotfix Accumulator for R80.30](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk153152) starting from Take 241
* [Jumbo Hotfix Accumulator for R80.20](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk137592) starting from Take 208

If you choose not to upgrade, the CalculateInternalNetwork needs to be run manually as a workaround.  

Steps to perform workaround:

1. Disable the SmartEvent blade in SmartConsole or by using the "`evconfig`" command and perform `cpstop; cpstart.`  

2. Add the *CONTROLLED_INTERNAL_NETWORK_CALCULATION* environment variable:
   1. Run: `# export CONTROLLED_INTERNAL_NETWORK_CALCULATION=1`
   2. Run: `# vi /opt/CPshrd-R80.xx/tmp/.CPprofile.sh`
   3. Add the following line at the end:   
      *CONTROLLED_INTERNAL_NETWORK_CALCULATION=1 ; export CONTROLLED_INTERNAL_NETWORK_CALCULATION*
   4. Save and close the file.
   5. Confirm the settings are enabled, run:  
      `# echo $CONTROLLED_INTERNAL_NETWORK_CALCULATION`Make sure that the output is 1
   6. Run:  
      `# mdsstop; mdsstart` on Multi-Domain Server   
      `# cpstop; cpstart` on Security Management servers.  

3. Make sure that FWM knows about the environment variable, run:   

   `# for pid in $(ps aux | grep fwm | grep -v grep | awk '{print $2}'); do cat /proc/$pid/environ | grep CONTROLLED_INTERNAL_NETWORK_CALCULATION -a; done`  

4. Run the `calculate_internal_network` manually using the `send_command` utility
   1. `# send_command -local -o calculate_internal_network`
   2. Wait until the calculation is done

The command will create a cache file - *var/tmp/internalNetworkSet* with the result   

5. Make sure the file */var/tmp/internalNetworkSet* was created. Run:  
`#ls -l /var/tmp/internalNetworkSet`

The SME will use the cache file instead of doing the calculation itself after enabling the SmartEvent blade.  

6. Log in to SmartConsole and enable the SmartEvent blade on the server.  

7. Publish the changes.   

<br />

**Note:** The *calculate_internal_network* command will need to be run on a daily basis with some cron job. Follow sk77300 to set up a cron job that runs with a frequency of less than a day.

---

# 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