- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Secondary gateway cannot ping its default gateway.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Secondary gateway cannot ping its default gateway.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can it ping if it becomes active?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We've not tried that yet. At the moment the site is live and we cannot have any downtime.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This may be normal, depending on the details of your configuration. With R80.40 and up, traffic from standby goes through sync interface towards the active member, see sk167453.
Try running traces to see where packets are "lost".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
All we are getting is "network unreachable" from traces and pings. Regardless of active/standby status, the device should be able to ping its own default gateway. The route is not even showing as active in the routing table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please look into the SK I already provided, you will see that it is a bit more complicated with ClusterXL
Assuming you have policy installed on the new appliance, and the cluster is running in Active/Standby, it should be all good.
However, by traces I mean, try to understand where exactly ICMP is broken. You can do that by running "fw monitor" on both standby and active cluster members. You can also check logs for drops of the relevant traffic.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oh boy, I just re-read your post, you are running an unsupported R80.30. This changes everything.
Please look into a similar thread in the community: https://community.checkpoint.com/t5/Security-Gateways/ClusterXL-standby-cannot-reach-gateway/m-p/257...
