Support Center > Search Results > SecureKnowledge Details
VSX cluster member is "Down" due to Critical Device "Instances" in "problem" state
Symptoms
  • Output of "cphaprob state" command shows that the state of VSX cluster member is "Down".

  • Output of "cphaprob list" command shows that Critical Device "Instances" reports its state as "problem".

    Example:

    Device Name: Instances
    Registration number: 5
    Timeout: none
    Current state: problem
    Time since last report: 4229.9 sec
    
Cause

Chain of events:

  1. CCP packets sent between cluster members contain a field that carries the number of configured CoreXL FW instances on the cluster member that sends these CCP packets.
  2. In VSX HA mode (not VSLS) - each Virtual System (excluding VS0) checks the number of configured CoreXL FW instances in the received CCP packet and compares it to the number of loaded CoreXL FW instances on this Virtual System.
  3. If the number of CoreXL FW instances is different, then Critical Device "Instances" is registered in the kernel and its state is reported as "problem".
    By design, when any Critical Device reports its state as "problem", the state of the entire cluster member is change to "Down".
  4. As soon as the number of CoreXL FW instances is detected as identical, the Critical Device "Instances" is unregistered.

Such mismatch between the number of CoreXL FW instances in the received CCP packet and the number of loaded CoreXL FW instances on this Virtual System can be caused in the following scenarios:

  • Multiple clusters on the same subnet with identical values of 5th byte in Source MAC address of CCP packets, known as:

    • In ClusterXL running Gaia R77.30 and above:
      Cluster_Global_ID
    • In ClusterXL running Gaia R75.40-R77.20 / SecurePlatform / IPSO:
      fwha_mac_magic


  • Mismatch in CoreXL configuration between the members of this VSX cluster / Virtual Systems of this cluster.

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