There are some things to consider in preparation of for migrating your checkmk server. There are also several scenarios regarding migration.

...

Scenario: Change the IP address of your Checkmk server

Things to consider

1. Agent Updater

   • If the update server is not configured as a DNS name, make sure to update the IP address of the update
   server 
   • server prior
    
   • to migration.
   Make sure
   • Ensure your TLS certificates
   do
   • match the new server configuration and are baked into the agent.
   • Verify
   ,
   • that all agents are up-to-date!
     
     

2. Agent Access

   • Checkmk Agent: Ensure your IP whitelist contains both the old and new IP of the server prior  to the migration (Rule: Allowed agent access via IP address (Linux, Windows))
   • SNMP: Ensure ACL on SNMP devices will allow the new IP
   • TLS Encryption: If you have registered to the Checkmk server using an IP/DNS name, you have to make sure this either remains the same
   ,
   • or you have to re-register
     
     

3. Firewall

   • Make sure your central firewall(s) allow all necessary traffic (See the following article for reference: Network ports used by Checkmk)
     
     

4. Routing

   • If custom routes have been configured on the checkmk server, make sure to check and, if necessary, adapt them.
     
     

5. Webserver

   • If the server name changes, you need to
   aquire
   • acquire new certificates. See also the section Agent Updater!
     
     

6. Mailserver

   • Make sure your mail server is still accessible from the new IP
     
     
7. Eventconsole

   Event Console

   • If your server acts as a target for SNMP traps or remote syslog messages, you might have to change the target IP/DNS name on the sending devices.