ACI F0x Messages

ACI F0* Commands

F0020: fltFabricSelectorIssuesConfig-failed

Severity: minor

Explanation: This fault occurs when a fabric selector (port selector, card selector, node selector etc.) is incorrectly configured.

Recommended Action: If you see this fault, take the following actions:
  1. Look at the configuration for issues
  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.
  3. For port-configured-for-apic, check the fabric port selector. Port connected to the controller cannot be configured using fabric port selector.
  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.
  5. For further details, refer to the documentation for fabric:SelectorIssues
  6. Verify the fabric selector configuration is correct and complete
  7. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0021: fltAaaRadiusProviderRadiusProvider_Inoperable

Severity: minor

Explanation: This fault occurs when the Radius Provider is not operational.

Recommended Action: If you see this fault, take the following actions:
  1. Verify the IP address and path to the Radius provider are still active and functioning.
  2. Ensure the configuration on the Radius provider has not changed.
  3. Verify that the Radius provider is still functioning properly
  4. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0022: fltAaaLdapProviderLdapProvider_Inoperable

Severity: minor

Explanation: This fault occurs when the LDAP provider is not operational.

Recommended Action: If you see this fault, take the following actions:
  1. Verify the IP address and path to the LDAP provider are still active and functioning.
  2. Ensure the configuration on the LDAP provider has not changed.
  3. Verify that the LDAP provider is still functioning properly
  4. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0023: fltAaaTacacsPlusProviderTacacsPlusProvider_Inoperable

Severity: minor

Explanation: This fault occurs when the TACACS+ provider is not operational.

Recommended Action: If you see this fault, take the following actions:
  1. Verify the IP address and path to the TACACS+ provider are still active and functioning.
  2. Ensure the configuration on the TACACS+ provider has not changed.
  3. Verify that the TACACS+ provider is still functioning properly
  4. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0048: fltStatsAExportJobIfc-export-failed

Severity: minor

Explanation: This fault occurs due to a Stats Export Policy session failure.

Recommended Action: If you see this fault, please check the Stats Export Policy configuration parameters and health of the destination export server.

F0051: fltDbgOdAggRsltTenantAtomicCounterExcessiveDrops

Severity: major

Explanation: This fault occurs when a significant number of packet drops are detected by a configured and enabled Atomic Counter

Recommended Action: If you see this fault, take the following actions:
  1. Check the network configuration in the packet path where this Atomic Counter policy is configured.
  2. Check for any CRC, etc errors in the packet path where this Atomic Counter policy is configured.
  3. Check interface counters and rates in the packet path where this Atomic Counter policy is configured to make sure there is no oversubscription.
  4. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0052: fltDbgOdAggRsltTenantAtomicCounterExcessPackets

Severity: major

Explanation: This fault occurs when a significant number of excess packets are detected by a configured and enabled Atomic Counter

Recommended Action: If you see this fault, take the following actions:
  1. Check the network configuration in the packet path where this Atomic Counter policy is configured.
  2. Check interface counters and rates in the packet path where this Atomic Counter policy is configured to make sure there is no oversubscription.
  3. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0053: fltConfigJobConfigBackupFailed

Severity: minor

Explanation: This fault occurs when a configuration export/import job fails.

Recommended Action: If you see this fault, take the following actions:
  1. Verify that the Controllers can reach the remote destination without issues and that the remote file is correct
  2. Verify that the remote destination is healthy.
  3. To clear this fault, you can acknowledge the job. In GUI:
    1. Navigate to the Operational tab of the config policy
    2. Select the failed job, and choose Delete from the Actions menu
  4. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0058: fltFirmwareDownloadDownloadFailed

Severity: major

Explanation: This fault occurs when a firmware download fails

Recommended Action: If you see this fault, take the following actions:
  1. Verify the location where the firmware stored is reachable through scp/http request
  2. Verify the directory and file location exist
  3. Verify the source name has valid characters [a-z], [A-Z], [0-9], underscore(_), dash(-), period(.)
  4. Verify the firmware file is valid
  5. Verify the file has sufficient permissions
  6. Free-up firmware repo by deleting any stale/old images.
  7. Verify username/password authentication
  8. Enclose the ip address within square brackets if specifying a v6 address. Otherwise, it will be considered as a hostname.
  9. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0080: fltDhcpProviderAddressAssignmentFailed

Severity: major

Explanation: This fault is raised when the DHCP server runs out of IP address to allocate to clients

Recommended Action: If you see this fault, take the following actions:
  1. Decommission if there are any unused switches in the fabric.
  2. If the above actions did not resolve the issue, collect a tech-support file and contact Cisco TAC.

F0098: fltStatsAExportJobSw-export-failed

Severity: minor

Explanation: This fault occurs due to a Stats Export Policy session failure.

Recommended Action: If you see this fault, please check the Stats Export Policy configuration parameters and health of the destination export server.

F0101: fltEqptStorageFailed

Severity: major

Explanation: This fault occurs when a storage device fails on a controller

Recommended Action: If you see this fault, take the following actions:
  1. Create a tech-support file and contact Cisco TAC.

F0103: fltCnwPhysIfDown

Severity: major

Explanation: This fault occurs when a physical interface on a controller is in the link-down state.

Recommended Action: If you see this fault, take the following actions:
  1. Verify that the physical port is properly connected to the peer device.
  2. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0104: fltCnwAggrIfDown

Severity: critical

Explanation: This fault occurs when a bond interface on a controller is in the link-down state.

Recommended Action: If you see this fault, take the following actions:
  1. Verify that the physical ports that make up the bond are properly connected to the peer devices.
  2. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0105: fltMaintUpgJobUpgradeFailed

Severity: major

Explanation: This fault occurs when a software upgrade fails on a controller

Recommended Action: If you see this fault, take the following actions:
  1. Make sure that the /firmware directory is not filled more than 75% before re-triggering the upgrade.
  2. Verify that the NTP providers with which the APIC is synchronized is correctly configured and is reachable.
  3. If Authentication using authkey is configured in NTP Server Check if all the keys given to APIC are correct. If not, redo the entire process starting with the NTP Provider.
  4. If Authentication using authkey is configured in NTP Server Check if the client password given to APIC is correct. The client password is used when generating the IFF group keys. If not, redo the entire process starting with the NTP Provider.
  5. Verify whether NTP daemon is running in the NTP Provider with which authentication has been established.
  6. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0106: fltCnwPhysIfPortOutofService

