Has anyone come across the issue with the IRQ for routing on the WAE?
My edge box in our customer demo lab stopped routing traffic and only starts once you er-apply the gateway statments back in. Then network connectivity is restored and the WAE thinks its passing traffic to be acceleration process but in fact the traffic is worse than native across the WAN. This is on a 512 with an inline module running either 4.0.15b6 and or 4.0.17b14
Which "gateway statements" are you referring to? Obviously performance shouldn't be worse than native when WAAS is deployed. Can you please verify what speed/duplex the inline ports are configured/running as?
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...