We are running ACE module version 'Version A2(2.0) [build 3.0(0)A2(2.0)]'
There are two 6500 chassis and each chassis has single ACE module configured in redundancy. All of a sudden the peer state changed to 'Peer State:FSM_FT_STATE_UNKNOWN' and my state got set to 'My State:FSM_FT_STATE_ACTIVE' on both the chassis.
I am not able to ping the Ft peer ip address anymore due to which both of the modules are not able to enter the active/hot failover mode. The ft vlan is properly configured to be passed between two chassis and they have been assigned to the respective ACE modules. The same configuration has been running for months and no configuration changes were done before the problem.
Please advise what may preventing the ACE FT interfaces to communicate as the pings between the Ft interfaces are failing and what could be the resolution.
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...
Cisco Documents are usually accurate, but when it came to the document
on Cisco APIC Signature-Based Transactions it was slightly off the mark.
This document is for those novices to API like me who cant seem to
figure out how to go about performing signat...