FAQ（ECL2.0）

Virtual Server - FAQ

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

• How to switch the VM (with HA function) intentionally when hypervisor failure on a trial basis?ECL2.0, Firewall (Brocade 5600 vRouter), Firewall (vSRX), Load Balancer, Virtual Server

  Sorry, it is not able to switch the virtual server, Firewall (Brocade 5600 vRouter)(vSRX) or Load Balancer(NetScaler VPX) intentionally as trial basis(in purpose of HA)

  Is this page helpful?

  Yes No

  Open in a new window
• Please tell me the behavior when pushing the "ctrl+alt+delete" button in console screen of virtual server.ECL2.0, Virtual Server

  The behavior is different depending on the OS.

  【Linux】
  If the guest OS is Linux, when you push the ctrl+alt+delete button, your virtual server will be rebooted.
  With the following command, you can disable the reboot function of the ctrl+alt+delete button.
  ------------------------------------------
  # systemctl mask ctrl-alt-del.target
  ------------------------------------------

  ※Even if you disabled the reboot function following the above methods if you click the ctrl+alt+delete button 7 times in 2 seconds (= sending the SIGNAL 7 times in 2 seconds), your virtual server will be rebooted.
  Please see the SIGNAL entries in the manual page of systemd (the URL shown below) for more information.
  -------
  https://man7.org/linux/man-pages/man1/systemd.1.html#SIGNALS
  -------

  【Windows】
  If the guest OS is Windows OS, if you click the ctrl+alt+delete button, your virtual server will not be rebooted.
  Instead of the OS reboot, the security option screen is displayed like the following image.
  

  Is this page helpful?

  Yes No

  Open in a new window
• I tried to put QCOW2 format private template in the volume but the status became an error and I could not configure it as bootable and couldn't create the root volume.ECL2.0, Virtual Server

  It's considered that the prepared volume size was insufficient in its size against the QCOW2 format private template.
  Regarding how to deal with the error, please create a bigger volume than the prepared volume size and put the QCOW2 format image template in the newly created bigger volume again.
  After that, please confirm whether the status should become an error again.

  Example)
  [issue] I tried to put QCOW2 format "Windows Server 2012 R2 Standard Edition" private template(13.6GB) into the 15GB volume and the status became an error.
  [cause] It's considered that the volume size was insufficient against the private template image created with "Windows Server 2012 R2 Standard Edition". When you create the volume with "Windows Server 2012 R2 Standard Edition", the volume size must be over 80GB. (see below document)
  [workaround] I created the volume over 80GB and put the image template in it again and I was able to create the root volume without problems.

  If you changed the volume size (= created the bigger volume) but the status should become an error repeatedly, we are sorry to bother you but we would like you to create a ticket to bring the issue to our attention.

  ** Reference URL **
  [Service Descriptions: Restrictions on the official image]　Each OS has the minimum necessary volume size.
  Service Descriptions - Virtual server - Restrictions on the official image

  ※Excerpt from the above Restrictions
  When you create a volume with the official image template, you are unable to create the volume if the size is less than the official image template size.
  (example: If you need to use Windows OS, you will need to prepare 80GB volume or bigger volume.)

  [FAQ: Difference between RAW format and QCOW2 format] ※If QCOW2 format, the data is compressed and uploaded to Image Storage.
  FAQ - If I upload my private template image to "Image Storage", which format should I select, RAW or QCOW2?Please tell me the difference between the two formats as well.

  Is this page helpful?

  Yes No

  Open in a new window
• I can't move the mouse pointer (mouse cursor) on the console screen accessed via the Cloud Computing Control Panel. (Mouse cursor is stuck on screen, and won't move.)ECL2.0, Virtual Server

  If you can't move the mouse pointer on the console screen, please try the following countermeasures.

  (1) "Changing the browser" or "Changing the client PC"
  You may be able to move the mouse pointer (mouse cursor).

  (2) Restart the virtual server.
  If there is no change after trying (1), please restart the virtual server via the Cloud Computing Control Panel at your discretion.

  Enterprise Cloud 2.0 has adopted Openstack as the cloud platform and the mechanism of the console connection to the virtual server also follows the mechanism of Openstack.
  Compared to the physical serial console connection, the console connection of the Openstack is less stable.

  Therefore, we strongly recommend the customer to enable the remote connection such as SSH or RDP connection as an alternative of the console connection to access to the virtual server resources.

  Is this page helpful?

  Yes No

  Open in a new window
• How to collect data, generate graphs and report for virtual server memory usage by using Monitoring menu?ECL2.0, Monitoring, Virtual Server

  For virtual server memory usage (and others that are not included in the meters provided as standard in Monitoring menu), you can use Monitoring function (graph display, alert setting, etc.) by using Custom Meter.

  There are two methods to use Custom Meter. You can choose either or both of them according to your environment.

  1. Use a custom meter agent
  (Note: Windows OS is not included in the target operating system)

  2. Create and use a script (for collecting data and sending it to the monitoring server)
  (Note: The script needs to be prepared by customers)

  Please refer to the tutorial below for detailed procedure on each method.
  Service Descriptions - Monitoring - Custom Meter
  Tutorials - Monitoring - Use Custom Meter

  Is this page helpful?

  Yes No

  Open in a new window
• License activation fails on the virtual server created from Windows Server Official Image Template.ECL2.0, OS, Virtual Server

  There is a possibility that connectivity to the license server provided by NTT Com may not be established.
  Follow the steps below to ensure connectivity to the license server.

  Tutorial - Activate your OS License

  Reference：Service Descriptions - Windows Server - Conditions for Usage with Other Services

  In order to implement OS license authentication, a common function gateway is required. When using Windows Server, please make sure to apply common function gateway.
  Also, if the common function gateway is removed, OS license authentication will be lost. Therefore, please be careful not to remove the common function gateway from the Windows Server that you are using.

  Is this page helpful?

  Yes No

  Open in a new window
• It is not possible to detach root volume from instance.ECL2.0, Virtual Server

  Root volume is not able to detach unlike data volume. Root volume continue to be root volume for appropriate instance unless deleting instance.
  Reference：Service Descriptions - Glossaries of Volume

  Is this page helpful?

  Yes No

  Open in a new window
• The IP address of the NIC has been changed on the virtual server, but the IP address displayed in the instance summary is not updated.ECL2.0, Virtual Server

  When changing the IP address of the virtual server, it is necessary not only to change the IP on the guest OS (Windows or Linux) but also to operate on the Enterprise Cloud 2.0 portal.

  Specifically, it is necessary to newly connect the interface and delete the unnecessary interface for the IP address for replacement.

  Please refer to the following for working method.

  Tutorial - Virtual Server - Add a Network Interface to the Instance

  Please refer to below FAQ.
  When restarting right after configuring the interface or volume, encounter that the volume goes offline or the device name of the interface has been changed

  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