Severity: critical

Explanation: This fault occurs when a port is out-of-service because of a wiring error.

Recommended Action: If you see this fault, take the following actions:
  1. Ensure the device connected to the port is the correct device.
  2. Ensure the device connected to the port is configured properly for the fabric it is being connected to.
  3. If the device being connected is being reprovisioned from another fabric, ensure that the config on that device has been factory reset
  4. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0111: fltFabricLooseNodeOperIssues

Severity: major

Explanation: This fault occurs when operational issues are detected on a LooseNode (Unmanaged switch)

Recommended Action: If you see this fault, take the following action:
  1. Check and reestablish LooseNode connectivity to Leaf Node
  2. If the above action did not resolve the issue, create a show tech-support file and contact Cisco TAC.

F0130: fltCompCtrlrConnectFailed

Severity: major

Explanation: This fault is raised when the VMM Controller is marked offline. Recovery is in process.

Recommended Action: If you see this fault repeatedly, take the following actions:
  1. Verify that there is network connectivity to VMM Controller.
  2. Verify that the user credentials to VMM Controller are correct.
  3. If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.

F0132: fltCompCtrlrOperationalIssues

Severity: major

Explanation: This fault is raised when Remote or External disruptive operations on VMM Controller are detected.

Recommended Action: If you see this fault, take the following actions:
  1. Ensure all vCenter hosts are in connected state and online
  2. Ensure at least one VM exists within the vCenter Inventory
  3. Ensure there are no VMs in an 'Unreachable' state
  4. Manually retrigger a VMM inventory sync by going to the VM networking -> Inventory -> Expand 'VMware' -> Expand Domain -> Expand 'Controllers' -> Right click on the controller and select "Trigger Inventory Sync"
  5. If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.

F0133: fltCompCtrlrUnsupportedOperation

Severity: major

Explanation: This fault is raised when deployment of given configuration fails for a Controller.

Recommended Action: If you see this fault, take the following actions:
  1. Try to delete and add the policy again.
  2. If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.

F0134: fltHvsAdjConfigIssues

Severity: minor

Explanation: This fault is raised when LooseNode (Unmanaged switch) has config issues such as missing Management Address config.

Recommended Action: If you see this fault, take the following actions:
  1. Configure Management Address address on LooseNode and ensure that LLDP or CDP is enabled to advertise Management Address
  2. If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.

F0135: fltCompEpPDUnsupportedOperation

Severity: major

Explanation: This fault is raised when remote or external disruptive EPG operations are performed on the Controller.

Recommended Action: If you see this fault, take the following actions:
  1. Restore EPG to its original state on the Controller.
  2. Detach and reattach the EPG to the VMM domain, or update its encapsulation value.
  3. If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.

F0214: fltOpflexODevOperationalIssues

Severity: major

Explanation: This fault is raised when there is an issue with respect to the OpFlex device

Recommended Action: If you see this fault, take the following actions:
  1. Check the AEP configuration on the domain attached to this device. Make sure there are valid interfaces.
  2. Check for any issues with the Port Channel/ VPC.
  3. Check connectivity to the OpFlex device.
  4. To restore, delete and re-add the OpFlex device.
  5. Try restarting the device.
  6. If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.

F0256: fltCoopDomCoopDomInconsistentCfg

Severity: major

Explanation: This fault occurs when the coop domain has inconsistent configuration in the council

Recommended Action: To recover from this fault, try the following actions
  1. Look at any configuration issues
  2. Verify the configuration is correct/complete

F0299: fltBgpPeerEntryFailed

Severity: warning

Explanation: This fault occurs when the peer state is not established

Recommended Action: To recover from this fault, try the following actions
  1. Look at any configuration issues
  2. Verify the configuration is correct/complete
  3. Check network connectivity to the peer
  4. If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.

F0309: fltInfraReplicaReplicaState

Severity: critical

Explanation: This fault occurs when a controller reports some data for service failed to initialize.

Recommended Action: If you see this fault, take the following actions:
  1. Check cluster connectivity. All controllers need to be listed and reported as available. Check this by using the apic command show controller or by looking at System->Controller->First Controller->Cluster as Seen By Node
  2. Ensure that the cluster configuration is stable. Make note of any any frequent and brief interruptions of cluster availability or prolonged unavailability.
  3. If any controllers are missing from the cluster, check if those controllers are accessible via other means like ssh.
  4. Check for other faults related to cluster health and availability by looking at System->Faults Count By Domain->Infra
  5. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0310: fltInfraReplicaCommitLogState

Severity: major

Explanation: This fault occurs when a controller reports some data for a service has been corrupted.

Recommended Action: If you see this fault, take the following actions:
  1. Check for errors regarding the disks in the controller
  2. Check the error logs on the controller to see if there is any additional information.
  3. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0317: fltInfraReplicaDatabaseState

Severity: major

Explanation: This fault occurs when a controller reports data in the internal datastore for a given service has been corrupted.

Recommended Action: If you see this fault, take the following actions:
  1. Check for errors regarding the disks in the controller
  2. Check the error logs on the controller to see if there is any additional information.
  3. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0320: fltVnsAL4L7ServiceFaultServiceMinorFault

Severity: minor

Explanation: This fault occurs when the L4-L7 service returns a minor fault

Recommended Action: If you see this fault, please refer to L4-L7 device vendor documentation.

F0321: fltInfraWiNodeHealth

Severity: critical

Explanation: This fault occurs when a controller reports the distributed internal database (data layer) of the controller cluster is not fully functional.

Recommended Action: If you see this fault, take the following actions:
  1. Check cluster connectivity. All controllers need to be listed and reported as available.
  2. Ensure that the cluster configuration is stable. Make note of any frequent and brief interruptions of cluster availability or prolonged unavailability.
  3. If any controllers are missing from the cluster, check if those controllers are accessible via other means like ssh.
  4. Check for other faults related to cluster health and availability by looking at System->Faults Count By Domain->infra
  5. Check that all services are up and running on all controllers. You can look for faults with code F1419.
  6. Check for any process crashes and cores.
  7. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0323: fltInfraServiceHealth

