Support Center > Search Results > SecureKnowledge Details
Regarding ClusterXL and OSPF
Symptoms
  • OSPF trace file will show the OSPF state moving from Exch Start to Exchange, then instead of progressing, move back to Exch Start.

    Example of the trace file where 1 OSPF neighbor is 172.16.1.1 and the Cluster is 172.16.254.1:

    Jun 28 17:18:25.765427+0.000156 OSPF STATE: NGB 172.16.1.1 change from < Init > to < 2 Ways >
    ........................
    Jun 28 17:18:25.765427+0.000493 OSPF STATE: NGB 172.16.1.1 change from < Exch Start > to < Exchange >


  • OSPF may perform adjacency with Physical IP Address of a cluster member instead of the cluster Virtual IP address.
Cause

By default, connections originating from ClusterXL members are NATed behind the Cluster Virtual IP address.

The use of a manual "no-NAT" above the automatic NAT rules negates this operation.


Solution
Note: To view this solution you need to Sign In .