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

# sk185064 - SNMP overall status OIDs for Application Control and URL Filtering return unknown values on Security Gateway

| Property | Value |
|----------|-------|
| Solution ID | sk185064 |
| Date Created | 2026-06-16 |
| Last Modified | 2026-06-18 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * SNMP queries to Application Control overall status OIDs return:  
  * Status code: `0`
  * An empty short description: `""`
  * An empty long description: `""`

  Affected OIDs:
  <!-- -->

  * .1.3.6.1.4.1.2620.1.39.101 (status code)
  * .1.3.6.1.4.1.2620.1.39.102 (short description)
  * .1.3.6.1.4.1.2620.1.39.103(long description)
* SNMP queries to URL Filtering overall status OIDs show the same result:  
  * .1.3.6.1.4.1.2620.1.43.101
  * .1.3.6.1.4.1.2620.1.43.102
  * .1.3.6.1.4.1.2620.1.43.103
* Application Control and URL Filtering blades show Healthy in SmartConsole and in `cpprod_util`.
* Other SNMP OIDs (for example, subscription status and database updates) return correct values.
* **Example**   
  Run on an SNMP manager (external host or NMS that queries the Security Gateway):  
  `$ snmpwalk -v2c -c <community_string> 192.168.1.10 .1.3.6.1.4.1.2620.1.39.101`  
  `SNMPv2-SMI::enterprises.2620.1.39.101 = INTEGER: 0`  
  `$ snmpwalk -v2c -c <community_string> 192.168.1.10 .1.3.6.1.4.1.2620.1.39.102`  
  `SNMPv2-SMI::enterprises.2620.1.39.102 = STRING: ""`  
  `$ snmpwalk -v2c -c <community_string> 192.168.1.10 .1.3.6.1.4.1.2620.1.39.103`  
  `SNMPv2-SMI::enterprises.2620.1.39.103 = STRING: ""`  
  **Note:** Do not use default community strings (for example, public) in production environments.

## Cause

The system collects detailed status metrics for Application Control and URL Filtering (such as subscription state and database updates).  
However, in this scenario:  

* The aggregated "overall status" values are not populated.
* Default placeholder values are used instead.

Data flow:  

* Internal component writes per-area values
* The `fwstatagent` process reads these values and exports them
* SNMP daemon retrieves the exported values
As a result, SNMP returns default values (0 and empty strings) for the overall status OIDs.

## Solution

[Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to obtain a Hotfix.

A Support Engineer will confirm compatibility with your environment.  
For faster resolution and verification, collect these files:

1. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Management Server
2. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from each Security Gateway / Cluster Member / Security Group
3. **Installation:**   
   Refer to [sk168597 - How to install a Hotfix](https://support.checkpoint.com/results/sk/sk168597).

**Verification**   
After applying the Hotfix:  

* Run the same SNMP query again
* Confirm that status code and descriptions show valid values

**Workaround (Optional)**   
Until the Hotfix is installed:  

* Monitor per-area SNMP OIDs (for example, subscription and update status) instead of overall status

**Notes**   

* This issue affects SNMP monitoring only.
* There is no impact on actual blade functionality

---

# 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