Severity: critical

Explanation: 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.

Recommended Action: If you see this fault, take the following actions:
  1. Check cluster connectivity. All controllers need to be listed and reported as available. Use the apic command show controller or by looking at System->Controllers->First Controller ->Cluster as Seen By Node.
  2. Ensure that the cluster configuration is stable. Make note of any any frequent and brief interruptions of cluster availability or prolonged unavailability.
  3. Check that the service in question is running on all controllers using System->Controllers->First Controller->Process.
  4. Check for any process crashes and cores using System->Controllers APIC name->Troubleshooting.
  5. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0324: fltVnsAL4L7ServiceFaultServiceMajorFault

Severity: major

Explanation: This fault occurs when the L4-L7 service returns a major fault

Recommended Action: If you see this fault, please refer to L4-L7 device vendor documentation.

F0325: fltInfraLoNodeHealth

Severity: critical

Explanation: 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.

Recommended Action: If you see this fault, take the following actions:
  1. Check cluster connectivity. All controllers need to be listed and reported as available using the apic command show controller or by looking at System->Controller ->First Controller-> Cluster as Seen By Node.
  2. Ensure that the cluster configuration is stable. Make note of any any frequent and brief interruptions of cluster availability or prolonged unavailability.
  3. Check that the service in question is running on all controllers using System->Controlers->First Controller ->Process.
  4. Check for any process crashes and cores.
  5. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0329: fltVnsScriptRTInfoScriptRunTimeInfo

Severity: major

Explanation: This fault occurs when there is a failure in starting the service script

Recommended Action: If you see this fault, please contact L4-L7 device vendor.

F0330: fltVnsScriptRTInfoScriptFunctions

Severity: minor

Explanation: This fault occurs when there is missing function in device package

Recommended Action: If you see this fault, please contact L4-L7 device vendor for a more recent version of device package.

F0338: fltOspfInstInstMemAlertCritical

Severity: warning

Explanation: This fault occurs when the ospf instance memory alert is critical

Recommended Action: To recover from this fault, try the following actions
  1. Look at any configuration issues
  2. Verify the configuration is correct/complete
  3. Reduce the number of ospf enabled interfaces
  4. Reduce the number of routes into ospf
  5. If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.

F0341: fltDhcpClientIfIfOperStFailed

Severity: major

Explanation: This fault occurs when the operational state of the dhcp client interface changes to failed state

Recommended Action: To recover from this fault, try the following actions
  1. Check the network connectivity between APIC controller and the node
  2. Try rebooting the switch using CLI or GUI.
  3. If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.

F0344: fltIgmpsnoopInstIgmpSnoopLocalLearningDisabledFault

Severity: major

Explanation: This fault occurs when the igmp snooping local learning is disabled

Recommended Action: To recover from this fault, try the following actions
  1. Reduce the number of multicast groups in the network behind the leaf node
  2. If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.

F0345: fltIgmpsnoopInstIgmpSnoopFabricearningDisabledFault

Severity: major

Explanation: This fault occurs when the igmp snooping fabric learning is disabled

Recommended Action: To recover from this fault, try the following actions
  1. Reduce the number of multicast groups in the fabric
  2. If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.

F0350: fltLldpAdjEpAdjStMultipleNbrs

Severity: warning

Explanation: This fault occurs when multiple neighbors are discovered on the interface

Recommended Action: None set.

F0361: fltIsisFmcastTreeTreeLargeDia

Severity: warning

Explanation: This event occurs when the tree diameter of a Mcast tree is deemed large.

Recommended Action: None set.

F0377: fltIsisInstInstMemAlertCritical

Severity: warning

Explanation: This fault occurs when the isis instance memory alert is critical

Recommended Action: None set.

F0391: fltIsisIfInitError

Severity: major

Explanation: This fault usually occurs when ISIS interface specific initaliztion fails.

Recommended Action: If you see this fault, take the following actions:
  1. Try shutting down and restarting the ISIS instance.
  2. If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.

F0394: fltIsisIfLvlProtocolError

Severity: major

Explanation: This fault usually occurs when ISIS interface specific protocol handling fails.

Recommended Action: If you see this fault, take the following actions:
  1. Try shutting down and restarting the ISIS instance.
  2. If the above actions did not resolve the issue, generate the show tech-support file and contact Cisco TAC.

F0397: fltAaaRadiusProviderRadiusProviderInoperable

Severity: minor

Explanation: This fault occurs when the Radius Provider is not operational.

Recommended Action: If you see this fault, take the following actions:
  1. Verify the IP address and path to the Radius provider are still active and functioning.
  2. Ensure the configuration on the Radius provider has not changed.
  3. Verify that the Radius provider is still functioning properly
  4. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0398: fltAaaLdapProviderLdapProviderInoperable

Severity: minor

Explanation: This fault occurs when the LDAP provider is not operational.

Recommended Action: If you see this fault, take the following actions:
  1. Verify the IP address and path to the LDAP provider are still active and functioning.
  2. Ensure the configuration on the LDAP provider has not changed.
  3. Verify that the LDAP provider is still functioning properly
  4. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0400: fltAaaTacacsPlusProviderTacacsPlusProviderInoperable

Severity: minor

Explanation: This fault occurs when the TACACS+ provider is not operational.

Recommended Action: If you see this fault, take the following actions:
  1. Verify the IP address and path to the TACACS+ provider are still active and functioning.
  2. Ensure the configuration on the TACACS+ provider has not changed.
  3. Verify that the TACACS+ provider is still functioning properly
  4. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0401: fltEqptdiagSubjUnsupported

Severity: minor

Explanation: This fault occurs when a diagnostic test is not supported.

Recommended Action: None set.

F0402: fltEqptdiagSubjNotAccessible

Severity: minor

Explanation: This fault occurs when a diagnostic test subject is not accessible.

Recommended Action: None set.

F0403: fltEqptdiagOnDSubjUnsupported

Severity: minor

Explanation: This fault occurs when a on-demand diagnostic test is not supported.

Recommended Action: None set.

