%LOG_LOCAL0-3-SYSTEM_MSG [F0020][configuration-failed][minor][DN of affected MO] Configuration failed for node [name] due to [configQual]Configuration failed for [dn] for node [name] due to [configQual]
This fault occurs when a fabric selector (port selector, card selector, node selector etc.) is incorrectly configured.
If you see this fault, take the following actions:
Step 1 Look at the configuration for issues
Step 2 For invalid-port, check the fabric port selector, it should have only fabric ports in it. Leaf host ports and fex host ports are not allowed to be configured using fabric port selector.
Step 3 For port-configured-for-apic, check the fabric port selector. Port connected to the controller cannot be configured using fabric port selector.
Step 4 For invalid-card, check the fabric card selector, its referring to a card which does not exist. Fault will clear once the card is added to the node.
Step 5 For further details, refer to the documentation for fabric:SelectorIssues
Step 6 Verify the fabric selector configuration is correct and complete
Step 7 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F0021][inoperable][minor][DN of affected MO] Radius Provider [name] unreachable
This fault occurs when the Radius Provider is not operational.
If you see this fault, take the following actions:
Step 1 Verify the IP address and path to the Radius provider are still active and functioning.
Step 2 Ensure the configuration on the Radius provider has not changed.
Step 3 Verify that the Radius provider is still functioning properly
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 [F0022][inoperable][minor][DN of affected MO] LDAP Provider [name] unreachable
This fault occurs when the LDAP provider is not operational.
If you see this fault, take the following actions:
Step 1 Verify the IP address and path to the LDAP provider are still active and functioning.
Step 2 Ensure the configuration on the LDAP provider has not changed.
Step 3 Verify that the LDAP provider is still functioning properly
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 [F0023][inoperable][minor][DN of affected MO] Tacacs+ Provider [name] unreachable
This fault occurs when the TACACS+ provider is not operational.
If you see this fault, take the following actions:
Step 1 Verify the IP address and path to the TACACS+ provider are still active and functioning.
Step 2 Ensure the configuration on the TACACS+ provider has not changed.
Step 3 Verify that the TACACS+ provider is still functioning properly
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 [F0048][stats-export-failed][minor][DN of affected MO] Statistics export failed. 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-2-SYSTEM_MSG [F0051][ac-tenant-drops][major][DN of affected MO] [percentDropP]% of packets were dropped during the last collection interval for [name] policy of type [type] under Tenant [dn]
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-2-SYSTEM_MSG [F0052][ac-tenant-excess-pkts][major][DN of affected MO] [percentExssP]% of packets were received in excess during the last collection interval for [name] policy of type [type] under Tenant [dn]
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 [F0053][configuration-failed][minor][DN of affected MO] Configuration backup/restore job [name] failed with error: [details]
This fault occurs when a configuration export/import job fails.
If you see this fault, take the following actions:
Step 1 Verify that the Controllers can reach the remote destination without issues and that the remote file is correct
Step 2 Verify that the remote destination is healthy.
Step 3 To clear this fault, you can acknowledge the job. In GUI:
Step 4 Navigate to the Operational tab of the config policy
Step 5 Select the failed job, and choose Delete from the Actions menu
Step 6 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F0058][download-failed][major][DN of affected MO] Failed to download the firmware image from source: [name], reason: [operQual], details: [operQualStr]
This fault occurs when a firmware download fails
If you see this fault, take the following actions:
Step 1 Verify the location where the firmware stored is reachable through scp/http request
Step 2 Verify the directory and file location exist
Step 3 Verify the firmware file is valid
Step 4 Verify the file has sufficient permissions
Step 5 Free-up firmware repo by deleting any stale/old images.
Step 6 Verify username/password authentication
Step 7 Enclose the ip address within square brackets if specifying a v6 address. Otherwise, it will be considered as a hostname.
Step 8 If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F0080][address-assignment-failed][major][DN of affected MO] DHCP server (ID [id]) with an IP address of [ip] could not assign additional IP addresses.
This fault is raised when the DHCP server runs out of IP address to allocate to clients
If you see this fault, take the following actions:
Step 1 Decommission if there are any unused switches in the fabric.
Step 2 If the above actions did not resolve the issue, collect a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F0098][stats-export-failed][minor][DN of affected MO] Statistics export failed. 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-2-SYSTEM_MSG [F0101][equipment-failed][major][DN of affected MO] Storage unit [name] on Node [id] has failed.
This fault occurs when a storage device fails on a controller
If you see this fault, take the following actions:
%LOG_LOCAL0-2-SYSTEM_MSG [F0103][port-down][major][DN of affected MO] Physical Interface [id] on Node [id] is now [operSt]
This fault occurs when a physical interface on a controller is in the link-down state.
If you see this fault, take the following actions:
Step 1 Verify that the physical port is properly connected to the peer device.
Step 2 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-1-SYSTEM_MSG [F0104][port-down][critical][DN of affected MO] Bond Interface [id] on Node [id] is now [operSt]
This fault occurs when a bond interface on a controller is in the link-down state.
If you see this fault, take the following actions:
Step 1 Verify that the physical ports that make up the bond are properly connected to the peer devices.
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 [F0105][upgrade-failed][major][DN of affected MO] Controller [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 controller
If you see this fault, take the following actions:
Step 1 If upgrade is done via API, check if the image version entered is correct.
Step 2 Delete the image from repo, delete and repost the firmware policy.
Step 3 Free-up stale/old images, delete and repost the firmware policy.
Step 4 Reboot the controller and retry the software installation using a policy based upgrade.
Step 5 Reboot the controller and retry the software installation using the command line interface.
Step 6 If above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-1-SYSTEM_MSG [F0106][wiring-check-failed][critical][DN of affected MO] Physical Interface [id] on Node [id] is out of service. Reason: [wiringIssues]
This fault occurs when a port is out-of-service because of a wiring error.
If you see this fault, take the following actions:
Step 1 Ensure the device connected to the port is the correct device.
Step 2 Ensure the device connected to the port is configured properly for the fabric it is being connected to.
Step 3 If the device being connected is being reprovisioned from another fabric, ensure that the config on that device has been factory reset
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 [F0111][operational-issues][major][DN of affected MO] Operational issues detected on LooseNode: [id], error: [[operIssues]]
This fault occurs when operational issues are detected on a LooseNode (Unmanaged switch)
If you see this fault, take the following action:
Step 1 Check and reestablish LooseNode connectivity to Leaf Node
Step 2 If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F0130][connect-failed][major][DN of affected MO] Connection to VMM controller: [hostOrIp] with name [name] in datacenter [rootContName] in domain: [domName] is failing repeatedly with error: [[remoteErrMsg]]. Please verify network connectivity of VMM controller [hostOrIp] and check VMM controller user credentials are valid.
This fault is raised when the VMM Controller is marked offline. Recovery is in process.
If you see this fault repeatedly, take the following actions:
Step 1 Verify that there is network connectivity to VMM Controller.
Step 2 Verify that the user credentials to VMM Controller are correct.
Step 3 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F0132][operational-issues][major][DN of affected MO] Operational issues detected for VMM controller: [hostOrIp] with name [name] in datacenter [rootContName] in domain: [domName] due to error: [remoteOperIssues].
This fault is raised when Remote or External disruptive operations on VMM Controller are detected.
If you see this fault, take the following actions:
Step 1 To restore, delete and re-add the VMM Controller.
Step 2 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F0133][unsupported-operation][major][DN of affected MO] Unsupported remote operation on controller: [hostOrIp] with name [name] in datacenter [rootContName] in domain [domName] detected, error: [[deployIssues]]
This fault is raised when deployment of given configuration fails for a Controller.
If you see this fault, take the following actions:
Step 1 Try to delete and add the policy again.
Step 2 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F0134][config-issues][minor][DN of affected MO] Config Issues detected on LooseNode: [nbrName] connected to Host: [name] for controller: [hostOrIp] with name [name] in datacenter [rootContName] in domain [domName], error: [[configIssues]]
This fault is raised when LooseNode (Unmanaged switch) has config issues such as missing Management Address config.
If you see this fault, take the following actions:
Step 1 Configure Management Address address on LooseNode and ensure that LLDP or CDP is enabled to advertise Management Address
Step 2 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F0135][unsupported-operation][major][DN of affected MO] Unsupported remote operation detected on EPG: [faultDKey] detected in Controller: [hostOrIp] with name [name] in datacenter [rootContName] in domain [domName], error: [[remoteOperIssues]]
This fault is raised when remote or external disruptive EPG operations are performed on the Controller.
If you see this fault, take the following actions:
Step 1 Restore EPG to its original state on the Controller.
Step 2 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F0214][operational-issues][major][DN of affected MO] Operational issues detected for OpFlex device: [devId] [ip] for logical switch [lNodeDn] detected, error: [[devOperIssues]]
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-2-SYSTEM_MSG [F0256][protocol-coop-topology-anomaly][major][DN of affected MO] Inconsistent configuration in the coop council
This fault occurs when the coop domain has inconsistent configuration in the council
To recover from this fault, try the following actions
%LOG_LOCAL0-4-SYSTEM_MSG [F0299][protocol-bgp-adjacency-down][warning][DN of affected MO] BGP peer is not established, current state [operSt]
This fault occurs when the peer state is not established
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-1-SYSTEM_MSG [F0309][init-failure][critical][DN of affected MO] Replica [rplId] in the internal database partition (shard) [shrdId] for the service [name] failed to initialize or failed to copy database snapshot from its peer.
This fault occurs when a controller reports some data for service failed to initialize.
If you see this fault, take the following actions:
Step 1 Check cluster connectivity. All controllers need to be listed and reported as available.
Step 2 Ensure that the cluster configuration is stable. Make note of any any frequent and brief interruptions of cluster availability or prolonged unavailability.
Step 3 If any controllers are missing from the cluster, check if those controllers are accessible via other means like ssh.
Step 4 Check for other faults related to cluster health and availability
Step 5 If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F0310][commit-log-corruption][major][DN of affected MO] Corruption in the commit log for replica [rplId] in the internal database partition (shard) [shrdId] for service [name]
This fault occurs when a controller reports some data for a service has been corrupted.
If you see this fault, take the following actions:
Step 1 Check for errors regarding the disks in the controller
Step 2 Check the error logs on the controller to see if there is any additional information.
Step 3 If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F0317][database-corruption][major][DN of affected MO] Corruption in the database for replica [rplId] in the internal database partition (shard) [shrdId] for service [name]
This fault occurs when a controller reports data in the internal datastore for a given service has been corrupted.
If you see this fault, take the following actions:
Step 1 Check for errors regarding the disks in the controller
Step 2 Check the error logs on the controller to see if there is any additional information.
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 [F0320][configuration-failed][minor][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 minor fault
If you see this fault, please refer to L4-L7 device vendor documentation.
%LOG_LOCAL0-1-SYSTEM_MSG [F0321][unhealthy][critical][DN of affected MO] Controller [id] is unhealthy because: [health]
This fault occurs when a controller reports the distributed internal database (data layer) of the controller cluster is not fully functional.
If you see this fault, take the following actions:
Step 1 Check cluster connectivity. All controllers need to be listed and reported as available.
Step 2 Ensure that the cluster configuration is stable. Make note of any any frequent and brief interruptions of cluster availability or prolonged unavailability.
Step 3 If any controllers are missing from the cluster, check if those controllers are accessible via other means like ssh.
Step 4 Check for other faults related to cluster health and availability
Step 5 Check that all services are up and running on all controllers.
Step 6 Check for any process crashes and cores.
Step 7 If there are core files, collect them for Cisco TAC.
Step 8 If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-1-SYSTEM_MSG [F0323][unhealthy][critical][DN of affected MO] Lost connectivity to leader for some data subset(s) of [name] on controller [id]
This fault occurs when a controller reports it has lost connectivity to the replica leader for one or more data subsets of specific service. The service cannot process request in this state.
If you see this fault, take the following actions:
Step 1 Check cluster connectivity. All controllers need to be listed and reported as available.
Step 2 Ensure that the cluster configuration is stable. Make note of any any frequent and brief interruptions of cluster availability or prolonged unavailability.
Step 3 Check that the service in question is running on all controllers.
Step 4 Check for any process crashes and cores.
Step 5 If there are core files, collect them for Cisco TAC.
Step 6 If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F0324][configuration-failed][major][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 major fault
If you see this fault, please refer to L4-L7 device vendor documentation.
%LOG_LOCAL0-1-SYSTEM_MSG [F0325][unhealthy][critical][DN of affected MO] Connectivity has been lost to the leader for some data subset(s) of a service on controller [id], the service may have unexpectedly restarted or failed.
This fault occurs when a controller reports it has lost connectivity to the cluster replica leader for one or more data subsets for a service. The service cannot process requests in this state.
If you see this fault, take the following actions:
Step 1 Check cluster connectivity. All controllers need to be listed and reported as available.
Step 2 Ensure that the cluster configuration is stable. Make note of any any frequent and brief interruptions of cluster availability or prolonged unavailability.
Step 3 Check that the service in question is running on all controllers.
Step 4 Check for any process crashes and cores.
Step 5 If there are core files, collect them for Cisco TAC.
Step 6 If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F0329][configuration-failed][major][DN of affected MO] Device Package from [priKey] for [priKey] version [priKey] has stopped and restart count has exceeded maximum attempts
This fault occurs when the there is a failure in starting the service script
%LOG_LOCAL0-3-SYSTEM_MSG [F0330][configuration-failed][minor][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 version of device package.
%LOG_LOCAL0-4-SYSTEM_MSG [F0338][protocol-ospf-limits-exceeded][warning][DN of affected MO] OSPF instance [name] is critically low in memory
This fault occurs when the ospf 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 ospf enabled interfaces
Step 4 Reduce the number of routes into ospf
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 [F0341][protocol-dhcp-interface-down][major][DN of affected MO] DHCP Client interface operational state failed
This fault occurs when the operational state of the dhcp client interface changes to failed state
To recover from this fault, try the following actions
Step 1 Check the network connectivity between APIC controller and the node
Step 2 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 [F0344][protocol-igmpsnoop-limits-exceeded][major][DN of affected MO] IGMP Snooping local learning is disabled
This fault occurs when the igmp snooping local learning is disabled
To recover from this fault, try the following actions
Step 1 Reduce the number of multicast groups in the network behind the leaf node
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 [F0345][protocol-igmpsnoop-limits-exceeded][major][DN of affected MO] IGMP Snooping fabric learning is disabled
This fault occurs when the igmp snooping fabric learning is disabled
To recover from this fault, try the following actions
Step 1 Reduce the number of multicast groups in the fabric
Step 2 If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F0350][oper-state-failed][warning][DN of affected MO] Multiple neighbors discovered on port [id]
This fault occurs when multiple neighbors are discovered on the interface
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 [F0360][protocol-isis-down][warning][DN of affected MO] Tree id [id] with root [root] became inactive
This event occurs when the oper state of a Mcast tree changes to inactive.
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 [F0361][protocol-isis-topology-anomaly][warning][DN of affected MO] Tree id [id] with root [root] has large dia [diameter]
This event occurs when the tree diameter of a Mcast tree is deemed large.
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 [F0377][protocol-isis-limits-exceeded][warning][DN of affected MO] ISIS instance is critically low in memory
This fault occurs when the isis instance memory alert is critical
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 [F0391][protocol-isis-interface-initialization-failed][major][DN of affected MO] ISIS process encountered error in bringing up protocol on the interface [id]
This fault usually occurs when ISIS interface specific initaliztion 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 [F0394][protocol-isis-interface-level-down][major][DN of affected MO] Software error encountered during protocol processing for interface
This fault usually occurs when ISIS interface specific protocol handling 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-3-SYSTEM_MSG [F0397][inoperable][minor][DN of affected MO] Radius Provider [name] unreachable
This fault occurs when the Radius Provider is not operational.
If you see this fault, take the following actions:
Step 1 Verify the IP address and path to the Radius provider are still active and functioning.
Step 2 Ensure the configuration on the Radius provider has not changed.
Step 3 Verify that the Radius provider is still functioning properly
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 [F0398][inoperable][minor][DN of affected MO] Ldap Provider [name] unreachable
This fault occurs when the LDAP provider is not operational.
If you see this fault, take the following actions:
Step 1 Verify the IP address and path to the LDAP provider are still active and functioning.
Step 2 Ensure the configuration on the LDAP provider has not changed.
Step 3 Verify that the LDAP provider is still functioning properly
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 [F0400][inoperable][minor][DN of affected MO] Tacacs+ Provider [name] unreachable
This fault occurs when the TACACS+ provider is not operational.
If you see this fault, take the following actions:
Step 1 Verify the IP address and path to the TACACS+ provider are still active and functioning.
Step 2 Ensure the configuration on the TACACS+ provider has not changed.
Step 3 Verify that the TACACS+ provider is still functioning properly
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 [F0401][equipment-diags-restricted][minor][DN of affected MO] Diagnostics test not supported.
This fault occurs when a diagnostic test is not supported.
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 [F0402][equipment-diags-restricted][minor][DN of affected MO] Diagnostics test not accessible.
This fault occurs when a diagnostic test subject is not accessible.
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 [F0403][equipment-diags-restricted][minor][DN of affected MO] Ondemand diagnostics test not supported.
This fault occurs when a on-demand diagnostic test is not supported.
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 [F0404][equipment-diags-restricted][minor][DN of affected MO] Ondemand diagnostics test not accessible.
This fault occurs when a on-demand diagnostic test subject is not accessible.
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 [F0411][equipment-psu-failed][minor][DN of affected MO] Power supply failed. (serial number [ser])
This fault occurs when psu is failed
To recover from this fault, try the following actions
Step 1 Replace the power supply unit
Step 2 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC
%LOG_LOCAL0-3-SYSTEM_MSG [F0412][equipment-psufan-failed][minor][DN of affected MO] Fan in power supply failed
This fault occurs when the fan in the psu is failed
To recover from this fault, try the following actions
Step 1 Replace the power supply unit
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 [F0415][equipment-card-failed][major][DN of affected MO] Supervisor powered up in wrong slot (Serial number [ser])
This fault typically occurs when the SUP is inserted in the wrong slot
To recover from this fault, try the following actions
Step 1 Insert the SUP in the correct slot
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 [F0416][equipment-card-failed][major][DN of affected MO] Unknown software card id
This fault typically occurs when a card with an unknown card id is inserted in the chassis
To recover from this fault, try the following actions
Step 1 Remove the card from the chassis
Step 2 Fix the software card index to one of the known types
Step 3 If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC
%LOG_LOCAL0-3-SYSTEM_MSG [F0418][configuration-failed][minor][DN of affected MO] Configuration failed for [name], [name] [name] [name]
This fault occurs when a Contract, with a scope set as something other than Context, is added to an ?™EPG Collection for Context??in a Private Network
If you see this fault, take the following actions:
Step 1 Look at each Contract associated to the Private Network?™s ?™EPG Collection for Context??
Step 2 Verify that all of these Contracts have a scope of "Context"
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 [F0440][equipment-sprom-failed][major][DN of affected MO] Sprom failed [errRsn]
This fault usually occurs if the backplane sprom is corrupted
If you see this fault, take 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 [F0441][equipment-sprom-failed][major][DN of affected MO] Chassis IDPROM is invalid
This fault would occur if the backplane IDPROM contents become invalid or corrupted
If you see this fault, take the following actions:
Step 1 Create a show tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F0449][equipment-sensor-failed][major][DN of affected MO] Sensor of type [type] on Node [id] has failed.
This fault usually occurs if sensor fails
If you see this fault, take the following actions:
Step 1 replace the component that has failed
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 [F0454][wiring-check-failed][major][DN of affected MO] Port [id] is out of service due to [wiringIssues]
This fault occurs when a port is out-of-service because of a wiring error.
If you see this fault, take the following actions:
Step 1 Ensure the device connected to the port is the correct device.
Step 2 Ensure the device connected to the port is configured properly for the fabric it is being connected to.
Step 3 If the device being connected is being reprovisioned from another fabric, ensure that the config on that device has been factory reset
Step 4 If above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F0467][configuration-failed][minor][DN of affected MO] Configuration failedConfiguration failed for [epgPKey] node [id] [pathName] on FEX [extChId] due to [configQual]Configuration failed for [epgPKey] node [id] [pathName] due to [configQual]Configuration failed for node [id] [targetDn] due to [configQual]Configuration failed for [tDn] due to [configQual]Configuration failed for node [id] due to [configQual]Configuration failed for [epgPKey] due to [configQual]Configuration failed for [epgDn] due to [configQual]
This fault occurs when an End Point Group is incompletely or incorrectly configured.
If you see this fault, take the following actions:
Step 1 Look at the configuration for issues
Step 2 For bd-not-present, this could be a temporary issue when the bridge domain has not yet been deployed to the node. If the EPG is associated with the default bridge domain, check the Connectivity Instrumentation Policy
Step 3 For context-not-present, this could be a temporary issue while the VRF has not yet been deployed to the node. If the EPG is associated with the default VRF, check the Connectivity Instrumentation Policy under Networking / Protocol Policies in common tenant
Step 4 For vlan-capacity, check that the number of configured EPGs and bridge domains deployed on a node do not exceed the supported number
Step 5 For vxlan-capacity, check that the number of configured EPGs, bridge domains and VRFs deployed on a node do not exceed the supported number
Step 6 For invalid-path, check that the configured path exists and is valid. Following issues are possible: The path (i.e. port/port-channel/Attachable-Profile/Loose-Node) getting referred does not exist on the node. The domain associated with the EPG is not allowed to use the specified path. Check the Attachable Profile configuration associated with the domain. The path (i.e. port/port-channel/Attachable-Profile/Loose-Node) is deployed on FEX and is part of l2Out/l3Out. l2Out and l3Out are NOT supported on FEX
Step 7 For port-part-of-port-channel, the configured interface is already configured as a port channel member
Step 8 For port-configured-as-l3, the configured interface is already configured as L3
Step 9 For port-configured-as-l2, the configured interface is referring to an interface that is already configured as L2
Step 10 For port-configured-for-fex, the configured interface is already configured for attaching to a FEX
Step 11 For port-configured-for-apic, the configured interface is connected to a controller
Step 12 For port-channel-capacity, check that the number of configured port channels deployed on a node do not exceed the supported number
Step 13 For native-or-untagged-encap-failure, multiple encaps are configured as native or untagged on the same path. Check the configured mode type
Step 14 For multiple-external-encap, a bridge domain can be extended outside the fabric using only one external encap per node
Step 15 For multiple-ctx-configuration, an L3 interface can belong to only 1 VRF at a time
Step 16 For encap-already-in-use, another EPG is already configured using this encap
Step 17 For invalid-vlan, this EPG?™s encap is not valid for the domain on which the EPG is configured
Step 18 For path-wiring-issues, the configured interface has wiring issues
Step 19 For further details, refer to the documentation for fv:NwIssues
Step 20 Verify the End Point Group configuration is correct and complete
Step 21 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F0468][configuration-failed][minor][DN of affected MO] Ctx Configuration failedCtx Configuration failed for [ctxDn] due to [configQual]
This fault occurs when an A given Ctx configured to use a DNS Profile which doesn?™t configured In Fabric. Only DNS Profiles configured for fabric can be used
If you see this fault, take the following actions:
Step 1 For dns-policy-not-present issue: Check the Configuration and make sure that DNS Profile consumed by Ctx is defined in fabric
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 [F0469][configuration-failed][minor][DN of affected MO] BD Configuration failedBD Configuration failed for [bdDn] due to [configQual]
This fault occurs when there is one or more duplicate Subnets defined for BDs or/and AEpGs associated with the Ctx.
If you see this fault, take the following actions:
Step 1 For duplicate-subnets-within-ctx issue: Find the Ctx that this BD is associated with and find all other BDs associated with the Ctx, Find all the AEpGs associated with BDs found in previous step, Verify that there is no single subnets configured for AEpGs and BDs associated with Ctx.
Step 2 For dhcp-policy-not-present issue: Check the Configuration and make sure that DHCP Pelay Profile consumed by BD is defined in Tenant.
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 [F0471][equipment-asic-failed][major][DN of affected MO] ASIC failed on slot SLOT:[id] (Serial number [ser]).
This fault occurs when an ASIC on a card sees a fatal failure during runtime
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-2-SYSTEM_MSG [F0474][interface-tunnel-down][major][DN of affected MO] Hardware programming for tunnel interface failed.
This fault occurs when tunnel manager fails to create a tunnel due to hardware failure.
To correct this fault, please attempt to create the tunnel again.
%LOG_LOCAL0-2-SYSTEM_MSG [F0475][interface-tunnel-down][major][DN of affected MO] Tunnel destination is not reachable.
This fault occurs when destination becomes unreachable.
To correct this fault, please ensure that the destination is reachable.
%LOG_LOCAL0-2-SYSTEM_MSG [F0482][interface-tunnel-down][major][DN of affected MO] Tunnel destination IP address is not resolved.
This fault occurs when destination IP address is unresolved.
To correct this fault, please ensure that the destination IP address is resolved./
%LOG_LOCAL0-2-SYSTEM_MSG [F0507][vpc-domain-down][major][DN of affected MO] vPC domain bringup failed, all fabric links down.
This fault occurs when vpc domain bringup fails due to all fabric links being down.
%LOG_LOCAL0-2-SYSTEM_MSG [F0508][vpc-domain-down][major][DN of affected MO] vPC domain bringup failed, no route to peer.
This fault occurs when vpc domain bringup fails because there is no route to peer.
%LOG_LOCAL0-2-SYSTEM_MSG [F0509][vpc-domain-down][major][DN of affected MO] vPC domain bringup failed, peer unreachable.
This fault occurs when vpc domain bringup fails due to peer being unreachable.
%LOG_LOCAL0-2-SYSTEM_MSG [F0510][vpc-domain-down][major][DN of affected MO] vPC domain bringup failed, domain compat failed.
This fault occurs when vpc domain bringup fails due to domain compatibility failure.
Please verify domain configuration and hardware compatibility of both the peers.
%LOG_LOCAL0-2-SYSTEM_MSG [F0511][vpc-domain-down][major][DN of affected MO] vPC domain bringup failed, error in election.
This fault occurs when vpc domain bringup fails due to election error.
Please make sure that domain configuration is consistent with the peer.
%LOG_LOCAL0-2-SYSTEM_MSG [F0512][vpc-domain-down][major][DN of affected MO] vPC domain bringup failed, keepalive not operational.
This fault occurs when vpc domain bringup fails due to keepalive being inoperational.
%LOG_LOCAL0-2-SYSTEM_MSG [F0513][vpc-domain-down][major][DN of affected MO] Global configuration is not consistent with peer ([compatQualStr]).
This fault occurs when global configuration on the peers is not consistent.
Please make sure that global configuration is consistent with the peer.
%LOG_LOCAL0-2-SYSTEM_MSG [F0518][interface-vpc-down][major][DN of affected MO] VPC [name] configuration is not consistent with peer ([compatQualStr]).
This fault occurs when vPC configuration on the peers is not consistent.
Please make sure that the vPC configuration is consistent with the peer.
%LOG_LOCAL0-1-SYSTEM_MSG [F0520][vpc-domain-down][critical][DN of affected MO] Peer keep-alive send has failed.
%LOG_LOCAL0-1-SYSTEM_MSG [F0522][vpc-domain-down][critical][DN of affected MO] Peer keep-alive receive has failed.
%LOG_LOCAL0-3-SYSTEM_MSG [F0523][configuration-failed][minor][DN of affected MO] Configuration failed for EPG [name] due to [configIssues]Configuration failed for [name], [name] [name] [name] due to [configIssues]Configuration failed for [name], [name] [name] [name] due to [configIssues]Configuration failed for [name], [name] [name] [name] due to [configIssues]Configuration failed for [name], [name] [name] [name] due to [configIssues]Configuration failed for [name], [name] [name] [name] due to [configIssues]
This fault occurs when an End Point Group is incompletely or incorrectly configured.
If you see this fault, take the following actions:
Step 1 Look at the configuration for issues
Step 2 Verify the End Point Group configuration is correct and complete
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 [F0524][configuration-failed][minor][DN of affected MO] For [name], application profile [name], application EPG [name], configuration failed for static end-point [name] due to missing path
This fault occurs when Static Endpoing is incompletely configured.
If you see this fault, take the following actions:
Step 1 Specify on which path the static endpoint is present
Step 2 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-1-SYSTEM_MSG [F0532][interface-physical-down][critical][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 infra and epg
If you see this fault, take the following actions
Step 1 Check the port connectivity
Step 2 Remove the configuration or 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-2-SYSTEM_MSG [F0543][interface-physical-down][major][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 infra and no epg
If you see this fault, take the following actions
Step 1 Check the port connectivity
Step 2 Remove the configuration or 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 [F0546][interface-physical-down][warning][DN of affected MO] Port is down, reason:[operStQual]([operErrDisQual]), used by:[usage]
This fault occurs when a port is down and is not in use for infra
If you see this fault, take the following actions
Step 1 Check the port connectivity
Step 2 Remove the configuration or 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-3-SYSTEM_MSG [F0564][configuration-failed][minor][DN of affected MO] Controller profile [hostOrIp] with name [name] in datacenter [rootContName] in domain [name] configuration failed due to [configIssues]
This fault is raised when the VMM Controller cannot be deployed due to a missing or invalid configuration.
If you see this fault, take the following actions:
Step 1 Verify that the policy for the VMM Controller is complete.
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 [F0565][deployment-failed][major][DN of affected MO] Deployment of EPG [faultDKey] failed on domain [name] due to [deployIssues]
This fault is raised when the Endpoint Group cannot be deployed due to a missing or invalid configuration.
If you see this fault, take the following actions:
Step 1 Verify that a VLAN pool is associated to the VMM Domain.
Step 2 If a Port Encap value is specified in the Endpoint Group-to-VMM association, verify that this value is a VLAN encap and it is part of an encapsulation block with static allocation mode in the VLAN pool. VXLAN Port Encap is not supported.
Step 3 Disable EPG isolation if the EPG is associated with a VMware Domain in AVS mode, or a Microsoft(SCVMM) Domain.
Step 4 Review the fault message and add missing or remove invalid configuration.
Step 5 If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-2-SYSTEM_MSG [F0600][interface-pcmbr-down][major][DN of affected MO] Port is suspended.
This fault occurs when port has been suspended by LACP.
Please verify the configuration on both ends of the port-channel.
%LOG_LOCAL0-3-SYSTEM_MSG [F0603][interface-pcmbr-down][minor][DN of affected MO] Port is operationally individual.
This fault occurs when port becomes operationally individual.
Please verify the configuration on both ends of the port-channel.
%LOG_LOCAL0-3-SYSTEM_MSG [F0618][configuration-failed][minor][DN of affected MO] Management address is not allocated to node [id]Out-of-band management address is not allocated to node [id]In-band management address is not allocated to node [id]
This fault occurs when a management node address is not allocated to a node.
If you see this fault, take the following actions:
Step 1 Create a node management address policy for the node.
Step 2 Ensure that there are no other faults related to the node management address policy.
Step 3 If above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F0650][missing-ip-addr][warning][DN of affected MO] IP Address Missing for Source Endpoint with MAC [tDn] in Endpoint Group [tDn] in Application [tDn] in Tenant [tDn]
This fault occurs when the source Endpoint IP address that the traceroute policy is configured to run with is not found in the fabric.
If you see this fault, take the following actions:
Step 1 Verify that the configured source Endpoint IP address in the Traceroute Policy exists in the fabric 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-4-SYSTEM_MSG [F0657][missing-ip-addr][warning][DN of affected MO] IP Address Missing for Destination Endpoint with MAC [tDn] in Endpoint Group [tDn] in Application [tDn] in Tenant [tDn]
This fault occurs when the destination Endpoint IP address that the traceroute policy is configured to run with is not found in the fabric.
If you see this fault, take the following actions:
Step 1 Verify that the configured destination Endpoint IP address in the Traceroute Policy exists in the fabric 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-3-SYSTEM_MSG [F0699][configuration-failed][minor][DN of affected MO] Policies from switch interface policy group [accGrpDn] failed to be deployed on node [id]. Reason: [deplSt]
: All policies associated with the configured Fex/Port Policy Group should get deployed to all nodes associated with the configured Fex/Port Selector Profiles for the Node Profile. A Fault has been raised because the associated policies have not been deployed to the configured node.
: If you see this fault take the following actions: - Verify that configured node is ready to receive policies - Verify that configured node is capable of handling the associated access Fex/Port level policies - If the listed recommendations do not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F0701][configuration-failed][minor][DN of affected MO] Deployment of Domain [name] failed due to [configIssues]
Infra Policy fault is raised when the configured Domain 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 to identify configuration issue.
Step 2 Modify configuration to add any missing parameters.
Step 3 Modify configuration to remove any invalid configuration parameters.
Step 4 If the listed recommendations do not resolve the issue, collect tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F0721][configuration-failure][minor][DN of affected MO] VLAN/VxLAN/NVGRE pool [name] deployment failed due to: [configIssues].
This fault is raised when a VLAN/VxLAN/NVGRE 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-4-SYSTEM_MSG [F0749][configuration-failed][warning][DN of affected MO] Failed to configure the vPC policy for the vPC pair [id] and a virtual IP address of [virtualIp] because: [configQual]
This fault occurs when a virtual Port Channel (vPC) policy is created but it has not been deployed yet (for example in a pre-provisioning scenario) and at least one of the following are conditions true:
Step 1 At least one of the fabric nodes that is part of the vPC is not ready
Step 2 The IP address for at least one of the fabric nodes is unknown
Step 3 One of the fabric nodes that is part of the vPC pair is already paired with another node (each node can only be part of one vPC pair)
Step 4 One of the fabric nodes is not a leaf (vPC pairs can only be formed between two leafs)
Step 5 The Virtual Ip address has been not allocated yet
Step 6 The Logical Pair Id has not been allocated yet
Step 7 Nodes are not in same POD
If you see this fault, take the following actions:
Step 1 Verify that corresponding fabric nodes are ready
Step 2 Verify that corresponding fabric nodes are ready
Step 3 Verify that corresponding fabric nodes are leaf
Step 4 Verify that the fabric node is not already part of another protection group
Step 5 In case of fabricExplicitGEp, verify that the pair id is set
Step 6 If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-3-SYSTEM_MSG [F0750][oper-state-change][minor][DN of affected MO] The vPC policy for the vPC pair [id] and a virtual IP address of [virtualIp] has changed state because: [configQual]
This fault is occurs when a vPC policy has been deployed to a fabric node, then at least one of the following conditions is true:
Step 1 One of the fabric nodes that is part of the vPC is not ready
Step 2 The fabric node ip address is not known
Step 3 One of the fabric nodes is not a leaf (vPC pairs can only be formed between two leafs)
If you see this fault, take the following actions:
Step 1 Verify that corresponding fabric nodes are ready
Step 2 Verify that corresponding fabric nodes are leafs
Step 3 Verify that the fabric node is not already part of another protection group
Step 4 If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-1-SYSTEM_MSG [F0751][oper-state-fail][critical][DN of affected MO] The vPC policy for the vPC pair [id] and a virtual IP of [virtualIp] has a state of [configSt] because: [configQual]
This fault occurs when a virtual Port Channel (vPC) policy is no longer deployed because both of the member fabric nodes that are part of the vPC pair are not ready to receive policies
If you see this fault, take the following actions:
Step 1 Verify that corresponding fabric nodes are ready to receive policies
Step 2 Verify that corresponding fabric nodes are leafs
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 [F0756][resolution-failed][minor][DN of affected MO] Could not resolve the target [tRn] to form a named relationship. Using a default target [tDn] instead
This fault occurs when a configured target of a named relationship cannot be resolved.
If you see this fault, take the following actions:
Step 1 Verify that the configuration for the named target is correct and complete, and that it exists
Step 2 Verify the configuration for the specific relationship is correct and complete.
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 [F0757][configuration-failed][minor][DN of affected MO] Service graph template [name] for tenant [name] configuration is invalid.
This fault occurs due to an invalid service graph configuration.
If you see this fault, please modify service graph configuration to fix validation errors.
%LOG_LOCAL0-3-SYSTEM_MSG [F0758][graph-rendering-failed][minor][DN of affected MO] Service graph [name] for tenant [name] could not be instantiated. Info: [configInfo]
This fault occurs when a service graph could not be instantiated.
If you see this fault, take the following actions:
Step 1 Look at the graph configuration for issues
Step 2 For missing-lif, check for fault on LDev or check LDev specified in LDevCtx
Step 3 For function-type-mismatch-failure, check for valid MFunc in the MDev for selected LDev
Step 4 For missing-ldev-ctx, check if LDevCtx is defined under tenant, or check if LDev associated with LDevCtx has proper MDev specified.
Step 5 For missing-lif, check that matching LIF for func connector exists
Step 6 For invalid-filter-referred-by-rsconntoflt, check AbsFuncConn to filter relation is formed
Step 7 For missing-l3ctx, check that RsConnToCtxTerm points to valid tDn
Step 8 For param-cardinality-error, check that configuration parameter has valid cardinality, Graph param/rel can only have at most one instance
Step 9 For invalid-abstract-graph-config-param, check that all abstract graph configurations are valid
Step 10 For param-validation-failed, check that all specified params are valid
Step 11 For invalid-param-scope, check that RsScopeToTerm is configured and is pointing to valid terminal or terminal node. Or check that there is no missing default RsScopeToTerm in AbsConfig
Step 12 For invalid-conn-for-configparam, check that RsCfgToConn is configured in AbsConn and is pointing to a valid connector
Step 13 For invalid-rsmconnatt, check for valid RsMConn in AbsConn
Step 14 For missing-mandatory-param, check that all mandatory graph params and graph relations exist
Step 15 For invalid-relation-target, fix the incorrect service folder/param name
%LOG_LOCAL0-3-SYSTEM_MSG [F0759][graph-rendering-failure][minor][DN of affected MO] Service graph [name] for tenant [name] could not be instantiated. Function node [name] configuration is invalid.
This fault occurs when a service graph could not be instantiated.
If you see this fault, please modify graph configuration to resolve cause of fault.
%LOG_LOCAL0-3-SYSTEM_MSG [F0760][graph-rendering-failure][minor][DN of affected MO] Service graph [name] for tenant [name] could not be instantiated. Terminal Node [name] configuration is invalid.
This fault occurs when a service graph could not be instantiated.
If you see this fault, please modify graph configuration to resolve cause of fault.
%LOG_LOCAL0-3-SYSTEM_MSG [F0761][configuration-failed][minor][DN of affected MO] Service graph for tenant [name] could not be instantiated. Configuration param [name] configuration is invalid.Service graph [graphDn] for tenant [name] could not be instantiated. Configuration param [name] for function node [name] configuration is invalid.Service graph [name] for tenant [name] could not be instantiated. Configuration param [name] for function node [name] configuration is invalid.
This fault occurs when a cfg parameter has an error..
If you see this fault, please modify your configuration to provide all needed parameters and folders.
%LOG_LOCAL0-3-SYSTEM_MSG [F0762][configuration-failed][minor][DN of affected MO] Configuration folder [name], which is in tenant [name] could not be processed.Service graph template [name] for tenant [name] could not be processed. Configuration folder [name] for function [name] configuration is invalid.Abstract function profile [name] for tenant [name] could not be processed. Configuration folder [name] for shared configuration of logical devices is invalid.
This fault occurs when a cfg parameter has an error..
If you see this fault, please modify your configuration to update service graph config parameters and folders.
%LOG_LOCAL0-3-SYSTEM_MSG [F0763][configuration-failed][minor][DN of affected MO] Configuration parameter [name], which is in tenant [name] could not be processed.Service graph template [name] for tenant [name] could not be processed. Configuration param [name] for function [name] configuration is invalid.Abstract function profile [name] for tenant [name] could not be processed. Configuration param [name] for shared configuration of logical devices is invalid.
This fault occurs when a cfg parameter has an error..
If you see this fault, please modify your configuration to update service graph config parameters and folders.
%LOG_LOCAL0-3-SYSTEM_MSG [F0764][configuration-failed][minor][DN of affected MO] L4-L7 Devices configuration [name] for tenant [name] is invalid.
This fault occurs when a logical device is being configured in a way which is not compatible with the meta device information supplied by the device package.
If you see this fault, please modify LDev configuration to resolve cause of fault.
%LOG_LOCAL0-3-SYSTEM_MSG [F0765][configuration-failed][minor][DN of affected MO] Concrete device [name] in L4-L7 devices [name] for tenant [name] configuration is invalid.
This fault occurs when a user provided Concrete device configuration is invalid. The config issues indicate the exact reason for the error.
If you see this fault, please modify CDev configuration to resolve cause of fault.
%LOG_LOCAL0-3-SYSTEM_MSG [F0766][configuration-failed][minor][DN of affected MO] Configuration folder [name], which is in tenant [name] could not be instantiated.Service graph [name] for tenant [name] could not be instantiated. Configuration folder [name] for function [name] has an error.Service graph template [name] for tenant [name] could not be instantiated. Configuration folder [name] for function [name] has an error.
This fault occurs when a config folder has an error. The config issues indicate the exact reason for the error.
If you see this fault, please modify configuration of the folder to resolve the cause of fault.
%LOG_LOCAL0-3-SYSTEM_MSG [F0768][configuration-failed][minor][DN of affected MO] Configuration relation [name], which is in tenant [name] has an error.Service graph [name] for tenant [name] could not be instantiated. Configuration relation [name] for function [name] has an error.Service graph template [name] for tenant [name] could not be instantiated. Configuration relation [name] for function [name] has an error.
This fault occurs when a config GRel has an an error. The config issues indicate the exact reason for the error.
If you see this fault, please modify configuration of the GRel to resolve the cause of fault.
%LOG_LOCAL0-3-SYSTEM_MSG [F0769][configuration-failed][minor][DN of affected MO] Service graph [name] for tenant [name] could not be instantiated. Function connector instance [name] for function node [name] configuration is invalid.
This fault occurs when a Function Connector (FuncConnInst) 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-3-SYSTEM_MSG [F0770][configuration-failed][minor][DN of affected MO] Service graph [name] for tenant [name] could not be instantiated. Terminal node connector instance [name] for terminal node [name] configuration is invalid.
This fault occurs when a Terminal Connector (TermConnInst) 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-3-SYSTEM_MSG [F0771][configuration-failed][minor][DN of affected MO] Service graph [name] for tenant [name] could not be instantiated. Connection instance [name] configuration is invalid.
This fault occurs when a Connection Inst (ConnectionInst) has an error.The config issues the exact reason for the error.
If you see this fault, please modify your configuration to resolve the cause of fault.
%LOG_LOCAL0-3-SYSTEM_MSG [F0772][configuration-failed][minor][DN of affected MO] LIf configuration [name] for L4-L7 Devices [name] for tenant [name] is invalid.
This fault occurs when a Logical Interface configuration is invalid.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-1-SYSTEM_MSG [F0843][test-failure][critical][DN of affected MO] Abstract Class ATestObj fault, name=[name], descr=[descr], pUint64=[propUint64], propBmp8=[propBmp8], propBmp64=[propBmp64] propEnum16=[propEnum16].
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 [F0844][test-failure][minor][DN of affected MO] Concrete Class TLTestObj fault, name=[name], descr=[descr], pUint32=[propUint32], pUByte=[propUByte], propBmp8=[propBmp8], propBmp64=[propBmp64] [name].
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 [F0845][test-failure][major][DN of affected MO] Concrete Class CTestObj () fault, name=[name], descr=[descr], pUint32=[propUint32], pUByte=[propUByte], propBmp8=[propBmp8], [propBmp64], [propBmp64] [propBmp64] [name]
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 [F0846][test-failure][critical][DN of affected MO] Abstract Class ATestObj fault, name=[name], descr=[descr], pUint64=[propUint64].
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 [F0847][test-failure][minor][DN of affected MO] Concrete Class TLTestObj fault, name=[name], descr=[descr], pUint32=[propUint32], pUByte=[propUByte], propBmp8=[propBmp8], propBmp64=[propBmp64] [name] [address].
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 [F0848][test-failure][major][DN of affected MO] Concrete Class CTestObj () fault, name=[name], descr=[descr], pUint32=[propUint32], pUByte=[propUByte], propBmp8=[propBmp8], [propBmp64], [propBmp64] [propBmp64] [name] [address]
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 [F0849][configuration-failed][minor][DN of affected MO] Configuration failed due to [configQual] for node [name]Configuration failed due to [configQual] for [dn] for node [name]
This fault occurs when a infra selector (port selector, card selector, node selector etc.) is incorrectly configured.
If you see this fault, take the following actions:
Step 1 Look at the configuration for issues
Step 2 For invalid-port, check the infra port selector, it should have only leaf host ports or fex host ports. Fabric ports are not allowed to be configured using infra port selector.
Step 3 For port-configured-for-apic, check the infra port selector and the associated policies. Port connected to the controller can be configured for limited policies. Its allowed to be associated with only infra::AccPortGrp.
Step 4 For invalid-card, check the infra card selector, its referring to a card which does not exist. Fault will clear once the card is added to the node.
Step 5 For further details, refer to the documentation for fabric:SelectorIssues
Step 6 Verify the infra selector configuration is correct and complete
Step 7 If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.
%LOG_LOCAL0-4-SYSTEM_MSG [F0853][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 [F0854][resolution-failed][warning][DN of affected MO] Failed to form relation to MO [tRn] of class [tCl] in context [tContextDn]
This fault is raised when the inventory policy refers to a scheduler that does not exist.
Check that the name of the scheduler is spelled correctly or create it if it doesn?™t exist.
%LOG_LOCAL0-4-SYSTEM_MSG [F0855][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 [F0856][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 [F0857][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 [F0859][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 [F0860][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 [F0861][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 [F0862][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 [F0864][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 [F0865][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 [F0866][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 [F0867][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 [F0868][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 [F0869][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 [F0870][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 [F0871][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 [F0872][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 [F0873][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 [F0874][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 [F0875][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 [F0876][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 [F0878][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 [F0879][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 [F0880][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 [F0881][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 [F0882][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 [F0883][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 [F0885][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 [F0886][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 [F0887][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 [F0888][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 [F0889][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 [F0897][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 [F0898][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 [F0899][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 [F0900][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 [F0901][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 [F0902][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 [F0903][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 [F0904][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 [F0905][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 [F0906][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 [F0907][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 [F0909][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 [F0913][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 [F0916][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 [F0917][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 [F0918][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 [F0919][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 [F0920][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 [F0921][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 [F0922][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 [F0923][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 [F0924][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 [F0925][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 [F0926][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 [F0927][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 [F0940][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 [F0943][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 [F0944][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 [F0945][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 [F0946][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 [F0947][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 [F0948][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 [F0949][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 [F0950][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 [F0951][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 [F0952][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 [F0953][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 [F0954][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 [F0955][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 [F0956][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 [F0957][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 [F0959][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 [F0960][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 [F0963][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 [F0964][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 [F0965][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 [F0966][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 [F0967][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 [F0970][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 [F0971][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 [F0973][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 [F0974][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 [F0976][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 [F0977][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 [F0978][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 [F0979][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 [F0981][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 [F0982][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 [F0983][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 [F0984][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 [F0988][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 [F0989][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 [F0990][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 [F0991][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 [F0992][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 [F0993][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 [F0994][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 [F0995][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 [F0996][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 [F0997][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 [F0998][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 [F0999][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 [F1003][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 [F1004][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 [F1005][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 [F1006][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 [F1007][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 [F1008][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 [F1009][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 [F1010][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 [F1011][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 [F1012][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 [F1013][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 [F1014][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 [F1015][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 [F1016][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 [F1017][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 [F1018][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 [F1019][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 [F1020][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 [F1021][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 [F1023][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 [F1024][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 [F1025][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 [F1026][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 [F1027][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 [F1028][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 [F1029][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 [F1030][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 [F1031][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 [F1032][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 [F1033][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 [F1034][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 [F1037][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 [F1038][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 [F1040][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 [F1041][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 [F1048][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 [F1049][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 [F1053][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 [F1054][resolution-failed][minor][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 [F1055][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 [F1056][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 [F1058][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 [F1059][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 [F1060][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 [F1062][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 [F1063][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 [F1064][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 [F1065][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 [F1066][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 [F1067][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 [F1068][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 [F1069][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 [F1070][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 [F1071][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 [F1073][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 [F1074][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 [F1075][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 [F1076][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 [F1077][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 [F1079][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 [F1080][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 [F1081][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 [F1082][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 [F1083][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 [F1084][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 [F1085][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 [F1086][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 [F1087][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 [F1088][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 [F1089][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 [F1090][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 [F1091][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 [F1092][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 [F1094][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 [F1095][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 [F1096][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 [F1097][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 [F1098][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 [F1099][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 [F1100][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 [F1101][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 [F1102][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 [F1103][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 [F1104][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 [F1105][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 [F1106][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 [F1107][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 [F1110][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 [F1111][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 [F1112][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 [F1115][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 [F1117][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.