We've had our UCS B Series chassis up for almost 2 years now and it's time to update the firmware from 2.0(3b) to the latest. This is uncharted territory so I wanted to get some feedback from those who have already updated their firmware. Our servers are B230 M2s and B200 M3s all deployed with the same Service Profile Template. We have 2 fabric interconnects. All the servers are part of a VMware cluster.
What I'm unclear on is the steps (which is pretty much all there is) and I'm hoping someone can confirm that I've got this in the right order.
Step 1. Download the UCS Infrastructure Software Bundle from the Cisco support downloads. Also Download the Cisco UCS B-Series Blade Server Software Bundle. I would use the latest of both.
Step 2. Via UCS Manager, download firmware under the Firmware Management Tab. Here I have the option to download locally or to a remote server and then retrieve via some protocol like TFTP. Given the option, a local download seems easier.
Step 3. Install the downloaded firmware to the fabric interconnects. Activate the firmware only on the subordinate FI.
Step 4. Upgrade the Infrastructure firmware. Because our UCS is at 2.0 we can't use the Firmware Auto Install feature. First we update CIMC and IOMs. Here I would go into each server individually and hit the General Tab and then Update Firmware. Then Activate firmware. Will this restart the server? Is the firmware for the adapters uploaded to the FI in step 2?
Step 5. Activate the Cisco UCS Manager Software via the Equipment node's Firmware management tab. Change the verions to the most recent.
Step 6. Activate firmware for IOM. Same as UCS Manager
Step 7. Failover the FI to the upgraded subordinate FI. Upgrade the firmware on the non-updated FI.
Step 8. Update the host firmware package. Under Server-Policies we only have one Host Firmware Package defined. Within that the only thing checked is under the BIOS tab - one option is checked for each of the two models of UCS blade servers we have. Where does the firmware for this come from? Was it included in the UCS Infrastructure Software Bundle?
And those are the steps as I understand them. I'd really appreciate any corrections or additions. Thanks for the help.
Thanks wdey. I think I understand. Upgrading UCS Manager to 2.2.1c will give me the autoinstall options for everything that follows (infrastructure, adapters, CIMCs, IOMs, servers)?
Under this autoinstall scenario do I need to update the fabric interconnects one at a time or does the autoinstall update and failover as necessary?
Thanks for that last link. It was very useful. I see now the breakdown of what the infrastructure software bundle includes and the server software bundle contents. Are both of these uploaded to the FIs in my step 1 step 2 above?
>>>>> Upgrading UCS Manager to 2.2.1c will give me the autoinstall options for everything that follows (infrastructure, adapters, CIMCs, IOMs, servers)?
Yes ! Infrastructure = UCSM (which you upgrade manually first), IOM, and FI
Server is actually done with Host Firmware Package, therefore create one eg. name it "HFP", and include it in your service profiles. Then with Autoinstall server, you refer to this "HFP", which will then be updated to e.g. 2.2.1c, and CIMC, BIOS, Adaptor,.... is updated (which requires a server reboot); therefore check, that you have a maintenance policy with ACK in place !!
>>>>>> Under this autoinstall scenario do I need to update the fabric interconnects one at a time or does the autoinstall update and failover as necessary?
This is all done automatically ! starting with IOM and then slave FI; then the upgrade stops and waits for a ACK, after which the master FI is done; before the ACK you should check, that all your uplinks.... are ok
>>>>> Are both of these uploaded to the FIs in my step 1 step 2 above?
PS. During the upgrade, you might see tons of error messages, which you can very likely forget, and clear when the upgrade is done
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...