Exinda EXNV-3062 Instruction Manual

ADMINISTRATION GUIDE
Find out how to set up and configure Exinda Network Orchestrator in different
environments and how to customize advanced features.

The information and content in this document is provided for informational purposes only and is provided "as is" with no warranties of
any kind, either express or implied, including without limitation any warranties of merchantability, fitness for a particular purpose, and
non-infringement. GFI Software disclaims and in no event shall be liable for any losses or damages of any kind, including any
consequential or incidental damages in connection with the furnishing, performance or use of this document. The information is
obtained from publicly available sources. Though reasonable effort has been made to ensure the accuracy of the data provided, GFI
makes no warranty, promise or guarantee about the completeness, accuracy, recency or adequacy of information contained in this
document and is not responsible for misprints, out-of-date information, or errors. GFI reserves the right to revise or update its products,
software or documentation without notice. You must take full responsibility for your use and application of any GFI product or service. No
part of this documentation may be reproduced in any form by any means without prior written authorization of GFI Software.
If you believe there are any factual errors in this document, please contact us and we will review your concerns as soon as practical.
GFI and Exinda Network Orchestrator are trademarks or registered trademarks of GFI Software or its affiliates in the US and other countries.
Any other trademarks contained herein are the property of their respective owners.
Exinda Network Orchestrator is copyright of Exinda Inc.. - 1999-2017 Exinda Inc.. All rights reserved.
Document Version: 7.4.7
Last updated (month/day/year): 05/23/2018

Contents
1 Introduction 8
1.1 How an Exinda implements WAN optimization 8
1.2 What is network orchestration? 8
1.3 Exinda system components 8
1.3.1 Exinda Appliance 8
1.3.2 Exinda Web UI 9
1.3.3 Exinda Management Center 9
1.3.4 Exinda Solution Center 9
1.3.5 Exinda Service Delivery Point (SDP) 9
1.4 The Exinda product line 9
1.4.1 Exinda physical appliances 9
1.4.2 Exinda virtual appliances 15
1.5 Product naming conventions 16
2 Getting started 17
2.1 WUI Guided Tour 17
2.2 Deployment options 18
2.2.1 Key terms 18
2.2.2 Basic characteristics and behaviors of Exinda Appliances 18
2.2.3 In-path topologies 19
2.2.4 Out-of-path topologies 28
2.2.5 Clustering topologies 57
2.3 Upgrading and downgrading 61
2.3.1 Upgrading to the latest firmware version 61
2.3.2 Rolling back to the previously installed version of ExOS 62
2.4 Installing an Exinda Appliance 63
2.4.1 Gathering required information 64
2.4.2 Connecting the appliance to the physical network 64
2.4.3 Installing an Exinda Virtual Appliance 65
2.4.4 Scenario 75
2.4.5 Use Case 75
2.4.6 Scenario 77
2.4.7 Use-case 77
2.4.8 Use Cases 78
2.4.9 Related Topics 92
2.4.10 Related Topics 92
2.4.11 Related Topics 102
2.4.12 Related Topics 108
2.4.13 Related Topics 109
2.4.14 Related Topics 116
2.4.15 Related Topics 121
2.4.16 Related Topics 122
2.4.17 Related Topics 124
2.4.18 Related Topics 126
2.4.19 Related Topics 126
2.4.20 Related Topics 134
2.4.21 Related Topics 135
2.4.22 Creating an initial configuration using the Basic Wizard 135
2.4.23 Licensing information 139

