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

# sk183958 - When adding Virtual Tunnel Interfaces (VTI) on a Standby Cluster Member, its cluster state temporarily changes to "DOWN"

| Property | Value |
|----------|-------|
| Solution ID | sk183958 |
| Date Created | 2025-09-15 |
| Last Modified | 2025-09-19 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20, R81.10 (EOS) |
| OS | Gaia |

## Symptoms

- * When adding Virtual Tunnel Interfaces (VTI) on a Standby ClusterXL Member, its cluster state temporarily changes from "STANDBY" to "DOWN" because the Critical Device "ROUTED" reports its state as "problem".

* When adding Virtual Tunnel Interfaces (VTI) on an Active ClusterXL Member, its cluster state does not change.

## Cause

This behavior is by design in ClusterXL environments running version R81.10 and higher.

These alerts and state transitions are expected during planned routing changes on the Standby ClusterXL Member and can be safely ignored.

When a Virtual Tunnel Interface (VTI) or a static route is added or modified on the Standby ClusterXL Member, the 'routed' daemon must restart to apply the new configuration.

To prevent a short outage or failback race condition (as seen in versions R81 and lower) on the Standby ClusterXL Member:

1. The Critical Device "ROUTED" reports its state as "problem" when such a configuration event occurs, regardless of whether the interface is used by a dynamic routing protocol.
2. The Standby ClusterXL Member changes its cluster state from STANDBY to DOWN.
3. The 'routed' daemon loads the new configuration.
4. The Critical Device "ROUTED" reports its state as "ok".
5. The Standby ClusterXL Member changes its cluster state from DOWN to STANDBY.

To prevent a short outage or failback race condition (as seen in versions R81 and lower) on the Active ClusterXL Member, the Critical Device "ROUTED" reports its state as "problem" only if the interface is used by a dynamic routing protocol.

This mechanism ensures cluster stability and prevents traffic impact during configuration changes, but results in expected alerts and state transitions on the Standby ClusterXL Member only.

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