Beruflich Dokumente
Kultur Dokumente
Virtual
Connection
Mesh
How it works
The PacketFabric Cloud Router creates a single When a customer adds a cloud provider to the
routing domain for any two or more independent routing domain, PacketFabric creates a Cloud
connections to cloud providers. It does not Router instance immediately adjacent to that
require a physical connection or infrastructure. provider. From there, PacketFabric provisions
There is no need to own or maintain any a Layer 2 virtual connection between the
equipment, to wait for physical infrastructure distributed Cloud Router instance and the cloud
deployment, or to hairpin data transfer through provider’s egress port, over which a BGP session
existing infrastructure. is established.
You can use PacketFabric’s Cloud Router to Each Cloud Router is then connected via Layer
connect multiple regions of a single cloud 3 mesh over the PacketFabric platform to every
service provider, connect multiple cloud service other Cloud Router instance in its routing domain.
providers in the same region, or connect multiple
cloud service providers in different regions. The service demarcation points are at the
egress ports attached to the cloud provider. The
PacketFabric’s Cloud Router is a distributed physical connection between the PacketFabric
service that consists of multiple virtual router egress port and the cloud service provider is
instances on the PacketFabric network. Each shared among multiple PacketFabric customers.
router instance is created as necessary for However, each customer’s service is secured
optimal routing and scaling. within its own private Layer 2 connection.
NAAS PLATFORM
Disaster Recovery
US WEST 2
SCENARIO: The customer relies on multiple
BGP PEER
cloud providers for automated data Amazon Amazon Redshift
backup and recovery, and requires reliable S3 EC2
CONTACT
packetfabric.com
sales@packetfabric.com
+1-844-475-8322
@packetfabric @packetfabric
1/21/21