Server Details

The details page allows you to have all the significant information about a Server, and it includes where you can perform all the maintenance activities of the Server itself, such as managing the status and the multiple settings.

You can access the details page by clicking on the Server's name from the view page.

The details page is divided into several sections and appears as follows:

The control panel

At the top is the control panel, the only fixed element among the sections, it contains various information about the Server and more generic actions, in detail it can be divided as follows:

At the top left (n. 1) we have the Server's name and the link to return to the Server list, next to the right (n. 2) is the Server status and management actions, in order:

• The power on and off button
• The Rename operation
• The console

At the bottom is instead present the account of the Server's information, here you can find information such as:

• The Server name
• The operating system
• The plan
• The resources core, RAM, Disk, and if present GPU
• The relative Ipv4 and Ipv6
• The Server identification ID (to be communicated in case of platform malfunctions)
• The datacenter where the Server is located
• The creation date
• And finally the Server Version

Manage the status

By clicking the Power On or Off button you can change the status of your Server, once clicked a confirmation form will open, following confirmation the requested operation will be forwarded to the virtual Server.

Renaming a Server

From here you can also rename your Server, to do this simply click the "RENAME" button and enter the desired name, the use of empty spaces is not allowed and they will automatically be replaced with '-'.

Open the console

You can also open a remote console to the Server, for viewing the console the known open-source library noVNC is used.

Simply click on "CONSOLE", a new window will then appear attempting to connect to the virtual Server.

Warning

"v1" type Servers are being deprecated, therefore they do not support opening remote consoles

Resources

Immediately below the panel are several sections, including "RESOURCES", this section tracks , starting from the Server metrics, graphs on their performance thus allowing a quick analysis of the state of the machines.

It appears as follows:

There are charts on CPU, RAM consumption, and finally on Network traffic.

Warning

Metrics are not available for "v1" type Servers and for the "eCSGPU8" plan.

Templates

The template section allows the creation of Templates from already existing Servers.

The section appears as follows:

Creating a template is very simple, you need to click on "CREATE A TEMPLATE" and enter a description, once done, a template creation request will be forwarded to the Remote Server.

Warning

Template creation is not supported by "v1" type servers and for the "eCSGPU8" plan.

Interfaces

The network section allows you to connect our server of interest to a private network.

To do this, it is necessary to create at least one private network.

Interfaces are effectively network devices added to the virtual server and have the following characteristics:

• An interface requires at least one active VLAN to exist;

• Deleting all VLANs will result in the destruction of the interface;

• The creation and deletion of an interface will automatically restart the server;

Even though at least one VLAN is required to create an interface, knowledge of this technology is not necessary to use the private networks of our services.

Upon the addition of an interface, our web panel will automatically create a basic VLAN to allow the network to function.

The basic configuration will bring us to the following state:

To delve deeper into the subject of VLANs and get the most out of private networks, it is advisable to start with the following papers:

• VLAN;

• IEEE 802.1Q;

The section will appear as follows:

Adding an Interface

From this section, you can add as many interfaces as there are networks created, to do this, it is necessary to

click on "ADD AN INTERFACE" (n. 1) and select the desired network.

The creation will cause the machine to restart and upon completion, the MAC address

of the newly created interface will be visible.

Managing VLANs

From this section, you can also manage all the VLANs of an interface.

To do this, you can use the commands on the right.

Above the text field, there are special commands available to allow faster management

of our VLANs.

You can:

1. Select a single VLAN: "10" (if you want to select VLAN 10)

2. Select a range of VLANs: "10-20" (if you wish to select all VLANs from 10 to 20)

3. Send multiple commands in succession: "10,20-30" (if you wish to select VLAN 10 and all VLANs from 20 to 30)

You can also type "*" to automatically select all VLANs from 1 to 4094 or "!" to insert all VLANs

not yet created.

Creating a VLAN

To create an interface, you need to enter the selection command in the appropriate field and click "CREATE VLANS"(n. 2).

The VLAN will be created and will be available when the status (the circle on the left) turns green.

Attention

Attempting to create a VLAN with the same id as a recently deleted VLAN may cause an error.

To prevent this, wait for the delete action to be completed.

Removing a VLAN

You can remove one or more VLANs using the above commands and clicking "REMOVE VLANS"(n. 4).

Attention

To remove or modify a VLAN, it must be in a stable state, indicated by the dot next to the VLAN id.

Attempting to modify a VLAN in an unstable state will cause an error.

Changing the PVID

From here, you can also select a new PVID, to do this simply indicate a created VLAN and click

