Cisco Cisco MGX-FRSM-HS2 B Serial Frame Service Module Libro blanco
White Paper
© 2009 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 14 of 25
NAM can provide per-client and per-server reports to help identify problematic sites and applications. Problematic
sites and application information can be also obtained from sources like end-user complaints, known infrastructure
limitations and dedicated tests.
Possible activities:
●
View worst performing client/server pairs for non-complying applications, determine the client site, application
and server
●
Use mid-term reports of client/server of interest to further confirm that the problem is capacity
Useful reports
Worst client-server performing transaction report can be used to determine the typical branch site that experiences
issues, based on the client network address (Figure 12). Filtering can be performed on clients to confirm that a
particular client would have performance issue with various servers -- indicating a potential site issue.
If the customer has NAM located in the Branch, he can get insight into the aggregate performance of a particular
application /server (example is shown in Figure 10).
3.4 Short-list candidate sites and applications
What are we trying to achieve?
Decide on the sites for WAAS optimization.
How do we achieve that?
The most sites that have application performance level that do not comply with the objectives are naturally WAAS
deployment candidates.
Selection of the candidates for WAAS could include the following:
●
assessment of the previous steps
●
assessment of how much the issues can be addressed by addition of more bandwidth
●
operational factors like for PoC/Pilot -- selection of an accessible site
3.5 Install WAAS + NAM
What are we trying to achieve?
Have WAAS and NAM reporting components properly configured
How do we achieve that?
WAAS deployment includes the following reporting components:
●
Configuration of WAE FA to send the traffic reports to NAM (typically done using WAAS CM).