09-27-2024 05:29 AM
Hi all,
I am looking for a site, or compatibility matrix between APIC release and switches version. When I upgrade the APIC release have I always to also upgrade the switches version (example version 5.2(5) requires 15.2(5) only?)
I have been asked to update only the APIC cluster, but I wonder if this is wrong.
Thanks
Solved! Go to Solution.
09-27-2024 06:32 AM
The general guidelines are as follows:
Regards,
Robert
09-27-2024 05:35 AM
Hello @irenof
Is it what you looking for ?
https://www.cisco.com/c/en/us/td/docs/Website/datacenter/acihwsupport/index.html
09-27-2024 06:32 AM
The general guidelines are as follows:
Regards,
Robert
09-28-2024 12:38 AM
Hi @Robert Burns, thank you for the detailed answer. When you refer to Switches runninx 4x, do you you refer to 14.x NX-OX ACI version?
My actual situation is:
APIC 4.2(4i) and Switches 14.2(4i)
According to your answer it is safe to upgrade only the APIC to 4.2(7l)?
Thanks
09-27-2024 01:43 PM
Hi @irenof ,
Mostly I agree with @Robert Burns 's reply, but there is at least one case where I know upgrading the APICs before the switches can create a profound security issue.
I really don't know why this isn't in the release notes, but with the following condiditons:
THEN YOU HAVE A PROBLEM UPGRADING THE APICS WITHOUT THE SWICH UPGRADE
This is what happened in my case, upgrading from 4.x to 5.0 where Cisco decided that any filter that had port 22 in its definition would be changed to SSH - it goes like this:
When the APIC running v4 pushes the contact to the switch running v14, it uses the numeric 22 in the filter, which the switch software interprets as a filter for port 22
When the APIC running v5 pushes the contact to the switch running v14, it uses the textual SSH in the filter, which the switch software interprets as a filter for any port
So any contracts which previously allowed only port 22 for attached devices now suddenly have ALL TRAFFIC allowed.
I had thought I'd written about this on this forum but neither the search on this forum or Google could find it. But I did do a short video (https://www.youtube.com/watch?v=KCKj-eGBR5Y), wrote a blog post about it (https://rednectar.net/2020/09/05/aci-version-mismatch-alert-dont-use-v5-on-apic-and-v14-on-leaves/) and posted on Facebook (https://www.facebook.com/groups/1028679983855301/permalink/3549697478420193/) where @dpita pointed out the problem to me.
I have no idea if or when Cisco will repeat this with say port 3306 and turn it into MySQL for instance - but if they do, I expect the same problem will occur.
09-28-2024 12:42 AM
Hi @RedNectar, this is what I am afraid of. I have not so deep experience in ACI, so I am not confident in upgrading API without also upgrade the switches.
My options, without also upgrade the switches are:
1) from APIC 4.2(4i) and NX-OS ACI 14.2(4i) ----> APIC 4.2(7) and NX-OS ACI 14.2(4i)
2) from APIC 4.2(4i) and NX-OS ACI 14.2(4i) ----> APIC 5.2(5) and NX-OS ACI 14.2(4i)
Are both options possible?
According to your answer I should be very careful and do an assestment on the conf and policies befor upgrade to 5.2(5)...
Thanks
09-28-2024 01:02 PM
Hi @irenof ,
Ditto to @Robert Burns APIC 4.2 with NXOS 14.2 = good
APIC 5.2 with NXOS 14.2 = definitely check if there are any filters that specify port 22, and ideally run in this mode as a transition
09-28-2024 09:18 AM
ACI Switch images are the same as the APIC version just x10 so 14.2(1) woudl be paired with 4.2(1).
From above both are supported. There would be less risk IMO with Option 1 - which doesn't cross a major version (4.x > 5.x), but depending how long you intend to run mixed mode, both are options.
Robert
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide