We're looking to consolidate our IT infrastructure into our datacenter and are looking at the WAAS solution for WAN optimisation and app acceleration. I have a couple of queries that I can't easily find answers too.
1 I've found performance data for the NME-WAE-502-K9 (500 concurrent TCP connections and around 5 Mbps optimized traffic). However, I can't find relative performance data for the 512 and 612 WAEs. Does anyone have this info (real world stats would be ideal)? - A number of our remote sites have BW of 10Mbps and 100Mbps..
2 I'm still not clear on the features of the Central Manager license; I know that a CM is required within a WAAS solution. I'm looking at putting a pair of WAE-612s into the datacenter (100Mbps connection) and am not sure if I should have both with the CM license - Does the CM license include the functionality of the Enterprise (e.g. App acceleration, CIFS etc) or should I have one with CM and the other with Ent license and then will this work as redundant pair?
1. WAE-7326 is no longer a recommended platform. The WAE-7341 should be used instead. The WAE-7341 is targeted for WAN bandwidth up to 310Mbps. In addition, the WAE-7371 is targeted for WAN bandwidth up to 1Gbps.
2. The number of WAEs that can be managed by a CM depends on the WAE model you are using for the CM. The current numbers are as following:
WAE-512-1GB = 500
WAE=512-2GB = 1,000
WAE-612-2GB = 2,000
WAE-612-4GB = 2,500
It does not matter what model WAEs are being managed.
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...