SMO Image Cloning

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

Background

You can use SMO 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 Scalable 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 Scalable 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 cluster configuration image auto-clone state

Shows the current auto-clone state.

set cluster configuration image auto-clone state {on | off}

Controls the auto-cloning state:

  • on - enabled

  • off - disabled

Note - SMO Image Cloning does not support Gaia snapshot (the included fcd).

Working with image's MD5 in Gaia gClish:

Command

Instructions

show cluster configuration image md5sum

Shows the MD5 of the local image.

set cluster configuration image md5sum

Updates the MD5 of the local image.

This is done automatically during reboot, admin UP, and hotfix installation.