Data Center Real User Monitoring

Transcription

1 Data Center Real User Monitoring WAN Optimization Getting Started Release

2 Please direct questions about Data Center Real User Monitoring or comments on this document to: APM Customer Support FrontLine Support Login Page: Copyright 2012 Compuware Corporation. All rights reserved. Unpublished rights reserved under the Copyright Laws of the United States. U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Compuware Corporation license agreement and as provided in DFARS (a) and (a) (1995), DFARS (c)(1)(ii) (OCT 1988), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. Compuware Corporation. This product contains confidential information and trade secrets of Compuware Corporation. Disclosure is prohibited without the prior express written permission of Compuware Corporation. Use of this product is subject to the terms and conditions of the user's License Agreement with Compuware Corporation. Documentation may only be reproduced by Licensee for internal use. The content of this document may not be altered, modified or changed without the express written consent of Compuware Corporation. Compuware Corporation may change the content specified herein at any time, with or without notice. All current Compuware Corporation product documentation can be found at Compuware, FrontLine, Network Monitoring, Private Enterprise, Server Monitoring, Transaction Trace Analysis, Compuware APM, Vantage for Java and.net Monitoring, VantageView, Compuware APM, Real-User Monitoring First Mile, Gomez Performance Network, Data Center Real User Monitoring, dynatrace, and PurePath are trademarks or registered trademarks of Compuware Corporation. Cisco is a trademark or registered trademark of Cisco Systems, Inc. Adobe Reader is a registered trademark of Adobe Systems Incorporated in the United States and/or other countries. All other company and product names are trademarks or registered trademarks of their respective owners. Build: January 3, 2013, 23:45

3 Contents Contents Introduction Who Should Read This Guide Organization of the Guide Related Publications Accessing Customer Support Reporting a Problem Documentation Conventions Chapter 1 WAN Optimization Overview Chapter 2 WAN Optimization Adjustment in DCRUM WAN Optimization Controller Support Deployment Models In-path Single Monitoring Point Traffic Identification In-path Double Monitoring Point Traffic Identification (LAN optimized) In-path Double Monitoring Point Traffic Identification (LAN) In-path Advanced Mode Virtual In-path Advanced Mode Network Traffic Classification Deployment Models Single Sniffing Point Definition Double Sniffing Point Definition (LAN optimized) Double Sniffing Point Definition (LAN) AMD Sniffing Points Configuration for WAN Optimization WAN Optimization Setup Verification Configuring Compuware APM to Recognize Optimized WAN Traffic WAN Optimization and SSL WAN Optimization Configuration Summary Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring Special Considerations for Using NAM in Data Center Real User Monitoring Configuring CAS to Receive Data from NAM

4 Contents Attaching Cisco Network Analysis Module to RUM Console Configuring NAM Attaching NAM to CAS Scalability and Capacity Considerations Using NAM to Report Voice and Video Statistics in DCRUM Using NAM to Report Optimized WAN Statistics in DCRUM Chapter 4 WAN Optimization Reports Appendix A Metrics Related to WAN Optimization Adjustment Altered Perspective Reports Appendix B Known Restrictions in WAN Optimization Support

5 INTRODUCTION Who Should Read This Guide This manual is intended for administrators of Data Center Real User Monitoring who want to monitor applications on their optimized WAN links. Organization of the Guide This guide is organized as follows: WAN Optimization Overview [p. 9] Introduces to the concept of WAN optimization. WAN Optimization Adjustment in DCRUM [p. 11] Describes how to deploy and configure DCRUM to provide performance data measurement adjustment for WAN optimization. Using Cisco Network Analysis Module in Data Center Real User Monitoring [p. 27] Describes how to configure DCRUM to use data provided by Cisco NAM. WAN Optimization Reports [p. 41] Describes WAN optimization related reports. Metrics Related to WAN Optimization Adjustment [p. 43] Provides referential information on metrics related to WAN optimization. Known Restrictions in WAN Optimization Support [p. 47] Lists known issues and restrictions in WAN optimization support in DCRUM. Related Publications Documentation for your product is distributed on the product media. For DCRUM, it is located in the \Documentation directory. It can also be accessed from the Media Browser. You can also access online documentation for Compuware products via our FrontLine support site at FrontLine provides fast access to information about your Compuware products. You can download documentation and FAQs as well as browse, ask questions and get answers on user forums (requires subscription). The first time you access FrontLine, you are required to register and obtain a password. Registration is free. 5

6 Introduction PDF files can be viewed with Adobe Reader, version 7 or later. If you do not have the Reader application installed, you can download the setup file from the Adobe Web site at Accessing Customer Support Corporate Web Site To access Compuware's site on the Web, go to The Compuware site provides a variety of product and support information. FrontLine Support Web Site You can access online customer support for Compuware products via our FrontLine support site at FrontLine provides fast access to critical information about your Compuware products. You can read or download documentation, frequently asked questions, and product fixes, or your questions or comments. The first time you access FrontLine, you are required to register and obtain a password. Registration is free. Contact Us The contact information to all local Compuware offices is provided on the Web site. All high-priority issues should be reported by phone. Reporting a Problem When contacting APM Customer Support, please provide as much information as possible about your environment and the circumstances that led to the difficulty. You should be ready to provide: Client number. This number is assigned to you by Compuware and is recorded on your sales contract. The version number of the AMD, report servers, and RUM Console with RUM Console Server. Report Server Use the report server GUI by selecting Help Product Information About, or Tools Diagnostics System Status. AMD Scroll down to the Testing AMD section. At the bottom of the diagnostic data paragraph, look for Version ND-RTM v. ndw.ww.x.y.zz. RUM Console and RUM Console Server Use the RUM Console GUI by selecting Help About menu item. TCAM Use the TCAM GUI by selecting Help About menu item. 6

7 Introduction Environment information, such as the operating system and release (including service pack level) on which the product (AMD, report server) is installed, memory, hardware/network specifications, and the names and releases of other applications that were running. Problem description, including screen captures. Exact error messages, if any (screen captures recommended). Whether or not the problem is reproducible. If it is, include a sequence of steps for problem recreation. If it is not, include a description of the actions taken before the problem occurred. A description of the actions that may have been taken to recover from the problem, and their results. Debug information for specific components obtained from RUM Console. Information about the RUM Console itself. To export all the information, navigate to Tools Export Diagnostic Information in the RUM Console menu. Information about the report servers. To export the information for a specific ADS or CAS, right-click the device on the Devices tab in the RUM Console and choose Export Diagnostic Information from the context menu. Include Collector Diag Option to include diagnostic information on data collectors attached to the report server. Save as Destination path and filename for the diagnostic package file. Information about the AMD. To export the information for a specific AMD, right-click the device on the Devices tab in the RUM Console and choose Export Diagnostic Information from the context menu. Include Data Files Option to include fragments of traffic data. Time range Time range of the monitoring data to be included with the diagnostics. Data File Filter (RegEx) Regular expression filter for monitoring data files generated during the defined time range. Save as Destination path and filename for the diagnostic package file. Information from the TCAM System Event log of the machine where the TCAM is operating. TCAM logs which by default are stored in C:\ProgramData\Compuware\VTCAM for Windows Server 2008 and C:\Documents and Settings\All Users\Compuware\VTCAM for Windows Server

