The CIFS object cache in WAAS (either in 4.0 or 4.1) is by server name or IP address. So if you preposition a dfs share, it could be from the leaf node closest to your core WAE, which may not be the one closest to your users at the edge. You can affect this by naming the WAE location where you want to preposition from (http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v411/configuration/guide/filesvr.html#wp1043516). The CIFS acceleration is designed to be transparent to the end users and to use autodiscovery to accelerate remote servers, including DFS servers. You should not have to join the WAEs to the domain, it should be transparent to both them and the DFS servers.
Are the users going from a local server to a remote server and their responses are worse? Or they had a remote file server and now it's worse?
Can you tell if the users traffic is being accelerated by the CIFS adapters? Look in the connections listings to see if the CIFS adapter is identified in them.
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...