Sawx01 1

e d u c a t io n se rv ic e s c o u rse w a re
WAN Acceleration Appliances

Student Guide
NOTE: Please note this Student Guide has been developed from an audio narration. Therefore it will have
conversational English. The purpose of this transcript is to help you follow the online presentation and may require
reference to it.
Slide 1
© 2010 Juniper Networks, Inc. All rights reserved. | www.juniper.net | Proprietary and Confidential
Welcome to Juniper Networks WAN Acceleration Appliances eLearning module. WAN acceleration may be perceived
to be a bit of a niche market and, admittedly, it is. However, it’s a market where Juniper can demonstrate some real
strength and also provide a value added service to our customers. These days, all of our customers are quite
financially challenged. IT managers basically have to do more with fewer resources. That’s a problem that WAN
acceleration helps solve.
WAN acceleration is an undefined technology. It’s open to vendor interpretation. This course explains Juniper’s
interpretation of WAN acceleration, why Juniper’s interpretation is so broad, what value add Juniper brings to the
market place and, most importantly, what some of the differentiators are between Juniper and many of our
competitors in the industry.
As mentioned, Juniper has some real strength in the WAN acceleration market, making it a good entry into traditional
non-Juniper accounts. With WAN acceleration, you’re able to establish a strong foothold, and then customer
satisfaction with it can open the door to introduce some of the more traditional Juniper products – such as routers,
switches, and security products.
Course SAWX01A © Juniper Networks, Inc. 2

Slide 2
© 2010 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SAWX01A www.juniper.net | 2
Throughout this module, you will find slides with valuable detailed information. You can stop any slide with the Pause
button to study the details. You can also read the notes by using the Notes tab. You can click the Feedback link at
anytime to submit suggestions or corrections directly to the Juniper Networks eLearning team.

Slide 3
Course Objectives
 On completing this course, you will be able to:

•Provide an overview of the WAN acceleration marketplace
•Discuss Juniper Networks WAN Acceleration product
•Discuss some of the applications that work with the WAN
acceleration product
•Describe the two main competitors to Juniper Networks
WAN acceleration product, and list their strengths and
weaknesses
•Understand technical information and details behind the
WAN acceleration product
•Describe reports that are involved with the WAN
acceleration product
Upon completing this course, you will be able to:

•Provide an overview of the WAN acceleration marketplace
•Discuss Juniper’s WAN Acceleration product
•Discuss some of the applications that work with the WAN acceleration product
•Describe the two main competitors to Juniper’s WAN acceleration product, and list their strengths and weaknesses
•Understand technical information and details behind the WAN acceleration product, and
•Describe reports that are involved with the WAN acceleration product

Slide 4
Agenda: WAN Acceleration Appliances
 WX Series Market Overview

 Product Introduction
 Applications
 Competition
 Reports
 WX Client
This course consists of six sections. The six main sections are provided in sequential order and are titled as follows:
• WX Series Market Overview
• Product Introduction
• Applications
• Competition
• Reports, and
• WX Client

Slide 5
WX Series Market Overview
WX Series Market Overview

Slide 6
Section Objectives
 After completing this section, you will be able to:

• Understand the conflict going on in the distributed
enterprise
• Describe current branch office trends
• Explain how the WAN slows applications
• Describe how the Juniper Networks WAN acceleration
product provides a framework for addressing some of the
problems facing the distributed enterprise
After completing this section, you will be able to:

•Understand the conflict going on in the distributed enterprise
•Describe current branch office trends
•Explain how the WAN slows applications, and
•Describe how the Juniper WAN acceleration product provides a framework for addressing some of the problems
facing the distributed enterprise

Slide 7
Conflict in the Distributed Enterprise
Business Objectives
 Reduce costs
 Increase productivity
 Ensure regulatory compliance
IT Objectives User Objectives

 Consolidate servers,  Get instant response
data centers times
 Simplify administration,  Collaborate easily
backup, and recovery and readily
 Reduce branch office  Avoid complexity
equipment and staff
There’s a conflict going on in the distributed enterprise. On the left hand side you see the objectives of the IT
organization. Based upon the business objectives at the top, IT needs to consolidate data centers, consolidate
servers, simplify the administration of all these resources, and also reduce branch office equipment and the IT staff
needed to maintain it.
This is consistent with the overall business objectives of cost reduction, productivity improvement, and even regulatory
compliance. If all of these resources are in one location, it’s much easier to monitor compliance for those resources.
The boxing gloves come into play where user objectives are concerned. Users are distributed to remote offices with
limited bandwidth and they are fighting response time issues, collaboration issues, and the overall complexity of the
system.

Slide 8
Branch Office Trends

DMZ www.company.com
Internal security Content Wi-Fi Bandwidth usage

protection Direct Internet Split Internet
No IT staff tunneling Remote
management HQ
 Number of branch offices (all sizes) to grow

approximately 6.5% annually
•Increased migration towards the branch/remote offices
(from ~85% of employees in the branch in 2003 to 91%
today) – Nemertes Research
 By 2008, 50% of the companies surveyed will
significantly increase their WAN access bandwidth—
Infonetics
Despite the conflict shown in the previous slide, the trend is definitely to distribute employees to more and more
branch offices or even home offices. At this point, for any major organization approximately 90% of employees are in
branch or remote offices.
The good news for all us networking people is that over half the companies surveyed realize they have to significantly
increase their WAN bandwidth over the next year or two in order to satisfy their users and branch offices. That, of
course, is at odds with the financial constraints that all of our customers have to endure. And that’s a good segue for
WAN acceleration.

Slide 9
How the WAN Slows Applications
Manageability
Application
Contention
SAP
Limited Oracle
The WAN Pipe
Bandwidth Web
VoIP
Latency
Lower-priority apps slow

More rich content Protocol chattiness
down critical ones
Inability to understand application and WAN performance
This is a quick look at the traditional problem that all of the branch offices have to endure. There is limited bandwidth
and they have to cram all their applications through that limited pipe. Some folks use the analogy of trying to force a
fire hose’s worth of data through a soda straw. It doesn’t really matter what the applications are. In all cases, if they
are bandwidth constrained, that becomes a problem.
But the problem is a little broader than that because bandwidth itself doesn’t necessarily provide the solution. The old
adage that bandwidth solves all Quality of Service (QoS) issues may play in the LAN, but not in the WAN. The reason
is that the chattiness of some of these protocols is their own worst enemy. That means even though these protocols
are waiting for acknowledgements, throwing more bandwidth at the problem doesn’t deliver the acknowledgements
any faster – and that’s because latency is also a factor.
From a WAN acceleration perspective, we certainly need to look at bandwidth, but latency also needs to be
considered, as do the applications. This changes the role of the traditional networking SE. Instead of just being in a
“plumbing” business, if you will, they now have to get into the actual applications in order to provide their customer
with a true WAN acceleration solution.
Course SAWX01A © Juniper Networks, Inc.

10
Slide 10
Key Business Initiatives: Cut Costs;

Improve Productivity
 Avoid WAN upgrade  Improve user

productivity
 Increase access to
shared resources  Centralize servers
 Improve disaster  Consolidate data
