Security

How can I debug my lea client for checkpoint?

jbsplunk
Splunk Employee
Splunk Employee

Does anyone know of a good way to debug problems with the checkpoint lea client? I've been having trouble getting my configured.

1 Solution

Chubbybunny
Splunk Employee
Splunk Employee

Yes! you'll want to add a shell variable that calls OPSEC debugging when the lea_loggrabber client is called.
First, set the OPSEC debug level:

OPSEC_DEBUG_LEVEL=3; export OPSEC_DEBUG_LEVEL

Then run the splunk lea_loggrabber.sh script manually:

SPLUNK_HOME=/opt/splunk/ ./lea-loggrabber.sh 

The debug output is very verbose so you may want to send the output to a file for splunk support to review.

If you need to dive deeper into the problem, on the Checkpoint Manager you can also enable OPSEC debugging.

% fw debug fwm on OPSEC_DEBUG_LEVEL=9

The debug file is located at $FWDIR/log/fwm.elg

To stop the FWM debug, execute:

% fw debug fwm off OPSEC_DEBUG_LEVEL=1

View solution in original post

Chubbybunny
Splunk Employee
Splunk Employee

Yes! you'll want to add a shell variable that calls OPSEC debugging when the lea_loggrabber client is called.
First, set the OPSEC debug level:

OPSEC_DEBUG_LEVEL=3; export OPSEC_DEBUG_LEVEL

Then run the splunk lea_loggrabber.sh script manually:

SPLUNK_HOME=/opt/splunk/ ./lea-loggrabber.sh 

The debug output is very verbose so you may want to send the output to a file for splunk support to review.

If you need to dive deeper into the problem, on the Checkpoint Manager you can also enable OPSEC debugging.

% fw debug fwm on OPSEC_DEBUG_LEVEL=9

The debug file is located at $FWDIR/log/fwm.elg

To stop the FWM debug, execute:

% fw debug fwm off OPSEC_DEBUG_LEVEL=1
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...