Enterprise Cloud Knowledge Center
Close the Menu
Home > Enterprise Cloud 2.0 Support Information > FAQ - Enterprise Cloud 2.0 > Why the hot swap is N/A at the time of an HDD failure regarding Workload Optimized 2?

FAQ

Why the hot swap is N/A at the time of an HDD failure regarding Workload Optimized 2?

(:Last updated）

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.

  • ECL2.0
    •  
  • Baremetal Server
    •  

Related Pages

  • Vulnerabilities and Exposures for VMware ESXi and VMware vCenter Server (CVE-2021-21972, CVE-2021-21973, CVE-2021-21974)ECL2.0

    Thank you for using Enterprise Cloud (ECL) service.

    Please be informed of the response method and workaround of vulnerabilities (CVE-2021-21972, CVE-2021-21973, CVE-2021-21974) which were found in VMware ESXi and VMware vCenter Server provided by VMware in the Hypervisor menu for ECL2.0.

    Vulnerability information

    https://www.vmware.com/security/advisories/VMSA-2021-0002.html

    Affected Menu

    CVE

    Affected Menu

    CVE-2021-21974

    Official Image Template

    • ESXi-6.5.u1_64_BYOL_baremetal-server_01

    • ESXi-6.7.u3_64_BYOL_baremetal-server_01

    • vSphere_ESXi-6.5.u1_64_dedicated-hypervisor_01

    • vSphere_ESXi-6.7.u3_64_dedicated-hypervisor_01

    CVE-2021-21972,CVE-2021-21973

    Guest Image

    • vCenter-Server_6.5_u1e_Standard_not-include-lisence_vSphere-ESXi_001

    • vCenter-Server-Appliance_6.7_u3b_Standard_not-include-license_vSphere-ESXi_001

    Countermeasure

    Please upgrade to the modified version or perform a workaround.

    How to deal with CVE-2021-21974

    Solution

    • Please apply the patch to vSphere ESXi. The patch for each version is on following site. * VMware account is required.

    Minor Version

    Patch

    URL

    vSphere ESXi 6.7

    ESXi670-202102401-SG

    https://docs.vmware.com/en/VMware-vSphere/6.7/rn/esxi670-202102001.html

    vSphere ESXi 6.5

    ESXi650-202102101-SG

    https://docs.vmware.com/en/VMware-vSphere/6.5/rn/esxi650-202102001.html

    Workaround

    How to deal with CVE-2021-21972,CVE-2021-21973

    Solution

    • Please upgrade the modified version and download the image of each version from the following site. * VMware account is required.

    Minor Version

    Build Number

    URL

    vCenter Server 6.7

    17138064

    https://docs.vmware.com/en/VMware-vSphere/6.7/rn/esxi670-202102001.html

    vCenter Server 6.5

    17590285

    https://docs.vmware.com/en/VMware-vSphere/6.5/rn/esxi650-202102001.html

    Workaround

     

    Thank you.

    Open in a new window
  • Attention to vulnerability in Citrix Gateway Plug-in for Windows (CVE-2020-8257 / CVE-2020-8258)ECL2.0

    Thank you for using NTT Communications Enterprise Cloud.

    A vulnerability (CVE-2020-8257 / CVE-2020-8258) of Citrix Gateway Plug-in for Windows used for SSL-VPN connection has been confirmed in the remote console access (RCA) function of the Baremetal Server Menu of ECL2.0. The common platform of ECL2.0 is not affected by this problem. We recommend that customers using the ECL2.0 Baremetal Server Menu to check the latest information on vulnerabilities and take appropriate action as necessary.

    Vulnerability information

    https://support.citrix.com/article/CTX282684

    Affected Menu

    Baremetal Server

    Affected Version

    Citrix Gateway Plug-in 13.0 for Windows before 64.35
    Citrix Gateway Plug-in 12.1 for Windows before 59.16

    Countermeasure

    When try to make SSL-VPN connection from customer's client, upgrade of Citrix Gateway Plug-in Client will be required. Please upgrade the Plug-in following the instructions on the screen.

     

    Thank you.

    Open in a new window
  • When I tried to perform various settings on the UEFI (BIOS) screen at bare metal server startup, I was asked for the Administrator password. Please tell me the password to enter here.Baremetal Server, ECL2.0 / Operation, Specification

    The Administrator password required on the UEFI (BIOS) is not disclosed.

    If all functions of UEFI (BIOS) are provided to customers, it will be difficult to use and maintain quality of the service. So please note that customers are not allowed to change the settings.

    Service Descriptions - Baremetal Server - Terms and Conditions

    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 make NIC redundancy at Baremetal ServerBaremetal Server, ECL2.0 / Construction, Specification

    Steps to make NIC redundancy at Baremetal Server whose host OS is created with Enterprise Cloud 2.0 official template Red Hat Enterprise Linux 7 image is following.

    ==================================================
    1. Connect same logical network to each physical network device which connected each 2 physical NIC on same plane Baremetal server via Enterprise Cloud 2.0 Cloud computing control panel
    ==================================================
    Please make connection between same logical network and each physical network device which connected each 2 physical NIC on same plane Baremetal server with the procedure which informing at following tutorial. In this case, please specify each same segment type.

    In addition, please specify same segment ID about segment ID(VLAN ID) each in the case of using vlan in segment type.

    ==================================================
    2. Make redundant interface and configure IP address to redundant interface on Baremetal server host OS(Red Hat Enterprise Linux 7)
    ==================================================
    Please make interface redundancy with execute following command with Shell on Baremetal server host OS(Red Hat Enterprise Linux 7).

    --------------------------------------------------
    2-1. Disable IPv4 and IPv6 on physical NIC#1 and #2 which connected to the same plane on Baremetal server
    --------------------------------------------------
    # nmcli connection modify [physical_connection_name_1] autoconnect on ipv4.method disable ipv6.method ignore
    # nmcli connection modify [physical_connection_name_2] autoconnect on ipv4.method disable ipv6.method ignore

    ※Please specify the existing connection name which corresponds to physical NIC#1 on Baremetal server to physical_connection_name_1
    ※Please specify the existing connection name which corresponds to physical NIC#2 on Baremetal server to physical_connection_name_2

    --------------------------------------------------
    2-2. Create bonding interface using physical NIC#1 and #2 connected to the same plane on Baremetal server
    --------------------------------------------------
    # nmcli connection add type bond con-name [bond_connection_name_1] ifname [bond_interface_name_1] miimon 100 updelay 0 downdelay 0 mode active-backup primary [slave_interface_name_1] # nmcli connection add type bond-slave ifname [slave_interface_name_1] master [bond_interface_name_2] # nmcli connection add type bond-slave ifname [slave_interface_name_2] master [bond_interface_name_2]

    ※Please specify the existing connection name which corresponds to physical NIC#1 on Baremetal server to physical_connection_name_1
    ※Please specify the existing connection name which corresponds to physical NIC#2 on Baremetal server to physical_connection_name_2
    ※Please specify the new creating connection name for bonding interface to bond_connection_name_1
    ※Please specify the new creating bonding interface name to bond_interface_name_1
    ※Please specify the interface name of physical NIC#1 on Baremetal server which becomes to slave of bonding interface to slave_interface_name_1
    This interface becomes to primary physical NIC of bonding interface.
    ※Please specify to interface name of physical NIC#2 on Baremetal server which becomes to slave of bonding interface to slave_interface_name_2
    This interface becomes to secondary physical NIC of bonding interface.
    ※Please specify bonding interface name to bond_interface_name_2. Accordingly, please specify the same value as "bond_interface_name_1"

    --------------------------------------------------
    (Please carry out "2-3." in addition in the case of only using "flat" for segment type when connected with logical network in "1.".)
    2-3. Manually IP address setting to bonding interface(Please specify the parameters such as the default gateway more as needed.)
    --------------------------------------------------
    # nmcli connection modify [bond_connection_name_2] autoconnect on ipv4.method manual ipv4.address [ip_address_1]

    ※Please specify the connection name of bonding interface to bond_connection_name_2.
    Accordingly, please specify the same value as "bond_connection_name_1".
    ※Please specify the IP address assigned to bonding interface with CIDR format to ip_address_1.

    --------------------------------------------------
    (Please carry out "2-4." in addition in the case of only using "vlan" for segment type when connected with logical network in "1.".)
    2-4. Disable IPv4 and IPv6 on bonding interface.
    --------------------------------------------------
    # nmcli connection modify [bond_connection_name_2] autoconnect on ipv4.method disable ipv6.method ignore

    ※Please specify the connection name of bonding interface to bond_connection_name_2.
    Accordingly, please specify the same value as "bond_connection_name_1".

    --------------------------------------------------
    (Please carry out "2-5." in addition in the case of only using "vlan" for segment type when connected with logical network in "1.".)
    2-5. Create VLAN interface using bonding interface
    --------------------------------------------------
    # nmcli connection add type vlan dev [bond_interface_name_3] con-name [vlan_connection_name_1] ifname [vlan_interface_name] id [vlan_id]

    ※Please specify the new creating bonding interface name which VLAN interface uses to bond_interface_name_3.
    Accordingly, please specify the same value as "bond_interface_name_1".
    ※Please specify the new creating connection name which is for VLAN interface to vlan_connection_name_1
    ※Please specify the new creating VLAN interface name to vlan_interface_name.
    ※Please specify VLAN ID which corresponds to connected logical network to vlan_id.

    --------------------------------------------------
    (Please carry out "2-6." in addition in the case of only using "vlan" for segment type when connected with logical network in "1.".)
    2-6. Manually IP address setting to VLAN interface(Please specify the parameters such as the default gateway more as needed.)
    --------------------------------------------------
    # nmcli connection modify [vlan_connection_name_2] autoconnect on ipv4.method manual ipv4.address [ip_address_2]

    ※Please specify the connection name of VLAN interface to vlan_connection_name_2.
    Accordingly, please specify the same value as "vlan_connection_name_1".
    ※Please specify the IP address assigned to VLAN interface with CIDR format to ip_address_2.

    --------------------------------------------------
    2-7. Restarting network(or rebooting OS)
    --------------------------------------------------
    # systemctl restart network.service
    (# shutdown -r now)

    --------------------------------------------------

    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.

▲