8 Introduction NOTE Please compress all the files before sending them to Customer Support. Compuware values your comments and suggestions about the Compuware APM products and documentation. Your feedback is very important to us. If you have questions or suggestions for improvement, please let us know. Documentation Conventions The following font conventions are used throughout documentation: This font Bold Citation Documentation Conventions [p. 8] Fixed width Fixed width bold Fixed width italic Menu Item Screen Indicates Terms, commands, and references to names of screen controls and user interface elements. Emphasized text, inline citations, titles of external books or articles. Links to Internet resources and linked references to titles in Compuware documentation. Cited contents of text files, inline examples of code, command line inputs or system outputs. Also file and path names. User input in console commands. Place holders for values of strings, for example as in the command: cd directory_name Menu items. Text screen shots. Code block Blocks of code or fragments of text files. 8

9 CHAPTER 1 WAN Optimization Overview Corporate branch offices are often widely dispersed geographically and depend on efficient Wide Area Network (WAN) links to access resources and applications at a main datacenter or other branches. To this end, WAN optimization was developed to reduce the load on WAN connections between data centers, servers, and clients. The goal of WAN optimization is to improve application response time and reduce the required bandwidth over a WAN connection by using a WAN controller on each end of the WAN link. A WAN Optimizer is deployed on either end of a WAN connection to optimize the traffic sent over the WAN. The WAN Optimizer classifies, prioritizes, and compresses network data, caches network traffic, and streamlines protocols to maximize the performance of a service delivered over distributed network. WAN optimization controllers (WOCs) are physical devices that transparently intercept local network traffic, optimize it, and send the optimized traffic over the WAN link to the receiving controller. On the other side of the WAN, the receiving WOC transparently converts the optimized traffic from the WAN link into normal network traffic. The typical WAN optimization scenario involves at least two WOCs located between the data center (or a server) and a branch office (or a client). Figure 1. WAN optimization concept Unoptimized link Optimized WAN link Unoptimized link WAN Branch office Data center The most common optimization techniques involve: Transport (TCP) optimization TCP flow-control round trips are reduced by: Fast error recovery 9

10 Chapter 1 WAN Optimization Overview Mitigated slow-start Window scaling Pre-established TCP connection pools between the WAN-optimizing appliances Payload Optimization The TCP payload is indexed and stored on disk on each side of the WAN: Data segments (blocks) are replaced with references to this data Byte-level indexing is independent of the application or file Application Acceleration Application-specific acceleration is used to reduce application traffic. In Common Internet File System (CIFS) SMB emulation is used: By spoofing the CIFS protocol By reading ahead and writing behind Specific modules can be made available from individual vendors for a specific application Using a combination of these techniques and setting up the acceleration appliances to act as proxy servers, end-user experience can be accelerated significantly. NOTE Application optimization monitoring is not supported in the current version of DCRUM. 10

11 CHAPTER 2 WAN Optimization Adjustment in DCRUM WAN optimization adjustment in DCRUM is designed to make your deployment aware of WAN optimization in the network and able to rectify measurements that might be skewed by optimization. DCRUM is capable of collecting and reporting numerous metrics based on monitored network traffic within your network infrastructure. When these metrics are used in an optimized WAN environment, however, their calculations must be adjusted to account for the presence of WAN optimization. DCRUM does so by detecting optimized traffic on WAN links and recalculating network metrics respecting WAN optimization. AMD deployment The typical deployment, in which an AMD is connected on both sides of the data center WOC, makes it possible to observe the network traffic before and after it is optimized. This deployment requires the ports destined for WAN optimization to be spanned on both sides of the WOC so the traffic destined for optimization and traffic already optimized is available to the AMD. With this information, DCRUM is able to correlate WAN packets and adjust metrics by utilizing the Application Delivery Channel Delay (ADCD) metric. Figure 2. Single AMD monitoring both sides of a WAN optimization controller Unoptimized link Optimized WAN link Unoptimized link WOC WOC WAN Branch office Data center AMD Central Analysis Server (CAS) 11

12 Chapter 2 WAN Optimization Adjustment in DCRUM The transaction measurements performed on an unoptimized link are adjusted based on measurements taken on the optimized link. In protocols involving more than one operation in a single connection, the AMD correlates optimized packets with operations. Using this single AMD configuration, DCRUM performs the following adjustments: Correlate WAN packets The report server correlates WAN packets belonging to a specific transaction. Introduce the Application Delivery Channel Delay metric. If protocol or application traffic does not allow for packet correlation, Compuware APM uses the ADCD metric to adjust network and WAN metrics. NOTE WAN Optimization metrics added to the standard DMI report may alter the values of certain metrics. For example, a report displaying Total bytes for a specific software service, will display a different value for the same Total bytes metric if that report contains metrics associated with optimized WAN. Adding a WAN Optimization metric to the report widens the perspective of that report and as such, the report then displays the WAN Optimization metrics combined with values observed locally. As a result, a duplication of some metric values occurs. WAN Optimization Controller Support Compuware APM 12.0 supports the physical in-path deployment of Riverbed Technology's Steelhead WAN optimization controller (WOC) and Cisco Wide Area Application Engine (WAE). The in-path deployment requires that the WOC be connected to the LAN-side device (datacenter backbone switch) and the corresponding WAN-side device (router). This deployment model is reflected in the AMD configuration scenario as a solution for WAN optimization adjustment in Compuware APM. For more information, see AMD deployment [p. 11]. Riverbed WAN optimization support has been thoroughly tested against physical Steelhead appliances. In addition, tests against Steelhead Mobile, a software equivalent of the WOC for remote users, have also been conducted, but in a narrower range. Physical in-path. Virtual in-path WCCP. Data Center Real User Monitoring supports usage of Web Cache Communications Protocol (WCCP) where Riverbed Steelhead appliances are connected to a switch in the path of the network flow between the servers and the clients. Data Center Real User Monitoring also supports deployments in which the Riverbed Interceptor redirects traffic to a cluster of Riverbed Steelheads. This deployment requires that the Riverbed Interceptor device be deployed with access to data as if it was in-path (for example, the traffic 12

13 Chapter 2 WAN Optimization Adjustment in DCRUM flow can be mirrored to the AMD simulating the in-path deployment); otherwise, DCRUM would not be able to provide correct measurements. For details on deployment models for your Steelhead appliances, please refer to your Steelhead documentation. Cisco WAN optimization support has been thoroughly tested against physical Cisco WAAS appliances. The following deployments are supported: Virtual in-path WCCP (default deployment for WAAS). Physical in-path, also known as inline. Compuware APM 12.0 supports Cisco WAN optimization using a generic analyzer to calculate the ADCD metric. ADCD is approximated using the WAN RTT value. Unsupported deployments The following deployments are not supported: Out-of-path Virtual in-path: Layer-4 switch Hybrid Policy-based routing (PBR) NOTE While the above virtual in-path deployments are officially unsupported, TAP filtering could be used for Layer-4 switch and Hybrid deployments, and PBR could be filtered at the MPLS level. In addition, Cisco WAAS as router modules are not supported. Deployment Models Identification and classification of network traffic at specific monitoring points on the WAN side and the LAN side of the WOC allows the AMD to observe the network traffic within your WAN optimization deployment and report the performance of WAN optimized network and applications. AMD monitoring the entire network traffic in various monitoring points within your infrastructure, needs to distinguish the types of network traffic that it is observing. You can classify the traffic types by identifying the networks in the monitoring point rules. The three network types that you can identify within your WAN optimization deployment are: WAN LAN Optimized Datacenter LAN 13

