Our company was concerned about bandwidth issues on our 100M int on the CSS v8.10. Currently we have the client vlan on a 1G vlan690 and server vlans on 100M. We are noticing high output drops on all the 6500 100M connected int to the CSS. We were planning on trunking all the vlans on the 1G and also upgrading the failover link from 100M to 1G (box2box red). I would like to know if this new config will work and is this redesign recommended for scalability purposes. I have the new configs attached. Thoughts?
Thx Giles, Understood sounds like a good failover option. One concern though, we have an SCA2 module in slot 3 on both CSS's does this change our failover if say the SCA2 module in slot 3 fails how will this affect vip/interface redundancy option vs box2box?
Perfect, one last question Giles. How does this new vip/redundancy affect my config sync command? I was reading that you have to create seperate app session interfaces in order to execute the config sync command is this true?
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...