An FSM is a workflow model, similar to a flow chart, that is composed of the following:
A finite number of stages (states)
Transitions between those stages
The current stage in an FSM is determined by past stages and the operations performed to transition between the stages. A transition from one stage to another is dependent on the success or failure of an operation.
Cisco UCS Manager uses FSM tasks that run in the Data Management Engine (DME) to manage end points in the Cisco UCS object model, including the following
Physical components (chassis, I/O module, servers)
Logical components (LAN cloud, policies)
Workflows (server discovery, service profile management, downloads,
The DME manages the FSM stages and transitions and instructs the Application Gateway (AG) to perform operations on the managed end points. Therefore, each stage can be considered to be an interaction between the DME, AG, and managed end point. The AGs do the real work in interacting with managed end points, such as the CIMC, adapter, or I/O module.
When all of the FSM stages have run successfully, Cisco UCS considers the FSM to be successful.
If the FSM encounters an error or timeout at a stage, the FSM retries that stage at scheduled intervals. When the retry count has been reached for that stage, the FSM stops and Cisco UCS Manager declares the change to have failed. If an FSM task fails, Cisco UCS Manager raises faults and alarms.
Multiple FSM tasks can be associated to an end point. However, only one FSM task at a time can run. Additional FSM tasks for the same end point are placed in a queue and are scheduled to be run when the previous FSM task is either successfully completed or fails.
You can view the FSM details for a particular end point to determine if a task succeeded or failed. You can also use the FSM to troubleshoot any failures.