PDF(1.3 MB) View with Adobe Reader on a variety of devices
ePub(1.4 MB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(805.6 KB) View on Kindle device or Kindle app on multiple devices
Updated:May 27, 2020
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 document describes on steps to troubleshoot an issue where blade fails to discover due to server power state-MC Error.
Cisco recommends that you have a working knowledge of these topics:
Cisco Unified Computing System (UCS)
Cisco Fabric Interconnect (FI)
The information in this document is based on these software and hardware versions:
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Blade firmware upgrade, the server went down after uptime policy reboot.
Some power event in the data center.
Above could be the possible trigger of the issue.
This error message occurs upon a reboot or during discovery.
"Unable to change the blade power state"
UCSM reports this alert for a blade that fails to get powered on
Blade rebooted as a part of firmware upgrade or any other maintenance fails to discover /turn-up with below message in FSM:
“Unable to change server power state-MC Error(-20): Management controller cannot or failed in processing request(sam:dme:ComputePhysicalTurnup:Execute)”
power-on-fail.hist inside the tmp/techsupport_pidXXXX/CIMCX_TechSupport-nvram.tar.gz)
If the above does not help and as next step, collect UCSM and Chassis techsupport log bundle.
It helps to further investigate the issue.
With the previously mentioned symptoms, Try these steps to recover the issue.
Step 1: Verify that blade FSM Status is “Failed” with description “state-MC Error(-20)”.
Navigate to Equipment > Chassis X > Server Y > FSM
Step 2: Note down impacted blade Serial number and Decommission the Blade.
<<< IMP: Note down Problem blade serial number from General tab before decommissioning it. It will required at later stage in Step-4 >>>
Navigate to Equipment > Chassis X > Server Y > General > Server Maintenance > Decommission > Ok.
Step 3. FI-A/B# reset slot x/y
For Example #Chassis2-Server 1 is impacted.
FI-A# reset slot 2/1
Wait for 30-40 seconds after running the above command
Step-4: Recommission the Blade that has been decommissioned.
Navigate to Equipment > Decommissioned > Servers > Look for the server we decommissioned (Find correct blade with Serial number Noted in Step-2 before decommissioning) > Check Recommission Tick box against correct Blade (Validate with Serial number) > Save Changes.
Step-5: Resolve Slot, if observed.
Navigate to Equipment > Chassis X > Server Y.
If you get “Resolve Slot Issue” pop-up for the blade that you recommissioned, then verify its serial number and click “here” to accept the server in slot.
Blade discovery should start now.
Wait till Server Discovery gets completed. Monitor the progress in Server FSM tab.
Step 6. If step one to five don’t help and FSM again fails, then decommission the blade and try to RESEAT it physically.
If still server is unable to discover reach out to Cisco TAC if this is a hardware issue.
NOTE: If you have B200 M4 blade and notice failure scenario #2 , please refer following bug and Contact TAC
CSCuv90289 B200 M4 fails to power on due to POWER_SYS_FLT