# SNMP OID .1.3.6.1.4.1.2620.1.6.7.5.1.5.X incorrectly shows 100% CPU utilization

**Product**: Security Gateways, Security Management  
**Version**: R81.20, R82  
**OS**: Gaia  
**Last Modified**: 2025-12-21

## Symptoms

- Running the `snmpwalk` command on OID .1.3.6.1.4.1.2620.1.6.7.5.1.5 (for example, `snmpwalk -v 2c -c public 127.0.0.1 .1.3.6.1.4.1.2620.1.6.7.5.1.5`), shows high CPU values for one or more CPUs.

- These CPU spikes are not detected by CPview, Spike Detective, or the `top` command.

- The spikes are seen on random CPUs.

- The spikes are seen even in lab environments where the appliances do not process traffic at all.

## Cause

- A calculation error causes false spikes to show.
- Even though these spikes are very brief, they can trigger traps that result in misleading high CPU alerts.

## Solution

This problem was fixed. The fix is included in:

- [Jumbo Hotfix Accumulator for R82](https://sc1.checkpoint.com/documents/Jumbo_HFA/R82/Default.htm) starting from Take 36  
- [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 111  
- [Jumbo Hotfix Accumulator for R81.10](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.10/Default.htm) starting from Take 183

If you choose not to upgrade, Check Point can supply a **Hotfix**. [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.

For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

**Hotfix installation instructions:**

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

#### NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

## Article Properties

**Access Level**: General  
**Status**: Approved by TAC  
**Date Created**: 2024-10-28  
**Last Modified**: 2025-12-21