What would I use if for? What are some use-cases?
| Use-case #1: I have software that REQUIRES multicast for service discovery. A surprising number of virtual appliances built for virtual infrastructure but not cloud infrastructure REQUIRE multicast protocols in order to function. This is also true of many enterprise software packages (grid computing packages, database clusters, wikis and more). Even inside the enterprise complexity and lead times prevent shared use of available resources in disparate customer controlled data centers because VLAN reconfiguration would be too expensive. VPN-Cubed allows you to get the multicast traffic into the overlay network before it is rejected by the underlying network infrastructure. This allows you control of your protocols. |
|
 |
| |
|
|
Use-case #2: I am an early adopter of cloud computing and love the flexibility provided by public cloud like Amazon EC2 but I want to control my own network addresses, not be given some different set of VLAN addresses when I reboot my servers. VPN-Cubed gives you control of your addressing allowing you to give your cloud servers static addresses that only change when YOU want them to. Local infrastructure control of addressing in the public clouds!
|
|
 |
| |
|
|
Use-case #3: I have completed some of my “datacenter to cloud” migrations but am now under pressure to use new monitoring and management tools. Can’t I use my existing datacenter NOC (network operations center)? VPN-Cubed allows you to simply set up an overlay network for the express purpose of connecting cloud VLANS (at EC2 for example) to data center management installations using popular commercial systems like Tivoli, Unicenter, OpenView, as well as leading open source systems like Nagios, Hyperic and GroundWorks.
|
|
 |
| |
|
|
Use-case #4: I am a cloud early adopter and I want to use both Amazon EC2 USA and Amazon EC2 Europe for both fail over and data privacy issues. How can I securely link the two environments and treat them as one logical network? VPN-Cubed does this “out of the box” with a pre-packaged solution “VPN-Cubed for EC2” available for self-service clients as well as those needing some professional services support.
Check out our New VPN-Cubed for EC2 Paid AMIs and get your VPN-Cubed overlay network up and running in EC2 NOW! |
|
 |
| |
|
|
Use-case #5: I have an ISV who has a hardware (or software) solution which I would like to evaluate but it will be quite disruptive for me to install. Isn’t there some way I can test their solution as if it was on my local network? VPN-Cubed allows your ISV to install their solution as a virtual server in a public cloud like EC2, yet make it available to a DMZ or particular set of VLANs in your corporate environment. The burden of testing the ISV solution should rest with your vendor with minimal impact or workload on your team.
|
|
 |
| |
|
|
Use-case #6: I don’t use public clouds but my organization uses virtual infrastructure extensively (VMware, Citrix Xen, etc.). We have multiple data centers which we attempt to use flexibly between business units, but the IT organization can’t keep up with the VLAN changes needed to make business units comfortable with shared infrastructure. VPN-Cubed works in private clouds or virtual infrastructure environments allowing overlapping infrastructure sharing arrangements to be constructed. Business unit demands can be rapidly constructed using overlay networks provided by VPN-Cubed.
|
|
 |
What's included?
VPN-Cubed is offered as a packaged service. While most implementations will vary based on a customer's unique topology, the basic services includes:
| * |
An overlay network created through the use of VPN-Cubed Managers. VPN-Cubed Managers can be thought of as virtual switches, virtual routers, or virtual bridges depending on the topology needs. |
| * |
Customer controlled addressing, topology, protocols and encryption for up to 50 cloud or virtual infrastructure devices utilizing up to 4 VPN-Cubed Managers. |
| * |
1-year configuration support included (up to 12 hours of tele-consultation) |
| * |
Additional devices beyond base package - optionally available |
| * |
Additional VPN-Cubed Managers for more complex installs - optionally available
|
| * |
Overlay network design services - optionally available
|
Technical Overview
Interested in the finer details of why VPN-Cubed is different than a regular VPN or tunnel? Check out this VPN-Cubed Technical Overview for more details.
Technical specifications:
| * |
Customer-controlled security using an encrypted LAN in a single cloud and an encrypted WAN across multiple clouds |
| * |
Enhanced security via VPN-Cubed, in addition to customer's cloud vendor VLAN, and individual virtual server firewalls |
| * |
Multicast support in the cloud enables seamless software compatibility without costly changes |
| * |
Customer-controlled network addresses for their devices in a cloud or across multiple clouds |
| * |
Enables failover strategies from one cloud vendor to another |
| * |
Available for use with most operating systems, virtual environments and third-party cloud offerings including Amazon EC2 and Flexiscale |
| * |
Patent-pending solution |
Support for...
| * |
Virtualization Formats: VMware (Workstation, Virtual Server, ESX Server), Citrix Xen, Microsoft Hyper-V, Open Source Xen, Parallels (Workstation, Server), Amazon AMI, KVM, Sun (xVM and xVM Ops Center 2.0), and others as requested. |
| * |
Operating Systems: Windows Server 2008, Debian (Etch, Lenny), Ubuntu (8.04LTS), Fedora 9, CentOS 4, Red Hat Enterprise Linux 5, openSuse, Novell SLES, and others. |
| * |
Clouds: Amazon EC2, ElasticHosts, Flexiscale, GoGrid, Mosso, and others as requested. |
Hey, I have more questions...
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)
|
