Study guide

7.7 fw monitor, fw ctl zdebug, and cpview

CCSA R82 — Check Point Certified Security Administrator Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Architecture

1.1 CCSA R82 Exam Facts 1.2 Standalone vs Distributed Deployment 1.3 Gaia OS, clish and expert Mode 1.4 The SmartConsole Suite 1.5 Secure Internal Communication and the ICA

2 Chapter 2: Security Policy & Access Control

2.1 Policy Packages 2.2 Access Control Policy Overview 2.3 Ordered Layers and First-Match Evaluation 2.4 Inline Layers and Nested Rule Matching 2.5 Access Rules: Fields, Actions, and Track Options 2.6 Implied Rules and Global Properties 2.7 Stealth and Cleanup Rules: Placement and Best Practice 2.8 Hit Count and Policy Install Workflow

3 Chapter 3: Network Address Translation (NAT)

3.1 NAT Overview in Check Point 3.2 Hide NAT (Many-to-One) 3.3 Static NAT (One-to-One) 3.4 Automatic vs Manual NAT and Proxy ARP

4 Chapter 4: Identity Awareness

4.1 Identity Awareness Overview 4.2 Active Directory Query 4.3 Identity Collector 4.4 Identity Agent 4.5 Captive Portal and Access Roles

5 Chapter 5: Threat Prevention

5.1 Threat Prevention Overview 5.2 Application Control 5.3 URL Filtering 5.4 Intrusion Prevention System (IPS) 5.5 Anti-Bot and Anti-Virus 5.6 Threat Emulation and Threat Extraction 5.7 TP Profiles, Best Practice, and Ordered Layers for TP 5.8 HTTPS Inspection

6 Chapter 6: ClusterXL — High Availability, Load Sharing, and Failover

6.1 ClusterXL Overview: Why Clustering, HA vs Load Sharing 6.2 High Availability Mode: Active/Standby, Primary Up vs Active Up 6.3 Load Sharing Modes: Multicast, Unicast (Pivot), and Traffic Distribution 6.4 Cluster Control Protocol (CCP) and State Synchronization 6.5 Failover, Cluster States, and Troubleshooting with cphaprob

7 Chapter 7: VPN, Logs, and Troubleshooting

7.1 Site-to-Site IPsec VPN 7.2 Remote Access VPN 7.3 Encryption Domains and VPN Communities 7.4 Mobile Access Blade 7.5 Logs, Monitor, and SmartEvent 7.6 Backups, Snapshots, and Migrate Export 7.7 fw monitor, fw ctl zdebug, and cpview 7.8 cpinfo and Common Issues

7.7 fw monitor, fw ctl zdebug, and cpview

Key Takeaways Explain This Topic AI

fw monitor captures at Chain Module inspection points (i/I/o/O plus e/E for VPN), not just at the interface like tcpdump.

fw ctl zdebug + drop prints dropped packets with the kernel drop reason in real time; use cpview first for an overview.

Only one fw monitor instance can run at a time; stop it with Ctrl+C or fw monitor -U from another shell.

fw ctl zdebug + drop and fw monitor -F share SecureXL/sim filter settings; running both can break the -F filter.

Last updated: July 2026

Packet Capture and Debug Tools

When a connection is being dropped and you cannot tell from the log why, Check Point provides three layered tools: fw monitor for packet capture at inspection points, fw ctl zdebug for kernel-level drop reasons, and cpview for a real-time performance and drop-statistics overview. CCSA questions test which tool to start with in each scenario and the key syntax of each.

fw monitor

fw monitor captures packets at the Chain Modules — the inspection points inside the firewall VM. Unlike tcpdump (which captures only at the interface), fw monitor can show a packet at multiple points in the inspection chain, which is what lets you tell whether a packet was dropped before or after NAT, before or after VPN encryption, and so on.

The four core inspection-point masks:

  • Mask Position
  • i Pre-Inbound — before the FW VM
  • I Post-Inbound — after the FW VM
  • o Pre-Outbound — before the FW VM
  • O Post-Outbound — after the FW VM

