Two Check Point Cluster Members Routing Tables Differ

Check Point cluster routing table mismatch

How many times did you run into an outage that was caused by the fact that the secondary cluster member, which is now active, was missing a route?

Want to avoid routing table mismatches from happening again? Here’s a sample of an alert you’d get with indeni:

Description:

The routing tables for the following two cluster members do not match: they show different static routes. This could cause in problems during failover or under load sharing.

indeni will re-check this alert every 1 minute. If indeni determines the issue has been resolved, it will automatically be flagged as such.

Missing Routes:

  • 10.1.2.0/255.255.255.0 is routable from this device but not from CPG_01 (10.3.1.70)
  • 172.1.2.0/255.255.255.0 is routable from this device but not from CPG_01 (10.3.1.70)

Manual Remediation Steps:

Review the routing tables of both cluster members and resolve any discrepancies.

Leave a Reply