Introduction

Purpose of the document

The purpose of this document is to provide the user with basic information on the use of a dedicated server provided in the IaaS model by Atman, with particular reference to administrative access to the device and the use of remote management interfaces such as IPMI, XCC or other tools provided as part of a given hardware configuration.

The manual is intended to help the user to perform the basic steps involved in getting started with the service, including in particular:

  • finding the access data for the server,

  • logging into the relevant administrative panels,

  • gaining remote access to the server console,

  • performing basic administrative operations,

  • identification of the most common login and access problems.

The document is practical and operational in nature. It has been prepared in such a way that the user can independently go through the most important steps related to accessing the server and its basic operation.

Scope of instructions

The manual covers the basic steps to be taken by the user after launching a dedicated server service in the IaaS model.

The scope of the document includes, in particular:

  • access to information about the service in the Atman Customer Zone,

  • location of technical and access data to the server,

  • logging into the server management interface,

  • use of remote console mechanisms,

  • basic operations available via IPMI/XCC, such as:

    • server status overview,

    • launching a remote console,

    • server restart,

    • switching the server on or off,

    • ISO image mounting, if available,

  • security rules for the use of access data,

  • basic diagnostic measures in the event of access problems.

The manual does not replace the server manufacturer’s documentation or the documentation of the operating system installed on the server. It also does not cover the detailed configuration of applications, system services, client-side security policies or operating system administration after logging into the server.

For whom the manual is intended

The manual is intended for customers using the dedicated server service in the IaaS model at Atman and for those responsible on the customer side for the technical administration of the server environment.

In particular, the document is aimed at:

  • system administrators,

  • IT infrastructure administrators,

  • application maintenance teams,

  • persons responsible for the implementation or migration of services to a dedicated server,

  • customers starting to use Atman’s IaaS services,

  • users who need access to the server console beyond the standard access via SSH, RDP or other system services.

The document can also be helpful for non-technical people who manage the service from an organisational perspective and need a basic understanding of where access data is located and how to communicate it to the right technical people.

To perform some of the activities described, you may require the appropriate permission level in the Atman Customer Area and basic knowledge of server administration.

Brief description of the dedicated server service

A dedicated server in the IaaS model is a service whereby a physical server is made available to a customer for the customer’s exclusive use. Unlike shared environments, the server’s hardware resources - such as processors, RAM, disk space and network interfaces - are assigned to a single client and are not shared with other users.

Dedicated server service enables the running of operating systems, business applications, databases, virtualisation environments, backup systems, e-commerce platforms, AI/HPC solutions and other services requiring high performance, resource predictability and control of the environment.

As part of the service, the customer receives access to a server infrastructure maintained in an Atman data centre. The server is installed, powered, cooled and connected to the network according to the parameters of the purchased service. The customer is given the ability to remotely manage the server, including access to the operating system and, depending on the configuration, to a hardware management interface such as IPMI or XCC.

The hardware management interface allows selected administrative actions to be performed independently of the operating system. This allows the user to access the server console, perform a reboot, check the basic status of the device or perform an operating system installation using remote installation media.

A dedicated server in the IaaS model combines the features of a classic physical infrastructure with a service model. The customer benefits from the dedicated hardware without having to purchase it, maintain it in their own server room and provide power, cooling and physical availability of the infrastructure themselves.