With the December release of Cisco ACI v1.2 (codename Brazos), a plethora of a new capabilities were added. The first on my list to cover is the ‘Shared L3Out’; the ability to use one L3Out to provide external network connectivity across numerous private networks/VRFs. Sharing a single L3Out helps resolve some of the border leaf scale limitations in prior versions, as well as sidestep the complexity involved in configuring numerous, individual VRF-lite adjacencies as was previously required.
In this write-up, I’m going to cover the upgrade process for a typical Cisco ACI fabric. Overall, the ACI fabric upgrade process is fairly straightforward, and with sufficient redundancy of connected devices can be performed without any adverse impact to production traffic.
If you’ve unsuccessfully tried several times to upload files to your ACI fabric on version 1.1(4e), you may be encountering this issue:
From the APIC v1.2(1i) release notes (available here).
“Due to bug CSCux40954, which was resolved in this release, the Cisco APIC firmware process using the Upload button from the GUI does not work. The upload appears to complete successfully, but the firmware is not updated in the repository. You must instead download the image using SCP or HTTP from a server to the APIC.”