VIRL on Packet |
All you need is a valid VIRL license key and Packet.net account. You can purchase a key here.
Already have one? Download your key.
Register with Packet.net and create your account with a method of payment through credit card or PayPal.
When you are ready to deploy, follow the deployment instructions for VIRL PE on Packet.
When using the VIRL on the Packet platform, you will be charged for the server on 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 large topologies or want to experiment with Cisco node images that consume more memory and CPU than your local system has to offer, Packet.net may be the solution. Packet offers a range of bare-metal servers perfectly suited for VIRL PE at a fraction of the cost of a new computer. Deploying VIRL PE to Packet.net also gives you the flexibility of running VIRL from anywhere at any time you have an internet connection.
You don't have to have VIRL installed in order to use VIRL on Packet. Using your active VIRL license key, you can bring up your own VIRL server on Packet whenever you need it. See detailed instructions.
The VIRL servers are exposed on the internet. When deploying VIRL from your Packet portal, all information is encrypted using SSL. Once your VIRL server is ready for use, you can enable OpenVPN to secure your connection. OpenVPN is not enabled by default, so you are responsible to maintain the security of your system.
Yes! All of the features that you can use on your local VIRL instance, you can also use remotely.
Yes, but it comes at a cost! As long as you have a Packet server “checked out" (listed in your Packet portal), whether it is running, shutdown, or rebooting, you will accrue charges. Only when your server is DELETED will Packet’s rental fee stop.
Yes, it is possible to connect VMs running on a local VIRL server to VMs running on Packet's platform. In order to make this possible, you may need to configure OpenVPN.
Ultimately, the user is responsible for ensuring termination of the server when work is done. Please see the Running Cost section 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.
Important Note: the current Packet.net deployment process no longer installs a “Dead Man’s Timer.” Your VIRL server on Packet.net will not shut down automatically. You must log in to the Packet.net portal to terminate your server instance.
Yes. For 3rd party VMs images, please remember that the VM images are not retained. When you DELETE your VIRL PE server, all information stored on its disk, like VM images, will be deleted permanently.
Packet has data-centers in the US, EU, Japan, and is continually expanding. VIRL server deployments are only available in the following datacenters:
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 must log in to the Packet.net portal to terminate their server instance.
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.
Important Note: the current Packet.net deployment process no longer installs a “Dead Man’s Timer.” Your VIRL server on Packet.net will not shut down automatically. You must log in to the Packet.net portal to terminate your server instance.
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 server provisioning, availability, direct access to a system console or Packet's user portal should be directed to Packet.net. Issues relating to the operation of VIRL PE on a provisioned 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 from Cisco or Packet.net.
As a VIRL PE on Packet user, you understand that your VIRL server instance on Packet's bare metal platform is directly connected to the Internet. It is highly recommended that all necessary security precautions be applied. VIRL provides specific commands to enable default security profiles and the ability to enable a more secure connection method using OpenVPN. While we have made every effort to secure the VIRL PE, the user assumes responsibility for the security of their VIRL PE server at all times.