14 Chapter 2 WAN Optimization Adjustment in DCRUM Depending on your deployment model you may be required to identify all three networks. You can identify the networks based on network interface, VLAN, MPLS or GRE/WCCP values. The more network traffic you identify and classify its type, the more precise analysis of your WAN optimization performance will be. Identifying the optimized WAN traffic on the WAN side is the minimum configuration to monitor the WAN optimization performance however, you should provide as much information as possible about the observed traffic at any of the monitoring points in your optimized WAN environment. Specifying traffic type within your LAN infrastructure is optional, but classifying at least one of the traffic types on the LAN side allows you to gather more precise optimization measurements and improved performance of traffic analysis. In-path Single Monitoring Point Traffic Identification This deployment model requires the identification of the network traffic only on one side of the WOC ( the WAN side). After network traffic on the WAN side has been classified as WAN traffic, the rest of the network traffic ( the LAN side) is automatically classified as regular LAN traffic. This monitoring deployment assumes that the AMD monitors the network traffic before the WOC and this given, identification of the optimized WAN traffic is required. Once the specific network traffic on the WAN side has been identified as WAN optimized, the rest of the network traffic (the LAN side) will be automatically classified as regular LAN traffic (Datacenter LAN). However, traffic on the LAN side that is matched with the traffic on the WAN side will be automatically reclassified as LAN traffic destined for, or returning from, optimization (LAN optimized). This configuration requires minimal knowledge of the traffic that is being observed however, the LAN side relies on automatic detection and matching of optimized WAN and LAN traffic and as such, this may be inadequate for certain applications. Figure 3. Monitoring scenario for identification of WAN traffic only. Network traffic classification can be achieved by defining monitoring point rules. For each of the monitoring points within a deployment you can identify the network type by interface, VLAN, MPLS or GRE/WCCP values. For more information, see Network Traffic Classification [p. 17]. In-path Double Monitoring Point Traffic Identification (LAN optimized) This deployment model requires the identification of the network traffic on both sides of the WOC ( the WAN side and the LAN side). Network traffic observed on the WAN side of the 14

15 Chapter 2 WAN Optimization Adjustment in DCRUM WOC is matched with the network traffic on the LAN side and by default the LAN side is classified as LAN traffic destined for, or returning from, optimization (LAN -optimized). Defining the network traffic type on the LAN side, you can specify the traffic that you expect to be, or already was, optimized (LAN optimized). This, along with matched traffic on the WAN side, will present the performance data of your WAN optimization environment. All other traffic observed on the LAN side will be classified and reported as regular LAN traffic (Datacenter LAN). Figure 4. Monitoring scenario for identification of WAN traffic and LAN traffic destined for optimization. Network traffic classification can be achieved by defining monitoring point rules. For each of the monitoring points within a deployment you can identify the network type by interface, VLAN, MPLS or GRE/WCCP values. For more information, see Network Traffic Classification [p. 17]. In-path Double Monitoring Point Traffic Identification (LAN) This deployment model requires the identification of the network traffic on both sides of the WOC ( the WAN side and the LAN side). Network traffic observed on the WAN side of the WOC is matched with the network traffic on the LAN side and by default it is classified as datacenter LAN traffic (Datacenter LAN). Use a configuration like this to separate the optimized LAN traffic from the rest of your LAN traffic. This can be achieved by specifying regular LAN traffic. This configuration isolates a segment of your LAN that you do not expect to be optimized; its traffic, therefore, does not need to be correlated with the optimized traffic on the WAN side. This makes it possible to identify the traffic relating only to clients utilizing the connections that are not optimized and at the same time to identify the rest of the traffic as relating only to clients utilizing the connections that are optimized. Figure 5. Monitoring scenario for identification of WAN traffic and regular LAN traffic. 15

16 Chapter 2 WAN Optimization Adjustment in DCRUM Network traffic classification can be achieved by defining monitoring point rules. For each of the monitoring points within a deployment you can identify the network type by interface, VLAN, MPLS or GRE/WCCP values. For more information, see Network Traffic Classification [p. 17]. In-path Advanced Mode This deployment model requires the identification of the network traffic type on both sides of the WOC ( the WAN side and the LAN side). Network traffic observed on the LAN side can be further separated into LAN traffic destined for optimization (LAN Optimized) and datacenter LAN traffic (Datacenter LAN). Classifying all possible network traffic allows for better precision of measurements however, it requires most information about the monitored environment. The three types of networks that should be identified in the monitoring point rules are: WAN LAN Optimized Datacenter LAN The advanced mode also allows you to specify the network traffic that should not be taken into consideration at all and should be omitted in WAN optimization performance calculations. The network identification defined in the monitoring point rule as type Drop will not be part of the monitoring of WAN optimization. Figure 6. Monitoring scenario for identification of WAN traffic, LAN traffic destined for optimization and regular LAN traffic. Network traffic classification can be achieved by defining monitoring point rules. For each of the monitoring points within a deployment you can identify the network type by interface, VLAN, MPLS or GRE/WCCP values. For more information, see Network Traffic Classification [p. 17]. Virtual In-path Advanced Mode This deployment model requires the identification of the network traffic type on both sides of the WOC ( the WAN side and the LAN side). Network traffic observed on the LAN side can be further separated into LAN traffic destined for optimization and regular LAN traffic. Additional configuration is required to isolate WAN type traffic between the WOC and traffic routing devices. 16

17 Chapter 2 WAN Optimization Adjustment in DCRUM When virtual in-path deployment is in use, the WAN traffic is often redirected by the routing device and the WOC device. It is important to identify the traffic belonging to WAN optimized network and separate it from all other traffic. Typically, the WAN optimized network would be identified by VLAN, MPLS, or GRE/WCCP values in the monitoring point rules and the following rule would treat would set all other traffic on that interface as Drop. Figure 7. Monitoring scenario for identification of WAN traffic, LAN traffic destined for optimization and regular LAN traffic. Network traffic classification can be achieved by defining monitoring point rules. For each of the monitoring points within a deployment you can identify the network type by interface, VLAN, MPLS or GRE/WCCP values. For more information, see Network Traffic Classification [p. 17]. Network Traffic Classification Network classification and identification occurs by adding a rule that classifies the network traffic as a particular network type. Each of the rules is a set of network details that is used to filter and classify the network traffic. You can define the rule by providing the following information to classify the network traffic: Traffic type (required) The traffic type choices depend on your deployment model. For example, in the In-path double point (LAN optimized) deployment model you are expected to classify only two types of the network traffic, the WAN traffic on the WAN side and the LAN optimized traffic on the LAN side. This choice of deployment model will limit the traffic type options to WAN and LAN Optimized. The advanced mode deployments contain all available traffic types: WAN LAN Optimized Datacenter LAN Drop Name (optional) Common name or description for this network. Interface (optional) List of interfaces available for network classification. 17

