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

# sk182622 - "CloudGuard Controller is not responding" error in SmartConsole after installing Jumbo Hotfix Accumulator

| Property | Value |
|----------|-------|
| Solution ID | sk182622 |
| Date Created | 2024-08-26 |
| Last Modified | 2024-09-08 |
| Technical Level | General |
| Products | Security Management Server, Cloud Firewall, Multi-Domain Security Management Server |
| Versions | R81.20, R81.10 (EOS), R81.10 (EOS), R81.10 (EOS), R81.20, R81.20 |

## Symptoms

- SmartConsole displays a warning stating that the CloudGuard Controller is not responding after you install R81.20 Jumbo Hotfix Accumulator Take 79 or R81.10 Jumbo Hotfix Accumulator Take 158 on the Security Management Server/Multi-Domain Security Management Server:  

`
"Error: 'CloudGuard Controller' is not responding. Verify that 'CloudGuard Controller' is installed on the gateway.`  
`
If 'CloudGuard Controller' should not be installed verify that it is not selected in the Products List of the gateway (SmartConsole > Gateway > General Properties > Check Point Products List). This error may occur if the Security Cluster is in Multi-Version Cluster mode. After upgrading all the cluster members to the same version, this error should disappear".`

## Cause

The cause of the issue is an incorrect reference set in the *amon_fw.conf* file.

The issue does **not** effect the functionality of the CloudGuard Controller, but it displays an incorrect status, which can be confusing.  
To make sure that CloudGuard Controller is enabled and running, run the `vsec stat` command, for example:
`[Expert@management:0]# vsec stat`  
`CloudGuard Controller is `**enabled and running**  

`Usage:`  
` on Enable CloudGuard Controller`  
` off Disable CloudGuard Controller`

<br />

## Solution

This problem was fixed. The fix is included starting from:

* [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 84
* [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 165

Check Point recommends to always upgrade to the [Recommended version](https://support.checkpoint.com/results/sk/sk95746) ([Security Gateway](https://support.checkpoint.com/product/73) / [VSX](https://support.checkpoint.com/product/359) / [Security Management Server](https://support.checkpoint.com/product/184) / [Multi-Domain Security Management Server](https://support.checkpoint.com/product/166) / [SmartConsole](https://support.checkpoint.com/product/191)).

If you choose not to upgrade, [contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for your version.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing it.  
For faster resolution and verification, collect these files:

1. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Management Server involved in the case.
2. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Security Gateway / each Cluster Member involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://support.checkpoint.com/results/sk/sk168597).

As a **workaround** , you can run these steps:**Important note:** Apply these steps **only** on **R81.20 Jumbo Hotfix Accumulator Take 79** or **R81.10 Jumbo Hotfix Accumulator Take 158**.

**For Security Management:**

1. Connect to the server with SSH and log in to expert mode.

2. Run: `amon_config cpstatdll add vSEC-Controller $FWDIR/lib vsec_monitoring_agent`

3. Run: `cpwd_admin stop -name CPD -path "$CPDIR/bin/cpd_admin" -command "cpd_admin stop"`

4. Run: `cpwd_admin start -name CPD -path "$CPDIR/bin/cpd" -command "cpd"`

**For Multi-Domain Security Management Server:**

1. Connect to the server with SSH and log in to expert mode.

2. To enter the applicable domain context run: `mdsenv <DOMAIN_IP>`

3. Run: `amon_config cpstatdll add vSEC-Controller $MDS_FWDIR/lib vsec_monitoring_agent`

4. Repeat steps 2 and 3 for each applicable domain.

5. Run: `mdsstop; mdsstart`

---

# 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