2.5 Managing multiple appliances with the Exinda Management Center 144
2.5.1 Getting started with EMC 145
2.5.2 Deploying Exinda Management Center as a Virtual Machine 145
2.5.3 How EMC fits into the appliance feedback loop 147
2.5.4 Exinda Management Center Concepts 147
2.5.5 Best Practices 147
2.5.6 Configuring the EMC 149
2.5.7 Importing appliance configuration 153
2.5.8 Configuring an appliance manually 158
2.5.9 Configuring a bridge 161
2.5.10 Optimizer Policy Tree 164
2.5.11 Sending configuration changes to the appliances 170
3 Using 172
3.1 Defining a network environment 172
3.1.1 Adding network objects 172
3.1.2 Working with dynamically created network objects 182
3.1.3 Working with users and groups as objects 184
3.1.4 Configuring VLAN objects 186
3.1.5 Adding protocol objects 190
3.1.6 Adding application objects 190
3.1.7 Adding and updating application group objects 193
3.1.8 Configuring anonymous proxy detection and monitoring 199
3.1.9 Configuring service level agreement objects 201
3.1.10 Creating an HTML response object 206
3.1.11 Configuring schedule objects 208
3.1.12 Configuring adaptive response limits 210
3.1.13 Configuring application performance score objects 216
3.1.14 Configuring an application performance metric object 229
3.2 Monitoring your network 231
3.2.1 Dashboards 232
3.2.2 Monitoring network traffic in real time 237
3.2.3 Monitoring network interfaces 249
3.2.4 Monitoring network throughput 252
3.2.5 Monitoring service levels 254
3.2.6 Monitoring applications 265
3.2.7 Monitoring network users 275
3.2.8 Monitoring hosts traffic volume 278
3.2.9 Monitoring network conversations 281
3.2.10 Monitoring subnets 284
3.2.11 Monitoring virtual circuits 289
3.2.12 Monitoring the effects of controls 292
3.2.13 Monitoring optimization reports 299
3.2.14 Monitoring Exinda Appliance system performance 304
3.2.15 Viewing monitoring statistics 313
3.3 Monitoring applications with the Exinda Solution Center 322
3.3.1 How performance reports work 323
3.3.2 Using Application Performance reports 324
3.3.3 Bandwidth usage 326
3.3.4 Using the Application Performance Monitor VoIP report 327
3.3.5 Recreational Traffic 329
3.3.6 Data Center Continuity 329
3.3.7 RIAA Notice Prevention 330

3.3.8 Using Network Governance reports 332
3.3.9 Answers to common questions about Solution Center Application Performance 333
3.3.10 Adding and deleting Solutions 334
3.3.11 Setting a new baseline 335
3.3.12 Working with Application Performance charts 335
3.3.13 Investigating a poor application performance score (APS) 336
3.3.14 Investigating unusual performance 336
3.3.15 Deleting an Application Performance report 336
3.4 Managing network traffic 337
3.4.1 The Exinda policy tree 338
3.4.2 Circuits 341
3.4.3 Virtual Circuits 348
3.4.4 Policies overview 362
3.4.5 The optimizer wizard 380
3.4.6 Calculating network performance metrics 384
3.5 Configuring for common use cases and scenarios 389
3.5.1 Monitoring and controlling traffic in a captive portal system 389
3.5.2 Backhauling Internet traffic 394
3.5.3 Setting and enforcing quotas 396
3.5.4 Creating Applications from DSCP-marked traffic (like Riverbed accelerated traffic) 400
3.5.5 Clustering and high availability 401
3.5.6 Controlling anonymous proxy traffic 408
3.6 Managing Exinda Appliances with EMC 409
3.6.1 Viewing appliances in the tenancy 410
3.6.2 Moving appliances within the tenancy 410
3.6.3 Configuration Library 413
3.6.4 Configuring your Appliances through the CLI 450
3.7 Service Delivery Point (SDP) 451
3.7.1 SDP Web User Interface (WUI) and Features 452
3.7.2 Getting started with SDP 453
3.7.3 Changing the default view settings in SDP WUI 461
3.7.4 Tools 465
3.7.5 Managing appliances in SDP 467
3.7.6 The SDP dashboard 473
3.7.7 Viewing reports in SDP 474
3.7.8 Viewing the config log in SDP 476
3.7.9 Install SDP as a Virtual Appliance 477
4 Settings 481
4.1 Network settings 481
4.1.1 NIC configuration 481
4.1.2 IP address configuration 484
4.1.3 Routes configuration 487
4.1.4 DNS and domain names configuration 488
4.1.5 HTTP proxy configuration 491
4.1.6 Email configuration 491
4.1.7 SNMP configuration 494
4.1.8 Integrate with Active Directory 499
4.1.9 IPMI Configuration 519
4.1.10 Overview of QoS by host 523
4.2 System Setup 547
4.2.1 Date and Time Configuration 547
4.2.2 UI Access Configuration 550