18 Chapter 2 WAN Optimization Adjustment in DCRUM VLAN (optional) VLAN tag. No VLAN in traffic checkbox allows to specify that observed network traffic does not contain VLAN traffic. It forces all observed VLAN packets NOT to be automatically recognized as VLAN. MPLS (optional) Label of a MPLS-based network. No MPLS in traffic checkbox allows to specify that observed network traffic does not contain MPLS traffic. It forces all observed MPLS packets NOT to be automatically recognized as MPLS. GRE/WCCP (optional) Generic Routing Encapsulation (GRE) /Web Cache Communication Protocol (WCCP) identification. No GRE/WCCP in traffic checkbox allows to specify that observed network traffic does not contain GRE/WCCP packets. It forces all observed GRE/WCCP packets NOT to be automatically recognized as GRE/WCCP. Direction (available and required only for Cisco deployments) Direction of the observed traffic to be classified. For example, it is possible to create two network traffic classifications of the same network traffic containing the same VLAN tag. Traffic going To Server is classified as WAN while the same VLAN traffic going From Server can be classified as Datacenter LAN. Available options are: Both From server To server Deployment Models The following deployment models refer to AMD versions or earlier. Even when using the latest console release, the legacy deployment model will be used to configure AMD running software version or earlier. Identification of a WAN sniffing point is only the minimum required configuration to obtain WAN optimization measurements. You should provide as much additional information as possible about your optimized WAN environment to achieve precise measurements. Configuration of sniffing points 2 and 3 is optional, but identifying at least one of these points allows you to gather specific traffic for more precise measurement and to improve performance of traffic analysis. Single Sniffing Point Definition This configuration enables you to configure only the optimized WAN sniffing point, and classifies the rest of the traffic located on the LAN side of the WOC as regular LAN traffic. However, traffic on the LAN side that is matched with the traffic on the WAN side is classified as LAN optimized. This configuration requires minimal knowledge of the traffic that is being observed, 18

19 Chapter 2 WAN Optimization Adjustment in DCRUM but it depends on automatic detection and matching of optimized WAN and LAN traffic, and this may be inadequate for certain applications. Figure 8. Minimal configuration for WAN optimization monitoring WOC LAN WAN 1 2 Data center AMD Configuration with one defined point This configuration states that traffic observed on interfaces eth0 and eth1 will be considered optimized WAN traffic, while any other traffic by default will be considered LAN traffic. Table 1. Single sniffing point Definition Point 1 Point 2 Point 3 Name My optimized WAN traffic Interfaces eth0 eth1 VLAN MPLS Double Sniffing Point Definition (LAN optimized) In this scenario, each defined sniffing point is located on each side of the WOC. Sniffing point 1 monitors the optimized traffic and matches the data with unoptimized traffic observed on sniffing point 2. Using the sniffing point 2 definition, you can filter the traffic that you expect to be optimized. This, along with observed traffic on sniffing point 1, will present the measurement data for your WAN optimization environment. 19

20 Chapter 2 WAN Optimization Adjustment in DCRUM Figure 9. Monitoring scenario with two sniffing points defined WOC WAN 1 2 Data center 3 AMD LAN Configuration with defined points for optimized WAN and optimized LAN This configuration states that traffic tagged VLAN 102 and 104 will be considered optimized WAN traffic and traffic observed on eth2 will be considered as regular LAN traffic that has been optimized. The rest of the observed traffic will be considered regular LAN traffic. Table 2. Double sniffing point (LAN optimized) Definition Point 1 Point 2 Point 3 Name My optimized WAN traffic My Data Center traffic Interfaces eth2 VLAN 102, 104 MPLS Double Sniffing Point Definition (LAN) Use a configuration like this to separate the optimized LAN traffic from the rest of your LAN traffic. This can be achieved by specifying sniffing point 3. This configuration isolates a segment of your LAN that you do not expect to be optimized; its traffic, therefore, does not need to be correlated with the optimized traffic. This makes it possible to identify the traffic relating only to clients utilizing the connections that are not optimized and at the same time to identify the rest of the traffic as relating only to clients utilizing the connections that are optimized. 20

21 Chapter 2 WAN Optimization Adjustment in DCRUM Figure 10. Monitoring configuration separating a segment of unoptimized LAN from optimized LAN WOC WAN 1 2 Data center 3 AMD LAN Configuration with defined points for optimized WAN and regular LAN In this configuration, traffic observed on interface eth1 is considered optimized WAN traffic, while traffic observed on interface eth2 is considered regular LAN traffic. The rest of the traffic is considered LAN optimized. In the event that no traffic is observed on either eth1 or eth2, the tagged VLAN traffic will be classified respectively: VLAN 102 for eth1 as WAN optimized, and VLAN 104 for eth2 as regular LAN traffic. The rest of the traffic will be considered LAN optimized. Table 3. Double sniffing point (LAN) Definition Point 1 Point 2 Point 3 Name My optimized WAN traffic My corporate LAN traffic Interfaces eth1 eth2 VLAN MPLS AMD Sniffing Points Configuration for WAN Optimization A sniffing point is a point in your network architecture where the AMD can monitor traffic. Sniffing points A sniffing point can be: 1. A point where optimized WAN traffic is expected. 2. A point where optimized WAN traffic is already converted to LAN traffic. 21

22 Chapter 2 WAN Optimization Adjustment in DCRUM 3. A point within your LAN infrastructure that can be used to exclude a LAN segment to achieve more accurate WAN optimization measurements. For each sniffing point you define, you need to provide one of the following to identify the type of traffic being monitored: Name Interfaces VLAN MPLS This is the human-readable name you give the sniffing point. If you do not provide a name, the AMD populates the name with a generic string indicating the type of sniffing point. Network interfaces monitoring traffic on a particular sniffing point. The list of interfaces available is automatically retrieved from the configured AMD. Use commas to separate multiple VLAN identifiers. Virtual links between distant network nodes identified by a label carried within the MPLS header. Use commas to separate multiple labels. Sniffing point detail priority The components of a sniffing point configuration have an order of precedence that corresponds to their positions on the screen from top to bottom: If you specify interfaces, the AMD uses them to identify the traffic on the sniffing point. If you do not specify interfaces, the AMD uses the VLAN identifier. If you do not specify any of the above, the AMD uses the MPLS label. WAN Optimization Setup Verification After WAN optimization-related configuration is completed, your AMD will begin to observe the WAN traffic immediately and WAN optimization reports will present the metrics related to optimized WAN. To verify that your configuration of DCRUM is monitoring and reporting you WAN optimization traffic, examine the Link View Status - Links report. To access this report, select Reports Network View and click the Links tab. Usage and Performance metrics containing positive values for WAN link type indicate that your WAN optimization is recognized by DCRUM and is actively monitored. Configuring Compuware APM to Recognize Optimized WAN Traffic All AMDs that monitor network traffic using WAN optimization must be configured before Compuware APM can automatically recognize optimized WAN traffic. RUM Console will help you to configure and propagate the configuration to all your AMDs. Before You Begin It is good practice to have the following information handy during configuration: The deployment model of your WAN optimization. 22

23 Chapter 2 WAN Optimization Adjustment in DCRUM The manufacturer of your WOCs. The details for each of the sniffing points being used in the WAN optimization solution. The AMD physically connected to the network infrastructure as shown in AMD deployment [p. 11]. It is assumed that you have a computer running RUM Console with which you are able to connect to the AMD responsible for monitoring WAN and LAN traffic within your WAN optimization environment. It is also assumed that you are familiar with the concept of configuration types and are able to publish the configuration to the specific AMD. Note that to view data for optimized WAN links on the Tiers report, you must have the Enterprise CAS personality license. To make Compuware APM aware that it is operating in an optimized WAN environment and collect measurements from such an environment, perform the following steps: 1. Start and log in to RUM Console. 2. Select the Entire Configuration perspective. 3. Click the Devices tab to display the current device list. 4. Right-click an AMD and select Open Configuration from the context menu. 5. Click Edit as Draft to set your configuration to draft mode (if you are not in draft mode already). 6. In the Configuration tree, open Global and click WAN Optimization to display the WAN optimization screen. 7. Select the Enable WAN optimization adjustment check box. 8. In the Deployment model section, select one of the predefined deployment models for your WAN optimization. 9. Select a WAN acceleration engine vendor. 10. In the Sniffing points section, enter a Name for each of your sniffing points. This will enable you to identify your sniffing points while creating and viewing reports. 11. For each of your sniffing points, edit the Interfaces list to indicate the interfaces that correspond to the deployment model. To add an interface, click the icon. To remove an interface, select it and click the icon. 12. Optional: For each of your sniffing points, enter one or more VLAN IDs of the network to be observed at this sniffing point. Use commas to separate multiple VLAN identifiers. 13. Optional: For each of your sniffing points, enter the MPLS label of the network to be observed at that sniffing point. Use commas to separate multiple labels. 14. Publish the draft configuration on the monitoring device. a. In the Entire Configuration perspective, select the Devices tab. b. Right-click the device and select Publish Draft Configuration from the context menu. 23

