thanks for fast replays! From what I can see it doesn't make big difference if I will use FI for failover or if I will do it under windows 2012.
So if I will do it on FIs I just need to pick the option "Enable Failover" instead of binding it to one of the Fabrics or I can have 2 vNICs each binded to separated Fabric and let do the Failover on System leavel but then it can only by Active standby - "Switch Independent" and I can't use any "LACP" method or "Static Teaming" right?
We call "enable failover" on the vnic in the service profile hardware failover. If you control it on the OS, it's called software failover.
Don't do both ! it can lead to problems (2 control loops, working against each other)
Your reasoning is correct ! active /stby, switch independent.
Windows 2012 R2 has functionality that requires Teaming setup. eg. you would like to have a vlan trunk entering your OS ? (the alternative would be to create as many interfaces as their are Vlans, and each vnic is assigned one vlan); in this case you have to create a team and the create subinterfaces, to split off the vlans.
Anyway, scalability is a argument against Hardware failover; FI has to do a lot of work (GARP handling); this is done by the control plane (CPU of the FI) for all blades ?
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...