FAQ(ECL2.0)

Virtual Server - FAQ

Showing 101-110 of 116
  • MTU on Virtual Server which created by RedHat Enterprise Linux official image is 1450 byte. What should I do when I'd like to change MTU to 1500 byte?ECL2.0, Virtual Server

    Default MTU value on Virtual Server which created by RedHat Enterprise Linux official image is 1450 byte.
    Please conduct the following setting when customer would like to change MTU to 1500 byte.

    【How to change MTU】
    1.Login to created virtual server as root user
    2.Change MTU value on each interface of the virtual server

    [Command]
    ifconfig <InterfaceName> mtu 1500
    
    [Example]
    ifconfig eht0 mtu 1500

     

    3.Delete the following configuration about MTU value on Virtual Server which created by RedHat Enterprise Linux official image (RedHatEnterpriseLinux-7.1_64_include-license_virtual-server_22)if customer would like to fix MTU as 1500 byte because the MTU value reverts to default setting(i.e.1450 byte) when customer reboots the virtual server.

    [Command]
    vi /etc/rc.local
    
    [Configuration which need to be deleted]
    for vnic in \`/sbin/ifconfig | grep eth | grep -v ether | cut -d":" -f1\`
    do
     /sbin/ifconfig \${vnic} mtu 1450
    done
  • Windows instance faced bluescreen or freeze. What should I do?ECL2.0, Virtual Server

    Windows instance faced blue screen or freeze.

    Windows Server 2012R2 official images may cause a suddenly blue screen or freeze.
    The workaround is to update the network driver, storage driver, and memory balloon driver.
    There are two ways to update the software: using the Internet (Workaround 1) and not using the Internet (Workaround 2). Please check the following steps for each option.

    Workaround 1. Update on the Internet available instances


    Note: This workaround requires the Internet connection for your instance.

    1. Download a virtio-win-0.1.208 image to the instance

    Download a virtio-win-0.1.208 image from here for the instance for which you want to update the virtio driver.

    2. Mount the ISO file

    Mount the ISO file you downloaded.

    3. Update network drivers

    In "Server Manager", click "Tools" and select "Computer Management".

    Press "Device Manager" in the left pane.

    Expand "Network adapters" in the center pane.
    Verify that "Red Hat VirtIO Ethernet Adapter" is displayed. (If you are using multiple logical networks, the adapter for the number of logical networks are displayed.)

    Right click on the displayed adapter and select "Properties".

    Select "Driver" tab in the displayed window.

    Confirm that the Driver Version is "63.74.104.14100" or lower, and press "Update Driver..." in the same window.

    The Windows Driver Update Wizard opens.
    Click on "Browse my computer for driver software".

    A dialog box appears to select the directory where the new driver software is stored.
    Click "Browse..." to select the drive on which you mounted the ISO file, click "OK", and then click "Next".

    When the pop-up "Would you like to install this device software?" appears, click "Install".

    Then, when you see "Windows has successfully updated your device software", press "Close".

    You are automatically returned to the window where you checked the version before updating the driver.
    Make sure that the version is "63.85.104.20800", and press "Close".

    If the driver versions do not change, please apply the update to all Network Adapters, then "6. Eject the ISO (DVD drive)", and reboot the instance and try the update again.

    If you are using multiple logical networks, update the remaining Red Hat VirtIO Ethernet Adapters to version "63.85.104.20800" as well.

    4. Update storage drivers

    In "Server Manager", click "Tools" and select "Computer Management".

    Press "Device Manager" in the left pane, and expand "Network adapters" in the center pane.
    Verify that the Red Hat VirtIO SCSI contoller is displayed. (If you are using multiple disks, the adapter for the number of disks are displayed.)

    Right click on the displayed adapter and select "Properties".
    Check the version in "Driver" tab of the window.

    Follow the same procedure for updating the network driver to the Red Hat VirtIO SCSI contoller, verify that it is upgraded to "62.85.104.20800".

    If you have multiple disks, update the remaining Red Hat VirtIO SCSI contoller to version "62.85.104.20800" as well.

    5. Update memory balloon drivers

    Note: If you are using the official image "WindowsServer-2012R2_Standard_64_include-license_virtual-server_20", please contact us for more details.

    In "Server Manager", click "Tools" and select "Computer Management".

    Press "Device Manager" in the left pane, and expand "System Devices" in the center pane.
    Verify that the VirtIO Balloon Driver is displayed.

    Right click on the displayed adapter and select "Properties".
    Check the version in "Driver" tab of the window.

    Follow the same procedure for updating the network driver to the VirtIO Balloon Driver, verify that it is upgraded to "62.85.104.20800".

    6. Eject the ISO (DVD drive)

    Eject the ISO (DVD drive).

    7. Reboot the instance

    Reboot the WindowsServer instance.

    Workaround 2. Update on the Internet unreachable instances


    Note: With this workaround, it is possible to update virtio drivers even if your instance does not have the Internet connection. However, since the procedure includes the creation of a temporary instance and volume, a fee will be charged.

    1. Create a temporary volume with a virtio-win-0.1.208 image

    Create a 15GB temporary volume and attach it to a temporary instance (created from an official WindowsServer 2012R2 image) with the Internet connection.

    In "Server Manager", click "Tools" and select "Computer Management".

    Press "Disk Management" in the left pane.

    Right click on "Disk 1" and select "Online".

    Right click on "Disk 1" and select "Initialize Disk".

    Select MBR format and click "OK".

    Right click on unallocated area of "Disk 1" and select "New Simple Volume...".

    Follow the instructions in the Wizard to set up the volume.
    In the following example, the disk is formatted with NTFS and used as drive D.

    When the volume is available as drive D, download a virtio-win-0.1.208 image from here and save it in the drive.

    Shutdown the temporary instance and detach the temporary volume.

    2. Import the virtio-win-0.1.208 image from the temporary volume

    Attach the temporary volume to the instance for which you want to update the virtio drivers.

    In "Server Manager", click "Tools" and select "Computer Management".
    Press "Disk Management" in the left pane.
    Right click on the disk of the temporary volume and select "Online".

    When the volume is available, mount the virtio-win-0.1.208 image.

    3. Update virtio drivers

    Follow the same procedure as Workaround 1 to update the virtio drivers.

    4. Detach the temporary volume

    Eject the ISO (DVD drive) you mounted in "2. Import the virtio-win-0.1.208 image from the temporary volume".
    In "Server Manager", click "Tools" and select "Computer Management".
    Press "Disk Management" in the left pane.
    Right click on the disk of the temporary volume and select "Offline".
    Shutoff the instance and detach the temporary volume.

    5. Start the instance

    Start the WindowsServer instance.

  • SAP applications on Virtual Server Service are supported by SAP?ECL2.0, Virtual Server

    Red Hat Enterprise Linux for SAP Applications menu offers environments for SAP Applications supported by SAP.

  • System clock has been changed when shutdown & launch or reboot instances.ECL2.0, Virtual Server

    System clock on Windows Server is reset and changed to Coordinated Universal Time (UTC)when shutdown&launch or reboot instances.

    After Windows OS is booted, System clock is synchronized to NTP server and recovered to time which is set before shutdown&launch or reboot.

    We recommend that you set UTC for your Windows instances, however, you can conduct the following workaround if you would like to avoid it.

    # When Windows does not synchronize with a NTP server, the system clock may show an irregular date after Windows restarts.
    In this case, this system clock will return to a regular date by stopping and starting the instance once.
    After that, the regular date will be kept even if you restart Windows.

    Workaround

    1. Open Command Prompt Window
    2. Execute the following command for setting RealTimeIsUniversal registry key

    reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation" /v RealTimeIsUniversal /d 1 /t REG_DWORD /f

    3. Execute the following command for confirmation of the above setting

    reg query "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TimeZoneInformation" /s

    , and confirm whether the following message is outputted as execution result.

    RealTimeIsUniversal    REG_DWORD    0x1
  • Unable to deploy Storage Spaces on Windows Server on Instance.Virtual Server

    Even if you mount Volume on Instance, it unable to deploy Storage Spaces as default setting

    because driver on Instance does not correspond to Storage Spaces.

    It has 2 workarounds for it as below;

    Please note that both workarounds have cautioned, understand the cautions and conduct any workarounds at your own risk.

     

    Workaround1.Changing driver type

    You can deploy Storage Spaces if you change driver type on Instance by configuring property to snapshot which was created from Instance of Virtual Server. Detail procedure is the following.

    (Step for changing driver type)

    1. Select Windows Server of Official template, and create an Instance
    2. Log in The Instance via console, and setting account
    3. After shut down the Windows Server Instance, create snapshot from the Instance
    4. Configure property in the snapshot via API(It requires API operation) After getting Keystone token, execute the following API for changing driver type in the snapshot from ’hw_disk_bus’ to ’ide’API format for changing ’hw_disk_bus’ from default(virtio) to ’ide’curl -i -X PATCH -H 'Content-Type: application/openstack-images-v2.1-json-patch'  -H 'X-Auth-Token: {token}' https://{endpoint}/v2/images/{image_id} -d '[{"path": "/hw_disk_bus", "value": "ide", "op": "add"}]' Confirm response '200 OK' against the above API callHTTP/1.1 200 OK

      content-length: 1662

      server: Apache

      connection: close

      *snip*

      (Reference)Roll back to default setting

      API format for changing ’hw_disk_bus’ from ’ide’ to default(virtio)

      curl -i -X PATCH -H 'Content-Type: application/openstack-images-v2.1-json-patch'  -H 'X-Auth-Token: {token}' https://{endpoint}/v2/images/{image_id} -d '[{"path": "/hw_disk_bus", "value": "virtio", "op": "replace"}]

    5. Create Instance from the snapshot which was executed procedure 4.
    6. Enable to deploy Storage Spaces on setting display on Windows Server as the following image.faq_vs_storage_space

     

    (Cautions)

    • Up to 4 volumes(including root volume) can be attached to each Instance by this work around.
    • Volume can’t be attached/detached with power-on. Please power off Instance when attach/detach Volume.
    • API operation is required when attaching additional Volume. It fails to attach additional Volume by GUI operation for attaching to existing disk pass. (API format for attaching additional Volume)

    curl -i 'https://{endpoint}/v2/{project_id}/servers/{server_id}/os-volume_attachments' -X POST -H "Accept: application/json" -H "Content-Type: application/json"  -H "X-Auth-Token: {token}" -d '{"volumeAttachment": {"device": "{device_path}", "volumeId": "{volume_id}"}}

    • This workaround might cause to decrease I/O performance to Volume.

     

    Workaround2.Using Block Storage

    You can deploy Storage Spaces if you use Block Storage(Provisioned I/O Performance) and mount it instead of Volume of Virtual Server.

    (Cautions)

    This workaround has been verified by Enterprise Cloud Provider, however, it is not supported by Microsoft Corporation because Block Storage adopts iSCSI connection and Microsoft does not support iSCSI connection for Storage Space.

     

    ▼Reference:Deploy Storage Spaces - TechNet - Microsoft

    https://technet.microsoft.com/en-us/library/jj822938%28v=ws.11%29.aspx

     

    ▼Reference:Service Description of Block Storage(Provisioned I/O Performance)

    /en/documents/service-descriptions/rsts/storage/block_storage.html

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

    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 keymap with the below command and input "[".

    localectl set-keymap jp106
    [How to return the keymap 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 keymap with the below command and input ".".

    localectl set-keymap fr
    [How to return the keymap 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 keymap with the below command and input "Shift + \(backslash)".

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

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

  • ”No valid host was found” has been displayed when creating Instance.ECL2.0, Virtual Server

    The cause might be one of following issues.

    1. Specified IP address has been already used on other resources.

    2. Customer tries to allocate IP address from "IP Address Allocation Pools" of Logical Network, but there is no available IP address in "IP Address Allocation Pools" left.

    3. The menu is not provided in that region or group.

    Please refer to below for the list of services provided in each region or group. Service Descriptions - The List of Services provided in each Region

    4. Creating an instance is not available temporarily.

    (1) Please try it again later.

    (2) Please consider creating an instance in another region / another group.

    (3) When the issue is not resolved by the above actions, due to popular demand, we are afraid that it might not be possible to do resource creation and flavor change in the region/group where the customer is trying to do it. In that case, please create a ticket via Ticket System.

  • Can I extend the created Volume?ECL2.0, Virtual Server

    Yes.

    When extending the volume, please refer to the following procedure.

    Service Description - Extending Volumes

    If you implement this and create a new instance from the extended volume, the extended part will be recognized as an unallocated space on the OS.

    When extending a volume, it is necessary to detach the volume from the instance once, but detaching is not possible for the root volume (the first volume including the OS area).
    Therefore, delete the instance once, extend the volume, specify the extended volume, and create the instance again. (Deleting an instance keeps the root volume and its contents.)

  • IP address is not assigned on Windows Server Instance when I launch the Instance after the Instance has been stopped. Why does it occur and what should I do?ECL2.0, Virtual Server

    It might occur when customer reboot(including reboot by HA function) Windows Server Instance. (Displaying as “Duplicate”, and IP address might be 169.254.x.x of auto configuration address)

    This event might occur DAD(Duplicate Address Detection) function of Windows OS when DHCP of logical network is set OFF.
    (due to colliding between DAD function and position confirmation frame of logical network)

    If this event has occurred, you can resolve this by the following procedures.

    1. Configure the interface address on Windows OS again.
    2. Reboot Windows OS(Guest OS)

    And, the following 2 methods are the workaround for this event.

    *)The 1st method(Enable to DHCP function on logical network) is recommended rather than 
    the 2nd method( In case it needs to disable to DHCP function on logical network, 
    customer should configure static IP address and disable to DAD function on Windows OS.) 
    because the 2nd method is expected to only decrease possibility of this event 
    (i.e. this event might be occur even if execute the 2nd method).

    1. Enable to DHCP function on logical network

    (You can specify IP address even if DHCP on logical network is enabled. We recommend to enable to DHCP on logical network unless customer has any specific reason to use customer’s own DHCP server.)

    2. In case it needs to disable to DHCP function on logical network, customer should configure static IP address and disable to DAD function on Windows OS.

    (Reference) How to disable to DAD function on Windows OS

    1. Access to search box from Start menu, input "regedt32" on search box and execute enter.
    2. Click "HKEYLOCAL MACHINE" on Registry Editor
    3. Click System→CurrentControlSet→Services→TcpIp→Parameters
    4. Right-click Parameters, and click New→DWORD(32-bit)Value
    5. Delete "New Value #1", and input "ArpRetryCount"
    6. Double-click "ArpRetryCount", and input "0" on Value date

    (Note) Disabling DAD function will interfere with the operation of the failover cluster. In the environment using a failover cluster, please enable DHCP for Logical Network, delete the ArpRetryCount setting,

  • Is there the auto-scale function?Virtual Server

    We have NOT provided the auto-scale function so far. However, you can be automated to add an Instance in the event of the high-loaded if you utilize to combine with Monitoring.

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.