Support Center > Search Results > SecureKnowledge Details
Interface flapping (down/up) in a ClusterXL environment Technical Level
Symptoms
  • SmartView Tracker logs show:

    "cluster_info: (ClusterXL) Interface Active Check on member N (x.x.x.x) detected a problem (Y interfaces required, only X up)"

  • SmartView Tracker logs show:

    "cluster_info: (ClusterXL) interface IF_NAME of member N (x.x.x.x) is down"

  • No functionality problems seen in cluster.

  • Each cluster interface is attached to a switch, and only one interface is flapping.

  • Following error can occur in kernel cluster debug (fw ctl debug -m cluster + stat) at the moment of this issue:

    FW-1: fwha_report_id_problem_status: State (FAILURE) reported by device Interface Active Check (blocking)
    FW-1: fwha_update_local_state: local (state STANDBY -> FAILURE)
    FW-1: fwha_set_new_local_state: entering with current state=STANDBY and new state=FAILURE
Cause

An interface can be flapping for several different reasons:

  • Due to IGMP Snooping enabled on switches
  • Due to multicast limits configured on switches
  • Latency in CCP packets
  • CCP packet loss on the network
  • etc

Refer to ClusterXL Administration Guide (R55, R60, R61, R62, R65, R70, R71, R75, R75.20, R75.40, R75.40VS, R76, R77, R80.10, R80.20, R80.30) - Chapter 'High Availability and Load Sharing in ClusterXL' - Hardware Requirements, Compatibility and Cisco Example


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