Data Center Real User Monitoring WAN Optimization Getting Started Release 12.2.0
Please direct questions about Data Center Real User Monitoring or comments on this document to: Customer Support https://community.compuwareapm.com/community/display/support Copyright 2014 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 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (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 https://community.compuwareapm.com/community/display/apmdoc. Compuware, FrontLine, Network Monitoring, Enterprise Synthetic, Server Monitoring, Dynatrace Network Analyzer, Dynatrace, VantageView, Dynatrace, Real-User Monitoring First Mile, and Dynatrace Performance Network are trademarks or registered trademarks of Compuware Corporation. Cisco is a trademark or registered trademark of Cisco Systems, Inc. Internet Explorer, Outlook, SQL Server, Windows, Windows Server, and Windows Vista are trademarks or registered trademarks of Microsoft Corporation. Firefox is a trademark or registered trademark of Mozilla Foundation. Red Hat and Red Hat Enterprise Linux are trademarks or registered trademarks of Red Hat, Inc. J2EE, Java, and JRE are trademarks or registered trademarks of Oracle Corporation. VMware is a trademark or registered trademark of VMware, Inc. SAP and SAP R/3 are trademarks or registered trademarks of SAP AG. 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. Local Build: December 8, 2014, 14:50
Contents Contents Introduction...................................................... Who Should Read This Guide.......................................... Organization of the Guide............................................. Related Publications................................................. Customer Support Information......................................... Reporting a Problem................................................. Documentation Conventions........................................... Chapter 1 WAN Optimization Overview............................... Chapter 2 WAN Optimization Adjustment in DC RUM.................... 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 for Earlier Version AMDs............................. 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 Dynatrace to Recognize Optimized WAN Traffic.................. WAN Optimization and SSL........................................... WAN Optimization Configuration Summary............................... Chapter 3 WAN Optimization Reports................................. Appendix A Metrics Related to WAN Optimization Adjustment............. Altered Perspective Reports........................................... 5 5 5 5 6 6 6 9 11 12 13 14 14 15 16 16 17 18 19 19 20 21 22 22 23 24 25 27 28 3
Contents Appendix B Known Restrictions in WAN Optimization Support............. 31 4
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 DC RUM [p. 11] Describes how to deploy and configure DC RUM to provide performance data measurement adjustment for WAN optimization. WAN Optimization Reports [p. 25] Describes WAN optimization related reports. Metrics Related to WAN Optimization Adjustment [p. 27] Provides referential information on metrics related to WAN optimization. Known Restrictions in WAN Optimization Support [p. 31] Lists known issues and restrictions in WAN optimization support in DC RUM. Related Publications Documentation for your product is distributed on the product media. For Data Center RUM, it is located in the \Documentation directory. It can also be accessed from the Media Browser. Go online (https://community.compuwareapm.com/) for fast access to information about your Dynatrace 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. 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 http://www.adobe.com/downloads/. 5
Introduction Customer Support Information Dynatrace Community For product information, go to https://community.compuwareapm.com/ and click Support. You can review frequently asked questions, access the training resources in the APM University, and post a question or comment to the product forums. You must register and log in to access the Community. Corporate Website To access the corporate website, go to http://www.dynatrace.com. The Dynatrace site provides a variety of product and support information. Reporting a Problem Use these guidelines when contacting APM Customer Support. When submitting a problem, log on to the Dynatrace Support Portal at https://support.compuwareapm.com/, click the Open Ticket button and select Data Center Real User Monitoring from the Product list. Refer to the DC RUM FAQ article at https://community.compuwareapm.com/community/display/dl/dcrum+data+collection+guide to learn know how to provide accurate diagnostics data for your DC RUM components. Most of the required data can be retrieved using RUM Console. Documentation Conventions The following font conventions are used throughout documentation: This font Bold Citation Documentation Conventions [p. 6] Fixed width Fixed width bold Fixed width italic 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 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 6
Introduction This font Menu Item Screen Code block Indicates Menu items. Text screen shots. Blocks of code or fragments of text files. 7
Introduction 8
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
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 can accelerate end-user experience significantly. NOTE Application optimization monitoring is not supported in the current version of DC RUM. 10
CHAPTER 2 WAN Optimization Adjustment in DC RUM WAN optimization adjustment in DC RUM is designed to make your deployment aware of WAN optimization in the network and able to rectify measurements that might be skewed by optimization. DC RUM 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. DC RUM 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, DC RUM 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
Chapter 2 WAN Optimization Adjustment in DC RUM 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, DC RUM 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, Dynatrace 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 Dynatrace 12.3 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 Dynatrace. 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 flow can be mirrored to the AMD simulating the in-path deployment); otherwise, DC RUM would not be able to provide correct measurements. 12
Chapter 2 WAN Optimization Adjustment in DC RUM For details on deployment models for your Steelhead appliances, 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. Dynatrace 12.3 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 enables the AMD to observe the network traffic within your WAN optimization deployment and report the performance of the WAN-optimized network and applications. An AMD monitoring all network traffic at 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
Chapter 2 WAN Optimization Adjustment in DC RUM 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 by type, the more precise the analysis of your WAN optimization performance will be. The minimum configuration to monitor WAN optimization performance is identifying the optimized WAN traffic on the WAN side. 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 the traffic type within your LAN infrastructure is optional, but classifying at least one of the traffic types on the LAN side enables you to gather more precise optimization measurements and to improve the 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 therefore that identification of optimized WAN traffic is required. After the specific network traffic on the WAN side has been identified as WAN optimized, the rest of the network traffic (the LAN side) is automatically classified as regular LAN traffic (Datacenter LAN). However, traffic on the LAN side that is matched with the traffic on the WAN side is 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, but the LAN side relies on automatic detection and matching of optimized WAN and LAN traffic, so this configuration 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 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 14
Chapter 2 WAN Optimization Adjustment in DC RUM 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 is 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 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 is classified as datacenter LAN traffic (Datacenter LAN). Use a configuration like this to separate 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 using the connections that are optimized. Figure 5. Monitoring Scenario for Identification of WAN Traffic and Regular LAN Traffic 15
Chapter 2 WAN Optimization Adjustment in DC RUM 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 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 enables more precise measurements, but it requires more 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 monitored as part 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 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
Chapter 2 WAN Optimization Adjustment in DC RUM When virtual in-path deployment is in use, WAN traffic is often redirected by the routing device and the WOC device. It is important to identify traffic belonging to the WAN optimized network and separate it from all other traffic. Typically, the WAN optimized network is identified by VLAN, MPLS, or GRE/WCCP values in the monitoring point rules, and the following rule 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 a 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 limits 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
Chapter 2 WAN Optimization Adjustment in DC RUM VLAN (optional) VLAN tag. If the No VLAN in traffic check box is selected, 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 an MPLS-based network. If the No MPLS in traffic check box is selected, 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. Enter the WCCP System ID that is running in GRE tunnel. The Dynamic service identifier can be a number from 0 to 254 and can be obtained from your router by running the show ip wccp command at the router's command prompt. Select the check box when your traffic does not use WCCP in GRE tunnel. If the No GRE/WCCP in traffic check box is selected, 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 for Earlier Version AMDs The following deployment models refer to AMD versions 12.0.1 or earlier. Even when using the latest console release, the earlier deployment model will be used to configure AMD running software version 12.0.1 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. 18
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, 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 Chapter 2 WAN Optimization Adjustment in DC RUM 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
Chapter 2 WAN Optimization Adjustment in DC RUM 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
Chapter 2 WAN Optimization Adjustment in DC RUM 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 102 104 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. 3. A point within your LAN infrastructure that can be used to exclude a LAN segment to achieve more accurate WAN optimization measurements. 21
Chapter 2 WAN Optimization Adjustment in DC RUM For each sniffing point you define, identify the type of traffic being monitored by specifying one of the following: 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. The 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 DC RUM 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 DC RUM and is actively monitored. Configuring Dynatrace to Recognize Optimized WAN Traffic All AMDs that monitor network traffic using WAN optimization must be configured before Dynatrace can automatically recognize optimized WAN traffic. Use the RUM Console to configure and propagate the configuration to all your AMDs. Before You Begin The following information is required for configuration: The deployment model of your WAN optimization. The manufacturer of your WOCs. 22
Chapter 2 WAN Optimization Adjustment in DC RUM 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. To make Dynatrace 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 on to RUM Console. 2. Select Devices and Connections Manage Devices from the top menu, to display the current device list. 3. Select Open Configuration from the context menu for an AMD. The AMD Configuration window appears. 4. Click Edit as Draft to set your configuration to draft mode (if you are not in draft mode already). 5. In the Configuration tree, open Global and click WAN Optimization to open the WAN optimization screen. 6. Select the Enable WAN optimization adjustment check box. 7. In the Deployment model section, select one of the predefined deployment models for your WAN optimization. 8. Select a WAN acceleration engine vendor. 9. In the Sniffing points section, enter a Name for each of your sniffing points. This enables you to identify your sniffing points while creating and viewing reports. 10. 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. 11. 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. 12. 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. 13. Publish the draft configuration on the monitoring device. WAN Optimization and SSL While the typical network and software services can be optimized using standard optimization methods, encrypted network traffic requires special consideration. 23
Chapter 2 WAN Optimization Adjustment in DC RUM 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, 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 Dynatrace, 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 user-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. The Optimized client network tier is created automatically based on data received from the AMD. 24
CHAPTER 3 WAN Optimization Reports Configuring WAN optimization in DC RUM 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. 25
Chapter 3 WAN Optimization Reports 26
APPENDIX A Metrics Related to WAN Optimization Adjustment The following metrics are applicable while monitoring WAN optimization environment with Dynatrace. 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. 27
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 Software service, operation, and site data 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. 28
Appendix A Metrics Related to WAN Optimization Adjustment Example 1. Example Report with Altered Perspective To create a report showing a change of perspective: 1. Choose Reports DMI Define Simple Report from the top menu. 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. Click Back to report definition. On the Sections and Layout tab, click 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 12. Report Presenting a Change of Perspective The first table displays the proper Total bytes (330) observed for the www software service. 29
Appendix A Metrics Related to WAN Optimization Adjustment 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. 30
APPENDIX B Known Restrictions in WAN Optimization Support The AMD attempts to match the monitored LAN traffic with the corresponding WAN traffic and to calculate the operation time and other WAN optimization-related metrics as precisely as possible. When you observe data inconsistency on the reports, consult the following sections to identify your particular case. WAN Optimized Links are not recognized on the master CAS server In a deployment in which master and slave CAS instances are analyzing monitored traffic but the AMD is attached to the slave CAS only, the master CAS will not be able to recognize WAN Optimized Links even if the RTM_AUTO_WANOPT_DISCOVERY property is set to ON on both CAS servers. This limitation is caused by the master to slave synchronization design. Although the slave CAS is able to accept the configuration from the master CAS, the master CAS, by design, does not accept configuration from any slave CAS. To resolve this situation, the WAN Optimized links in question have to be added to the master CAS server manually, using an external file method. For more information, see Formatting the Site, Area, and Region Definitions in the Data Center Real User Monitoring Administration Guide. Difference between measurement methodologies of Riverbed Technology and Data Center Real User Monitoring CAS reports may display data that differs from the data displayed in the built-in reports available on Riverbed Technology Steelhead devices. Steelhead reports are related to application-level data, while data displayed in Data Center Real User Monitoring reports are at the network level. As a result, their reported volume measurements and compression ratios are different and should not be compared. Missing measurements In certain situations, the AMD is not able to capture and analyze traffic, which means that the WAN optimization adjustment cannot be calculated as usual. When this happens, operation 31
Appendix B Known Restrictions in WAN Optimization Support time and ADCD are instead calculated based on the value of RTT over the WAN link, because the WAN RTT is the closest available approximation of ADCD. Such situations on average do not exceed 0.2% of the total TCP operations to be optimized and carried over WAN links. AMD running in a virtual machine environment In general, the AMD can be effectively installed and operated on a virtual machine. If the AMD is running on a virtual machine and monitoring WAN optimization, however, the measured data will be affected due to time stamp fluctuations. To monitor your WAN optimization infrastructure, you should use physical machines for AMDs. WAN Optimization Controller (WOC) caching discrepancies Some WOC appliances can cache data for a quicker response from the client. This may cause measurement discrepancies between data observed by the WAN optimization enabled AMD on the server side and the End-User Experience data observed by the AMD on the client side. This occurs because the WOC appliance itself is answering the client requests from its cached data instead of the server, so not all of the traffic can be observed and measured on the data center side. The discrepancies that may occur in this situation vary depending on the protocol you are monitoring and the WAN optimization options that are enabled. WAN Optimization reports can show questionable data The WAN Accelerated Environment performance report differentiates the WOCs by using the User Defined Links (UDL) and defined Sites. Since the WAN optimization-enabled AMD monitors the WAN and LAN traffic only by the server, it is not possible to recognize the user name in the optimized WAN traffic, so user-defined links and sites cannot map the locations based on user names. The reports will present reliable data only if the locations are determined by IP address. For more information, see Configuring Sites, Areas, and Regions in the Data Center Real User Monitoring Administration Guide and Adding Sites Manually in the Data Center Real User Monitoring Administration Guide. 32