FAQ

I want to place an ISO file in the image storage area and mount the ISO image on the virtual server. Is there a function to mount the ISO image as an optical drive?

2017-06-27 (2020-10-07:Last updated）

The function which mount the ISO image on the virtual server as an optical drive is not provided by this service. (The ISO image of the virtual server can only be used for OS installation.)
We apologize for the inconvenience. Please mount the ISO image on the virtual server and mount the ISO image using the virtual drive etc.

Reference: Service Descriptions _ Image storage area - Private ISO

Is this page helpful?

Yes No

ECL2.0
Virtual Server

yum and dnf commands fail on Red Hat Enterprise Linux 8Baremetal Server, Dedicated Hypervisor, ECL2.0, OS, Virtual Server

Issue

The yum command and dnf command may fail in Red Hat Enterprise Linux 8 (RHEL8). We apologize for the inconvenience, but please follow the procedure described in the remedy.

- Curl error (56): Failure when receiving data from the peer for -<Region Name>.ecl.ntt.com.local/pulp/repos/content/dist/rhel8/rhui/8/x86_64/appstream/os/repodata/repomd.xml
[OpenSSL SSL_read: error:14094415:SSL routines:ssl3_read_bytes:sslv3 alert certificate expired,errno 0]

Affected Template

The following templates in each menu are affected.

Menu	Template
Virtual Server *1	RedHatEnterpriseLinux-8.1_64_include-license_virtual-server_02 RedHatEnterpriseLinux-8.2_64_include-license_virtual-server_02
Baremetal Server	RedHatEnterpriseLinux-8.1_64_include-license_baremetal-server_01
Dedicated Hypervisor	RedHatEnterpriseLinux-8.1_64_include-license_hw9_vSphere-ESXi_02

*１For these templates, customers can use yum or dnf without the following Solution.

RedHatEnterpriseLinux-8.1_64_include-license_virtual-server_12

RedHatEnterpriseLinux-8.2_64_include-license_virtual-server_12

Solution

To avoid the problem, the customer needs to renew the client certificate.

①Delete the existing existing rpm file

rpm -e rh08-sr-rhui-client02-<Region Name>-ecl-ntt-com-2.0-1.noarch

Select <Region Name> from jp1, jp2, jp4, jp5, jp6, uk1, de1, fr1, us1, sg1, hk1.

②Modify hosts file

Add the following to /etc/ hosts file.

169.254.127.24 rhcds-sr-vip-<Region Name>.ecl.ntt.com.local

③Get the new rpm file

#curl --insecure https://<Link Local Address>/pub/rhui-client-packages/<rpm package name> >> <rpm package name>
#curl --insecure https://<Link Local Address>/pub/rhui-gpg-key/RPM-GPG-KEY-rhui-custom >> RPM-GPG-KEY-rhui-custom

・Link Local Address

Please specify 169.254.127.24 for <link local address>.

・rpm package name

For <rpm package name>, specify an appropriate file according to the region.

JP1 rh08-sr-rhui-client02-jp1-ecl-ntt-com-2.0-2.noarch.rpm
JP2 rh08-sr-rhui-client02-jp2-ecl-ntt-com-2.0-2.noarch.rpm
JP4 rh08-sr-rhui-client02-jp4-ecl-ntt-com-2.0-2.noarch.rpm
JP5 rh08-sr-rhui-client02-jp5-ecl-ntt-com-2.0-2.noarch.rpm
JP6 rh08-sr-rhui-client02-jp6-ecl-ntt-com-2.0-2.noarch.rpm
US1 rh08-sr-rhui-client02-us1-ecl-ntt-com-2.0-2.noarch.rpm
UK1 rh08-sr-rhui-client02-uk1-ecl-ntt-com-2.0-2.noarch.rpm
SG1 rh08-sr-rhui-client02-sg1-ecl-ntt-com-2.0-2.noarch.rpm
HK1 rh08-sr-rhui-client02-hk1-ecl-ntt-com-2.0-2.noarch.rpm
DE1 rh08-sr-rhui-client02-de1-ecl-ntt-com-2.0-2.noarch.rpm
AU1 rh08-sr-rhui-client02-au1-ecl-ntt-com-2.0-2.noarch.rpm
FR1 rh08-sr-rhui-client02-fr1-ecl-ntt-com-2.0-2.noarch.rpm

④Install rpm files

#chown root:root ~/<rpm package name>
#chown root:root ~/RPM-GPG-KEY-rhui-custom
#chmod u+x ~/<rpm package name>
#chmod u+x ~/RPM-GPG-KEY-rhui-custom
#rpm -U <rpm package name>

⑤Import GPG Key

#rpm --import ~/RPM-GPG-KEY-rhui-custom

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
On Monitoring Control Panel, CPU utilization of Virtual Server Instance sometimes exceed 100%. Is this normal?ECL2.0, Monitoring, Virtual Server / Operation, Specification
Yes. The maximum value is “100 percent x number of CPU cores”. (Example: If the virtual server instance is 16 CPUs, the value ranges from 0 to 1600 percent.)
So CPU Utilization may exceed 100%, depending on the flavor of the virtual server.
Reference:
Service Description - Monitoring - Data Collection/Accumulation - Virtual Server Instance
Service Description - Virtual Server - Plan List
Is this page helpful?
Yes No
Open in a new window
The volume can not be operated when the instance is deleted while the volume is attachedECL2.0, Virtual Server
Issue
When you delete an instance while the volume is attached, sometimes you can’t operate the volume. For example, you can’t delete or attach the volume to another instance.
In this case, The instance is deleted completely, but the volume attached to “None” and status is still “In-use”.

Solution
In order to avoid this issue, please detach a volume after turning off an instance before you delete an instance.
If this issue is happen and you can’t operate the volume, please inquire with a ticket.
Open in a new window
It is not possible to detach root volume from instance.ECL2.0, Virtual Server / Operation, Specification
Root volume is not able to detach unlike data volume. Root volume continue to be root volume for appropriate instance unless deleting instance.
Reference：Service Descriptions - Glossaries of Volume
Is this page helpful?
Yes No
Open in a new window

FAQ

I want to place an ISO file in the image storage area and mount the ISO image on the virtual server. Is there a function to mount the ISO image as an optical drive?

Support Information

Enterprise Cloud 2.0

Enterprise Cloud 1.0

We appreciate your cooperation in improving the site

Thank you