So were you upgrading to 2.5 code and this occured? In 2.5 we are also loading new switch code and you may have a issue. Loss of the internal communications between the VxWorks and the Switch may happen when down grading from 2.5 back to 2.3. Cisco TAC has a method to find if your Internal ethernet link is set wrong so you may need to open a case. Are you still down?
So the SN5428 is coming up in bootmode right? You can not telnet to it, right? You were upgrading from 2.X to 2.5, right? If the problem is tat the SN5428 is failing diags because it cannot see the FC switch then you will need to get console access to see if this can be fixed. You can email me at firstname.lastname@example.org and I can send a method we can try to recover the switch. This is bug CSCdy66379
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...