We have moved our Backend vlans (10.1.3.x & 10.1.4.x) from CSS to ACE recently. To proceed further with the Front end move, we need some configuration assistance with respect to ACE. The scenario is explained below:-
Front End vlans 600 (10.1.6.x) & 700 (10.1.12.x) are currently configured/active in CSS. From the ACE, we have static routes for these vlans to be reachable by the backend Vlans 300 (10.1.3.x) & 400 (10.1.4.x). Once we configure vlan 600 & 700 interfaces in ACE, these networks will be known as locally connected thereby breaking the existing routes to the CSS front end vlans.
In order to perform a phase by phase move if the front end servers, we need to have vlan 600 & vlan 700 configured at both CSS & the ACE End without breaking the production backend & Front end.
Will specific static routes in ace precede the locally connected network or is there a recommended migration plan for this scenario?
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...