Virtual Server - Documents

• Service introduction
• Support information

Known Issues

• About the issue when upload large size image to Image Storage
• VRRP configuration settings between the virtual servers

FAQ

• There is no alert on the resource status display function, why did the alert mail notification came?Common, ECL2.0, Virtual Server / Specification

  The customer virtual server instance is not detected and an abnormal state is not detected in the monitoring virtual server instance, the status indicating the abnormality is not displayed in the resource status display function.

  Is this page helpful?

  Yes No

  Open in a new window
• Error in resource status display function.Is there a problem?Common, ECL2.0, Virtual Server / Specification

  An alert was detected in the monitoring virtual server instance installed on the same physical server that houses the customer virtual server instance.

  Therefore, if there is a possibility that the entire virtual server instance on the same physical server may be affected, the operation status of the monitoring virtual server instance is displayed on the resource status screen.

  However, due to the failure of the monitoring virtual server instance alone, if the customer virtual server instance is operating normally, there will be no separate notification via e-mail.

  When a failure of the monitoring virtual server instance is recovered, the status indicating abnormality will not be displayed.

  Is this page helpful?

  Yes No

  Open in a new window
• Error in resource status display function. There is no error indication now, but I want to know if there is any influence.Common, ECL2.0, Virtual Server / Specification

  An alert was detected in the monitoring virtual server instance installed on the same physical server that houses the customer virtual server instance.

  Therefore, if there is a possibility that the entire virtual server instance on the same physical server may be affected, the operation status of the monitoring virtual server instance is displayed on the resource status screen.

  However, if there is a failure of the monitoring virtual server instance alone and the customer virtual server instance is operating normally, there will be no separate notification via e-mail.

  When a failure of the monitoring virtual server instance is recovered, the status indicating abnormality will not be displayed.

  Is this page helpful?

  Yes No

  Open in a new window
• How do I specify the order of NICs when creating virtual server instances?ECL2.0, Virtual Server / Construction, Specification

  At the time of instance creation, when there are multiple logical networks connected and configured, NICs will be randomly recognized from multiple logical networks when the instance starts up.

  If you want to specify the order of NICs arbitrarily, please try the following procedure.
  ===============================
  1. When creating a virtual server, create it by connecting only one logical network
  2. Stop virtual server
  3. Connect another logical network to the virtual server
  4. Activate the virtual server and check whether the order of NICs is in the intended state
  5. Repeat the above 2,3,4 as many times as the number of logical networks you want to connect
  ===============================

  Is this page helpful?

  Yes No

  Open in a new window
• I can not create a virtual server using a specific IP address in the IP address band of the logical network. There is a response of ping even though I am not using the corresponding IP address.ECL2.0, Virtual Server / Construction, Specification

  When creating a subnet for a logical network, if you check [Enable DHCP], it will use one IP address for the DHCP server (the lowest number of unused addresses in the IP address assignment pool will be automatically assigned). Also, this DHCP server returns a ping response.
  Please use other than the IP address assigned for the DHCP server.

  * (Supplement) What is DHCP (server address setting function) of the logical network?

  Is this page helpful?

  Yes No

  Open in a new window
• How to assign a static IP address?ECL2.0, Virtual Server / Construction, Specification

  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, Specification

  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 change will be applied from 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 / Operation

  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 to 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 a 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 of disk 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 / Operation, Specification

  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 is suddenly fail to connection 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 / Operation, Specification

  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