Hardware Requirements


Minimum Hardware Requirements
Verify that your machine meets the following minimum hardware requirements:
  • • Host system must be able to access the Internet on a regular basis (TCP ports 4505 & 4506 outbound enabled on any firewall/proxy)
  • • A minimum of 8GB of RAM and four core CPU must be allocated to the VIRL virtual machine for better performance and functionality. *More resources allows for larger simulations; suggest 12GB for 20 nodes. *This is dependent on the nodes launched in the simulation. Cisco IOSXRv requires 3GB of memory to launch.
  • • Intel VT-x / EPT or AMD-V / RVI virtualization extensions present and enabled in the BIOS
  • • 70GB of free disk space for installation
  • • Estimate the hardware resources you would need to spin up a certain simulation using our resource calculator. The resource calculator has its own tab in the VIRL FAQ navigation below this hardware requirements tab.


Hypervisors
You must have installed one of the following supported Hypervisors in order to run Cisco VIRL:
  • • VMware Fusion Pro v5.02 or later (including v6.x or v7.x).
  • • VMware Workstation for Windows or Linux v8.04 or later (including v9 -> v12).
  • • VMware Player v5.02 or later (including v6.x and 7x).
  • • VMware Workstation Player 12 or later - NOTE Virtual Network Editor requires Workstation 12 Pro.
  • • VMware ESXI 5.1/5.5/6.x using vSphere Client: ESXi 5.1U2 (Build 1483097), ESXi 5.5U1 (Build 1623387), ESXi 6.0 (Build 2494585).
**These Hypervisors are not included as part of Cisco VIRL and must be installed separately.


Note on VMware Player and ESXi
** VMware Player – Note:
  • • VIRL provides the capability to link both the management- and data-plane interfaces of nodes within a simulation to external networks and devices on those networks. This connectivity requires that an interface be shared between the host PC and the VIRL virtual machine.
  • • Both VMware Fusion Pro and VMware Workstation Pro provide tools to configure the required virtual networks and interfaces. VMware Player and VMware Workstation Player do not include such tools, so although VIRL will still operate with VMware Player and VMware Workstation Player, the ability to communicate over Ethernet from the PC to nodes within a simulation will be inhibited. If such direct Ethernet connectivity is desired then either VMware Fusion Pro (for Mac), VMware Workstation or Workstation Pro (Windows or Linux) is required. Please refer to the VMware website for product comparison details: https://www.vmware.com/products/.
  • • Users are able to communicate with nodes within a simulation running on VMware Player using the VM Maestro ‘Telnet to console port’ or ‘ssh to Management port’ access mechanisms.
** VMware ESXi – Note: ESXi host MUST have Intel CPU with VT-X / EPT support. AMD processors are NOT supported.


Non-Hypervisor Installations (Bare-metal)
Verify that your machine meets the following minimum hardware requirements:
  • • Host system must be able to access the Internet on a regular basis (TCP ports 4505 & 4506 outbound enabled on any firewall/proxy)
  • • Four CPU cores and 8GB of DRAM – more resources allows for larger simulations
  • • Intel VT-x / EPT or AMD-V / RVI virtualization extensions present and enabled in the BIOS
  • • 70GB of free disk space for installation
  • • Ability to boot the ISO image or attach the ISO via an integrated management interface (such as the Cisco Integrated Management Controller)


VIRL on Packet
Requirements for running VIRL on Packet's bare metal cloud platform
  • • 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.
  • • Alternatively, use the VIRL launcher app with Virtualbox or AppCatalyst to set up your VIRL on Packet server: See detailed instructions.