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

# sk185024 - Virtual System goes down due to unrelated interface monitoring

| Property | Value |
|----------|-------|
| Solution ID | sk185024 |
| Date Created | 2026-06-03 |
| Last Modified | 2026-06-04 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |

## Symptoms

- A Virtual System (VS) is in the **Down** state even though:

* The affected interface is not assigned to the VS.

* The affected interface should not be monitored in the context of non-VS0 VSs.

Additional Observations:

* The interface was previously configured as a slave in a bond.

* The bond was removed, and the interface was later reused as a standalone interface.

## Cause

This behavior can occur when an interface that was previously part of a bond is reused as a standalone interface.

In this scenario:

* The system retains internal association data from the previous bond configuration.

* The interface is still referenced in a global scope and may remain associated with VS monitoring.

* As a result, the interface is incorrectly evaluated in non-relevant VS contexts, which can cause the VS state to become **Down**.

## 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