Adding or removing an interface in ClusterXL High Availability topology might cause fail-over

Support Center > Search Results > SecureKnowledge Details

Technical Level

Solution ID	sk57100
Technical Level
Product	ClusterXL
Version	All
OS	SecurePlatform 2.6, Gaia, Crossbeam XOS
Platform / Model	All
Date Created	08-Nov-2010
Last Modified	22-Sep-2020

Symptoms

Adding or removing an interface (either physical, or logical (e.g. VLAN)) in ClusterXL High Availability topology might cause fail-over due to Critical Device "Interface Active Check" reporting its state as "problem".

Cause

Adding an interface (either physical, or logical) on a cluster member is done in Operating System. Check Point kernel always attaches itself to the interface. As a result, Cluster Layer also detects a new interface, and by design, expect to receive and to send CCP packets through that interface. Since this new interface is not defined yet in cluster Topology, CCP packets will not be sent/received through that interface. As a result, Cluster Layer declares that interface as failed, which in turn causes fail-over.

Removing an interface (either physical, or logical) on a cluster member cause the Cluster Layer to detect less interfaces than on the other member. By design, fail-over occurs in such case.

Solution

Note: To view this solution you need to Sign In .