Update the licenses for the new IP Address of the Security Management Server.
Download these licenses.
Take a backup of the Security Management Server. For Gaia OS, see the Gaia Administration Guide for your version. For SecurePlatform OS, see the SecurePlatform Administration Guide for your version.
Export the management database:
For R80.20 and higher: Use the "migrate_server export" command.
Move the OS backup and the management database export from this Security Management Server to a secure location. Compare the MD5 hash values values of the copied files to make sure they are not corrupted.
Connect with SmartConsole (R80 and higher) / SmartDashboard (R77.30 and lower) to the Security Management Server.
Edit the Security Management Server object:
Change the object's current IP Address to the new IP Address.
From the left tree, click Network Management (SmartConsole R80 and higher) / Topology (SmartDashboard R77.30 and lower) and change the IP Address on the interface to match. Otherwise, there will be a conflict.
Click OK.
Publish the session (in SmartConsole R80 and higher).
Close all SmartConsole / SmartDashboard windows.
Stop the Check Point services:
Connect to the command line on the Security Management Server.
Run: cpstop
Change the IP Address on the corresponding interface in the operating system:
In SecurePlatform, use the sysconfig command. See the SecurePlatform Administration Guide for your version.
Important: If Security Management Server has only one interface, you must connect through the serial console.
Install a license with the new IP Address.
Start the Check Point services. Run: cpstart
Connect with SmartConsole (R80 and higher) / SmartDashboard (R77.30 and lower) to the Security Management Server.
Install the database on all servers:
In SmartConsole (R80 and higher), click the Menu button > Install database > select all servers > click Install.
In SmartDashboard (R77.30 and lower), click the Policy menu > Install database > select all servers > click Install.
Notes:
Because the hostname (name of the Security Management Server) has not been changed, SIC communication should not be affected, as long as the routing is correct.
Make sure that there is connectivity between the Security Management Server and the managed Security Gateways by adding a rule that allows the new IP address and pushing policy to all managed Security Gateways.
On your DNS Server, map the host name of your Security Management Server to the new IP address.