"PVID" (n. 3) to start the update process.

Configuring an Interface on the Server

Although all infrastructure operations are performed by our services, a simple manual configuration is necessary to enable our instances to communicate.

This allows the end user to have full control over their own network with the resulting flexibility.

It is therefore necessary to connect within your servers and configure the network address that we want to use for communication.

To do this, you can follow this quick example:

The example considers the case where you want to configure the network 192.168.1.0/24 (the choice of the network is entirely at the user's discretion).

The example refers to the following servers with the following IP addresses and MAC addresses, but it can be replicated with any server:

Server	IP We Want to Assign	MAC Address on the Panel
test-1	192.168.1.1	52:54:00:b9:27:40
test-2	192.168.1.2	52:54:00:a2:0e:c1

Both servers are connected to the network: "net000026"

First, it is necessary to access the console of these servers via the web panel or via SSH connection.

Once this is done, we must verify which interface is connected to the network. This can be done by comparing the MAC address visible from the panel with the MAC addresses within the individual server:

Analyzing the server "test-1"

ip link

You will have an output similar to the following:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000

    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000

    link/ether 10:00:ac:11:00:14 brd ff:ff:ff:ff:ff:ff

3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000

    link/ether 52:54:00:b9:27:40 brd ff:ff:ff:ff:ff:ff

By comparing the MAC addresses, it is possible to identify that the eth1 interface has the same MAC address as visible from the panel.

You can then configure eth1 to communicate with the server test-2:

First, you need to "turn on" the eth1 interface:

sudo ip link set dev eth1 up

Next, you need to indicate to our server that to reach the network 192.168.1.0/24, we must pass through eth1:

sudo ip route add 192.168.1.0/24 dev eth1

The last step is to specify which IP you want to use on this

interface (in the case of test-1 we insert 192.168.1.1):

sudo ip address add 192.168.1.1/24 dev eth1

Now, the same operations must be performed on test-2:

sudo ip link set dev eth1 up

sudo ip route add 192.168.1.0/24 dev eth1

sudo ip address add 192.168.1.2/24 dev eth1

Finally, the two servers will be able to communicate securely on their private network. This behavior can be tested

with the following command (assuming you are on test-1):

ping 192.168.1.2 -c 5

You will have the following result:

PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.

64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.369 ms

64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.464 ms

64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.419 ms

64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=0.453 ms

64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=0.455 ms


--- 192.168.1.2 ping statistics ---

5 packets transmitted, 5 received, 0% packet loss, time 11ms

rtt min/avg/max/mdev = 0.369/0.432/0.464/0.035 ms

Attention

These commands might not make the network configuration persistent. In other words, the configuration might be lost upon

the machine's reboot, especially if using tools like a network manager.

To prevent this, it is necessary to configure the network devices persistently.

Persistent configuration can vary from distribution to distribution and is not within the scope of this guide.

Settings

The settings are the most advanced section present on the details page, containing various subsections each with very specific purposes and it appears as follows:

Reserved Periods

One of the most interesting features present in the settings is surely the reserved periods:

Reserved periods ensure resource capacity and savings over time, reducing maintenance costs and blocking resources for a certain period of time.

Adding a Reserved Period

To do this you need to click on "ADD A RESERVED PERIOD NOW" and the following menu will be displayed:

Here you can select the period of time you want to reserve the specific Server for.

Doing so will make it impossible to delete the Server until the period expires.

The percentage of Discount varies based on the reserved period and the plan.

The Group

It is possible to assign a Server to a Group from the "Group" subsection.

To do this you need to create the desired group.

Subsequently, you can add a Server to the group from the following menu:

Isolation

Isolation is an advanced feature that allows two Servers to be forced to be located on different physical hardware, and it can be used directly within the configurator.

From this page, however, you can observe the isolation status of the specific Server:

On the left we have the Server we are analyzing while on the right the different Servers it is isolated from.

Technical Support

Activating a technical support plan is highly recommended as it allows you to receive assistance from Seeweb's expert engineers on your specific Server.

Server support plans are subject to a monthly pay-per-use, the destruction of the Server will not interrupt the billing of support in the current month of use.

There are several support plans:

The Unmanaged plan is activated by default and provides the minimum support guaranteed by Seeweb technicians. The Basic and Global plans guarantee greater benefits and higher priority to your requests.

The Proactive plan is the most important and complete among our support services and guarantees maximum priority to your requests. For more information, see Proactive

Destroy a Server

Finally, it is also possible to destroy a Server from the last section of the settings:

The operation is very simple, just click on the trash can and confirm your deletion.