Technical issues

  1. Access to the IPMI
  2. Network Settings
  3. Equipment replacement
  4. Application for server repair
  5. Diagnostics
  6. Hard Drives
  7. Cooling system
  8. Memory

Access to the IPMI

Step 1. To access the IPMI need to open the billing.

Step 2. You must select the tab with a list of your servers, «Products/Services» → «Dedicated servers». Then select the desired server and click "To panel".

Step 3. We open the server control panel. Here we must choose "Servers", then select the desired server, and press the «KVM» button in the upper right corner.

Step 4. We get all the necessary information (IP address, login and password) for authorization in the IPMI control panel in this tab.

Step 5. Click the link, enter your login and password, click «Login».

Step 6. We logged into the IPMI control panel.

Now download «launch.jnlp» java file. Click on the «Remote Console Preview» image

Step 7. Start the downloaded file (this requires current version of Java Java). Finally, we are in the KVM.

Step 8. When you work with KVM, you may need to load the operating system image (iso) from CD / DVD. To do this, open the tab: «Virtual Media» → «Virtual Storage» at the KVM.

Opens «Virtual Storage 1.2 r2».

Step 9. Mount an image * .iso. To do this select field «Logical Drive Type» then select the item «ISO File» and select in the field «Image File Name and Full Path» the desired file (located on your computer). Then you need to click «Plug in» and «OK» («Virtual Storage» box closes).

Step 10. Boot from the virtual CD-ROM. Now we need to restart the server: «Power Control» → «Set Power Reset». Press «F11» immediately after the boot of bios to activate «BOOT MENU» (choice of the server upload sources). Select the item «ATEN Virtual CDROM» in the appeared menu.

Network settings

The subnet mask (for each subnet):
For any IP address, the gateway has the last octet .1
Thus gateway IP address (for example) it will be:
DNS servers:

Equipment replacement

All our servers required to undergo testing before they go to customers. But unfortunately servers, as well as any other equipment sometimes still break down.

Application for server repair

Replacing the server component is produced after customer handling to the technical support.

If your skills are not enough to identify a faulty component, you must specify in the application:

  • Faulty server (select from the drop down list of products / services)
  • The type of components (hard drive / RAM ...)
  • If the hard disk defective, specify its serial number
  • Log of the operating system, a screenshot, for hard disks - SMART status and etc., showing the existence of the problem, as well as indicating the faulty component.

If you can not clearly identify the cause of the problem, see "Diagnostics". Check the temperature of the CPU, hard disks, the status of attributes SMART. If after this you can identify the problem, describe the problem as defined above. If you can't clearly define the problem, create an application in Your Account, which indicate:

  • Faulty server (select from the drop down list of products / services)
  • The installed operating system
  • Maximum current technical description of the problem
  • Log the operating system screenshot and etc., indicating the existence of the problem (if available)


According to statistics, the main cause of problems are hard drives, memory, motherboards, power supplies, cooling system (cooler on the processor, fans). Processors break down much less often than the other components.

In order you do not lose data in the event of failure of the hard drive, we offer a server with two identical hard drives. All operating systems drives are used in software RAID 1 by default. In such a case, any data is written to two disks, so the failure of one disk does not lead to loss of data.

It's easy to diagnose the problems with hard drives, memory and server cooling system.

Hard Drives

Modern drives have self-diagnostic system (SMART), allows us to estimate the condition of the disc. To determine the parameters of SMART, we offer the use the utility smartctl.
The format of the call of this utility:

smartctl –a

In Linux command-line could be, for example:

smartctl -a /dev/sda

For FreeBSD

smartctl -a /dev/ad1

This utility displays a large amount of information, including a table with columns:


Check that for the parameters

Reallocated Sectors Count
Seek Error Rate
Uncorrectable Sector Count

value of the VALUE column is higher than value of THRESH column. The drop of any of the parameters below the permissible value is a reason to replace the drive.

Also notice the option Temperature_Celsius, column RAW_VALUE. This parameter indicates the current temperature of the disk. If the temperature rises above 45 degrees, then the server cooling system may be faulty. You should inform Technical Support about it.

Note that you must check all the hard rrivers installed in the server.

Cooling system

If the CPU temperature reaches 85 degrees Celsius or the temperature of the motherboard has reached 50 degrees, the cooling system is faulty, it's necessary to disassemble the server to find the fault.If any of the hard disks is warmed to 45 degrees, it is also likely to indicate a fault of cooling.
Checking the temperature of the components in the BIOS is the easiest way to find fault.

In FreeBSD, you can check the temperature of the CPU as follows:

kldload coretemp
sysctl -a | grep temperature

In Linux, you can check the temperature of the CPU as follows:
Install the necessary service packs

yum install lm_sensors hddtemp

Answer yes to all questions. Then run


After that, for the CPU temperature, you can run


You can check the temperature of your hard drive by calling

hddtemp /dev/sd*


You can test the RAM of your own server with the help of the program Memtest. To run the RAM test you should select the desired DSManager server, click on the icon to install the operating system, and then select Memtest. Memtest does not change the contents of the hard disk. However, note that triggered the installation of the operating system causes a hardware reset of the server. Therefore, exit the current operating system before you run memtest.

You can test the RAM by the KVM. The appearance of any fault in the RAM test is a reason to write an application for the replacement of RAM. Do not forget to attach a screenshot of the program memtest.