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

# sk185031 - SNMP MIB Import Fails for chkpnt-trap.mib

| Property | Value |
|----------|-------|
| Solution ID | sk185031 |
| Date Created | 2026-06-04 |
| Last Modified | 2026-06-09 |
| Technical Level | General |
| Products | Security Gateway, Security Management Server |
| Versions | R82.10, R82, R81.20, R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- An external SNMP manager cannot import the `chkpnt-trap.mib` file.

You see errors such as:
> `
> `Did not find 'multiDiskNameTrap' in module CHECKPOINT-MIB
> `
> `
>
> Did not find 'raidVolumeStateTrap' in module CHECKPOINT-MIB
> `
> `
>
> Did not find 'memTotalReal64Trap' in module CHECKPOINT-MIB
> `
> `

As a result:

* MIB compilation fails.
* Trap objects cannot be resolved by name.
* SNMP manager cannot fully load the Check Point MIB.

Notes:

* SNMP traps continue to work when referenced by Object Identifier (OID). Only name-based resolution is affected.
* This issue typically appears after upgrading from an earlier release.

## Cause

In affected builds, the `chkpnt-trap.mib` file includes IMPORT statements that reference symbols from the `CHECKPOINT-MIB` module.

Some of these referenced symbols (for example, `multiDiskNameTrap`, `raidVolumeStateTrap`) are not present in the target module.

This results in a mismatch that violates SNMP SMIv2 rules (standards for MIB structure and symbol resolution).

As a result:

* Standards-compliant SNMP managers cannot compile the MIB.
* Trap names cannot be resolved.
* MIB import fails.

## Solution

Resolution
----------

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

* [Check Point R82.10](https://support.checkpoint.com/results/sk/sk183506) starting from Take 103
* [Jumbo Hotfix Accumulator for R82](https://sc1.checkpoint.com/documents/Jumbo_HFA/R82/Default.htm) starting from Take 103
* [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 126

Check Point recommends to always upgrade to the [Recommended version](https://support.checkpoint.com/results/sk/sk95746).

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).

Post-Fix Verification
---------------------

After applying the fix (Hotfix or JHF):  

1. Reimport the updated MIB files into your SNMP manager:
   * `CHECKPOINT-MIB`
   * `chkpnt-trap.mib`
2. Verify that:
   * MIB compilation completes successfully.
   * Trap names are resolved correctly

Notes
-----

* This issue affects only MIB import and trap name resolution in third-party SNMP managers.
* SNMP traps continue to function when addressed by OID.
* Do not modify Check Point MIB files manually. Use only vendor-provided files.
* Keep the SNMP manager MIB database synchronized with the installed product version.
* Installing a Hotfix or JHF may require downtime. Plan a maintenance window.

---

# 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