24 Chapter 2 WAN Optimization Adjustment in DCRUM WAN Optimization and SSL While the typical network and software services can be optimized using standard optimization methods, encrypted network traffic requires special consideration. Typically, the WAN Optimization Controllers (WOCs), if configured properly, decrypt the SSL network traffic, optimize it, encrypt it again, and send it through the optimized WAN connection. For details on how to configure your WOC for encrypted network traffic, please refer to your WOC manufacturer's guide. Note that WAN optimization of encrypted, secure traffic may result in overall performance decrease for applications using SSL encryption. Riverbed Riverbed Technology's Steelhead WOC does not, by default, optimize SSL traffic. It uses pass-through to send encrypted traffic over the WAN connection in the form that it was received from the LAN. This default configuration, which is supported by Compuware APM, will generate accurate measurements for WAN optimization reports counting the SSL traffic as pass-through. If the Steelhead WOC is configured to decrypt and optimize SSL traffic, the AMD will approximate ADCD using the RTT value for the particular software service. Although it is not recommended, some software services use non-standard ports for their SSL traffic. If not configured for such non-standard ports, the WOC will treat the encrypted traffic as standard network traffic and will attempt to optimize it. As a result, the traffic observed by the AMD on the LAN and WAN sides of the WOC will not be fully matched, and measurements for that communication cannot be matched. The AMD will approximate the ADCD using the RTT value for the particular software service. For example, ADCD for a software service, which generates hits that are not detected on the WAN side, will be approximated using the RTT value. WAN Optimization Configuration Summary The following items need to be addressed in order to successfully configure monitoring of the optimized WAN traffic. The configuration will effect both the AMD and CAS report server. AMD Determine user-defined software service traffic that is transmitted over optimized WAN. Select the vendor of your WOCs. Carefully plan deployment and configure mirrored ports that mirror LAN traffic to be transmitted over optimized WAN. CAS Determine remote sites that reside on far ends of the optimized WAN lines. Designate sites of interest as used-defined links (UDLs). NOTE UDLs imported from an external file need to be modified manually in the import file (location-*.config) by setting the Loc_1.udl variable to true. 24

25 Chapter 2 WAN Optimization Adjustment in DCRUM The Optimized client network tier is created automatically based on data received from the AMD. 25

26 Chapter 2 WAN Optimization Adjustment in DCRUM 26

27 CHAPTER 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring CAS report servers can accept performance data from data collectors of type Cisco Network Analysis Module (NAM), version 4.2 or later. The devices must be configured and assigned to the report servers, using RUM Console in a similar way as for other types of devices. Configuring data monitoring options on a NAM device can be performed either before or after arranging for the device to be recognized by a RUM Console. Note, however, that the RUM Console provides an option to view NAM data sources or to connect to a NAM Web Console. It may therefore be convenient to follow the order given below: 1. Familiarize yourself with time synchronization and performance issues when using Cisco Network Analysis Module in Data Center Real User Monitoring. Knowledge of these concepts will enable you to choose correct values for configuration parameters. For more information, see Special Considerations for Using NAM in Data Center Real User Monitoring [p. 28]. 2. Configure the time interval at which CAS should interrogate NAM devices and at which it should generate its own data records. For more information, see Configuring CAS to Receive Data from NAM [p. 30]. 3. Attach the NAM to the RUM Console. For more information, see Attaching Cisco Network Analysis Module to RUM Console [p. 32]. 4. Configure the NAM devices to generate data readable by CAS. For more information, see Configuring NAM 5 [p. 33]. 5. Attach the NAM devices to the CAS installation. For more information, see Attaching NAM to CAS [p. 35]. Alternatively, you can configure your NAM first, as a separate task, by accessing it independently of the RUM Console. 27

28 Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring NOTE A NAM can list many data sources, but they do not all have to be used by the report servers that collect data from the NAM. When you attach a NAM to the CAS, you specify which of the available data sources should be used by the report server. The same NAM can supply data to a number of CAS installations and each one can use different data sources. For more information, see Attaching NAM to CAS [p. 35]. After you have attached your NAM to the RUM Console, the options to view NAM data sources and to access the NAM's Web Console, can be found in the context menu in the Devices view: To open the Web Console for a NAM, right-click the NAM in the Devices list and select Open Cisco NAM Web Console. To list the data sources currently defined for the NAM device, select Open Cisco NAM Data Sources. Supported NAM appliances The devices tested to work with CAS include: NAM-2220 NAM-2204 NAM-2x NAM-2 NAM-1x NAM-1 NME-NAM-80S NEM-NAM-120S WAVE-574 WAVE-674 Special Considerations for Using NAM in Data Center Real User Monitoring There are a number of configuration and reporting issues that are specific to using Cisco Network Analysis Module in Data Center Real User Monitoring. 1. Clock (time) synchronization between NAM and CAS This is one of the configuration steps described in Configuring NAM 5 [p. 33]. 2. Eliminating jitter in reported traffic statistics Jitter can be caused by CAS creating its own data monitoring records from data received for a variable number of NAM report intervals. While the average effect is still the same, the actual data is reported with a large jitter. To avoid jitter, correct dependencies must be maintained between the following parameters: 28

29 Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring the length of the monitoring interval used by CAS the length of the report interval used by NAM the length of the interval at which CAS interrogates NAM The recommended dependencies are as follows: In most cases the length of the report interval used by NAM should be equal to the length of the report interval used by CAS. If there is a danger of data duplication (see below), the length of the report interval used by NAM should be reduced to fit an integer number of times within the length of the report interval used by CAS. However, care should be taken not to reduce it too much, else other problems may occur; see other dependencies. The length of the interval at which CAS interrogates NAM should fit an integer number of times (two or more) within the length of the report interval used by CAS. Two is the recommended value and, care should be taken not to reduce the interrogation interval too much, else other problems may occur; see other dependencies. The length of the interval at which CAS interrogates NAM should be less than the length of the report interval used by NAM. The difference between the two values should allow sufficient time for data to be generated by and delivered from NAM to CAS. This, in practice, is at least 20 seconds, but often more. Therefore, for cases where there is no danger of data duplication: Configure the report interval on NAM to be equal to the monitoring interval configured for CAS: The default value is 5 minutes. Configure CAS to interrogate NAM at intervals of half that length, that is 2.5 minutes. 3. Reducing data duplication errors in scenarios where there is more than one NAM or AMD device, and some of the traffic is monitored by more than one device Data duplication can occur for two reasons: The same traffic being recognized as a differently named service (application), by two different monitoring devices Traffic for the same service (application) name, being counted twice by the report server The first type of data duplication can be avoided by ensuring that names used by AMD devices for monitored services, agree with the application names used by NAM devices. The second type of data duplication between AMD devices is resolved automatically within Data Center Real User Monitoring. However, some duplication may occur if the same traffic is being monitored by a number of different NAMs. This error can, however, be reduced by reducing the length of the report interval for all the NAM devices involved. The duplication error will then, on average, be less than half of the NAM report interval. Therefore, if there is a danger of data duplication, you should reduce the size of the report interval for NAM and the length of the interval at which CAS interrogates NAM, in such a way that the dependencies and conditions described in Item 2 [p. 28] are preserved. 4. Precedence of reporting between traffic monitored by AMD and NAM 29

