VIRL is now available on
Packet's bare metal cloud platform!

GET STARTED Sign up with Packet

Why VIRL on Packet?


COST EFFICIENT

Packet provides highly competitive hourly rates on a range of bare metal servers to suit your budget - starting at as low as $0.40/hr!
Learn more about Packet's pricing.

POWERFUL AND RELIABLE

With the performance of a resourceful bare-metal system, you can quickly and easily build and get to work with more demanding network topologies where lower-end system would struggle.

SAVES TIME

Packet provides premium bandwidth and set up automation that allows for 8-minute deploys.
When you're done, just terminate your server instance easily with one single command.


Launching from your VIRL server

If you are an existing customer with a valid VIRL license key and a local VIRL server successfully installed, you can launch VIRL on Packet directly from your local server using the Terraform toolset from Hashicorp. Your new VIRL server will be provisioned for you within 30 minutes!
We are also DOUBLING your node limit for free when you use VIRL on Packet.

Sign up with Packet to get your API key
Read step-by-step instructions
Watch tutorial





Launching from VIRL launcher app

If you have a valid VIRL license key and but do NOT have your VIRL instance installed or prefer not to launch through your VIRL server, you can launch VIRL on Packet with Virtualbox or AppCatalyst.
We are also DOUBLING your node limit for free when you use VIRL on Packet.

Sign up with Packet to get your API key
Read step-by-step instructions
Watch tutorial





READ DISCLAIMER


Get your VIRL license today today and set up your own server on Packet!


PURCHASE VIRL

More information and FAQ





open all close all

