The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter provides information about the faults that may be raised during one or more stages of an FSM task.
Note Unless an FSM fault appears on the Faults tab, you do not need to take any action to resolve the fault. FSM stages fail and retry for many reasons. These faults do not always indicate an issue with a component or the FSM.
[FSM:STAGE:FAILED|RETRY]: Checking license for chassis [chassisId] (iom [id])(FSM-STAGE:sam:dme:EquipmentIOCardFePresence:CheckLicense)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: identifying IOM [chassisId]/[id](FSM-STAGE:sam:dme:EquipmentIOCardFePresence:Identify)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configuring management identity to IOM [chassisId]/[id]([side])(FSM-STAGE:sam:dme:EquipmentIOCardFeConn:ConfigureEndPoint)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configuring fabric interconnect [switchId] mgmt connectivity to IOM [chassisId]/[id]([side])(FSM-STAGE:sam:dme:EquipmentIOCardFeConn:ConfigureSwMgmtEndPoint)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configuring IOM [chassisId]/[id]([side]) virtual name space(FSM-STAGE:sam:dme:EquipmentIOCardFeConn:ConfigureVifNs)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: triggerring chassis discovery via IOM [chassisId]/[id]([side])(FSM-STAGE:sam:dme:EquipmentIOCardFeConn:DiscoverChassis)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: enabling chassis [chassisId] on [side] side(FSM-STAGE:sam:dme:EquipmentIOCardFeConn:EnableChassis)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: unconfiguring access to chassis [id](FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:DisableEndPoint)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: erasing chassis identity [id] from primary(FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:UnIdentifyLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: erasing chassis identity [id] from secondary(FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:UnIdentifyPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: waiting for clean up of resources for chassis [id] (approx. 2 min)(FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:Wait)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: decomissioning chassis [id](FSM-STAGE:sam:dme:EquipmentChassisRemoveChassis:decomission)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: setting locator led to [adminState](FSM-STAGE:sam:dme:EquipmentLocatorLedSetLocatorLed:Execute)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: external mgmt interface configuration on primary(FSM-STAGE:sam:dme:MgmtControllerExtMgmtIfConfig:Primary)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: external mgmt interface configuration on secondary(FSM-STAGE:sam:dme:MgmtControllerExtMgmtIfConfig:Secondary)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: identifying a server in [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:FabricComputeSlotEpIdentify:ExecuteLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: identifying a server in [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:FabricComputeSlotEpIdentify:ExecutePeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Waiting for BIOS POST completion from CIMC on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:BiosPostCompletion)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: power server [chassisId]/[slotId] on with pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:BladeBootPnuos)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Waiting for system reset on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:BladeBootWait)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: power on server [chassisId]/[slotId] for discovery(FSM-STAGE:sam:dme:ComputeBladeDiscover:BladePowerOn)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Waiting for SMBIOS table from CIMC on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:BladeReadSmbios)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcConfigPnuOS)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: getting inventory of server [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcInventory)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcPreConfigPnuOSLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcPreConfigPnuOSPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: checking CIMC of server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcPresence)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Shutdown the server [chassisId]/[slotId]; deep discovery completed(FSM-STAGE:sam:dme:ComputeBladeDiscover:BmcShutdownDiscovered)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configuring primary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:ConfigFeLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configuring secondary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:ConfigFePeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configuring external user access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:ConfigUserAccess)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Invoke post-discovery policies on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:HandlePooling)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configure primary adapter in [chassisId]/[slotId] for pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicConfigPnuOSLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configure secondary adapter in [chassisId]/[slotId] for pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicConfigPnuOSPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: detect mezz cards in [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:NicPresenceLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: detect mezz cards in [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:NicPresencePeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicUnconfigPnuOSLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:NicUnconfigPnuOSPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Populate pre-boot catalog to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSCatalog)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Identify pre-boot environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSIdent)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Perform inventory of server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSInventory)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Populate pre-boot environment behavior policy to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSPolicy)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Scrub server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSScrub)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Trigger self-test of server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:PnuOSSelfTest)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Preparing to check hardware configuration server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:PreSanitize)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Checking hardware configuration server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:Sanitize)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: provisioning a Virtual Media device with a bootable pre-boot image for blade [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:SetupVmediaLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: provisioning a Virtual Media device with a bootable pre-boot image for blade [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:SetupVmediaPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disable Sol Redirection on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:SolRedirectDisable)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: set up bios token on server [chassisId]/[slotId] for Sol redirect(FSM-STAGE:sam:dme:ComputeBladeDiscover:SolRedirectEnable)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configure primary fabric interconnect in [chassisId]/[slotId] for pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:SwConfigPnuOSLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configure secondary fabric interconnect in [chassisId]/[slotId] for pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:SwConfigPnuOSPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unconfigure primary fabric interconnect for server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:SwUnconfigPnuOSLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unconfigure secondary fabric interconnect for server [chassisId]/[slotId] pre-boot environment(FSM-STAGE:sam:dme:ComputeBladeDiscover:SwUnconfigPnuOSPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: unprovisioning the Virtual Media bootable device for blade [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:TeardownVmediaLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: unprovisioning the Virtual media bootable device for blade [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:TeardownVmediaPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: If explicit power capping is enabled, check if power can be allocated to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:checkPowerAvailability)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:hagConnect)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:hagDisconnect)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:serialDebugConnect)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiscover:serialDebugDisconnect)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Deploying Power Management policy changes on chassis [id](FSM-STAGE:sam:dme:EquipmentChassisPsuPolicyConfig:Execute)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resetting FC persistent bindings on host interface [dn](FSM-STAGE:sam:dme:AdaptorHostFcIfResetFcPersBinding:ExecuteLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resetting FC persistent bindings on host interface [dn](FSM-STAGE:sam:dme:AdaptorHostFcIfResetFcPersBinding:ExecutePeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Waiting for BIOS POST completion from CIMC on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BiosPostCompletion)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Power-on server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:BladeBoot)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Waiting for system reset on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BladeBootWait)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Power on server [chassisId]/[slotId] for diagnostics(FSM-STAGE:sam:dme:ComputeBladeDiag:BladePowerOn)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Read SMBIOS tables on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BladeReadSmbios)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputeBladeDiag:BmcConfigPnuOS)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Getting inventory of server [chassisId]/[slotId] via CIMC(FSM-STAGE:sam:dme:ComputeBladeDiag:BmcInventory)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Checking CIMC of server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BmcPresence)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Shutdown server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:BmcShutdownDiagCompleted)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Cleaning up server [chassisId]/[slotId] interface on fabric A(FSM-STAGE:sam:dme:ComputeBladeDiag:CleanupServerConnSwA)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Cleaning up server [chassisId]/[slotId] interface on fabric B(FSM-STAGE:sam:dme:ComputeBladeDiag:CleanupServerConnSwB)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configuring primary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:ConfigFeLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configuring secondary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:ConfigFePeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configuring external user access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:ConfigUserAccess)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Waiting for debugging for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:DebugWait)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Derive diag config for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:DeriveConfig)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disable server [chassisId]/[slotId] interface on fabric A after completion of network traffic tests on fabric A(FSM-STAGE:sam:dme:ComputeBladeDiag:DisableServerConnSwA)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disable server [chassisId]/[slotId] connectivity on fabric B in preparation for network traffic tests on fabric A(FSM-STAGE:sam:dme:ComputeBladeDiag:DisableServerConnSwB)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Enable server [chassisId]/[slotId] connectivity on fabric A in preparation for network traffic tests on fabric A(FSM-STAGE:sam:dme:ComputeBladeDiag:EnableServerConnSwA)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Enable server [chassisId]/[slotId] connectivity on fabric B in preparation for network traffic tests on fabric B(FSM-STAGE:sam:dme:ComputeBladeDiag:EnableServerConnSwB)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Evaluating status; diagnostics completed(FSM-STAGE:sam:dme:ComputeBladeDiag:EvaluateStatus)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Gather status of network traffic tests on fabric A for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:FabricATrafficTestStatus)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Gather status of network tests on fabric B for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:FabricBTrafficTestStatus)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Waiting for collection of diagnostic logs from server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:GenerateLogWait)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Generating report for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:GenerateReport)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Populate diagnostics catalog to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostCatalog)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Connect to diagnostics environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostConnect)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disconnect diagnostics environment agent for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostDisconnect)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Identify diagnostics environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostIdent)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Perform inventory of server [chassisId]/[slotId] in diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:HostInventory)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Populate diagnostics environment behavior policy to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostPolicy)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Trigger diagnostics on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostServerDiag)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Diagnostics status on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:HostServerDiagStatus)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure adapter in server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:NicConfigLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure adapter in server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:NicConfigPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Retrieve adapter inventory in server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:NicInventoryLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Retrieve adapter inventory in server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:NicInventoryPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Detect adapter in server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:NicPresenceLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Detect adapter in server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:NicPresencePeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server [chassisId]/[slotId] diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:NicUnconfigLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server [chassisId]/[slotId] diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:NicUnconfigPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Derive diag config for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:RemoveConfig)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Remove VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:RemoveVMediaLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Remove VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:RemoveVMediaPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Reconfiguring primary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:RestoreConfigFeLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Reconfiguring secondary fabric interconnect access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:RestoreConfigFePeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Populate diagnostics environment with a user account to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:SetDiagUser)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Setup VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SetupVMediaLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Setup VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SetupVMediaPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disable Sol Redirection on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:SolRedirectDisable)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: set up bios token on server [chassisId]/[slotId] for Sol redirect(FSM-STAGE:sam:dme:ComputeBladeDiag:SolRedirectEnable)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Trigger network traffic tests on fabric A on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:StartFabricATrafficTest)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Trigger network tests on fabric B for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:StartFabricBTrafficTest)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Stop VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:StopVMediaLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Stop VMedia for server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:StopVMediaPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure primary fabric interconnect in server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SwConfigLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure secondary fabric interconnect in server [chassisId]/[slotId] for diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SwConfigPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unconfigure primary fabric interconnect for server [chassisId]/[slotId] in diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SwUnconfigLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unconfigure secondary fabric interconnect for server [chassisId]/[slotId] in diagnostics environment(FSM-STAGE:sam:dme:ComputeBladeDiag:SwUnconfigPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unconfigure external user access to server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:UnconfigUserAccess)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Connect to pre-boot environment agent on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:serialDebugConnect)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disconnect pre-boot environment agent for server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeDiag:serialDebugDisconnect)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:FabricLanCloudSwitchMode:SwConfigLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Fabric interconnect mode configuration to primary(FSM-STAGE:sam:dme:FabricLanCloudSwitchMode:SwConfigPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: VNIC profile configuration on local fabric(FSM-STAGE:sam:dme:VnicProfileSetDeploy:Local)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: VNIC profile configuration on peer fabric(FSM-STAGE:sam:dme:VnicProfileSetDeploy:Peer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: propogate updated settings (eg. timezone)(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpSettings)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: propogate updated timezone settings to management controllers.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: propogate updated timezone settings to management controllers.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: propogate updated timezone settings to NICs.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToAdaptorsLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: propogate updated timezone settings to NICs.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToAdaptorsPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: propogate updated timezone settings to FEXs and IOMs.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToFexIomLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: propogate updated timezone settings to FEXs and IOMs.(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:PropogateEpTimeZoneSettingsToFexIomPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: communication service [name] configuration to primary(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:SetEpLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: communication service [name] configuration to secondary(FSM-STAGE:sam:dme:CommSvcEpUpdateSvcEp:SetEpPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: restart web services in primary(FSM-STAGE:sam:dme:CommSvcEpRestartWebSvc:local)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: restart web services in secondary(FSM-STAGE:sam:dme:CommSvcEpRestartWebSvc:peer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: external aaa server configuration to primary(FSM-STAGE:sam:dme:AaaEpUpdateEp:SetEpLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: external aaa server configuration to secondary(FSM-STAGE:sam:dme:AaaEpUpdateEp:SetEpPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: realm configuration to primary(FSM-STAGE:sam:dme:AaaRealmUpdateRealm:SetRealmLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: realm configuration to secondary(FSM-STAGE:sam:dme:AaaRealmUpdateRealm:SetRealmPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: user configuration to primary(FSM-STAGE:sam:dme:AaaUserEpUpdateUserEp:SetUserLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: user configuration to secondary(FSM-STAGE:sam:dme:AaaUserEpUpdateUserEp:SetUserPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: keyring configuration on primary(FSM-STAGE:sam:dme:PkiEpUpdateEp:SetKeyRingLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: keyring configuration on secondary(FSM-STAGE:sam:dme:PkiEpUpdateEp:SetKeyRingPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: [action] file [name](FSM-STAGE:sam:dme:SysfileMutationSingle:Execute)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: remove files from local(FSM-STAGE:sam:dme:SysfileMutationGlobal:Local)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: remove files from peer(FSM-STAGE:sam:dme:SysfileMutationGlobal:Peer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: export core file [name] to [hostname](FSM-STAGE:sam:dme:SysdebugManualCoreFileExportTargetExport:Execute)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configuring automatic core file export service on local(FSM-STAGE:sam:dme:SysdebugAutoCoreFileExportTargetConfigure:Local)
Cisco UCS Manager could not set the configurations in the primary Fabric Interconnect for auto core transfer to remote TFTP server.
If you see this fault, take the following actions:
Step 1 Execute the show tech-support command and contact Cisco Technical Support.
[FSM:STAGE:FAILED|RETRY]: configuring automatic core file export service on peer(FSM-STAGE:sam:dme:SysdebugAutoCoreFileExportTargetConfigure:Peer)
Cisco UCS Manager could not set the configurations in the subordinate Fabric Interconnect (FI) for auto core transfer to remote TFTP server. This fault typically appears for one of the following reasons:
If you see this fault, take the following actions:
Step 1 Check the FI cluster state to ensure that the subordinate FI is reachable and functioning correctly. If the subordinate FI is down, take appropriate corrective actions so that the UCS cluster goes into HA ready state.
Step 2 If the HA state of the primary and subordinate FIs are good, execute the show tech-support command and contact Cisco Technical Support.
[FSM:STAGE:FAILED|RETRY]: persisting LogControl on local(FSM-STAGE:sam:dme:SysdebugLogControlEpLogControlPersist:Local)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: persisting LogControl on peer(FSM-STAGE:sam:dme:SysdebugLogControlEpLogControlPersist:Peer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: internal network configuration on [switchId](FSM-STAGE:sam:dme:SwAccessDomainDeploy:UpdateConnectivity)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Uplink eth port configuration on [switchId](FSM-STAGE:sam:dme:SwEthLanBorderDeploy:UpdateConnectivity)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: VLAN group configuration on [switchId](FSM-STAGE:sam:dme:SwEthLanBorderDeploy:UpdateVlanGroups)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Uplink fc port configuration on [switchId](FSM-STAGE:sam:dme:SwFcSanBorderDeploy:UpdateConnectivity)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Utility network configuration on [switchId](FSM-STAGE:sam:dme:SwUtilityDomainDeploy:UpdateConnectivity)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: create on primary(FSM-STAGE:sam:dme:SyntheticFsObjCreate:createLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: create on secondary(FSM-STAGE:sam:dme:SyntheticFsObjCreate:createRemote)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: sync images to subordinate(FSM-STAGE:sam:dme:FirmwareDownloaderDownload:CopyRemote)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: deleting downloadable [fileName] on local(FSM-STAGE:sam:dme:FirmwareDownloaderDownload:DeleteLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: downloading image [fileName] from [server](FSM-STAGE:sam:dme:FirmwareDownloaderDownload:Local)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: unpacking image [fileName] on primary(FSM-STAGE:sam:dme:FirmwareDownloaderDownload:UnpackLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: deleting image file [name] ([invTag]) from primary(FSM-STAGE:sam:dme:FirmwareImageDelete:Local)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: deleting image file [name] ([invTag]) from secondary(FSM-STAGE:sam:dme:FirmwareImageDelete:Remote)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: copying image from external repository to local repository(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:copyToLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: copying image from external repository to local repository of peer(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:copyToPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: rebooting local fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:resetLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: rebooting remote fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:resetRemote)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: updating local fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:updateLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: updating peer fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:updateRemote)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: verifying boot variables for local fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:verifyLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: verifying boot variables for remote fabric interconnect(FSM-STAGE:sam:dme:MgmtControllerUpdateSwitch:verifyRemote)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: waiting for IOM update(FSM-STAGE:sam:dme:MgmtControllerUpdateIOM:PollUpdateStatus)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: sending update request to IOM(FSM-STAGE:sam:dme:MgmtControllerUpdateIOM:UpdateRequest)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: activating backup image of IOM(FSM-STAGE:sam:dme:MgmtControllerActivateIOM:Activate)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resetting IOM to boot the activated version(FSM-STAGE:sam:dme:MgmtControllerActivateIOM:Reset)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: waiting for update to complete(FSM-STAGE:sam:dme:MgmtControllerUpdateBMC:PollUpdateStatus)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: sending update request to CIMC(FSM-STAGE:sam:dme:MgmtControllerUpdateBMC:UpdateRequest)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: activating backup image of CIMC(FSM-STAGE:sam:dme:MgmtControllerActivateBMC:Activate)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resetting CIMC to boot the activated version(FSM-STAGE:sam:dme:MgmtControllerActivateBMC:Reset)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: call-home configuration on primary(FSM-STAGE:sam:dme:CallhomeEpConfigCallhome:SetLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: call-home configuration on secondary(FSM-STAGE:sam:dme:CallhomeEpConfigCallhome:SetPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configuring the out-of-band interface(FSM-STAGE:sam:dme:MgmtIfSwMgmtOobIfConfig:Switch)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configuring the inband interface(FSM-STAGE:sam:dme:MgmtIfSwMgmtInbandIfConfig:Switch)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Updating virtual interface on local fabric interconnect(FSM-STAGE:sam:dme:MgmtIfVirtualIfConfig:Local)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Updating virtual interface on peer fabric interconnect(FSM-STAGE:sam:dme:MgmtIfVirtualIfConfig:Remote)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Enable virtual interface on local fabric interconnect(FSM-STAGE:sam:dme:MgmtIfEnableVip:Local)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disable virtual interface on peer fabric interconnect(FSM-STAGE:sam:dme:MgmtIfDisableVip:Peer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Transition from single to cluster mode(FSM-STAGE:sam:dme:MgmtIfEnableHA:Local)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: internal database backup(FSM-STAGE:sam:dme:MgmtBackupBackup:backupLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: internal system backup(FSM-STAGE:sam:dme:MgmtBackupBackup:upload)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: importing the configuration file(FSM-STAGE:sam:dme:MgmtImporterImport:config)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: downloading the configuration file from the remote location(FSM-STAGE:sam:dme:MgmtImporterImport:downloadLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Report results of configuration application(FSM-STAGE:sam:dme:MgmtImporterImport:reportResults)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Update endpoint on fabric interconnect A(FSM-STAGE:sam:dme:StatsCollectionPolicyUpdateEp:SetEpA)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Update endpoint on fabric interconnect B(FSM-STAGE:sam:dme:StatsCollectionPolicyUpdateEp:SetEpB)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: QoS Classification Definition [name] configuration on primary(FSM-STAGE:sam:dme:QosclassDefinitionConfigGlobalQoS:SetLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: QoS Classification Definition [name] configuration on secondary(FSM-STAGE:sam:dme:QosclassDefinitionConfigGlobalQoS:SetPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: vnic qos policy [name] configuration to primary(FSM-STAGE:sam:dme:EpqosDefinitionDeploy:Local)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: vnic qos policy [name] configuration to secondary(FSM-STAGE:sam:dme:EpqosDefinitionDeploy:Peer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: vnic qos policy [name] removal from primary(FSM-STAGE:sam:dme:EpqosDefinitionDelTaskRemove:Local)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: vnic qos policy [name] removal from secondary(FSM-STAGE:sam:dme:EpqosDefinitionDelTaskRemove:Peer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resetting Chassis Management Controller on IOM [chassisId]/[id](FSM-STAGE:sam:dme:EquipmentIOCardResetCmc:Execute)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: copying image from external repository to local repository(FSM-STAGE:sam:dme:MgmtControllerUpdateUCSManager:copyExtToLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: copying image from external repository to local repository of peer(FSM-STAGE:sam:dme:MgmtControllerUpdateUCSManager:copyExtToPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Updating UCS Manager firmware(FSM-STAGE:sam:dme:MgmtControllerUpdateUCSManager:execute)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Scheduling UCS manager update(FSM-STAGE:sam:dme:MgmtControllerUpdateUCSManager:start)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: system configuration on primary(FSM-STAGE:sam:dme:MgmtControllerSysConfig:Primary)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: system configuration on secondary(FSM-STAGE:sam:dme:MgmtControllerSysConfig:Secondary)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disable path [side]([switchId]) on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorExtEthIfPathReset:Disable)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Enabe path [side]([switchId]) on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorExtEthIfPathReset:Enable)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disable circuit A for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostEthIfCircuitReset:DisableA)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disable circuit B for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostEthIfCircuitReset:DisableB)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Enable circuit A for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostEthIfCircuitReset:EnableA)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Enable circuit B for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostEthIfCircuitReset:EnableB)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disable circuit A for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostFcIfCircuitReset:DisableA)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disable circuit B for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostFcIfCircuitReset:DisableB)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Enable circuit A for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostFcIfCircuitReset:EnableA)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Enable circuit B for host adaptor [id] on server [chassisId]/[slotId](FSM-STAGE:sam:dme:AdaptorHostFcIfCircuitReset:EnableB)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: external VM manager version fetch(FSM-STAGE:sam:dme:ExtvmmProviderConfig:GetVersion)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: external VM manager configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmProviderConfig:SetLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: external VM manager configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmProviderConfig:SetPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: external VM manager cetificate configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmKeyStoreCertInstall:SetLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: external VM manager certificate configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmKeyStoreCertInstall:SetPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: external VM manager deletion from local fabric(FSM-STAGE:sam:dme:ExtvmmSwitchDelTaskRemoveProvider:RemoveLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: external VM manager extension-key configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmMasterExtKeyConfig:SetLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: external VM manager extension-key configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmMasterExtKeyConfig:SetPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: applying changes to catalog(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:Apply)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: syncing catalog files to subordinate(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:CopyRemote)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: deleting temp image [fileName] on local(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:DeleteLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: evaluating status of update(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:EvaluateStatus)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: downloading catalog file [fileName] from [server](FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:Local)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: rescanning image files(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:RescanImages)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: unpacking catalog file [fileName] on primary(FSM-STAGE:sam:dme:CapabilityUpdaterUpdater:UnpackLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: deleting package [name] from primary(FSM-STAGE:sam:dme:FirmwareDistributableDelete:Local)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: deleting package [name] from secondary(FSM-STAGE:sam:dme:FirmwareDistributableDelete:Remote)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Power off server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeUpdateBoardController:BladePowerOff)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Power on server [chassisId]/[slotId](FSM-STAGE:sam:dme:ComputeBladeUpdateBoardController:BladePowerOn)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Waiting for Board Controller update to complete(FSM-STAGE:sam:dme:ComputeBladeUpdateBoardController:PollUpdateStatus)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Prepare for BoardController update(FSM-STAGE:sam:dme:ComputeBladeUpdateBoardController:PrepareForUpdate)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Sending Board Controller update request to CIMC(FSM-STAGE:sam:dme:ComputeBladeUpdateBoardController:UpdateRequest)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to local bladeAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncBladeAGLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to remote bladeAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncBladeAGRemote)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to local hostagentAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncHostagentAGLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to remote hostagentAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncHostagentAGRemote)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to local nicAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncNicAGLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to remote nicAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncNicAGRemote)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to local portAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncPortAGLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Sending capability catalogue [version] to remote portAG(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:SyncPortAGRemote)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Finalizing capability catalogue [version] deployment(FSM-STAGE:sam:dme:CapabilityCatalogueDeployCatalogue:finalize)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: cleaning host entries(FSM-STAGE:sam:dme:EquipmentFexRemoveFex:CleanupEntries)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: erasing fex identity [id] from primary(FSM-STAGE:sam:dme:EquipmentFexRemoveFex:UnIdentifyLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: waiting for clean up of resources for chassis [id] (approx. 2 min)(FSM-STAGE:sam:dme:EquipmentFexRemoveFex:Wait)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: decomissioning fex [id](FSM-STAGE:sam:dme:EquipmentFexRemoveFex:decomission)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: setting locator led to [adminState](FSM-STAGE:sam:dme:EquipmentLocatorLedSetFeLocatorLed:Execute)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: (FSM-STAGE:sam:dme:EquipmentChassisPowerCap:Config)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: cleaning host entries(FSM-STAGE:sam:dme:EquipmentIOCardMuxOffline:CleanupEntries)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Activate BIOS image for server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:ActivateBios)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Update blade BIOS image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BiosImgUpdate)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Waiting for BIOS POST completion from CIMC on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:BiosPostCompletion)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Power off server for configuration of service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:BladePowerOff)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BmcConfigPnuOS)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BmcPreconfigPnuOSLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BmcPreconfigPnuOSPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: unprovisioning the bootable device for server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BmcUnconfigPnuOS)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Boot host OS for server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BootHost)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Bring-up pre-boot environment for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:BootPnuos)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Waiting for system reset(FSM-STAGE:sam:dme:ComputePhysicalAssociate:BootWait)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Clearing pending BIOS image update(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ClearBiosUpdate)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configuring FlexFlash(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigFlexFlash)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configuring SoL interface on server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigSoL)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configuring external user access(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigUserAccess)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure logical UUID for server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:ConfigUuid)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalAssociate:DeassertResetBypass)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Update Host Bus Adapter image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HbaImgUpdate)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure host OS components on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HostOSConfig)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Identify host agent on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HostOSIdent)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Upload host agent policy to host agent on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HostOSPolicy)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Validate host OS on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:HostOSValidate)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Update LocalDisk firmware image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:LocalDiskFwUpdate)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalAssociate:MarkAdapterForReboot)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure adapter in server for host OS (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigHostOSLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure adapter in server for host OS (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigHostOSPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigPnuOSLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigPnuOSPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Update adapter image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicImgUpdate)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicUnconfigPnuOSLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicUnconfigPnuOSPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Populate pre-boot catalog to server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSCatalog)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure server with service profile [assignedToDn] pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSConfig)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Identify pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSIdent)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Perform inventory of server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSInventory)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure local disk on server with service profile [assignedToDn] pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSLocalDiskConfig)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Populate pre-boot environment behavior policy(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSPolicy)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Trigger self-test on pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSSelfTest)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unload drivers on server with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSUnloadDrivers)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Pre-boot environment validation for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:PnuOSValidate)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: waiting for BIOS activate(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PollBiosActivateStatus)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Waiting for BIOS update to complete(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PollBiosUpdateStatus)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Waiting for Board Controller update to complete(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PollBoardCtrlUpdateStatus)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: waiting for pending BIOS image update to clear(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PollClearBiosUpdateStatus)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Power on server for configuration of service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:PowerOn)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Preparing to check hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PreSanitize)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Prepare server for booting host OS(FSM-STAGE:sam:dme:ComputePhysicalAssociate:PrepareForBoot)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Checking hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalAssociate:Sanitize)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Disable Sol Redirection on server [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:SolRedirectDisable)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: set up bios token for server [assignedToDn] for Sol redirect(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SolRedirectEnable)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Update storage controller image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:StorageCtlrImgUpdate)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure primary fabric interconnect for server host os (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigHostOSLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure secondary fabric interconnect for server host OS (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigHostOSPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure primary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigPnuOSLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Configure secondary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigPnuOSPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configuring primary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigPortNivLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: configuring secondary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwConfigPortNivPeer)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unconfigure primary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SwUnconfigPnuOSLocal)
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 UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.