30 Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring In cases where data duplication occurs between AMD and NAM, CAS will automatically attempt data de-duplication, and then will award priority to data received from AMD. 5. Ensuring reliable network delay measurements For NAM devices, all transactions with response time larger than configured RspTimeMax will be considered slow. Because NAM does not report network delay (RTT) for slow responses, setting this value too low may disturb network delay measurements. Setting an appropriate value of RspTimeMax is one of the steps configuring described in Configuring NAM 5 [p. 33]. 6. Performing reliable bandwidth usage measurements Note that for client bytes and server bytes, NAM reports only the TCP payload and does not report TCP header size or size of any headers below the TCP layer. Therefore the reported bandwidth usage will appear lower by that value, as compared to the value reported by AMDs, which include header sizes. For example, for TCP/IP over Ethernet, the combined size of all the headers will be 54 bytes per packet, and the reported number of bytes transferred will not include this value. Configuring CAS to Receive Data from NAM CAS can accept data from different sources, including Cisco NAM. However, NAM is not a DCRUM component, so CAS must be configured to work with NAM and to know how to interpret the data. Before You Begin You should familiarize yourself with issues related to time synchronization and performance as described in Special Considerations for Using NAM in Data Center Real User Monitoring [p. 28]. An understanding of these concepts will enable you to choose appropriate values for the corresponding configuration parameters. You need to have administrative rights to perform configuration steps on the CAS. A set of properties must be tuned to acquire meaningful results in the reports. These properties are accessed on the User properties screen. To access User properties, type: in the Web browser's Address bar and press [Enter]. The User properties screen enables you to view and modify a large number of report server settings. Select the required setting, enter the required value, and click Set value. To configure CAS to receive data from NAM: 1. Optional: Configure the length of the interval at which CAS will interrogate NAM appliances. Choosing a value: Use the default value of 150 seconds (2.5 minutes) if the NAM report interval is set to 5 minutes, as it normally would be in situations where it is supplying data to CAS and there is no danger of data duplication. 30

31 Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring To reduce jitter in reported data, the length of the interval at which CAS interrogates NAM should fit two or more times within the length of the report interval used by CAS. For information on how to check or modify the value of the NAM report interval, see Configuring NAM 5 [p. 33]. For a discussion on advisable report interval values, see Special Considerations for Using NAM in Data Center Real User Monitoring [p. 28]. The corresponding configuration parameter (NAM_GET_FILE_PERIOD) can be accessed in CAS on the User properties screen. 2. Optional: Configure CAS monitoring interval. Choosing a value: If CAS is also receiving data from one or more AMD devices, the interval at which it will generate its data records will be taken from the AMDs. If only NAM appliances are connected, however, you may need to explicitly set the length of the interval or leave it at the default value of 5 minutes. The corresponding configuration parameter (NAM_ZDATA_PERIOD) can also be modified on the User properties screen. 3. Optional: Enable AMD and NAM traffic deduplication. Choosing a value: If AMD and Cisco NAM monitor the same traffic and the same CAS receives data for software services from these devices, the mechanism for deduplication built in to the report server can be enabled. Use NAM_AMD_DEDUPLICATION_VALID_TIME, which you can access on the User properties screen. This property sets the number of minutes for which the report server will retain a record of those software service sessions that have been reported by AMDs. During this time, matching sessions reported by Cisco NAM devices will be marked as duplicate and discarded. You should set this feature to three times the size of the monitoring interval (in minutes). A value of zero disables the deduplication mechanism. You must restart the server to put your changes into effect. 4. Optional: Synchronize DCRUM service names with NAM application names. If the same traffic is monitored by AMD devices and NAMs, to avoid data duplication you should ensure that the service names defined for the AMDs are the same as the application names used by NAMs. The software services and NAM application mapping is configurable by NAM_APPLICATION_MAPPING property on the User properties screen. By default, mapping is turned off. The property has three values: off No mapping is effective, NAM application and software service names are mixed and duplication can occur when AMD and NAM monitor the same traffic. 31

32 Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring cisco-to-cpwr NAM application names take precedence and all software service names will be given NAM application names as defined in the mapping file. cpwr-to-cisco Software service names take precedence and all NAM application names will be renamed to software service names as defined in the mapping file. You must restart the report server to put your changes into effect. To synchronize application names reported by NAM appliances and software service names monitored by AMDs, the CAS uses a configuration file stored on the report server's hard disk in the config directory (for example: <install_dir>\config). The cisco-application-map.properties file contains a mapping of NAM application names to software service names. Each line is a pair of the form: cisco\u0020app\u0020name=compuware software service name where the spaces on the left side of the equation must be replaced by the string \u0020. The strings are not case sensitive. You do not need to restart server after changing this file. Example 1. Sample NAM application names to software service names mapping Cisco=Compuware Cisco\u0020name=Compuware name For information on how to define service names on DCRUM, see Basic Monitoring Configuration in the Data Center Real User Monitoring Web Application Monitoring User Guide. Attaching Cisco Network Analysis Module to RUM Console You can attach a NAM device to RUM Console using the standard Data Center Real User Monitoring procedure for attaching a data collecting device. For more information, see Adding Devices in RUM Console in the Data Center Real User Monitoring Administration Guide. Note that: You should leave the Secondary IP Address for this Device field empty. The device type you select should be Cisco NAM. After specifying connection details, you need to click Next to proceed to SNMP connection parameters. There you need to enter the read community name and the port number to be used for SNMP communication. This step is mandatory for devices of type NAM. 32

33 Configuring NAM 5 Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring Before You Begin To choose the right values in this procedure, you should be familiar with issues related to time synchronization and performance as described in Special Considerations for Using NAM in Data Center Real User Monitoring [p. 28]. You can designate any user account on your NAM device as the user who CAS will ask for data. This user needs to be granted the Monitor Config privilege so that the special Application host table is available to the NAM and so non-tcp data can be read from it. Figure 12. Enabling rights on NAM 1. Open the NAM Web Console. You can connect to your NAM directly by using a browser to open the devices' Web console. Alternatively, if you have already added the NAM to your RUM Console, you can use the context menu in the console's Devices view and select to open the NAM Console from there: right-click the NAM listed in the Devices view and select Open Cisco NAM Web Console. 2. Configure the NAM report interval length. Select the Data Aggregation Interval Settings screen Setup Monitoring Aggregation Intervals and define the Short Term Interval values to match the length of the monitoring interval used by the CAS installation you will be connecting to. It is advised that you set both Traffic/Media and Response Time to the same value as on the CAS. If data duplication is possible because traffic is being monitored by more than one NAM or AMD, you may need to set NAM report intervals to lower values, though this may degrade performance. It is also important that report interval for the NAM is an integer and that the CAS monitoring interval be a multiple of the NAM report interval. For more 33

