1. I intend to do failover if any srvice/Gw/intf goes down.
Is this config correct for Intf/srv.
vrid 192.168.1.200 1 <-- For service
vrid 192.168.5.200 2 <-- For service
phy 1/1 <--for physical intf
phy 1/2 <--for physical intf
can i use both, vrid-peeer and criticla -phy in the same critical reporter... an example wil be very helpfull..
2. The ip of the service shud be the g/w or critical host address ? so can i put the ip of my uplink device or the server serving for l/b ? if yes, then what should i put in the keepalive aka-... ping list... the same ip?
ip address 192.168.5.7 <--just a spare ip.
keepalive type script ap-kal-pinglist ?192.168.5.1" <-- uplink L3 ip
keepalive frequency 2
keepalive maxfailure 2
keepalive retryperiod 2
Can you give me a example for the critical service..
3. you are right , i think trunk is not my option till i dont have a complex case..
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...