opsi manual opsi version 4.0.2 - opsi Download - uib

opsi manual opsi version 4.0.2
• The time since last seen:
The time since last seen results to:
– OK if the client has bee seen less or equal then 30 days before.
– Warning if the client has bee seen more then 30 days before.
This check may used in different variants, here is the simplest one, which includes all software packages:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkClientStatus -c opsiclient.\
domain.local
As variant it is possible to exclude products from the check. For example:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkClientStatus -c opsiclient.\
domain.local -x firefox
157 / 193
In the example above the product firefox was excluded from the check. So this check would not switch to critical
because the last action on firefox reported a failure.
Check: opsi-check-ProductStatus
An other target of the opsi Nagios connector is the software roll out monitoring by viewing to single product or a
group of products.
The result of the following checks is determined by the following states:
The software roll out state results to: * OK if the software is installed at the in the same product and package version
which is available at the server and no action request is set. * Warning if the software is installed in version that is
different to the servers version or if any action request is set. * Critical if there is a failed reported by the last action.
This checks has many variants and is so very flexible. The bast way to explain these variants are examples.
The simplest variant check one product on all clients. Here you have to give the product as the opsi productId.
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkProductStatus -e firefox
In a simple one server opsi environment, this check is all you need to check the state of the product firefox on every
client.
You will get the information how many clients are in Warning and in Critical states.
To get the information which clients exactly have the problems, you should call the check in the verbose mode:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkProductStatus -e firefox -v
An other variant is, that you may exclude a client from the check.
//// produkt muss angegebn werden ?! ////
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkProductStatus -e firefox -x \
client.domain.local
In a opsi environment with multiple depot servers you have to use additional options to check also the clients that are
not assigned to the config servers depot. If you have multiple depots, you may give the depots name as parameter:
check_opsi -H configserver.domain.local -P 4447 -u monitoring -p monitoring123 -t checkProductStatus -e firefox -d \
depotserver.domain.local
The reason is that the version of the software packages may differ between your depots. So every client has to be
checked against the versions at the depot where they are assigned to. An advantage is that can place the display of
the results to the depot server.
You may give instead of the depot servers name the keyword all which means all known depot servers. But this