Fault fltInfraLoNodeHealth

Rule ID:325


Explanation:
This fault occurs when a controller reports it has lost connectivity to the cluster replica leader for one or more data subsets for a service. The service cannot process requests in this state.

Recommended Action:
If you see this fault, take the following actions:

  1. Check cluster connectivity. All controllers need to be listed and reported as available using the apic command show controller or by looking at System->Controller ->First Controller-> Cluster as Seen By Node.
  2. Ensure that the cluster configuration is stable. Make note of any any frequent and brief interruptions of cluster availability or prolonged unavailability.
  3. Check that the service in question is running on all controllers using System->Controlers->First Controller ->Process.
  4. Check for any process crashes and cores.
  5. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

Raised on MO: infra:LoNode

Fault Name: fltInfraLoNodeHealth

Unqualified API Name: health
Code: F0325
Applied Mo DN Format:
     topology/pod-[id]/node-[id]/lon

Type: operational
Cause: unhealthy
Severity: critical
Weight: 100
Tags:
Message: Connectivity has been lost to the leader for some data subset(s) of a service on node id, the service may have unexpectedly restarted or failed.

Help:

Triggered By:
        leNotCnnct not equals 0u