FAQ（ECL2.0）

Virtual Server - FAQ

• All(116)
• Operation(37)
• Specification(70)
• Billing(2)
• Construction(21)

• How to assign a static IP address?ECL2.0, Virtual Server

  There are two ways to assign static IP addresses.
  1. Set the DHCP of the logical network to enable (default) and enter the static IP address on the attached screen of the logical network when creating the virtual server. In this case, as seen from the OS layer, the corresponding vNIC is addressed by DHCP, but in effect, the IP address entered above is allocated, thereafter basically no need to modify.

  2. Set DHCP of the logical network to disable and enter a static IP address on the attached screen of the logical network when creating the virtual server. In this case, since the IP address is not set from the OS layer at the time of server creation, log in at the console and set the IP address you entered earlier in the OS layer.

  In either method, there is no way that the instance can not be controlled from the GUI (for example, PowerOn / OFF can not be done, etc). However, the IP address seen from the cloud computing control panel and the IP address seen from the OS layer must be matched. Please be careful.

  We recommend 1. In case of selected 2, please refer notes.

  Is this page helpful?

  Yes No

  Open in a new window
• When is the billing for the volume of the virtual server started?ECL2.0, Virtual Server

  Billing starts from when the volume is created.
  Regardless of the start/stop of the instance, or the state of attaching/detaching to the instance, a monthly upper limit of usage fee (minutes) will occur from when the volume is created.

  Regarding the capacity, volume is charged by the capacity of the volume regardless of the actual usage.
  This is also true when adding a new volume or expanding the existing volume.

  In addition, when the volume is expanded, the price after a change will be applied when changing the size by expanding the volume.

  Reference: Service Descriptions - Virtual Server - Pricing

  Is this page helpful?

  Yes No

  Open in a new window
• Please tell me about the iSCSI configuration of virtual server.Block storage (IO performance ensure), ECL2.0, Virtual Server

  Approximate one minute downtime is expected in case of logical network failure which provides the network to virtual server. (See [Service Descriptions - Support] for detail.)
  If you set up storage connection by using iSCSI from virtual server, please take account into the downtime.
  If you connect to our block storage service, please refer [Tutorials - Attaching resources to a Block Storage Volume].
  If you connect to the storage that we don't provide, please contact your storage provider.

  The following shows some examples of configuration to hold I/O during the downtime.
  The impact on your application has to be tested and evaluated additionally for your system.

  The multipath devices can be used to make I/O queued at multipath layer in case of disconnection to iSCSI target.
  For RHEL guest, the option of 'features "1 queue_if_no_path"' makes I/Os held at multi-path layer when all paths are down.

  If the multipath devices are not used, the timeout of iSCSI layer needs to be set long enough.
  For RHEL guest, we set iSCSI initiator timeout to 120 seconds.

  Configuration file name: /etc/iscsi/iscsid.conf
  Parameter: node.session.timeo.replacement_timeout
  Value: 120 (Default value: 120)

  For Windows guest, we set both disks I/O timeout and iSCSI initiator request timeout to 120 seconds.

  Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\disk
  Name: TimeoutValue
  Value: 120 (Default value: 60)

  Key: HKLM\SYSTEM\CurrentControlSet\Control\Class{4D36E97B-E325-11CE-BFC1-08002BE10318}\0000\Parameters (*1)
  Name: MaxRequestHoldTime
  Value: 120 (Default value: 60)
  (*1) The part of "0000" may vary. Please choose the instance number of Microsoft iSCSI Initiator.

  Is this page helpful?

  Yes No

  Open in a new window
