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

# sk181418 - After a cluster failover, traffic stops flowing through VXLAN interfaces

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

## Symptoms

- * After a cluster failover, traffic stops flowing through VXLAN interfaces.

* Stopping the VXLAN connection and starting it again resolves the issue until the next cluster failover.

* Traffic capture with the FW Monitor tool ("`fw monitor -p all`") on cluster members shows that after a cluster failover, the cluster mechanism sends the VxLAN traffic from the new Active member to the Standby member (former Active) over the Sync interface.

  Example FW Monitor output:

  `
  [vs_0][fw_24] eth2:i16 (vpn tagging inbound)[44]: VIP -> IP_of_New_Active (UDP)`  
  `
  [vs_0][fw_24] eth2:i17 (vpn decrypt verify)[44]: VIP -> IP_of_New_Active (UDP)`  
  `
  [vs_0][fw_24] eth2:i18 (fw VM inbound )[44]: VIP -> IP_of_New_Active (UDP)`  
  `
  [vs_0][fw_24] eth2:I19 (vpn policy inbound)[44]: VIP -> IP_of_New_Active (UDP)`  
  `
  [vs_0][fw_24] eth2:I20 (fw SCV inbound)[44]: VIP -> IP_of_New_Active (UDP)`  
  `
  [vs_0][fw_24] eth2:I21 (vpn before offload)[44]: VIP -> IP_of_New_Active (UDP)`  
  `
  [vs_0][fw_24] eth2:I22 (fw offload inbound)[44]: VIP -> IP_of_New_Active (UDP)`  
  `
  [vs_0][fw_24] eth2:I23 (fw post VM inbound )[44]: VIP -> IP_of_New_Active (UDP)`  
  `
  [vs_0][fw_24] eth2:I24 `**(fw accounting inbound)[44]: VIP -> IP_of_Former_Active (UDP)**   
  `
  [vs_0][fw_24] eth2:I25 (RTM packet in)[44]: VIP -> IP_of_Former_Active (UDP)`  
  `
  [vs_0][fw_24] eth2:I26 (passive streaming (in))[44]: VIP -> IP_of_Former_Active (UDP)`  
  `
  [vs_0][fw_24] eth2:I27 (TCP streaming (in))[44]: VIP -> IP_of_Former_Active (UDP)`  
  `
  [vs_0][fw_24] eth2:I28 (IP Options Restore (in))[44]: VIP -> IP_of_Former_Active (UDP)`  
  `
  [vs_0][fw_24] eth2:I29 (Cluster Late Correction)[44]: VIP -> IP_of_Former_Active (UDP)
  `

## Cause

The cluster members hold all information about the connection.

After a cluster failover, the information about the VXLAN connection does not change.

As a result, the cluster mechanism hands over the VXLAN connection to the original cluster member (former Active) because it has the routing information for this connection.

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