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

# sk183336 - In ElasticXL in VSNext mode, traffic does not pass between Virtual Gateways that are connected through a Virtual Switch

| Property | Value |
|----------|-------|
| Solution ID | sk183336 |
| Date Created | 2025-05-21 |
| Last Modified | 2025-05-25 |
| Technical Level | Advanced |
| Products | Scalable Platforms |
| Versions | R82.10, R82 |
| OS | Gaia |

## Symptoms

- * When there are two or three ElasticXL Cluster Members in the status "Active" on the same ElasticXL Site (Load Sharing mode), traffic does not pass through the ElasticXL Cluster with the following VSNext topology:

  (Network 1) \<===\> \[ Virtual Gateway 1 \<===\> Virtual Switch \<===\> Virtual Gateway 2 \] \<===\> (Network 2)
* Traffic passes without problems when there is only one ElasticXL Cluster Member in the status "Active" on the ElasticXL Site.

* Kernel debug and traffic capture (when there are two or three ElasticXL Cluster Members in the status "Active" on the same ElasticXL Site) show that traffic is forwarded from the "Virtual Gateway 1" to the Virtual Switch, but the Virtual Switch fails to forward it further to "Virtual Gateway 2".

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