Fault fltAcRuleIpLatencyOperStFailed
                

Rule ID:2817


Explanation:
This fault occurs when either the total latency-stats rule reaches maximum programmable limit or an unsupported modification is made on an latency policy. The acRule for latency does not get programmed and is instead stuck in failed state.

Recommended Action:
To recover from this fault, try the following actions


  1. If the fault occurred because of a policy modification, disable and re-enable the latency policy with the changes.
  2. If the fault occurred because the maximum limit was reached, remove unneeded latency configuration policies to accommodate new policies.
  3. If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.

Raised on MO: ac:RuleIp

Fault Name: fltAcRuleIpLatencyOperStFailed

Unqualified API Name: latencyOperStFailed
Code: F2817
Applied Mo DN Format:
     topology/pod-[id]/node-[id]/sys/ac/ruleIp-[ruleId]
     sys/ac/ruleIp-[ruleId]

Type: operational
Cause: latency-rule-failed
Severity: minor
Weight: 100
Tags:
Message: Latency configuration for RuleruleId has failed due to latencyOperStQual

Help:

Triggered By:
         usage not equals 1u
        and
         latencyOperSt equals failed