F0404: fltEqptdiagOnDSubjNotAccessible

Severity: minor

Explanation: This fault occurs when a on-demand diagnostic test subject is not accessible.

Recommended Action: None set.

F0411: fltEqptPsuFailed

Severity: minor

Explanation: This fault occurs when psu is failed

Recommended Action: To recover from this fault, try the following actions
  1. Replace the power supply unit
  2. If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC

F0412: fltEqptPsuFanFailed

Severity: minor

Explanation: This fault occurs when the fan in the psu is failed

Recommended Action: To recover from this fault, try the following actions
  1. Replace the power supply unit
  2. If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC

F0413: fltEqptPsuSlotPsuMissing

Severity: minor

Explanation: This fault occurs when the the psu is missing

Recommended Action: To recover from this fault, try the following actions
  1. Connect power supply unit
  2. If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC

F0415: fltEqptCardMismatchSlot

Severity: major

Explanation: This fault typically occurs when the SUP is inserted in the wrong slot

Recommended Action: To recover from this fault, try the following actions
  1. Insert the SUP in the correct slot
  2. If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC

F0416: fltEqptCardUnknownSwId

Severity: major

Explanation: This fault typically occurs when a card with an unknown card id is inserted in the chassis

Recommended Action: To recover from this fault, try the following actions
  1. Remove the card from the chassis
  2. Fix the software card index to one of the known types
  3. If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC

F0418: fltVzAnyConfigurationFailed

Severity: minor

Explanation: 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

Recommended Action: If you see this fault, take the following actions:
  1. Look at each Contract associated to the Private Network's 'EPG Collection for Context'
  2. Verify that all of these Contracts have a scope of "Context"
  3. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0440: fltEqptSpromSpromFailed

Severity: major

Explanation: This fault usually occurs if the backplane sprom is corrupted

Recommended Action: If you see this fault, take the following actions:
  1. Fix the sprom contents
  2. If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

F0441: fltEqptSpromBPBadIDPROM

Severity: major

Explanation: This fault would occur if the backplane IDPROM contents become invalid or corrupted

Recommended Action: If you see this fault, take the following actions:
  1. Create a show tech-support file and contact Cisco TAC.

F0449: fltEqptSensorFailed

Severity: major

Explanation: This fault usually occurs if sensor fails

Recommended Action: If you see this fault, take the following actions:
  1. replace the component that has failed
  2. If the above actions did not resolve the issue, create a show tech-support file and contact Cisco TAC.

F0454: fltLldpIfPortOutofService

Severity: major

Explanation: This fault occurs when a port is out-of-service because of a wiring error.

Recommended Action: If you see this fault, take the following actions:
  1. Ensure the device connected to the port is the correct device.
  2. Ensure the device connected to the port is configured properly for the fabric it is being connected to.
  3. If the device being connected is being reprovisioned from another fabric, ensure that the config on that device has been factory reset
  4. If above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0467: fltFvNwIssuesConfig-failed

Severity: minor

Explanation: This fault occurs when an End Point Group / End Point Security Group is incompletely or incorrectly configured.

Recommended Action: If you see this fault, take the following actions:
  1. Look at the configuration for issues
  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
  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
  4. For vlan-capacity, check that the number of configured EPGs and bridge domains deployed on a node do not exceed the supported number
  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
  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. L3Dom associated with the L3out does not exist. Configure a valid L3 Domain and associate it with the L3Out
  7. For port-part-of-port-channel, the configured interface is already configured as a port channel member
  8. For port-configured-as-l3, the configured interface is already configured as L3
  9. For port-configured-as-l2, the configured interface is referring to an interface that is already configured as L2
  10. For port-configured-for-fex, the configured interface is already configured for attaching to a FEX
  11. For port-configured-for-apic, the configured interface is connected to a controller
  12. For port-channel-capacity, check that the number of configured port channels deployed on a node do not exceed the supported number
  13. For native-or-untagged-encap-failure, multiple encaps are configured as native or untagged on the same path. Check the configured mode type
  14. For multiple-external-encap, a bridge domain can be extended outside the fabric using only one external encap per node
  15. For multiple-ctx-configuration, an L3 interface can belong to only 1 VRF at a time
  16. For encap-already-in-use, another EPG is already configured using this encap
  17. For invalid-vlan :
    1. This EPG's encap may not be valid for the domain on which the EPG is configured
    2. Check Fabric -> Acccess Policies -> Switches -> Leaf Switches -> Profile -> has a leaf profile defined with required node where config is deployed.
    3. Check leaf-profile is associated with interface selector with target profile.
    4. Check whether Fabric -> Access Policies -> Interface -> Leaf Interfaces -> Profiles has interface profile configured with required port and associated to leaf interface policy group.
    5. Check configured leaf interface policy-group in Fabric -> Access Policies -> Interface -> Leaf Interfaces -> Policy Groups has ?Attached Entity Profile? configured.
    6. Attached Entity profile should have domain configured with vlan-pool contains deployed vlan.
  18. For insufficient vlan, check the sum of number of EPG and number of BD applied on switch which should not exceed the capapcity of ToR. Check scalability guide.
  19. For path-wiring-issues, the configured interface has wiring issues
  20. For router-id-conflict ensure that same router ID is used for node in the VRF. Also ensure that node specified under "Logical interface profile" has been added to "Logical node profile".
  21. For port configured as q-in-q tunnel originator/terminator, Configure Leaf Interface Profile with policy-group enabled with “L2 Interface policy” with edgeport turned-on. And also make sure to create Switch Association with Associated Interface Selector Profiles
  22. For further details, refer to the documentation for fv:NwIssues
  23. Verify the End Point Group configuration is correct and complete
  24. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0468: fltFvCtxConfigIssuesConfig-failed

Severity: minor

Explanation: This fault occurs when a given Ctx configured to use a DNS Profile which doesn't configured In Fabric or when BGP RouteTarget Profiles are not configured for Ctx associated to SR-MPLS L3Out.

