> Source: [sk172884](https://support.checkpoint.com/results/sk/sk172884)

# sk172884 - ping option and ip-reachability not working for a Standby cluster member

| Property | Value |
|----------|-------|
| Solution ID | sk172884 |
| Date Created | 2021-04-04 |
| Last Modified | 2021-04-07 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |

## Symptoms

- * When users use the 'set static-route' or 'set ip-reachability detection' command to set the ping option, the Active cluster member works as expected. Users see the ping request for the monitored IP address.
* After a fail-over, the new Active cluster member starts sending ping requests as expected.
* The Standby cluster member does not send a ping request to the monitored IP address. Note: This holds for the Standby cluster member's local IP address and its virtual IP address.
* The routing table of the Standby cluster member does not update according to the availability of the next hop.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content