Inline deployment with externally attached LAN

In this use case, the Exinda Virtual Appliance is set up for inlineIn 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. mode deployment with an externally attached LANLocal area network. There are primarily two scenarios for inline deployment of the virtual appliance:

1. The LAN-side users and applications connect to the Exinda Virtual Appliance through a physical NIC interface.
2. The applications are virtualized and isolated on the same host as the Exinda, on the LAN side interface of the Exinda Virtual Appliance.

This use case discusses the first scenario.

Scenario

Scenario details

• The branch users access virtualized local services (such as print, DHCPDynamic Host Configuration Protocol, and Active Directory).
• At least two physical NIC interfaces are bridged together in the virtual Exinda Virtual Appliance.
• User connections from the branch office to the Data Center applications are in line through the Exinda Virtual Appliance on both ends of the connections, and through external NIC interfaces.
• The Exinda provides diagnostic, shaping, and acceleration for all traffic in this configuration.
• Optionally, install the Exinda Virtual Appliance in a separate host in an inline mode configuration and connect through an external switch.

Use Case

In this scenario the hypervisor configuration is done at either a branch office with virtual infrastructure, or in the data center where the applications are running on the host VM. So, the local users accessing the WANWide Area Network leverage the Exinda for diagnostics, shaping, and acceleration.

Use-case for Inline deployment with externally attached LAN

In this use-case:

• The local LAN is sitting behind the hypervisor.
• The host has four NIC interfaces. NIC 0 is dedicated for management of the system and NIC 1 is idle or used for other purposes.
• NIC2 and NIC3 are mapped to SW2 and SW3.
• SW2 and SW3 are mapped to Exinda Virtual Appliance ETH2 and ETH3.
• ETH2 and ETH3 are mapped to NIC 2 and NIC 3, and are configured and bridged together by the Exinda virtual appliance.
• The data path from a client on the local LAN goes through the Exinda virtual appliance in Inline Mode and out to the WAN.
• Exinda Exinda Virtual Appliance software version is 7.4.2.
• This deployment works with either local or external storage.