4.2.3 SDP Configuration 552
4.2.4 Configure SQL Access 552
4.2.5 Monitoring Configuration 568
4.2.6 Netflow Configuration 572
4.2.7 Create a Scheduled Job 575
4.2.8 Alerts 577
4.2.9 Control Configuration 580
4.2.10 Disk Storage Explained 580
4.3 Certificates 587
4.3.1 Managing Certificates and CA Certificates 587
4.3.2 View all certificates and private keys 590
4.4 Optimization services 591
4.4.1 How Appliance Discovery Works 591
4.4.2 Configuring the Optimization Services 594
4.4.3 Universal Acceleration Service 595
4.4.4 Protocol-specific Acceleration 599
4.4.5 Data caching 625
4.5 Authentication 644
4.5.1 Display a List of Active Users 644
4.5.2 Local User Accounts 644
4.5.3 AAA 645
4.5.4 LDAP Authentication 646
4.5.5 Radius Authentication 647
4.5.6 TACACS+ authentication 647
4.6 System Maintenance 648
4.6.1 Manage System Configuration 648
4.6.2 Factory Defaults 651
4.6.3 Reboot/Shutdown 651
4.7 System Tools 653
4.7.1 Ping 653
4.7.2 Traceroute 654
4.7.3 DNS Lookup 654
4.7.4 Query a remote IPMI Exinda appliance 655
4.7.5 iPerf Client 656
4.7.6 iPerf Server 657
5 Troubleshooting 660
5.1 Diagnostics 660
5.1.1 Diagnostics Files 660
5.1.2 Acceleration Diagnostics 661
5.1.3 Monitor 664
5.1.4 NIC Diagnostics 665
5.1.5 Optimizer Diagnostics 666
5.1.6 RAID Diagnostics 667
5.1.7 TCP Dump 668
5.1.8 View the status of an alert 670
5.1.9 View the status of the community 671
5.1.10 Open a case with Exinda Networks Support Services 672
5.2 Log Files 672
5.2.1 Viewing System Log Files 673
5.2.2 Live Log 673
5.2.3 Tail Log 673
5.2.4 System Logging Configuration 674

5.3 Troubleshoot problems with MAPI acceleration 675
5.3.1 Outlook cannot connect to the Exchange server 676
5.3.2 Outlook slow to send or receive emails 676
5.3.3 Decrease in acceleration of MAPI traffic 676
5.3.4 Reduction ratio for MAPI is different between Client-side and Server-side Exindas 677
5.4 Troubleshoot issues with TCP acceleration 677
5.5 Troubleshoot issues with SMB file acceleration 677
5.6 Troubleshoot issues with Active Directory configuration 678
5.6.1 Exinda Appliance Reboots Every Night 678
5.6.2 WMI Service is not running 679
5.6.3 System account showing in traffic reports 679
5.6.4 No Communication Between the Exinda AD Connector and the Exinda Appliance 679
5.6.5 Exinda AD Connector stops running 679
5.6.6 Excluded Users Still Appear on the Exinda Appliance 680
5.6.7 Changes to the Exinda Active Directory Controller have no effect 680
5.6.8 The IP addresses are not being mapped to the AD users and groups 681
5.7 Troubleshooting Edge Cache 682
5.8 Topology troubleshooting 684
6 ExindaCommand Line Interface (CLI) 685
6.1 Using the Command Line Interface 685
6.1.1 Accessing the CommandLine Interface 685
6.1.2 CLI Configuration Jumpstart 686
6.1.3 Configure command line options 687
7 Copyright 689
7.1 Exinda End User License Agreement (EULA) 689
7.2 GNU General Public License (GPL) 690
7.2.1 Preamble 690
7.2.2 TERMS AND CONDITIONS 691
7.3 BSD 2.0 697
8 Safety and Compliance 699
8.1 EMC Notice 699
8.2 Compliances 699
8.2.1 CE 699
8.2.2 FCC Class A 699
8.3 Safety Guidelines 700
8.3.1 Lithium Battery Caution 700
9 Predefined Applications and Application Groups 701
9.1 Predefined Applications and Supported L7 Signatures 701
9.2 Predefined Application Groups 740

