What are the limitations of using ECSs?
It is recommended not to upgrade the kernel version and operating system version of the Elastic Cloud Server on your own. If you need to upgrade the main version of the operating system, such as upgrading from CentOS 7.5 to CentOS 7.6, please use the operating system switching function provided by the public cloud platform.
It is recommended not to uninstall the performance assistance optimization software pre-installed on the Elastic Cloud Server.
It is recommended not to modify the MAC address of the Elastic Cloud Server NIC.
How long does it take to create a cloud server?
In general, it only takes a few minutes to complete the activation.
Can multiple EVSs be mounted to one cloud server?
Yes, a cloud server can mount up to 8 EVSs as data disks. If you need to increase the quota, you can submit a ticket for adjustment.
Can multiple Elastic IPs be mounted to one cloud server?
Yes, you can create multiple NICs, bind each NIC to an Elastic IP, and then bind those NICs to an ECS instance.
How to use the Elastic Cloud Server purchased via Yearly/Monthly Subscription?
A subscription-based ECS cannot be deleted after it is created. If you need to stop using it, on the ECS list page, click More > Unsubscribe in the Operation column to unsubscribe.
· Uninstall is not supported for system disks purchased together when creating an Elastic Cloud Server.
· Uninstall is not supported for data disks purchased together when creating an Elastic Cloud Server.
· Unbind is not supported for Elastic IP purchased together when creating an Elastic Cloud Server. If you want to unbind the resources, we suggest that you place separate orders for resources.
How to use the Elastic Cloud Server purchased via Pay-As-You-Go Subscription?
Like traditional hardware servers, ECSs can be deployed with any business application, such as the email system, Web system, EPR system, etc. Once an ECS is created, you can use it on the cloud just as if you were using your own local PC or physical server. A pay-as-you-go ECS generates an order on demand after it is created, and resources can be deleted at any time. If you need to stop using it, on the ECS list page, click More > Delete in the Operation column to delete the resources.
· Uninstall is not supported for system disks purchased together when creating an Elastic Cloud Server.
· Uninstall is not supported for data disks purchased together when creating an Elastic Cloud Server.
· Unbind is not supported for Elastic IP purchased together when creating an Elastic Cloud Server. If there is a need for unbinding, it is recommended that resources be ordered separately
In general, it can be successfully activated within a few minutes. Specifically, it is related to the specifications of the Elastic Cloud Server, configuration resources (such as EVS, Elastic IP), and the current system load. Note: If it cannot be activated for a long time, please contact customer service for technical support.
What does the deleted Elastic Cloud Server mean?
This is an intermediate state of Elastic Cloud Server. It means that the Elastic Cloud Server has been deleted normally. In this state, the Elastic Cloud Server cannot provide external services and will be completely removed from the system in a short time.
Can a deleted ECS be activated again?
The deleted Elastic Cloud Server will only stay in the Elastic Cloud Server list of the management control center for a short period of time, and the system will remove it completely later, so it cannot be used to restore the system and data. You can purchase an Elastic Cloud Server with the same specifications again.
Do I need to shut down when upgrading CPU, memory, or bandwidth?
When upgrading CPU and memory, you need to shut down for upgrading, but when upgrading bandwidth, it is not necessary to shut down. For details about how to upgrade data disks and system disks, see EVS Product Description.
Can I install or upgrade the operating system myself?
Elastic Cloud Server requires the use of an operating system provided by us or created based on our operating system, which cannot be added or upgraded on its own, and the operating system can be patched.
Note: If you need to upgrade the major version of the operating system, such as upgrading from CentOS 7.2 to CentOS 7.3, please use the One-click Reinstall function provided by eSurfing Cloud platform.
What is the login username for Elastic Cloud Server?
The username is root for Linux OS and Administrator for Windows OS. The password is the one set by the user when creating Elastic Cloud Server.
Does the operating system have a graphical interface?
The Windows OS uses desktop management, while the Linux OS uses command line. Users can set up their own graphics management if needed.
Do I need to pay for reinstalling the operating system?
The reinstallation of the operating system provides the function of reinstalling the system from the original image at no additional cost.
What should I do if I find that the Reinstall System button cannot be selected when reinstalling the operating system?
For the running Elastic Cloud Server, the operating system cannot be reinstalled.
You need to shut down before reinstalling the system.
Can I choose another operating system when reinstalling the operating system?
Yes.
When I use the free command to check the memory of Elastic Cloud Server, why does it not match the actual memory?
Issue Description:
After successfully creating the Elastic Cloud Server, use the free - m command to query the memory size, but the query result does not match the actual configuration, which is smaller than the configuration at the time of creation.
Example:
Assuming that the actual memory size configured when creating the Elastic Cloud Server is 4194304KB (i.e. 4096MB). After creation, use the free - m command to query the memory size, and the echo message is as follows:
[root@localhost ~]# free -m
total used free shared buff/cache available
Mem: 3790 167 3474 8 147 3414
Swap: 1022 0 1022
You can see that the memory is only 3790MB, which is smaller than the actual 4096MB.
However, when using the dmidecode - t memory command to view the actual hardware memory size, the echo message is as follows:
[root@localhost ~]# dmidecode -t memory
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.8 present.
Handle 0x1000, DMI type 16, 23 bytes
Physical Memory Array
Location: Other
Use: System Memory
Error Correction Type: Multi-bit ECC
Maximum Capacity: 4 GB
Error Information Handle: Not Provided
Number Of Devices: 1
Handle 0x1100, DMI type 17, 40 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: Unknown
Data Width: Unknown
Size: 4096 MB
Form Factor: DIMM
Set: None
Locator: DIMM 0
Bank Locator: Not Specified
Type: RAM
Type Detail: Other
Speed: Unknown
Manufacturer: QEMU
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Rank: Unknown
Configured Clock Speed: Unknown
Minimum Voltage: Unknown
Maximum Voltage: Unknown
Configured Voltage: Unknown
You can see that the memory size viewed by using dmidecode -t memory is consistent with the actual configuration.
Possible reason:
First, the system initializes the relevant devices during startup, which occupies memory. When the kernel starts, it also occupies part of memory. The memory occupied by kdump can be set by yourself, and if you do not have special requirements, do not modify the memory size occupied by kdump.
Second, the free -m command queries the available memory of the Elastic Cloud Server, while the dmidecode -t memory command queries the actual hardware memory size.
Therefore, the memory size queried using the free -m command is smaller than the actual size, which is normal and not a problem.
The same problem exists with physical servers.