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

# sk170675 - Rule-base Hit Count is not updated by R80.20SP Virtual Systems (VSs) on SmartConsole

| Property | Value |
|----------|-------|
| Solution ID | sk170675 |
| Date Created | 2020-11-25 |
| Last Modified | 2021-09-23 |
| Technical Level | General |
| Products | Security Gateway, Scalable Platforms |
| Versions | R82.10, R82, R81.20, R82, R81.20 |

## Symptoms

- Rule base Hit Count is not updated by R80.20SP VSs.

## Cause

Hit Count information is normally broadcasted between SGMs over port 2357.   

However, on VSs, the FWD process does not listen to these ports; the FWD process on non-VS0 on non-SMO does not listen to port \<2357+VSID\>.  

For example, VS2 on SGM2 does not listen to port 2359.   

To confirm this, run: `g_all netstat -tulpn | grep <2357+VSID>`

<br />

## Solution

This problem was fixed. The fix is included in:

* [Jumbo Hotfix Accumulator for R80.20SP](https://supportcenter.us.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk155832) starting from Take 314

**Workaround for existing VS is also available:**   

1. Configure the Hit Count registry port for each VS (vsenv \<VSID\>):  

`# g_all cpprod_util CPPROD_SetValue FW1 HitCountLogPort 1 <2357+VSID> 1 `  

**Example:**  
`# g_all cpprod_util CPPROD_SetValue FW1 HitCountLogPort 1 2357 1 (For VS0)`  
`# g_all cpprod_util CPPROD_SetValue FW1 HitCountLogPort 1 2358 1 (For VS1)`  
`# g_all cpprod_util CPPROD_SetValue FW1 HitCountLogPort 1 2359 1 (For VS2)`

2. Reboot one chassis at a time.   

3. Make sure you run traffic on all members for each VS.   

4. Install policy on all VSs.   

5. Verify that the FWD on each member listens to the relevant ports (2357+VSID).   

**Example:**  
`# g_all netstat -tulpn | grep 2357`  
`# g_all netstat -tulpn | grep 2358`  
`# g_all netstat -tulpn | grep 2359`  
This step could take a few minutes.

To verify the solution:  

1. Run traffic on VS1 that reaches a non SMO member (same traffic you ran in the last session).  

2. On the Management GUI, verify that you are getting the hits: right-click on the rule \> Hit Count \> Refresh.   

If it is not updated due to a Hit Count issue on the Management side. A workaround is to close the GUI and open it again.  

**Workaround for future VSs:**   
1. Back up the following file on the SMO:  
`# cp $FWDIR/scripts/vsx_create_all_vs_dirs_script.bash $FWDIR/scripts/vsx_create_all_vs_dirs_script.bash_original`  

2. Edit the following file on the SMO:  
`# vi $FWDIR/scripts/vsx_create_all_vs_dirs_script.bash`  

3. At the end, before the line "`reset_env_vars`", copy the following line:  
``$CPDIR/bin/cpprod_util CPPROD_SetValue FW1 HitCountLogPort 1 `expr 2357 + $vs_id` 1``  

4. Save the file and copy it to all members:  
`# asg_cp2blades $FWDIR/scripts/vsx_create_all_vs_dirs_script.bash`  
To confirm that the changes took place, run the following command from the VS level (vsenv VSID):  
`# g_all cpprod_util CPPROD_GetValue FW1 HitCountLogPort 1`

---

# 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