recovery centers
 Enable new  Achieve regulatory
application compliance
rollout
 Reduce time to  Enable VoIP, other

troubleshoot money-saving apps
 Automate remote  Ensure critical apps
device deployment get priority service
 Manage remote sites  Make use of cheaper
with no local IT staff secondary links
The Juniper WAN acceleration product provides a framework for addressing the problems that we’ve been discussing.
That framework is represented by this wheel. You’ll see this wheel as a recurring icon throughout the presentation.
The wheel addresses four different aspects of WAN acceleration. At the 10 to 11 o’clock position on the wheel, we
address compression and caching. Compression and caching are nothing new to the industry. Those have been
handled by modems and by routers and even by switches for years. Compression and caching give you a way to put
more bits into a pipe. That is certainly good in terms of avoiding WAN upgrades and enabling applications to roll out at
a faster pace. However, things start to get interesting as you move to acceleration, represented by the 1 to 2 o’clock
position on the wheel.
Acceleration, from an SE’s perspective, means spoofing or proxying. It can be done at a TCP level, and also at an
application level. By doing so, it allows users to centralize their servers or consolidate data centers while additionally
providing high-speed access to remote users.
At the 4 to 5 o’clock position is Application Control. This is a great differentiator for Juniper versus our competitors
because we’re able to apply QoS in an accelerated environment. At some point, even after you compress and cache
the data and you accelerate the applications, you’re still going to fill up the WAN pipe and performance is going to be
an issue. You therefore want to prioritize services like voice-over-IP (VoIP)[VOYP] or other critical, real-time
applications, in order to ensure they get first crack at the bandwidth. Juniper allows you to do that.
Finally, at the 7 to 8 o’clock position on the wheel, is Visibility. This is another strong differentiator for Juniper because
it allows the network administrator to see the applications on his network and see what percentage of bandwidth
they’re using. They can also see what kind of return on investment they are getting from WAN acceleration. By seeing
the compression ratios and acceleration ratios, they can see how long it’s going to take before additional circuits need
to be deployed.
This is the WX Series framework we are going to use for the rest of the course.

11
Slide 11
Section Summary
 In this section, you have learned about:

• The conflict going on in the distributed enterprise
• Current branch office trends
• How the WAN slows applications
• How the Juniper WAN acceleration product provides a
framework for addressing some of the problems facing the
distributed enterprise
In this section, you have learned about:

• The conflict going on in the distributed enterprise
• Current branch office trends
• How the WAN slows applications, and
• How the Juniper WAN acceleration product provides a framework for addressing some of the problems facing the
distributed enterprise

12
Slide 12
Learning Activity 1: Question 1

In terms of conflict in the enterprise, which of the
following statements is true?
a) IT objectives are not consistent with user
objectives
b) IT objectives are not consistent with business
objectives
c) User objectives are consistent with IT objectives
d) User objectives are consistent with business
objectives

13
Slide 13

The traditional problem branch offices have to endure
is described by which of the following?
a) Limited bandwidth
b) Too few applications
c) Intermittent service
d) Long distances between sites

14
Slide 14
Product Introduction
Product Introduction

15
Slide 15
Section Objectives
 After completing this section, you will be able to:

• Describe the WAN acceleration reference architecture
• Discuss the WXC Series product family
• Describe the WX stack
•List the leading WX Series customers by industry
After completing this section, you will be able to:

• Describe the WAN acceleration reference architecture
• Discuss the WXC Series product family
• Describe the WX Stack, and
• List the leading WX Series customers by industry

16
Slide 16
WAN Acceleration Reference Architecture
Data
Center
WX
Series/WXC
WX
Branch Series
Series/WXC
Series
WAN
CMS
WX
Series/WXC
Branch Series
There are several different architectures by which WAN acceleration can be deployed in your customer base. They
can be mixed and matched, if necessary. However, the most common way to deploy WAN acceleration is to put a WX
Series box behind the router and in front of the switch. In essence, it’s in-line communications between the switch –
which represents the LAN at a branch office – and the router.
WAN acceleration devices only work in like pairs, so you need to establish tunnels between themselves. All three of
these devices would have tunnels interconnecting them, either in a fully meshed architecture or perhaps in a star
topology with the data center as the hub of that star.
A couple of things are apparent here. First, you have to have a WX Series device at each end for WAN acceleration to
work. If you don’t have a WX Series device at a remote location, you simply do not build an acceleration tunnel, and
you end up passing data through the least common denominator – which becomes the WAN speed. By no means will
the WX Series device ever cut off an office from the rest of the organization.
Second, this also shows that the WX Series device could potentially be a single point of failure for one of those branch
offices. After all, it’s directly in line with the communications. It’s important to note that the WX Series device is a WAN
acceleration device but does not have any WAN ports; instead, the ports are Ethernet in, Ethernet out. You connect
an Ethernet cable to the switch at 10/100/1000 speeds – what’s ever appropriate – and then you connect another one
to the router. The entire WAN portion is handled by the router, as you can see in this diagram. If, for some reason or
another, the WX Series device fails or if the power is lost to it, the input and output Ethernet ports are electrically
connected so, for all practical purposes, the switch will then be directly connected to the router. You will not be
accelerating or compressing any data, but neither will you lose connectivity to the branch office. You will still have
connectivity at the WAN speed.
The final point to make from this slide is that WX Series devices only speak to other WX Series devices. That is, there
are no standards for WAN acceleration. A Juniper WAN acceleration device will not speak to a Riverbed or a Cisco
WAAS or any other product out there. The same is true for all the other products; they only work in like pairs. Since
there are no standards and every vendor interprets WAN acceleration to their own ability, it is, for lack of a better term,
a proprietary technology. Having said that, Juniper’s interpretation is the broadest in the industry and it provides the
most options. But, again, it only works in a Juniper-to-Juniper environment

17
Slide 17
WX Series Hardware
 WXC1800: For really small branch offices
• Simple, small, low noise appliance easy to deploy and that can sit on a
desk
• From 512 Kbps up to 2 Mbps
• Fixed configuration (2 interfaces and 80 GB)
 WXC2600: For small/medium branch offices
• Modular appliance that fits in complex environments and with high
scalability
• From 1 Mbps up to 10 Mbps
• Modular # of interfaces (4 default + 4)
• Field replaceable disk (250 GB)
 WXC3400: For large branch offices or even data centers
• Highly modular appliance that fits in complex environments with high
scalability
• From 2 Mbps up to 45 Mbps
• Modular # of interfaces (4 default + 8)
• Field replaceable disk, power and fans
• Disk High Availability (2x500 GB disks with no RAID)
Let’s look at the WX Series hardware appliances in a little more detail. These are the three main models of the WX
Series platform; which can be thought of as small, medium and large.
The WXC1800 is a very small form factor desktop model that’s good for compression and acceleration up to about two
megabits. It is a simple, small, low noise appliance easy to deploy and which can easily sit on a desk. It is designed
for small branch offices that have only a few connections to other locations. Typically they would be at the end of a
spoke on a star topology.
The midsized model is the WXC2600. It’s good for up to Ethernet speeds of ten megabits. It is modular, so you can
add additional Ethernet ports to it as you grow, and also has field replaceable power and disks. It’s good for a mid-
sized office or perhaps a smaller enterprise organization.
The large data center unit – the WX3400 – is good for speeds up to DS3. It will support about 100 tunnels. It also has
hot swappable, field replaceable disks and fans and modular interfaces.
It’s important to note here that the WAN acceleration product line runs what we call the WX Series operating system.
The WX Series operating system, like any Juniper operating system, is entirely consistent from one platform to the
next. If you go from a WXC250, at the upper left hand portion of the slide, to a WXC590, or even to a stack of WXC
Series devices, you don’t gain or lose any features as you go up or down the stack. Instead, it’s just a matter of
scalability and performance. That’s how you size the appropriate product for your network. It’s also important to note
from this slide that there are two different categories of WAN acceleration devices.

