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

# sk181581 - Permanent tunnel cannot be monitored for a peer

| Property | Value |
|----------|-------|
| Solution ID | sk181581 |
| Date Created | 2023-10-24 |
| Last Modified | 2023-10-24 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R81.20, R81.10 (EOS) |

## Symptoms

- * When attempting an SNMP walk to the SNMP address of a peer configured with permanent tunnel state and set as either Dead Peer Detection (DPD) or passive, the operation fails and returns an error indicating that the SNMP instance for this configuration does not exist.
* The peer is configured in guide-edit as "DPD" or "PASSIVE". This is the case with third-party peers, but not only.
* Performing a snmpwalk to the permanent tunnel state SNMP address of a peer, which is configured as DPD, does not work and indicates as if the instance does not exist. For example:

  > `snmpwalk -v 2c -c datadog localhost .1.3.6.1.4.1.2620.500.9003.1.3.188.219.211.122.0
  > SNMPv2-SMI::enterprises.2620.500.9003.1.3.188.219.211.122.0 = No Such Instance currently exists at this OID`

## Cause

By design, the SNMP permanent tunnel state address is exclusively linked to permanent tunnels that use Check Point's proprietary tunnel monitoring.

<br />

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# 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