Exinda Network Orchestrator
2 Getting started
|
48
Screenshot 21: Use-case for Inline deployment with an isolated virtual LAN and virtual applications
In the diagram above, a virtual LAN is isolated and sits behind the Exinda Virtual Appliance all running on the same
host hypervisor.
The host has two NICs; NIC 0 is dedicated for management of the system and NIC 1 is idle or used for other purposes.
All virtual application workloads are configured in the hypervisor to SW2.
SW2 is configured to map to Exinda Virtual Appliance ETH2
ETH2 is configured as part of a bridged connection defined as BR2.
BR2 bridges NIC 2 and NIC 3 together in the Exinda virtual appliance. The data path for any application connected
to the SW2 virtual switch goes through the Exinda Virtual Appliance in inline mode through the ETH2/ETH3 bridged
configuration and out the NIC3 interface to the WAN.
OPTIONAL: If this is a branch office with local users, configure local users to connect through the NIC2 physical inter-
face and SW2/ETH2 Exinda Virtual Appliance interface and out to the WAN. This require mapping a third NIC interface.
Out-of-band (WCCP) mode
You can set up your Exinda Virtual Appliance in out-of-band mode, using WCCP protocol for deployment. This
deployment is typical for customers who have chosen to redirect a percentage of their traffic for acceleration and traffic
shaping through the Exinda Virtual Appliance. In the event the Exinda Virtual Appliance fails, all traffic previously
redirected to the Exinda Virtual Appliance goes through un-optimized and un-accelerated.
Use Cases
Summary of Contents for EXNV-10063
Page 369: ...Exinda Network Orchestrator 4 Settings 369 ...
Page 411: ...Exinda Network Orchestrator 4 Settings 411 Screenshot 168 P2P OverflowVirtualCircuit ...
Page 420: ...Exinda Network Orchestrator 4 Settings 420 Screenshot 175 Students OverflowVirtualCircuit ...