18
Slide 18
WXC Series ISM200 Module Overview

 Market leading WAN optimization comes into best-in-class
high-performance secured router
 WXC Series ISM200 is a WAN optimization module
J2350
• For J Series J2320
• J2320
• J2350
• J4350
• J6350
• That supports the full WX Series framework
• Compression/caching (includes disc)
• Acceleration
• Control J4350 J6350
• Visibility
• And provides a simple centralized device for branch offices that replies to the
comprehensive enterprise needs in:
• Security
• Routing
• Applications acceleration
The WXC Series ISM200 module is basically the WXC1800 from the previous slide, without the cover and without the
power supply. It has the same functionality and same hard disk put on a card that goes into a J Series router.
The value here is that your J Series router now controls your routing, your security, potentially VoIP as well, and WAN
Acceleration for a branch office. This is a huge differentiator for Juniper versus the competition because we make
routers and WAN Acceleration and we’re able to integrate the two to provide a complete solution for the branch office.

19
Slide 19
WX Stack Overview
 A WXC Stack consists of one WX100 device, acting as a Server
or stack master, with between 1 and 6 individual WXC590
devices, the Clients, connected to it to form a single virtual
WXC Series appliance
 Supports up to OC-3 Speeds
 Supports 840 Tunnels (branches)
To WAN
REM OTE
LOCAL
POW ER
1000 / 100 LIN K/ DAT A 1000 / 100 LINK /DA TA 1000 /100 LIN K/ DA TA
2 3 5 REM OTE
To LAN
LOCAL
CONSOLE 2 2 2
CLIENT
1 4 6 WX 1 00 BY PASS
1000
100
LINK /DATA
POWER
REMOTE
LOCAL
RE MOT E
LO CA L
10 00
BYP AS S
CONSOLE MANAGEM ENT 10 0
10 00/10 0 D AT A L INK D AT A
WXC 590
POWER
REMOTE
LOCAL
RE MOT E
LO CA L
10 00
BYP AS S
CONSOLE MANAGEM ENT 10 0
10 00/10 0 D AT A L INK D AT A
WXC 590
This is a picture of a WX Stack. A stack allows you to combine WX Series devices to achieve better scalability. Earlier
we mentioned that the WXC3400 can achieve DS3 speeds, but if you want to improve upon that and go up to an OC3
speed or 155 megabits speed, supporting over 800 tunnels, you can stack devices together.
You can stack up to six of them with one central device, known as a WX100, as a controller or server. You still have a
single Ethernet interface in, and a single Ethernet interface out. But you have the stack sharing processing resources
and disk resources for caching and for acceleration.
This would be a good central site solution for having up to about 800 tunnels to all of the branch offices. This would
allow you to take an OC3 into the central site and have distributed T1s or T3s – or whatever WAN speeds are
appropriate – to all the branch offices.

20
Slide 20
Where to Use a WXC Stack
 In general, a WXC stack is used to increase the

following capacities beyond the limit of a single WXC
Series device:
•WAN link speed above 45 Mbps
• The stack can scale up to 155 Mbps
•Tunnel count for a hub or data center WXC Series device
above 140
• The stack can scale up to supporting 840 tunnels (aka branches)
To expand on where to use the WX Stack – it would be at a central site or a large data center, where you would
potentially bring an OC3 circuit into the center, or maybe a Metro Ethernet 100 megabit circuit. You would then
subdivide that among the up to 840 tunnels for branch offices, each of which might have a T1 or T3 or a Metro
Ethernet circuit.
So, this is for the very large aggregation point in the network. This also has resilience built into it, in terms of multiple
units that back each other up and multiple disks that can back each other up.

21
Slide 21
WXC3400 Award: Product of the Month!
http://www.networkworld.com/slideshows/2008/071608-products-of-the-month.html
It’s worth noting that when the WXC3400 – the new high range product for up to DS-3 speeds – was released, it was
picked by Network World as their product of the month.

22
Slide 22
Leading WX Series Customers by Industry

Computer Banking/ Consumer Energy/ Transport/
Various
HW/SW Finance Goods Utilities Auto
With all of these accolades and with the Juniper name, as you would expect we have a very large customer base for
the WAN acceleration product. This is by no means a product in its infancy; it is a well established product, and it’s
being used by the biggest names in the entire enterprise world. As you look at this list of customers you’ll see it pretty
much covers the entire gamut.
Who is an ideal candidate for WAN acceleration? A general answer would be any organization that has branch offices
or wide area connectivity requirements, whether they use the Internet or MPLS or Frame Relay or any other
technology for their wide area connectivity. However, some particularly sweet spots worth noting are companies with
international links. Any organization that has international links or overseas links can immediately benefit from WAN
acceleration for two reasons; first, these links tend to have very high latency – so performance is a challenge for the
end users – and second, these links are also incredibly expensive – so being able to save on upgrades or reduce
bandwidth requirements has a direct financial impact to the organization.

23
Slide 23
Section Summary
 In this section, you have learned about:

•The WAN acceleration reference architecture
•The WXC Series product family
•The WX stack
•The leading WX Series customers by industry
In this section, you have learned about:

• The WAN acceleration reference architecture
• The WXC Series product family
• The WX Stack, and
• The leading WX Series customers by industry

24
Slide 24

The most common way to deploy WAN acceleration is to
put a WX box behind what and in front of what?
a) the switch, the router
b) the server, the switch
c) the gateway, the router
d) the router, the switch

25
Slide 25

The hard disk in a WXC device stores more information
by caching bit and byte patterns, which are stored
where and delivered where?
a) locally, remotely
b) locally, locally
c) remotely, locally
d) remotely, remotely

26
Slide 26

Which one of the following statements about the WXC
ISM 200 card is true?
a) It has full acceleration capabilities but is too
small to have a hard disk drive
b) It has all the capabilities of the WX family except
for reporting
c) It is a full WXC product with an onboard hard disk
for caching
d) It fits into any of the M-series or J-series routers

27
Slide 27
Applications
Applications

28
Slide 28
Section Objectives
 After completing this section, you will be able to

discuss the following applications and explain how
they can be optimized using Juniper Networks WAN
acceleration product:
• Microsoft Exchange (MAPI)
• Microsoft File Services (CIFS)
• Web-enabled applications
• Secure applications
• Data replication
• Voice-over-IP (VoIP)
• ERP
• Satellite communications
After completing this section, you will be able to discuss the following applications and explain how they can be
optimized using Juniper’s WAN acceleration product:
• Voice-over-IP
• ERP, and

