u/ObjectiveLeather319

If you find this useful, please consider giving the original CheckMates post a like! 😊
Full post: https://community.checkpoint.com/t5/Firewall-and-Security-Management/VIDEO-Complete-Check-Point-Hardware-Diagnostic-Execution/m-p/280847#M106475

I believe many people have already run the Hardware Diagnostic, but I also believe many have never done it. Since I was performing a complete Hardware Diagnostic on a Quantum Force 9800 cluster that I will be deploying, I decided to record this video to help others by going beyond what is covered in the official guide.

In this video, I demonstrate the complete Hardware Diagnostic process using loopback connectors, show what happens if something is done incorrectly, and explain the entire procedure step by step.

ISSUE FOUNDED TO SAVE HW LOG: I also present an issue that I have observed on recent Quantum Force versions. I have installed Quantum Force 9000, 19000, and 29000 firewalls, and none of them have been able to save the Hardware Diagnostic results to the USB drive at the end of the test, even when using a FAT32-formatted USB drive as described in the documentation.

I hope this video is helpful. I used all of my English for it (haha), so if you find it useful, please leave a like on the video and give this post a Kudos to encourage me to continue creating and sharing this kind of content.

If you find this useful, please consider giving the original CheckMates post a like! 😊
Full post: https://community.checkpoint.com/t5/Firewall-and-Security-Management/JH-122-Broke-Mobile-Access-Rules/td-p/280832

I wanted to share an issue I observed after upgrading a production cluster to JH 122.

Note: I upgraded a production cluster from JH 91 to JH 122 (Latest) to evaluate the fixes included in the release, mainly because I am currently investigating an SD-WAN probes issue and JH 122 contains several relevant SD-WAN improvements.

The upgrade was performed carefully by installing the Jumbo only on the standby member first, while keeping the other member on JH 91 as a rollback option.

After failover, the customer started experiencing unexpected drops on long-standing Mobile Access rules that had been working without issues for years.

Rolling back to JH 91 immediately resolved the problem, with no other configuration changes required.

I'm sharing this only as an observation so others planning to install JH 122 in environments using Mobile Access can be aware and validate carefully.

Has anyone else seen similar behavior or others?

See complete on the u/checkpoint CheckMates:

https://community.checkpoint.com/t5/Check-Point-for-Beginners/Maestro-for-Beginners-Core-Concepts-Explained/ba-p/270872

New to Check Point Maestro? Here's a quick overview:

• MHO (Maestro Hyperscale Orchestrator) is an orchestration platform designed to deliver hyperscale network security. It is the device responsible for coordinating firewall, the MHO distributes and forwards traffic to the Security Gateway Modules, which perform inspection and enforcement.
• The guide also explains the principals concepts SGM, Uplink, Downlink, MAGG, Sync, Management ports, Single Site vs. Dual Site, and the differences between the MHO-140 and MHO-175, Real topology.

If you're starting with Maestro, preparing for deployment, or preparing for CCME, I hope this guide helps.

I posted a Full guide on CheckMates:

https://community.checkpoint.com/t5/Check-Point-for-Beginners/LOM-for-Beginners/ba-p/279099?cat=2

(If you find it useful, I'd appreciate a like on the CheckMates post! 🙂)*

Many Check Point administrators still don't configure LOM (Lights Out Management), even though it's one of the most valuable features for remote troubleshooting.

Think of it like Dell iDRAC: it provides out-of-band management, allowing you to access the appliance even if Gaia is down, frozen, or powered off.

In the guide I cover:

• What LOM is and why it matters.
• A real-world example where LOM saved a maintenance window.
• Initial configuration steps.
• Firmware update recommendations.
• Best practices for deploying a dedicated LOM management network.

Do you enable LOM on every deployment, or have you ever needed it during a critical outage? I'd love to hear your experiences.

I post the full technical write-up (including root cause and solution):
https://community.checkpoint.com/t5/Firewall-and-Security-Management/Policy-installation-failed-on-gateway-Error-code-0-2-200262/m-p/280259

If you find it useful, I'd appreciate a like on the CheckMates post. 🙂

During a migration from a Single Gateway to a Cluster, the first policy installation failed with:

Policy installation failed on gateway (Error code: 0-2-2000262)

After some investigation with TAC, the root cause was unexpected Gateway/Cluster objects added to the VPN column of several Access Control rules after using the SmartConsole Replace feature.

Removing those objects (leaving only the VPN Community or Any) immediately resolved the issue.

Has anyone else seen this error or found a different solution? I'd be interested in comparing experiences.