Exinda Network Orchestrator 1 Introduction |8
1 Introduction
Every day critical business network traffic and recreational network traffic compete for bandwidth on strained networks.
The Exinda Network Orchestrator inspects, monitors and manages network traffic, maximizing speed and data flow
efficiency, giving priority to mission critical business applications across your LANs and WANs.
1.1 How an Exinda implements WAN optimization
As soon as you connect it to your network, an Exinda Appliance begins monitoring network traffic and gathering
statistics to help you make informed optimization decisions. The Exinda provides a multitude of settings, parameters and
tools you can use to tweak and squeeze every last byte of bandwidth from your network hardware.
Traffic shaping techniques, classifying and rationing bandwidth in alignment with your company goals and daily
needs
Intelligent data caching for rapid access to frequently used files and data stores
Data deduplication to eliminate redundant data and free bandwidth
Network monitoring, analysis and management to identify and limit social network traffic, gaming traffic, streaming
traffic and other non-essential traffic types
And getting started with Exinda Network Orchestrator is easy.
First you connect an Exinda Appliance to your network. Next, through the combination of an automatic, intelligent
discovery process and manual definitions, the Exinda Appliance learns about your network. Then you specify policies to
regulate traffic in your network. After that, you use Exinda's robust set of monitoring tools to gain total insight into the
traffic on your network and adjust your policies as needed.
1.2 What is network orchestration?
Network orchestration is the idea that networks can be programmed to support applications, giving priority to one over
another.
The Exinda Network Orchestrator provides the capability to detect and define data streams according to their origins,
destinations and other characteristics. Then it gives you the capability to set up rules governing how much network
resources a given data stream is allowed to consume.
An Exinda Network Orchestrator logically transforms your network from a group of disparate routers, hubs, switches,
bridges, repeaters and blade servers, working independently, into a single, responsive, service-based asset.
1.3 Exinda system components
Exinda includes a number of required and optional components that can be installed in your organization's
infrastructure.
1.3.1 Exinda Appliance
The Exinda product line includes a series of hardware and virtual network appliances designed to plug directly into your
environment with minimal effort. Appliances come in a range of sizes to handle every networking scenario and size,
from small offices with dozens of users to very large data centers that support hundreds of thousands.
For more information, refer to The Exinda product line (page 9).

Exinda Network Orchestrator 1 Introduction |9
1.3.2 Exinda Web UI
Exinda offers to user and administrator a Web User Interface that allows users to configure policies and monitor the
appliances performances through a variety of dashboard and reports.
1.3.3 Exinda Management Center
The Exinda Management Center (EMC) provides complete management insight and configuration control of your
Exinda Network Orchestrator appliances from one central console. All applications, devices, users, and activities across all
network locations are managed from a central location giving IT Administrators the ability to manage network policies
and manage appliance configuration across the entire organization.
For more information, refer to Managing multiple appliances with the Exinda Management Center (page 144).
1.3.4 Exinda Solution Center
The Exinda Solution Center provides a series of predefined monitors you can run to generate network performances
reports for applications like FTP, SSH, Salesforce.com, Microsoft Office365, VoIP, and many more.
For more information, refer to Monitoring applications with the Exinda Solution Center (page 322).
1.3.5 Exinda Service Delivery Point (SDP)
The Exinda Service Delivery Point (SDP) is a high performance add-on designed for enterprise network environments
looking to centrally manage multi-box Exinda deployments. It is available as both a hosted service and a virtual appliance.
SDP simplifies the tasks of installing, configuring, monitoring and reporting WAN optimization appliances. It is a key
differentiator in the traffic shaping & WAN optimization space. A fundamental component of Exinda's Unified
Performance Management solution, it rounds out the Exinda product line and makes it the most comprehensive and
effective solution for achieving peak application performance.
With secure access via a Web browser, SDP subscribers gain full visibility into network usage and control over applications
at any WAN site. SDP helps IT managers identify and control the underlying causes of poor network performance,
whether it be unwanted recreational peer-to-peer traffic or a misconfigured server.
Custom reports provide a granular analysis of network usage, top applications and top URLs. This information is critical in
setting an optimal network policy, throttling back applications and for future capacity planning.
For more information, refer to SDP Web User Interface (WUI) and Features (page 452).
1.4 The Exinda product line
The Exinda product line includes a series of hardware and virtual network appliances designed to plug directly into your
environment with minimal effort. Appliances come in a range of sizes to handle every networking scenario and size,
from small offices with dozens of users to very large data centers that support hundreds of thousands.
1.4.1 Exinda physical appliances
The tables below contain the technical specifications, hardware profiles and capacity guidelines for each Exinda
Network Orchestrator model listed in order of capacity, starting with the smallest.