Plus e (pre-VPN encrypt) and E (post-VPN encrypt) for VPN troubleshooting. A packet seen at i but not I was dropped by the inbound inspection; seen at I but not o was dropped between inbound and outbound; seen at o but not O was dropped by outbound inspection or after.

  • Common examples: fw monitor -e "accept;" -o /var/log/fw_mon.cap
  • fw monitor -e "host(192.168.1.1), accept;" -o /var/log/fw_mon.cap
  • fw monitor -e "port(80), accept;" -o /var/log/fw_mon.cap
  • fw monitor -F "0,0,8.8.8.8,0,0" -o /var/log/fw_mon.cap # accelerated + non-accelerated
  • fw monitor -T -e "accept;" -o /var/log/fw_mon.cap # with timestamps

-e takes an INSPECT filter and captures non-accelerated traffic. -F (capital) captures both accelerated and non-accelerated traffic using a simple srcPort,srcIP,dstPort,dstIP,proto filter. -o writes to a binary file you can read back with Wireshark (after converting with fw monitor -o or using the capinf / cppcap tools). Only one fw monitor instance can run at a time. Stop with Ctrl+C or fw monitor -U from another shell.

fw ctl zdebug

fw ctl zdebug is a wrapper around fw ctl debug that simplifies running kernel debugs. The flagship use case is dropped packets with reasons : fw ctl zdebug + drop # all drops with reasons

  • fw ctl zdebug + drop | grep 192.168.1.1 # drops for a specific IP
  • fw ctl zdebug + packet # packet path
  • fw ctl zdebug + conn # connection table
  • fw ctl zdebug + xlate # NAT table
  • fw ctl zdebug + sync # ClusterXL state sync

Under the hood it runs fw ctl debug -buf 1024 , enables your flags, runs fw ctl kdebug -f , waits for Ctrl+C, then runs fw ctl debug 0 . The 1024 KB buffer is small — for production-volume debugging use the full fw ctl debug commands with a larger buffer. After Ctrl+C you may need to run fw ctl debug 0 manually to fully reset the debug state. Leaving debug on after you finish is one of the most common performance degradation causes — always reset.

Important caveat : fw ctl zdebug + drop and fw monitor -F share the same SecureXL/sim debug filter settings. If you run both at the same time the -F capture can become unfiltered . If you must run both, start zdebug first, then fw monitor -F , and stop fw monitor -F first.

cpview

cpview is a real-time performance and drop-statistics monitor. It shows CPU, memory, network interfaces, connection counters, and — most importantly for troubleshooting — the drop statistics occurring on the gateway, broken down by reason code. Best practice is to start with cpview for a quick look at where packets are being dropped, then drill down with fw ctl zdebug + drop for the per-packet reason, then use fw monitor to confirm the exact inspection point. cpview is non-invasive and safe to leave running during a troubleshooting session.

Related Tools

Tool Use

tcpdump / cppcap Interface-level capture at positions i and O ; cppcap is the newer recommended replacement for tcpdump

  • easy_debug R81.10+ debug wizard that runs common debugs without knowing the full CLI syntax
  • fw ctl chain Shows Chain Modules and their positions — useful when designing a fw monitor filter
  • fwaccel off/on Disable/enable SecureXL — affects what fw monitor and tcpdump can see
  • vpn tu / vpn debug VPN-specific tunnel and debug utilities
  • When SecureXL Acceleration Matters

SecureXL-accelerated connections are offloaded to a fast path that bypasses the FW VM, so fw monitor with -e will not see them. To capture accelerated traffic you either use -F , disable SecureXL temporarily with fwaccel off (then back on with fwaccel on ), or look at the SecureXL drop counters in cpview . Disabling SecureXL in production impacts performance — only do it briefly during a debug window.

Exam Traps

Start with cpview for drop statistics, then fw ctl zdebug + drop for reasons, then fw monitor for the inspection point. Picking the wrong starting tool is a common wrong-answer pattern.

Only one fw monitor instance at a time.

fw ctl zdebug + drop shows drop reasons; fw monitor shows packet positions — they answer different questions.

Running fw monitor -F and fw ctl zdebug + drop together can break the filter; stop fw monitor -F first.

Forgetting to reset debug ( fw ctl debug 0 ) is a common cause of unexplained gateway slowdowns after a debug session.