We are running the latest code of WAAS and what I want to do is have all edge locations act as core as well. We have 10 locations and each location has critical servers that need to communicate (ie. file replication) with each other. I understand this isn't the intended "design" of this product, but has anyone else deployed it this way? Currently, the CIFS optimization is only working from edge to core. I did add core services to the edge device but it still isn't working.
It's definitely capable of doing that. Even without the WAFS services, you should still see significant improvements with TFO, DRE and LZ.
If you are running core and edge services on a WAE, you need at least 2 GB of RAM on the box. Then you need to add connectivity statements between the new cores and respective edges that you want to optimize between.
I have the connectivity setup in both directions with the bandwidth and low round trip time configured, We have4 gb memory and its still not working from core to edge. Do I need to configure the core WAAS with edge services?
Strange, I have both edge and core configured as core/edge and the configs are basically identical (each is in its own device group), but still the file copy when initiated from the core side is not optimized. Any other thoughts? I have rebooted all devices as well.
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
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...