# Overview

<!--- Template Guidance 
This is the architectural overview of your product and where you explain key concepts and introduce domain specific terminology. 
Don't rely on text alone: diagrams tend to go a long way to make these concepts clear. 
The goal is to ensure that people get a good mental model of what problem the product is solving and how it is solving it.
The target audience here is system designers and architects. 

NOTE: Take a look at the overview of NLB (community/community/content/product/networking/nlb/overview/_index.md) for a good reference example.
-->

Private Connect lets you connect your on-premises or hosted infrastructure with
one or more private networks from a single Exoscale organization. This guide
will show you how to set up Private Connect.


## Terminology
MAC (Media Access Control)
: A unique hardware address assigned to a network interface for communication
  on a local network

WAN (Wide Area Network)
: A network that spans a large geographic area, connecting multiple LANs

MAN (Metropolitan Area Network)
: A network that covers a city or campus, larger than a LAN but smaller than
  a WAN

HSRP (Hot Standby Router Protocol)
: A Cisco protocol that provides gateway redundancy by designating active and
  standby routers

VRRP (Virtual Router Redundancy Protocol)
: An open standard for assigning a virtual IP to multiple routers for gateway
  failover

LCAP (Local Cloud Access Point)
: A physical interconnect location enabling private, low-latency cloud access


## Features
Your situation to start with Private Connect can differ depending on where you store your infrastructure. If your infrastructure is collocated in the __same datacenter or datacenter campus__ as the Exoscale zone:

- The connection to Private Connect can be established via cross connections between Exoscale and your racks/cage within the datacenter. You are responsible for the cross connections setup and costs. Exoscale will provide a location, circuit-ID and letter of agreement (LOA) upon subscribing to Private Connect which let you order the cross connections to the datacenter operator.

- The connection in Equinix-based zones can be established using Equinix Cloud Exchange to reduce cross-connection costs and Private Connect costs. After you subscribe to Private Connect, Exoscale will provide the ECX information for interconnection.

If your infrastructure is located __in a separate datacenter__ from the Exoscale zone a WAN or MAN connection is required.