Recommended Action: If you see this fault, take the following actions:
  1. For dns-policy-not-present issue: Check the Configuration and make sure that DNS Profile consumed by Ctx is defined in fabric. Only DNS Profiles configured for fabric can be used.
  2. For bgp-route-target-profile-not-present issue: Check the Configuration and make sure that BGP RouteTarget Profiles are configured for Ctx associated to SR-MPLS L3Out.
  3. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0469: fltFvBDConfigIssuesConfig-failed

Severity: minor

Explanation: This fault occurs when there is one or more duplicate Subnets defined for BDs or/and AEpGs associated with the Ctx.

Recommended Action: If you see this fault, take the following actions:
  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.
  2. For dhcp-policy-not-present issue: Check the Configuration and make sure that DHCP Pelay Profile consumed by BD is defined in Tenant.
  3. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0471: fltEqptAsicAsicFailed

Severity: major

Explanation: This fault occurs when an ASIC on a card sees a fatal failure during runtime

Recommended Action: 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.

F0474: fltTunnelIfHwProgFail

Severity: major

Explanation: This fault occurs when tunnel manager fails to create a tunnel due to hardware failure.

Recommended Action: To correct this fault, please attempt to create the tunnel again.

F0475: fltTunnelIfDestUnreach

Severity: major

Explanation: This fault occurs when destination becomes unreachable.

Recommended Action: To correct this fault, please ensure that the destination is reachable.

F0482: fltTunnelIfDestIPUnres

Severity: major

Explanation: This fault occurs when destination IP address is unresolved.

Recommended Action: To correct this fault, please ensure that the destination IP address is resolved./>

F0507: fltVpcDomFabricLinksDown

Severity: major

Explanation: This fault occurs when vpc domain bringup fails due to all fabric links being down.

Recommended Action: Please verify fabric connectivity of the switch.

F0508: fltVpcDomPeerRouteDown

Severity: major

Explanation: This fault occurs when vpc domain bringup fails because there is no route to peer.

Recommended Action: Please verify peer configuration and fabric connectivity.

F0509: fltVpcDomPeerUnrch

Severity: major

Explanation: This fault occurs when vpc domain bringup fails due to peer being unreachable.

Recommended Action:

F0510: fltVpcDomDomCompatFail

Severity: major

Explanation: This fault occurs when vpc domain bringup fails due to domain compatibility failure.

Recommended Action: Please verify domain configuration and hardware compatibility of both the peers.

F0511: fltVpcDomElectionErr

Severity: major

Explanation: This fault occurs when vpc domain bringup fails due to election error.

Recommended Action: Please make sure that domain configuration is consistent with the peer.

F0512: fltVpcDomOobNotUp

Severity: major

Explanation: This fault occurs when vpc domain bringup fails due to keepalive being inoperational.

Recommended Action: Please verify keepalive configuration on both the peers.

F0513: fltVpcDomGlobalCompatFail

Severity: major

Explanation: This fault occurs when global configuration on the peers is not consistent.

Recommended Action: Please make sure that global configuration is consistent with the peer.

F0518: fltVpcIfIfCompatFail

Severity: major

Explanation: This fault occurs when vPC configuration on the peers is not consistent.

Recommended Action: Please make sure that the vPC configuration is consistent with the peer.

F0520: fltVpcKeepaliveKeepaliveSendFail

Severity: critical

Explanation: This event occurs when vPC peer keep-alive send has failed.

Recommended Action: Please check if there is an issue with l3 traffic between the peers.

F0522: fltVpcKeepaliveKeepaliveRecvFail

Severity: critical

Explanation: This event occurs when peer keep-alive receive has failed.

Recommended Action:

F0523: fltFvATgConfigurationFailed

Severity: minor

Explanation: This fault occurs when an End Point Group / End Point Security Group is incompletely or incorrectly configured.

Recommended Action: If you see this fault, take the following actions:
  1. Look at the configuration for issues
  2. Verify the End Point Group configuration is correct and complete
  3. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0524: fltFvStCEpConfigurationFailed

Severity: minor

Explanation: This fault occurs when a Static Endpoint (fvStCEp) is not correctly configured.

Recommended Action: If you see this fault, take the following actions:
  1. Specify on which path the static endpoint is present
  2. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0532: fltEthpmIfPortDownInfraEpg

Severity: critical

Explanation: This fault occurs when a port is down and is in use for epg

Recommended Action: If you see this fault, take the following actions
  1. Check the port connectivity
  2. Remove the configuration or administratively shut the port if the port is not in use
  3. To remove the static port configuration from EPG go to Tenant->ApplicationProfile->ApplicationEPG->Static Ports and remove the affected port if not being used.
  4. For mcp-loop-err-disable, this could be due to a loop in the network. Check the config to resolve any loops
  5. For lacp suspended ports, check for following issues -
    1. Check whether peer device supports lacp or not.
    2. Enable LACP feature in peer device, if peer device requires explicit global configuration.
    3. Check vlan range configured part of member interface and port-channel configurations matches.
    4. Check whether peer physical interface is added to port-channel as member interface.
    5. Check whether lacp is configured on member interface of peer device.
    6. If peer switch is of Cisco's, issue "show lacp counters" and verify interfaces of peer device are sending LACP PDU.
    7. Using the "show etherchannel summary"/"show port-channel summary" command, ensure that the port-channel shows the S (Layer-2) and U (in use) flags, and that both the interfaces appear in the ports column with the P (bundled) flag.
    8. If peer switch or router is not manufactured by Cisco, Please contact customer support of peer device's manufacturer for not sending lacp or recommended configuration guidelines.
  6. For reason of suspend(connected) port, check whether VPC domain is configured in GUI Fabric-> External Access/Access Policies ->Virtual Port Channel defaul to tie two switches part of VPC domain if intent is to make two switches part of VPC.
  7. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0543: fltEthpmIfPortDownInfraNoEpg

Severity: major

Explanation: This fault occurs when a port is down and is in use for infra and no epg

Recommended Action: If you see this fault, take the following actions
  1. Check the port connectivity
  2. Remove the configuration or administratively shut the port if the port is not in use
  3. For mcp-loop-err-disable, this could be due to a loop in the network. Check the config to resolve any loops
  4. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0546: fltEthpmIfPortDownNoInfra

Severity: warning

Explanation: This fault occurs when a port goes down

