I have a customer who uses UCS B-series infrastructure with single fabric interconnect (don't ask why). There is UCSM 1.4 running on it. Now, the customer purchased additional FI to create a cluster, as recommended. Now, the second FI arrived with 2.0 code. My question is, if I promote that single FI to a cluster and connect the seconf FI, will it be downgraded to 1.4 by the master, or newer version will take over, although it is on a slave? Should I perform manual downgrade to 1.4 on that new FI before I connect it to existing master? We do not need an upgrade to 2.0 now, 1.4 is doing just fine for this environment, so we want to stick wit it.
Never introduce a cluster member FI at a different version.
Best approach would be to downgrade the new FI to the same version first. Next promote the Standalone FI to primary, then introduce the secondary. (Though this process should not be disruptive, I would schedule downtime regardless to be safe.
Primary/Secondary roles are not chosen by the higher FW level.
If you have no need for the 2.0 features or bug fixes, then stay put where you are. If it's not broken, don't fix it.
We have just completed the migration. It went quite well. Just one thing was interesting. When I uploaded new package and requested version change in UCMS (for both: UCSM and kernel), the UCSM itself got restarted and new version became active. However, when I restarted the FI by power off/on the kernel and kickstart were still running previous version. The second reboot activated new NXOS. It happened with two FIs which we were downgrading. Did I miss something or it's just normal behavior?
Expected behavior. The proper procedure is to activate just UCSM first, let it activate the image (which will kill any existing UCSM instances), then activate the IOMs (startup version only), and finally activate the FI's one at a time.
Sounds like you doubled up a step which would schedule the second reboot to activate all endpoints.
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...