Alternatively, use the Kernel Debug Procedure with Connection Life Cycle.
Important - In cluster, perform these steps on all the Cluster Members in the same way.
Step |
Description |
---|---|
1 |
Connect to the command line on the Security Gateway. |
2 |
Log in to the Expert mode. |
3 |
Reset the kernel debug options:
|
4 |
Reset the kernel debug filters:
|
5 |
Configure the applicable kernel debug filters. |
6 |
Allocate the kernel debug buffer for every CoreXL FW instance:
|
7 |
Make sure the kernel debug buffer was allocated:
|
8 |
Enable the applicable debug flags in the applicable kernel modules:
|
9 |
Examine the list of the debug flags that are enabled in the specified kernel modules:
|
10 |
Start the kernel debug:
|
11 |
Replicate the issue, or wait for the issue to occur. |
12 |
Stop the kernel debug: Press CTRL+C |
13 |
Reset the kernel debug options:
|
14 |
Reset the kernel debug filters:
|
15 |
Analyze the debug output file:
|
Example - Connection 192.168.20.30:<Any> --> 172.16.40.50:80
... ... Replicate the issue, or wait for the issue to occur ... ... ... ... ... Press CTRL+C ... ...
|