Exinda Network Orchestrator 1 Introduction |10
Network Orchestrator 3062 Series
Screenshot 1: Front view of the Exinda 3062.
Screenshot 2: Rear view of the Exinda 3062.
Specification Details
Designed for Small Office
Supported Users Up to 1,600
Traffic Shaping
Shaping Throughput 150 Mbps
Concurrent Flow 45,000
New Connection Rate 4,000/s
Packets Per Second 45,000/s
Number of Traffic Policies 512
Traffic Acceleration
Acceleration Throughput 20 Mbps
Edge Cache Throughput 20 Mbps
Optimized Connections 2,000
Network Diagnostics

Exinda Network Orchestrator 1 Introduction |11
Specification Details
APS Objects 100
SLA Objects 100
PDF Reports 20
Hardware Specifications
Form Factor Desktop or 1U rack mount
Data Store/Cache Size 500 GB
NICs (Default) 2 Bridge Pairs, or 1 Bridge Pair plus 1 Management
NICs (expandable to) -
Redundant Power No
Network Orchestrator 4062 Series
Screenshot 3: Front view of the Exinda4062.
Screenshot 4: Rear view of the Exinda 4062.
Specification Details
Designed for Medium Office

Exinda Network Orchestrator 1 Introduction |12
Specification Details
Supported Users Up to 38,000
Traffic Shaping
Shaping Throughput 1 Gbps
Concurrent Flow 220,000
New Connection Rate 10,000/s
Packets Per Second 200,000/s
Number of Traffic Policies 1024
Traffic Acceleration
Acceleration Throughput 30 Mbps
Edge Cache Throughput 50 Mbps
Optimized Connections 6,000
Network Diagnostics
APS Objects 250
SLA Objects 250
PDF Reports 60
Hardware Specifications
Form Factor Desktop or 1U rack mount
Data Store/Cache Size 1 TB
NICs (Default) 3 Bridge Pairs, 1 Management, 1 Cluster (10GbE and 1Gb Fiber options available)
NICs (expandable to) 5 Bypass Bridges
Redundant Power Yes
Network Orchestrator 8063 Series
Screenshot 5: Front view of the Exinda 8062. The hardware of the Exinda 8062 and 8063 is the same.
Screenshot 6:

Exinda Network Orchestrator 1 Introduction |13
Specification Details
Designed for Small to Medium Data Center
Supported Users Up to 250,000
Traffic Shaping
Shaping Throughput 5 Gbps
Concurrent Flow 500,000
New Connection Rate 20,000/s
Packets Per Second 650,000/s
Number of Traffic Policies 2048
Traffic Acceleration
Acceleration Throughput 150 Mbps
Edge Cache Throughput 175 Mbps
Optimized Connections 25,000
Network Diagnostics
APS Objects 300
SLA Objects 300
PDF Reports 100
Hardware Specifications
Form Factor Desktop or 1U rack mount
Data Store/Cache Size 2 TB, RAID 10
Memory 32 GB
NICs (Default) 1 management, 1 cluster, IPMI support
Interface NIC Slots 1 half height occupied, 1 full height
NICs (expandable to) 4 bypass bridges
Redundant Power Yes
Network Orchestrator 10063 Series
Screenshot 7: Front view of the Exinda 10062. The hardware of the Exinda 10062 and 10063 is the same.

