11-20-2012 01:40 PM - edited 03-01-2019 10:44 AM
I've got two B230 M2 blades that are stuck at the same spot in the 2.1 upgrade process. Both are at 47%, with this text in the FSM tab:
Update storage controller image(FSM-STAGE:sam:dme:ComputePhysicalAssociate:StorageCtlrImgUpdate)"
dn="sys/chassis-1/blade-2/fsm/stage-AssociateStorageCtlrImgUpdate"
Been about 1 hour, no movement. These blades have no local storage, and I think that may be part of the problem. When I KVM into the hosts, they are both stuck right after loading eth0.
UCSM and the rest of the infrastructure bundle was upgraded to 2.1 without any problems.
Anyone else run into this issue and solve it?
mike
11-20-2012 08:26 PM
Hello Mike,
We need more information to better troubleshoot this issue.
Please open a TAC SR with UCSM and Chassis tech support logs.
Padma
11-21-2012 08:17 AM
Ok. Sorted it out. I had to re-acknowledge both blades and let the discovery process complete. This is mentioned in the 2.1 release notes for C-series hardware, but not B-series. Anyone else out that that runs into this problem might want to give this a shot.
mike
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: