Strengthen Your WAN Strategy
Whether tracking WAN performance or verifying a cloud service provider's SLA, network analyzers play a comprehensive role in monitoring, troubleshooting, and enforcement. Learn how to strengthen your WAN management strategy with Observer's WAN analysis and performance insight.
     
   
  Preparing for WAN Acceleration
Over the past few years, we have seen server consolidation occurring for many reasons ranging from security to virtualization and simple cost-cutting efforts. In addition to consolidation at the core, users are more distributed accessing the network from a variety of locations including remote and home offices and smart phones.

Having an increased number of remote users accessing applications on fewer servers can introduce significant bandwidth and latency issues. Applications are typically designed to operate in LAN environments, and may not function well when accessed via WAN. In this article, we'll look at using WAN acceleration technologies to address latency issues, types of WAN accelerators, and key issues when deploying WAN accelerators.

Overcoming WAN Performance Problems
To overcome WAN performance constraints and address latency and delay issues many have turned to WAN acceleration solutions. WAN accelerators speed the delivery of applications by eliminating redundant transmissions, staging data in local caches, and compressing and prioritizing data. WAN accelerators generally perform their task via three methods:

Tokenization: Saves bandwidth by ‘remembering’ chunks of data at each accelerator and forwarding tokens as reference points for data previously transmitted, rather than sending the same data over and over. When a token is received, the local accelerator swaps the received token for the referenced data to be forwarded from its local memory. This method works well for most applications with the occasional exception of digital scanner systems.

Compression: Likely the most effective method of acceleration, it compresses the raw data before sending. Data is then uncompressed on the remote machine unbeknownst to the user.

Caching: Data sent to a remote site is cached locally and synchronized at scheduled times, thus allowing content to be sent at off-peak times. This method can greatly reduce the amount of data sent over WAN links during normal work hours. Having data stored locally speeds its delivery to remote offices, and can allow them to function even if the WAN is down. When WAN service is restored, there can be issues with recompiling the newly cached data at each remote site with the core data.

The type of acceleration used will depend upon your goals, the applications you're optimizing, and network devices and configuration. For example, if you have implemented Quality of Server (QoS) for WAN prioritization, you'll want to understand whether the WAN accelerator will impact application QoS settings.

Deployment Preparations
Now let's look at five key considerations your network team will want to make before rolling out any type of WAN optimization device.

1) Define the applications traversing the WAN and identify the underlying protocols and codecs. You'll want to understand how each of these protocols is impacted by different types of acceleration. In the case of VoIP, for example, g.711 codec's quality will be impacted when traversing the WAN, whereas g.729 would only be minimally affected.

2) Understand which stations are communicating across the WAN and their locations. Ensure that equipment and stations are placed correctly for optimizing WAN performance. If you have multi-tiered applications with web frontends interfacing with SQL servers accessing a database to pull objects, it is best to keep the SQL packets local to one network and not flooding the WAN with 80-byte packets.

3) Define baseline measurements for application utilization and performance, including utilization throughout the day, application response times, and when operations should occur. Are backups taking too long, or occurring during peak demand times?

4) What is the actual latency for WAN links? It's important to understand whether latency is significant enough of an issue to justify WAN acceleration. A rule of thumb is if latency is above 45 ms, it is worth considering WAN acceleration.

5) Optimize applications by pinpointing delay locations. The WAN is an easy target to blame, however, the backend core processes are frequently the more likely culprit. Issues experienced by users when accessing the WAN may actually be attributed to the LAN, but due to proximity and bandwidth issues they may not be easy to detect. Acceleration in this case may help but not be as effective in resolving delay issues as making configuration changes at the core.

In Conclusion
As more users access applications from remote locations over the WAN, it will be critical for you to ensure a positive user experience. WAN accelerating technology is an attractive way to enhance application delivery while reducing bandwidth needs. The key to successfully deploying WAN optimization technology is to be aware of how acceleration will impact application delivery and quality and understanding the source of delay to improve troubleshooting. In the Tech Spotlight, we'll discuss using Observer® to prepare the network for a WAN acceleration deployment as well troubleshooting WAN performance problems

     
   
  Fine-Tuning WAN Acceleration with Observer
In the In Practice section, we discussed using WAN acceleration to reduce bandwidth demand and increase application delivery. In addition, we looked at key considerations for a successful rollout. Let's discuss how Observer helps with evaluating, optimizing, and troubleshooting WAN performance before and after rolling out WAN optimization technology.


  1. Auto-Baselining
    Run auto-baselining frequently to establish application performance baselines and compare application response and operation times over time. For example, verify that applications such as back-ups and software updates are running as scheduled and not impeding other business functions. Sometimes, operations can take longer to complete, which can indicate a problem. Second, before implementing WAN acceleration, it's important to understand response and completion time, so that you can identify and measure any improvements post deployment. (See how to set up Auto-Baselining.)


    To view Auto-Baselining reports:
    Main Menu > Trending/Analysis > Start Web Browser Report > select Application Transaction Analysis or Application Performance Analysis Baselining Report


  2. Application Transaction Analysis (ATA)
    ATA plays a critical role in allowing you to identify the specific point of an application delay and whether the point of delay was caused by the application traversing the WAN. (See how to set up ATA.)

    To view ATA:
    Main Menu > Trending/Analysis > Application Transaction Analysis


  3. VoIP Expert Events
    In converged networks with VoIP, it can be difficult to isolate the source of delay. VoIP Expert Events is critical for identifying the impact traversing the WAN may have on calls, as well as isolating specific problem points in a VoIP call. You'll also be able to monitor VoIP in relationship to other applications on the network. (See how to set up VoIP Expert Events.)

    To view VoIP Events:
    Capture > Packet Capture > Start Capture > Decode > Expert Analysis Tab > VoIP Events


  4. End-to-End Analysis
    Quickly identify whether delay issues occurred on the WAN or at the server or client. (See how to set up Server Analysis.)

    View Sever Analysis:
    Main Menu > Trending/Analysis > End-to-End Server Analysis


  5. MultiHop Analysis
    Once delay has been identified, use MutliHop Analysis to pinpoint the specific network segment or hop where delay occurred on the WAN. (See how to set up MultiHop Analysis.)

    View MultiHop Analysis:
    Main Menu > Trending/Analysis > MultiHop Analysis



     
 
november 2009  


Last Month's Answer
Routers operate at Layer 3 (network layer) of the OSI model.

Congrats to last month's winner, Alfred Kaeppeler of Karlsruhe, Germany.

This month's question:
A router that has eight ports will require how many IP addresses?

Submit your answer and be entered to win a Network Instruments® polo shirt.

5 Cloud Keys
Tips to avoid cloud computing failures

What's New in Observer 14?
Explore top new features

NetFlow's Limitations
How to broaden NetFlow visibility

NIU Dallas
December 7-10