SMO Image Cloning

Important - This section applies only to Scalable Platforms (Maestro and Chassis).

Background

You can use image cloning as a tool for cloning images from the Single Management Object (SMO) in a Security Group.

In addition to cloning the SMO version, this mechanism clones all installed Hotfixes, if there are any.

Best Practice: On Maestro, we recommend to use this tool when you add a new Maestro Security Appliance (an additional one, or a replacement for a failed one) to a Security Group On Chassis, we recommend to use this tool when you add a new SGM (an additional one, or a replacement for a failed one) to a Chassis.

When you activate the auto-clone feature, each Security Group Member updates these:

• MD5 of its local image during reboot

• Admin UP state

• Installed Hotfixes

If the MD5 of the local image is different from the MD5 of the SMO image, the Security Group Member clones the SMO image.

Working with image auto-clone in Gaia gClish:

Command	Instructions
show smo image auto-clone state	Shows the current auto-clone state.
set smo image auto-clone state {on | off}	Controls the auto-cloning state: on - enabled off - disabled

Note - Image cloning does not support Gaia Check Point security operating system that combines the strengths of both SecurePlatform and IPSO operating systems. snapshot (the included fcd).

Working with image's MD5 in Gaia gClish:

Command	Instructions
show smo image md5sum	Shows the MD5 of the local image.
set smo image md5sum	Updates the MD5 of the local image. This is done automatically on reboot, admin UP, and hotfix Software package installed on top of the current software version to fix a wrong or undesired behavior, and to add a new behavior. installation.