SMO Image Cloning
Background
You can use image cloning as a tool for cloning images from the Single Management Object Single Security Gateway object in SmartConsole that represents a Security Group configured on Quantum Maestro Orchestrator. Acronym: SMO. (SMO) in a Security Group
A logical group of Security Appliances that provides Active/Active cluster functionality. A Security Group can contain one or more Security Appliances. Security Groups work separately and independently from each other. To the production networks, a Security Group appears a single Security Gateway. Every Security Group contains: (A) Applicable Uplink ports, to which your production networks are connected; (B) Security Appliances (the Quantum Maestro Orchestrator determines the applicable Downlink ports automatically); (C) Applicable management port, to which the Check Point Management Server is connected..
In addition to cloning the SMO version, this mechanism clones all installed Hotfixes, if there are any.
|
Best Practice - We recommend to use this tool when you add a new |
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 |
---|---|
|
Shows the current auto-clone state. |
|
Controls the auto-cloning state:
|
|
Note - Image cloning does not support Gaia |
Working with image's MD5 in Gaia gClish:
Command |
Instructions |
---|---|
|
Shows the MD5 of the local image. |
|
Updates the MD5 of the local image. This is done automatically on reboot, admin UP, and hotfix |