After the SMO failover, Identity Collector connections are handled by both the old and new SMO

Product: Identity Awareness, Maestro HyperScale Firewall
Version: R81.20
OS: Gaia
Last Modified: 2026-07-23

Symptoms

• After SMO failover, End users cannot access resources located behind an Identity Awareness Gateway that is a Maestro Security Group. Identity information for the users is obtained by Captive Portal and/or Identity Collector.
• The $FWDIR/log/fw.elg. file for the relevant SMOs is flooded with error messages:
  session id not found in client_db, although ip was assigned to it
• In environments with Identity Collector, output of the asg_excp_conf command in the Maestro Security Group shows the correct IP Address(es) for Identity Collector.

Cause

After Single Management Object (SMO) failover, communication with Identity Collector is handled by both the old and new SMO. By design, connections matching the exceptions in asg_excp_conf remain on the same member after SMO failover. This causes mismatches in the Maestro kernel tables for Identity Awareness connections.

Solution

This problem was fixed. The fix is included starting from:

• Check Point R82
• Jumbo Hotfix Accumulator for R81.20 starting from Take 158

If you choose not to upgrade, Check Point can supply a Hotfix. Contact Check Point Support to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.

For faster resolution and verification, please collect CPinfo files from the Security Management Server and Security Gateways involved in the case.

Hotfix installation instructions:

Refer to sk168597 - How to install a Hotfix.

NOTE

This solution has been verified for the specific scenario described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Article Properties

Access Level: General
Status: Approved by TAC
Date Created: 2025-12-18
Last Modified: 2026-07-23