%LOG_LOCAL0-1-SYSTEM_MSG [F1819][interface-fexfabric-invalid-xcvr][critical][DN of affected MO] Transceiver attached to fex fabric is invalid
This fault occurs when an unsupported transceiver is used to attach to to the fabric link of a fex
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-3-SYSTEM_MSG [F1820][equipment-disk-limits-exceeded][minor][DN of affected MO] Disk usage for [path] is above normal
This fault occurs when the disk usage of a partiton increases beyond its threshold
To recover from this fault, try the following action
%LOG_LOCAL0-2-SYSTEM_MSG [F1821][equipment-disk-limits-exceeded][major][DN of affected MO] Disk usage for [path] is high
This fault occurs when the disk usage of a partiton increases beyond its threshold
To recover from this fault, try the following action
%LOG_LOCAL0-1-SYSTEM_MSG [F1822][equipment-disk-limits-exceeded][critical][DN of affected MO] Disk usage for [path] is critically high
This fault occurs when the disk usage of a partiton increases beyond its threshold
To recover from this fault, try the following action
%LOG_LOCAL0-4-SYSTEM_MSG [F1823][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-1-SYSTEM_MSG [F1824][obstacle][critical][DN of affected MO] Peer controller is incompatible: [incmptblReason]. The controller ID is [peerId], its version is [peerVersion]. Cluster Version is [clusterVersion]
This fault occurs when a controller is recognized as incompatible.
If you see this fault, take the following actions:
Step 1 The message included with the fault will also include a reason the controller is recognized as incompatible. Investigate the reason and correct it.
Step 2 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1827][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1828][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1830][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1831][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1832][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1833][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1834][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1835][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1836][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1837][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1838][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1839][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1840][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1852][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1853][policy-limit-exceeded][warning][DN of affected MO] Number of [oCl] exceeds supported fabric-wide limit of [limit]
This fault occurs when the number of policies of this type exceed the supported fabric-wide limit.
If you see this fault, take the following actions:
Step 1 Modify your configuration so that the total number of these policies are under the supported limit.
%LOG_LOCAL0-4-SYSTEM_MSG [F1859][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1861][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1862][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1863][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1865][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-2-SYSTEM_MSG [F1867][fabric-recovery-enabled][major][DN of affected MO] Fabric recovery is in progress
This fault occurs when a fabric is in recovery mode
If you see this fault, take the following actions:
Step 1 Wait until fabric is full recovered (all appliances and switched are in-service
%LOG_LOCAL0-4-SYSTEM_MSG [F1869][policy-limit-exceeded][warning][DN of affected MO] Number of [oCl] exceeds supported scope limit of [limit]
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F1887][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-1-SYSTEM_MSG [F1888][config-mismatch][critical][DN of affected MO] Native vlan is not configured on interface [id], but it is receiving MST(802.1s) BPDUs. This could result in a layer2 topology with a loop
This fault occurs when the native vlan is not configured on the interface but it is receiving MST (802.1s) BPDUs. It could lead to layer2 topology with a loop.
To recover from this fault, try the following actions
Step 1 Configure native vlan on the interface
Step 2 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F1889][configuration-failed][minor][DN of affected MO] Configuration restore job [name] failed to decrypt the following properties: [decryptErrors]
This fault occurs when configuration import fails to decrypt secure fields.
If you see this fault, take the following actions:
Step 1 Set the value manually for every secure field mentioned in the job object.
%LOG_LOCAL0-2-SYSTEM_MSG [F1890][power-state-deny][major][DN of affected MO] [descr] in slot [id] has power state changed to [pwrSt]
This fault typically occurs when the switch detects insufficient power for a card to power up and puts card in power denied state
To recover from this fault, try the following actions
Step 1 Verify power redundancy modes
Step 2 Increase the number of power supplies provisioned
Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC
%LOG_LOCAL0-4-SYSTEM_MSG [F1891][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-3-SYSTEM_MSG [F1893][configuration-failed][minor][DN of affected MO] Node [id] is not a spine and is marked as a route-reflector in the BGP Route Reflector Node Policy Endpoint (bgp:RRNodePEp) policy contained within the BGP Route Reflector Policy (bgp:InsPol) [name]
This fault occurs when a leaf is marked as a BGP route reflector
If you see this fault, take the following actions:
Step 1 Remove the leaf from the BGP Route Reflector Node Policy Endpoint (bgp:RRNodePEp) Policy and choose another node. Only spines can be BGP route reflectors..
Step 2 If the above actions did not resolve the issue, collect a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1904][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1905][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-1-SYSTEM_MSG [F1907][interface-management-down][critical][DN of affected MO] Port is down, reason:[operStQual]
This fault occurs when a port is set to up but the operational state is down
To recover from this fault, try the following actions
%LOG_LOCAL0-4-SYSTEM_MSG [F1909][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1911][too-many-destinations][warning][DN of affected MO] Syslog source is referring to a group ([tDn]) that contains too many remote destinations
This fault occurs when a firewall syslog source refers to a syslog group containing more remote destinations than the firewall supports (3).
If you see this fault, take one of the following actions:
Step 1 Remove excess remote destinations from the syslog group, so that total number is less than or equal to 3.
Step 2 Create a new syslog group with at most 3 remote destinations and point the firewall syslog source to it.
%LOG_LOCAL0-4-SYSTEM_MSG [F1912][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-2-SYSTEM_MSG [F1925][ipckt-ep-provisioning-failed][major][DN of affected MO] IpCktEP provisioning failure
This fault occurs when the IpCktEP configuration fails
If this fault is consistently happening, try the following actions
Step 1 Check if hardware supports this feature
Step 2 If the network connectivity is fine, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1940][equipment-failed][major][DN of affected MO] Power supply unit on Node [id] is failed
This fault occurs when the Power Supply Unit is in fail state
If you see this fault, take the following action:
Step 1 replace the power supply unit that is failed
Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1957][operator-action][major][DN of affected MO] Serial number [peerMbSn] for peer controller ID [peerId] requires APPROVAL / REJECTION / ERASURE
This fault occurs when it operator is expected to approve, reject or erase a controller?™s serial number.
If you see this fault, take either of the following actions:
Step 1 approve controller?™s serial number
%LOG_LOCAL0-4-SYSTEM_MSG [F1974][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1975][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-3-SYSTEM_MSG [F1976][configuration-failed][minor][DN of affected MO] Configuration is invalid due to [issue]
This fault occurs when there is incomplete or incorrect configuration, intermittent system errors.
If you see this fault, take the following actions:
Step 1 Look at the configuration for issues. Refer to the help on (vns:ConfIssue:issue) property for error explanantion
Step 2 Verify the configuration is correct and complete to resolve configuration related issues.
Step 3 The system should automatically recover from intermittent system errors and no action needs to be taken here.
Step 4 If the issue persists, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1991][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1992][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1993][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F1999][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2000][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2001][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2002][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-2-SYSTEM_MSG [F2008][dpp-resource-unavailable][major][DN of affected MO] DPP class failed due to hardware programming error
This fault occurs when DPP manager fails to activate a class due to hardware programming failure
To recover from this fault, try the following actions
Step 1 Look at any configuration issues
Step 2 Verify the configuration is correct/complete
Step 3 Delete the DPP class and add it back
Step 4 If the above actions did not resolve the issue, try rebooting the switch using CLI or GUI.
Step 5 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2009][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2011][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2012][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2013][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2014][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2015][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2016][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2031][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2041][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2042][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2043][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2044][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2060][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2065][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2067][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-3-SYSTEM_MSG [F2069][configuration-failed][minor][DN of affected MO] Configuration failed for [name], [name] [name], [name] due to [configIssues]
This fault occurs when under a given l3extLNodeP either one of following conditions is present: - there is a node deployment configuration but there is no path deployment configuration for that node; - there is a path deployment configuration but there is no node deployment configuration for the node where path is.
If you see this fault, take the following actions:
Step 1 Ensure that for every RsNodeL3OutAtt there is at least an RsPathL3OutAtt
Step 2 Ensure that for every RsPathL3OutAtt there is a corresponding an RsNodeL3OutAtt configured
%LOG_LOCAL0-3-SYSTEM_MSG [F2081][oper-issues][minor][DN of affected MO] Operational issues detected on security group: [name] in VM Controller:[name], VM Domain:[domName], VM Provider:[vendor], error: [remoteOperIssues]
This fault is raised when issues are detected with security group learned from vShield/NSX.
If you see this fault, take the following actions:
Step 1 Fix the issue by creating the security policy based on the fault description
Step 2 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2100][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2105][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-2-SYSTEM_MSG [F2107][dpp-config-error][major][DN of affected MO] Data Plane Policer configuration failed. Reason: [operStQual]
This fault occurs when Data Plane Policer policy fails.
To recover from this fault, try the following actions
Step 1 If the fault occurred because of an usupported configuration, remove the configuration.
Step 2 If the fault occurred due to a hardware programming error, try removing and re-applying the policy.
Step 3 If the fault occurred because the interface on which it was applied is down, try bringing up the link.
Step 4 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F2108][download-failed][major][DN of affected MO] Failed to sync the firmware image [name]
This fault occurs when a image is being replicated across all ifcs
If you see this fault, take the following actions:
Step 1 Verify the location where the firmware stored is reachable through scp/http request
Step 2 Verify the directory and file location exist
Step 3 Verify the firmware file is valid
Step 4 Verify the file has sufficient permissions
Step 5 Free-up firmware repo by deleting any stale/old images.
Step 6 Delete the image from repository and download again
Step 7 If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F2109][download-failed][major][DN of affected MO] Failed to sync the following firmware images [errorQual]
This fault occurs when a image is not synced across all ifcs
If you see this fault, take the following actions:
Step 1 Verify the location where the firmware stored is reachable through scp/http request
Step 2 Verify the directory and file location exist
Step 3 Verify the firmware file is valid
Step 4 Verify the file has sufficient permissions
Step 5 Free-up firmware repo by deleting any stale/old images.
Step 6 Delete the image from repository and download again
Step 7 If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2110][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2111][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-1-SYSTEM_MSG [F2121][configuration-failed][critical][DN of affected MO] vPC pairs are not configured in same zone
This fault occurs when a virtual Port Channel (vPC) policy is created but nodes are not part of same zone.
If you see this fault, take the following actions:
Step 1 Verify that corresponding fabric nodes are part of same zone configuration
Step 2 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2123][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-3-SYSTEM_MSG [F2132][oper-issues][minor][DN of affected MO] Operational issues detected on security group: [name] in VM Controller:[name], VM Domain:[domName], VM Provider:[vendor], error: [remoteOperIssues]
This fault is raised when issues are detected with security group learned from vShield/NSX.
If you see this fault, take the following actions:
Step 1 Fix the issue by deleting the security group policy/Epg
Step 2 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F2133][config-issues][major][DN of affected MO] Config Issues issues detected on security group: [name] in VM Controller:[name], VM Domain:[domName], VM Provider:[vendor] error: Multiple security group match same VNic
This fault is raised when multiple security groups match the same VNic.
If you see this fault, take the following actions:
Step 1 Change the security group criteria to match one VNic
Step 2 Delete the EPG policy and security group and re-add them again
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2145][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2147][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2148][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2149][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2167][config-failure][warning][DN of affected MO] vsan configuration failure
This fault is caused by a hardware programming failure
The system will periodically retry to program the hardware. If the failure is due to lack of hardware resources, free up resources by removing or simplifying existing configuration.
%LOG_LOCAL0-4-SYSTEM_MSG [F2168][config-failure][warning][DN of affected MO] BFD authentication configuration failure
This fault is caused by a hardware programming failure
The system will periodically retry to program the hardware. If the failure is due to lack of hardware resources, free up resources by removing or simplifying existing configuration.
%LOG_LOCAL0-4-SYSTEM_MSG [F2169][config-failure][warning][DN of affected MO] BFD interface address-family configuration failure
This fault is caused by a hardware programming failure
The system will periodically retry to program the hardware. If the failure is due to lack of hardware resources, free up resources by removing or simplifying existing configuration.
%LOG_LOCAL0-4-SYSTEM_MSG [F2170][config-failure][warning][DN of affected MO] BFD keepalive configuration failure
This fault is caused by a hardware programming failure
The system will periodically retry to program the hardware. If the failure is due to lack of hardware resources, free up resources by removing or simplifying existing configuration.
%LOG_LOCAL0-4-SYSTEM_MSG [F2185][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-2-SYSTEM_MSG [F2190][address-assignment-failed][major][DN of affected MO] Node (ID [id]) is configured with invalid role [configNodeRole]
This fault is raised when the configured node role doesn?™t match the role advertized by the node
If you see this fault, take the following actions:
Step 1 Reconfigure the nodeIdentity policy with correct role
Step 2 If the above actions did not resolve the issue, collect a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F2194][policy-deployment-failed][major][DN of affected MO] Failed to deploy policy [polDn] to service [svc] on node [ctx]Failed to deploy policy [polDn] to service [svc] on node [ctx]
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F2226][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2229][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2232][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2234][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2235][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-2-SYSTEM_MSG [F2238][operational-issues][major][DN of affected MO] Virtual Switch fault / [vleafIssues] / [faultDesc]
This fault is raised when there is an opertaional issue with respect to the OpFlex device
If you see this fault, take the following actions:
Step 1 From the fault description resolve the issue on the opflex device
Step 2 If the above actions did not resolve the issue, collect avs-tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F2239][operational-issues][major][DN of affected MO] Virtual Switch fault / [vleafIssues] / [faultDesc]
This fault is raised when there is an opertaional issue with respect to the OpFlex End Points.
If you see this fault, take the following actions:
Step 1 From the fault description resolve the issue for the end point
Step 2 If the above actions did not resolve the issue, collect avs-tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F2247][deployment-failed][major][DN of affected MO] Deployment of trunk EPG [faultDKey] failed on domain [name] due to [deployIssues]
This fault is raised when the trunk Endpoint Group cannot be deployed due to a missing or invalid configuration.
If you see this fault, take the following actions:
Step 1 Verify that a VLAN pool is associated to the VMM Domain.
Step 2 Verity that any encapsulation block of the trunk EPG is part of an encapsulation block in the VLAN pool.
Step 3 Review the fault message and add missing or remove invalid configuration.
Step 4 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2250][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2251][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2274][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2275][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2281][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2282][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2283][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2284][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-3-SYSTEM_MSG [F2299][configuration-failed][minor][DN of affected MO] Configuration is invalid due to [configIssues]
This fault occurs due to missing RP group range configuration.
If you see this fault, please create the RP group range configuration to fix validation errors.
%LOG_LOCAL0-4-SYSTEM_MSG [F2300][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2301][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2302][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2303][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2305][config-error][warning][DN of affected MO] L3 routing must be enabled when multicast is allowed on the bridge domain
This fault occurs when multicast is allowed on a bridge domain for which L3 routing is disabled.
If you see this fault, take the following actions:
Step 1 Enable L3 routing on the BD (set property "unicastRoute" to "yes") or disallow multicast (set property mcastAllow to "false")
Step 2 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC
%LOG_LOCAL0-3-SYSTEM_MSG [F2307][configuration-failed][minor][DN of affected MO] Configuration is invalid due to [configIssues]
This fault occurs due to invalid route map configuraiton. Only source specific route map is allowed.
If you see this fault, please fix the route map configuraiton.
%LOG_LOCAL0-3-SYSTEM_MSG [F2308][configuration-failed][minor][DN of affected MO] Configuration is invalid due to [configIssues]
This fault occurs due to invalid route map configuraiton. Only source specific route map is allowed.
If you see this fault, please fix the route map configuraiton.
%LOG_LOCAL0-3-SYSTEM_MSG [F2327][configuration-failed][minor][DN of affected MO] On node [id], fvMode is misconfiguredFor tenant [epgPKey], application profile [epgPKey], application EPG [epgPKey] on node [id] fvMode misconfiguration detected.For tenant [epgPKey], outside [epgPKey], external EPG [epgPKey] failed on node [id] fvMode misconfiguration detected.For tenant [epgPKey], outside [epgPKey], external EPG [epgPKey] failed on node [id] fvMode misconfiguration detected.For tenant [epgPKey], management profile [epgPKey], in-band EPG [epgPKey] failed on node [id] fvMode misconfiguration detected.For tenant [epgPKey], management profile [epgPKey], out-band EPG [epgPKey] failed on node [id] fvMode misconfiguration detected.
: This fault occurs when there is a mic-configuration for a given EPg/external vlan mode on a given node
: If you see this fault, take the following actions: - Verify that static configuration and EPg deployment via Attachable Entity Profile are all setting mode consistently For a given EPg/external vlan, mode should be consistently configured to untagged or untagged on all node interfaces. If the above conditions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2328][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-3-SYSTEM_MSG [F2330][configuration-failed][minor][DN of affected MO] Configuration is invalid due to [configIssues]
This fault occurs due to PIM is enabled on a layer 3 out that has external SVI interfaces.
If you see this fault, you may change the layer 3 out configure to get rid of the fault.
%LOG_LOCAL0-4-SYSTEM_MSG [F2331][protocol-igmp-state-limit-change][warning][DN of affected MO] Regular entries exceeded the threshold for interface [id]. Only [availRegEntries] entries remaining
This fault occurs when the state limit regular entries exceeds 80% of the maximum limit
To recover from this fault, try the following actions
Step 1 Delete some of the IGMP groups manually
Step 2 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2332][protocol-igmp-state-limit-change][warning][DN of affected MO] Reserved entries exceeded the threshold for interface [id]. Only [availRsvdEntries] entries remaining
This fault occurs when the state limit reserved entries exceeds 80% of the maximum limit
To recover from this fault, try the following actions
Step 1 Delete some of the IGMP groups manually
Step 2 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2333][protocol-igmp-state-limit-change][warning][DN of affected MO] Regular entries exhausted for interface [id]. Will use the available reserved entries
This fault occurs when the regular limit entries are exhausted but the reserved entries are still available. If a group matches the route map configured for the reserved entries, it will be learned else will be dropped
To recover from this fault, try the following actions
Step 1 Delete some of the IGMP groups manually
Step 2 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-1-SYSTEM_MSG [F2334][protocol-igmp-state-limit-change][critical][DN of affected MO] IGMP State limit reached for interface [id]. Please delete additional IGMP group entries manually
This fault occurs when the regular and reserved entries get exhausted or when the user configures the state limit value such that the regular/reserved limit value is lesser than the existing config or lesser than the existing number of IGMP entries. No additional groups will be learnt when this fault is hit
To recover from this fault, try the following actions
Step 1 Delete some IGMP groups manually
Step 2 Verify the configuration is correct/complete
Step 3 Reduce the number of prefixes exported into bgp
Step 4 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F2397][svcredir-provision-failed][major][DN of affected MO] PBR service source is in failed state, reason [operStQual].
This fault occurs when PBR service destination goes to failed state
To recover from this fault, try the following actions
Step 1 Check if hardware supports this feature
Step 2 Look at any configuration issues
%LOG_LOCAL0-2-SYSTEM_MSG [F2398][svccopy-provision-failed][major][DN of affected MO] copy service source is in failed state, reason [operStQual].
This fault occurs when copy service destination goes to failed state
To recover from this fault, try the following actions
Step 1 Check if hardware supports this feature
Step 2 Look at any configuration issues
%LOG_LOCAL0-3-SYSTEM_MSG [F2399][configuration-failed][minor][DN of affected MO] Configuration failedConfiguration failed for [epgPKey] node [id] [pathName] on FEX [extChId] due to [configQual]Configuration failed for [epgPKey] node [id] [pathName] due to [configQual]Configuration failed for node [id] [targetDn] due to [configQual]Configuration failed for [tDn] due to [configQual]Configuration failed for node [id] due to [configQual]Configuration failed for [epgPKey] due to [configQual]Configuration failed for [epgDn] due to [configQual]
This fault occurs when an End Point Group is incompletely or incorrectly configured.
If you see this fault, take the following actions:
Step 1 Look at the configuration for issues
Step 2 For insufficient-resources, this is due to overall there are not enough resources
Step 3 For invalid-vsan, this EPG?™s encap is not valid for the domain on which the EPG is configured
Step 4 For native-vsan-failure, multiple vsans are configured as native on the path
Step 5 For further details, refer to the documentation for fv:StorageIssues
Step 6 Verify the End Point Group configuration is correct and complete
Step 7 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F2404][configuration-failed][minor][DN of affected MO] Configuration is invalid due to [nwIssues]
This fault occurs because PIM is enabled on a VRF which is deployed on a a leaf which does not support multicast configuration.
If you see this fault, please disable PIM on of VRF that is deployed on on leaf that does not support multicast.
%LOG_LOCAL0-2-SYSTEM_MSG [F2405][interface-down][major][DN of affected MO] Port is down, reason:[operStQual]
This fault occurs when a VFC port is down
If you see this fault, take the following actions
Step 1 Check the port down reason and try resolving the issue
Step 2 Remove the configuration or administratively shut the port if the port is not in use
Step 3 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F2406][mac-limits-exceeded][major][DN of affected MO] Learning is disabled on if [name]
This fault occurs when the ep learning is disabled on interface
If this fault is consistently happening, try the following actions
Step 1 Check total number of MACs learnt on this interface
Step 2 Toggle the Port Security violation or change the maximum limit set for number of MACs that can be learnt on this interface
Step 3 If maximum limit is not set, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F2407][macckt-ep-provisioning-failed][major][DN of affected MO] MacCktEP provisioning failure
This fault occurs when the MacCktEP configuration fails
If this fault is consistently happening, try the following actions
Step 1 Check if hardware supports this configuration
Step 2 If the network connectivity is fine, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2409][config-error][warning][DN of affected MO] Configuration is invalid due to [configIssues].
This fault occurs when there are specific configuration errors on a bridge domain, but the igmpsnoop is disabled.
If you see this fault, take the following actions:
Step 1 For "igmpsnoop is disabled on multicast enabled BD" error, enable igmpsnoop (set adminSt in igmp:SnoopPol or disallow multicast (set property mcastAllow to "false")
Step 2 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC
%LOG_LOCAL0-3-SYSTEM_MSG [F2421][equipment-diags-failed][minor][DN of affected MO] Diagnostics test failed. reason:[operStQual]
This fault occurs when a diagnostic test fails.
The failed diagnostic test isolates the error to a port, card(FRU) or the entire switch. For port-level errors, the port are put in disabled state. For card or switch level errors, collect the show techsupport command output on the switch and contact Cisco TAC to eliminate any known software issues before replacing the hardware.
%LOG_LOCAL0-2-SYSTEM_MSG [F2428][operational-issues][major][DN of affected MO] Operational issues detected on Host: [name] for controller: [hostOrIp] with name [name] in datacenter [rootContName] in domain [domName] error: [[operIssues]]
This fault is raised when both the opflex channels for the host are down.
If you see this fault, take the following actions:
Step 1 Bring up the opflex channels back to their original state.
Step 2 If the above actions did not resolve the issue, collect avs-tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F2437][interface-down][minor][DN of affected MO] PortVsan not Up, reason:[operStQual]
This fault occurs when a VFC portVsan is down
If you see this fault, take the following actions
Step 1 Check the port down reason and try resolving the issue
Step 2 Remove the configuration or administratively shut the port if the port is not in use
Step 3 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F2438][vsan-failure][minor][DN of affected MO] Configured Vsan not UP, reason:Vsan configuration limit exceeded
This fault occurs when a Created Vsan count exceeds allowed limit on node
If you see this fault, take the following actions
Step 1 Check the number of allowed VSANS and deleted unused VSAN from node
Step 2 Please note if you configure more than supported VSANS first #num supported vsans will be created you could loose a working VSAN after switch reload.
Step 3 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2444][protocol-ospf-limits-exceeded][warning][DN of affected MO] Maximum ECMP Configuration [maxEcmp] has exceeded the recommended limit
This fault occurs when max-path configuration exceeds the recommended value
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F2445][traffic-map-config-fail][warning][DN of affected MO] Traffic map configuration failed, reason:[configStatus]
This fault occurs when traffic map configuration failed
If you see this fault, take the following actions
Step 1 Check if the configured NP port is the same as current one
Step 2 Remove the traffic map config, shutdown the F port and then config traffic map again
%LOG_LOCAL0-2-SYSTEM_MSG [F2446][interface-non-default-fecmode][major][DN of affected MO] Port has a non-default FEC mode configured
This fault occurs when a port is used by fabric and fec mode is not inherit
To recover from this fault, try the following actions
%LOG_LOCAL0-4-SYSTEM_MSG [F2447][config-failure][warning][DN of affected MO] NPV Traffic Map Configure Failure
This fault is caused by a hardware programming failure
The system will periodically retry to program the hardware. If the failure is due to lack of hardware resources, free up resources by removing or simplifying existing configuration.
%LOG_LOCAL0-4-SYSTEM_MSG [F2467][config-failure][warning][DN of affected MO] vfc port configuration failure
This fault is caused by a hardware programming failure
The system will periodically retry to program the hardware. If the failure is due to lack of hardware resources, free up resources by removing or simplifying existing configuration.
%LOG_LOCAL0-4-SYSTEM_MSG [F2481][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-4-SYSTEM_MSG [F2506][epg-provisioning-failed][warning][DN of affected MO] Allow Useg on EPG is not supported in this platform
This fault occurs when Allow Microsegmentation is enabled for an EPG in an unsupported platform
To recover from this fault, try the following actions
Step 1 Clear Allow Microsegmentation for this EPG
Step 2 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2507][epg-provisioning-failed][warning][DN of affected MO] Proxy Arp on EPG is not supported in this platform
This fault occurs when Proxy Arp is enabled for an EPG in an unsupported platform
To recover from this fault, try the following actions
Step 1 Clear Proxy Arp for this EPG
Step 2 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2508][epg-provisioning-failed][warning][DN of affected MO] Without enforcing intra-epg isolation, Proxy Arp on EPG is not supported
This fault occurs when intra-epg isolation is not enforced, but Proxy Arp is enabled for an EPG.
To recover from this fault, try the following actions
Step 1 Clear Proxy Arp for this EPG
Step 2 Or, enable intra-epg isolation enforced for this EPG
Step 3 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F2511][querier-layer2-layer3-conflict][warning][DN of affected MO] Switch querier has the same IP address as the SVI querier. Configure a different IP address / remove config when routing is enabled
This fault occurs when the switch querier is the same as the BD SVI querier
To remove this fault, configure a different switch querier IP address or remove the switch querier config if routing is enabled
Step 1 configure different IP for switch (layer-2) querier from the SVI querier or remove the switch querier config if routing is enabled
Step 2 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F2514][configuration-failed][minor][DN of affected MO] An out of service policy configuration has not been deployed on node [id], because: [deplSt]RsOosPath has not been deployed on controller/node [id] because: [deplSt]RsOosSlot has not been deployed on controller/node [id] because: [deplSt]
This fault occurs when an out of service policy has been created, but those policies have not been deployed to one or more fabric nodes.
If you see this fault, take the following actions:
Step 1 Verify that corresponding fabric node is ready to receive policies
Step 2 Verify that corresponding fabric node is part of the POD specified in the policy
Step 3 If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F2531][config-error][minor][DN of affected MO] Configuration is invalid due to [configIssues].
This fault occurs when there are specific configuration errors on EPG to VMM Domain Association.
If you see this fault, take the following actions:
Step 1 Change deployment immediacy to immediate and check if fault is cleared
Step 2 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC
%LOG_LOCAL0-4-SYSTEM_MSG [F2532][static-report-masklen-lesser][warning][DN of affected MO] Static report policy has masklen lesser than 24. Please provide masken = 24
This fault occurs when the IGMP static group policy has group mask of less than 24
To remove this fault, configure the static group policy route map with group mask of length greater than or equal to 24
Step 1 configure group masklen greater than or equal to 24 in the static group route map
Step 2 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-1-SYSTEM_MSG [F2533][protocol-mcp-topology-anomaly][critical][DN of affected MO] Loop is detected on lower priority MCP interface [id] in [loopDetVlan]
This fault occurs when a loop is detected
To recover from this fault, try the following actions
Step 1 Review the network topology and vlan configuration on the node and the peer
Step 2 If the above action did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-1-SYSTEM_MSG [F2534][protocol-mcp-topology-anomaly][critical][DN of affected MO] Loop is detected on higher priority MCP interface [id] in [loopDetVlan]
This fault occurs when a loop is detected
To recover from this fault, try the following actions
Step 1 Review the network topology and vlan configuration on the node and the peer
Step 2 If the above action did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F2542][analytics-agent-image-installation-failed][major][DN of affected MO] Image installation failed reason:[InstallOperStQual]
This fault occurs when Analytics agent Image installation failed on the switch
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F2543][invalid-configuration][major][DN of affected MO] Node [nodeId] with PodID [podId] has invalid configuration due to [configIssues]
This fault is raised when the podid provided does not exist
If you see this fault, take the following actions:
Step 2 If the above actions did not resolve the issue, collect a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F2547][nodeid-not-in-pod][major][DN of affected MO] Specified node not present in the specified pod [ctx]Specified node not present in the specified pod [ctx]
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-3-SYSTEM_MSG [F2560][change-in-fips-state][minor][DN of affected MO] Fips mode changed. Reboot needed
This fault occurs when FIPS 140-2 is enabled or disabled on the node
If you see this fault, a node reboot is required
Step 1 Check if a similar fault is generated on other nodes on fabric
%LOG_LOCAL0-3-SYSTEM_MSG [F2561][change-in-fips-state][minor][DN of affected MO] Fips mode changed. Reboot needed
This fault occurs when FIPS 140-2 is enabled or disabled on the switch node
If you see this fault, a node reboot is required
Step 1 Check if a similar fault is generated on other nodes on fabric
%LOG_LOCAL0-4-SYSTEM_MSG [F2562][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
The object refers to an object that was not found.
Make sure that referenced object exists and the name is spelled correctly in the relation object.
%LOG_LOCAL0-3-SYSTEM_MSG [F2563][callhome-msg-failure][minor][DN of affected MO] Callhome message failed to send to destination [email]. Please check smtp server config
This fault occurs when sending a callhome message to destination does not succeed.
If you see this fault, take the following actions:
Step 1 Verify destination information is correct.
Step 2 Ensure it is reachable (ping/ssh) from the fabric and DNS entries have been configured correctly.
Step 3 You may remove and reconfigure the syslog destination.
Step 4 If the above action did not resolve the issue, contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F2573][oobmgmt-ip-in-use][major][DN of affected MO] [oobMgmtAddr] of [name] is already in use.
This fault occurs when the controller out-of-band management IP address cannot be assigned as it is in use (local or remote).
If you see this fault, take the following actions:
Step 1 Identify the interface that is using this IP. For example: You can use linux utility ?™arping??to locate the MAC address of interface using the IP address. arping -I oobmgmt -c 1
Step 2 If above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F16438][connect-failed][warning][DN of affected MO] [FSM:STAGE:FAILED|RETRY]: Connect stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:Connect)
This fault is raised when Controller Connect Stage fails.
If you see this fault, take the following actions:
Step 1 Check the Controller Name, IP address and login credentials are correct
Step 2 This stage will be retried automatically. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F16438][get-inventory-failed][warning][DN of affected MO] [FSM:STAGE:FAILED|RETRY]: Inventory pull stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:GetInventory)
%LOG_LOCAL0-4-SYSTEM_MSG [F16438][get-timestamp-failed][warning][DN of affected MO] [FSM:STAGE:FAILED|RETRY]: Get Current Timestamp stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:GetTimestamp)
%LOG_LOCAL0-4-SYSTEM_MSG [F16438][init-failed][warning][DN of affected MO] [FSM:STAGE:FAILED|RETRY]: Init stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:Init)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F16438][online-failed][warning][DN of affected MO] [FSM:STAGE:FAILED|RETRY]: Online stage VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:Online)
%LOG_LOCAL0-4-SYSTEM_MSG [F16438][post-inventory-failed][warning][DN of affected MO] [FSM:STAGE:FAILED|RETRY]: Post Inventory stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:PostInventory)
%LOG_LOCAL0-4-SYSTEM_MSG [F16438][subscribe-events-failed][warning][DN of affected MO] [FSM:STAGE:FAILED|RETRY]: Event Registration stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:SubscribeEvents)
%LOG_LOCAL0-4-SYSTEM_MSG [F16443][cleanup-failed][warning][DN of affected MO] [FSM:STAGE:FAILED|RETRY]: Cleanup stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrRemove:Cleanup)
%LOG_LOCAL0-4-SYSTEM_MSG [F16443][cleanup2-failed][warning][DN of affected MO] [FSM:STAGE:FAILED|RETRY]: Extended Cleanup stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrRemove:Cleanup2)
%LOG_LOCAL0-4-SYSTEM_MSG [F16443][disconnect-failed][warning][DN of affected MO] [FSM:STAGE:FAILED|RETRY]: Disconnect stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrRemove:Disconnect)
%LOG_LOCAL0-4-SYSTEM_MSG [F16443][mit-clean-failed][warning][DN of affected MO] [FSM:STAGE:FAILED|RETRY]: MIT cleanup stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrRemove:MitClean)
%LOG_LOCAL0-4-SYSTEM_MSG [F16443][offline-failed][warning][DN of affected MO] [FSM:STAGE:FAILED|RETRY]: Offline stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrRemove:Offline)
%LOG_LOCAL0-4-SYSTEM_MSG [F16443][un-subscribe-events-failed][warning][DN of affected MO] [FSM:STAGE:FAILED|RETRY]: Unsubscribe Events stage VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrRemove:UnSubscribeEvents)
%LOG_LOCAL0-4-SYSTEM_MSG [F540726][connect-failed][warning][DN of affected MO] [FSM:STAGE:REMOTE-ERROR]: Connect stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:Connect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F540726][get-inventory-failed][warning][DN of affected MO] [FSM:STAGE:REMOTE-ERROR]: Inventory pull stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:GetInventory)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F540726][get-timestamp-failed][warning][DN of affected MO] [FSM:STAGE:REMOTE-ERROR]: Get Current Timestamp stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:GetTimestamp)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F540726][init-failed][warning][DN of affected MO] [FSM:STAGE:REMOTE-ERROR]: Init stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:Init)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F540726][online-failed][warning][DN of affected MO] [FSM:STAGE:REMOTE-ERROR]: Online stage VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:Online)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F540726][post-inventory-failed][warning][DN of affected MO] [FSM:STAGE:REMOTE-ERROR]: Post Inventory stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:PostInventory)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F540726][subscribe-events-failed][warning][DN of affected MO] [FSM:STAGE:REMOTE-ERROR]: Event Registration stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrAdd:SubscribeEvents)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F540731][cleanup-failed][warning][DN of affected MO] [FSM:STAGE:REMOTE-ERROR]: Cleanup stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrRemove:Cleanup)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F540731][cleanup2-failed][warning][DN of affected MO] [FSM:STAGE:REMOTE-ERROR]: Extended Cleanup stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrRemove:Cleanup2)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F540731][disconnect-failed][warning][DN of affected MO] [FSM:STAGE:REMOTE-ERROR]: Disconnect stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrRemove:Disconnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F540731][mit-clean-failed][warning][DN of affected MO] [FSM:STAGE:REMOTE-ERROR]: MIT cleanup stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrRemove:MitClean)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F540731][offline-failed][warning][DN of affected MO] [FSM:STAGE:REMOTE-ERROR]: Offline stage for VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrRemove:Offline)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-4-SYSTEM_MSG [F540731][un-subscribe-events-failed][warning][DN of affected MO] [FSM:STAGE:REMOTE-ERROR]: Unsubscribe Events stage VM Controller: [name] VM Domain: [domName] VM Provider: [name] Error: [remoteErrMsg](FSM-STAGE:ifc:vmmmgr:CompCtrlrRemove:UnSubscribeEvents)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F606210][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:ResConsumerRegister
This fault occurs when resource consumer registration (used for ID / resource tracking) fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606211][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:ResConsumerUnregister
This fault occurs when resource consumer unregistration (used for ID / resource tracking) fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606212][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:TagInstConfDef
This fault occurs when a tag reference configuration fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606213][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:TagAliasInstConfAliasDef
This fault occurs when an alias reference configuration fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606214][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:TagAliasDelInstDelAliasDef
This fault occurs when alias reference fails to be deleted
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606220][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:IdentSourceRelease
This fault occurs when an internal identifier fails to be released.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606233][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:dbgr:DbgexpNodeStatusRemoveFile
This fault is raised when sending export file name to correct APIC to remote it, fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606234][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:dbgr:SvccoreACoreSendCoreInfo
This fault is raised when task to send core MO info to correct shard fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606234][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:dbgrelem:SvccoreNodeSendCoreInfo
This fault is raised when task to report core info from node to APIC fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606236][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:extXMLApi:AaaUserResetAdminPasswd
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F606242][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:bootmgr:FirmwareSourcePopulateRepo
This fault occurs upon failure to update information about a downloaded image
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606243][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:bootmgr:FirmwareDownloadPopulateDownload
This fault occurs upon failure to update information about download
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606245][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:dbgrelem:DbgexpNodeStatusReportNodeStatus
This fault is raised when task to report export status from node to APIC fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606253][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:PconsResolverResolve
This fault is raised when the node (leaf/spine) fails to send the message to controller to resolve all its policies.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606262][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompCtrlrAdd
This fault is raised when FSM for Controller Add operation fails.
If you see this fault, take the following actions:
Step 1 Check if there are repeated failures of any FSM stage
Step 2 Perform the suggested actions to correct stage failures
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606267][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompCtrlrRemove
This fault is raised when FSM for Controller Remove operation fails.
If you see this fault, take the following actions:
Step 1 Check if there are any FSM stage failures
Step 2 Perform the suggested Actions to correct stage failures
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606274][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:ae:TopSystemSendTopSystem
This fault is raised when sending top System changes to Topology Manager fails
%LOG_LOCAL0-2-SYSTEM_MSG [F606277][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:ae:FirmwareCtrlrFwStatusContSendCtrlrRunning
This fault is raised when sending controller firmwareCtrlrRunning object to firmwareFwStatusCont fails
%LOG_LOCAL0-2-SYSTEM_MSG [F606278][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:ae:MaintNodeInMaintSendCtrlrUpgradeReq
This fault is raised when Appliance Element fails to send upgrade request to scheduler
%LOG_LOCAL0-2-SYSTEM_MSG [F606279][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:ae:FirmwareFirmwareLoadCatalog
This fault occurs when loading compatibility catalog for the firmware fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606347][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompEpPDAddorDelExtPol
This fault is raised when adding/deleting Portgroupsfor a VMM Controller fails.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606348][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompVNicPDDefVNicUpdate
This fault is raised when updating a vNIC profile definition fails. This typically happens if fhe Physical-NICs of the Hosts are not placed in DVS(vDS) managed by APIC
Please ensure Physical-NICs of host is placed in the DVS(vDS) managed by APIC. This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606349][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:HvsExtPolUpdate
This fault is raised when sending the external policy information from vShield controller to vCenter controller fails
This is an internal system task. This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606350][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:LacpLagPolDefUpdateLacp
This fault is raised when updating the LACP Lag Policy at the DVS fails.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606351][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompPolContUpdateCtrlrPol
This fault is raised when updating the Controller policy container at the DVS fails.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606352][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompStatsPolUpdateStatsPol
This fault is raised when updating the statistics monitoring policy for the Controller fails.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606353][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:FvnsVxlanInstDefAddorDelFvnsInst
This fault is raised when adding/deleting a VXLAN Pool definiton for the Controller fails.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606354][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:FvnsMcastAddrInstDefAddorDel
This fault is raised when adding/deleting a Multicast Address Pool definition for the VMM Controller fails.
This task is internal system task. This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606359][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:HvsLNodeAddorDelUplinkPortGroup
This fault is raised when adding/deleting an uplink Porgroup for the Controller fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606360][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:HvsLNodeAddorDelVtepPortGroup
This fault is raised when adding/deleting a VTEP Porgroup for the Controller fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606361][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompHpNicAddorDelVtepNic
This fault is raised when adding/deleting a VTEP NIC fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606365][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:NwPathEpUpdatePathEp
This fault is raised when notification of a network path endpoint update fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606365][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:VpcIfUpdatePathEp
This fault is raised when notification of a network path endpoint update fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606367][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompHpNicUpdateHostVendorConfig
This fault is raised when updating host vendor configuration fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606369][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:HvsExtPolSetExtPolInfo
This fault is raised when setting external policy information for the Controller fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606371][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompEpPConnResolveEPgAdj
This fault is raised when Endpoint Attach/Detach update to Policy Manager fails. This is an internal task.
This task is retried automatically. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606379][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompCtrlrFindCluster
This fault is raised when Cluster update to VMM Controller fails.
If you see this fault, take the following actions:
Step 1 Validate that one or more of the physical NIC of all the hosts of the cluster are attached to the DVS
Step 2 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606386][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompCtrlrHandleObjUpd
This fault is raised when sending cluster add message to VMM Controller fails.
This task is internal system task. This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606389][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompCtrlrPrepareLNode
This fault is raised when DVS preparation operation for vShield Controller fails.
If you see this fault, take the following actions:
Step 1 Validate that vShield is associated with vCenter and it is reachable from vShield
Step 2 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606391][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompHvGetHpNicAdj
This fault is raised when LLDP/CDP Adjacency information is not found for the physical adapters on the host.
If you see this fault, take the following actions:
Step 1 Validate LLDP configuration on DVS, vCenter and Physical Switch connected to the Host.
Step 2 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606392][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompMgmtNicGetMgmtNicIp
This fault is raised when the IP address for the interface on the host cannot be found.
This task is automatically retried. If you see repeated failures, take the following actions:
Step 1 Check network connectivity for the host.
Step 2 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC. This failure is automatically retried.
%LOG_LOCAL0-2-SYSTEM_MSG [F606395][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:CompRsCtrlrGetAssocCtrlrInfo
This fault is raised when an error is encountered when obtaining vCenter hyperlink reference from vCloud Director.
If you see this fault, take the following actions:
Step 1 Validate that vCenter is associated with the vCloud Director. If not re-attach the vCenter
Step 2 Validate that vCenter hyperlink reference can be obtained using vCloud RestAPI
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC. This failure is automatically retried.
%LOG_LOCAL0-2-SYSTEM_MSG [F606430][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:MaintNodeInMaintCanIUpgrade
This fault is raised when CanIUpgrade handshake fails fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606434][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:LldpIfLldpDiscovery
This fault is raised when update Adrelay on LLDP discovery fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606435][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:FvVDEpWaitForEpP
This fault is raised when wait for endpoing profile download fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606436][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:HvsRtNicAdjReportLooseNode
This fault is raised when LooseNode Report Update to TopoManager fails.
This failure is automatically retried. If you see repeated failures, Collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606436][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:LeqptLooseNodeReportLooseNode
This fault is raised when notification about a LooseNode (unmanaged node) discovery or update fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606483][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:SysdebugTechSupportInitiate
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F606484][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:SysdebugTechSupportDeleteTechSupFile
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F606486][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:SysdebugCoreDownload
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F606486][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:SysdebugTechSupportDownload
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F606487][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:SysdebugLogControlEpLogControlPersist
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F606565][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FabricRsDecommissionNodeRemoveSwitch
This fault is raised when send decommission message to switch fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606566][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FabricRsDecommissionNodeTopoCleanup
This fault is raised when remove node request fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606567][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FabricDecommissionJobPmCleanup
This fault is raised when send policy cleanup request fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606597][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:DhcpDiscNodeReport
This fault is raised when notification about a DHCP discovered node fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606615][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VzFilterConfRFltP
This fault occurs when filter profile fails to be updated
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606616][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VzFltTaskAggrConfRFltPAggr
This fault occurs when filter profile fails to be configured for aggregated filters
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606617][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VzCtrctEPgContCtrctToEpPUpd
This fault occurs when endpoint profile remote EPG contract fails to be updated
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606640][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FvCollectionContBringInfoIntoCollectionShard
This fault occurs when EPG configuration fails to be delivered to contract collection
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606640][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VzCollectionContBringInfoIntoCollectionShard
This fault occurs when EPG collection for context configuration fails to be delivered to contract collection
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606643][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VzTabooCreateAnyTaboo
This fault occurs when a taboo entry fails to be delivered to a remote EPG
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606644][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VzBrCPVzForceConfig
This fault occurs when a dependent L4-L7 service graph template fails to be updated
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606655][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:DhcpRsProvUpdDhcpProvAddress
This fault is raised when update DHCP provider address fails
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F606664][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:InfraNodeCfgManageVpcId
This fault is raised when virtual port channel ID assignment fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606666][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FabricAProtGEpManageVIP
This fault is raised when virtual IP address assignment fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606667][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FabricNodePEpManageProtectionChainIP
This fault is raised when protection chain IP address assignment fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606668][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:DbgexpExportPSendNodeList
This fault is raised when send controller and node list fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606669][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:DbgexpTechSupPDeleteTechSupIfcTrackers
This fault is raised when delete controller tracker list for techsupport collection fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606670][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:DbgexpTechSupOnDDeleteOnDIfcTrackers
This fault is raised when delete controller tracker list for on-demand collection fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606671][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:FvVDEpEpAttachorDetach
This fault is raised when notification of an endpoint attach or detach fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606674][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:TagRefDelInst
This fault is raised when delete tag reference target fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606725][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:VpcIfUpdateVpcProtLink
This fault is raised when notfication of virtual port channel interface info fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606755][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FvEPgEpP
This fault is raised when configuration of endpoint profile definition (EpP) fails
This is an internal system task. This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606757][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FvEPgUpdMgmtDeplCont
This fault is raised when attempt to update inband management epg with device cluster interface fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606758][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FvRtProvProvDhcpUpd
This fault is raised when update DHCP provider with relation to current bridge domain fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606761][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FvAEpDefEndPointUpd
This fault is raised when notify endpoint update fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606764][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:CompRsCtrlrPEpPDUpd
This fault is raised when an EpG update to the VMM Controller fails.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606764][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FvRsDomAttEpPDUpd
This fault is raised when configuration of endpoint profile definition (EpPD) to the domain fails
This is an internal system task. This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606764][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsEPpInfoEpPDUpd
This fault is raised when L4-L7 service graph could not create port groups on VCenter required for directing service graph traffic to service VMs.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606765][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VmmCtrlrPConfig
This fault is raised when a configuration update to the VMM Controller fails.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606766][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:InfraEpPDSendDomDefToEpP
This fault is raised when a configuration update to EPP failed.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606833][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:MgmtInBZoneBringNodeInfoToInBMgmtEppShard
This fault is raised when send node information from infra to management EPG fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606834][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:MgmtOoBZoneBringNodeInfoToOoBMgmtEppShard
This fault is raised when send node information from infra to out-of-band management EPGfails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606835][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:MgmtOoBOobEpP
This fault is raised when send out-of-band endpoint profile update fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606836][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:MgmtCollectionContBringProvInfoIntoCtrct
This fault is raised when send out-of-band provider information to contract fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606837][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:MgmtCollectionContBringConsInfoIntoCtrct
This fault is raised when send EPG consumer information to contract fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606840][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:PresResolverResolverRepl
This fault is raised when handle replication for resolver fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606842][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:SpanSrcReportSpanSrcDef
This fault is raised when notification about a Span source fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606843][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:SpanTaskParamUpdateSpanSrcGrpDef
This fault is raised when notification about a Span source group fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606844][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FvRtDestEpgSpanEpg
This fault is raised when notification about a Span source group fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606845][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:DbgacEpgSummaryReportODACDef
This fault is raised when notification about a on-demand atomic counter policy fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606871][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:TopSystemUpdateTopSystem
This fault is raised when system change notification to Topology Manager fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606872][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:TopSystemUpdateFabricNode
This fault is raised when sending system information to Topology Manager fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606875][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:DbgRemotePortUpdateRemotePortToDbgrelem
This fault is raised when update remote port info to debugger-element fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606897][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:TestinfralabFreebiesReportFreebies
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F606899][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:SyntheticContextTest
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F606900][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:SyntheticContextLocalTest
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F606901][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:SyntheticContextTest2
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F606902][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:SyntheticContextTest3
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F606910][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:InfraRsFuncToEpgReportPortsToEpp
This fault is raised when deploy of EPG on ports associated with Attached Entity Profile fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F606911][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:InfraRsDomPSendAttEntityPToVmmDomP
This fault is raised when sending policies associated with attached entity profile to domain fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607041][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FvAEPgLegacyEpP
This fault is raised when updating endpoint profile failed for legacy mode.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607041][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsEPgDefLegacyEpP
This fault is raised if endpoint profile update for service graph internal EPG fails.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607045][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsEPpInfoEPpInfo
This fault is raised when L4-L7 service graph related information could not be deleted from leafs.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607048][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsLDevInstVDevUpdGraphInst
This fault is raised when updating virtual device configuration to script handler failed.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607050][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VzACollectionProcessContract
This fault is raised when rendering associated service graphs failed.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607450][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:ae:TopSystemControllerChassis
This fault is raised when sending top System changes for Chassis to Topology Manager fails
%LOG_LOCAL0-2-SYSTEM_MSG [F607451][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:TopSystemSwitchChassis
This fault is raised when chassis change notification to Topology Manager fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607479][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:ae:PconsResolverResolveAllPolicies
This fault occurs when forced policy resolution fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607480][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:eventmgr:CallhomeInvPUpdateCallhomeInvP
This fault is raised when task to update execution status of callhome inventory policy fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607481][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsRsLDevInstVDevUpd
This fault is raised when updating device configuration on script handler failed.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607493][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:MgmtInstPInstPEpP
This fault is raised when send endpoint profile update for management EPG fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607496][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:topomgr:FabricShardTaskHolderUnsubscribeFromPM
This fault is raised when sending Fabric Node subscription removal to Policy Manager fails
%LOG_LOCAL0-2-SYSTEM_MSG [F607514][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:DbgacTenantSpaceCmnAcSendDbgProfile
This fault is raised when notification for a on-demand atomic counter policy fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607560][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:topomgr:FabricNodeIdentPSend
This fault is raised when sending Fabric Node Member information to Topology Manager fails
%LOG_LOCAL0-2-SYSTEM_MSG [F607560][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:topomgr:FabricNodeInfoSend
This fault is raised when sending Fabric NodeInfo data to Appliance Element fails
%LOG_LOCAL0-2-SYSTEM_MSG [F607560][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:topomgr:FabricNodeSend
This fault is raised when sending root Fabric Node changes to Appliance Element fails
%LOG_LOCAL0-2-SYSTEM_MSG [F607563][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:scripthandler:VnsScriptRTInfoUpdateScriptRTInfo
This fault is raised when updating runtime info under service script failed.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607564][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:TopSystemUpdateRunningVer
This fault is raised when running software version fails to be updated
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607571][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:AaaADomainRefPushDomainRefsToRbacEp
This fault is raised when configuration distribution of RbacRules fails
This is an internal system task. This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607574][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:PconsResolverContCheckBootStrap
This fault is raised when ports cannot be brought in service after incomplete policy registration
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607575][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:PconsResolveCompleteRefPolicyDeploymentDone
This fault is raised when the message to notify leaf/spine about policy deployment completion fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607588][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:bootmgr:FirmwareFirmwareAutoloadCatalog
This fault occurs when loading firmware compatibility catalog fails.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607589][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:PconsResolverContCheckBootStrapWorstCaseTask
This fault is raised when bringing ports in service after bootstrap completion fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607590][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FvSubnetBDDefContUpdateBDDefWithRouteDef
This fault is raised when update bridge domain with static route fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607591][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FvTabooCtxDefContUpdateCtxDefWithTabooDef
This fault is raised when update private network with taboo configuration fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607592][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FvCtrctCtxDefContUpdateCtxDefWithEPgDef
This fault is raised when update private network with EPG summary information fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607603][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:dhcpd:DhcpClientUpdateFnv
This fault occurs when updating the fabric node vector fails.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607610][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:ae:FvInBEpPInBUpd
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F607620][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsLDevCtxReRenderGraph
This fault is raised when sending message to contract shard failed and graph instance could not be re-rendered.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607623][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FvSubnetBDDefContUpdateBDHolder
This fault is raised when update bridge domain container fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607628][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VzCollectionContBringCollectionIntInfoIntoCtrct
This fault occurs when contract or bundle interface configuration fails to be delivered to contract or bundle
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607632][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:topomgr:FabricNodeTaskHolderSubscribeToPM
This fault is raised when sending Fabric Node subscription to the Policy Manager via Appliance Element fails
%LOG_LOCAL0-2-SYSTEM_MSG [F607660][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FabricProtGEpVPcRegisterForNotification
This fault is raised when register for node notification fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607661][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:TagRefUpdateAlias
This fault occurs when an alias instance update fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607664][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:scripthandler:VnsCMgmtNatCreate
This fault is raised when NAT entry creation for concrete device management interface failed.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607664][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:scripthandler:VnsCtrlrEpNatCreate
This fault is raised when NAT entry creation for controller appliance failed.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607666][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:LeqptLooseNodeReportPathGrp
This fault is raised when reporting fabric path group on an external connected node fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607667][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policyelem:CallhomeInvTaskSendInventory
This fault is raised when send callhome inventory fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607670][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:FabricAProtGEpSpineProxyCreate
This fault is raised when notify spine proxy create fails
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607684][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VzCtrctEPgContUpdateCtxDefWithAnyREpPCtrct
This fault occurs when private network configuration fails to be updated with remote contract collection
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607689][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsRsTermToAnySvcFltUpd
This fault is raised when service graph related filter update for L3 network?™s Any fails.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607689][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsRsTermToEPgSvcFltUpd
This fault is raised when security filters required to allow traffic from EPgs to L4-L7 service graph traffic could not be downloaded to leafs.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607690][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:vmmmgr:AaaIDomainRefReportDomainRefsToRbacEp
This fault is raised when the update of security domain configuration to PolicyMgr fails. This is an internal task used by the system.
%LOG_LOCAL0-2-SYSTEM_MSG [F607725][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsSDEPpInfoEpPDUpdS
This fault is raised when L4-L7 service graph could not create port groups on VCenter required for directing service graph traffic to service VMs.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607726][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsSDEPpInfoEPpInfoS
This fault is raised when L4-L7 service graph related information could not be configured on leafs.
This task is automatically retried. If you see repeated failures, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F607727][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsREPpInfoAllocateEncap
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F607728][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsLDevInstAllocateVDevId
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F607729][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsSLDevInstConsRemoveVGrp
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F607730][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:VnsSLDevInstRemoveVDev
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.
%LOG_LOCAL0-2-SYSTEM_MSG [F607746][fsm-failed][major][DN of affected MO] [FSM:FAILED]: ifc:policymgr:L3extRtLIfCtxToOutRoutePeering
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco ACI Release Notes and the Cisco ACI Troubleshooting Guide. If you cannot resolve the issue, export an On-demand TechSupport data file and contact Cisco Technical Support.