Recommended Action: If you see this fault, take the following actions
  1. Check the port connectivity
  2. Administratively shut the port if the port is not in use
  3. For mcp-loop-err-disable, this could be due to a loop in the network. Check the config to resolve any loops
  4. For bpdu-guard-err-disable, Check configuration of peer device connected to Top of Rack Switch where peer device is sending BPDU to Top of Rack switch's interface and interfaces were configured with BPDU guard makes interface to go into err-disabled as intended
  5. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0564: fltVmmCtrlrPConfigFailed

Severity: minor

Explanation: This fault is raised when the VMM Controller cannot be deployed due to a missing or invalid configuration.

Recommended Action: If you see this fault, take the following actions:
  1. Verify that the policy for the VMM Controller is complete.
  2. Review the fault message and add missing or remove invalid configuration.
  3. If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.

F0565: fltVmmEpPDDeployFailed

Severity: major

Explanation: This fault is raised when the Endpoint Group cannot be deployed due to a missing or invalid configuration.

Recommended Action: If you see this fault, take the following actions:
  1. Verify that a VLAN pool is associated to the VMM Domain.
  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.
  3. Disable EPG isolation if the EPG is associated with a VMware Domain in AVS mode, or a Microsoft(SCVMM) Domain.
  4. Review the fault message and add missing or remove invalid configuration.
  5. Check whether required encap blocks are configured in pool.
  6. If the above actions did not resolve the issue, collect tech-support file and contact Cisco TAC.

F0600: fltPcAggrMbrIfPortSuspended

Severity: major

Explanation: This fault occurs when port has been suspended.

Recommended Action: Please verify the configuration on both ends of the port-channel.

F0603: fltPcAggrMbrIfPortIndividual

Severity: minor

Explanation: This fault occurs when port becomes operationally individual.

Recommended Action: Please verify the configuration on both ends of the port-channel.

F0618: fltMgmtNodeDefMgmtAddressNotAllocated

Severity: minor

Explanation: This fault occurs when a management node address is not allocated to a node.

Recommended Action: If you see this fault, take the following actions:
  1. Create a node management address policy for the node.
  2. Ensure that there are no other faults related to the node management address policy.
  3. If above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0650: fltTraceroutepRsTrEpSrcMissingSrcIp

Severity: warning

Explanation: This fault occurs when the source Endpoint IP address that the traceroute policy is configured to run with is not found in the fabric.

Recommended Action: If you see this fault, take the following actions:
  1. Verify that the configured source Endpoint IP address in the Traceroute Policy exists in the fabric and is correct
  2. Review the fault message and add missing or remove invalid configuration
  3. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0657: fltTraceroutepRsTrEpDstMissingDestIp

Severity: warning

Explanation: This fault occurs when the destination Endpoint IP address that the traceroute policy is configured to run with is not found in the fabric.

Recommended Action: If you see this fault, take the following actions:
  1. Verify that the configured destination Endpoint IP address in the Traceroute Policy exists in the fabric and is correct
  2. Review the fault message and add missing or remove invalid configuration
  3. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0699: fltInfraHostCfgConfigurationFailed

Severity: minor

Explanation: : 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.

Recommended Action: : 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.

F0701: fltInfraADomPConfigFailed

Severity: minor

Explanation: Infra Policy fault is raised when the configured Domain cannot be deployed due to a missing or invalid configuration.

Recommended Action: If you see this fault, take the following actions:
  1. Review the fault message to identify configuration issue.
  2. Modify configuration to add any missing parameters.
  3. Modify configuration to remove any invalid configuration parameters.
  4. If the listed recommendations do not resolve the issue, collect tech-support file and contact Cisco TAC.

F0721: fltFvnsAInstPConfigFailed

Severity: minor

Explanation: This fault is raised when a VLAN/VxLAN/NVGRE pool cannot be deployed due to a missing or invalid configuration.

Recommended Action: If you see this fault, take the following actions:
  1. Review the fault message and correct the invalid configuration.
  2. If the above actions did not resolve the issue, collect a tech-support file and contact Cisco TAC.

F0749: fltFabricProtGEpConfigurationFailed

Severity: warning

Explanation: 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:
  1. At least one of the fabric nodes that is part of the vPC is not ready
  2. The IP address for at least one of the fabric nodes is unknown
  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)
  4. One of the fabric nodes is not a leaf (vPC pairs can only be formed between two leafs)
  5. The Virtual Ip address has been not allocated yet
  6. The Logical Pair Id has not been allocated yet
  7. Nodes are not in same POD
Recommended Action: If you see this fault, take the following actions:
  1. Verify that corresponding fabric nodes are ready
  2. Verify that corresponding fabric nodes are ready
  3. Verify that corresponding fabric nodes are leaf
  4. Verify that the fabric node is not already part of another protection group
  5. In case of fabricExplicitGEp, verify that the pair id is set
  6. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0750: fltFabricProtGEpOperStateChange

Severity: minor

Explanation: 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:
  1. One of the fabric nodes that is part of the vPC is not ready
  2. The fabric node ip address is not known
  3. One of the fabric nodes is not a leaf (vPC pairs can only be formed between two leafs)
Recommended Action: If you see this fault, take the following actions:
  1. Verify that corresponding fabric nodes are ready
  2. Verify that corresponding fabric nodes are leafs
  3. Verify that the fabric node is not already part of another protection group
  4. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0751: fltFabricProtGEpOperStateFail

Severity: critical

Explanation: 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

Recommended Action: If you see this fault, take the following actions:
  1. Verify that the corresponding fabric nodes are ready to receive policies by checking Fabric->Inventory->Fabric Membership->Leaf Node Status to be Active.
  2. Verify that the corresponding fabric nodes are leafs by checking the Fabric->Inventory->Fabric Membership->Role .
  3. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0756: fltPolNToRefMismatchTarget

Severity: minor

Explanation: This fault occurs when a configured target of a named relationship cannot be resolved.

Recommended Action: If you see this fault, take the following actions:
  1. Verify that the configuration for the named target is correct and complete, and that it exists
  2. Verify the configuration for the specific relationship is correct and complete.
  3. If the above actions did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0757: fltVnsAbsGraphValidationFailed

Severity: minor

Explanation: This fault occurs due to an invalid service graph configuration.

