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.
Moquery is the command line cousin of Vizore, it's very helpful and efficient sometimes during the troubleshooting. This article aims to provide moquery cheat sheet to the users for some most common seen scenarios.
Here is the checklist before customers/partners contact Cisco TAC:
Firmware Version of APIC and Switch
Download Switch and APIC techsupport logs
Problem description (Symptoms with details)
Business impact (eg, what kind of services...
moquery usageAPIC moquerySwitchmoquery
This document discuss a common issue observed during the VMM integration & VM workload migration to ACI fabric.
VMware Virtual machines are hosted in Cisco UCS-B seri...