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

# sk116815 - Dynamic Routing protocols cannot be configured on non-Cluster interfaces

| Property | Value |
|----------|-------|
| Solution ID | sk116815 |
| Date Created | 2017-04-13 |
| Last Modified | 2017-04-19 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * After configuring Dynamic Routing protocols on a non-Cluster interface (whose "Network Objective" in the Cluster object's "Topology was set to "`1st Sync`", "`Non-Monitored Private`", or "`Monitored Private`"), the Dynamic Routing protocol is not working as expected.

* The following messages are displayed when querying an OSPF, RIP or PIM status on such non-Cluster interface:

  ```
  
  HostName> show ospf interface eth1
  RTGRTG0019  OSPF: interface eth1 not configured for OSPF
  
  HostName> show rip interface eth1
  RTGRTG0019  RIP: Interface eth1 is not running RIP
  
  HostName> show pim interface eth1
  Interface eth1 is not active.
  ```

## Cause

By design, on Cluster Members, Dynamic Routing can be configured only on Cluster interfaces, whose "Network Objective" in the Cluster object's "Topology was set to "Cluster" and Virtual IP address was configured.

RouteD daemon does not allow the Dynamic Routing protocols to initialize on non-Cluster interfaces.

## 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