Recommended Action: If you see this fault, please modify service graph configuration to fix validation errors.

F0758: fltVnsGraphInstRenderingFailed

Severity: minor

Explanation: This fault occurs when a service graph could not be instantiated.

Recommended Action: If you see this fault, take the following actions:
  1. Look at the graph configuration for issues
  2. For missing-lif, check for fault on LDev or check LDev specified in LDevCtx
  3. For function-type-mismatch-failure, check for valid MFunc in the MDev for selected LDev
  4. For missing-ldev-ctx, check if LDevCtx is defined under tenant, or check if LDev associated with LDevCtx has proper MDev specified.
  5. For missing-lif, check that matching LIF for func connector exists
  6. For invalid-filter-referred-by-rsconntoflt, check AbsFuncConn to filter relation is formed
  7. For missing-l3ctx, check that RsConnToCtxTerm points to valid tDn
  8. For param-cardinality-error, check that configuration parameter has valid cardinality, Graph param/rel can only have at most one instance
  9. For invalid-abstract-graph-config-param, check that all abstract graph configurations are valid
  10. For param-validation-failed, check that all specified params are valid
  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
  12. For invalid-conn-for-configparam, check that RsCfgToConn is configured in AbsConn and is pointing to a valid connector
  13. For invalid-rsmconnatt, check for valid RsMConn in AbsConn
  14. For missing-mandatory-param, check that all mandatory graph params and graph relations exist
  15. For invalid-relation-target, fix the incorrect service folder/param name

F0759: fltVnsNodeInstNodeRenderingFailed

Severity: minor

Explanation: This fault occurs when a service graph could not be instantiated.

Recommended Action: If you see this fault, please modify graph configuration to resolve cause of fault.

F0760: fltVnsTermNodeInstNodeRenderingFailed

Severity: minor

Explanation: This fault occurs when a service graph could not be instantiated.

Recommended Action: If you see this fault, please modify graph configuration to resolve cause of fault.

F0761: fltVnsGParamResolutionFailed

Severity: minor

Explanation: This fault occurs when a cfg parameter has an error..

Recommended Action: If you see this fault, please modify your configuration to provide all needed parameters and folders.

F0762: fltVnsAbsFolderResolutionFailed

Severity: minor

Explanation: This fault occurs when a cfg parameter has an error..

Recommended Action: If you see this fault, please modify your configuration to update service graph config parameters and folders.

F0763: fltVnsAbsParamResolutionFailed

Severity: minor

Explanation: This fault occurs when a cfg parameter has an error..

Recommended Action: If you see this fault, please modify your configuration to update service graph config parameters and folders.

F0764: fltVnsALDevConfMismatch

Severity: minor

Explanation: 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.

Recommended Action: If you see this fault, please modify LDev configuration to resolve cause of fault.

F0765: fltVnsCDevConfMismatch

Severity: minor

Explanation: This fault occurs when a user provided Concrete device configuration is invalid. The config issues indicate the exact reason for the error.

Recommended Action: If you see this fault, please modify CDev configuration to resolve cause of fault.

F0766: fltVnsGFolderResolutionFailed

Severity: minor

Explanation: This fault occurs when a config folder has an error. The config issues indicate the exact reason for the error.

Recommended Action: If you see this fault, please modify configuration of the folder to resolve the cause of fault.

F0768: fltVnsGRelResolutionFailed

Severity: minor

Explanation: This fault occurs when a config GRel has an an error. The config issues indicate the exact reason for the error.

Recommended Action: If you see this fault, please modify configuration of the GRel to resolve the cause of fault.

F0769: fltVnsFuncConnInstValidationFailed

Severity: minor

Explanation: This fault occurs when a Function Connector (FuncConnInst) has an error.The config issues the exact reason for the error.

Recommended Action: If you see this fault, please modify configuration to resolve the cause of fault.

F0770: fltVnsTermConnInstValidationFailed

Severity: minor

Explanation: This fault occurs when a Terminal Connector (TermConnInst) has an error.The config issues the exact reason for the error.

Recommended Action: If you see this fault, please modify configuration to resolve the cause of fault.

F0771: fltVnsConnectionInstValidationFailed

Severity: minor

Explanation: This fault occurs when a Connection Inst (ConnectionInst) has an error.The config issues the exact reason for the error.

Recommended Action: If you see this fault, please modify your configuration to resolve the cause of fault.

F0772: fltVnsALIfValidationFailed

Severity: minor

Explanation: This fault occurs when a Logical Interface configuration is invalid.The config issues the exact reason for the error.

Recommended Action: If you see this fault, please modify configuration to resolve the cause of fault.

F0843: fltSyntheticATestObjPm-atest

Severity: critical

Explanation: This fault is for testing purpose. It is to test if EM framework can raise and clear fault correclty.

Recommended Action: This fault will not be raised on customer or QA test bed:
  1. This fault is for testing purpose. It is to test if EM framework can raise and clear fault correclty.

F0844: fltSyntheticTLTestObjPm-tltest

Severity: minor

Explanation: This fault is for testing purpose. It is to test if EM framework can raise and clear fault correclty.

Recommended Action: This fault will not be raised on customer or QA test bed:
  1. This fault is for testing purpose. It is to test if EM framework can raise and clear fault correclty.

F0845: fltSyntheticCTestObjPm-ctest

Severity: major

Explanation: This fault is for testing purpose. It is to test if EM framework can raise and clear fault correclty.

Recommended Action: This fault will not be raised on customer or QA test bed:
  1. This fault is for testing purpose. It is to test if EM framework can raise and clear fault correclty.

F0846: fltSyntheticATestObjPe-atest

Severity: critical

Explanation: This fault is for testing purpose. It is to test if EM framework can raise and clear fault correclty.

Recommended Action: This fault will not be raised on customer or QA test bed:
  1. This fault is for testing purpose. It is to test if EM framework can raise and clear fault correclty.

F0847: fltSyntheticTLTestObjPe-tltest

Severity: minor

Explanation: This fault is for testing purpose. It is to test if EM framework can raise and clear fault correclty.

Recommended Action: This fault will not be raised on customer or QA test bed:
  1. This fault is for testing purpose. It is to test if EM framework can raise and clear fault correclty.

