UCS Firmware update to Chassis

[ITDEPT0014]

We are preparing to upgrade our Chassis to 4.1.3m after a previous update to the fabric interconnects and currently have two critical errors:

1. FSM:FAILED]: Update identities to external identifier manager(FSM:sam:dme:IdentIdentRequestUpdateIdent). Remote-Invocation-Error: FSM Retries Exhausted

2. [FSM:FAILED]: Sending UCS Inventory to UCS Central.(FSM:sam:dme:GmetaHolderInventory). Remote-Invocation-Error: FSM Retries Exhausted

The 2nd one I believe is not an issue as we do not have a UCS Central system, and when checking Cisco for the first error, it categorizes the error as a warning and not critical.

Can this be due to the Fabrics being on the newer version while the Chassis and Blades are still on version 3.2(3h)?

My question: Is it safe to proceed with the Chassis upgrade, or do we need to address this?

[Wes Austin]

Both of these errors are related to UCS Central. If you are not using it, I would recommend going to the Admin tab in UCSM and removing/unregistering from UCS central and it will clear the faults. If you dont want to do this, you can proceed with the chassis upgrade anyway and it will not impact anything. This is not related to the FI and Chassis being on different versions. The errors are basically saying "I cant talk to UCS Central that you have registered me to"

NOTE: Please make sure you are not using UCS Central before you unregister. If you unregister and there are policies, profiles, etc that are being manged from UCS central it could cause issues and re-registering will not automatically resolve.

[ITDEPT0014]

Thank you Wess.

People that set up system no longer around, and we are not sure if they had Central or tried to setup by accident with out it and attached is what is currently setup.  Since everything appears to be set to Local on this screen, is it safe to Select the "Unregister From UCS Central" option or is there something else that needs to be done before selecting that?

[Wes Austin · Accepted solution]

It should be safe if everything is set to local. You can also spot check your profiles, pools, templates, etc and make sure nothing is using anything "global" or with a green dot next to it. To be extra cautious, make sure your cleanup mode is set to localize global.

Localize Global—When a Cisco UCS domain is unregistered, all global policies in the Cisco UCS domain will be localized to Cisco UCS Manager. The policies remain in the Cisco UCS domain, policy ownership is now local to Cisco UCS Manager, and Cisco UCS Manager admin users can make changes.

https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-manager/GUI-User-Guides/Server-Mgmt/3-2/b_Cisco_UCS_Manager_Server_Mgmt_Guide_3_2.pdf 

[ITDEPT0014]

Thank you Wes, that worked.