29
Slide 29
Applications Optimized by the

WX Series/WXC Series
 Exchange (MAPI)  VoIP
 File Services (CIFS)  ERP
 Web (HTTP)  SAP
 Secure Socket Layer (SSL)  Satellite connections
 Data Replication
We’re now going to get into some detail about how the WX Series accelerates applications. We’re going to look at
several applications individually, starting with Microsoft Exchange, followed by Microsoft File Services. We’ll also look
at web-enabled applications, such as HTTP, SSL for the secure socket layer, and data replication. Some applications
that are supported by all of these are VoIP, ERP, SAP, and satellite connections.

30
Slide 30
Centralized Exchange: The Challenge

Easier admin but slows users Centralized
and takes more bandwidth Servers
WAN
 Message retrieval subject to delay

•Multiple round trips required per e-mail, so even minimal
latency slows users
 Bandwidth requirements increase dramatically
•Many more message are sent across WAN, creating a
bandwidth crunch
The first application we’ll look at is Microsoft Exchange, or the common Outlook application that we all use in the
office. In a typical scenario, centralized servers are used to deliver messages to all of the branch offices. Hence, they
have to transit the WAN. The interesting thing is, if you send a message to your next door neighbor, it probably goes
over the WAN to the centralized server, back over the WAN, and then to your neighbor.
As will be discussed in the section covering technical details, there’s a stop/start effect of a window size of only 1 in
MAPI (Messaging Application Programming Interface – Microsoft Outlook’s interface for email), which comes into play
as you send something to your neighbor – you have the stop/start, ping pong effect getting to the server, and then the
same effect as it returns. Also, in the example on the slide, you’re seeing four copies of a message being delivered to
each of the two branch offices. That means the exact same message is delivered four times to four different users with
all of the same challenges across the WAN, such as the ping pong effect. These are things that the WX Series with
application acceleration attempts to solve.

31
Slide 31
Exchange: The Juniper Networks Solution
WX
e Series/WXC
Series
WAN e e
e
 AppFlow pipelines messages across the WAN

• By the time the client requests the message, the local WX Series/WXC
Series device sends it at LAN speeds
 Dramatic acceleration and bandwidth savings
• Compression and caching significantly improve the results
 Transparent to clients and servers
 Effective on links with even modest latency (20–30 ms)
This is the WX Series view of a similar transaction. First, the WX Series provides local acknowledgements to the
server so you’re not waiting on acknowledgements and the ping pong effect across the WAN. Second, it’s going to
compress all of the data as it’s transmitted between WX Series devices, and third, it’s going to cache known patterns.
Thus, instead of four copies of the message being sent, to each branch office across the WAN, only one copy is sent
– without the ping pong effect, and in a compressed format. For the other three copies, in theory, a lot of the patterns
will be cached, so you’re able to deliver just pointers to those patterns. You don’t get a 25% utilization factor for
sending one message versus four, but you do get something close to that, and that improves further with regard to
lack of latency and also compression.
This kind of a performance improvement, incidentally, is available on links with even a modest latency of only 20-30
milliseconds.

32
Slide 32
Exchange Acceleration: Results

2 MB e-mail with Excel File Attachment
748 Kbps link between Boston and New York
35ms of latency
Results
Before Juniper 45 seconds with no acceleration
Networks
After Juniper 2 seconds with AppFlow technology enabled
Networks
Improvements
23x performance gain
“The users are reporting faster message opening times, by about a factor of four. They’re
getting 1 MB files in 15 seconds instead of a minute.”
- IT Director
With every application we have some real world results from actual customer experiences. In this particular case, we
are looking at Microsoft Exchange on a 748K link between Boston and New York – that’s half a T1 with only 35
milliseconds of latency. When transmitting a 2MB Excel file attachment, the before version was about 45 seconds.
After installing the WX Series devices with compression, caching, TCP acceleration and, most importantly, with MAPI
acceleration, that transfer time went down to 2 seconds.