• The instance which installed VM-Series provided by Palo Alto Networks is suddenly fail to connection.ECL2.0, Virtual Server

  Although the Instance created by own brought image is not supported, it is reported that the Instance which installed VM-Series provided by Palo Alto Networks suddenly fails to connect when DPDK(Data Plane Development Kit) on driver configuration sets "ON".
  Furthermore, DPDK is not supported in the instance of Virtual Server as below;
  FAQ - Is DPDK supported in Virtual Server?

  Just for your information, it's out of support but here is the procedure change DPDK setting to "OFF".

  1. Checking DPDK setting in the instance

  Executing the following command, and check DPDK setting whether ON or OFF

  show system setting dpdk-pkt-io

  - If DPDK is "ON", the following message is appeared

  Device current Packet IO mode: DPDK

  - If DPDK is "OFF", the following message is appeared

  Device current Packet IO mode: Packet MMAP

  2. Change DPDK to "OFF"

  Change DPDK to "OFF" by executing the following command

  set system setting dpdk-pkt-io off

  After changing, reboot device and/or system as necessary, and please check DPDK setting by the procedure 1.

   

  *)The Instance created by own brought image is not supported.
  Please note the information on this page is just for your information as our knowledge base.
  The above setting how to change DPDK may change without prior notice by any reason such as Palo Alto Networks policy.
  Also, please confirm and test for checking any impacts by customer self because it is not supported.

  Is this page helpful?

  Yes No

  Open in a new window
