Cisco Cisco MGX-FRSM-HS2 B Serial Frame Service Module Libro blanco
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
White Paper
© 2009 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.
Page 18 of 25
The graph below shows the changes to a ~60Kbps limited WAN link. Fa4/2 represents the outgoing branch traffic.
Traffic increased about 60% in the LAN and was slightly reduced in the WAN after optimization was turned on. Port
information is taken from if Table polling of the branch router after configuration of the managed chassis in NAM.
Click Reports -> Basic Reports. Select the LAN bytes out and WAN bytes in reports for the branch Router/Switch.
Note:
See Appendix for instructions on setting up reports.
3.7 Monitor and Troubleshoot
What are we trying to achieve?
Support for end-to-end monitoring and troubleshooting when WAAS is deployed
How do we achieve that?
Once WAAS solution is deployed, users can leverage the additional points of probing provided by WAE FAs to
complement the picture they can get from direct packet examination (like SPAN) and NetFlow. NAM functions like
Monitoring, Reporting, Threshold setting and packet capture/decode can help monitor the deployment health and
troubleshoot issues.
Multi data-source report was added to ease troubleshooting across different probing point. This report (Figure 19)
can show the response time experience from multiple data sources to help assess the problem source. As an
example, if various probing points show a larger delay toward the WAN (say the Edge-Client shows a larger Server-
Network-Delay and the DC-Server shows the opposite), it may suggest a network issue in the WAN.
Useful reports
The following reports can be leveraged:
●
Short-term and mid-term reports discussed in the previous sections
●
Multi data-source report (Figure 17)
Figure 19. Cross data-source report
Select Monitor -> Response Time -> Multi Segment.
4. Deployment Considerations
This document assumes the following:
●
WAAS is deployed in a hub and spoke model
●
NAM is located in the Data-Center side of the WAAS deployment. Support for cases where NAM is located in
the branch will be noted explicitly. NAM deployment can be a Virtual Blade on Core WAE or a dedicated
hardware (blade or appliance).