In order to use the VIRL on Packet service, you must have a valid VIRL license key. You can purchase a key here. Already have one? Download your key.
You must register with Packet.net and create your account with a method of payment through credit card or paypal. You need a Packet API key to proceed.
If you already have a VIRL instance installed, you can launch VIRL on Packet directly from your VIRL server. See detailed instructions or watch the tutorial.
Alternatively, use the VIRL launcher app with Virtualbox or AppCatalyst to set up your VIRL on Packet server. See detailed instructions or watch the tutorial.
When using the VIRL on the Packet platform, you will be charged for the serveron an hourly basis at the rate set based on the server type that you're using (See Packet's pricing details).
By using the platform, you agree to be bound by the terms and conditions of this disclaimer. If you do not agree to the terms and conditions herein, then you must immediately cease all access and use of the VIRL platform through the Packet Bare Metal platform, or the Packet Bare Metal platform, itself.
If you have larger topologies, or want to experiment with virtual machine images that consume more memory and CPU, then the range of server types that Packet offer are perfect places to run VIRL. Remember that since this is running in the Cloud, you can also use VIRL when you're traveling and away from your home server.
You don't have to have VIRL installed in order to use VIRL on Packet. Using the simple 'VIRL boxcutter' launcher together with a valid VIRL license key, you can bring up your own VIRL server in the cloud whenever you need it. See detailed instructions.
The VIRL servers are exposed on the Internet. SSH and OpenVPN are the only two ways in which you are connected to your server. However, if you disable the default security features, you are responsible to maintain the security of your own system.
Yes! All of the features that you can use on your local VIRL instance, you can also use remotely.
No - this is a bare-metal solution, not a virtual machine solution. When your VIRL server is terminated, all information, vm images, topologies etc are deleted from the server.
Yes, it is possible to connect VMs running on a local VIRL server to VMs running on Packet's cloud platform.
The VIRL servers are configured with a 'dead man's timer' which is set to expire after four (4) hours. At this point, the server will be terminated. You can alter the timer as you see fit. The timer is there to try to avoid 'unexpected charges' if you were to forget to terminate the server. Ultimately, the user is responsible for ensuring termination of the server when work is done. Please see the Running Cost and Dead Man’s Timer sections below for more details.
You are solely responsible for ensuring that you terminate your VIRL server instance in order to avoid unexpected charges. If you forget to or otherwise do not terminate your VIRL instance for whatever reason, then you are solely responsible for the settlement of any and all associated costs and charges incurred with Packet.net. Neither Cisco nor Packet will be responsible or liable for any costs, damages, charges or other amounts incurred by you in connection with your use of the packet service.
Yes - the only exception is if you are using Static IP addresses on the Flat network (172.16.1.x by default). When using VIRL on the Cloud, the Flat network is 172.16.11.x, so you will need to adjust your Static IP addresses accordingly.
For 3rd party VMs images, please remember that the VM images are not retained. When you turn down the server, all information, VM images, topologies, etc. will be deleted from the server.
Packet have data-centers on the East and West Coast of the US, as well as in Holland. VIRL servers can be started in each of these locations.
When a VIRL server is brought up on the Packet platform, charging will commence. This includes the period where the VIRL software is being automatically installed and configured. The customer is responsible for ensuring that they terminate their VIRL server instance in order to avoid unexpected charges.
If the customer forgets to terminate their instance, the customer is responsible for the settlement of any and all associated costs with Packet.net.
You are solely responsible for ensuring that you terminate your VIRL server instance in order to avoid unexpected charges. If you forget to or otherwise do not terminate your VIRL instance for whatever reason, then you are solely responsible for the settlement of any and all associated costs and charges incurred with Packet.net. Neither Cisco nor Packet will be responsible or liable for any costs, damages, charges or other amounts incurred by you in connection with your use of the packet service. Please see details on Packet's pricing details.
Users are able to terminate their server instance on Packet by issuing the command “terraform destroy .”. Although the command may report 'success', users are advised to log in to the Packet.net portal and confirm that their server instance has indeed been terminated. If the server instance is still present, the server instance can be terminated via operations on the Packet.net portal.
You are solely responsible for ensuring that you terminate your VIRL server instance in order to avoid unexpected charges. If you forget to or otherwise do not terminate your VIRL instance for whatever reason, then you are solely responsible for the settlement of any and all associated costs and charges incurred with Packet.net. Neither Cisco nor Packet will be responsible or liable for any costs, damages, charges or other amounts incurred by you in connection with your use of the packet service.
When a VIRL server is initialized, a 'dead man's timer' value is set. The purpose of the timer is to avoid a server instance being left running on the platform for an indefinite period.
The timer value is set by default to four (4) hours and can be changed by modifying the 'dead mans timer' value in the settings.tf file before you start your server instance. If your server is running at the point where the timer expires, your server instance will be terminated automatically. If your server is running at the point where the timer expires, your server instance will be terminated automatically. Any information held on the server will be lost.
You are able to see when the timer will expire by logging in (via ssh) to the server instance and issuing the command “sudo atq”. You can remove the timer, leaving the server to run indefinitely, by issuing the command "sudo atrm 1". Cisco cannot be held accountable should the customer forget to adjust the 'dead man's timer', and in so doing, encounter a server termination event.
You are solely responsible for ensuring that you terminate your VIRL server instance in order to avoid unexpected charges. If you forget to or otherwise do not terminate your VIRL instance for whatever reason, then you are solely responsible for the settlement of any and all associated costs and charges incurred with Packet.net. Neither Cisco nor Packet will be responsible or liable for any costs, damages, charges or other amounts incurred by you in connection with your use of the packet service.
Issues relating to the operation of the server itself are to be directed to Packet.net or via their online chat, knowledgebase, or help [at] packet [dot] net. Issues relating to the operation of VIRL on the server should be directed to VIRL's community forum. There is no special support offering in respect to using VIRL on Packet's bare metal platform.
Customers must understand that their VIRL server instance on Packet's bare metal platform is connected directly to the Internet. Therefore the necessary security precautions should be applied.
VIRL provides specific commands to enable default security profiles and to enable a more secure connection method using OpenVPN (https://openvpn.net/). While we have made every effort to secure the VIRL server instance, the customer assumes responsibility for the security of the VIRL server at all times.


Sign up with Packet for free today


Sign up with Packet
FAQ FOLLOW VIRL Privacy Policy
Copyright © 2016 Cisco and/or its affiliates. All Rights Reserved.