01-14-2014 07:06 AM - edited 03-01-2019 11:27 AM
Hi expers,
Recently we purchasing a lot of B200 M3. After we boot up server. UCSM show all the CPU and Memory error "F0502" as image in the below. Have any one also encounter same issue? And how to fix it?
Best regards,
Meng-Yuan Hsieh (Nick)
Solved! Go to Solution.
01-14-2014 10:10 AM
Hello Meng,
Just update your UCS to use your new hardware.
■The B200 M3 with E5-2600 CPUs requires UCSM 2.0.2(q) or later
■The B200 M3 with E5-2600 v2 CPUs requires UCSM 2.1.3 or later
https://www.cisco.com/en/US/prod/collateral/ps10265/ps10280/B200M3_SpecSheet.pdf
Regards,
Richard
01-15-2014 03:43 AM
Hi,
Both methods will solve the issue. Is always recommended keep your system updaded, but if you don't have a window maintenance to do that now you can just update the catalog.
Regards,
Richard
01-14-2014 10:10 AM
Hello Meng,
Just update your UCS to use your new hardware.
■The B200 M3 with E5-2600 CPUs requires UCSM 2.0.2(q) or later
■The B200 M3 with E5-2600 v2 CPUs requires UCSM 2.1.3 or later
https://www.cisco.com/en/US/prod/collateral/ps10265/ps10280/B200M3_SpecSheet.pdf
Regards,
Richard
01-14-2014 10:28 AM
Meng,
Good input from Richard above, if you are already running one of those versions or later, you may also try to update the Capability Catalog: https://supportforums.cisco.com/docs/DOC-11820 << the process is not disruptive and takes about 0.005 seconds . Try the latest Cap Catalog version from the same chain.
Rate ALL helpful answers.
-Kenny
01-14-2014 07:23 PM
Hi Richard and Kenny,
I have the other case is running on the version 2.1(1a). The B200 M3 with E5-2600 cpus. For this case which workaround should I use? Upgrade firmware or update Capability Catalog?
Best regards,
Meng-Yuan Hsieh (Nick)
01-15-2014 03:43 AM
Hi,
Both methods will solve the issue. Is always recommended keep your system updaded, but if you don't have a window maintenance to do that now you can just update the catalog.
Regards,
Richard
01-15-2014 07:30 AM
Hi Richard,
I used our lab update Capability Catalog from 2.1(1a) to 2.1(3c). Then decommission and re-decommission server. But event still did not clear. Until I reboot FI. Then event been cleared. For this workaround is that correct?
Best regards,
Meng-Yuan Hsieh (Nick)
01-15-2014 09:28 AM
Hi,
According with documentation the restart of any component is not necessary (I'm not saying about re-discovery process).
01-15-2014 10:37 AM
Hi Richard,
I used GUI update catalog. And the active new catalog. But the even still there. So I try to restart each component.
Sent from Cisco Technical Support iPhone App
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: