FAQ(ECL2.0)
Virtual Server - FAQ
- 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.
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.) - Is there the auto-scale function?Virtual Server
- 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.
- Configure the interface address on Windows OS again.
- 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
- Access to search box from Start menu, input "regedt32" on search box and execute enter.
- Click "HKEYLOCAL MACHINE" on Registry Editor
- Click System→CurrentControlSet→Services→TcpIp→Parameters
- Right-click Parameters, and click New→DWORD(32-bit)Value
- Delete "New Value #1", and input "ArpRetryCount"
- 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,
- Can I take the backups of the Instance(s) or the Volume(s)?Virtual Server
You can take the backups of the Instance(s) by imaging the Instance(s) and/or Volume(s). The followings are the 2 ways different ways to do it.
This is a function in order for you to create an image of the current state. Please note that this does not include scheduling and restoring functions and taking incremental backups.- Snapshot: In this case, you have created the Image from the Snapshot (Imaging the route disk state).
NOTE: You are required to shutdown the relevant Instance prior to taking the Image. If you take it without shutdown that Instance the file mismatch may occur. because of that, you may fail to take them normally. - Image: When you want to convert volumes into disk images (Bootable volumes or Unbootable volumes etc).
NOTE: You can NOT image a Volume if the Volume has been attached to the relevant Instance. So, you are required to detach the Volume (from the Instance) prior to imaging it.
- Snapshot: In this case, you have created the Image from the Snapshot (Imaging the route disk state).