opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
161 / 193
The created user monitoring will be stored with its encrypted password at the /etc/opsi/passwd and is not a user
which may be used to login at a shell. In fact it is no real Unix user.
You have to create this user only on your config server, even if you have multiple depots.
At your Nagios server you should mask the user and password by making an entry at the /etc/nagios3/resource.cfg.
This should look for example like this:
$USER2$=monitoring
$USER3$=monitoring123
The number behind $USER may vary. If this configuration was not used before, there should be only $USER1$ be
used. According to what you are using here, you might have to change the other examples in this manual.
20.5.2 opsi-Nagios-Connector configuration directory
To make the maintenance of the Nagios configuration easier, we recommend to put all opsi nagios connector related
configuration files in one separated place.
So just create below /etc/nagios3/conf.d a new directory named opsi for these configurations.
The configuration files we will place in this directory are:
• Nagios Template: opsitemplates.cfg
• Hostgroups: opsihostgroups.cfg
• Server Hosts: .cfg
• Commands: opsicommands.cfg
• Contacts: opsicontacts.cfg
• Services: opsiservices.cfg
All the client configuration files we recommend to put in sub directory of this place. Therefore you create below
/etc/nagios3/conf.d/opsi another directory named clients.
20.5.3 Nagios template: opsitemplates.cfg
Using templates is a standard functionality of Nagios which will not explained here. The main advantage is that it
makes the single configuration files smaller and easier to read (and write).
Inside of the templates we use some Nagios custom variables for often used values. According to the fact, that the
most checks have to run on the opsi config server, we will define the name and port of the config server as such a
custom variable:
_configserver configserver.domain.local
_configserverurl 4447
You will find this below in the template definitions.
These custom variables may later on be referenced by the Nagios macros: $_HOSTCONFIGSERVER$ and
$_HOSTCONFIGSERVERPORT$. (These macros have leading HOST in their name, because they are defined inside of
a host definition).
For more details on variable and macro take look at your Nagios documentation.
Now the first file we create in /etc/nagios3/conf.d/opsi is the template definition file opsitemplates.cfg.
This file may hold different templates. Every template is created according to the following patter (which contains
comments for better understanding):