Enterprise Cloud 2.0 Support

Enterprise Cloud 2.0 is working properly.

Keyword Search

Search by Service

Popular FAQs

  • Is it possible to use asymmetric communication (communication in which traffic go and return are separate routes)?ECL2.0, Logical Network / Construction, Specification

    In Enterprise Cloud 2.0, asymmetric communication may not be able to communicate.

    Please design so that traffic going and returning are symmetric communication with the same route.

    Target menu

    · Virtual server

    · Firewall

    · Load balancer

    · Network type security  

     

    Asymmetric communication example 1

    When multiple interfaces are used, partial communication may be asymmetric communication.

    Please add individual static routes and design to be symmetric communication.

     

    Asymmetric communication example 2

    When VRRP redundancy is performed with multiple interfaces, if the VRRP state (Master / Backup) is different Transit communication is asymmetric communication.

    Make VRRP statuses consistent and design to be symmetric.

    Please refer to the tutorial for detailed configuration example of firewall / load balancer.

     

    Asymmetric communication example 3

    If you use the DSR (Direct Server Return) function on the load balancer, the return communication will cause the load balancer Since it does not pass through, it becomes asymmetric communication.

    Please do not use the DSR function and design it as target communication.

    Is this page helpful?

    Yes No
  • Please tell me the service description of cloud-init and cloudbase-init which are included official images of Virtal Server.ECL2.0, Virtual Server / Construction, Specification

    The service descripton about cloud-init(for Linux series) and cloudbase-init(for Windows series) in official images of Virtual Server are as below;

    ■cloud-init(for Linux series)

    1.Timing of execution

    Launch Instance(including reboot by HA function)
    *) It’s required that the instance can access to the mata data service. If not, the cloud-init can’t be executed.
    For details, please refer to the service descripton of Virtual Server.

    2.Extent of influence

    ・Install keypair settitng to the instance when the instance is launched at first time only(i.e. create instance).
    ・Install Post-install script to the instance when the instance is launched at first time only(i.e. create instance).
    ・The following 5 files are changed by executing cloud-init;

    - /etc/hostname: hostname is changed when the instance is launched.
    - /etc/hosts: If instance name is changed, the new instance name is added on hosts when the instance is launched.
    - /etc/locale.conf: Initialized to en_US.UTF-8(default value of cloud-init) when the instance is launched at first time only(i.e. create instance).
    - /etc/ssh/sshd_config: Initialized to PasswordAuthentication no(default value of cloud-init) when the instance is launched at first time only(i.e. create instance).
    - /etc/ssh/ssh_host_*: Recreated sh_host_* when the instance is launched at first time only(i.e. create instance).
    (/etc/ssh/ssh_host_dsa_key.pub, /etc/ssh/ssh_host_ecdsa_key, /etc/ssh/ssh_host_rsa_key.pub, /etc/ssh/ssh_host_ed25519_key.pub,
     /etc/ssh/ssh_host_ecdsa_key.pub, /etc/ssh/ssh_host_dsa_key, /etc/ssh/ssh_host_ed25519_key, /etc/ssh/ssh_host_rsa_key)

    3.Reference: Workaround for updating automatically by cloud-init

    ・Customer can invalidate auto updates about executing cloud-init by the following setting;

    - /etc/hostname: Setting to "preserve_hostname:True" on "/etc/cloud/cloud.cfg"
    - /etc/hosts: Setting to "manage_etc_hosts: False" on "/etc/cloud/cloud.cfg"
    - /etc/locale.conf: Setting to "your setting value(ex.locale: ja_JP.Shift_JIS)" on " /etc/cloud/cloud.cfg"
    - /etc/ssh/sshd_config: Setting to "ssh_pwauth:True" on "/etc/cloud/cloud.cfg"
    - /etc/ssh/ssh_host_*: Setting to "ssh_deletekeys:False" on "/etc/cloud/cloud.cfg"

    ■cloudbase-init(for Windows series)

    1.Timing of execution

    Launch at first time only(i.e. create instance).
    *) It’s required that the instance can access to the mata data service. If not, the cloud-init can’t be executed.
    For details, please refer to the service descripton of Virtual Server.

    2.Extent of influence

    ・Install Post-install script to the instance when the instance is launched at first time only(i.e. create instance).
    ・Specified instance name when create instancce is registered to hostname.

    3.Reference: Workaround for updating automatically by cloudbase-init when create instance

    ・Customer can invalidate auto updates about executing cloudbase-init by the following setting;
    Remove “cloudbaseinit.plugins.common.sethostname.SetHostNamePlugin” from “plugins=”
    on cloudbase-init.conf which is stored on “C:\Program Files (x86)\Cloudbase Solutions\Cloudbase-Init\conf”
    in the windows instance.

    Is this page helpful?

    Yes No
  • When restarting right after configuring the interface or volume, encounter that the volume goes offline or the device name of the interface has been changedECL2.0, Virtual Server / Operation

    There is a possibility that the following event will occur if you perform specific target operation.
    We will inform you what to do when each event occurs.

    Target operation

    · Add / delete interfaces or attach / detach volumes while the instance is stopped, then start the instance.
    · Performing off / on (* 1) (including rebooting with HA) after adding / deleting interfaces and attaching / detaching the volume while the instance is running.

    * We recommend adding / deleting interfaces, attaching / detaching volumes with the instance “stopped”, and confirming after startup.
    * 1 Performing shut down on the OS, confirm that the status of the instance has stopped, and then start the instance with the portal or API. (Please note that “reboot” on OS is not effective as this action.)

    Event and Workaround

    Windows Series

    1. If the DHCP function of the connected logical network is disabled and a fixed IP address is set, the correspondence between the device name of the interface and the IP address may be replaced with another logical network connected .
    The correspondence between the device name of the interface and the IP address can be confirmed by the following procedure.
    · Check the fixed IP address assigned to each logical network on the portal “cloud computing” -> “server” -> “virtual server”> – “instance” screen
    · Click the name of the logical network on the “Network” -> “Logical Network” screen of the portal and check the MAC address of the logical network to be connected in “Port” field
    · Access instances to the console and check the fixed IP address set for each MAC address on the “Network and Sharing Center” screen of the control panel to see if it is consistent with the display on the portal.

    * Workaround
    Please reset the correct static IP address from the “Network and Sharing Center” screen of the control panel.
    * We recommend that DHCP of logical network be enabled unless there is a special reason to use your own DHCP server.

    2. The state of the connected volume may be offline.
    The status of the volume can be confirmed from “File service and storage service” -> “volume” -> “disk” of the server manager.

    * Workaround
    In the Server Manager’s “File Service and Storage Service” -> “Volume” -> “Disk” screen, right click on the volume and select “Bring Online” to bring it online. (See the figure below)

    Linux Series

    1. If the DHCP function of the connected logical network is disabled and a fixed IP address is set, the correspondence between the device name of the interface and the IP address may be changed.
    The correspondence between the device name of the interface and the IP address can be confirmed by the following procedure.
    · Check the fixed IP address assigned to each logical network on the portal “cloud computing” -> “server” -> “virtual server”> – “instance” screen
    · Click the name of the logical network on the “Network” -> “Logical Network” screen of the portal and check the MAC address of the logical network to be connected in “Port” field
    · Access the instance on the console, check the fixed IP address set for each MAC address by ifconfig, and check whether it is consistent with the display on the portal

    * Workaround
    Please reset the correct static IP address.
    <Ubuntu Series>
    Edit `/etc/network/interfaces`, set the correct static IP address, and execute `service networking restart`.
    <CentOS Series>
    Edit `/etc/sysconfig/network-scripts/ifcfg-ethx`, set the correct static IP address, then execute `service network restart`. (※ ethx depends on the interface name for setting fixed IP address)

    * We recommend that DHCP of logical network be enabled unless there is a special reason to use your own DHCP server.

    2. If you do not add the reboot mount setting in / etc / fstab, the mounted volume will be unmounted.
    A list of mounted devices can be checked with the `df` command or the `mount` command.

    * Workaround
    Please mount the volume again with the `mount` command.
    In terms of Linux specifications, volumes will be unmounted each time it is restarted unless you add mount settings to `/etc/fstab` so please be sure to add mount settings in advance.

     

    Please note that once these instances are started up or turned off / on (* 2), they will not occur again unless you newly add / delete interfaces or newly attach / detach volumes.

    Is this page helpful?

    Yes No
  • Windows instance faced bluescreen or freeze. What should I do?ECL2.0, Virtual Server / Operation
     Note
    The following procedures are for instances which are created from Windows 2012 R2 Official Image before 
    “WindowsServer-2012R2_Standard_64_include-license_virtual-server_42” (Released on July 19 2018).
    Cusotmer does not need to do the procedure to the instances which are created from Windows 2012 R2 Official image 
    since “WindowsServer-2012R2_Standard_64_include-license_virtual-server_42”.

    Windows instance which was created from official image may face bluescreen or freeze suddenly.
    This event can be avoided by updating VirtIO/viostor/memory balloon driver if customer wants to keep existing instance.
    There are 2 workarounds about VirtIO update. One is to required internet connectivity, and the other is not to require internet connectivity. Procedures are as below;

    Workaround 1: VirtIO update to Instance which has internet connectivity

    *) CAUTION: This workaround requires target instance has internet connection.

     

    1. Download virtio-win-0.1.141 image to target instance

    Download virtio-win-0.1.141 image to target instance from here.

     

    2. Mount ISO file

    Mount downloaded ISO file on DVD Drive

    iso-file-mount-to-dvddrive

     

     

    3. Update virtio driver

    3-1. Click “Tool” on Server Manager, and click “Computer Management”

    computer-management2

     

     

    3-2. Click “Device Manager “on the left side of Computer Management

    devicemanager

     

     

    3-3. Expand “Network adapters” on the center of Computer Management. Confirm Red Hat VirtIO Ethernet Adapter is displayed. (it is displayed accordance with the number of logical network)

    virtupdate-test

     

     

    3-4. Right-click displayed Red Hat VirtIO Ethernet Adapter (first adapter if more than one), and click “Properties”.

    red-hat-virtio-ethernet-adapter2

     

     

    3-5. Click Driver tab on Properties

    driver-tab

     

     

    3-6. Confirm Driver version is not “63.74.104.14100”, and click “Update Driver…”

    update-driver

     

     

    3-7. Click “Browse my computer for driver software “

    windows-update-wizard

     

     

    3-8. Click “Browse…”, select DVD drive which ISO file mounts on, click “OK” and click “Next”

    browserforfolder

     

     

    3-9. Pop up “Would you like to install this device software?”, and click “Install”.

    would-you-like-to-install-this-device-software

     

     

    3-10. Close window after “Windows has successfully updated your device software” was displayed, confirm virtio version is updated to 63.73.104.14100 and close window.

     

    If driver version is not updated, please reboot instance and try updating again after update all Network Adapter and conduct [4. Eject mounted ISO(DVD drive)].

     

    3-11. Update other un-updated Red Hat VirtIO Ethernet Adapter to “63.73.104.14100” version as well when a number of logical network are connected.

     

    4.Update viostor driver
    4-1.Click “Tool” on Server Manager, and click “Computer Management”.
    virtioドライバのアップデート

     

    4-2.Click “Device Manager “on the left side of Computer Management.

    device-manager2

     

    4-3.Expand “Storage controllers” on the center of Computer Management. Confirm Red Hat VirtIO SCSI Controller is displayed. (it is displayed accordance with the number of mounted disk).

     

     

    4-4.Right-click displayed Red Hat VirtIO SCSI Controller (first adapter if more than one), and click “Properties”.

     

     

    4-5.Update Red Hat VirtIO SCSI Controller to “62.74.104.14100” by repeating the workaround 3-5~3-10 for Red Hat VirtIO SCSI Contoller.

     

     

    4-6.Update other un-updated Red Hat VirtIO SCSI Controller to “62.74.104.14100” version as well when a number of disks are connected.

     

     

    5.Update memory balloon driver

    ※Please inform us when you are using the official image “WindowsServer-2012R2_Standard_64_include-license_virtual-server_20”.

    5-1.Click “Tool” on Server Manager, and click “Computer Management”.
    virtioドライバのアップデート

     

    5-2.Click “Device Manager “on the left side of Computer Management.

    device-manager2

     

    5-3.Expand “System devices” on the center of Computer Management. Confirm VirtIO Balloon Driver is displayed.

     

     

    5-4.Right-click displayed VirtIO Balloon Driver, and click “Properties”.

     

    5-5.Update VirtIO Balloon Driver to “62.74.104.14100” by repeating the workaround 3-5~3-10 for VirtIO Balloon Driver.

     

    6. Eject mounted ISO(DVD drive)

    Eject mounted ISO(DVD drive).

    eject-mounted-iso

     

     

    7. Reboot instance

    Reboot target WindowsServer instance.

     

     

    Workaround 2 : VirtIO update to Instance which doesn’t have internet connectivity

    *) CAUTION: This workaround doesn’t need target instance has internet connection, however, charge of  Image Storage and Volume are occurred in accordance with these usage because the workaround requires to use Image Storage and Volume.

     

    1. Download virtio-win-0.1.141 image to target instance

    Download virtio-win-0.1.141 image to any computer which has internet connectivity from here

    *) Customer should use the above linked image in Workaround 2 because the image is customized for using as Workaround 2 by referring the following virtio-win-0.1.141 image.

    Reference: virtio-win-0.1.141 image

    https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.141-1/virtio-win-0.1.141.iso

     

    2. Upload virtio-win-0.1.141 image to Image Storage

    Upload virtio-win-0.1.141 image to Image Storage in customer’s tenant from the computer which has internet connectivity.

     

    3.Create volume from virtio-win-0.1.141 image
    Select “Create Volume“ on Actions list of virtio-win-0.1.141 image, and create volume from virtio-win-0.1.141 image.

     

    Name:Anything

    Description:Anything(Option)

    Use image as a source:virtio-win-0.1.141 (352MB) is selected automatically

    Size(GB):15

    Zone/Group:Same Zone/Group as target insntace which need to be updated virtio driver.

     

    4. Attach the volume to target instance
    Open Portal>Virtual Server>Volume, and select “Manage Attachments“ on Actions list.

    “Attach to Instance“ is poped up, selecet target instance which need to be updated virtio driver and click “Attach Volume“.

     

    5. Log in to target instance
    Launch target Windows instance, and log in to the instance via VNC console etc.

     

    6. Make the attached volume online

    Make the volume attached on the instance available on Windows by configuring on OS.

    Open Server Manager>Dashboard, click “Tool“ on upper right and click “ Computer Management“. Click “Disk Management“ on the left side of Computer Management.

    Confrim 15GB disk with Offline is displayed on disk list on the lower center of Computer Management, right click around “ Disk X (X is number such as 1 and 2) Basic Offline“ and click “Online“.

    Confrim disk named as “ virtio-0.1.141“ is displayed on disk list on the upper center of Computer Management.

    computer-management_wo2

     

     

    7. Update virtio driver

    7-1. Click “Tool” on Server Manager, and click “Computer Management”

    computer-management2

     

     

    7-2. Click “Device Manager “on the left side of Computer Management

    devicemanager

     

     

    7-3. Expand “Network adapters” on the center of Computer Management. Confirm Red Hat VirtIO Ethernet Adapter is displayed. (it is displayed accordance with the number of logical network)

    virtupdate-test

     

     

    7-4. Right-click displayed Red Hat VirtIO Ethernet Adapter(first adapter if more than one), and click “Properties”.

    red-hat-virtio-ethernet-adapter2

     

     

    7-5. Click Driver tab on Properties

    driver-tab

     

     

    7-6.Confirm Driver version is not “63.74.104.14100”, and click “Update Driver…”

    update-driver

     

     

    7-7. Click “Browse my computer for driver software “

    windows-update-wizard

     

     

    7-8. Click “Browse…”, select mounted virtio-0.1.141 disk, click “OK” and click “Next”
    7-9.  Pop up “Would you like to install this device software?”, and click “Install”.

    would-you-like-to-install-this-device-software

     

     

    7-10.  Close window after “Windows has successfully updated your device software” was displayed, confirm virtio version is updated to 63.73.104.14100 and close window.

     

    If driver version is not updated, please reboot instance and try updating again after update all Network Adapter.

     

    7-11. Update other un-updated Red Hat VirtIO Ethernet Adapter to “63.73.104.14100” version as well when a number of logical network are connected.

     

    8.Update viostor driver
    8-1.Click “Tool” on Server Manager, and click “Computer Management”.
    virtioドライバのアップデート

     

    8-2.Click “Device Manager “on the left side of Computer Management.

    device-manager2

     

    8-3.Expand “Storage controllers” on the center of Computer Management. Confirm Red Hat VirtIO SCSI Controller is displayed. (it is displayed accordance with the number of mounted disk).

     

     

    8-4.Right-click displayed Red Hat VirtIO SCSI Controller (first adapter if more than one), and click “Properties”.

     

     

    8-5.Update Red Hat VirtIO SCSI Controller to “62.74.104.14100” by repeating the workaround 3-5~3-10 for Red Hat VirtIO SCSI Contoller.

     

     

    8-6.Update other un-updated Red Hat VirtIO SCSI Controller to “62.74.104.14100” version as well when a number of disks are connected.

     

     

    9.update memory balloon driver

    ※Please inform us when you are using the official image “WindowsServer-2012R2_Standard_64_include-license_virtual-server_20”.

    9-1.Click “Tool” on Server Manager, and click “Computer Management”.
    virtioドライバのアップデート

     

    9-2.Click “Device Manager “on the left side of Computer Management.

    device-manager2

     

    9-3.Expand “System devices” on the center of Computer Management. Confirm VirtIO Balloon Driver is displayed.

     

     

    9-4.Right-click displayed VirtIO Balloon Driver, and click “Properties”.

     

    9-5.Update VirtIO Balloon Driver to “62.74.104.14100” by repeating the workaround 7-5~7-10 for VirtIO Balloon Driver.

     

    10. Shut off Instance and detach Volume
    Offline virtio-0.1.141 disk on Computer Management>Disk Management of display which was used in “6. Make the attached volume online”, and shut off Windows Server instance.

    Select “Manage Attachments” on Actions list of virtio-win-0.1.141 volume.

    “Manage Atttachments“ is poped up, and click “Detach volume“.

     

    11. Reboot instance

    Reboot target Windows Server instance.

     

     

    Is this page helpful?

    Yes No
  • When connecting the console of virtual server,there might be some keyboard layout differences.What to do in such case?ECL2.0, Virtual Server / Construction, Specification

    When you attach the Virtual Server Instance from the Console which is shown on the control panel by using any Japanese keyboard (JIS keyboard). The settings of some JIS keyboards have been different from the one of standard keyboards.

    This causes by the respective scopes. Therefore, you are required to execute this task. The following is the picture of standard keyboard.

    Furthermore, after you have configured “sshd config” (“Remote Desktop” for Windows) settings at the initial startup (this is “launch”) of the Virtual Server, you need to attach the respective Instances with “SSH” (“RDP” for Windows) when utilizing it normally.

    If you select “Standard (US) keyboard” when using the English one, you have no problem to operate it.

     

    faq_virtual_server_keyboard_01

    NOTE: Please use shift key to input respective symbols which are shown on upper-side for each key as the above picture.

     

    <Reference>
    When you use JIS keyboard, please refer to below procedures to input some symbols.
    # Please note that below procedures may not be available due to OS versions.

    1. “@”

    Linux series
    Change the key map with the below command and input “[“.

    localectl set-keymap jp106
    [How to return the key map setting]
    localectl set-keymap us

    # When you execute ssh command, you do not have to use “@” by using -l option.
    ssh -l <username> <IP address of the server>

    2. “:”

    Linux series
    Change the key map with the below command and input “.”.

    localectl set-keymap fr
    [How to return the key map setting]
    localectl set-keymap us

    # In vi editor, you can input “:” by “Shift + Q”.
    # You can also input “:” by “Shift + Ctrl + :”

    3. “=”

    Linux series
    Change the key map with the below command and input “Shift + \(backslash)”.

    localectl set-keymap jp106
    [How to return the key map setting]
    localectl set-keymap us

    <Reference>
    When you use Windows OS, screen keyboard may be helpful.

    Is this page helpful?

    Yes No

Documents

Tutorials

Manage ECL 2.0 resources like tenants, VMs and networks.

Service Descriptions

Service menu and specifications of each Enterprise Cloud service.

API References

API details of each service to manage instances ( For developers ).

Solution Guides

Various examples of using Enterprise Cloud.

We appreciate your cooperation in improving the site

Did this FAQ be helpful? If you have any comments, please let us know.

Thank you

Your feedback has been received.