33
Slide 33
Exchange Acceleration: Results (Cont'd.)
2.8 MB e-mail with PDF file attachment

384 Kbps link between Chicago and Mexico City
100ms of latency
Results
Before Juniper 96 seconds with no acceleration
Networks
After Juniper 57 seconds with TCP acceleration
Networks 5 seconds with AppFlow technology enabled
Improvements
Here’s another real customer example, with a 384K link between Chicago and Mexico City and with 100ms of latency.
Incidentally, international links are great targets for WAN acceleration because of the high latency as well as the high
cost.
To transmit a 2.8MB email attachment, just a PDF file, the before benchmark was about a minute and a half, and the
after benchmark a matter of just 5 seconds. That’s about a 20X performance gain experienced by this particular
customer.

34
Slide 34
File Services: The Challenge

 CIFS transfers files in small data chunks; needs an ACK
for each
 Creates ping-pong effect
 Happens above the TCP layer
• Not solved by accelerating TCP
WAN Request
ack
ack
Windows ack Windows
ack
Clients ack Server
The next application we will look at is Microsoft File Services or CIFS, which stands for common interface for file
services. This is best known by users as the drag and drop protocol, where you can select a file from the server, drag
it to your desktop, and have it transferred over the WAN.
As with MAPI, the ping pong effect is rather painful for this, as this slide illustrates in slow motion. What’s going to
happen is the server transmits a chunk of data, then waits for an acknowledgement, transmits the next chunk, and so
forth, until the entire file is received by the client. It should be noted that compression would help, but that would have
a marginal effect because, for quite a lot of time, if there is any latency on the line, the WAN circuit is idle while waiting
for acknowledgements.
In order to really address the CIFS problem, you have to work at the application layer of CIFS itself.

35
Slide 35
File Services: The Juniper Networks

Solution
 WX Series/WXC Series devices pipeline files across

the WAN by way of AppFlow following initial request
 Files are served to the client at LAN speeds
WAN
request
Windows Windows
Clients Server
The Juniper WAN acceleration solution for CIFS is quite similar to MAPI. We provide the acknowledgements locally,
from the WX Series device adjacent to the file server, so those will be delivered at gigabit speeds. In the meantime,
we are also going to concatenate some of the packets and compress them, sending them across the WAN, and then
deliver them to the clients. We’ll also intercept the client’s acknowledgements locally and not transmit those across the
WAN. So, in addition to compression, we have also eliminated the ping pong effect.

36
Slide 36
File Services Acceleration: Results
98MB CAD file for AEC firm

T-1 link between Denver and Atlanta
60ms of latency
Results
Before Juniper 711 seconds with no compression or acceleration
After Juniper 140 seconds with compression and caching
13 seconds with AppFlow acceleration
Improvements
Here are some real world results from CIFS acceleration. In this particular example, a T1 link is installed between
Denver and Atlanta, with about 60ms of latency. That’s about average for this kind of circuit. In this case, an
architectural engineering firm is transferring a 98MB CAD file. The before result required about 12 minutes to transfer
the file. After turning on compression and caching, that time went down to about 2 ½ minutes, which is certainly a
good improvement. But then, after turning on CIFS acceleration, that time declined to 13 seconds, for a 55X
performance gain.
This presents a very noticeable effect to the end user. The difference from his perspective, while sitting at his desk, is
between starting a file transfer and then going to get a cup of coffee or making a phone call and then coming back to
continue working, versus transferring the same file and having immediate access to his resources and his work.

37
Slide 37
File Services Acceleration: Results (Cont'd.)
21MB zip file for financial services firm

768 Kbps link between Boston and New York
35ms of latency
Results
Before Juniper 420 seconds with no compression or acceleration
After Juniper 15 seconds with compression and caching
12 seconds with AppFlow acceleration
Improvements
Here we have one other real world example, on a half T1, or about a 768K link, between Boston and New York. A
financial firm is transferring a 21MB file. It should be noted that this is a zip file, so it’s already compressed. The link
has about 35 ms of latency. The before results were about 7 minutes and the after results were a matter of seconds.
Again, a major performance improvement – subjective and quantitative – was experienced by the users.

38
Slide 38
Web Apps: The Challenge
 More and more applications moving from client-server

to a Web interface
 Significant bandwidth impact
•Bandwidth consumption increases 10x or more versus
client-server architecture
 Latency dramatically slows page display times
•HTTP requests objects one at a time, with ACK required for
each
•Each page typically has several dozen objects
•Web caches don’t help—still ask server to
confirm freshness
Another application supported by Juniper’s WAN acceleration appliances is HTTP acceleration, or Web acceleration.
This does not mean that users can surf the Internet faster.
If you go back to the basic reference architecture, you’ll remember that WAN acceleration devices build tunnels
between like devices – WX Series device to WX Series device. If your favorite web site happens to have the WX
Series device with a tunnel back to your location, then you could improve your performance surfing that particular site.
However, where HTTP acceleration comes into play or is much more beneficial is with web-enabled applications. Most
applications at this point use HTML as a front end. ERP and SAP certainly are good examples of that. Oracle uses
HTML as a front end, and most of the financial and business applications a customer uses will in fact have HTTP
involved.
HTTP acceleration makes those particular applications run much faster in the wide area environment. This is a
differentiator for Juniper versus Cisco, since Cisco does not support HTTP acceleration.

39
Slide 39
Web Apps: Slow Performance

 Client browses to  Gets the page, displays  Asks for object 1,  Asks for object 2,  Asks for object 3,
www.Juniper.net what it can and figures receives and receives and receives and
out what objects it displays it displays it displays it
needs to get
Web
WAN
Web
Clients Server
Page display slowed by WAN

latency—subsequent displays
of this page remain delayed
because cached objects must
be confirmed
This slide provides an overview of how HTML works. This is true whether you have a web application or you are
looking at a web page itself.
HTML is designed to be very highly modular. The reason is that the webmaster may want to substitute different pieces
of the web page from time to time. For example, Juniper Networks may want to advertise our new firewall services
today, then tomorrow we might want to use that same space to announce a seminar series, and the next day we may
want to tell you about some new router developments. Modularity is very important to the task of moving things in and
out of a web page based on the needs of the user.
When you request a web page you get a framework and that framework will tell you how many objects are going to be
involved with the web page and where they go. You may have noticed while surfing the Internet, in the lower left hand
corner of your browser you usually get a number that says something like “22 objects to load,” and then it counts down
as they are loaded. That’s the framework requesting each object.
The way HTML works then is you request a web page, you get the framework, the framework tells you what objects to
request, and then you ask for them one by one. That is, you request object number 1, get object number 1, request
object number 2, get object number 2, and so forth. If there are a lot of graphics or there is video involved, this could
take quite a while. It is representative of the ping pong effect that we saw with MAPI and CIFS – only now you’re
getting visual feedback as well.

40
Slide 40
Web Apps: The Juniper Networks Solution
 Build table of URLs and their associated objects

 Request objects, confirm freshness, pipeline to client
WX Series/WXC Series WX Series/WXC Series
HTTP
WAN Web
Clients Server
When HTTP acceleration is enabled on the Juniper WAN acceleration devices, it acts as a local web cache for the
users. If users already have a web cache, they may not need this function. However, additionally, we will also be
compressing the data as it goes over the WAN.
In an HTTP accelerated environment, when a client requests a web page from a web-enabled application, the WX
Series delivers that request to the server, it gets the framework, confirms the freshness of all the objects, and then
delivers the objects locally – assuming they are cached.
This means the very first time the web site or web application is utilized, the data will be compressed and you’ll have
TCP acceleration, but you really won’t have much benefit from the HTTP acceleration. All subsequent times, however,
web objects will be cached and you won’t need to transmit them over the WAN.

41
Slide 41
Web Acceleration: Customer Results
Global Manufacturing Firm Retail Firm

Issue: Offices accessing intranet and in- Issue: Call center employees accessing
house web applications customer database
Latency: 50ms and 250ms Latency: 70ms and 300ms
Web acceleration: 1.5x to 2x Web acceleration: 2x to 3x
WX Series/WXC WX Series/WXC
Series Series
WAN
AFE
Web Clients
Web Servers
Web-enabled applications typically use much smaller pieces of data or files than a CIFS file transfer or a large
Microsoft MAPI attachment. As a result, the performance gain isn’t going to be quite as dramatic for web-enabled
applications as we saw for CIFS and MAPI. However, the average user, as some of these metrics illustrate, can
expect a 2-3X and maybe a 5X performance improvement when using WX Series devices for their Web-enabled
applications.

42
Slide 42
Web Acceleration: Business Benefits
 Users get faster page displays for Web-based apps

•The higher the latency and the more complicated the Web
page, the greater the acceleration benefit
 The bandwidth impact of Web apps is reduced
 The need for Web caches is eliminated
 Businesses can prioritize different Web apps
•WX Series/WXC Series devices can differentiate between
Web traffic
 Employee productivity increases
•Key apps such as ERP will run faster with Web acceleration
 Users don’t have to change their work processes
•Deployment is transparent to clients, servers and network
The business benefit of HTTP acceleration is that users can do their job much more quickly. A good example of this
might be a hotel reservation agent, where the reservation agent gets the framework, which is similar whether he’s
making reservations for John going to Chicago or David going to New York. Basically the framework and the
information are similar. The names, dates, and locations are really the only things that change.
If the screens can be painted faster, they provide better customer service to their users by having a faster response
time. They are also able to handle more transactions in a given time period.

43
Slide 43
Secure Applications: The Challenge

 Branch users accessing more applications over the WAN
 Application access migrating to secure access (for example,
from HTTP to HTTPS)
 Application sessions are encrypted from client to server
WX Series/WXC WX Series/WXC
Series Series
WAN
Branch Office Data Center
With the advent of the Internet has also come the advent of security challenges. To overcome that, encryption (and, in
particular, SSL) has become a requirement. Now users are accessing the same applications, that they previously
used HTTP for over HTTPS, in order to have encrypted service end-to-end.

44
Slide 44
Secure Applications:
The WX Series Solution
 AppFlow™ for SSL accelerates SSL-encrypted applications
across the WAN
 SSL certificates/private keys only required for data center WX
Series device
 Zero touch for client or server, maintains end-to-end security
WX
WX Series/WXC
Series/WXC Series
Series
WAN
Branch Office Data Center
Juniper’s WX Series platform is also capable of accelerating SSL-enabled applications. In order to do this it uses
private and public keys as well as external certificates. The WX Series does not in any way require client or server
interference, so it’s zero touch for the client and server, and yet it maintains the end-to-end security.
This is ideal for web-enabled applications such as SAP or ERP that now use secure HTTP instead of just the regular
flavor.

45
Slide 45
The WX Series Solution (Cont'd.)
WXC250 WXC590
SSL IPsec SSL
Application
Server
 AppFlow for SSL allows WX Series device to

transparently decrypt SSL, optimize and re-encrypt
SSL for enterprise applications
 WX Series participates in the application’s security
model, maintaining end-to-end security
 IPsec between WX Series devices
The Juniper story for SSL acceleration is similar to what we use for HTTP or MAPI or CIFS in that we locally terminate
the SSL connection from the client to the WX Series device and from the server to the WX Series device adjacent to it.
However, this means that you’re transmitting information over the Internet without using SSL encryption. After all, it
has been locally terminated at the two ends of the circuit.
In order to overcome this, we use an IPsec connection between the WX Series devices so that it’s a question of
what’s more secure, IPsec or SSL? And the answer is they both use the same encryption algorithms, so it’s not a
matter of which is more secure – they are equally good in that respect.

46
Slide 46
MSFT SharePoint Results
 Upload of Microsoft Excel, PowerPoint, and Word files

 WAN (T1, coast to coast US)
 85–98% improvement in response time
File Upload
WAN (1.5Mbps, 100ms roundtrip)
86
2MB XLS
82
Baseline
2MB PPT
WX Cold
83
WX Warm
2MB DOC
0 10 20 30 40 50 60 70 80 90
(seconds)
SSL acceleration is a relatively new development for Juniper. We don’t have a large collection of real world customer
results. However, we do have some benchmarks that are significant.
Starting with a common application for SSL, which is Windows SharePoint Services, transferring large files generally
results in about an 85% performance improvement when you turn on SSL acceleration.

47
Slide 47
Secure Applications: SAP Results
 Transaction: 5 MB SAP-KM document

 WAN (Frac T1, US domestic), (Frac T1,
US–International)
 >97% improvement in response time
5MB SAP-KM 5MB SAP-KM
WAN (768Kbps, 60ms roundtrip) WAN (768Kbps, 300ms roundtrip)
Baseline 56 142
Baseline
WX Cold 1.35 1.59

WX Cold
WX Warm WX Warm 1.31

1.13
0 10 20 30 40 50 60 0 20 40 60 80 100 120 140 160
(seconds) (seconds)
SAP, when transmitting 5MB files back and forth, tends to result in a better than 95% performance improvement. This
depends upon the latency of the circuit, but under most circumstances you can expect similar results.

48
Slide 48
Secure Applications: Oracle Results
 Oracle iProcurement session with and without

document access
 WAN (T1, coast to coast US)
 67–81% improvement in response time
Oracle iProcurement Session Oracle iProcurement Session with Document Access

WAN (1.5Mbps, 100ms roundtrip) WAN (1.5Mbps, 100ms roundtrip)
Baseline 20.44 Baseline 58.44
WX Cold 13.5 WX Cold 47.5
WX Warm 6.78 WX Warm 11.08
0 5 10 15 20 25 0 10 20 30 40 50 60
(seconds) (seconds)
Oracle also uses secure HTTP, or HTTPS as it’s better known. Oracle tends to have very good compression of their
data, so the performance improvement you get with SSL acceleration is still very significant. It tends to be better than
about 60%, but it’s not quite as dramatic as with some other applications.

49
Slide 49
Data Replication: The Challenge
 Cannot rely on effective tape backups at sites with

no IT
 WAN-based backups create a significant
traffic load
•Replication traffic can swamp other key applications
 Overnight backups across the WAN are often not
completing over night
•24/7 operations mean no off time for the WAN to run
replication
Another ideal application for WAN acceleration is data replication, or the dreaded nightly backups. The challenges
people are having now with regard to nightly backups are twofold: on one hand the data tends to exceed the time
allotted for the backup, so they often cut into business hours, and on the other hand there’s the exact opposite
problem, which is business hours in a 7 by 24 shop cut into what would traditionally be backup times.
Since there aren’t any off hours in the 7 by 24 operation, there’s no time to use the WAN just for backup purposes.

50
Slide 50
Data Replication:
The Juniper Networks Solution
 Eliminate repetitious traffic
• Data replication often includes significant repetition that compression
and caching remove from the WAN
 Prioritize more important traffic
• QoS ensures high-priority traffic isn’t stepped on by data repetition
 Allocate bandwidth to enable continuous replication
 Accelerate TCP
• Backup traffic benefits from being pipelined across the WAN
WX WX
Series/WXC Series/WXC
Series Series
WAN
HQ DR Site
The Juniper solution for data replication is based heavily on the network sequence caching aspect of the WXC Series
product line. A reasonable assumption to make on a nightly backup is that 100% of the data has not changed
overnight. In fact, 50% of the data that will be backed up probably hasn’t changed. Maybe you could say that only 10-
20% has changed from one day to the next.
Therefore, if a lot of information is cached, you don’t have to transmit or retransmit that information over the WAN.
Instead, you just transmit pointers to the cached sequences. In addition to that, the compression, TCP acceleration,
and quality of service aspects of the WX Series help improve the backup performance as well.

51
Slide 51
Data Replication: Results

Banco Santander
T-1 link between Miami and New York; need data replication outside Miami
Results Backup WAN Capacity Access Time

Before Juniper Tape in Miami, courier T-1 link full 4 seconds
Networks to NY, manual restore
After Juniper
Networks Continuous data rep 5x increase 1 second
Annual Savings
$60,000 in additional bandwidth costs
“Because of (Juniper Networks), our WAN now supports continuous data replication and our
users get instant access to their key applications.”
- Eugene Rivera
Technical Support Manager, Banco Santander
One customer example of an organization that benefited heavily from using the WX Series for data replication is a
Latin American bank that had a T1 connecting their Miami and New York offices. The T1 was completely full and the
access time for transactional records was about four seconds.
Their backup procedure was to FedEx a tape from Miami to New York every night. After putting in WXC Series
products they were able to do continuous data replication in real time and their transactional times went from four
seconds to only one second. That resulted in an estimated savings of $60,000 in upgrade costs. In addition to that,
they also saved quite a bit of money on FedEx expenses.

52
Slide 52
Data Replication: Business Benefits
 Improve data integrity

•More frequent replication ensures freshness of data
 Simplify regulatory compliance
•Reduce staff time needed for manual backups
 Reduce disaster recovery time
•Improved recovery time and recovery point objectives
 Improve collaboration on shared data
 Save on bandwidth costs by avoiding WAN upgrades
Key Partnerships
This slide lists the overall business case for using the WX Series for data replication. It improves data integrity since
we check the integrity of the data that’s being transmitted across the WAN. It also greatly simplifies the nightly
backups or data replication processes, and improves the overall performance of not only the backups but all other
applications as well.

53
Slide 53
VoIP: The Challenge
 IT must be prepared for VoIP

•It’s coming to enterprises, and it doesn’t behave
like data
 VoIP needs priority service
•Calls require little bandwidth but cannot
tolerate delay
 Data traffic can swamp voice calls
•Need to allocate room on the WAN
 Performance problems grow as call volume increases
Another good application for WAN acceleration is voice-over-IP, or VoIP. VoIP is becoming more and more prolific on
corporate networks. It’s a good way to save money and it’s also a good way to combine your networking facilities for
voice and data.
However, users are very sensitive to problems in voice traffic; latency, lost packets, or out of sequence packets are
very, very obvious during a conversation. Therefore, VoIP, above and beyond all else, still needs priority as real time
data.

54
Slide 54
VoIP: The Juniper Networks Solution
 Reduce traffic from other apps to make room for

voice
•Compression and caching can provide 10x to 100x capacity
improvements
 Allocate bandwidth for and prioritize
voice traffic
•Built-in QoS templates simplify VoIP deployments
 Compress voice headers to reduce VoIP traffic
•Up to 30% reduction
 Provide visibility into VoIP performance
The Juniper WAN acceleration solution can provide many benefits for a voice over IP environment. However, it’s
important to note that we do not accelerate voice over IP traffic, per se, such as we would with CIFS or MAPI or
HTTP. Instead, the benefit that’s derived for voice over IP is more indirect.
The first thing to note is that we can compress UDP traffic and UDP headers. VoIP packets tend to be very small and
the bulk of the packet is the header itself. So compressing the UDP header tends to yield about a 30% performance
improvement or a 30% traffic reduction for UDP voice over IP traffic. Our competitors cannot compress UDP, so this is
a good differentiator for Juniper.
Second, we can prioritize voice over IP or any other application with our quality of service infrastructure in the WX
Series product line. This also is a good differentiator for Juniper Networks versus Cisco, which does not have any
quality of service attributes built into their WAAS product line.
Third, and perhaps most important, we can make a lot more room for voice over IP traffic by compressing,
accelerating, and caching all the other data on the network, thus leaving more room for the voice traffic.
All these together greatly improve the voice over IP environment for customers.

55
Slide 55
VoIP Acceleration: Customer Results
Hines & Associates

VoIP at five locations in three states
Needed to improve service consistency and voice quality
Results Voice Calls Quality Citrix Traffic

Before Juniper Dropped calls at high volume Printing problems
Networks
After Juniper Telco-grade voice No performance issues
Networks
Savings
$48,000 in avoided upgrade costs
“(Juniper Networks) paid for itself in less than a year. Our existing network can now support
twice the VoIP traffic with Telco-grade quality.”
- Carl Valiulis
IT Director, Hines & Associates
This real world customer result comes from a company called Hines & Associates in the Midwest. Before Juniper, they
tried to run VoIP traffic and they had dropped calls and high user frustration. They had some printing challenges as
well.
After installing Juniper WAN acceleration devices at each of their locations, they effectively had Telco grade voice
using VoIP, and their printing problems also went away. They estimated this immediately generated about $48,000 in
avoided upgrade costs or real time savings.

56
Slide 56
ERP: The Challenge
 Enable pervasive deployment

•Must provide access to remote employees throughout
the business
 Avoid high cost of a global rollout
•Cost of pervasive deployment cannot exceed the value of
the application
 Centralize servers
•Distributed users are remote from the application server
 Accommodate bandwidth demands of Web
implementations
•10x the bandwidth for the same client-server transaction
The next application we’ll look at is ERP. This typifies any web-enabled application, whether it’s ERP, SAP, or just
about anything else. ERP in particular tends to be a very centralized application where servers are located back at the
corporate data center and users could be all over – such as sales reps, order entry folks, customer service agents,
and so forth.
The challenge with this is that you’re loading screens over the WAN and you have the typical HTTP delays and
latency associated with that.

57
Slide 57
ERP: The Juniper Networks Solution
 Compression and caching reduce bandwidth

consumption
•Typical traffic volume reduction ranges from 70%–95%
 QoS prioritizes critical traffic
 HTTP acceleration speeds transaction times
for Web-based ERP applications
•Typical performance increases from 2x to 4x
The Juniper solution for ERP applications is to use HTTP acceleration features. In addition to caching and
compression, which typically reduces traffic volumes considerably, we can also accelerate HTTP with local caching.
Typical performance increase ranges from about 2-4 times in terms of transactional data. It’s not as dramatic as the
numbers you get from MAPI or CIFS, but that’s because the data quantity tends to be much smaller, and it tends to
involve short, brief transactional packets.

58
Slide 58
ERP Acceleration: Customer Results
JTI—World’s largest single instance of SAP

Global implementation for sales, manufacturing and distribution
Results SAP Response Time Bandwidth Impact of SAP Link Throughput
Before Juniper 6 seconds 500% increase 4 Mbps

Networks
After Juniper 1 second 65% reduction 10 Mbps
Networks
Deployed WX Series devices in 150 locations

Improved application results for Citrix, VoIP and other
web-based applications
“(Juniper Networks) was initially deployed to solve a WAN pain—capacity.

Now (Juniper Networks) is an important application enabler for us.”
- Gunter Hogendorf
Head of IT Vendor Management and Service Delivery
A good customer example of ERP or SAP acceleration is from a company called JTI, which has the world’s largest
implementation of SAP in a single data center. Prior to implementing WX Series devices, they had a response time of
about six seconds and their bandwidth was pretty much saturated, seeing an overall link throughput of about 4Mbps
on their T1s.
After incorporating the WX Series with HTTP acceleration, their response time went down to about one second for
most transactions. They also saw a significant reduction in bandwidth and an overall throughput improvement of up to
10Mbps on their circuits.
This organization consists of about 150 locations and, in addition to running ERP and SAP, they also run Citrix, voice
over IP, and various other web applications.

59
Slide 59
Satellite: The Challenge
 More satellite-based proprietary applications

migrating to open standards on IP
 Latency on satellite links dramatically slows
IP-based communications
 Procuring additional bandwidth often impossible or
too expensive to justify
 Prioritized services typically difficult to implement
Satellite links are probably the ideal poster child for the WX Series. They tend to be very high latency, bandwidth is
quite expensive, and upgrades or adding bandwidth is a very difficult and costly process. If you add all of these
together they make a very good application for WAN acceleration.

60
Slide 60
Satellite: The Juniper Networks Solution
 Accelerate applications over high-delay satellite links

•TCP termination dramatically improves response times
 Compression and caching increase available
bandwidth
•Often gain 2x to 4x capacity on satellite links
 QoS wizards simplify application prioritization
•Built-in templates enable easy deployment
WX WX
Series/WXC Series/WXC
Series Series
TCP Accel
TCP AppFlow TCP
Because of the extremely high latency associated with satellite links, TCP acceleration has the biggest impact here.
The TCP floating window tends to be either 8 or 128 packets. A propagation delay for a satellite is about a third of a
second up and another third of a second down, or approximately two-thirds of a second for a round trip.
That means for two-thirds of a second you are waiting for acknowledgements as opposed to actually transmitting data
after every 8 or sometimes 128 data packets. The local termination of TCP, along with forward error correction
provided by the WX Series product line, alleviates this problem.
Additionally, you can use compression and caching to reduce the overall impact of satellite communications, and the
QoS capabilities of the WX Series can allow you to prioritize real time data over the slow satellite links.

61
Slide 61
Satellite Acceleration: Customer Results

Royal Caribbean Cruise Lines
Deployed WX Series platforms on satellite links to 27 ships and two islands as well as
several terrestrial links
Results Satellite Utilization New Apps
Before Juniper 100% Unsupportable
Networks
After Juniper 15% Passenger manifests, credit
Networks card transactions
Annual Savings
$1.3 million in avoided upgrades
“We are adding more distributed applications to the ships to better service our guests and
prepare a more personalized experience.”
- Aurora Aday
Manager, Network Communication Solutions, RCCL
An excellent customer example for the WX Series over satellite is the company Royal Caribbean Cruise Line. Royal
Caribbean owns approximately 27 ships and two islands in the middle of the Caribbean. They use satellites to
communicate with each of these. Before the WX Series their links were 100% saturated and they had no way to
deploy additional applications without very costly upgrades, which they estimated to be well over a million dollars.
After putting a WX Series device on each of their ships and also on each of the two islands, their satellite utilization
went down from 100% to 15%. As a result, they were able to add new applications, the first of which was credit card
approvals, which is something very valuable to cruise lines.
Not only did Royal Caribbean Cruise Line avoid a million dollars in upgrade costs but they were also able to deploy
very profitable applications.

62
Slide 62
Satellite Acceleration: Business Benefits
 Deliver the lowest-cost bandwidth to hard-to-reach

locations
 Increase available bandwidth on constrained
satellite links
 Reduce delayed response times for applications
 Prioritize critical traffic easily
 Support new IP-based applications
The business benefits associated with WAN acceleration over satellites are fairly obvious and include better
performance, upgrade cost savings, and the ability to deploy new IP-based applications.

63
Slide 63
WAN Acceleration Results

Clearcase CIFS
8x to 30x
CVS MAPI
Improvement
4x to 14x
WebDAV FTP
Improvement
0x 30x
HTTP
TSM
Backup
Notes
Sybase
0x 15x 2x to 5x
Improvement
SAP
Maximum Improvement
Oracle
Minimum Improvement
0x 5x
Juniper has a spreadsheet online that’s available to help calculate the improvement that can be expected from WAN
acceleration. That improvement is going to be based on three factors: bandwidth, latency (which figures into the
equation very heavily), and the actual applications.
From an SE’s perspective, latency and application awareness are critical. Based on what we’ve seen in the real world,
here are some of the estimates of what you can expect in terms of best and least improvement for various
applications.
You’ll notice that CIFS and MAPI have some of the biggest numbers. FTP is also very impressive. But even
applications like Oracle, with only a 2-3X performance improvement, show improvement that is significant and quite
noticeable to users. Just about any of these applications can be used to make a good business case for WAN
acceleration.

64
Slide 64
Section Summary
 In this section, you have learned about the following

applications and how they can be optimized using
Juniper Networks WAN acceleration product:
• Voice-over-IP
• ERP
In this section, you have learned about the following applications and how they can be optimized using Juniper
Networks WAN acceleration product:
• Voice-over-IP (VoIP)
• ERP, and

65
Slide 65

The WX eliminates the ping pong effect by doing which
of the following?
a) replicating data
b) using centralized servers
c) forward error correction
d) providing local acknowledgements to the server