• Is DPDK supported in Virtual Server?ECL2.0, Virtual Server

  DPDK(Data Plane Development Kit) is not supported in the instance of Virtual Server(it's out of guarantee).

  Is this page helpful?

  Yes No

  Open in a new window
• On Monitoring Control Panel, CPU utilization of Virtual Server Instance sometimes exceed 100%. Is this normal?ECL2.0, Monitoring, Virtual Server

  Yes. The maximum value is “100 percent x number of CPU cores”. (Example: If the virtual server instance is 16 CPUs, the value ranges from 0 to 1600 percent.)
  So CPU Utilization may exceed 100%, depending on the flavor of the virtual server.

  Reference:
  Service Description - Monitoring - Data Collection/Accumulation - Virtual Server Instance

  Service Description - Virtual Server - Plan List

  Is this page helpful?

  Yes No

  Open in a new window
• Is it possible to move an instance to another Tenant?ECL2.0, Image Storage, Virtual Server

  It is not possible to move an instance directly to another tenant, but by using the "Image share" function or "copy of the image" function of the "Image Storage" menu, you can create a copy of the instance in another tenant.
  # Please refer to below for the details of "Image share" or "copy of the image".
  Service Description - Image Storage - Operable Items in Private Template

  Create a copy of the instance by using "Image share"
  (Create a copy in another tenant in the same region)

  Instance created from image

  1. In the source tenant, create a snapshot of the instance.
  Tutorials - Virtual Server - Create a Snapshot of the Instance

  2. (In case of data volumes attached to the instance) In the source tenant, detach volumes from the instance and upload them to an image.
  Tutorials - Virtual Server - Upload a Volume to an Image

  3. In the source tenant, add the destination tenant on "Edit Image Share Member".
  Tutorials - Image Storage - Edit Image Share Member ( Operate in an Image-sending Tenant)

  4. In the destination tenant, accept an Additional Share Member Request.
  Tutorials - Image Storage - Accept an Additional Share Member Request (Operation at an Image-received/Image-shard Tenant)

  5. In the destination tenant, create an instance from snapshot (when you shared images of data volumes, create data volumes from image and attach them to the instance).
  Tutorials - Virtual Server - Adding a Data Volume to an Instance

  6. (When the instance in the source tenant is unnecessary) In the source tenant, terminate the instance.
  Tutorials - Virtual Server - Terminate an Instance

  Instance created from volume

  1. In the source tenant, delete the instance.
  Tutorials - Virtual Server - Terminate an Instance

  2. In the source tenant, upload the root volume to an image (In case of data volumes attached to the instance, upload them to an image too).
  Tutorials - Virtual Server - Upload a Volume to an Image

  3. In the source tenant, add the destination tenant on "Edit Image Share Member".
  Tutorials - Image Storage - Edit Image Share Member ( Operate in an Image-sending Tenant)

  4. In the destination tenant, accept an Additional Share Member Request.
  Tutorials - Image Storage - Accept an Additional Share Member Request (Operation at an Image-received/Image-shard Tenant)

  5. In the destination tenant, create a volume from image and create an instance from volume (when you shared images of data volumes, create data volumes from image and attach them to the instance).
  Tutorials - Virtual Server - Adding a Data Volume to an Instance

  6. (When the instance in the source tenant is unnecessary) In the source tenant, terminate the instance.

  Create a copy of the instance by using "copy of the image"
  (Create a copy in another region in the same contract)

  Instance created from image

  1. In the source tenant, create a snapshot of the instance.
  Tutorials - Virtual Server - Create a Snapshot of the Instance

  2. (In case of data volumes attached to the instance) In the source tenant, detach volumes from the instance and upload them to an image.
  Tutorials - Virtual Server - Upload a Volume to an Image

  3. In the source tenant, copy the images to the destination tenant.
  Tutorials - Image Storage - Copy Images

  4. In the destination tenant, create an instance from snapshot (when you copied images of data volumes, create data volumes from image and attach them to the instance).
  Tutorials - Virtual Server - Adding a Data Volume to an Instance

  5. (When the instance in the source tenant is unnecessary) In the source tenant, terminate the instance.
  Tutorials - Virtual Server - Terminate an Instance

  Instance created from volume

  1. In the source tenant, delete the instance.
  Tutorials - Virtual Server - Terminate an Instance

  2. In the source tenant, upload the root volume to an image (In case of data volumes attached to the instance, upload them to an image too).
  Tutorials - Virtual Server - Upload a Volume to an Image

  3. In the source tenant, copy the images to the destination tenant.
  Tutorials - Image Storage - Copy Images

  4. In the destination tenant, create a volume from image and create an instance from volume (when you copied images of data volumes, create data volumes from image and attach them to the instance).
  Tutorials - Virtual Server - Adding a Data Volume to an Instance

  5. (When the instance in the source tenant is unnecessary) In the source tenant, terminate the instance.

  Is this page helpful?

  Yes No

  Open in a new window
• Is it possible to restore deleted instances?ECL2.0, Virtual Server

  If created from an image, deleting the instance also deletes the root disk and can not be restored.
  If created from a volume, the corresponding root volume will remain as volume even if the instance is deleted. It is possible to restore by creating the instance again from that volume.
  

  Reference:
  Service Descriptions - Virtual Server - Image: Instance: Creation & Deletion
  Service Descriptions - Virtual Server - Operable Attributes of Instance

  Regarding the restoration of data, we have not acquired backup of customer's data saved in this menu, so we ask you to acquire it as necessary.
  Service Descriptions - Virtual Server - Notes

  Is this page helpful?

  Yes No

  Open in a new window
• Is there a charge for the suspended virtual server?ECL2.0, Virtual Server

  Yes. Regarding the virtual server, it will be charged even while it is stopped.
  For details, please refer to the following.

  Enterprise Cloud2.0 Pricing / Pricing Calculator

  Is this page helpful?

  Yes No

  Open in a new window
• There is a user named cloud base-init in the Administrator of the virtual server (Windows). Can I disable it?ECL2.0, Virtual Server

  Cloudbase-init is used to start the cloud base-init process when starting Windows Server.
  When the cloud base-init process starts up, the contents set in the post-install script are reflected, and the instance name is registered in the hostname when the instance is created.

  If you stop cloud base-init, please do it at your own discretion.

  Reference:
  FAQ - Please tell me the service description of cloud-init and cloud base-init which are included official images of Virtual Server.

  FAQ - Cloud Initialization Service is stopped when starting virtual server. Is there any problem with server?

  Is this page helpful?

  Yes No

  Open in a new window