Upgraded and now lost connection

[bcav311]

I upgraded the FI and USCM and now i'm not able to access anything. My FI are pinging and i'm able to access them but i'm only given three options in the CLI. I can no longer access the USCM from the web. Is there a way i can load my back up that i took before the upgrade without access to the USCM?

This is my first go at anything dealing with a UCS so anything would help. Thanks

UCS 5108

m2 Blades

I upgraded the UCSM to 3.2(3I)

[Kirk J]

Want to make sure you aren't using the older deprecated 6100 series FIs, which aren't supported in 3.x

Thanks,

Kirk...

[bcav311]

yes they are 6100's and after upgrading realized that they are not compatible.  i'm trying now to go back and put the old versions in place but having trouble now connecting.

[Kirk J]

Download the 2.28m version from https://software.cisco.com/download/home/283612660/type/283655658/release/2.2(8m)

Use a recent version of 7-zip to extract the embedded image until you see a 'isan' folder (you'll have to extract several layers of embedded files this way to get to the isan folder.  The isan\plugin_img folder will contain the ucs-manager-k9.2.2.8m.bin, ucs-6100-k9-system.5.2.3.N2.2.28m.bin, ucs-6100-k9-kickstart.5.2.3.N2.2.28m.bin files you need to rebuild the FI.

ucs-k9-bundle-infra.2.2.8m.A\ucs-k9-bundle-infra.2.2.8m\isan\plugin_img 

Now following the steps outlined in https://community.cisco.com/t5/data-center-documents/how-to-recover-from-a-software-failure-on-the-6120-fabric/ta-p/3121751 to rebuild the FIs.

If your current FI happens to still have the old copies of kickstart, system, and ucs manager files for your original 2.2 version, then you can boot to those using the local path instead of the tftp path for the newer ones.

You will need a tftp server to put those files on, in order to copy them over after you have broken into the boot loader.

You happen to have a UCSM backup of your logical or system configs?

Thanks,

Kirk...

[bcav311]

So we are now able to get into the UCSM. It is running version 3.2. I tried to upgrade the FI so that it is the same version as the B but it failed. A is running 4.2(I)nI(1.43q) and B is running 5.2(3)n2(2.28f). I tried to upgrade A but it still fails and if we restart it, it will not come back with the startup version it basically crashes and we have to go manually choose the boot files. The only boot files we are showing are that 4.2 version, none of the other versions.

I took a full state backup over everything before changing anything as well.