Fabric running 3.2, going to discover 4.2 for Multi-Pod
I have a client with their production, single-pod fabric running 3.2(3), the one which can be directly upgraded to 4.2(7q). We are proposing upgrading the production fabric first, then going to introduce the other Pod because it is net-new. The new hardware are being shipped and not ready on-site, however according to the BoM it would be 4.2 anyway, so we figure upgrading the production fabric would be done sooner or later.
However, during EoY, they are afraid that upgrading the production fabric. They are proposing if we could introduce the new pod (running 4.2) to the fabric (running 3.2), then only upgrade the production fabric once everything has been migrated to the new pod.
Is it possible to discover new hardware with such mismatched versions?
P/s: no 5.2 train since their production Spines are not supported.
Good afternoon Friends, these days I was accessing the DNAC manager and my surprise is that I did not have access, after a basic analysis I observed that the equipment was operational, but without being able to access it via DNA GUI (browser) I also ident...
Today we are going to talk about how to configure backups in the Cisco ACI APIC Dashboard. As you might know APIC is a UCS based CIMC controller and we can check the configuration backups on the Cisco ACI APIC Dashboard. Remember that the HA solution mus...
Listen: https://smarturl.it/CCRS9E14 Follow us: https://twitter.com/CiscoChampion
Organizations are undergoing digital transformation like never before. Global spending on digital transformation of business practices, products, and organization...