34 Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring information, see Special Considerations for Using NAM in Data Center Real User Monitoring [p. 28]. 3. Adjust Refresh Interval. Select Administration Preferences to change Refresh Interval value. Enter the number of seconds equal to your monitoring interval. 4. Define NAM collections for Response Time monitoring. Data Center Real User Monitoring obtains data from NAM Response Time monitoring. Therefore, for the data to be available in Data Center Real User Monitoring, collections for Response Time monitoring have to be configured on the NAM device and their data sources indicated. On the NAM, go to Setup Monitoring Response Time to check whether any collections are currently created for Response Time monitoring. Create new collections for the traffic you want to monitor. 5. Specify NAM setup preferences. In NAM setup preferences, in Administration Preferences ensure that: The option to perform IP host resolution is not selected. Data is set to display in Bytes. International Notation is set to 1, Ensure time synchronization between NAM and CAS. The most reliable way to ensure time synchronization is to synchronize both devices to the same source server. To synchronize the NAM with an external time server, use the configuration options provided in the NAM Console, under Administration System System Time. For information on how to synchronize CAS to an external time server, see Time Synchronization with an External Time Server in the Data Center Real User Monitoring Administration Guide. 7. Ensure that the time interval at which the CAS will interrogate the NAM is appropriate for the report intervals defined on the NAMs. This interval should be less than the report interval defined on the NAM, and the difference between those two times should be at least equal to the time required for data generation and transfer from the NAM to the CAS. For more information, see Special Considerations for Using NAM in Data Center Real User Monitoring [p. 28]. 8. Optional: Synchronize DCRUM service names with NAM application names. If the same traffic is monitored by AMD devices and NAMs, to avoid data duplication you should ensure that the service names defined for the AMDs are the same as the application names used by NAMs. For information on how to define application names for a NAM, refer to the NAM documentation, and in particular to the Setting Up the Application chapter of the User Guide for the Cisco Network Analysis Module Traffic Analyzer. For more information, see Step 4 [p. 31]. 9. Optional: Configure NAM to provide voice statistics to DCRUM. Go to Setup Monitoring Voice and see if Enable Call Signal Monitoring is selected. 34

35 Attaching NAM to CAS After adding a NAM device to the RUM Console, you can use the RUM Console to attach your NAM to a CAS server. The procedure is in part the same as that for adding other data collectors, though some additional steps are required. Before You Begin Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring Attach the NAM device to the RUM Console and configure the NAM to generate data readable by CAS. For more information, see Attaching Cisco Network Analysis Module to RUM Console [p. 32] and Configuring NAM 5 [p. 33]. To attach a NAM to a CAS server: 1. Use the standard Data Center Real User Monitoring procedure for attaching a data collecting device to a report server. For more information, see Managing Report Servers in RUM Console in the Data Center Real User Monitoring Administration Guide. Before you save and publish the server configuration, you need to perform an extra step of selecting data sources. 2. Select NAM data sources to be used by CAS. NOTE If traffic information for a particular software service is received from a number of data sources, then: Only one data source will be used to generate reports for this service. The data source will be selected alphabetically. 1 Duplicate data for this service, coming from other data sources, will be discarded. This limitation does not apply to link-based reports (reports for individual data sources), which will always report all of the data for each link (data source). Note that the above implies that if a given service is seen on a number links (data sources) because of, for example, load balancing, only one data source will be chosen, resulting in partial loss of data. To select data sources, in the CAS Server Configuration window, right-click the NAM device and use the context menu to perform one of the two possible actions: Select individual data sources: Click Configure Cisco NAM Data Sources to open the Data Sources wizard. Once in the wizard, select which data sources from the device will be used by the report server. Select All Span data source: 1 The order is alphabetical by link alias name, though initially, when new data sources are added to CAS reports, the link names are derived directly from the names of the corresponding data sources. This can subsequently be changed by defining different alias names. 35

36 Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring Click Assign ALL SPAN Cisco NAM Data Source to assign the ALL SPAN data source to the report server. This operation can be performed on a number of selected devices at once. Note that even though ALL SPAN is an aggregate of all the data sources for the device, it is possible to select it and at the same time select other data sources for that device. Above de-duplication rules will then apply. 3. In the CAS Server Configuration window, click Save and continue changing server configuration, or click Save and Publish to save and immediately publish your configuration changes. Scalability and Capacity Considerations CAS capacity depends on the number of monitored sessions (conversations), which are unique combinations of client IP, server IP, port, and URL. It does not depend on the number of the attached data collectors. However, performance problems may occur if data collectors are unable to provide data within sufficient speed or frequency. NOTE The time interval at which CAS will interrogate NAM should be less than the report interval defined on NAM, and the difference between those two times should be at least equal to the time required for data generation and transfer from NAM to CAS. For more information, see Special Considerations for Using NAM in Data Center Real User Monitoring [p. 28]. One of the implication of this limit is that if you are reducing the length of the report interval on a NAM because, for example, you want to reduce data duplication errors, you should not reduce the interval below the value that would conflict with the above requirement. It is recommended that at least 20 seconds be left for a NAM to export its data to a file and make the file available for CAS. Using NAM to Report Voice and Video Statistics in DCRUM Cisco Network Analysis Module can be used to report voice and video data to the Central Analysis Server. You will be able to use voice and video related reports after attaching NAM to the report server. Note that integrating NAM with DCRUM is an extension of the existing functionality, as the CAS is capable of reporting VoIP data monitored by Network Monitoring. This means that if you combine all three solutions the data presented by the CAS reports will be mixed. Note also that if you are using only NAM as voice and video monitoring source you may see empty columns or charts due to limited number of statistics NAM provides. NOTE You should not configure NAM and Network Monitoring Probe to monitor the same VoIP traffic. Should this happen, ensure to configure software service names to indicate which portion of traffic they concern. Do not use identical names in these two products. 36

37 Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring Differences between NAM and DCRUM terminology The main source for voice and video metrics and dimensions is the NAM RTP Stream Traffic table. To leverage reporting CAS uses statistics provided in other tables as well. Table 4. Mapping of NAM and DCRUM VoIP dimensions NAM Source Addr: Port Dest Addr: Port Payload Type Status DCRUM Endpoint host name Endpoint host name Software Service - Comment The value is changed based on the data acquired form the Known Phones table. The IP address is mapped to phone number. The value is changed based on the data acquired form the Known Phones table. The IP address is mapped to phone number. Names are synchronized based on mapping contained in the CAS dictionary file. For more information, see Step 4 [p. 31]. The status is not directly reported on CAS reports: For active calls (that is the ones that did not end within a given monitoring interval) only bytes and packets are shown. For inactive streams all VoIP metrics are reported. Table 5. Mapping of NAM and DCRUM VoIP metrics NAM Worst MOS Adj Pkt Loss (%) Jitter (ms) - DCRUM MOS VoIP loss rate VoIP Jitter Calls Total bytes Comment Calculated based on merged data for the number of conversations between hosts. A call on DCRUM reports is equal to a conversation between a pair of IP addresses reported by NAM. Additional metrics acquired from other NAM tables. Several voice and video dimensions and metrics are not imported from NAM: Dimensions SSRC Start Time 37

