sk182734 - Virtual System in a VSX VSLS Cluster with a Virtual Router does not fail over when a cluster interface is disconnected
Virtual System in a VSX VSLS Cluster with a Virtual Router does not fail over when a cluster interface is disconnected
Product
VSX (Traditional)
Version
R81.10 (EOS), R81.20, R82
OS
Gaia
Last Modified
2026-01-19
Symptoms
- Virtual Systems in a VSX VSLS Cluster that connect to a Virtual Router do not fail over when a cluster interface that belongs to one of these Virtual Systems is disconnected.
- Enabling Link Monitoring (setting the kernel parameter 'fwha_monitor_if_link_state = 1') on all interfaces does not resolve the issue.
Cause
Virtual Systems in a Virtual Router Group do not failover correctly when a cluster interface that belongs to a Virtual System is disconnected.
Background: A Management Server creates the corresponding Virtual Router Group automatically when you create a Virtual Router object. The Virtual Router in a Virtual Router Group manages all Virtual Systems in that Virtual Router Group. It makes sure all Virtual Systems are Active on the same VSX Cluster Member as the Virtual Router. If at least one Virtual System or the Virtual Router in the affected Virtual Router Group fails, all Virtual Systems and the Virtual Router in the same Virtual Router Group fail over from the affected VSX Cluster Member to another VSX Cluster Member.
Refer to the cphaprob show_vsls_groups command in the VSX Administration Guide for your version.
Solution
This problem was fixed. The fix is included in:
- Jumbo Hotfix Accumulator for R82 starting from Take 41
- Jumbo Hotfix Accumulator for R81.20 starting from Take 115
- Jumbo Hotfix Accumulator for R81.10 starting from Take 183
If you choose not to upgrade, Check Point can supply a Hotfix. Contact Check Point Support to get a Hotfix for this issue.
A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.
For faster resolution and verification, please collect CPinfo files from the Security Management Server and Security Gateways involved in the case.
Hotfix installation instructions: Refer to sk168597 - How to install a Hotfix.
NOTE
This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.
Article Properties
Access Level: General
Status: Approved by TAC
Date Created: 2024-10-09
Last Modified: 2026-01-19