Checkpoint 156-836 - Check Point Certified Maestro Expert (CCME) R81.X

This command is used to set the number of sites in a Maestro environment, which can be either one or two. The number of sites determines the site-sync configuration and the failover policies for the Security Groups and the Security Group Members. The default value is one, and it can be changed only before the first Security Group is created.

References =

•Maestro basic setup documentation - Page 2 - Check Point CheckMates

•Check Point R81.10 for Scalable Platforms - Check Point Software

•CHECK POINT MAESTRO EXPERT

This is the correct answer because it follows the upgrade order and procedure specified in the R81.10 and R81.20 Administration Guides for Maestro environments. The MHOs are responsible for managing and synchronizing the SGMs, so they must be upgraded to the target version before the SGMs. However, the SGMs can be upgraded one by one or in batches, as long as they arecompatible with the MHOs. The upgrade process also supports Multi-Version Clustering, which allows different versions of SGMs to operate in the same Security Group with zero downtime.

References =

•Check Point R81.10 for Scalable Platforms - Check Point Software

•Check Point R81.20 for Scalable Platforms - Check Point Software

•CHECK POINT MAESTRO EXPERT

A Security Group (SG) requires at least one management port and one uplink port to function properly. The management port is used to connect the SG to the Maestro Hyperscale Orchestrator (MHO) and the customer’s management infrastructure, such as SmartConsole or SmartDomain Manager. The uplink port is used to connect the SG to the customer’s network infrastructure, such as switches, routers, or firewalls. The uplink port is also used to send and receive traffic from the customer’s network to the SG.

The SMO Master is the SGM that is responsible for managing the Security Group and communicating with the MHO. If the SMO Master fails, the Backup SMO Master, which is the SGM with the next lowest SGM ID, will take over the role of the SMO Master and ensure the continuity of the Security Group operations.

References = Maestro Expert (CCME) Course - Check Point Software, page 14; Check Point Accredited Maestro Expert - New exam a… - Check Point CheckMates, page 1.

"Asg stat -v" could be a part of the core diagnostic tools, providing valuable statistics and information for manual diagnostics.

References =

•Maestro Expert (CCME) Course - Check Point Software 3

•Check Point Maestro R81.X Administration Guide 1

•Check Point Maestro R81.X Getting Started Guide 2

3: https://www.checkpoint.com/downloads/training/ccme-maestro-expert-r81.10-course.pdf 1: https://www.manualslib.com/manual/2031661/Check-Point-Maestro-R80-20sp.html 2: https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_Maestro_GettingStarted/html_frameset.htm

In a Check Point Maestro environment, a splitter is used to divide a single high-speed port (e.g., QSFP or QSFP28) into multiple lower-speed ports (e.g., SFP or SFP+). However, a splitter cannot be used to connect a single port on an Orchestrator to the same Appliance, as this would not align with the purpose of a splitter, which is to expand connectivity to multiple devices or ports, not to loop back to a single device.

Exact Extract:

“A splitter is used to divide a single high-speed port on the Orchestrator (e.g., QSFP or QSFP28) into multiple lower-speed ports (e.g., SFP or SFP+). Splitters are typically used to connect a single Orchestrator port to multiple ports on an external switch or to multiple Appliances. However, a splitter cannot be used to connect a single Orchestrator port to the same Appliance, as this does not align with the splitter’s purpose of expanding connectivity.”

—Check Point Certified Maestro Expert (CCME) R81.X Courseware, Module 3: Dual Orchestrator Environment, Lesson 3.2: Connectivity Options, page 3-10

—Check Point R81 Maestro Administration Guide, Chapter 3: Working with Security Group Modules, Section: Connectivity, page 3-10

Explanation of Options:

A. To connect a single port on an Orchestrator to the same Appliance: Correct, as a splitter is not designed for this purpose and cannot be used to connect an Orchestrator port to a single Appliance.

B. To connect a single port on an Orchestrator to multiple ports on an external switch: Incorrect, as this is a valid use case for a splitter.

C. To connect a single port on an Appliance to multiple ports on the Orchestrator: Incorrect, as splitters can be used in configurations where an Appliance connects to multipleOrchestrator ports.

D. To connect a single port on an Orchestrator to multiple Appliances: Incorrect, as this is another valid use case for a splitter.

The correction rate is the percentage of connections that require correction by the correction layer, which is a mechanism that ensures that the traffic is processed by the correct SGM in the Security Group. The correction rate depends on the distribution mode (Layer 3 or Layer 4) and the traffic pattern. In some scenarios, such as when the traffic is asymmetric or when the distribution mode is Layer 4, the correction rate can approach 100 percent of all connections. This is not a problem, as the correction layer is designed to handle such situations without affecting the performance or availability of the Security Group1.

References = Maestro Expert (CCME) Course - Check Point Software, page 16.

SecureXL is typically used to accelerate trusted traffic, including non-F2F (face-to-face) traffic, through a secure, fast path.

References =

•SecureXL Fast Accelerator (fw fast_accel) for R80.20 and above 1

•SecureXL Fast Accelerator - Need to clarify packet flow 2

1: https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails= &solutionid=sk156672 2: https://community.checkpoint.com/t5/Security-Gateways/SecureXL-Fast-Accelerator-Need-to-clarify-packet-flow/td-p/114651

One of the possible reasons for the “Failed to get remote orchestrator interfaces” error message, when clicking on “Orchestrator” in WebUI, is that the remote orchestrator has no empty interfaces that can be assigned to a security group. This can happen if all the interfaces on the remote orchestrator are already part of configured security groups, or if the remote orchestrator has no physical interfaces at all. In this case, the WebUI cannot display the unassigned interfaces of the remote orchestrator, and shows the error message.

References

•Not able to see unassigned interfaces on checkpoint Orchestrator

•Maestro 140 not detecting Interfaces

•Maestro Expert (CCME) Course - Check Point Software, page