38 Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring Metrics Act Pkt Loss/million Total SSC Troubleshooting If voice monitoring is enabled ensure also that NAM tables contain the requested data. For example if you cannot see phone numbers on the reports, log in to NAM and verify data in the Known Phones table. If other VoIP statistics are not reported by the CAS make sure they exist in the RTP Stream Traffic table. Using NAM to Report Optimized WAN Statistics in DCRUM Cisco Network Analysis Module is capable of reporting WAN optimization data to Data Center Real User Monitoring report server. Data obtained from Cisco NAM will be available in custom reports created in DMI. If you plan to monitor WAN optimization controllers (WOCs) and generate reports of the optimized WAN traffic, the following configuration will allow you to utilize the data gathered by Cisco NAM. The essential part of reporting optimized WAN using NAM data is creating and defining the appropriate data sources. While creating a data source in NAM, make sure that the Wide Area Application Services (WAAS) is selected as a data source type, and the appropriate WAAS segments are selected. The following WAAS segments are available: Client Client WAN Server WAN Server Pass-through Once the Cisco NAM data sources are properly defined, they can be used to present data to Data Center Real User Monitoring report server. You can assign NAM data sources to the report server using the RUM Console. 1. Open the Data Center Real User Monitoring report server configuration in the RUM Console. 2. On the Assigned devices tab, locate the Cisco NAM device assigned to the report server. 38

39 Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring NOTE If your Cisco NAM device is not listed, check the list of devices managed by the RUM Console and add the your NAM device to the RUM Console and to the report server configuration. For more information, see Adding Devices in RUM Console in the Data Center Real User Monitoring Administration Guide and Adding and Editing Devices in a Report Server Configuration in the Data Center Real User Monitoring Administration Guide. 3. Right-click the Cisco NAM device and select Configure Cisco NAM Data Sources from the menu. 4. Select appropriate data sources from the Available Cisco NAM Data Sources list and move them to the Assigned Data Sources list. Figure 13. Selecting Cisco NAM data sources for optimized WAN monitoring Adding NAM data sources to Data Center Real User Monitoring report server in order to view the optimized WAN statistics requires selecting at least three WAAS segments defined as Cisco NAM data sources. 5. Click OK to save changes. 39

40 Chapter 3 Using Cisco Network Analysis Module in Data Center Real User Monitoring 40

41 CHAPTER 4 WAN Optimization Reports Configuring WAN optimization in DCRUM allows for more precise analysis of the defined sites, links, software services, and individual operations. A typical user viewing the Tiers report can quickly assess the performance of the WAN optimization service. For example, let's assume that while viewing the Tiers report, you notice in the Network Tiers table that the Client optimized network tier is not performing as expected. Drilling down in the optimized tier will reveal the report displaying defined sites. At this point, you can quickly ascertain whether the problem occurs with a given Client site, potentially identifying an issue with a specific application, load distribution, or misconfigured WAN Optimization Controller (WOC) at the branch end. You can also determine whether the problem is with all sites, which could indicate a problem with the local WOC or with a common application for all sites. Examining the Sites report you can drill down to the best or the worst performing link within the Client site and review the breakdown of the applications relating to that link. Once again, you can assess whether the problem relates to one specific application or to the entire link. Single application failure or performance downgrade could suggest a failed optimization policy for that service or indicate that this particular application is not suitable for optimization. Often, just the knowledge of a particular application performing poorly is not enough to determine the cause of the performance issue. By clicking the specific Application on the Applications for Site report, you will drill down to a Transactions for Site report. This report will present the selected application broken into individual transactions. 41

42 Chapter 4 WAN Optimization Reports 42

43 APPENDIX A Metrics Related to WAN Optimization Adjustment The following metrics are applicable while monitoring WAN optimization environment with Compuware APM. 50pc ADCD The 50th percentile of the ADCD metric. 80pc ADCD The 80th percentile of the ADCD metric. 85pc ADCD The 85th percentile of the ADCD metric. 90pc ADCD The 90th percentile of the ADCD metric. 95pc ADCD The 95th percentile of the ADCD metric. 99pc ADCD The 99th percentile of the ADCD metric. Application Delivery Channel Delay In WAN optimized scenario, Application Delivery Channel Delay (ADCD) is a quality metric represented in milliseconds. The ADCD is determined by initial observation of the traffic between a client and a server. ADCD is a derivative of RTT measured on a WAN link expressed in time and as such it can be understood as latency, where the larger ADCD would indicate a higher network latency. ADCD also includes time spent in the data center WOC for traffic buffering and processing. A change of ADCD from its initial value reflects a change of quality in WAN optimization service. For example, sudden increase of ADCD would suggest that the quality of the service has worsened and conversely, a sudden decrease of ADCD value could suggest an improvement in WAN optimization. Client site UDL A dimension designed to filter only the User Defined Links. By default it is set to true (Yes) for WAN Optimization Sites report. LAN-WAN byte ratio The amount of compression performed and expressed as a percentage. 100% for pass-through. 43

44 Appendix A Metrics Related to WAN Optimization Adjustment Greater than 100% if more bytes on the WAN side, including both pass-through and optimized traffic. Less than 100% if fewer bytes on the WAN side, including both pass-through and optimized traffic. Max ADCD The maximum of the ADCD metric. Min ADCD The minimum of the ADCD metric. Percentage of optimized traffic (bytes) Indicates the traffic distribution in two separate branches: optimized traffic and passed-through traffic. The higher the value, the more bytes are optimized. Low values may indicate poorly configured optimization or optimization device overload. Stdv ADCD The standard deviation of the ADCD metric. Total bytes compression The data optimization observed, expressed as a byte reduction and a percentage, where a lower byte count on the WAN side means a higher reduction: 0% for pass-through. Less than 0% if more bytes were observed on the WAN side, including both pass-through and optimized traffic. Greater than 0% if fewer bytes were observed on the WAN side, including both pass-through and optimized traffic. This metric should not exceed 100%. Total bytes on LAN side The sum of bytes (client's and server's) observed on the LAN side before network traffic is directed into the WAN Optimization Controller (WOC). Total bytes on WAN side The sum of bytes (client's and server's) observed on the WAN side after network traffic leaves the WAN Optimization Controller (WOC), including bytes that have been passed through and those that have been marked as optimized. Altered Perspective Reports Adding any WAN Optimization metric or Link-related dimension to the Monitored traffic data view will change the perspective of that report. This action will automatically disable deduplication for the report, altering the values of certain metrics, and, as a result, the report will display the WAN Optimization metrics combined with values observed locally. For example, a report displaying Total bytes for a specific software service will display a different value for the same Total bytes metric if that report contains metrics associated with an optimized WAN or a dimension associated with a Link. 44

45 Appendix A Metrics Related to WAN Optimization Adjustment Example 2. An example report with altered perspective To create a report showing a change of perspective: 1. Open the Data Mining Interface screen. 2. Select Software service as a dimension and select Total bytes as a metric. Optionally you can select a filter for a known software service, such as www. 3. Create two duplicates of the created section by clicking the (Duplicate section) icon twice. 4. Add Total bytes on WAN side and Total bytes on LAN side metrics to the first duplicated section metric list. Optionally, for a better visual representation, you can move the Total bytes on WAN side and Total bytes on LAN side metrics to the top of the metrics list. 5. Add the Link name dimension to the list of dimensions for the second duplicated section. 6. Click Display report. Figure 15. A report presenting a change of perspective The first table displays the proper Total bytes (330) observed for the www software service. The second table displays the same Software service and the same Total bytes metric, but, because WAN Optimization metrics were added to the second section, deduplication has been automatically disabled, altering the final Total bytes value (616). The third table also displays the same Software service and the same Total bytes metric. However, in this table, because Link name has been added as a dimension, the Total bytes indicated is broken down per defined Link name. The sum of the Total bytes values will equal the Total bytes value displayed in the second table, indicating that the perspective of this report has changed and that deduplication has been automatically disabled. 45