Exinda Network Orchestrator 1 Introduction |14
Screenshot 8: Rear view of the Exinda 10062. The hardware of the Exinda 10062 and 10063 is same.
Specification Details
Designed for Medium to Large Data Center
Supported Users Up to 400,000
Traffic Shaping
Shaping Throughput 10 Gbps
Concurrent Flow 1,200,000
New Connection Rate 32,000/s
Packets Per Second 1,400,000/s
Number of Traffic Policies 4096
Traffic Acceleration
Acceleration Throughput 500 Mbps
Edge Cache Throughput 250 Mbps
Optimized Connections 32,000
Network Diagnostics
APS Objects 300
SLA Objects 300
PDF Reports 100
Hardware Specifications
Form Factor Desktop or 2U rack mount
Data Store/Cache Size 1.8 TB, RAID 10
Memory 64 GB
NICs (Default) 1 management, 3 extra on-board interfaces, 1 IPMI
Interface NIC Slots 3 half height, 2 full height
NICs (expandable to) 10 bypass bridges
Redundant Power Yes

Exinda Network Orchestrator 1 Introduction |15
Network Orchestrator 12063 Series
Specification Details
Designed for Large Data Center
Supported Users Up to 600,000
Traffic Shaping
Shaping Throughput 15 Gbps
Concurrent Flow 1,800,000
New Connection Rate 38,000/s
Packets Per Second 1,800,000/s
Number of Traffic Policies 4096
Traffic Acceleration
Acceleration Throughput 2 Gbps
Edge Cache Throughput 500 Mbps
Optimized Connections 49,000
Network Diagnostics
APS Objects 400
SLA Objects 400
PDF Reports 150
Hardware Specifications
Form Factor Desktop or 2U rack mount
Data Store/Cache Size SSD 1.6 TB, RAID 2
Memory 256 GB
NICs (Default) 1 management, 3 extra on-board interfaces, 1 IPMI
Interface NIC Slots 4 half height, 3 full height
NICs (expandable to) 18 bypass bridges
Redundant Power Yes
1.4.2 Exinda virtual appliances
The virtual Exinda Network Orchestrator provides the same monitoring, reporting and control features as the Exinda
hardware appliances. Capacity is determined by a combination of licensing and underlying hardware.
Exinda Virtual
A virtual Exinda Network Orchestrator runs on a host machine under a hypervisor, using dedicated resources. The
minimum dedicated hypervisor hardware requirements are listed in the table below:

Exinda Network Orchestrator 1 Introduction |16
Model EXNV-
3062
EXNV-
4062
EXNV-
8063
EXNV-10063 EXNV-12063
CPU (# x GHz) 4 x 2.0 4 x 2.4 8 x 2.4 12 x 2.4 (if license <=
300M)
24 x 2.4 (if license >
300M)
12 x 2.4 (if license <=
300M)
24 x 2.4 (if license >
300M)
Memory (GB) 6 8 32 64 64
Disk Space
(GB)
250 250 500 500 2000
Requirements:
Intel Xeon class, 64-bit CPU with VT Enabled
Hard drive space on a single disk
NOTE
Disk extending techniques are not supported on virtual appliances. Adding additional storage requires a hard disk.
1.5 Product naming conventions
Encoded within the Exinda Network Orchestrator model numbers are the features and licensing of the appliance.
This is the model number syntax:
<hardware series> <software license> <hardware version>-<bandwidth parameters>
hardware series The hardware model number.
software license The purchased license.
hardware version The platform configuration version.
bandwidth optimization | bandwidth acceleration / optimization The amount of bandwidth for acceleration, visibility and QoS.
Example:
Product model 8862-100/500 reflects the following information:
Series - 8000
Software license - x800 (acceleration, visibility and QoS control)
Hardware version - 6.2
Bandwidth - 100 Mbps (100 Mbps for acceleration, 500 Mbps for visibility and QoS)

