---
title: "Manage virtual machines"
canonical: "https://docs.aryaka.com/space/KNOW/1510425/Manage%20virtual%20machines"
format: markdown
---
Aryaka supports an integration with Palo Alto Networks VM-Series and Check Point virtual machines (VM) to provide a virtual firewall that operates on your Aryaka Network Access Point (ANAP). The following models are supported for each vendor: Palo Alto Networks—VM‑50 and VM‑100 models. Check Point—Does not assign model numbers. Their licensing is based on the number of virtual CPUs (vCPU) the VM uses. VMs with one or two vCPUs are supported. To view virtual machines Log in to MyAryaka. The Home page appears. Click  SD-WAN  >  Settings  in the left navigation pane. The Settings page appears and displays a series of tiles. Click  Virtual Machines  in the VM Configuration tile. The Virtual Machines page appears and displays a table of all VMs. The following details are included for each VM: Name—User-assigned name given to the VM when it was created. If the site has ANAPs with VMs deployed in high availability (HA), an ACTV/SBY (active/standby) indicator appears in the Name column. Status—One of the following configuration states of the VM. If this virtual machine is deployed in HA mode, this column displays the status of the standby device in parenthesis next to the status of the active device, for example, Configured (Configured). Configured—MyAryaka configuration is synchronized with the ANAP.  Provisioning—MyAryaka configuration is being modified. The status is updated when Ayaka Customer Support completes the configuration. Activation Pending—MyAryaka configuration is synchronized with the ANAP, but the VM itself is not updated until it is activated. You can activate the VM as described in the  Operate a virtual machine procedure  later in this topic. Partitioning Pending—MyAryaka configuration has been modified, but the ANAP must be repartitioned to be synchronized. You can partition the VM as described in the  Operate a virtual machine procedure  later in this topic. VM Config Failed—MyAryaka configuration is synchronized, but the VM failed to load the configuration. You can stop and restart the VM as described in the  Operate a virtual machine procedure  later in this topic. Image Being Downloaded—VM Image is being downloaded. You must wait for the download to complete and the status to update. Image Download Failed—VM Image download failed. You can try again or use the method described in the  Upload VM images from a flash drive  procedure in the  Virtual machine images  topic. Image Checksum Failed—VM Image checksum operation failed. Ensure the correct checksum was used for the image file, and that it was entered correctly. Running Status—One of the following operational states of the VM. If this virtual machine is deployed in HA mode, this column displays the status of the standby device in parenthesis next to the status of the active device, for example, Running (Stopped). Running—VM is operating. Stopped—VM has been manually stopped. Unavailable—VM is not running for a reason other than being manually stopped. Datapath—Whether or not the VM is in the datapath (that is, is the VM processing network traffic). It is possible for a VM to have a Running Status of Running, and not be in the datapath processing actual traffic. If this virtual machine is deployed in HA mode, this column displays the status of the standby device in parenthesis next to the status of the active device, for example, In Datapath (Not in Datapath). Site—Location of the ANAP on which the VM is deployed. Vendor—Company that developed the associated virtual machine product.  VM Model—Vendor-assigned model name or number used to identify the virtual machine product.  Profile—Name of the VM profile used by this VM. A profile and the associated VM image are used to create the VM. Configure VMs The following graphic shows the general steps required to deploy, configure, and operate the VM. Each step is explained in detail in the corresponding related topic linked from this page. There are two ways to configure VMs: Upload VM images, create VM profiles, and then create and operate the VM.  This workflow is intended simplify the creation and management of images and profiles in organizations that have large numbers of these components and intend to reuse them at multiple sites. If you chose this method, begin deploying your VM by completing the procedure described in  Virtual machine images . Create a virtual machine.  The Add Virtual Machine page enables you to perform all required steps from one UI location. This includes uploading VM images and creating VM profiles. If you are deploying a small number of VMs, you may prefer performing the multi-step configuration of a VM in one place. If you chose this method, deploy your VM by completing the procedure described in  Create virtual machines . Operate a VM The Virtual Machines page lists all existing VMs you have created in MyAryaka. You can select a VM to view it’s details.  Each virtual machine's details page contains the following four panes on the Active ANAP tab that contain one or two buttons that control the VM and the ANAP where it is deployed: Partition ANAP Activate VM Config Stop/Restart VM or Start/Restart VM Remove VM From Datapath Each pane also displays the current state of the VM. The current state is automatically updated every three minutes, or can be manually updated by clicking the Refresh icon in the banner. To operate a virtual machine Log in to MyAryaka. The Home page appears. Click  SD-WAN  >  Settings  in the left navigation pane. The Settings page appears and displays a series of tiles. Click  Virtual Machines  in the VM Configuration tile. The Virtual Machines page appears and displays a table of all VMs. Locate the VM that you want to operate. It must be in one of the following states: Status column is Configured. Running Status column is either VM Running or VM Stopped. Click the table row of the VM. The  <VM_name>  page for the selected VM appears. The top of the page displays the four operations panes. If the VM is configured in high availability (HA) mode, each of the VMs has its own controls. The controls are located on the Active and Standby tabs. Perform one or more of the following operations on the selected virtual machine (the operations are described in detail in the table that follows): Partition the ANAP Activate the VM configuration Start, stop, or restart the VM Remove the VM from the datapath Operation Current State Description Partition ANAP—Creates disk space on the ANAP for the installation of the current VM. The operation then performs a reboot (stop and restart) of the ANAP.  This icon is disabled after the partition is created. In Sync—VM configuration file matches the partition configuration. Out of Sync—VM is running, but the VM configuration file and the partition configuration  do not  match.  Failed—Error occurred when creating the partition on the ANAP. Activate VM Config—Updates the VM's configuration using the settings currently on this page. This icon is disabled after the configuration is activated. Activation Pending—VM configuration changes have been made in MyAryaka, but have not been sent to the VM. In Sync—VM configuration matches the VM configuration pages in MyAryaka. Stop or Start—If the VM is running, the Stop icon appears, if the VM is stopped, the Start icon appears. Clicking the displayed icon performs the corresponding operation (that is, starts or stops the VM). Running—Virtual machine is started and is operational. Stopped—Virtual machine is stopped. A VM can be running, but until it is inserted into the datapath by clicking the Datapath icon, the VM is  not  processing traffic. Restart—Stops and then automatically restarts the VM. The icon is deactivated during the period when the VM is unavailable. Running—Virtual machine is started and is operational. Stopped—Virtual machine is stopped. A VM can be running, but until it is inserted into the datapath by clicking the Enable VM icon, the VM is  not  processing traffic. Remove VM From Datapath—If the VM is disabled, the label reads  Not in Datapath , if the VM is enabled, the label reads  In Datapath . Clicking the icon enables or disables the VM by inserting or removing it from the datapath. The VM can be fully imaged, installed, configured, and running, but until it is inserted into the datapath, it is  not  processing traffic. In Datapath—VM is inserted in the datapath and is processing traffic using the ANAP's IP address (from step 6 in  Create virtual machines ) and associated configuration settings. Not In Datapath—VM is  not  inserted in the datapath, therefore it is not processing traffic. The ANAP continues to processes traffic using the LAN's IP address and associated configuration. In this topic Related topics Create virtual machines Virtual machine profiles Virtual machine images