I have a Checkmk instance with 3 sites. I would like to merge these and have therefore updated the agents and sites to the current 2.1.0p47 version. Now I want to merge the sites before I update further. The servers are all Linux Debian Server 10 or 11 and run on different hosts.
I also have servers that only have an internal IP. So I have the case that two servers are not directly accessible for my Checkmk server. Is it possible to set up a proxy jump with ssh?
Regarding ssh jump:
as you can define any command in the individual host check command rule, you could use either a ssh jump or also port forwarding if that works within your network policy
Thanks for your answer @gstolz, the merging of the sites works so far. I only have problems with the two hosts that are not directly accessible from the Checkmk server.
So I can make a config file in the .ssh directory of OMD in which I also have the SSH keys in which I define a jump via another server that has access in the event of these servers. This server must then also receive the key so that it can forward this?
I’d have to look into ssh jump host configuration details but let’s say it like this: checkmk will just use your ssh binary + .ssh config, so anything you can get working as the Linux CLI user of your site, will work from within checkmk as well.
that worked with a simple SSH config I was able to establish a connection. Now the checks work and the server is also on the correct site. Unfortunately, of course, the PING does not work and therefore the server is displayed as DOWN, even if all checks work. Do you know a solution for this?
For this purpose the rule “Host Check Command” exists.
Usually the host state is determined by some version of PING. If that is not possible you can either set it to “always up” or to the status of some service (and other things).
In our environment we use the status of the Checkmk Agent. If that is green, the host is considered UP. In every other case the host is considered DOWN.