A SaaS platform updated its servers with a host firmware package, but each chassis IOM is still on the old firmware and the fabric interconnect reports a mismatch. Which update brings the IOM in line with the interconnect?
Select an answer to reveal the explanation.
Short Explanation
You updated the desks inside the offices and left the floor's telephone closet on the old system. You bring the IOM forward with the infrastructure firmware that belongs with the fabric interconnect, not with another pass of the host package. A pin group chooses an uplink path, and it does not install firmware on the IOM.
Full Explanation
UCS splits server firmware from infrastructure firmware. The host firmware package covers components on the server, such as BIOS, adapters, and controllers. The IOM in the chassis is infrastructure, and its firmware is updated with the fabric interconnect infrastructure so the IOM code matches the interconnect it talks to. Another host firmware package, even if someone aims it at the chassis, does not boot the IOM. That is why this SaaS platform still sees a mismatch after the servers were updated. A scrub policy clears server state when a profile is removed. It does not load an IOM image on disassociation. A LAN pin group binds vNIC traffic to an uplink. It has no role in which firmware the IOM runs, and pinning cannot make an old IOM pretend to be the newer interconnect image. Caveat: the infrastructure update has its own maintenance window and can disrupt the chassis path, so it should be sequenced across the fabric interconnect pair rather than treated as a host reboot. Operational check: install the infrastructure image that matches the interconnect, then confirm the IOM reports the compatible firmware and the mismatch clears.