Exinda Network Orchestrator 2 Getting started |17
2 Getting started
This getting started guide steps through the basic process of installing, configuring and using your Exinda Network
Orchestrator. Each step builds on the previous step and contains links to relevant help topics with detailed instructions to
get your Exinda up and running in your network environment.
1 Install your Exinda Appliance
If you are using a Exinda Appliance hardware box, refer to Installing the Hardware Appliance into the Network.
Installing a Exinda Virtual Appliance depends on the hypervisor it supports, refer to Overview of the Virtual Appliances for
installation instructions on supported hypervisors.
2 Start monitoring the traffic
Start monitoring the traffic that passes through your Exinda Appliance. For more information, refer to Monitoring your network
(page 231).
If you are looking to monitor particular traffic patterns or usage, you can configure objects to support this.
Create network objects to monitor the traffic usage of branches, departments, classes of devices etc. A network object can
include one or more subnets and one or more IP addresses. For more information, refer to Adding network objects (page
172).
Configure active directory to identify traffic usage of users on the network. For more information, refer to Integrate with
Active Directory (page 499).
Create an application object if a new or custom application is not identified by the system. For more information, refer to
Adding application objects (page 190).
3 Configure Traffic Policy
Configuring traffic policy requires a bit of setup, however, the simplest solution is to run the Optimizer Policy Wizard. By
answering a few questions in the wizard, the system then sets up a traffic policy that effectively controls the general traffic
scenarios. See Optimizer Policy Tree to understand how the policy configuration works.
You can also customize the traffic policy and have multiple policies in place to match your requirements. For more information,
refer to Policies overview (page 362).
4 Create alerts and application performance monitors
Set alerts on various aspects of the traffic. You can monitor the user experience of particular applications and set an alert when
the user experience becomes poor. You can monitor the availability of a site by pinging the IP address and define an alert when
the latency exceeds your specified threshold or when the packet loss is severe. You can monitor for particular activity that may
indicate an issue, such as asymmetric route detection, maximum accelerated connections exceeded, NIC collisions, or dropped
packets, and so on.
To monitor the user experience of particular applications, create an Application Performance Score object.
To monitor a particular IP address for availability, create an Site Service Level Agreements object.
The alerts are sent by email assuming the appliance is configured to send e-mail. For more information, refer to Email con-
figuration (page 491).
5 Find solutions and get notified
The Exinda appliance displays solutions and notifies you if certain undesirable thresholds are exceeded or if other notable traffic
patterns are identified so that you can take action to tune your network.
For more information, refer to Monitoring applications with the Exinda Solution Center (page 322).
For more information, refer to Alerts (page 577).
6 Control and accelerate traffic accordingly
Go back and tune traffic policy to control and accelerate traffic to ensure business critical traffic is ensured the bandwidth that is
needed, and that the traffic is prioritized and accelerated properly.
2.1 WUI Guided Tour
To view an interactive slide show of the UI, go to Guided Tour

Exinda Network Orchestrator 2 Getting started |18
2.2 Deployment options
An Exinda Appliance fits almost anywhere in your network environment. As a general rule, anywhere network packets
move from one device to another, whether via physical cables or virtualization, you can plug in an Exinda Appliance.
In this section of the guide, you'll walk-through the most common Exinda Appliance deployments.
Many of the example topologies you'll see are used by Exinda customers from various industries around the globe. The
list is by no means exhaustive, but you'll undoubtedly find something similar enough to your network environment for
you to build on.
2.2.1 Key terms
Throughout the deployment options section, you'll see common networking terms you may already be familiar with.
Depending on your background and experience, you may have seen the terms used slightly differently than the way
they're used in this guide.
To make the deployment examples clear and concise, the terms and definitions are included here.
Term Definition
In-path In-path describes a type of topology and refers to deploying an Exinda Appliance between network devices that
send and receive data packets to each other, like a switch and a router. When an Exinda Appliance is in-path, it
automatically inspects all packets traveling along its path.
Out-of-path An Exinda Appliance connected to only one network device is considered out-of-path. By default, that implies
network packets don't naturally travel through the Exinda Appliance to get to their destinations. For example,
connecting an Exinda Appliance to a switch or hub on the LAN. In this case, the Exinda Appliance behaves like any
other network client and requires specific protocols or modes to enable packet monitoring and inspection.
Inline In network terminology, an inline device receives packets and forwards them to their intended destination. Routers,
firewalls and switches are examples of inline devices. The inline designation also alerts you the device is critical to
network function. If the device goes down, network traffic is affected. In an in-path topology, an Exinda Appliance is
deployed Exinda Appliancesinline in the network.
Clustering Grouping Exinda Appliances together in systems to perform the same functions in each system or to mirror each
other. Example scenarios include failover, load balancing and multipath networks.
Application
Acceleration
Application Acceleration is an intelligent network enhancer based on a set of proprietary algorithms embedded in
an Exinda Appliance. It reduces latency, increases network throughput, frees network capacity and a whole lot more.
To get the benefits of Application Acceleration, you need at least two Exinda Appliances.
2.2.2 Basic characteristics and behaviors of Exinda Appliances
All Exinda Appliance hardware models share some basic characteristics and behaviors. This list provides helpful
information to keep in mind while planning and implementing a deployment.
Every Exinda Appliance has at least one pair of hardware bypass ports marked LAN and WAN.
Exinda Appliance LAN and WAN ports failover to pass-through mode in the event of system failure or power loss.
It's best practice to deploy the Exinda Appliance powered off. This ensures the hardware bypass is working.
NOTE
There may be a short interruption to network connectivity while the Exinda appliance switches out of bypass mode
during boot-up. Although switching in and out of bypass takes less than a millisecond, this may force neighboring
equipment to renegotiate their layer 2 topology, which could take several seconds

