Support Center > Search Results > SecureKnowledge Details
ClusterXL does not advertise BGP routes to Cisco router when configuring Cisco Loopback interface as neighbor IP address Technical Level
Symptoms
  • ClusterXL does not advertise BGP routes to Cisco router when configuring Cisco Loopback interface as neighbor IP address, although route redistribution to BGP was enabled on cluster members for interfaces and static routes.

  • BGP debug on cluster members shows (in /var/log/routed.log):

    bgp_rt_send_group_peer(X): local interface for peer PEER_IP_ADDRESS (Routing AS AS_NUMBER) is not defined
    bgp_rt_send_group_peer: peer PEER_IP_ADDRESS (Routing AS AS_NUMBER) write blocked after N routes sent
Cause

RouteD fails to retrieve the Cluster IP address (RouteD daemon replaces the nexthop field with its own IP Address. For clusters, this means RouteD has to retrieve the Cluster IP address.)


Solution

This problem was fixed. The fix is included in:

Check Point recommends to always upgrade to the most recent version.

 

For other versions, Check Point can supply a Hotfix. Contact Check Point Support to get a Hotfix for this issue.
A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.

 

Installation instructions:

  1. Install the improved package:
    [Expert@HostName]# rpm -Uvh --force routed*.rpm

  2. Restart RouteD daemon if needed:
    [Expert@HostName]# ps auxw | grep routed
    [Expert@HostName]# tellpm process:routed
    [Expert@HostName]# ps auxw | grep routed
    [Expert@HostName]# tellpm process:routed t
    [Expert@HostName]# ps auxw | grep routed
This solution is about products that are no longer supported and it will not be updated
Applies To:
  • 01074110 , 01074450 , 01074448
  • 00943284 , 01084509 , 01120612

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment