%LOG_LOCAL0-4-SYSTEM_MSG [F1121][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 [F1123][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 [F1125][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 [F1126][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 [F1127][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 [F1128][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 [F1129][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 [F1182][config-failure][warning][DN of affected MO] vlan 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 [F1183][config-failure][warning][DN of affected MO] vrf 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 [F1184][config-failure][warning][DN of affected MO] vPC domain 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 [F1185][config-failure][warning][DN of affected MO] vPC 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 [F1186][config-failure][warning][DN of affected MO] Port configuration failure. Reason: [ethpmCfgState] Failed Config: [ethpmCfgFailedBmp]
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 [F1187][config-failure][warning][DN of affected MO] Port-channel 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 [F1188][config-failure][warning][DN of affected MO] tunnel 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 [F1189][config-failure][warning][DN of affected MO] sub-interface 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 [F1190][config-failure][warning][DN of affected MO] vlan membership 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 [F1191][config-failure][warning][DN of affected MO] vPC 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 [F1192][config-failure][warning][DN of affected MO] Port-channel([parentSKey]) membership configuration failure for [tSKey]
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-2-SYSTEM_MSG [F1194][qos-resource-unavailable][major][DN of affected MO] Qos class failed due to hardware programming error
This fault occurs when qos 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 qos 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-2-SYSTEM_MSG [F1195][qos-resource-unavailable][major][DN of affected MO] Dscp rule failed due to hardware programming error
This fault occurs when qos manager fails to activate a dscp rule due to hardware programming failure
To recover from this fault, try the following actions
Step 1 Look at any configuration issues
%LOG_LOCAL0-2-SYSTEM_MSG [F1196][qos-resource-unavailable][major][DN of affected MO] Dot1p rule failed due to hardware programming error
This fault occurs when qos manager fails to activate a dot1p rule due to hardware programming failure
To recover from this fault, try the following actions
Step 1 Look at any configuration issues
%LOG_LOCAL0-2-SYSTEM_MSG [F1197][bd-limits-exceeded][major][DN of affected MO] Learning is disabled on BD [name]
This fault occurs when the ep learning is disabled
If this fault is consistently happening, try the following actions
Step 1 Check network connectivity for stp flaps
Step 2 If the network connectivity is fine, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1199][span-provision-failed][major][DN of affected MO] Span source is in failed state, reason [operStQual].
This fault occurs when span source on a port goes to failed state
To recover from this fault, try the following actions
Step 1 Look at any configuration issues
%LOG_LOCAL0-2-SYSTEM_MSG [F1200][span-provision-failed][major][DN of affected MO] Span source is in failed state, reason [operStQual].
This fault occurs when span source on a circuit goes to failed state
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 Check network connectivity and ensure the circuit is up
%LOG_LOCAL0-2-SYSTEM_MSG [F1201][span-provision-failed][major][DN of affected MO] Span destination is in failed state, reason [operStQual].
This fault occurs when span destination goes to failed state
To recover from this fault, try the following actions
Step 1 Look at any configuration issues
%LOG_LOCAL0-4-SYSTEM_MSG [F1207][protocol-arp-adjacency-down][warning][DN of affected MO] Static ARP adjacency is [operSt], reason [operStQual]
This fault occurs when the operational state of the arp adjacency is down
To recover from this fault, try the following actions
Step 1 Look at any configuration issues
%LOG_LOCAL0-3-SYSTEM_MSG [F1209][configuration-failed][minor][DN of affected MO] Configuration failed for node [name], [name] [tDn] due to [configQual]
This fault occurs when an out-of-service policy is incorrectly configured.
If you see this fault, take the following actions:
Step 1 Look at the configuration for issues
Step 2 For invalid-path, confirm that the specified interface is correct
Step 3 For further details, refer to the documentation for fabric:PathIssues
Step 4 Verify the fabric selector configuration is correct and complete
Step 5 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1213][protocol-bgp-limits-exceeded][warning][DN of affected MO] BGP instance is critically low in memory
This fault occurs when the bgp instance memory alert is critical
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 Reduce the number of peers in bgp configuration
Step 4 Reduce the number of prefixes exported into bgp
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 [F1214][protocol-bgp-adjacency-down][warning][DN of affected MO] BGP peer is shut, reason: [shutStQual]
This fault occurs when the peer is shut down because the prefix limit is exceeded or no memory
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 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-4-SYSTEM_MSG [F1215][protocol-bgp-limits-exceeded][warning][DN of affected MO] BGP maximum prefix limit is exceeded [acceptedPaths]
This fault occurs when the accepted prefixes from the peer is greater than the configured limit
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 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 [F1224][interface-svi-down][major][DN of affected MO] SVI is down, [operStQual]
This fault occurs when the svi bring up failed because of hardware programming failure
To recover from this fault, try the following actions
Step 1 Try reconfiguring the svi.
Step 2 If the above action did not resolve the issue, try rebooting the switch using CLI or GUI.
Step 3 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F1228][configuration-failed][minor][DN of affected MO] Configuration failed for [name] [name] due to [configIssues]
This fault occurs when a Contract is incompletely / incorrectly configured.
If you see this fault, take the following actions:
Step 2 Verify the configuration is correct / complete
Step 3 For filter-not-present, check if the configured filter is correct
Step 4 For taboo-has-no-filter, check if the Taboo configuration is correctly configured to an existing filter
Step 5 For subject-not-in-use-due-to-label, check if the configured label is correct
Step 6 For any-to-prov-shared-service, this is an invalid configuration
Step 7 For further details, refer to the documentation for vz:ConfigIssues
Step 8 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1233][configuration-failed][major][DN of affected MO] Deployment of Attached Entity Profile [name] failed with error: [configIssues]
Infra Policy fault is raised when both CDP and LLDP policies are configured for the same Attached Entity Profile.
If you see this fault, take the following actions:
Step 1 Review the fault message to identify configuration issue.
Step 2 Modify configuration to remove any invalid configuration parameters.
Step 3 If the listed recommendations do not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1236][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 [F1237][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 [F1239][link-failed][critical][DN of affected MO] Link between node [n1] slot [s1] port [p1] and node [n2] slot [s2] port [p2] is invalid. [wiringIssues]
This fault occurs when a link state is not ok
If you see this fault, take the following action:
Step 1 check if connectivity between the nodes for the link is ok
Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F1240][configuration-failed][minor][DN of affected MO] Configuration failed for [name], [name] due to [configIssues]
This fault occurs when a Taboo list is incompletely / incorrectly configured.
If you see this fault, take the following actions:
Step 2 Verify the configuration is correct / complete and rectify any of the configIssues
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 [F1241][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 [F1258][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 [F1259][actrl-provisioning-failed][major][DN of affected MO] Rule failed due to software programming error
This fault occurs when policy manager fails to activate a management rule due to software programming failure
To recover from this fault, try the following actions
Step 1 Look at any configuration issues
%LOG_LOCAL0-3-SYSTEM_MSG [F1261][configuration-failed][minor][DN of affected MO] Configuration failed due to [configQual] for node [name]Configuration failed due to [configQual] for [instPKey] for node [name]Configuration failed due to [configQual] for [instPKey] for node [name]
This fault occurs when a encap namespace (VLAN/VXLAN namespace etc.) is incorrectly configured.
If you see this fault, take the following actions:
Step 1 Look at the configuration for issues
Step 2 For overlapping-encap-namespace, check the VLAN/VXLAN Instance Profiles and the associated domain configurations. Two overlapping instance profiles are not allowed to be pushed to the same node.
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 [F1262][unhealthy][minor][DN of affected MO] Non optimal leader for some database partitions of [name] on controller [id]
This fault occurs when a controller reports some services do not have ideal replica leaders for some of the internal database partitions (shards).
If you see this fault, take the following actions:
Step 1 Ensure that you have a minimum of 3 APICs
Step 2 Verify that all the APICs are reported as available and Fully-Fit in cluster.
Step 3 If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1284][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 [F1286][invalid-src-or-dst][minor][DN of affected MO] The source or the destination switch for the traceroute node [name] is a spine
This fault occurs when a Spine node is used as a source or destination in a traceroute.
If you see this fault, take the following actions:
Step 1 Verify that the policy for traceroute is applied to the correct Node by making sure the proper Node ID is in the "Target DN" property.
Step 2 Verify that the correct Nodes have been chosen as sources and destinations.
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 [F1295][configuration-failed][minor][DN of affected MO] Datetime Policy Configuration for [name] failed due to : [configQual]
This fault is raised when a Date and Time Policy (datetime:Pol) fails to apply due to configuration issues.
If you see this fault, take the following actions:
Step 1 Ensure that the path (over the inband or out-of-band managment network) that the date and time policy would use to get to the date and time server is configured properly and accessible.
Step 2 Ensure that the End Point Group is configured properly for the date and time policy.
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1296][interface-vpc-down][major][DN of affected MO] vPC [name] is down.
%LOG_LOCAL0-4-SYSTEM_MSG [F1297][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 [F1298][configuration-failed][minor][DN of affected MO] EPG [name] policy deployment on node [id] failed due to [deploymentState]For tenant [epgPKey], application profile [epgPKey], deployment of application EPG [epgPKey] failed on node [id]. Reason [deploymentState]For tenant [epgPKey], outside [epgPKey], deployment of external EPG [epgPKey] failed on node [id]. Reason [deploymentState]For tenant [epgPKey], outside [epgPKey], deployment of external EPG [epgPKey] failed on node [id]. Reason [deploymentState]For tenant [epgPKey], management profile [epgPKey], deployment of in-band EPG [epgPKey] failed on node [id]. Reason [deploymentState]For tenant [epgPKey], management profile [epgPKey], deployment of out-band EPG [epgPKey] failed on node [id]. Reason [deploymentState]
: This fault occurs when deliverying EPg policies to a node has failed
: If you see this fault, take the following actions: - Verify node is reachable by pinging the TEP address from the APIC; - Verify node can deploy this type of policy (spine can deploy only mgmt EPg) If the above conditions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F1299][configuration-failed][minor][DN of affected MO] A profile configuration has not been deployed on node [id], because: [deplSt]Pod profile configuration [profileDn] has not been deployed on controller/node [id] because: [deplSt]Controller profile configuration [profileDn] has not been deployed on controller [id] because: [deplSt]Switch profile configuration [profileDn] has not been deployed on node [id] because: [deplSt]Module profile configuration [profileDn] has not been deployed on node [id] because: [deplSt]Interface profile configuration [profileDn] has not been deployed on node [id] because: [deplSt]Switch profile configuration [profileDn] has not been deployed on node [id] because: [deplSt]Module profile configuration [profileDn] has not been deployed on node [id] because: [deplSt]Interface profile configuration [profileDn] has not been deployed on node [id] because: [deplSt]FEX profile configuration [profileDn] has not been deployed on node [id] because: [deplSt]Interface override configuration [profileDn] has not been deployed on node [id] because: [deplSt]Interface override configuration [profileDn] has not been deployed on node [id] because: [deplSt]Node override configuration [profileDn] has not been deployed on node [id] because: [deplSt]Node override configuration [profileDn] has not been deployed on node [id] because: [deplSt]
This fault occurs when a selector level policy has been created, all policies in the corresponding policy group should be deployed on all fabric nodes in that selector level policy but those selector level 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 capable of handling those selector level policies
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 [F1300][configuration-failed][minor][DN of affected MO] A Fabric Node Group (fabricNodeGrp) configuration was not deployed on the fabric node [id] because: [deplSt]
This fault occurs when a Fabric Node Group (fabricNodeGrp) has been created, all the policies targeted by the policy group should have been deployed on all the fabric nodes in that group, however some of those policies have not been deployed to a fabric node.
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 capable of handling those fabric node group level policies
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 [F1305][configuration-failed][minor][DN of affected MO] SNMP Policy Configuration for [name] failed due to: [configQual]
This fault occurs when SNMP policy configuration failed to apply.
If you see this fault, take the following actions:
Step 1 For access-epg-not-specified, ensure that the SNMP policy has a correctly configured relationship to the management EPG.
Step 2 For access-epp-is-not-available, confirm the affected endpoint is reachable in the management EPG and management tenant with selected EPG is correctly configured on endpoint.
Step 3 For context-info-is-not-present-in-epp, confirm the management tenant is correctly configured with a context/network
Step 4 For community-is-not-configured-in-snmp-policy, check that the SNMP community specified in the tenant configuration exists in the SNMP policy for the fabric.
Step 5 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1307][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 [F1310][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 [F1313][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] HpNic: [mac], error: [[hpNicOperIssues]]
This fault is raised when remote or external disruptive operations are performed on Host Physical NIC from within the Controller.
If you see this fault, take the following actions:
Step 1 Restore the NIC to the original state.
Step 2 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1314][configuration-failed][warning][DN of affected MO] configuration failed *[faultMessage]*Graph configuration resulted in *[faultMessage]* for [name] in context [ctxName] on cluster [priKey] in tenant [priKey] for graph [priKey] with id [id], function [key]Graph configuration resulted in *[faultMessage]* for [name] in context [ctxName] on cluster [priKey] in tenant [priKey] for graph [priKey] with id [id]Graph configuration resulted in *[faultMessage]* for [name] in context [ctxName] on cluster [priKey] in tenant [priKey]Device configuration resulted in *[faultMessage]* for [name] on device [name] in cluster [name] in tenant [name]Device configuration resulted in *[faultMessage]* for [name] on device [name] in cluster [priKey] in tenant [priKey]Cluster configuration resulted in *[faultMessage]* for [name] on cluster [name] in tenant [tnDn]Cluster configuration resulted in *[faultMessage]* for [name] in tenant [name]Graph configuration resulted in *[faultMessage]*
This fault occurs when the L4-L7 service returns a warning fault
If you see this fault, please refer to L4-L7 device vendor documentation.
%LOG_LOCAL0-1-SYSTEM_MSG [F1315][configuration-failed][critical][DN of affected MO] configuration failed *[faultMessage]*Graph configuration resulted in *[faultMessage]* for [name] in context [ctxName] on cluster [priKey] in tenant [priKey] for graph [priKey] with id [id], function [key]Graph configuration resulted in *[faultMessage]* for [name] in context [ctxName] on cluster [priKey] in tenant [priKey] for graph [priKey] with id [id]Graph configuration resulted in *[faultMessage]* for [name] in context [ctxName] on cluster [priKey] in tenant [priKey]Device configuration resulted in *[faultMessage]* for [name] on device [name] in cluster [name] in tenant [name]Device configuration resulted in *[faultMessage]* for [name] on device [name] in cluster [priKey] in tenant [priKey]Cluster configuration resulted in *[faultMessage]* for [name] on cluster [name] in tenant [tnDn]Cluster configuration resulted in *[faultMessage]* for [name] in tenant [name]Graph configuration resulted in *[faultMessage]*
This fault occurs when the L4-L7 service returns a critical fault
If you see this fault, please refer to L4-L7 device vendor documentation.
%LOG_LOCAL0-2-SYSTEM_MSG [F1317][equipment-psu-mismatch][major][DN of affected MO] Power supply group is non-redundant
This fault occurs when there is a single power supply in the chassis or there are mismatchd power supplies in the chassis
To recover from this fault, try the following actions
Step 1 Add more power supplies
Step 2 Remove mismatched power supplies
Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC
%LOG_LOCAL0-2-SYSTEM_MSG [F1318][equipment-psu-missing][major][DN of affected MO] No psu detected
This fault occurs when PSU are not detected correctly
To recover from this fault, try the following actions
Step 1 Properly seat the power supplies
Step 2 Remove mismatched power supplies
Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC
%LOG_LOCAL0-2-SYSTEM_MSG [F1321][equipment-ft-failed][major][DN of affected MO] All fans in tray located in slot [id] in [role] [name] failed
This fault occurs when a fan tray fails
To recover from this fault, try the following actions
Step 1 Replace the fan tray that failed
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC
%LOG_LOCAL0-4-SYSTEM_MSG [F1322][equipment-fan-failed][warning][DN of affected MO] Fan [id] in slot [id] in [role] [name] failed
This fault occurs when a fan fails
To recover from this fault, try the following actions
Step 1 Check the fan tray to see if it is still fully operational; if not, replace it
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC
%LOG_LOCAL0-2-SYSTEM_MSG [F1323][equipment-ft-missing][major][DN of affected MO] Fan tray missing in slot [id] in [role] [name]
This fault occurs when a fan tray is missing
To recover from this fault, try the following actions
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC
%LOG_LOCAL0-2-SYSTEM_MSG [F1324][configuration-failed][major][DN of affected MO] Configuration of management interface of device in cluster [priKey] in tenant [priKey] failed
This fault occurs when the there is a failure in setting up the management interface to a service node
If you see this fault, please try with deleting management interface related configuration and then reposting it back.
%LOG_LOCAL0-2-SYSTEM_MSG [F1325][configuration-failed][major][DN of affected MO] Controller Endpoint configuration for tenant [priKey] and segment [seg] on appliance [appliance] failed
This fault occurs when the there is a failure in setting up the management interface on the controller which is used to communicate to the service node
If you see this fault, please try with deleting management interface related configuration and then reposting it back.
%LOG_LOCAL0-3-SYSTEM_MSG [F1329][stats-export-skipped][minor][DN of affected MO] Statistics export was skipped because of too many failues. Failure reason: [details]. Refer to [dn] policy for configuration details.
This fault occurs due to a Stats Export Policy session failure.
If you see this fault, please check the stats export configuration parameters and health of the destination export server.
%LOG_LOCAL0-3-SYSTEM_MSG [F1330][stats-export-skipped][minor][DN of affected MO] Statistics export was skipped because of too many failues. Failure reason: [details]. Refer to [dn] policy for configuration details.
This fault occurs due to a Stats Export Policy session failure.
If you see this fault, please check the Stats Export Policy configuration parameters and health of the destination export server.
%LOG_LOCAL0-3-SYSTEM_MSG [F1332][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-3-SYSTEM_MSG [F1336][configuration-failed][minor][DN of affected MO] Service graph template function profile: [name], which is in tenant [name] is invalid.Service graph template function profile: [name], which is in tenant [name] is invalid.Service graph template function profile: [name], which is under the device package by vendor [vendor], device model [model], package version [version] is invalid.
This fault occurs due to an invalid abstract function profile configuration.
If you see this fault, please ensure that the abstract function profile is valid.
%LOG_LOCAL0-3-SYSTEM_MSG [F1339][configuration-missing][minor][DN of affected MO] Configuration missing for [name] [name] [name] has a label, but no EPG is associated: [configIssues]
This fault occurs when a Subject has a Label, but there is no EPG associated to a Contract that is also associated to that Subject.
If you see this fault, take the following actions:
Step 2 Verify the configuration is correct / complete
Step 3 For subject-not-in-use-due-to-label, check if the configured label is correct
Step 4 For further details, refer to the documentation for vz:ConfigIssues
Step 5 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F1340][configuration-failure][minor][DN of affected MO] Multicast Address pool [name] deployment failed due to: [configIssues].
This fault is raised when a Multicast Address pool cannot be deployed due to a missing or invalid configuration.
If you see this fault, take the following actions:
Step 1 Review the fault message and correct the invalid configuration.
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 [F1342][dot1p-provisioning-failed][major][DN of affected MO] Configuration failed
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 [F1343][dscp-provisioning-failed][major][DN of affected MO] Configuration failed
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 [F1344][config-failure][warning][DN of affected MO] Address configuration failure. Reason: [ipv4CfgState]
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 [F1345][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 [F1346][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 [F1347][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 [F1348][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 [F1349][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 [F1350][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 [F1351][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 [F1353][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 [F1360][protocol-coop-adjacency-down][warning][DN of affected MO] Operational state is down, reason:[operStQual]
This fault occurs when the operational state of the coop adjacency is down
To recover from this fault, try the following actions
Step 1 Look at any configuration issues
Step 2 Look at any connectivity issues
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 [F1362][interface-fexfabric-incompatible][warning][DN of affected MO] FEX connected to this port incompatible
This fault occurs when there is an incompatibility between the leaf and the attached 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-4-SYSTEM_MSG [F1364][bd-provisioning-failed][warning][DN of affected MO] Optimized ARP forwarding is not supported with unknown MAC flood
This fault occurs when the arp flood knob is not set in bridge only mode
To recover from this fault, try the following actions
Step 1 Set the arp flood knob for this BD
Step 2 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1368][protocol-snmp-provision-failed][major][DN of affected MO] SNMP Client programming failed, reason: [operStQual]
This fault occurs when snmp client security programming fails
To recover from this fault, try the following actions
Step 1 Look at any configuration issues.
Step 2 Confirm the affected endpoint is reachable in the management EPG
Step 3 and management tenant with selected EPG is correctly configured on endpoint.
%LOG_LOCAL0-2-SYSTEM_MSG [F1369][protocol-snmp-provision-failed][major][DN of affected MO] SNMP User programming failed, reason: [operStQual]
This fault occurs when snmp user programming fails
To recover from this fault, try the following actions
Step 1 Look at any configuration issues
%LOG_LOCAL0-1-SYSTEM_MSG [F1370][intrusion][critical][DN of affected MO] Messages from a controller (node-[id]) with the Globally Unique Identifier (GUID) [chassis] and the IP address [addr] started arriving at [frstMsgTs] and are being rejected because: [icmsReason]
This fault occurs when messages arrive periodically from controllers that are considered illegitimate by the controller cluster.
If you see this fault, take the following actions:
Step 1 The message included with the fault will also include a reason the controller messages are considered illegitimate. 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-2-SYSTEM_MSG [F1371][policy-deployment-failed][major][DN of affected MO] Failed to deploy policy [polDn] to service [svc] on node with id [systemId]Failed to deploy policy [polDn] to service [svc] on node with id [systemId]
This fault occurs when deployment of policy to a leaf/spine fails.
Check the state of leaf/spine using "acidiag fnvread" and make sure the state of the leaf/spine is active. If not active
Step 1 Check if leaf/spine is down
Step 2 Check network connectivity of leaf/spine to controllers
Step 3 If above options did not solve, create tech-support and contact Cisco TAC
%LOG_LOCAL0-2-SYSTEM_MSG [F1373][deployment-failed][major][DN of affected MO] Deployment of EPG failed on Controller: [tDn] in domain: [name] due to error: [deployIssues]
This fault is raised when the Endpoint Group cannot be deployed on a VMM Controller due to a missing or invalid configuration.
If you see this fault, take the following actions:
Step 1 Review the faults on the associated VMM Controller.
Step 2 Review the fault message and add missing or remove invalid configuration.
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1374][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 [F1375][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 [F1377][configuration-failed][minor][DN of affected MO] Folder configuration is invalid due to [configIssues]Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in tenant [name] is invalid due to [configIssues]Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in bridge domain [name] for tenant [name] is invalid due to [configIssues]Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in private network [name] for tenant [name] is invalid due to [configIssues]Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in application profile [name] for tenant [name] is invalid due to [configIssues]Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in EPG [name] of application profile [name] for tenant [name] is invalid due to [configIssues]
This fault occurs when a Folder configuration is invalid.The config issues indicate the exact reason for the error.
If you see this fault, please modify configuration to resolve the cause of fault.
%LOG_LOCAL0-3-SYSTEM_MSG [F1378][configuration-failed][minor][DN of affected MO] Parameter configuration is invalid due to [configIssues]Parameter [name] of Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in tenant [name] is invalid due to [configIssues]Parameter [name] of Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in bridge domain [name] for tenant [name] is invalid due to [configIssues]Parameter [name] of Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in private network [name] for tenant [name] is invalid due to [configIssues]Parameter [name] of Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in application profile [name] for tenant [name] is invalid due to [configIssues]Parameter [name] of Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in EPG [name] of application profile [name] for tenant [name] is invalid due to [configIssues]
This fault occurs when a Parameter configuration is invalid.The config issues indicate the exact reason for the error.
If you see this fault, please modify configuration to resolve the cause of fault.
%LOG_LOCAL0-3-SYSTEM_MSG [F1379][configuration-failed][minor][DN of affected MO] Relation configuration is invalid due to [configIssues]Relation [name] of Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in tenant [name] is invalid due to [configIssues]Relation [name] of Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in bridge domain [name] for tenant [name] is invalid due to [configIssues]Relation [name] of Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in private network [name] for tenant [name] is invalid due to [configIssues]Relation [name] of Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in application profile [name] for tenant [name] is invalid due to [configIssues]Relation [name] of Folder [name] that is used to configure node [nodeNameOrLbl] of service graph [graphNameOrLbl] for contract [ctrctNameOrLbl], in EPG [name] of application profile [name] for tenant [name] is invalid due to [configIssues]
This fault occurs when a Relation configuration is invalid.The config issues indicate the exact reason for the error.
If you see this fault, please modify configuration to resolve the cause of fault.
%LOG_LOCAL0-4-SYSTEM_MSG [F1385][protocol-ospf-adjacency-down][warning][DN of affected MO] OSPF adjacency is not full, current state [operSt]
This fault occurs when the adjacency state is not up
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 Check network connectivity to the peer
Step 4 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1386][config-error][warning][DN of affected MO] ARP flooding must be enabled when L2 unknown unicast is set to flood
This fault occurs when the bridge domain ARP flood is not enabled and the L2 unknown unicast is set to flood
If you see this fault, take the following actions:
Step 1 Enable ARP flood for this BD
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 [F1387][config-failure][warning][DN of affected MO] Port-channel 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-3-SYSTEM_MSG [F1394][interface-physical-down][minor][DN of affected MO] Port is down, reason:[operStQual]([operErrDisQual]), used by:[usage]
This fault occurs when a port is down and is in use for fabric
If you see this fault, take the following actions
Step 1 Check the port connectivity
Step 2 Administratively shut the port if the port is not in use
Step 3 For mcp-loop-err-disable, this could be due to a loop in the network. Check the config to resolve any loops
Step 4 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1397][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 [F1399][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 [F1400][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 [F1410][obstacle][critical][DN of affected MO] Cluster cannot continue to [clGmChngDir] from its current size [opClSz] for the following reason: [cseoReason]. The controller ID is [ctrlrId], the service ID is [svcId], the internal database partition (shard) ID is [shrdId] and the replica ID is [rplId]
This fault occurs when the operational size for a controller cluster can not reach the configured target size.
If you see this fault, take the following actions:
Step 1 Ensure that the controller cluster is contiguous, it must grow from the end and can not have any gaps in the cluster numbering.
Step 2 Verify that the cluster health is fully fit.
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 [F1414][syslog-remote-dest-not-reachable][minor][DN of affected MO] syslog server [host] hostname not resolvable.
This fault occurs when a configured syslog server is not reachable.
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-3-SYSTEM_MSG [F1416][configuration-failed][minor][DN of affected MO] Function connector [name] of function node [name] for service graph template [name] for tenant [name] has an error.
This fault occurs when an Abstract Function Connector (AbsFuncConn) has an error.The config issues the exact reason for the error.
If you see this fault, please modify configuration to resolve the cause of fault.
%LOG_LOCAL0-2-SYSTEM_MSG [F1419][service-failed][major][DN of affected MO] Service [name] failed on apic [name]
This fault occurs when a Data Management Engine (DME) process fails on a controller
If you see this fault, take the following actions:
Step 1 If one exists, collect the core file for the process
%LOG_LOCAL0-2-SYSTEM_MSG [F1425][ip-provisioning-failed][major][DN of affected MO] IPv4 address is operationally down, reason:[operStQual]
This fault occurs when the operational state of the ipv4 address state is changed to subnet-overlap/no primary/addr already confgd as next hop in a static route
To recover from this fault, try the following actions
%LOG_LOCAL0-4-SYSTEM_MSG [F1427][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 [F1432][scheduler-paused-on-member-upgrade-failure][major][DN of affected MO] The scheduler for the firmware upgrade group [polName] is paused because one or more members of the group failed to upgrade or the user manually paused scheduler
This fault occurs when upgrade is paused on a group due to one or more members of the group failing to be upgraded and the maintenance policy specifies that it should pause when there is a failure (pauseOnFailure) or the user manually pauses the scheduler
If you see this fault, take the following actions:
Step 1 If the scheduler was manually paused, unpause the scheduler
Step 2 Look for individual node faults indicating why the upgrade failed. Try to understand why the upgrade failed. Once you have identified and corrected the reason for the upgrade failure, then unpause the scheduler on this maintenance group.
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 [F1433][scheduler-paused-on-cluster-health][major][DN of affected MO] The scheduler for the firmware upgrade group [polName] is paused because the controller cluster is not healthy
This fault occurs when upgrade is paused due to cluster not being healthy
If you see this fault, take the following actions:
Step 1 Look for other faults indicating why the cluster is not healthy. Try to understand why the cluster is not healthy and correct that. Once you have identified and corrected the unhealthy controller cluster, the fault will clear automatically on the next upgrade attempt.
Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1434][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 [F1435][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 [F1436][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 [F1449][msg-msg-failure][minor][DN of affected MO] Failed to resolve Vrfname for destination [host] of group [name] on node [id] ([name]) of pod [podId]
This fault occurs when the configured SNMP trap destination endpoint cannot be resolved by the switch.
If you see this fault, take the following actions:
Step 1 Verify destination information is correct.
Step 2 Verify EPG is configured correctly.
Step 3 Ensure destination is reachable (via ping/ssh) from the fabric and DNS entries have been configured correctly.
Step 4 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F1450][msg-msg-failure][minor][DN of affected MO] EpgDn not set for destination [host] of group [name] on node [id] ([name]) of pod [podId]
This fault occurs when SNMP Trap Destination does not have a valid Endpoint Group Destination configured.
If you see this fault, take the following actions:
Step 1 Configure EpGDn property of the SNMP Trap Destination.
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 [F1451][equipment-psu-down][minor][DN of affected MO] Power supply shutdown. (serial number [ser])
This fault occurs when psu is shut down
To recover from this fault, try the following actions
Step 1 Connect a power supply to this PSU
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC
%LOG_LOCAL0-4-SYSTEM_MSG [F1467][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 [F1471][deployment-failed][major][DN of affected MO] EPG deployment failed due to [remoteErrMsg]
This fault is raised when the SCVMM plugin encounters an exception.
If you see this fault, take the following actions:
Step 1 Check the system events in the SCVMM or WAP machine for details.
%LOG_LOCAL0-4-SYSTEM_MSG [F1472][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 [F1473][configuration-failed][major][DN of affected MO] Device Package from [priKey] for [priKey] version [priKey] is missing the following functions: [moduleStatus]
This fault occurs when there is missing function in device package
If you see this fault, please contact L4-L7 device vendor for a more recent verion of device package.
%LOG_LOCAL0-2-SYSTEM_MSG [F1477][ip-provisioning-failed][major][DN of affected MO] Route NextHop is operationally down, reason:[operStQual]
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 [F1478][duplicate-oobmgmt-ip][major][DN of affected MO] [oobMgmtAddr] of [name] is duplicate of [inbMgmtAddr]. Continue to use the old [oobMgmtAddr]
This fault occurs when the controller out-of-band management IP address a is duplicate of the inband managment IP address
If you see this fault, take the following actions:
Step 1 Modify the controller out-of-band management IP address
Step 2 If above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1479][duplicate-ibmgmt-ip][major][DN of affected MO] [inbMgmtAddr] of [name] is duplicate of [oobMgmtAddr]. Continue to use the old [inbMgmtAddr]
This fault occurs when the controller inband management IP address is a duplicate of the out-of-band managment IP address
If you see this fault, take the following actions:
Step 1 Modify the controller inband management IP address
Step 2 If above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1480][upgrade-failed][major][DN of affected MO] Fabric node [id] failed to upgrade to [desiredVersion]. The upgrade has an upgrade status of [upgradeStatus] - [upgradeStatusStr]. The failure occured at the [installStage] stage of the install.
This fault occurs when a software upgrade fails on a fabric node.
If you see this fault, take the following actions:
Step 1 Reboot the fabric node and retry the software installation using a policy upgrade.
Step 2 Reboot the fabric node and retry the software installation using the command line interface.
Step 3 If above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1483][protocol-bfd-adjacency-down][major][DN of affected MO] BFD session [discr] to neighbor [destAddr] on interface [ifId] has gone down. Reason: [diag].
%LOG_LOCAL0-4-SYSTEM_MSG [F1484][protocol-ospfv3-limits-exceeded][warning][DN of affected MO] OSPFv3 instance [name] is critically low in memory
This fault occurs when the ospfv3 instance memory alert is critical
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 Reduce the number of ospfv3 enabled interfaces
Step 4 Reduce the number of routes into ospfv3
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 [F1486][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 [F1487][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 [F1500][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 [F1501][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 [F1507][vrf-provisioning-failed][warning][DN of affected MO] External L3 interface router macs are not configured identically
This fault occurs when all the external L3 interfaces (created for external connectivity) are not configured with the same router mac. This might affect packet forwarding between the external L3 interfaces.
To recover from this fault, try the following actions
Step 1 Reconfigure all the external l3 interface router macs with the same value
Step 2 If the above action did not resolve the issue, try rebooting the switch using CLI or GUI.
Step 3 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1509][invalid-ibmgmt-encap][major][DN of affected MO] Inband mgmt encap vlan is invalid/missing
This fault occurs when APIC inband management encap vlan is invalid/missing
If you see this fault, take the following actions:
%LOG_LOCAL0-4-SYSTEM_MSG [F1510][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 [F1511][config-failure][warning][DN of affected MO] Route Nexthop configuration failure. Reason: [ipv4CfgState]
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-1-SYSTEM_MSG [F1526][equipment-card-failed][critical][DN of affected MO] Module [physId] failed
This fault occurs when a card sees a fatal error during runtime. The card is put in a fail state and cannot be put back in operation.
If a card is found in a fail state, 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-4-SYSTEM_MSG [F1527][equipment-full][warning][DN of affected MO] Storage unit [name] on Node [id] mounted at [mount] is [capUtilized]% full
This fault occurs when the utilization of storage capacity on a controller is greater than 75%
If you see this fault, take the following actions:
Step 1 Cleanup any files created by the user on the partition on the storage device that the fault was produced on to free up space
Step 2 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1528][equipment-full][major][DN of affected MO] Storage unit [name] on Node [id] mounted at [mount] is [capUtilized]% full
This fault occurs when storage capacity utilization is between 85% and 90%
If you see this fault, take the following action:
Step 1 Cleanup any files created by the user on the partition on the storage device that the fault was produced on to free up space
Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-1-SYSTEM_MSG [F1529][equipment-full][critical][DN of affected MO] Storage unit [name] on Node [id] mounted at [mount] is [capUtilized]% full
This fault occurs when storage capacity utilization is greater than 90%
If you see this fault, take the following action:
Step 1 replace the storage unit that is full
Step 2 cleanup the storage unit that has faulted
Step 3 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1534][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 [F1539][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 [F1543][node-inactive][critical][DN of affected MO] Node [id] is inactive and not reachable.
This fault occurs when a node is not reachable
If you see this fault, take the following action:
Step 1 Check connectivity for the node that cannot be reached
Step 2 Check if the node is powered up
Step 3 If the node is decommissioned, clean reboot the node manually as a workaround
Step 4 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-1-SYSTEM_MSG [F1544][node-unsupported][critical][DN of affected MO] Node [id] is unsupported or has been cabled incorrectly
This fault occurs when an unsupprted node is connected to the fabric
If you see this fault, take the following action:
Step 1 Check if the node is a supported model and has been cabled correctly
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1545][packets-dropped][major][DN of affected MO] [dropPktPercentage]% of packets were dropped during the last collection interval[dropPktPercentage]% of packets were dropped during the last collection interval on the path from node [srcNodeId] to node [dstNodeId][dropPktPercentage]% of packets were dropped during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the VPC pair [dstNodeId]-[dstNodeId2][dropPktPercentage]% of packets were dropped during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the single node [dstNodeId][dropPktPercentage]% of packets were dropped during the last collection interval on the path from the single node [srcNodeId] to the VPC pair [dstNodeId]-[dstNodeId2]
This fault occurs when a significant number of packet drops are detected by a configured and enabled Atomic Counter
If you see this fault, take the following actions:
Step 1 Check the network configuration in the packet path where this Atomic Counter Policy is configured.
Step 2 Check for any CRC, etc errors in the packet path where this Atomic Counter Policy is configured.
Step 3 Check interface counters and rates in the packet path where this Atomic Counter Policy is configured to make sure there is no oversubscription.
Step 4 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F1546][packets-dropped][minor][DN of affected MO] [dropPktPercentage]% of packets were dropped during the last collection interval[dropPktPercentage]% of packets were dropped during the last collection interval on the path from node [srcNodeId] to node [dstNodeId][dropPktPercentage]% of packets were dropped during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the VPC pair [dstNodeId]-[dstNodeId2][dropPktPercentage]% of packets were dropped during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the single node [dstNodeId][dropPktPercentage]% of packets were dropped during the last collection interval on the path from the single node [srcNodeId] to the VPC pair [dstNodeId]-[dstNodeId2]
This fault occurs when a small number of packet drops are detected by a configured and enabled Atomic Counter
If you see this fault, take the following actions:
Step 1 Check the network configuration in the packet path where this Atomic Counter Policy is configured.
Step 2 Check for any CRC, etc errors in the packet path where this Atomic Counter Policy is configured.
Step 3 Check interface counters and rates in the packet path where this Atomic Counter Policy is configured to make sure there is no oversubscription.
Step 4 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1547][packets-dropped][major][DN of affected MO] [excessPktPercentage]% of packets were received in excess during the last collection interval[excessPktPercentage]% of packets were received in excess during the last collection interval on the path from node [srcNodeId] to node [dstNodeId][excessPktPercentage]% of packets were received in excess during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the VPC pair [dstNodeId]-[dstNodeId2][excessPktPercentage]% of packets were received in excess during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the single node [dstNodeId][excessPktPercentage]% of packets were received in excess during the last collection interval on the path from the single node [srcNodeId] to the VPC pair [dstNodeId]-[dstNodeId2]
This fault occurs when a significant number of excess packets are detected by a configured and enabled Atomic Counter
If you see this fault, take the following actions:
Step 1 Check the network configuration in the packet path where this Atomic Counter Policy is configured.
Step 2 Check interface counters and rates in the packet path where this Atomic Counter Policy is configured to make sure there is no oversubscription.
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 [F1548][packets-dropped][minor][DN of affected MO] [excessPktPercentage]% of packets were received in excess during the last collection interval[excessPktPercentage]% of packets were received in excess during the last collection interval on the path from node [srcNodeId] to node [dstNodeId][excessPktPercentage]% of packets were received in excess during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the VPC pair [dstNodeId]-[dstNodeId2][excessPktPercentage]% of packets were received in excess during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the single node [dstNodeId][excessPktPercentage]% of packets were received in excess during the last collection interval on the path from the single node [srcNodeId] to the VPC pair [dstNodeId]-[dstNodeId2]
This fault occurs when a small number of excess packets are detected by a configured and enabled Atomic Counter
If you see this fault, take the following actions:
Step 1 Check the network configuration in the packet path where this Atomic Counter Policy is configured.
Step 2 Check interface counters and rates in the packet path where this Atomic Counter Policy is configured to make sure there is no oversubscription.
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 [F1549][packets-dropped][major][DN of affected MO] [dropPktPercentage]% of packets were dropped during the last collection interval[dropPktPercentage]% of packets were dropped during the last collection interval on the path from node [srcNodeId] to node [dstNodeId][dropPktPercentage]% of packets were dropped during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the VPC pair [dstNodeId]-[dstNodeId2][dropPktPercentage]% of packets were dropped during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the single node [dstNodeId][dropPktPercentage]% of packets were dropped during the last collection interval on the path from the single node [srcNodeId] to the VPC pair [dstNodeId]-[dstNodeId2]
This fault occurs when a significant number of packet drops are detected by a configured and enabled Atomic Counter
If you see this fault, take the following actions:
Step 1 Check the network configuration in the packet path where this Atomic Counter Policy is configured.
Step 2 Check for any CRC, etc errors in the packet path where this Atomic Counter Policy is configured.
Step 3 Check interface counters and rates in the packet path where this Atomic Counter Policy is configured to make sure there is no oversubscription.
Step 4 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F1550][packets-dropped][minor][DN of affected MO] [dropPktPercentage]% of packets were dropped during the last collection interval[dropPktPercentage]% of packets were dropped during the last collection interval on the path from node [srcNodeId] to node [dstNodeId][dropPktPercentage]% of packets were dropped during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the VPC pair [dstNodeId]-[dstNodeId2][dropPktPercentage]% of packets were dropped during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the single node [dstNodeId][dropPktPercentage]% of packets were dropped during the last collection interval on the path from the single node [srcNodeId] to the VPC pair [dstNodeId]-[dstNodeId2]
This fault occurs when a small number of packet drops are detected by a configured and enabled Atomic Counter
If you see this fault, take the following actions:
Step 1 Check the network configuration in the packet path where this Atomic Counter Policy is configured.
Step 2 Check for any CRC, etc errors in the packet path where this Atomic Counter Policy is configured.
Step 3 Check interface counters and rates in the packet path where this Atomic Counter Policy is configured to make sure there is no oversubscription.
Step 4 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1551][packets-dropped][major][DN of affected MO] [excessPktPercentage]% of packets were received in excess during the last collection interval[excessPktPercentage]% of packets were received in excess during the last collection interval on the path from node [srcNodeId] to node [dstNodeId][excessPktPercentage]% of packets were received in excess during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the VPC pair [dstNodeId]-[dstNodeId2][excessPktPercentage]% of packets were received in excess during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the single node [dstNodeId][excessPktPercentage]% of packets were received in excess during the last collection interval on the path from the single node [srcNodeId] to the VPC pair [dstNodeId]-[dstNodeId2]
This fault occurs when a significant number of excess packets are detected by a configured and enabled Atomic Counter
If you see this fault, take the following actions:
Step 1 Check the network configuration in the packet path where this Atomic Counter Policy is configured.
Step 2 Check interface counters and rates in the packet path where this Atomic Counter Policy is configured to make sure there is no oversubscription.
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 [F1552][packets-dropped][minor][DN of affected MO] [excessPktPercentage]% of packets were received in excess during the last collection interval[excessPktPercentage]% of packets were received in excess during the last collection interval on the path from node [srcNodeId] to node [dstNodeId][excessPktPercentage]% of packets were received in excess during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the VPC pair [dstNodeId]-[dstNodeId2][excessPktPercentage]% of packets were received in excess during the last collection interval on the path from the VPC pair [srcNodeId]-[srcNodeId2] to the single node [dstNodeId][excessPktPercentage]% of packets were received in excess during the last collection interval on the path from the single node [srcNodeId] to the VPC pair [dstNodeId]-[dstNodeId2]
This fault occurs when a small number of excess packets are detected by a configured and enabled Atomic Counter
If you see this fault, take the following actions:
Step 1 Check the network configuration in the packet path where this Atomic Counter Policy is configured.
Step 2 Check interface counters and rates in the packet path where this Atomic Counter Policy is configured to make sure there is no oversubscription.
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 [F1553][configuration-failed][major][DN of affected MO] Failed to configure SPAN with source [name] due to invalid EPG [tDn]: [stateQual]([state])
This fault is raised when the span policy failed to get deployed.
If you see this fault, take the following actions:
Step 1 Verify that the EPG in the relation?™s target DN is valid and present.
Step 2 Review the fault message and add missing or remove invalid configuration
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1554][configuration-failed][major][DN of affected MO] Failed to configure SPAN with source [name] due to missing/invalid private L3 network Context [tDn]: [stateQual]([state])
This fault is raised when the fabric span policy failed to get deployed due to missing Ctx.
If you see this fault, take the following actions:
Step 1 Verify that the Ctx in the relation?™s target DN is valid and present.
Step 2 Review the fault message and add missing or remove invalid configuration
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1555][configuration-failed][major][DN of affected MO] Failed to configure SPAN with source [name] due to missing/invalid private layer L2 network context [tDn]: [stateQual]([state])
This fault is raised when the fabric span policy failed to get deployed due to missing BD.
If you see this fault, take the following actions:
Step 1 Verify that the BD in the relation?™s target DN is valid and present.
Step 2 Review the fault message and add missing or remove invalid configuration
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1556][configuration-failed][major][DN of affected MO] Failed to configure SPAN destination [name]: port [tDn] on node [tDn] is not a local port relative to the SPAN source
This fault is raised when the span policy failed to get deployed.
If you see this fault, take the following actions:
Step 1 Verify that the PathEp in the relation?™s target DN contains local ports in the node where SrcGroup resides
Step 2 Review the fault message and add missing or remove invalid configuration
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1557][configuration-failed][warning][DN of affected MO] Failed to configure SPAN with destination group [name] due to missing/invalid destination group [tDn]
This fault is raised when the span policy failed to get deployed.
If you see this fault, take the following actions:
Step 1 Verify that the destionation group in the relation?™s target DN is present in the fabric.
Step 2 Review the fault message and add missing configuration
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1558][session-overflown][major][DN of affected MO] Failed to configure SPAN: The session has exceeded the maximum allowed (48)
This fault is raised when the number of span sessions deployed exceeds the maximum number allowed.
If you see this fault, take the following actions:
Step 1 Verify that the number of span sessions deployed is less than the maximum number allowed
Step 2 Review the fault message and add missing configuration
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1559][configuration-failed][major][DN of affected MO] Failed to configure SPAN with destination [name] of destination group [name] due to [fstate]Failed to configure SPAN with destination [name] of destination group [name] on tenant [name] due to [fstate]
This fault is raised when the a dest related configuration issues.
If you see this fault, take the following actions:
Step 1 Verify that the dest related configuration is correct.
Step 2 Review the fault message and add missing configuration
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1560][configuration-failed][major][DN of affected MO] Failed to configure SPAN with source group [name] due to [fstate]
This fault is raised when the a src related configuration issues.
If you see this fault, take the following actions:
Step 1 Verify that the dest related configuration is correct.
Step 2 Review the fault message and add missing configuration
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1561][configuration-failed][major][DN of affected MO] Failed to configure SPAN with source [name] due to [fstate]
This fault is raised when the an individual src related configuration issues.
If you see this fault, take the following actions:
Step 1 Verify that the source related configuration is correct.
Step 2 Review the fault message and add missing configuration
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1562][configuration-failed][major][DN of affected MO] Failed to configure SPAN with source [name] on port [tDn] on node [tDn] due to [fstate]
This fault is raised when the an individual RsSrcToPathEp related configuration issues.
If you see this fault, take the following actions:
Step 1 Verify that the Src to PathEp related configuration is correct.
Step 2 Review the fault message and add missing configuration
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1563][test-failure][major][DN of affected MO] my name is [dn]. my ancestor name is [dn] = [dn]. my ancestor is [dn]. Also ancestors priKey is [priKey]
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 [F1564][test-failure][major][DN of affected MO] my name is [dn]. my ancestor name is [dn] = [dn]. my ancestor is [dn]. Also ancestors priKey is [priKey]
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 [F1565][configuration-failed][minor][DN of affected MO] Device validate operation for device [name] in cluster [priKey] in tenant [priKey] failed
This fault occurs when the L4-L7 service node configuration fails
If you see this fault, please make sure that the device has the correct IP and is supported by the package.
%LOG_LOCAL0-3-SYSTEM_MSG [F1566][configuration-failed][minor][DN of affected MO] Device modify operation for device [name] in cluster [priKey] in tenant [priKey] failed
This fault occurs when the L4-L7 service node configuration fails
If you see this fault, please check for faults in the device configuration.
%LOG_LOCAL0-3-SYSTEM_MSG [F1567][configuration-failed][minor][DN of affected MO] Device audit operation for device [name] in cluster [priKey] in tenant [priKey] failed
This fault occurs when the L4-L7 service node configuration fails
If you see this fault, please check for faults in the device configuration.
%LOG_LOCAL0-1-SYSTEM_MSG [F1569][equipment-card-mismatch][critical][DN of affected MO] Module mismatch. One of the following is true: 1) this model is not compatible with other models already inserted 2) this model can not be inserted in this slot 3) if supervisor slot, there is a memory mismatch with active supervisor
This fault occurs when a wrong type of card is inserted in the chassis
If a card is found in mismatch state, then the card has to be replaced
%LOG_LOCAL0-2-SYSTEM_MSG [F1570][configuration-failed][major][DN of affected MO] Failed to configure SPAN with source [name] due to missing or invalid target EPG [tDn]: [stateQual]([state])
This fault occurs when a Span Policy fails to deploy due to a missing or invalid source EPG
If you see this fault, take the following actions:
Step 1 Verify that the configured source EPG in the Span Policy exists and is correct
Step 2 Review the fault message and add missing or remove invalid configuration
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 [F1571][configuration-failed][major][DN of affected MO] Failed to configure SPAN with destination [name] due to missing or invalid target EPG [tDn] with IP [ip]: [stateQual]([state])
This fault occurs when a Span Policy fails to deploy due to a missing or invalid destination EPG
If you see this fault, take the following actions:
Step 1 Verify that the configured destination EPG in the Span Policy exists and is correct
Step 2 Review the fault message and add missing or remove invalid configuration
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 [F1572][test-failure][major][DN of affected MO] This is the default messageThis is the message for switch, name is [name] and the switch only prop is [swCTestOnly]This is the message for IFC, name is [name] and the IFC only prop is [ifcCTestOnly]
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 [F1573][test-failure][major][DN of affected MO] This is the default messageThis is the message for switch, name is [name] and the switch only prop is [swCTestOnly]This is the message for IFC, name is [name] and the IFC only prop is [ifcCTestOnly]
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-1-SYSTEM_MSG [F1574][ntp-error][critical][DN of affected MO] Ntp configuration on Node [id] for [remote] is not reachable
This fault occurs when a ntp configuration on a controller has problems
If you see this fault, take the following actions:
Step 1 Verify that the ntp peers are correctly configured and are reachable.
Step 2 Verify that the ntp peers have the correct keys.
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 [F1582][firmware-version-mismatch][minor][DN of affected MO] FPGA version mismatch detected. Running version: [version] Expected version:[expectedVer]
This fault occurs when running FPGA firmware version is not an expected version.
Update the running FPGA firmware to the version bundled up with the current running image.
%LOG_LOCAL0-3-SYSTEM_MSG [F1583][firmware-version-mismatch][minor][DN of affected MO] BIOS version mismatch detected. Running version: [biosVer] Expected version:[expectedVer]
This fault occurs when running BIOS firmware is not an expected version.
Update the running BIOS firmware to the version recommended for the current running image.
%LOG_LOCAL0-4-SYSTEM_MSG [F1600][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 [F1601][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 [F1603][config-failure][warning][DN of affected MO] Address configuration failure. Reason: [ipv6CfgState]
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 [F1604][config-failure][warning][DN of affected MO] Route Nexthop configuration failure. Reason: [ipv6CfgState]
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-3-SYSTEM_MSG [F1606][oper-issues][minor][DN of affected MO] Operational issues detected on portgroup: [name] in VM Controller:[name], VM Domain:[domName], VM Provider:[vendor], error: [operIssues]
This fault is raised when issues are detected with portgroups learned from vCenter. E.g. missing EPg policy
If you see this fault, take the following actions:
Step 1 Fix the issue by creating the 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-3-SYSTEM_MSG [F1613][configuration-failed][minor][DN of affected MO] Controller management policy in tenant [name] is invalid.
This fault occurs when the inband mgmt policy posted by the user is incorrect. The config issues indicate the exact reason for the error.
If you see this fault, please modify the configuration to resolve cause of fault.
%LOG_LOCAL0-4-SYSTEM_MSG [F1614][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 [F1615][ip-provisioning-failed][major][DN of affected MO] IPv6 address is operationally down, reason:[operStQual]
This fault occurs when the operational state of the ipv6 address state is changed to subnet-overlap/no primary/addr already confgd as next hop in a static route
To recover from this fault, try the following actions
%LOG_LOCAL0-2-SYSTEM_MSG [F1616][oper-state-failed][major][DN of affected MO] Route NextHop is operationally down, reason:[operStQual]
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 [F1617][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 [F1629][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 [F1630][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 [F1631][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 [F1639][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 [F1640][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 [F1648][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 [F1649][configuration-failed][major][DN of affected MO] Operation on device Package on appliance [appliance] failed
This fault occurs when an operation on device package fails. The config issues indicate the exact reason for the error.
If you see this fault, please capture tech-support file, delete device package and repost the device package again.
%LOG_LOCAL0-3-SYSTEM_MSG [F1651][export-data-failed][minor][DN of affected MO] Upload triggered at [lastCollectionTime] for policy [polName] [lastCollectionStatus]. Check operational status for details.
This fault occurs when export operation for techsupport or core files did not succeed.
If you see this fault, take the following actions:
Step 1 look at techsupport status and figure out which IFC/node is erroring out.
Step 2 Verify the destination it is trying to export data to is healthy/reachable
Step 3 If the above action did not resolve the issue, contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1654][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 [F1655][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 [F1656][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 [F1657][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 [F1658][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 [F1659][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 [F1660][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 [F1661][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 [F1662][protocol-coop-version-mismatch][warning][DN of affected MO] Leaf (citizen node) with version:[curVersion] is lower than highest supported version:[councilMinMaxVersion] in fabric. Upgrade leaf [lastLowerVersionAddr] to a firmware revision which supports coop version [maxVersion]
This fault occurs when the version of the Council Of Oracles Protocol (COOP) running on a leaf (citizen node) is determined by the spine (oracle node) to be lower than what is currently supported. No impact to connectivity should be seen due to running at lower version. However, failure to upgrade to the fabric node firmware on the leaf that contains highest supported version of coop may impact coop performance or coop may not operate with supported functionalities introduced in the higher coop version.
To recover from this fault, try the following actions
Step 1 Verify there is no leaf (citizen node) with a lower coop version than highest supported version running in the fabric. To verify the leaf with lower version:
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use the GUI to examine the maxVersion value under Fabric Inventory Pod Leaf Protocols COOP [domain-name] ; or
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use REST API to examine the maxVersion value from https://[leaf-ip]/api/mo/sys/coop/inst/dom-[domain-name].xml; or
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use CLI to examine the maxVersion value in file /mit/sys/coop/inst/dom-[domain-name]
Step 2 Upgrade the fabric node software on the leaf in question to a version that has the highest supported coop version running in the fabric. You can examine other leafs to determine what switch firmware version to upgrade to.
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 [F1663][protocol-coop-version-mismatch][warning][DN of affected MO] Spine (oracle node) with version:[curVersion] is lower than highest supported version:[maxVersion] in fabric. Upgrade spine in question to a firmware revision which supports coop version [maxVersion]
This fault occurs when the version of the Council Of Oracles Protocol (COOP) running on a spine (oracle node) is determined by another spine to be lower than what is currently supported. No impact to connectivity should be seen due to running at lower version. However, failure to upgrade the fabric node firmware on the spine that contains highest supported version of coop may impact coop performance or coop may not operate with supported functionalities introduced in the higher coop version.
To recover from this fault, try the following actions
Step 1 Verify there is no spine (oracle node) with a lower coop version than highest supported version running in the fabric. To verify the spine with the lower version:
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use the GUI to examine the maxVersion value under Fabric Inventory Pod Leaf Protocols COOP [domain-name] Oracle Adjacencies [spine ip]; or
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use REST API to examine the maxVersion value from https://[spine-ip]/api/mo/sys/coop/inst/dom-[domain-name].xml?query-target=subtree=coopOracleAdj; or
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use CLI to examine the maxVersion value in file /mit/sys/coop/inst/dom-[domain-name]/oracle-[spine-ip]
Step 2 Upgrade the fabric node software on the spine in question to a version that has the highest supported coop version running in the fabric. You can examine other spines to determine what switch firmware version to upgrade to.
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 [F1664][protocol-coop-version-mismatch][warning][DN of affected MO] Spine (oracle node) or leaf (citizen node) with version:[curVersion] is lower than highest supported version:[maxVersion] in fabric. Upgrade node in question to a firmware revision which supports coop version [maxVersion]
This fault occurs when the version of the Council Of Oracles Protocol (COOP) running on a leaf (citizen node) or spine (oracle node) is determined by a leaf to be lower than what is currently supported. No impact to connectivity should be seen due to running at lower version. However, failure to upgrade the fabric node firmware on the node in question to the highest supported version of coop may impact coop performance or coop may not operate with supported functionalities introduced in the higher coop version.
To recover from this fault, try the following actions
Step 1 Verify there is no spine (oracle node) with a lower coop version than highest supported version running in the fabric. To verify the spine with lower version:
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use the GUI to examine the maxVersion value under Fabric Inventory Pod Leaf Protocols COOP [domain-name] Oracle Adjacencies [spine ip]; or
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use REST API to examine the maxVersion value from https://[spine-ip]/api/mo/sys/coop/inst/dom-[name].xml?query-target=subtree=coopOracleAdj; or
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use CLI to examine the maxVersion value in file /mit/sys/coop/inst/dom-[domain-name]/oracle-[spine-ip]
Step 2 Upgrade the fabric node software on the spine in question to a version that has the highest supported coop version running in the fabric. You can examine other spines to determine what switch firmware version to upgrade to.
Step 3 Verify there is no leaf (citizen node) with a lower coop version than highest supported version running in the fabric. Identify the leaf node that has a lower coop version by doing the following on any spine:
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use the GUI to examine the lastLowerVersionAddr under Fabric Inventory Pod Leaf Protocols COOP [domain-name] ; or
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use REST API to examine the lastLowerVersionAddr value from https://[spine-ip]/api/mo/sys/coop/inst/dom-[domain-name].xml; or
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use CLI to examine the lastLowerVersionAddr value in file /mit/sys/coop/inst/dom-[domain-name] Now confirm the supported highest version for the leaf node, identified from above, is lower than highest supported in fabric as follow:
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use the GUI to examine the maxVersion under Fabric Inventory Pod Leaf Protocols COOP [domain-name]; or
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use REST API to examine the maxVersion value from https://[leaf-ip]/api/mo/sys/coop/inst/dom-[domain-name].xml; or
??img src="./Cisco ACI System Messages Reference Guide - ACI System Messsages [Cisco Application Policy Infrastructure Controller (APIC)] - Cisco_files/blank.gif" alt="" width="19" height="2" border="0"> Use CLI to examine the maxVersion value in file /mit/sys/coop/inst/dom-[domain-name]
Step 4 Upgrade the fabric node software on the leaf in question to a version that has the highest supported coop version running in the fabric. You can examine other leafs to determine what switch firmware version to upgrade to.
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 [F1665][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 [F1669][configuration-failed][minor][DN of affected MO] Controller profile [hostOrIp] with name [name] in SCVMM Cloud [rootContName] in domain [name] configuration failed due to [msftConfigIssues]
This fault is raised when the SCVMM plugin encounters an exception in provisioning vmmCtrlrP.
If you see this fault, take the following actions:
Step 1 Check the system events in the SCVMM or WAP machine for details.
%LOG_LOCAL0-4-SYSTEM_MSG [F1674][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 [F1676][connect-failed][major][DN of affected MO] Communication status for Microsoft Agent is [operSt]
This fault is raised when the VMM Controller Agent is not able to communicate with the APIC.
If you see this fault, take the following actions:
Step 1 Verify that the SCVMM server is online.
Step 2 Verify that the ACI SCVMM Agent is running on the SCVMM Server
Step 3 Review the HostnameOrIp configuration. Connections to an SCVMM HA setup should be configured with the SCVMM HA IP or FQDN, not the individual Cluster Node infromation nor the Windows Failover Cluster information.
Step 4 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1678][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 [F1680][ac-provisioning-failed][minor][DN of affected MO] [ruleId] configuration for [tenantName] [vrfName] has failed due to [operStateQual]
This fault occurs when either the total Atomic Counter rule reaches maximum programmable limit or an unsupported modification is made on an Atomic counter policy. The acRule does not get programmed and is instead stuck in failed state.
To recover from this fault, try the following actions
Step 1 If the fault occurred because of a policy modification, disable and re-enable the atomic counter policy with the changes.
Step 2 If the fault occurred because the maximum limit was reached, remove unneeded Atomic Counter configuration policies to accommodate new policies.
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 [F1686][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 [F1688][interface-physical-invalid-xcvr][critical][DN of affected MO] Transceiver is defective and unable to be brought up in system
This fault occurs when a transceiver is defective and unable to be used in the system
To recover from this fault, try the following actions
%LOG_LOCAL0-3-SYSTEM_MSG [F1690][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 [F1691][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 [F1692][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 [F1693][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 [F1696][interface-physical-provisioning-failed][warning][DN of affected MO] Port has invalid configuration of both EPG and span destination
This fault occurs when a port is set to epg and also a span destination which is invalid.
To recover from this fault, try the following actions
%LOG_LOCAL0-2-SYSTEM_MSG [F1698][operational-issues][major][DN of affected MO] Operational issues detected for OpFlex device: [hostName], error: [[state]]
This fault is raised when there is an issue with respect to the OpFlex device
If you see this fault, take the following actions:
Step 1 To restore, delete and re-add the OpFlex device.
Step 2 Check connectivity to the OpFlex device.
Step 3 Try restarting the device.
Step 4 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1699][protocol-ntp-provisioning-failed][warning][DN of affected MO] Ntp configuration on [role] [name] is not synced to NTP server
This fault occurs when a ntp configuration on a switch has problems
If you see this fault, take the following actions:
Step 1 Verify that the ntp peers are correctly configured and are reachable.
Step 2 Verify that the ntp peers have the correct keys.
Step 3 Configure multiple NTP servers for to guarantee availability of a valid NTP Server for synchronization.
Step 4 If NTP Servers are configured with a DNS Name and not an IP Address, Verify if it?™s a valid domain name and verify if the policy with DNS providers are configured.
Step 5 If there is a firewall in-between the ACI Fabric and NTP Servers, make sure that the firewall allows NTP traffic.
Step 6 Verify whether NTP daemon is running in all or some of the NTP servers.
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 [F1700][protocol-ntp-sync-failed][minor][DN of affected MO] Ntp configuration on [role] [name] is [srvStatus]
This fault occurs when a ntp configuration on a controller has problems
If you see this fault, take the following actions:
Step 1 Verify that the ntp peers are correctly configured and are reachable.
Step 2 Verify that the ntp peers have the correct keys.
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 [F1703][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 [F1706][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 [F1707][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 [F1712][deployment-failed][major][DN of affected MO] VIP Not Allocated
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 [F1722][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 [F1726][configuration-failed][minor][DN of affected MO] Duplicate IP address: [descr]Duplicate out-of-band management address: [descr]Duplicate in-band management address: [descr]
This fault occurs when the same IP address is configured on multiple nodes.
If you see this fault, take the following actions:
Step 1 Identify the nodes that are using the same IP address.
Step 2 Fix address pools, or the static IP that is assigned to the conflicting nodes.
Step 3 If above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1729][protocol-ospfv3-adjacency-down][warning][DN of affected MO] OSPFv3 adjacency is not full, current state [operSt]
This fault occurs when the adjacency state is not up
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 Check network connectivity to the peer
Step 4 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1731][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 [F1778][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 [F1781][configuration-failed][minor][DN of affected MO] Multiple IP addresses: [descr]Mulitple out-of-band management addresses: [descr]Multiple in-band management addresses: [descr]
This fault occurs when the same node is configured with mulitple addresses.
If you see this fault, take the following actions:
Step 1 Identify the node that has duplicate addresses.
Step 2 Fix address pools, management groups that assign multiple addresses to the same node.
Step 3 If above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F1782][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tDn] of class [tCl]
%LOG_LOCAL0-3-SYSTEM_MSG [F1783][configuration-failed][minor][DN of affected MO] Failed to allocate address for appliance [appliance].
This fault occurs when the system could not allocate an ip address for one or more nodes in the cluster. The configIssues indicate the exact reason for the error.
If you see this fault, please check if the address range (fvns:AddrInst) is valid and sufficient for the cluster.
%LOG_LOCAL0-1-SYSTEM_MSG [F1784][protocol-mcp-topology-anomaly][critical][DN of affected MO] Loop is detected on lower priority MCP interface [id]
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 [F1785][protocol-mcp-topology-anomaly][critical][DN of affected MO] Loop is detected on higher priority MCP interface [id]
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-4-SYSTEM_MSG [F1786][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 [F1787][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 [F1792][protocol-ospfv3-limits-exceeded][warning][DN of affected MO] Number of non-self-originated LSAs [nonSelfLsaCnt] has exceeded allowed limit [maxLsa]
This fault occurs when the number of non-self-originated LSAs from the neighbor is greater than the configured 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 [F1793][protocol-ospf-limits-exceeded][warning][DN of affected MO] Number of non-self-originated LSAs [nonSelfLsaCnt] has exceeded allowed limit [maxLsa]
This fault occurs when the number of non-self-originated LSAs from the neighbor is greater than the configured 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 [F1794][bd-limits-exceeded][warning][DN of affected MO] Optimized flooding is ignored on this BD [name]
This fault occurs when the optimized flood mode is ignored on the BD because of resource limitations. The current limit for optimized flood is 50 BDs deployed on the node
If this fault is consistently happening, try the following actions
Step 1 Change the unknown multicast destination action to flood mode
Step 2 Reduce the number of BDs with unknown multicast destination action in opt-flood mode
%LOG_LOCAL0-2-SYSTEM_MSG [F1798][ip-provisioning-failed][major][DN of affected MO] IPv6 LLaddress is operationally down, reason:[lloperStQual]
This fault occurs when the operational state of the ipv6 LL address state is changed to subnet-overlap/no primary/addr already confgd as next hop in a static route
To recover from this fault, try the following actions
%LOG_LOCAL0-4-SYSTEM_MSG [F1799][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 [F1800][actrl-resource-unavailable][major][DN of affected MO] [pfxRuleFailed] number of Prefix failed
This fault occurs when the policy manager on the affected object fails to activate a prefix entry due to either a hardware or software programming failure
To recover from this fault, try the following actions
Step 1 Verify Policy CAM usage on the Operations Capacity Dashboard
Step 2 Remove unused contracts and filters applied to EPGs
Step 3 Collect an on-demand techsupport which includes the leaf switches described in the affected object and contact TAC
%LOG_LOCAL0-2-SYSTEM_MSG [F1801][actrl-resource-unavailable][major][DN of affected MO] [zoneRuleFailed] number of Rules failed
This fault occurs when the policy manager fails to activate a contract filter rule on the affected object due to either a hardware or software programming failure
To recover from this fault, try the following actions
Step 1 Verify Policy CAM usage on the Operations Capacity Dashboard
Step 2 Remove unused contracts and filters applied to EPGs
Step 3 Collect an on-demand techsupport which includes the leaf switches described in the affected object and contact TAC
%LOG_LOCAL0-4-SYSTEM_MSG [F1806][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 [F1807][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 [F1808][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 [F1809][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 [F1810][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 [F1811][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 [F1812][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 [F1813][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 [F1815][invalid-transceiver][critical][DN of affected MO] Transceiver is invalid and unable to be brought up in system
This fault occurs when a transceiver is invalid or has hardware issues.
To recover from this fault, try the following actions
Step 1 Remove the defective transceiver and replace with valid one.
%LOG_LOCAL0-2-SYSTEM_MSG [F1816][protocol-isis-dom-down][major][DN of affected MO] Failed to bring up protocol on the VRF [name].
This fault usually occurs when protocol bring up on a VRF fails.
If you see this fault, take the following actions:
Step 1 Try shutting down and restarting the ISIS instance.
Step 2 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F1817][configuration-failed][major][DN of affected MO] Failed to configure SPAN with too many sessions
This fault is raised when the span policy failed to get deployed.
If you see this fault, take the following actions:
Step 1 Verify that there are too many sessions configured.
Step 2 Review the fault message and remove some unused span configuration
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.