Exinda Network Orchestrator 2 Getting started |19
2.2.3 In-path topologies
Exinda Appliances are often deployed between a core switch and a WAN/Internet router. In this type of deployment,
the Exinda Appliance is referred to as inline, which is a way to describe a network device in a primary network path that
receives packets and forwards them to their destinations. In this case, the Exinda Appliance receives packets from the
core switch and sends them to the Internet/WAN router and vice versa.
Screenshot 9: Inline deployment of an Exinda Appliance
Usually, the WAN port on your Exinda appliance is cabled to the WAN/Internet router, using the crossover Ethernet cable.
And the LAN port on your Exinda appliance is cabled to the core switch, using the straight Ethernet cable. If your
appliance has a dedicated management port, it also needs to be cabled to an internal switch using an Ethernet cable.
Both cables are shipped along with the appliance.
For more information, refer to Basic characteristics and behaviors of Exinda Appliances (page 18).
For specific information about your model, download its Quick Start Guide.
Once all Ethernet cables are in place, power the Exinda Appliance off and ensure the network connectivity. Then, power
on the Exinda Appliance, let it fully boot and ensure network connectivity.
The following topics describe how to configure and operate your Exinda Appliance within various in-path topologies.
Main site Internet link topology: single site with one Exinda Appliance
A simple way to monitor network traffic between the Internet and your local network, is to plug-in your Exinda Appliance
on the network path between your network users and the router, firewall or other gateway device that controls access
from your LAN to the Internet.

Exinda Network Orchestrator 2 Getting started |20
Screenshot 10: Main site internet link deployment
The topology depicted in the diagram shows a basic Exinda Appliance network deployment with several sets of users
from a Main Site and Branch sites linking over the Internet. In Exinda terminology, this general configuration is aptly
named, Main Site Internet Link topology.
The left side of the diagram labeled "Main Site" represents a typical office environment, comprising network users, a
switch, a router and an Exinda Appliance.
The middle of the diagram represents the Internet and the right side of the diagram represents all the people,
machines and programs that want access to servers and applications hosted at the Main Site.
In this setup, the Exinda Appliance is connected to the switch and the router on the Main Site. So network traffic
emanating from the Main Site to the Internet and traffic from the Internet to the Main Site must pass through the Exinda
Appliance.
With the Exinda Appliance deployed between the switch and the router, you get visibility to all the traffic entering and
leaving the Main Site network via the router.
Installing the Exinda Appliance in a main site internet link topology
This install is straightforward and requires just a few steps.
The high level plan is to plug your Exinda Appliance inline between the switch and router.
In most network environments, the switch will already be physically connected to the router. We're going to temporarily
disconnect the switch and router from each other, insert the Exinda Appliance between them and reconnect
everything with the Exinda Appliance firmly in the middle.
NOTE
In network terminology, an "inline" device receives packets and forwards them to their intended destination.
Routers, switches and firewalls are examples of inline devices. The inline designation also alerts you that the device
is critical to network function. If the device goes down, network traffic is affected.
1. Connect the WAN port to your router/firewall using a crossover cable.
2. Connect the LAN port to the LAN switch.
3. Leave the Exinda Appliance powered off.