66
Slide 66

Is the following statement true or false?
HTTP acceleration is a good differentiator for Juniper

because Cisco does not accelerate HTTP.
a) True
b) False

67
Slide 67

Juniper’s WX platform accelerates SSL-enabled
applications by using private and public what and
external what?
a) circuits, algorithms
b) certificates, hard drives
c) keys, certificates
d) blogs, servers

68
Slide 68

Which of the following are ways that Juniper’s WAN
acceleration benefits VoIP? (Select 3.)
a) By compressing the UDP headers
b) By prioritizing VoIP traffic
c) By accelerating the VoIP traffic itself
d) By making more room for VoIP traffic by
compressing, accelerating, and caching all the
other data on the network

69

Sawx01 1

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Sawx01 1

Transféré par

Droits d'auteur :

Formats disponibles

e d u c a t io n se rv ic e s c o u rse w a re

WAN Acceleration Appliances

WAN Acceleration Appliances

Course SAWX01A © Juniper Networks, Inc. 2

Course SAWX01A © Juniper Networks, Inc. 3

 On completing this course, you will be able to:

Upon completing this course, you will be able to:

Course SAWX01A © Juniper Networks, Inc. 4

Agenda: WAN Acceleration Appliances

 WX Series Market Overview

Course SAWX01A © Juniper Networks, Inc. 5

