Cisco UCS-IOM-2208XP auto upgrade keep rebooting and looping the same

[Markus5849]

I have one IO module 2208XP connected to chassis 5108. It is connected to a FI 6400 series with 4.2(1i) firmware. When it was connected, the IO module is showing Identifying, and then Auto Upgrade, after that the IO module is rebooted. When it was up, it did the same thing which it identify, auto upgrade and reboot again and again. Any advise?

[johan.lalouette]

I have exactly the same issue on UCS-IOM-2204XP connected to chassis 5108 with FI 6454 4.2.1i.
I have already change 1 IO module and the entire chassis. The problem remains and no solutions from cisco TAC yet.

[Markus5849]

I resolved the issue by downgrading the firmware.

[ncormackepic]

Which version did you downgrade to?

Just the FIs needed downgrading?

I'm encountering exact same issue, however my FIs came with 4.2.3b.

[Riaan van Niekerk]

We experienced IOM auto-upgrade issues when upgrading from FI-6248 to FI-6454 because the IOM images were missing from the FI. When we staged the new FIs to upgrade their firmware to the same level as the FI-6248, before swapping them out, we upgraded the standalone FIs with UCS Central. We suspect that because the FIs were not connected to an IOM, it did not leave the IOM bundles on the FI. You can check if the IOM image is on the FI:

• UCSM -> Equipment -> Firmware Management -> Images -> (select the IOM, there are a couple) -> 
• The name of the image indicates for which IOM model it is, e.g. ucs-2200-6400.4.2.1i.bin.
• Check that field "Present on Fabric" says A, B (for a clustered domain) or A (for a stand-alone FI). If it says "Unknown", it means there is an issue with that image.

We were able to fix the missing IOM image issue:

1. For our staged FIs that were not in use, we did a force upgrade to the version that the FI was running, but were experiencing the issue with. It won't restart manager or the FI since they are already running the correct code version. It should put the IOM images in the correct locations. 
2. If that does not fix the reboot loop, or "Present on Fabric" is still Unknown, Cisco TAC have a command (root access required) to copy the IOM images from bootflash to the correct location on the FI.

Not sure if your issue is similar, but maybe some of this is useful. We had LOTS of IOM firmware issues when upgrading our FIs on the 4.2 series firmware, possibly due to using Central. This is one of the many reasons why we stopped upgrading our domains via Central.