FAQ(ECL2.0)

ECL2.0 - FAQ

Showing 251-258 of 258
Items per page:
  • 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

    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

    Performing off / on (* 2) (including rebooting with HA) after adding/deleting interfaces and attaching/detaching the volume (* 1).

    * 1. We recommend adding/deleting interfaces, attaching / detaching volumes with the instance "stopped", and confirming after startup.
    * 2. 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 as effective as this action.)

    Recommended operation
    1. Stop the instance(OS shutdown would be recommended)
    2. Add/delete the interface or attach/detach the volume
    3. Start the instance
    4. Confirm the status of the interface or the volume
        4-1 Whether the correspondence between the device name of the interface and IP address is correct, or not
            -> If it is not correct, follow the steps described below in "Event and Workaround".
        4-2.Whether the volume is online(Windows) or mounted properly(Linux), or not
            -> If it is not correct, follow the steps described below in "Event and Workaround".
    Once you perform off / on (* 2), these issues never occur again unless you newly add/delete the interface or attach/detach the volume.
    # After you perform the above recommended operation, if you newly add/delete the interface or attach/detach the volume, the issues might occur again. In that case, you need to follow the steps described below in "Event and Workaround" again.
    # The above is the specification of OpenStack.

    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.

    Is this page helpful?

    Yes No
  • About the Ping response specification of the AWS gateway.Amazon Web Services Inter-Connectivity, ECL2.0

    Communication with the AWS gateway implements flow restriction to protect the service infrastructure. Please do not alive monitoring with Ping to AWS gateway.
    Note that we do not implement the above flow restriction for communication passing through the AWS gateway, and will provide quality and speed according to the contract plan.

    Is this page helpful?

    Yes No
  • Interfaces on Red Hat Enterprise Linux on Virtual Server are not configure when operate "add interface" via GUI/API. What should I do?ECL2.0, OS, Virtual Server

    When you create a virtual server instance from the official template for RedHatEnterpriseLinux provided by us, only 1 configuration profile will be created at default, even if you add multiple interfaces in creation.

    Therefore, when customer operates the following setting to Red Hat Enterprise Linux on Virtual Server, please operate the setting as described below.

    - Selecting several networks when creating instance.
    - Adding interface by  "add interface" via GUI/API after creating instance.

    Please operate the following configuration on Red Hat Enterprise Linux OS

    1. Executing nmcli command for confirming enable network connection
    ("eth0" is only displayed with default)

    # nmcli con show

    2. Confirming whether the adding interfaces such as "eth1" are displayed.

    # nmcli dev show

    3. Configuring the adding interfaces.
    (The following command is example to configure "eth1" as "System eth1")

    # nmcli c add type ethernet ifname eth1 con-name "System eth1"

    Is this page helpful?

    Yes No
  • The error message "access denied" is displayed when "set interfaces" command is executed.ECL2.0, Firewall (Brocade 5600 vRouter)

    The command "set interface data plane * address *" is not available, while "set interface data plane * description" is available.
    If you like to setup the IP address of interface, please login to the Smart Data Platform Portal site.

    Is this page helpful?

    Yes No
  • Where should I contact if I want to ask technical questions about Arcserve UDP Advanced Edition?Arcserve, ECL2.0

    Please contact the software support desk of Arcserve. You can find the details of how to contact them in “Application Receipt Mail”.

    In addition, support included in this menu is “Technical support”. Please refer to Arcserve Support Policy (EN) for the details of the support conditions.

    Reference
    Service Descriptions - Arcserve - Software Support
    (excerpt)
    Product support for Arcserve UDP Advanced Edition is provided directly by Arcserve.
    
    Tutorial - Arcserve - New Application method of Arcserve License
    (excerpt)
    On the main menu screen, your application contents will be displayed.
    And we will send “Application Receipt Mail” to the “E-mail address” you registered, so please confirm its contents.

     

    Is this page helpful?

    Yes No
  • 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.

    Is this page helpful?

    Yes No
  • 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 this page helpful?

    Yes No
  • 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 this page helpful?

    Yes No

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.