Troubleshooting guide

Chapter 9 Troubleshooting Active Network Management Fail-over in High Availability Applications
Advanced Technical Reference Guide 4.1 • June 2000 105
# Test Description Test Configuration Expected result Remarks
4. Disconnect 1interface
from the primary machine,
then 1interface from the
secondary, plug back
(secondary first).
Try the opposite.
Cluster machines in
Active-up High
Availability (HA)
mode.
The active machine should be the
one with most active interfaces and
remain so even if a machine with a
lower serial number has the same
amount of active interfaces.
Resolving Common Fail-Over Problems
This section lists some common problems and solution from the Check Point Technical Services
SecureKnowledge knowledge base.
Whenever the primary returns to service it does not take over as the primary
machine
The cause for this is that the "Return control to the highest priority ready machine" box, is not checked on both
the primary and the secondary modules.
To fix this, check the "Return control to the highest priority ready machine" box, on both the primary and the
secondary modules.
Sometimes Whenever the primary returns to service it does not take over as the primary machine – even though
the High Availability tab has been set correctly for the primary and "Return control to the highest priority ready
machine" is checked in NT or primary is set to primary-up in Solaris. This issue is presently under investigation
See the SecureKnowledge Solution (ID: 55.0.6797869.2673485) in the Check Point Technical Services site
How to address external interfaces for High Availability for Automatic Failover
External interfaces must have identical IP addresses for High Availability (HA) to work properly.
See the SecureKnowledge Solution (ID: 47.0.1736725.2532249) in the Check Point Technical Services site