Fault fltAcRuleIpOperStFailed
                
                    
                         Explanation:   
This fault occurs when either
                     the total Atomic Counter or Latency rule reaches maximum 
                     programmable limit or an unsupported modification is
                     made on an Atomic counter or Latency policy. The acRule does
                     not get programmed and is instead stuck in failed 
                     state. 
 
                         Recommended Action:   
 To recover from this fault,
                     try the following actions 
                     
Fault Name: fltAcRuleIpOperStFailed
                         Unqualified API Name: operStFailed
                         
                         Code: F1680
                         
                         Applied Mo DN Format: 
                         
                                  topology/pod-[id]/node-[id]/sys/ac/ruleIp-[ruleId]
                             
                                  sys/ac/ruleIp-[ruleId]
                             
                         
                         Type: operational
                         
                         Cause: ac-provisioning-failed
                         
                         Severity: minor
                         
                         Weight: 100
                         
                         Tags: 
                         
                         Message: 
ruleId configuration for tenantName vrfName has failed due to operStateQual
                         
                         Help: 
                         
                         
                         Triggered By: 
                         
                                    operState equals failed