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.
[FSM:STAGE:FAILED|RETRY]: Unconfigure secondary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate: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]: Sync power state for server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SyncPowerState)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 BIOS request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalAssociate:UpdateBiosRequest)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputePhysicalAssociate:UpdateBoardCtrlRequest)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 Storage(FC Zones) Connectivity(FSM-STAGE:sam:dme:ComputePhysicalAssociate:VerifyFcZoneConfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalAssociate:activateAdaptorNwFwLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalAssociate:activateAdaptorNwFwPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:activateIBMCFw)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 host agent on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:hagHostOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:hagPnuOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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(FSM-STAGE:sam:dme:ComputePhysicalAssociate:hagPnuOSDisconnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Reset CIMC of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:resetIBMC)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:serialDebugPnuOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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(FSM-STAGE:sam:dme:ComputePhysicalAssociate:serialDebugPnuOSDisconnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 network firmware(FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateAdaptorNwFwLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 network firmware(FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateAdaptorNwFwPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateIBMCFw)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForAdaptorNwFwUpdateLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForAdaptorNwFwUpdatePeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Wait for CIMC firmware completion on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForIBMCFwUpdate)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputePhysicalDisassociate: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]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:ComputePhysicalDisassociate: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:ComputePhysicalDisassociate: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:ComputePhysicalDisassociate: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]: Bring-up pre-boot environment on server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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 on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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]: Configuring BIOS Defaults on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:ConfigBios)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputePhysicalDisassociate: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]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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]: Apply post-disassociation policies to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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 adapter for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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 on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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]: Unconfigure host OS connectivity from server adapter(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigHostOSLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 host OS connectivity from server adapter(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigHostOSPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputePhysicalDisassociate: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:ComputePhysicalDisassociate: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:ComputePhysicalDisassociate: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(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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]: Populate pre-boot environment behavior policy to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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 pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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]: Unconfigure server from service profile [assignedToDn] pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSUnconfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 validate server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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]: Power on server for unconfiguration of service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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 server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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]: Shutdown server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:Shutdown)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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 [serverId] for Sol redirect(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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 for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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 on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:ComputePhysicalDisassociate: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:ComputePhysicalDisassociate: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 host OS connectivity from server to primary fabric interconnect(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwUnconfigHostOSLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 host OS connectivity from server to secondary fabric interconnect(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwUnconfigHostOSPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputePhysicalDisassociate: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 pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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]: Unconfiguring BIOS Settings and Boot Order of server [serverId] (service profile [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigBios)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 FlexFlash(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigFlexFlash)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Removing SoL configuration from server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigSoL)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Restore original UUID for server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigUuid)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 Storage(FC Zones) Connectivity(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:VerifyFcZoneConfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:hagPnuOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:hagPnuOSDisconnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:serialDebugPnuOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:serialDebugPnuOSDisconnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 power cap of server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowerCap: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 up CIMC configuration for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:CleanupCIMC)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 local port config for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:CleanupPortConfigLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 peer port config for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:CleanupPortConfigPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Decommissioning server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission: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]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission: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]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission: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]: Soft shutdown of server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftShutdown: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]: Hard shutdown of server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardShutdown: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]: Power-on server [dn](FSM-STAGE:sam:dme:ComputePhysicalTurnup: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]: Power-cycle server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowercycle: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]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowercycle: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 [dn](FSM-STAGE:sam:dme:ComputePhysicalPowercycle: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]: Hard-reset server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardreset: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]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardreset: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 [dn](FSM-STAGE:sam:dme:ComputePhysicalHardreset: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]: Soft-reset server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftreset: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]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftreset: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 [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftreset: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]: Updating fabric A for server [dn](FSM-STAGE:sam:dme:ComputePhysicalSwConnUpd:A)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 fabric B for server [dn](FSM-STAGE:sam:dme:ComputePhysicalSwConnUpd:B)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Completing BIOS recovery mode for server [dn], and shutting it down(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Cleanup)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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]: Resetting server [dn] power state after BIOS recovery(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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 V-Media device with a bootable BIOS image for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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 V-Media device with a bootable BIOS image for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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]: Shutting down server [dn] to prepare for BIOS recovery(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Shutdown)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Running BIOS recovery on server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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 V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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]: Waiting for completion of BIOS recovery for server [dn] (up to 15 min)(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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]: Power on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset: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]: Resetting CMOS for server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset: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]: Preparing to check hardware configuration server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset: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]: Reconfiguring BIOS Settings and Boot Order of server [serverId] for service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:ReconfigBios)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 logical UUID of server [serverId] for service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:ReconfigUuid)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset: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]: Resetting Management Controller on server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetBmc: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]: Reset IOM [id] on Fex [chassisId](FSM-STAGE:sam:dme:EquipmentIOCardResetIom: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]: Waiting for BIOS POST completion from CIMC on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id] for discovery(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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]: Configuring connectivity on CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcConfigureConnLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 connectivity on CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcConfigureConnPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 [id] via CIMC(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:ComputeRackUnitDiscover: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:ComputeRackUnitDiscover: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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id]; deep discovery completed(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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]: unprovisioning the bootable device for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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]: power server [id] on with pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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]: setting adapter mode to discovery for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ConfigDiscoveryMode)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 adapter mode to NIV for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ConfigNivMode)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 server [id] for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 server [id] for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 and get mezz cards information from [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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]: detect and get mezz cards information from [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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]: Populate pre-boot catalog to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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]: Explore connectivity of server [id] in pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSConnStatus)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Explore connectivity of server [id] in pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSConnectivity)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id] pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id] pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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]: Waiting for SMBIOS table from CIMC on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ReadSmbios)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id] for Sol redirect(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:ComputeRackUnitDiscover: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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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]: Configuring fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigureConnLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigureConnPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: determine connectivity of server [id] to fabric(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwPnuOSConnectivityLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: determine connectivity of server [id] to fabric(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwPnuOSConnectivityPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 primary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwUnconfigPortNivLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 secondary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwUnconfigPortNivPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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 [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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]: wait for connection to be established(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:waitForConnReady)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Analyzing changes impact(FSM-STAGE:sam:dme:LsServerConfigure:AnalyzeImpact)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 config to server [pnDn](FSM-STAGE:sam:dme:LsServerConfigure:ApplyConfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving and applying default identifiers locally(FSM-STAGE:sam:dme:LsServerConfigure:ApplyDefaultIdentifiers)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving and applying identifiers locally(FSM-STAGE:sam:dme:LsServerConfigure:ApplyIdentifiers)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving and applying policies(FSM-STAGE:sam:dme:LsServerConfigure:ApplyPolicies)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 configuration template [srcTemplName](FSM-STAGE:sam:dme:LsServerConfigure:ApplyTemplate)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: committing storage for service profile(FSM-STAGE:sam:dme:LsServerConfigure:CommitStorage)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Evaluate association with server [pnDn](FSM-STAGE:sam:dme:LsServerConfigure:EvaluateAssociation)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving storage policy(FSM-STAGE:sam:dme:LsServerConfigure:ProvisionStorage)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Computing binding changes(FSM-STAGE:sam:dme:LsServerConfigure:ResolveBootConfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving default identifiers from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveDefaultIdentifiers)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolve distributable from operations manager(FSM-STAGE:sam:dme:LsServerConfigure:ResolveDistributable)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving distributable names from host pack(FSM-STAGE:sam:dme:LsServerConfigure:ResolveDistributableNames)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving identifiers from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveIdentifiers)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolve images from operations manager(FSM-STAGE:sam:dme:LsServerConfigure:ResolveImages)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving various dependent policies from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveNetworkPolicies)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving various template policies from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveNetworkTemplates)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving various policies from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolvePolicies)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving schedule policy from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveSchedule)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving schedule policy from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ValidatePolicyOwnership)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 Association completion on server [pnDn](FSM-STAGE:sam:dme:LsServerConfigure:WaitForAssocCompletion)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 storage commit to complete(FSM-STAGE:sam:dme:LsServerConfigure:WaitForCommitStorage)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 ack or maint window(FSM-STAGE:sam:dme:LsServerConfigure:WaitForMaintPermission)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 maintenance window(FSM-STAGE:sam:dme:LsServerConfigure:WaitForMaintWindow)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 storage provisioning to complete(FSM-STAGE:sam:dme:LsServerConfigure:WaitForStorageProvision)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Ethernet traffic monitor (SPAN)configuration on [switchId](FSM-STAGE:sam:dme:SwEthMonDeploy:UpdateEthMon)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: FC traffic monitor (SPAN)configuration on [switchId](FSM-STAGE:sam:dme:SwFcMonDeploy:UpdateFcMon)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:FabricSanCloudSwitchMode: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 FC mode configuration to primary(FSM-STAGE:sam:dme:FabricSanCloudSwitchMode: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]: external mgmt user deployment on server [dn] (profile [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalUpdateExtUsers:Deploy)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 tech-support file from GUI on local(FSM-STAGE:sam:dme:Sysdebugshow tech-supportInitiate: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]: delete tech-support file from GUI on local(FSM-STAGE:sam:dme:Sysdebugshow tech-supportDeleteTechSupFile: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]: delete tech-support file from GUI on peer(FSM-STAGE:sam:dme:Sysdebugshow tech-supportDeleteTechSupFile: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]: Copy the tech-support file to primary for download(FSM-STAGE:sam:dme:Sysdebugshow tech-supportDownload:CopyPrimary)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: copy tech-support file on subordinate switch to tmp directory(FSM-STAGE:sam:dme:Sysdebugshow tech-supportDownload:CopySub)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Delete the tech-support file from primary switch under tmp directory(FSM-STAGE:sam:dme:Sysdebugshow tech-supportDownload:DeletePrimary)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Delete the tech-support file from subordinate under tmp directory(FSM-STAGE:sam:dme:Sysdebugshow tech-supportDownload:DeleteSub)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputePhysicalUpdateAdaptor:PollUpdateStatusLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputePhysicalUpdateAdaptor:PollUpdateStatusPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 the server(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PowerOff)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 the blade(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor: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]: sending update request to Adaptor(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:UpdateRequestLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 Adaptor(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:UpdateRequestPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 Adaptor(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:ActivateLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 Adaptor(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:ActivatePeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputePhysicalActivateAdaptor: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]: power on the blade(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor: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]: reseting the blade(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor: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]: applying changes to catalog(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:ApplyCatalog)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 changes to subordinate(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog: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]: evaluating status of activation(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog: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]: rescanning image files(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog: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]: activating catalog changes(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog: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]: applying changes to catalog(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt:ApplyCatalog)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 management extension changes to subordinate(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt: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]: evaluating status of activation(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt: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]: rescanning image files(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt: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]: activating management extension changes(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt: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]: Copy the license file to subordinate for inventory(FSM-STAGE:sam:dme:LicenseDownloaderDownload: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 temporary files for [fileName] on local(FSM-STAGE:sam:dme:LicenseDownloaderDownload: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]: deleting temporary files for [fileName] on subordinate(FSM-STAGE:sam:dme:LicenseDownloaderDownload:DeleteRemote)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 license file [fileName] from [server](FSM-STAGE:sam:dme:LicenseDownloaderDownload: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]: validation for license file [fileName] on primary(FSM-STAGE:sam:dme:LicenseDownloaderDownload:ValidateLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: validation for license file [fileName] on subordinate(FSM-STAGE:sam:dme:LicenseDownloaderDownload:ValidateRemote)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Installing license on primary(FSM-STAGE:sam:dme:LicenseFileInstall: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]: Installing license on subordinate(FSM-STAGE:sam:dme:LicenseFileInstall: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]: Clearing license on primary(FSM-STAGE:sam:dme:LicenseFileClear: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]: Clearing license on subordinate(FSM-STAGE:sam:dme:LicenseFileClear: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]: Updating on primary(FSM-STAGE:sam:dme:LicenseInstanceUpdateFlexlm: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 on subordinate(FSM-STAGE:sam:dme:LicenseInstanceUpdateFlexlm: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]: configuring SoL interface on server [dn](FSM-STAGE:sam:dme:ComputePhysicalConfigSoL: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]: removing SoL interface configuration from server [dn](FSM-STAGE:sam:dme:ComputePhysicalUnconfigSoL: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]: Shutting down port(FSM-STAGE:sam:dme:PortPIoInCompatSfpPresence:Shutdown)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Execute Diagnostic Interrupt(NMI) for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDiagnosticInterrupt: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]: Copy the Core file to primary for download(FSM-STAGE:sam:dme:SysdebugCoreDownload:CopyPrimary)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: copy Core file on subordinate switch to tmp directory(FSM-STAGE:sam:dme:SysdebugCoreDownload:CopySub)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Delete the Core file from primary switch under tmp directory(FSM-STAGE:sam:dme:SysdebugCoreDownload:DeletePrimary)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Delete the Core file from subordinate under tmp directory(FSM-STAGE:sam:dme:SysdebugCoreDownload:DeleteSub)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:EquipmentChassisDynamicReallocation: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]: Execute KVM Reset for server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetKvm: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 connectivity on CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:BmcConfigureConnLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 connectivity on CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:BmcConfigureConnPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 connectivity to CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:SwConfigureConnLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 connectivity to CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:SwConfigureConnPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 on local fabric-interconnect(FSM-STAGE:sam:dme:ComputeRackUnitOffline:CleanupLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 on peer fabric-interconnect(FSM-STAGE:sam:dme:ComputeRackUnitOffline:CleanupPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitOffline:SwUnconfigureLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitOffline:SwUnconfigurePeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 FI locator led to [adminState](FSM-STAGE:sam:dme:EquipmentLocatorLedSetFiLocatorLed: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]: Apply switch configuration(FSM-STAGE:sam:dme:FabricEpMgrConfigure:ApplyConfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 physical configuration(FSM-STAGE:sam:dme:FabricEpMgrConfigure:ApplyPhysical)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Validating logical configuration(FSM-STAGE:sam:dme:FabricEpMgrConfigure:ValidateConfiguration)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 on physical change application(FSM-STAGE:sam:dme:FabricEpMgrConfigure:WaitOnPhys)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 alias configuration on local fabric(FSM-STAGE:sam:dme:VnicProfileSetDeployAlias: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 alias configuration on peer fabric(FSM-STAGE:sam:dme:VnicProfileSetDeployAlias: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]: Configure physical port mode on fabric interconnect [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:ConfigSwA)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 physical port mode on fabric interconnect [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:ConfigSwB)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Performing local port inventory of switch [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:PortInventorySwA)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Performing peer port inventory of switch [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:PortInventorySwB)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 physical transition on fabric interconnect [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:VerifyPhysConfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 management cluster role configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmEpClusterRole: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 management cluster role configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmEpClusterRole: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]: set Veth Auto-delete Retention Timer on local fabric(FSM-STAGE:sam:dme:VmLifeCyclePolicyConfig: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]: set Veth Auto-delete Retention Timer on peer fabric(FSM-STAGE:sam:dme:VmLifeCyclePolicyConfig: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]: Turn beacon lights on/off for [dn] on fabric interconnect [id](FSM-STAGE:sam:dme:EquipmentBeaconLedIlluminate:ExecuteA)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Turn beacon lights on/off for [dn] on fabric interconnect [id](FSM-STAGE:sam:dme:EquipmentBeaconLedIlluminate:ExecuteB)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 admin speed for [dn](FSM-STAGE:sam:dme:EtherServerIntFIoConfigSpeed:Configure)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputePhysicalUpdateBIOS:Clear)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputePhysicalUpdateBIOS:PollClearStatus)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputePhysicalUpdateBIOS: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 BIOS update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalUpdateBIOS: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 BIOS image(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS: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]: clearing pending BIOS image activate(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:Clear)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputePhysicalActivateBIOS:PollActivateStatus)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 activate to clear(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:PollClearStatus)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 the server(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:PowerOff)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 the server(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS: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]: updating BIOS tokens(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:UpdateTokens)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 identities to external identifier manager(FSM-STAGE:sam:dme:IdentIdentRequestUpdateIdent: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]: Synchronise ID universe to external identifier manager(FSM-STAGE:sam:dme:IdentMetaSystemSync: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]: Check identifier manager availability(FSM-STAGE:sam:dme:IdentMetaSystemSync:Ping)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Execute Reset IPMI configuration for server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetIpmi: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]: Activate BIOS image for server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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 Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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]: Bring-up pre-boot environment for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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]: Update LocalDisk firmware image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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 Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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 Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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]: Shutting down server [dn] after firmware upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:Shutdown)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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 for Sol redirect(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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 pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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:ComputePhysicalFwUpgrade: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 pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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]: Sending update BIOS request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:UpdateBiosRequest)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputePhysicalFwUpgrade:UpdateBoardCtrlRequest)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:activateAdaptorNwFwLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:activateAdaptorNwFwPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:activateIBMCFw)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:hagPnuOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:hagPnuOSDisconnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Reset CIMC of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:resetIBMC)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:serialDebugPnuOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:serialDebugPnuOSDisconnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 network firmware(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:updateAdaptorNwFwLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 network firmware(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:updateAdaptorNwFwPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:updateIBMCFw)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:waitForAdaptorNwFwUpdateLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:waitForAdaptorNwFwUpdatePeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Wait for CIMC firmware completion on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:waitForIBMCFwUpdate)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:ComputeRackUnitAdapterReset: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]: Power-cycle server [dn](FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset:PowerCycle)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 [dn](FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset: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 [dn](FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset: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]: Enabling port(FSM-STAGE:sam:dme:PortPIoInCompatSfpReplaced:EnablePort)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Register FSM Execute(FSM-STAGE:sam:dme:ExtpolEpRegisterFsm: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]: Configure cross-domain XML for FLEX client on local fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainConfig: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]: Configure cross-domain XML for FLEX client on peer fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainConfig: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]: Remove cross-domain XML for FLEX client on local fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainDelete: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]: Remove cross-domain XML for FLEX client on peer fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainDelete: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]: Mount nfs [remoteDir] from server [server] on local switch(FSM-STAGE:sam:dme:NfsMountInstMount:MountLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Mount nfs [remoteDir] from NFS server [server] on peer switch(FSM-STAGE:sam:dme:NfsMountInstMount:MountPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Register client with Ops Mgr(FSM-STAGE:sam:dme:NfsMountInstMount:RegisterClient)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Verify client registration with Ops Mgr(FSM-STAGE:sam:dme:NfsMountInstMount:VerifyRegistration)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unmount nfs [remoteDir] from server [server](FSM-STAGE:sam:dme:NfsMountInstUnmount:UnmountLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Unmount nfs [remoteDir] from server [server](FSM-STAGE:sam:dme:NfsMountInstUnmount:UnmountPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 mount suspend success to operations manager(FSM-STAGE:sam:dme:NfsMountDefReportNfsMountSuspend:Report)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Synchronise requestors with storage broker(FSM-STAGE:sam:dme:StorageSystemSync: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]: Activating IOMs(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateIOM)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 Local Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateLocalFI)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 Peer Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateRemoteFI)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 UCSM(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateUCSM)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 Activation to complete on IOMs(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfIOM)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 Activation to complete on Local Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfLocalFI)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 Activation to complete on Peer Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfRemoteFI)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 UCSM Activate to complete(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfUCSM)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 of IOMs to complete(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollUpdateOfIOM)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolve distributable from operations manager(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ResolveDistributable)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving distributable name from infra pack(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ResolveDistributableNames)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolve images from operations manager(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ResolveImages)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 back-up image of IOMs(FSM-STAGE:sam:dme:FirmwareSystemDeploy:UpdateIOM)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 Deploy to begin(FSM-STAGE:sam:dme:FirmwareSystemDeploy:WaitForDeploy)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 User Acknowledgement To Start Primary Fabric Interconnect Activation(FSM-STAGE:sam:dme:FirmwareSystemDeploy:WaitForUserAck)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 Catalog(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ActivateCatalog)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolve distributable from operations manager(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ResolveDistributable)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving distributable name(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ResolveDistributableNames)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolve images from operations manager(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ResolveImages)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolving scrub policy from UCS Central(FSM-STAGE:sam:dme:ComputeServerDiscPolicyResolveScrubPolicy:Resolve)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: fc zone configuration on [switchId](FSM-STAGE:sam:dme:SwFcSanBorderActivateZoneSet:UpdateZones)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 certificates, channels and policy meta data(FSM-STAGE:sam:dme:ExtpolEpRepairCert:cleanOldData)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 latest certificates(FSM-STAGE:sam:dme:ExtpolEpRepairCert:request)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: unregister from old UCS Central, if needed(FSM-STAGE:sam:dme:ExtpolEpRepairCert:unregister)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 that cert was provisioned(FSM-STAGE:sam:dme:ExtpolEpRepairCert:verify)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 GUID of UCS Central(FSM-STAGE:sam:dme:ExtpolEpRepairCert:verifyGuid)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyControlEpOperate:Resolve)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeReleasePolicyFsm:Release)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeReleaseOperationFsm:Release)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeReleaseStorageFsm:Release)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeResolveManyPolicyFsm:ResolveMany)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeResolveManyOperationFsm:ResolveMany)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeResolveManyStorageFsm:ResolveMany)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeReleaseManyPolicyFsm:ReleaseMany)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeReleaseManyOperationFsm:ReleaseMany)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeReleaseManyStorageFsm:ReleaseMany)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeResolveAllPolicyFsm:ResolveAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeResolveAllOperationFsm:ResolveAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeResolveAllStorageFsm:ResolveAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeReleaseAllPolicyFsm:ReleaseAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeReleaseAllOperationFsm:ReleaseAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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:PolicyPolicyScopeReleaseAllStorageFsm:ReleaseAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 config copy to Ops Mgr(FSM-STAGE:sam:dme:MgmtExportPolicyReportConfigCopy:Report)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 config import to Ops Mgr(FSM-STAGE:sam:dme:ExtpolProviderReportConfigImport:Report)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Resolve Policy FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolvePolicyFsm: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]: Resolve Resource FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolveResourceFsm: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]: Resolve VM FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolveVMFsm: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]: Resolve Mgmt Controller FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolveControllerFsm: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]: Deleting registry information from config file(FSM-STAGE:sam:dme:MgmtControllerRegistryConfig:Remove)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Throttle inventory(FSM-STAGE:sam:dme:GmetaHolderInventory:CheckInventoryStatus)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 inventory to UCS-Central(FSM-STAGE:sam:dme:GmetaHolderInventory:ReportFullInventory)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:FAILED|RETRY]: Terminating Cimc Sessions(FSM-STAGE:sam:dme:ComputePhysicalCimcSessionDelete: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]: Resolving controlled type global policies(FSM-STAGE:sam:dme:PolicyControlledTypeOperate:ResolveAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 resource-mgr with VnetEp deletion(FSM-STAGE:sam:dme:FabricVnetEpSyncEpPushVnetEpDeletion:Sync)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the 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 log file export service on local(FSM-STAGE:sam:dme:SysdebugLogExportPolicyConfigure:Local)
Cisco UCS Manager could not set the configurations in the primary Fabric Interconnect for log file transfer to remote 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 log file export service on peer(FSM-STAGE:sam:dme:SysdebugLogExportPolicyConfigure:Peer)
Cisco UCS Manager could not set the configurations in the subordinate Fabric Interconnect (FI) for log file transfer to remote 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: (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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: [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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: (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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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:REMOTE-ERROR]: 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.
[FSM:STAGE:REMOTE-ERROR]: Unconfigure secondary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate: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:REMOTE-ERROR]: Sync power state for server(FSM-STAGE:sam:dme:ComputePhysicalAssociate:SyncPowerState)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Sending update BIOS request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalAssociate:UpdateBiosRequest)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Sending Board Controller update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalAssociate:UpdateBoardCtrlRequest)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Verifying Storage(FC Zones) Connectivity(FSM-STAGE:sam:dme:ComputePhysicalAssociate:VerifyFcZoneConfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Activate adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalAssociate:activateAdaptorNwFwLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Activate adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalAssociate:activateAdaptorNwFwPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Activate CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:activateIBMCFw)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Connect to host agent on server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalAssociate:hagHostOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:hagPnuOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalAssociate:hagPnuOSDisconnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Reset CIMC of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:resetIBMC)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent for association with [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalAssociate:serialDebugPnuOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalAssociate:serialDebugPnuOSDisconnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Update adapter network firmware(FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateAdaptorNwFwLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Update adapter network firmware(FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateAdaptorNwFwPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Update CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:updateIBMCFw)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForAdaptorNwFwUpdateLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForAdaptorNwFwUpdatePeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Wait for CIMC firmware completion on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalAssociate:waitForIBMCFwUpdate)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Waiting for BIOS POST completion from CIMC on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: unprovisioning the bootable device for server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Bring-up pre-boot environment on server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Waiting for system reset on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Configuring BIOS Defaults on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:ConfigBios)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Configuring external user access(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Apply post-disassociation policies to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Configure adapter for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Configure adapter for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Unconfigure host OS connectivity from server adapter(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigHostOSLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Unconfigure host OS connectivity from server adapter(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:NicUnconfigHostOSPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Populate pre-boot catalog to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Identify pre-boot environment agent on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Populate pre-boot environment behavior policy to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Scrub server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Trigger self-test of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Unconfigure server from service profile [assignedToDn] pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:PnuOSUnconfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Pre-boot environment validate server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Power on server for unconfiguration of service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Preparing to check hardware configuration server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Checking hardware configuration server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Shutdown server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:Shutdown)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Disable Sol redirection on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: set up bios token for server [serverId] for Sol redirect(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Configure primary fabric interconnect for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Configure secondary fabric interconnect for pre-boot environment on server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: configuring primary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: configuring secondary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Unconfigure host OS connectivity from server to primary fabric interconnect(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwUnconfigHostOSLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Unconfigure host OS connectivity from server to secondary fabric interconnect(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:SwUnconfigHostOSPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Unconfigure primary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Unconfigure secondary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalDisassociate: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:REMOTE-ERROR]: Unconfiguring BIOS Settings and Boot Order of server [serverId] (service profile [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigBios)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Unconfiguring FlexFlash(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigFlexFlash)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Removing SoL configuration from server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigSoL)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Restore original UUID for server (service profile: [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:UnconfigUuid)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Verifying Storage(FC Zones) Connectivity(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:VerifyFcZoneConfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent on server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:hagPnuOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent for server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:hagPnuOSDisconnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent on server for disassociation with service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalDisassociate:serialDebugPnuOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent for server(FSM-STAGE:sam:dme:ComputePhysicalDisassociate:serialDebugPnuOSDisconnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Configuring power cap of server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowerCap: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:REMOTE-ERROR]: Cleaning up CIMC configuration for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:CleanupCIMC)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Cleaning up local port config for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:CleanupPortConfigLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Cleaning up peer port config for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission:CleanupPortConfigPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Decommissioning server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission: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:REMOTE-ERROR]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission: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:REMOTE-ERROR]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDecommission: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:REMOTE-ERROR]: Soft shutdown of server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftShutdown: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:REMOTE-ERROR]: Hard shutdown of server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardShutdown: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:REMOTE-ERROR]: Power-on server [dn](FSM-STAGE:sam:dme:ComputePhysicalTurnup: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:REMOTE-ERROR]: Power-cycle server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowercycle: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:REMOTE-ERROR]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowercycle: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:REMOTE-ERROR]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalPowercycle: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:REMOTE-ERROR]: Hard-reset server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardreset: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:REMOTE-ERROR]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardreset: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:REMOTE-ERROR]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalHardreset: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:REMOTE-ERROR]: Soft-reset server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftreset: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:REMOTE-ERROR]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftreset: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:REMOTE-ERROR]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalSoftreset: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:REMOTE-ERROR]: Updating fabric A for server [dn](FSM-STAGE:sam:dme:ComputePhysicalSwConnUpd:A)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Updating fabric B for server [dn](FSM-STAGE:sam:dme:ComputePhysicalSwConnUpd:B)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Completing BIOS recovery mode for server [dn], and shutting it down(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Cleanup)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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:REMOTE-ERROR]: Resetting server [dn] power state after BIOS recovery(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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:REMOTE-ERROR]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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:REMOTE-ERROR]: Provisioning a V-Media device with a bootable BIOS image for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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:REMOTE-ERROR]: Provisioning a V-Media device with a bootable BIOS image for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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:REMOTE-ERROR]: Shutting down server [dn] to prepare for BIOS recovery(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery:Shutdown)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Running BIOS recovery on server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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:REMOTE-ERROR]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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:REMOTE-ERROR]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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:REMOTE-ERROR]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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:REMOTE-ERROR]: Unprovisioning the V-Media bootable device for server [dn](FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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:REMOTE-ERROR]: Waiting for completion of BIOS recovery for server [dn] (up to 15 min)(FSM-STAGE:sam:dme:ComputePhysicalBiosRecovery: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:REMOTE-ERROR]: Power on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset: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:REMOTE-ERROR]: Resetting CMOS for server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset: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:REMOTE-ERROR]: Preparing to check hardware configuration server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset: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:REMOTE-ERROR]: Reconfiguring BIOS Settings and Boot Order of server [serverId] for service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:ReconfigBios)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Reconfiguring logical UUID of server [serverId] for service profile [assignedToDn](FSM-STAGE:sam:dme:ComputePhysicalCmosReset:ReconfigUuid)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Checking hardware configuration server [serverId](FSM-STAGE:sam:dme:ComputePhysicalCmosReset: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:REMOTE-ERROR]: Resetting Management Controller on server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetBmc: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:REMOTE-ERROR]: Reset IOM [id] on Fex [chassisId](FSM-STAGE:sam:dme:EquipmentIOCardResetIom: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:REMOTE-ERROR]: Waiting for BIOS POST completion from CIMC on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: power on server [id] for discovery(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: provisioning a bootable device with a bootable pre-boot image for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Configuring connectivity on CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcConfigureConnLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Configuring connectivity on CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:BmcConfigureConnPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: getting inventory of server [id] via CIMC(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: checking CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Shutdown the server [id]; deep discovery completed(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: unprovisioning the bootable device for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: power server [id] on with pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Waiting for system reset on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: setting adapter mode to discovery for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ConfigDiscoveryMode)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: setting adapter mode to NIV for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ConfigNivMode)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: configuring external user access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Invoke post-discovery policies on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: configure primary adapter in server [id] for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: configure secondary adapter in server [id] for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: detect and get mezz cards information from [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: detect and get mezz cards information from [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Populate pre-boot catalog to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Explore connectivity of server [id] in pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSConnStatus)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Explore connectivity of server [id] in pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:PnuOSConnectivity)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Identify pre-boot environment agent on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Perform inventory of server [id] pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Populate pre-boot environment behavior policy to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Scrub server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Trigger self-test of server [id] pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Preparing to check hardware configuration server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Waiting for SMBIOS table from CIMC on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:ReadSmbios)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Checking hardware configuration server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Disable Sol Redirection on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: set up bios token on server [id] for Sol redirect(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: configure primary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: configure secondary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: configuring primary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: configuring secondary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Configuring fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigureConnLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Configuring fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwConfigureConnPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: determine connectivity of server [id] to fabric(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwPnuOSConnectivityLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: determine connectivity of server [id] to fabric(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwPnuOSConnectivityPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Unconfiguring primary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwUnconfigPortNivLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Unconfiguring secondary fabric interconnect access to server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover:SwUnconfigPortNivPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Disconnect pre-boot environment agent for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Connect to pre-boot environment agent on server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: Disconnect pre-boot environment agent for server [id](FSM-STAGE:sam:dme:ComputeRackUnitDiscover: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:REMOTE-ERROR]: wait for connection to be established(FSM-STAGE:sam:dme:ComputeRackUnitDiscover:waitForConnReady)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Analyzing changes impact(FSM-STAGE:sam:dme:LsServerConfigure:AnalyzeImpact)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Applying config to server [pnDn](FSM-STAGE:sam:dme:LsServerConfigure:ApplyConfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving and applying default identifiers locally(FSM-STAGE:sam:dme:LsServerConfigure:ApplyDefaultIdentifiers)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving and applying identifiers locally(FSM-STAGE:sam:dme:LsServerConfigure:ApplyIdentifiers)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving and applying policies(FSM-STAGE:sam:dme:LsServerConfigure:ApplyPolicies)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Applying configuration template [srcTemplName](FSM-STAGE:sam:dme:LsServerConfigure:ApplyTemplate)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: committing storage for service profile(FSM-STAGE:sam:dme:LsServerConfigure:CommitStorage)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Evaluate association with server [pnDn](FSM-STAGE:sam:dme:LsServerConfigure:EvaluateAssociation)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving storage policy(FSM-STAGE:sam:dme:LsServerConfigure:ProvisionStorage)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Computing binding changes(FSM-STAGE:sam:dme:LsServerConfigure:ResolveBootConfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving default identifiers from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveDefaultIdentifiers)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolve distributable from operations manager(FSM-STAGE:sam:dme:LsServerConfigure:ResolveDistributable)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving distributable names from host pack(FSM-STAGE:sam:dme:LsServerConfigure:ResolveDistributableNames)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving identifiers from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveIdentifiers)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolve images from operations manager(FSM-STAGE:sam:dme:LsServerConfigure:ResolveImages)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving various dependent policies from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveNetworkPolicies)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving various template policies from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveNetworkTemplates)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving various policies from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolvePolicies)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving schedule policy from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ResolveSchedule)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving schedule policy from UCS Central(FSM-STAGE:sam:dme:LsServerConfigure:ValidatePolicyOwnership)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Waiting for Association completion on server [pnDn](FSM-STAGE:sam:dme:LsServerConfigure:WaitForAssocCompletion)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Waiting for storage commit to complete(FSM-STAGE:sam:dme:LsServerConfigure:WaitForCommitStorage)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Waiting for ack or maint window(FSM-STAGE:sam:dme:LsServerConfigure:WaitForMaintPermission)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Waiting for maintenance window(FSM-STAGE:sam:dme:LsServerConfigure:WaitForMaintWindow)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: waiting for storage provisioning to complete(FSM-STAGE:sam:dme:LsServerConfigure:WaitForStorageProvision)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Ethernet traffic monitor (SPAN)configuration on [switchId](FSM-STAGE:sam:dme:SwEthMonDeploy:UpdateEthMon)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: FC traffic monitor (SPAN)configuration on [switchId](FSM-STAGE:sam:dme:SwFcMonDeploy:UpdateFcMon)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:FabricSanCloudSwitchMode: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:REMOTE-ERROR]: Fabric interconnect FC mode configuration to primary(FSM-STAGE:sam:dme:FabricSanCloudSwitchMode: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:REMOTE-ERROR]: external mgmt user deployment on server [dn] (profile [assignedToDn])(FSM-STAGE:sam:dme:ComputePhysicalUpdateExtUsers:Deploy)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: create tech-support file from GUI on local(FSM-STAGE:sam:dme:Sysdebugshow tech-supportInitiate: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:REMOTE-ERROR]: delete tech-support file from GUI on local(FSM-STAGE:sam:dme:Sysdebugshow tech-supportDeleteTechSupFile: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:REMOTE-ERROR]: delete tech-support file from GUI on peer(FSM-STAGE:sam:dme:Sysdebugshow tech-supportDeleteTechSupFile: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:REMOTE-ERROR]: Copy the tech-support file to primary for download(FSM-STAGE:sam:dme:Sysdebugshow tech-supportDownload:CopyPrimary)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: copy tech-support file on subordinate switch to tmp directory(FSM-STAGE:sam:dme:Sysdebugshow tech-supportDownload:CopySub)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Delete the tech-support file from primary switch under tmp directory(FSM-STAGE:sam:dme:Sysdebugshow tech-supportDownload:DeletePrimary)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Delete the tech-support file from subordinate under tmp directory(FSM-STAGE:sam:dme:Sysdebugshow tech-supportDownload:DeleteSub)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: waiting for update to complete(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PollUpdateStatusLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: waiting for update to complete(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PollUpdateStatusPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Power off the server(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:PowerOff)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: power on the blade(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor: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:REMOTE-ERROR]: sending update request to Adaptor(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:UpdateRequestLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: sending update request to Adaptor(FSM-STAGE:sam:dme:ComputePhysicalUpdateAdaptor:UpdateRequestPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: activating backup image of Adaptor(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:ActivateLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: activating backup image of Adaptor(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor:ActivatePeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor: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:REMOTE-ERROR]: power on the blade(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor: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:REMOTE-ERROR]: reseting the blade(FSM-STAGE:sam:dme:ComputePhysicalActivateAdaptor: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:REMOTE-ERROR]: applying changes to catalog(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog:ApplyCatalog)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: syncing catalog changes to subordinate(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog: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:REMOTE-ERROR]: evaluating status of activation(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog: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:REMOTE-ERROR]: rescanning image files(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog: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:REMOTE-ERROR]: activating catalog changes(FSM-STAGE:sam:dme:CapabilityCatalogueActivateCatalog: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:REMOTE-ERROR]: applying changes to catalog(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt:ApplyCatalog)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: syncing management extension changes to subordinate(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt: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:REMOTE-ERROR]: evaluating status of activation(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt: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:REMOTE-ERROR]: rescanning image files(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt: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:REMOTE-ERROR]: activating management extension changes(FSM-STAGE:sam:dme:CapabilityMgmtExtensionActivateMgmtExt: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:REMOTE-ERROR]: Copy the license file to subordinate for inventory(FSM-STAGE:sam:dme:LicenseDownloaderDownload: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:REMOTE-ERROR]: deleting temporary files for [fileName] on local(FSM-STAGE:sam:dme:LicenseDownloaderDownload: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:REMOTE-ERROR]: deleting temporary files for [fileName] on subordinate(FSM-STAGE:sam:dme:LicenseDownloaderDownload:DeleteRemote)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: downloading license file [fileName] from [server](FSM-STAGE:sam:dme:LicenseDownloaderDownload: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:REMOTE-ERROR]: validation for license file [fileName] on primary(FSM-STAGE:sam:dme:LicenseDownloaderDownload:ValidateLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: validation for license file [fileName] on subordinate(FSM-STAGE:sam:dme:LicenseDownloaderDownload:ValidateRemote)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Installing license on primary(FSM-STAGE:sam:dme:LicenseFileInstall: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:REMOTE-ERROR]: Installing license on subordinate(FSM-STAGE:sam:dme:LicenseFileInstall: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:REMOTE-ERROR]: Clearing license on primary(FSM-STAGE:sam:dme:LicenseFileClear: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:REMOTE-ERROR]: Clearing license on subordinate(FSM-STAGE:sam:dme:LicenseFileClear: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:REMOTE-ERROR]: Updating on primary(FSM-STAGE:sam:dme:LicenseInstanceUpdateFlexlm: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:REMOTE-ERROR]: Updating on subordinate(FSM-STAGE:sam:dme:LicenseInstanceUpdateFlexlm: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:REMOTE-ERROR]: configuring SoL interface on server [dn](FSM-STAGE:sam:dme:ComputePhysicalConfigSoL: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:REMOTE-ERROR]: removing SoL interface configuration from server [dn](FSM-STAGE:sam:dme:ComputePhysicalUnconfigSoL: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:REMOTE-ERROR]: Shutting down port(FSM-STAGE:sam:dme:PortPIoInCompatSfpPresence:Shutdown)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Execute Diagnostic Interrupt(NMI) for server [dn](FSM-STAGE:sam:dme:ComputePhysicalDiagnosticInterrupt: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:REMOTE-ERROR]: Copy the Core file to primary for download(FSM-STAGE:sam:dme:SysdebugCoreDownload:CopyPrimary)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: copy Core file on subordinate switch to tmp directory(FSM-STAGE:sam:dme:SysdebugCoreDownload:CopySub)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Delete the Core file from primary switch under tmp directory(FSM-STAGE:sam:dme:SysdebugCoreDownload:DeletePrimary)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Delete the Core file from subordinate under tmp directory(FSM-STAGE:sam:dme:SysdebugCoreDownload:DeleteSub)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:EquipmentChassisDynamicReallocation: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:REMOTE-ERROR]: Execute KVM Reset for server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetKvm: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:REMOTE-ERROR]: Configuring connectivity on CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:BmcConfigureConnLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Configuring connectivity on CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:BmcConfigureConnPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Configuring fabric-interconnect connectivity to CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:SwConfigureConnLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Configuring fabric-interconnect connectivity to CIMC(FSM-STAGE:sam:dme:MgmtControllerOnline:SwConfigureConnPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: cleaning host entries on local fabric-interconnect(FSM-STAGE:sam:dme:ComputeRackUnitOffline:CleanupLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: cleaning host entries on peer fabric-interconnect(FSM-STAGE:sam:dme:ComputeRackUnitOffline:CleanupPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Unconfiguring fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitOffline:SwUnconfigureLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Unconfiguring fabric-interconnect connectivity to CIMC of server [id](FSM-STAGE:sam:dme:ComputeRackUnitOffline:SwUnconfigurePeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: setting FI locator led to [adminState](FSM-STAGE:sam:dme:EquipmentLocatorLedSetFiLocatorLed: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:REMOTE-ERROR]: Apply switch configuration(FSM-STAGE:sam:dme:FabricEpMgrConfigure:ApplyConfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Applying physical configuration(FSM-STAGE:sam:dme:FabricEpMgrConfigure:ApplyPhysical)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Validating logical configuration(FSM-STAGE:sam:dme:FabricEpMgrConfigure:ValidateConfiguration)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Waiting on physical change application(FSM-STAGE:sam:dme:FabricEpMgrConfigure:WaitOnPhys)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: VNIC profile alias configuration on local fabric(FSM-STAGE:sam:dme:VnicProfileSetDeployAlias: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:REMOTE-ERROR]: VNIC profile alias configuration on peer fabric(FSM-STAGE:sam:dme:VnicProfileSetDeployAlias: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:REMOTE-ERROR]: Configure physical port mode on fabric interconnect [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:ConfigSwA)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Configure physical port mode on fabric interconnect [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:ConfigSwB)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Performing local port inventory of switch [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:PortInventorySwA)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Performing peer port inventory of switch [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:PortInventorySwB)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Verifying physical transition on fabric interconnect [id](FSM-STAGE:sam:dme:SwPhysConfPhysical:VerifyPhysConfig)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: external VM management cluster role configuration on local fabric(FSM-STAGE:sam:dme:ExtvmmEpClusterRole: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:REMOTE-ERROR]: external VM management cluster role configuration on peer fabric(FSM-STAGE:sam:dme:ExtvmmEpClusterRole: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:REMOTE-ERROR]: set Veth Auto-delete Retention Timer on local fabric(FSM-STAGE:sam:dme:VmLifeCyclePolicyConfig: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:REMOTE-ERROR]: set Veth Auto-delete Retention Timer on peer fabric(FSM-STAGE:sam:dme:VmLifeCyclePolicyConfig: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:REMOTE-ERROR]: Turn beacon lights on/off for [dn] on fabric interconnect [id](FSM-STAGE:sam:dme:EquipmentBeaconLedIlluminate:ExecuteA)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Turn beacon lights on/off for [dn] on fabric interconnect [id](FSM-STAGE:sam:dme:EquipmentBeaconLedIlluminate:ExecuteB)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Configure admin speed for [dn](FSM-STAGE:sam:dme:EtherServerIntFIoConfigSpeed:Configure)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: clearing pending BIOS image update(FSM-STAGE:sam:dme:ComputePhysicalUpdateBIOS:Clear)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: waiting for pending BIOS image update to clear(FSM-STAGE:sam:dme:ComputePhysicalUpdateBIOS:PollClearStatus)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: waiting for BIOS update to complete(FSM-STAGE:sam:dme:ComputePhysicalUpdateBIOS: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:REMOTE-ERROR]: sending BIOS update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalUpdateBIOS: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:REMOTE-ERROR]: activating BIOS image(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS: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:REMOTE-ERROR]: clearing pending BIOS image activate(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:Clear)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: waiting for BIOS activate(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:PollActivateStatus)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: waiting for pending BIOS image activate to clear(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:PollClearStatus)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Power off the server(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:PowerOff)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: power on the server(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS: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:REMOTE-ERROR]: updating BIOS tokens(FSM-STAGE:sam:dme:ComputePhysicalActivateBIOS:UpdateTokens)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Update identities to external identifier manager(FSM-STAGE:sam:dme:IdentIdentRequestUpdateIdent: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:REMOTE-ERROR]: Synchronise ID universe to external identifier manager(FSM-STAGE:sam:dme:IdentMetaSystemSync: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:REMOTE-ERROR]: Check identifier manager availability(FSM-STAGE:sam:dme:IdentMetaSystemSync:Ping)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Execute Reset IPMI configuration for server [dn](FSM-STAGE:sam:dme:ComputePhysicalResetIpmi: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:REMOTE-ERROR]: Activate BIOS image for server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Update blade BIOS image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Waiting for BIOS POST completion from CIMC on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Power off server for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: provisioning a bootable device with a bootable pre-boot image for server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: prepare configuration for preboot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: unprovisioning the bootable device for server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Bring-up pre-boot environment for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Waiting for system reset(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Clearing pending BIOS image update(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Update Host Bus Adapter image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Update LocalDisk firmware image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Update adapter image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Unconfigure adapter of server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Populate pre-boot catalog to server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Configure server with service profile [assignedToDn] pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Identify pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Perform inventory of server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Populate pre-boot environment behavior policy(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Trigger self-test on pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Unload drivers on server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Pre-boot environment validation for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: waiting for BIOS activate(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Waiting for BIOS update to complete(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Waiting for Board Controller update to complete(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: waiting for pending BIOS image update to clear(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Power on server for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Preparing to check hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Checking hardware configuration(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Shutting down server [dn] after firmware upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:Shutdown)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Disable Sol redirection on server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: set up bios token for server for Sol redirect(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Update storage controller image(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Configure primary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Configure secondary fabric interconnect for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: configuring primary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: configuring secondary fabric interconnect access to server(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Unconfigure primary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Unconfigure secondary fabric interconnect for server pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade: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:REMOTE-ERROR]: Sending update BIOS request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:UpdateBiosRequest)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Sending Board Controller update request to CIMC(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:UpdateBoardCtrlRequest)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Activate adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:activateAdaptorNwFwLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Activate adapter network firmware on(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:activateAdaptorNwFwPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Activate CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:activateIBMCFw)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:hagPnuOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:hagPnuOSDisconnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Reset CIMC of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:resetIBMC)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Connect to pre-boot environment agent for Firmware Upgrade(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:serialDebugPnuOSConnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Disconnect pre-boot environment agent(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:serialDebugPnuOSDisconnect)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Update adapter network firmware(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:updateAdaptorNwFwLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Update adapter network firmware(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:updateAdaptorNwFwPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Update CIMC firmware of server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:updateIBMCFw)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:waitForAdaptorNwFwUpdateLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Wait for adapter network firmware update completion(FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:waitForAdaptorNwFwUpdatePeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Wait for CIMC firmware completion on server [serverId](FSM-STAGE:sam:dme:ComputePhysicalFwUpgrade:waitForIBMCFwUpdate)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: deassert reset-bypass(FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset: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:REMOTE-ERROR]: Power-cycle server [dn](FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset:PowerCycle)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Preparing to check hardware configuration server [dn](FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset: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:REMOTE-ERROR]: Checking hardware configuration server [dn](FSM-STAGE:sam:dme:ComputeRackUnitAdapterReset: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:REMOTE-ERROR]: Enabling port(FSM-STAGE:sam:dme:PortPIoInCompatSfpReplaced:EnablePort)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Register FSM Execute(FSM-STAGE:sam:dme:ExtpolEpRegisterFsm: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:REMOTE-ERROR]: Configure cross-domain XML for FLEX client on local fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainConfig: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:REMOTE-ERROR]: Configure cross-domain XML for FLEX client on peer fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainConfig: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:REMOTE-ERROR]: Remove cross-domain XML for FLEX client on local fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainDelete: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:REMOTE-ERROR]: Remove cross-domain XML for FLEX client on peer fabric-interconnect(FSM-STAGE:sam:dme:ExtpolRegistryCrossDomainDelete: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:REMOTE-ERROR]: Mount nfs [remoteDir] from server [server] on local switch(FSM-STAGE:sam:dme:NfsMountInstMount:MountLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Mount nfs [remoteDir] from NFS server [server] on peer switch(FSM-STAGE:sam:dme:NfsMountInstMount:MountPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Register client with Ops Mgr(FSM-STAGE:sam:dme:NfsMountInstMount:RegisterClient)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Verify client registration with Ops Mgr(FSM-STAGE:sam:dme:NfsMountInstMount:VerifyRegistration)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Unmount nfs [remoteDir] from server [server](FSM-STAGE:sam:dme:NfsMountInstUnmount:UnmountLocal)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Unmount nfs [remoteDir] from server [server](FSM-STAGE:sam:dme:NfsMountInstUnmount:UnmountPeer)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Report mount suspend success to operations manager(FSM-STAGE:sam:dme:NfsMountDefReportNfsMountSuspend:Report)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Synchronise requestors with storage broker(FSM-STAGE:sam:dme:StorageSystemSync: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:REMOTE-ERROR]: Activating IOMs(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateIOM)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Activating Local Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateLocalFI)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Activating Peer Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateRemoteFI)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Activating UCSM(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ActivateUCSM)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Waiting for Activation to complete on IOMs(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfIOM)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Waiting for Activation to complete on Local Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfLocalFI)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Waiting for Activation to complete on Peer Fabric Interconnect(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfRemoteFI)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Waiting for UCSM Activate to complete(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollActivateOfUCSM)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Waiting for update of IOMs to complete(FSM-STAGE:sam:dme:FirmwareSystemDeploy:PollUpdateOfIOM)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolve distributable from operations manager(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ResolveDistributable)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving distributable name from infra pack(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ResolveDistributableNames)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolve images from operations manager(FSM-STAGE:sam:dme:FirmwareSystemDeploy:ResolveImages)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Updating back-up image of IOMs(FSM-STAGE:sam:dme:FirmwareSystemDeploy:UpdateIOM)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Waiting for Deploy to begin(FSM-STAGE:sam:dme:FirmwareSystemDeploy:WaitForDeploy)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Waiting for User Acknowledgement To Start Primary Fabric Interconnect Activation(FSM-STAGE:sam:dme:FirmwareSystemDeploy:WaitForUserAck)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Activating Catalog(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ActivateCatalog)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolve distributable from operations manager(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ResolveDistributable)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving distributable name(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ResolveDistributableNames)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolve images from operations manager(FSM-STAGE:sam:dme:FirmwareSystemApplyCatalogPack:ResolveImages)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolving scrub policy from UCS Central(FSM-STAGE:sam:dme:ComputeServerDiscPolicyResolveScrubPolicy:Resolve)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: fc zone configuration on [switchId](FSM-STAGE:sam:dme:SwFcSanBorderActivateZoneSet:UpdateZones)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Cleaning certificates, channels and policy meta data(FSM-STAGE:sam:dme:ExtpolEpRepairCert:cleanOldData)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Provisioning latest certificates(FSM-STAGE:sam:dme:ExtpolEpRepairCert:request)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: unregister from old UCS Central, if needed(FSM-STAGE:sam:dme:ExtpolEpRepairCert:unregister)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: checking that cert was provisioned(FSM-STAGE:sam:dme:ExtpolEpRepairCert:verify)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: verifying GUID of UCS Central(FSM-STAGE:sam:dme:ExtpolEpRepairCert:verifyGuid)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyControlEpOperate:Resolve)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleasePolicyFsm:Release)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseOperationFsm:Release)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseStorageFsm:Release)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveManyPolicyFsm:ResolveMany)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveManyOperationFsm:ResolveMany)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveManyStorageFsm:ResolveMany)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseManyPolicyFsm:ReleaseMany)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseManyOperationFsm:ReleaseMany)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseManyStorageFsm:ReleaseMany)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveAllPolicyFsm:ResolveAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveAllOperationFsm:ResolveAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeResolveAllStorageFsm:ResolveAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseAllPolicyFsm:ReleaseAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseAllOperationFsm:ReleaseAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: (FSM-STAGE:sam:dme:PolicyPolicyScopeReleaseAllStorageFsm:ReleaseAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Report config copy to Ops Mgr(FSM-STAGE:sam:dme:MgmtExportPolicyReportConfigCopy:Report)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Report config import to Ops Mgr(FSM-STAGE:sam:dme:ExtpolProviderReportConfigImport:Report)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Resolve Policy FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolvePolicyFsm: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:REMOTE-ERROR]: Resolve Resource FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolveResourceFsm: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:REMOTE-ERROR]: Resolve VM FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolveVMFsm: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:REMOTE-ERROR]: Resolve Mgmt Controller FSM Execute(FSM-STAGE:sam:dme:ObserveObservedResolveControllerFsm: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:REMOTE-ERROR]: Deleting registry information from config file(FSM-STAGE:sam:dme:MgmtControllerRegistryConfig:Remove)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Throttle inventory(FSM-STAGE:sam:dme:GmetaHolderInventory:CheckInventoryStatus)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Report inventory to UCS-Central(FSM-STAGE:sam:dme:GmetaHolderInventory:ReportFullInventory)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Terminating Cimc Sessions(FSM-STAGE:sam:dme:ComputePhysicalCimcSessionDelete: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:REMOTE-ERROR]: Resolving controlled type global policies(FSM-STAGE:sam:dme:PolicyControlledTypeOperate:ResolveAll)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: Update resource-mgr with VnetEp deletion(FSM-STAGE:sam:dme:FabricVnetEpSyncEpPushVnetEpDeletion:Sync)
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:STAGE:REMOTE-ERROR]: configuring log file export service on local(FSM-STAGE:sam:dme:SysdebugLogExportPolicyConfigure:Local)
Cisco UCS Manager could not set the configurations in the primary Fabric Interconnect for log file transfer to remote 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:REMOTE-ERROR]: configuring log file export service on peer(FSM-STAGE:sam:dme:SysdebugLogExportPolicyConfigure:Peer)
Cisco UCS Manager could not set the configurations in the subordinate Fabric Interconnect (FI) for log file transfer to remote 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:FAILED]: sam:dme:EquipmentIOCardFePresence
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EquipmentIOCardFeConn
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EquipmentChassisRemoveChassis
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EquipmentLocatorLedSetLocatorLed
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtControllerExtMgmtIfConfig
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:FabricComputeSlotEpIdentify
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputeBladeDiscover
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EquipmentChassisPsuPolicyConfig
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:AdaptorHostFcIfResetFcPersBinding
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputeBladeDiag
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:FabricLanCloudSwitchMode
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:VnicProfileSetDeploy
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:CommSvcEpUpdateSvcEp
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:CommSvcEpRestartWebSvc
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:AaaEpUpdateEp
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:AaaRealmUpdateRealm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:AaaUserEpUpdateUserEp
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PkiEpUpdateEp
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SysfileMutationSingle
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SysfileMutationGlobal
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SysdebugManualCoreFileExportTargetExport
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SysdebugAutoCoreFileExportTargetConfigure
Cisco UCS Manager could not set the configurations for auto core transfer to remote TFTP server.
Check the error for the failed FSM stage and take the recommended action for that stage.
[FSM:FAILED]: sam:dme:SysdebugLogControlEpLogControlPersist
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SwAccessDomainDeploy
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SwEthLanBorderDeploy
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SwFcSanBorderDeploy
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SwUtilityDomainDeploy
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SyntheticFsObjCreate
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:FirmwareDownloaderDownload
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:FirmwareImageDelete
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtControllerUpdateSwitch
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtControllerUpdateIOM
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtControllerActivateIOM
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtControllerUpdateBMC
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtControllerActivateBMC
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:CallhomeEpConfigCallhome
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtIfSwMgmtOobIfConfig
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtIfSwMgmtInbandIfConfig
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtIfVirtualIfConfig
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtIfEnableVip
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtIfDisableVip
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtIfEnableHA
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtBackupBackup
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtImporterImport
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:StatsCollectionPolicyUpdateEp
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:QosclassDefinitionConfigGlobalQoS
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EpqosDefinitionDeploy
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EpqosDefinitionDelTaskRemove
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EquipmentIOCardResetCmc
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtControllerUpdateUCSManager
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtControllerSysConfig
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:AdaptorExtEthIfPathReset
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:AdaptorHostEthIfCircuitReset
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:AdaptorHostFcIfCircuitReset
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ExtvmmProviderConfig
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ExtvmmKeyStoreCertInstall
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ExtvmmSwitchDelTaskRemoveProvider
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ExtvmmMasterExtKeyConfig
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:CapabilityUpdaterUpdater
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:FirmwareDistributableDelete
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputeBladeUpdateBoardController
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:CapabilityCatalogueDeployCatalogue
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EquipmentFexRemoveFex
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EquipmentLocatorLedSetFeLocatorLed
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EquipmentChassisPowerCap
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EquipmentIOCardMuxOffline
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalAssociate
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalDisassociate
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalPowerCap
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalDecommission
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalSoftShutdown
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalHardShutdown
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalTurnup
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalPowercycle
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalHardreset
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalSoftreset
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalSwConnUpd
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalBiosRecovery
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalCmosReset
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalResetBmc
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EquipmentIOCardResetIom
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputeRackUnitDiscover
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:LsServerConfigure
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SwEthMonDeploy
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SwFcMonDeploy
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:FabricSanCloudSwitchMode
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalUpdateExtUsers
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:Sysdebugshow tech-supportInitiate
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:Sysdebugshow tech-supportDeleteTechSupFile
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:Sysdebugshow tech-supportDownload
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalUpdateAdaptor
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalActivateAdaptor
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:CapabilityCatalogueActivateCatalog
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:CapabilityMgmtExtensionActivateMgmtExt
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:LicenseDownloaderDownload
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:LicenseFileInstall
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:LicenseFileClear
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:LicenseInstanceUpdateFlexlm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalConfigSoL
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalUnconfigSoL
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PortPIoInCompatSfpPresence
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalDiagnosticInterrupt
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SysdebugCoreDownload
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EquipmentChassisDynamicReallocation
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalResetKvm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtControllerOnline
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputeRackUnitOffline
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EquipmentLocatorLedSetFiLocatorLed
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:FabricEpMgrConfigure
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:VnicProfileSetDeployAlias
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SwPhysConfPhysical
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ExtvmmEpClusterRole
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:VmLifeCyclePolicyConfig
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EquipmentBeaconLedIlluminate
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:EtherServerIntFIoConfigSpeed
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalUpdateBIOS
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalActivateBIOS
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:IdentIdentRequestUpdateIdent
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:IdentMetaSystemSync
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalResetIpmi
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalFwUpgrade
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputeRackUnitAdapterReset
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PortPIoInCompatSfpReplaced
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ExtpolEpRegisterFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ExtpolRegistryCrossDomainConfig
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ExtpolRegistryCrossDomainDelete
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:NfsMountInstMount
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:NfsMountInstUnmount
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:NfsMountDefReportNfsMountSuspend
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:StorageSystemSync
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:FirmwareSystemDeploy
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:FirmwareSystemApplyCatalogPack
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputeServerDiscPolicyResolveScrubPolicy
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SwFcSanBorderActivateZoneSet
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ExtpolEpRepairCert
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyControlEpOperate
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleasePolicyFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseOperationFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseStorageFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeResolveManyPolicyFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeResolveManyOperationFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeResolveManyStorageFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseManyPolicyFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseManyOperationFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseManyStorageFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeResolveAllPolicyFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeResolveAllOperationFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeResolveAllStorageFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseAllPolicyFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseAllOperationFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyPolicyScopeReleaseAllStorageFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtExportPolicyReportConfigCopy
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ExtpolProviderReportConfigImport
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ObserveObservedResolvePolicyFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ObserveObservedResolveResourceFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ObserveObservedResolveVMFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ObserveObservedResolveControllerFsm
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:MgmtControllerRegistryConfig
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:GmetaHolderInventory
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:ComputePhysicalCimcSessionDelete
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:PolicyControlledTypeOperate
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:FabricVnetEpSyncEpPushVnetEpDeletion
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.
[FSM:FAILED]: sam:dme:SysdebugLogExportPolicyConfigure
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. Also refer to the Cisco UCS Manager Release Notes and the Cisco UCS Troubleshooting Guide. If you cannot resolve the issue, create a show tech-support file and contact Cisco TAC.