Enterprise Cloud Knowledge Center
Close the Menu
Home > Enterprise Cloud 2.0 Support Information > FAQ - Enterprise Cloud 2.0 > Even if I execute the ECL CLI command (ecl baremetal server stop), the bare metal server does not stop.

FAQ

Even if I execute the ECL CLI command (ecl baremetal server stop), the bare metal server does not stop.

(:Last updated）

The ECL CLI command (stop ecl bare metal server) executes a shutdown on software level via ACPI, so, depending on software status, it might take some time to stop power supply or it might not be stopped.

If you want to definitely stop the baremetal server, please stop the power supply on hardware level as referred to the below document.

Tutorial - Baremetal Server - Baremetal Server power operations

  • ECL2.0
    •  
  • Baremetal Server
    •  

Related Pages

  • How to change BIOS settings on Baremetal server?Baremetal Server, ECL2.0 / Construction, Operation, Specification

    In the server list of Cloud Computing Control Panel, you can change the setting at 'Set UEFI' from the action of the target Baremetal server.

    Refer to below Tutorial regarding how to access to UEFI(BIOS) setting window.
    Tutorial - Baremetal Server Tools

    Refer to below Service Description regarding the list of UEFI settings.
    Service Description - Baremetal Server - UEFI Function

    Open in a new window
  • About the issue which the DHCP server of the logical network announces an unintended cache (resolver) DNS server addressBaremetal Server, Common Function Gateway, ECL2.0, Logical Network, Virtual Server

    Overview of the Issue

    • The DHCP server of the logical network delivers an IP address (IP address of the DHCP server) that the customer does not intend as the IP address of the cache (resolver) DNS server.
    • If the OS of the virtual server instance or the bare metal server acquires the IP address (DHCP server IP address) that the customer does not intend as the IP address of the cache (resolver) DNS server by DHCP, the global name space name can be resolved.* Enterprise Cloud 2.0 does not offer cache (resolver) DNS server.

    Detail of the issue

    Region

    • JP3, JP4, JP5

    Menu

    • It occurs when both of the logical network and the server (virtual server or bare metal server) satisfy the following conditions.
    • Logical network
      • Case 1. Create from the Logical Network menu and enter the following items in the subnet
        • DHCP enabled: Checking
        • DNS server: You have not entered an IP address in the text box
      • Case 2. Common Functions Common Functions Created from Gateway Menu All logical networks for gateway
    • Server
      • Case 1. Create with virtual server menu, with the following settings
        • Interface: Connected to a logical network that meets the above conditions
        • OS: Obtained the IP address of the cache (resolver) DNS server by DHCP
      • Case 2. Bare metal server
        • Interface: Connected to a logical network that meets the above conditions
        • OS: Obtained the IP address of the cache (resolver) DNS server by DHCP

    Confirmation method

    • The method of checking whether the condition that this event meets is as follows.
    • Logical network
      • Subnet
        • Cloud Computing Control Panel> Network> Logical Network> Please press subnet name from subnet.
          • DHCP Enabled: Please confirm whether it is valid on "Subnet Details" screen
          • DNS Server: It may be applicable when DNS server is "None" on "Subnet Details" screen. In case of "None", it indicates whether the DNS server address has been delivered without entering the IP address in the DNS server, or 0.0.0.0 is entered to stop distributing the DNS server address.
    • Virtual Server
      • Interface
        • Please press the instance name from the cloud computing control panel> server> virtual server> instance and check on the "instance details" screen
      • OS
        • Windows Server 2012 R2 / Windows Server 2016: Network and Sharing Center> Changing adapter settings> "Interface name connected to logical network"> Properties> Internet Protocol Version 4 (TCP / IPv4) Please check on Internet Protocol Version 4 (TCP / IPv4) Properties screen
        • Execute the following command at Red Hat Enterprise Linux / CentOS: Shell and check the output.
          • nmcli connection show <interface name connected to the logical network>
    • Bare metal server
      • Interface
        • Cloud Computing Control Panel> Server> Please press the bare metal server name from the bare metal server and check on the "Bare Metal Server Details" screen.
      • OS
        • Windows Server 2012 R2: Network and Sharing Center> Changing Adapter Settings> "Logical (VLAN) Interface Connected to Logical Network"> Properties> Internet Protocol Version 4 (TCP / IPv4) Please check on the Properties of protocol version 4 (TCP / IPv4) screen
        • Execute the following command at Red Hat Enterprse Linux / CentOS: Shell and check the output
          • nmcli connection show <interface name connected to the logical network>

    Solution

    The solution is as follows.

    1. When it is necessary to acquire the IP address of the cache (resolver) DNS server by DHCP
      • Please perform the following setting in "Edit Subnet".
        • DNS Server: Enter the IP address of the cache (resolver) DNS server in the text box (* 1)
    2. When it is not necessary to acquire the IP address of the cache (resolver) DNS server by DHCP
      • Please perform the following setting in "Edit Subnet".
        • DNS Server: Check the "Disable DNS Server" check box. (* 2)

    * 1 We do not offer cache (resolver) DNS server in Enterprise Cloud 2.0. Therefore, please specify the IP address of your internal DNS server and the IP address of the cache DNS server provided by the customer's selected public DNS service.

    * 2 In the case of API, enter 0.0.0.0 in the DNS server section.

    Schedule

    We plan to change the setting of the logical network of existing customers and stop delivery of an unintended cache (resolver) DNS server address.

    If you need to take action before then, please take measures to deal with delivery / distribution of DNS server addresses referring to the above mentioned actions.

    Open in a new window
  • How to change the default gateway for VMware vSphere ESXi?Baremetal Server, ECL2.0 / Construction

    Please follow the below steps.
    1. Execute the Remote Console Access to Baremetal server according to Tutorial.
    2. On DCUI screen, of VMware vSphere ESXi, press [F2].
    3. On Authentication Required screen, put User / Password and press [Enter].
    4. On System Customization screen, select "Configure Management Network" and press [Enter].
    5. On Configure Management Network screen, select "IP Configuration" and press [Enter].
    6. On IP Configuration screen, change IP address of Default Gateway and press [Enter].
    7. On IP Configuration screen, press [Esc].
    8. When you are required to reflect the change and reboot the management network, press [Y] on Configure Management Network : Confirm screen.

    Open in a new window
  • How to transfer the files saved on the client terminal to the ECL2.0 server?Baremetal Server, ECL2.0, Virtual Server / Operation

    Please prepare FTP server, etc. and transfer the files via the Internet.

    Open in a new window
  • Why the hot swap is N/A at the time of an HDD failure regarding Workload Optimized 2?Baremetal Server, ECL2.0 / Construction, Specification

    It is one of the specifications of Workload Optimized 2 that the customers can set up the RAID configuration and so forth. So, the hot swap is not available to protect the data owned by the customers.

    Open in a new window

Support Information

Enterprise Cloud 2.0

Enterprise Cloud 1.0

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.

▲