WAN Acceleration Appliances

WX Series Market Overview

WX Series Market Overview

Course SAWX01A © Juniper Networks, Inc. 6

 After completing this section, you will be able to:

After completing this section, you will be able to:

Course SAWX01A © Juniper Networks, Inc. 7

Conflict in the Distributed Enterprise

IT Objectives User Objectives

Course SAWX01A © Juniper Networks, Inc. 8

Branch Office Trends

Internal security Content Wi-Fi Bandwidth usage

 Number of branch offices (all sizes) to grow

Course SAWX01A © Juniper Networks, Inc. 9

How the WAN Slows Applications

Lower-priority apps slow

Inability to understand application and WAN performance

Course SAWX01A © Juniper Networks, Inc.

Key Business Initiatives: Cut Costs;

 Avoid WAN upgrade  Improve user

 Reduce time to  Enable VoIP, other

Course SAWX01A © Juniper Networks, Inc.

 In this section, you have learned about:

In this section, you have learned about:

Course SAWX01A © Juniper Networks, Inc.

Learning Activity 1: Question 1

Course SAWX01A © Juniper Networks, Inc.

Learning Activity 1: Question 2

Course SAWX01A © Juniper Networks, Inc.

WAN Acceleration Appliances

Course SAWX01A © Juniper Networks, Inc.

 After completing this section, you will be able to:

After completing this section, you will be able to:

Course SAWX01A © Juniper Networks, Inc.

WAN Acceleration Reference Architecture

Course SAWX01A © Juniper Networks, Inc.

Course SAWX01A © Juniper Networks, Inc.

WXC Series ISM200 Module Overview

Course SAWX01A © Juniper Networks, Inc.

Course SAWX01A © Juniper Networks, Inc.

Where to Use a WXC Stack

 In general, a WXC stack is used to increase the

Course SAWX01A © Juniper Networks, Inc.

WXC3400 Award: Product of the Month!

Course SAWX01A © Juniper Networks, Inc.

Leading WX Series Customers by Industry

Course SAWX01A © Juniper Networks, Inc.

 In this section, you have learned about:

In this section, you have learned about:

Course SAWX01A © Juniper Networks, Inc.

Learning Activity 2: Question 1

Course SAWX01A © Juniper Networks, Inc.