You need to run a kernel debug over a longer period of time as the problem occurs only once or twice a week. Therefore you need to add a timestamp to the kernel debug and write the output to a file…

The correct answer is B. fw ctl kdebug -T -f -o filename debug. To start collecting the kernel debug into cyclic output files: On the Security Gateway / each Cluster Member, run in the Expert mode: fw ctl kdebug [-k] -T -f -o /<Path>/<Name of Output File> -m <Number of Cyclic Files> [-s <Size of Each Cyclic File in KB>]

Troubleshoot R81.20 Security Gateway Issues

Question

You need to run a kernel debug over a longer period of time as the problem occurs only once or twice a week. Therefore you need to add a timestamp to the kernel debug and write the output to a file. What is the correct syntax for this?

Options

Afw ctl debug -T -f > filename debug
Bfw ctl kdebug -T -f -o filename debug
Cfw ctl kdebug -T > filename debug
Dfw ctl kdebug -T -f > filename.debug

How the community answered

(54 responses)

A
6% (3)
B
83% (45)
C
9% (5)
D
2% (1)

Explanation

To start collecting the kernel debug into cyclic output files: On the Security Gateway / each Cluster Member, run in the Expert mode: fw ctl kdebug [-k] -T -f -o /<Path>/<Name of Output File> -m <Number of Cyclic Files> [-s <Size of Each Cyclic File in KB>]

Topics

#fw ctl kdebug#kernel debug#command syntax#debug output

Community Discussion

No community discussion yet for this question.

Full 156-587 Practice