Last updated: April 26. 2018
1. Changing the language
During the basic configuration, you specified the language of your device. You can change this at any time, either via the console configuration or via the device settings in the web interface.
2. Changing the network configuration
During the basic configuration, you specified the network configuration of your device. You can change this at any time, either via the console configuration or via the device settings in the web interface. If you made an error when specifying the network configuration, the device may no longer be accessible via the network. In this case you can only correct the settings on the console.
3. Configuring host and domain names
Host and domain names serve to identify a computer in the network. When sending emails for example, these names are used to form the sender address. In addition, the configured host name is added as a source host to all log entries that are sent to a syslog server. This makes it easier to assign the entries.
4. Configuring name resolution
In most environments, DNS servers are used to translate IP addresses into host names and vice versa. Host names or FQDNs (Fully Qualified Domain Names) are frequently used for monitoring instead of IP addresses.
In order to use the name resolution on your device, you must configure the IP addresses of at least one DNS server in your environment. It is recommended to enter at least two DNS servers.
5. Configuring time synchronisation
The system time of the device is used for many purposes, such as for recording measurement data or writing log files. A stable system time is therefore very important. This is best ensured by using a time synchronisation service (NTP).
6. Forwarding syslog entries
Log messages are generated on the device by the operating system and some permanently running processes. They are initially written into a local log via syslog.
You can also send these entries to a central or higher-level syslog server where they can be evaluated, filtered or archived.
Select the item Syslog to configure the forwarding.
In the dialogue box that appears next, you can configure which protocol you wish to use for forwarding. Syslog via UDP is more widely used, but not as reliable as via TCP. So if your syslog server supports both protocols, it is recommended to use TCP.
7. Changing the default web page
If you access the host address of the device directly via the web browser without entering a path, you will be taken to the web interface of the device in the default setting. However, it is also possible for you to be forwarded directly to a monitoring instance of your choice.
8. Configuring outgoing emails
So that you can send emails from the device (in the case of events during monitoring for example), the forwarding of emails to one of your mail servers must be configured.
In order for the sending of emails to work, you must have at least configured the host address of your mail server as an SMTP relay server. This server will receive the emails from your device and forward them.
However, configuring the SMTP relay server is only sufficient as long as your mail server accepts emails via anonymous SMTP. If your mail server requires authentication, then you need to activate the appropriate login method under the item Authentication and indicate the access data of an account that can log onto the mail server.
If you do not even receive any emails after the configuration, it is worth taking a look at the system log of the device. All attempts to send emails are logged here.
The device itself can send system emails if there are critical problems (e.g. a job cannot be executed or a hardware problem has been detected). In order to receive these emails, you must configure an email address to which these emails are to be sent.
9. Changing access to Check_MK agents
A Check_MK agent is installed on the device and can only be queried by the device itself in the basic setting. You can use it to create an instance on the device and directly add the device to the monitoring.
It is also possible to make the Check_MK agent accessible from another device, meaning the device can also be monitored by another Check_MK system (e.g. in a distributed environment of a central server). For this purpose, you can configure a list of IP addresses that are allowed to contact the Check_MK agent.