F0848: fltSyntheticCTestObjPe-ctest

Severity: major

Explanation: This fault is for testing purpose. It is to test if EM framework can raise and clear fault correclty.

Recommended Action: This fault will not be raised on customer or QA test bed:
  1. This fault is for testing purpose. It is to test if EM framework can raise and clear fault correclty.

F0849: fltInfraSelectorIssuesConfig-failed

Severity: minor

Explanation: This fault occurs when a infra selector (port selector, card selector, node selector etc.) is incorrectly configured.

Recommended Action: If you see this fault, take the following actions:
  1. Look at the configuration for issues
  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.
  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.
  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.
  5. For further details, refer to the documentation for fabric:SelectorIssues
  6. Verify the infra selector configuration is correct and complete
  7. If the above action did not resolve the issue, create a tech-support file and contact Cisco TAC.

F0853: fltBgpRsPeerPfxPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0854: fltCallhomeRsInvSchedulerResolveFail

Severity: warning

Explanation: This fault is raised when the inventory policy refers to a scheduler that does not exist.

Recommended Action: Check that the name of the scheduler is spelled correctly or create it if it doesn't exist.

F0855: fltCallhomeRsDestGroupRelResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0856: fltCallhomeRsDestGroupResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0857: fltCallhomeRsQueryGroupRelResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0859: fltConditionRsNodeAaaRecRetPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0860: fltConditionRsNodeEventRecRetPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0861: fltConditionRsNodeFaultRecRetPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0862: fltConditionRsNodeHealthRecRetPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0864: fltConfigRsExportSchedulerResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0865: fltConfigRsImportSourceResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0866: fltDatetimeRsNtpProvToNtpAuthKeyResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0867: fltDbgacRsToEpForEpToEpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0868: fltDbgacRsFromEpForEpToEpgResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0869: fltDbgacRsToLDevForEpToExtResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0870: fltDbgacRsToEpForEpgToEpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0871: fltDbgacRsToEpgForEpgToEpgResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0872: fltDbgacRsToLDevForEpgToIpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0873: fltDbgacRsFromLDevForExtToEpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0874: fltDbgacRsFromEpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0875: fltDbgacRsFromEpgResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0876: fltDbgacRsFromLDevForIpToEpgResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0878: fltDbgacRsToEpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0879: fltDbgacRsToEpgResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0880: fltDbgexpRsUserCtxResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0881: fltDbgexpRsDataResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0882: fltDbgexpRsExportDestResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0883: fltDbgexpRsTSSchedulerResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0885: fltDhcpRsDhcpOptionPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0886: fltDhcpRsRelayPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0887: fltDhcpRsProvResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0888: fltPolRsFirmwareRepoPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0889: fltDnsRsDnsProfileResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0897: fltFabricRsMonModuleFabricPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0898: fltFabricRsCallhomeInvPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0899: fltFabricRsMonInstFabricPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0900: fltFabricRsNodeCorePResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0901: fltFabricRsNodeTechSupPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0902: fltFabricRsPsuInstPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0903: fltFabricRsMonIfFabricPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0904: fltFabricRsApplCorePResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0905: fltFabricRsApplMonPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0906: fltFabricRsApplTechSupPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0907: fltFabricRsCtrlrPGrpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0909: fltFabricRsLePortPGrpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0913: fltFabricRsLeCardPGrpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0916: fltFabricRsLeCardPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0917: fltFabricRsLePortPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0918: fltFabricRsLeNodePGrpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0919: fltFabricRsCommPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0920: fltFabricRsTimePolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0921: fltFabricRsPodPGrpBGPRRPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0922: fltFabricRsPodPGrpCoopPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0923: fltFabricRsPodPGrpIsisDomPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0924: fltFabricRsSnmpPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0925: fltFabricRsPodPGrpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0926: fltFabricRsVpcInstPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0927: fltFabricRsSpPortPGrpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0940: fltFabricRsSpCardPGrpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0943: fltFabricRsSpCardPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0944: fltFabricRsSpPortPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0945: fltFabricRsSpNodePGrpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0946: fltFirmwareRsFwgrppResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0947: fltFvRsBDToOutResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0948: fltFvRsBDToProfileResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0949: fltFvRsBDToRelayPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0950: fltFvRsBdFloodToResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0951: fltFvRsBdToEpRetResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0952: fltFvRsCtxResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0953: fltFvRsIgmpsnResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0954: fltFvRsABDPolMonPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0955: fltFvRsBdResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0956: fltFvRsDomAttResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0957: fltFvRsAEPgMonPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0959: fltFvRsApMonPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0960: fltFvRsBgpCtxPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0963: fltFvRsCtxToEpRetResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0964: fltFvRsOspfCtxPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0965: fltFvRsCtxMonPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0966: fltFvRsDomDefNsLocalResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0967: fltFvRsConsResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0970: fltFvRsConsIfResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0971: fltFvRsCustQosPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0973: fltFvRsProtByResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0974: fltFvRsProvResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0976: fltFvRsBDSubnetToOutResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0977: fltFvRsBDSubnetToProfileResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0978: fltFvRsTnDenyRuleResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0979: fltFvRsTenantMonPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0981: fltInfraRsVlanNsResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0982: fltInfraRsFuncToEpgResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0983: fltInfraRsLacpPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0984: fltInfraRsLacpIfPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0988: fltInfraRsMonModuleInfraPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0989: fltInfraRsAttEntPResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0990: fltInfraRsCdpIfPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0991: fltInfraRsHIfPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0992: fltInfraRsL2InstPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0993: fltInfraRsLldpIfPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0994: fltInfraRsMonIfInfraPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0995: fltInfraRsSpanVDestGrpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0996: fltInfraRsSpanVSrcGrpResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0997: fltInfraRsStpIfPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0998: fltInfraRsMonNodeInfraPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.

F0999: fltInfraRsMstInstPolResolveFail

Severity: warning

Explanation: The object refers to an object that was not found.

Recommended Action: Make sure that referenced object exists and the name is spelled correctly in the relation object.