ACI System Messages
This section lists basic information about the system messages generated by APIC and the ACI switches.
Tip |
For investigating an ACI system message, refer to the "Researching a Fault" section of the Cisco APIC Faults, Events, and System Messages Management Guide (https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/1-x/faults/guide/b_APIC_Faults_Errors.html. You can also find additional details about the faults or events that generate these system messages in the sources listed below. |
-
Cisco APIC System Faults and Messages Reference (https://www.cisco.com/c/dam/en/us/td/docs/Website/datacenter/syslogref/index.html) — An interactive Web-based lookup tool. Enter an APIC fault or event code to learn the cause, recommended action, affected object, severity, and other properties of the system message.
-
Cisco APIC Faults, Events, and System Messages Management Guide (https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/1-x/faults/guide/b_APIC_Faults_Errors.html) — Describes the sources, creation, lifecycle, and management of APIC faults, events, and system messages, and discusses how to research and handle faults and events.
-
Cisco APIC Management Information Model Reference (https://developer.cisco.com/site/apic-mim-ref-api/) — A comprehensive Web-based reference listing all APIC object classes and properties, event types, fault types, and syslog messages. In the Navigation frame of this reference, select the Classes tab to view the properties of the affected object class for a fault or event. Select the Syslog Messages tab and the Syslog Faults link to view a list of faults by fault code. To view the faults by affected object or by the fault name, select the Faults tab.
This document is also embedded in the APIC GUI and can be accessed by clicking the "Help and Tools" icon in the main menu bar, then selecting Documentation > API Documentation.
Note |
Fault messages whose names begin with ‘fsm’ are internal finite state machine (FSM) faults. These faults are raised when specific internal messages or tasks between APIC software components cannot be processed. FSM faults are rarely raised, and when they are, they are often transient (for example, if the system is temporarily busy). These tasks have built-in retries and will raise a fault only after multiple successive retry failures. After such a fault is raised, the retries continue and the fault may eventually be cleared. If an FSM fault persists, the recommended action is to contact Cisco TAC. |