Fortinet black logo

Handbook

Diagnose commands

6.0.0
Copy Link
Copy Doc ID 4afb0436-a998-11e9-81a4-00505692583a:490100
Download PDF

Diagnose commands

Diagnose commands are available for automation stitches, allowing you to do the following:

Testing

To test an automation stitch, use the diagnose automation test <automation-stitch-name> <log> command.

Example output

# diagnose automation test HA-failover

automation test is done. stitch:HA-failover

Enable and disable log dumping

To toggle between enabling and disabling log dumping, use the diagnose test application autod 1 command.

Example output

# diagnose test application autod 1

autod log dumping is enabled

# diagnose test application autod 1

autod log dumping is disabled

autod logs dumpping summary:

autod dumped total:0 logs, num of logids:0

Display settings

To display settings for all automation stitches, use the diagnose test application autod 2 command.

Example output

# diagnose test application autod 2

csf: enabled root:yes

total stitches activated: 2

stitch: Compromised-IP-Banned

destinations: all

trigger: Compromised-IP-Banned

actions:

Compromised-IP-Banned_ban-ip type:ban-ip interval:0

stitch: HA-failover

destinations: HA-failover_ha-cluster_25;

trigger: HA-failover

actions:

HA-failover_email type:email interval:0

subject: HA Failover

mailto:admin@example.com;

Display history

To display the history for all your automation stitches, use the diagnose test application autod 3 command.

Example output

# diagnose test application autod 3

stitch: Compromised-IP-Banned

local hit: 0 relayed to: 0 relayed from: 0

last trigger:Wed Dec 31 20:00:00 1969

last relay:Wed Dec 31 20:00:00 1969

actions:

Compromised-IP-Banned_ban-ip:

done: 0 relayed to: 0 relayed from: 0

last trigger:Wed Dec 31 20:00:00 1969

last relay:Wed Dec 31 20:00:00 1969

stitch: HA-failover

local hit: 1 relayed to: 1 relayed from: 1

last trigger:Thu May 24 11:35:22 2018

last relay:Thu May 24 11:35:22 2018

actions:

HA-failover_email:

done: 1 relayed to: 1 relayed from: 1

last trigger:Thu May 24 11:35:22 2018

last relay:Thu May 24 11:35:22 2018

Example output

# diagnose test application autod 2

csf: enabled root:yes

total stitches activated: 2

stitch: Compromised-IP-Banned

destinations: all

trigger: Compromised-IP-Banned

actions:

Compromised-IP-Banned_ban-ip type:ban-ip interval:0

stitch: HA-failover

destinations: HA-failover_ha-cluster_25;

trigger: HA-failover

actions:

HA-failover_email type:email interval:0

subject: HA Failover

mailto:admin@example.com;

Display history for every automation stitch

To display the history for all your automation stitches, use the diagnose test application autod 3 command.

Example output

# diagnose test application autod 3

stitch: Compromised-IP-Banned

local hit: 0 relayed to: 0 relayed from: 0

last trigger:Wed Dec 31 20:00:00 1969

last relay:Wed Dec 31 20:00:00 1969

actions:

Compromised-IP-Banned_ban-ip:

done: 0 relayed to: 0 relayed from: 0

last trigger:Wed Dec 31 20:00:00 1969

last relay:Wed Dec 31 20:00:00 1969

stitch: HA-failover

local hit: 1 relayed to: 1 relayed from: 1

last trigger:Thu May 24 11:35:22 2018

last relay:Thu May 24 11:35:22 2018

actions:

HA-failover_email:

done: 1 relayed to: 1 relayed from: 1

last trigger:Thu May 24 11:35:22 2018

last relay:Thu May 24 11:35:22 2018

Related Videos

sidebar video

Fortinet Security Fabric 6.0.0 Series - Part 3: Compromised Hosts Management

  • 880 views
  • 5 years ago
sidebar video

Fortinet Security Fabric 6.0.0 Series - Part 6: Automation

  • 1,379 views
  • 5 years ago
sidebar video

Fortinet Security Fabric 6.0.0 Series - Part 7: Automation: AWS Lambda and Gener

  • 865 views
  • 5 years ago

Diagnose commands

Diagnose commands are available for automation stitches, allowing you to do the following:

Testing

To test an automation stitch, use the diagnose automation test <automation-stitch-name> <log> command.

Example output

# diagnose automation test HA-failover

automation test is done. stitch:HA-failover

Enable and disable log dumping

To toggle between enabling and disabling log dumping, use the diagnose test application autod 1 command.

Example output

# diagnose test application autod 1

autod log dumping is enabled

# diagnose test application autod 1

autod log dumping is disabled

autod logs dumpping summary:

autod dumped total:0 logs, num of logids:0

Display settings

To display settings for all automation stitches, use the diagnose test application autod 2 command.

Example output

# diagnose test application autod 2

csf: enabled root:yes

total stitches activated: 2

stitch: Compromised-IP-Banned

destinations: all

trigger: Compromised-IP-Banned

actions:

Compromised-IP-Banned_ban-ip type:ban-ip interval:0

stitch: HA-failover

destinations: HA-failover_ha-cluster_25;

trigger: HA-failover

actions:

HA-failover_email type:email interval:0

subject: HA Failover

mailto:admin@example.com;

Display history

To display the history for all your automation stitches, use the diagnose test application autod 3 command.

Example output

# diagnose test application autod 3

stitch: Compromised-IP-Banned

local hit: 0 relayed to: 0 relayed from: 0

last trigger:Wed Dec 31 20:00:00 1969

last relay:Wed Dec 31 20:00:00 1969

actions:

Compromised-IP-Banned_ban-ip:

done: 0 relayed to: 0 relayed from: 0

last trigger:Wed Dec 31 20:00:00 1969

last relay:Wed Dec 31 20:00:00 1969

stitch: HA-failover

local hit: 1 relayed to: 1 relayed from: 1

last trigger:Thu May 24 11:35:22 2018

last relay:Thu May 24 11:35:22 2018

actions:

HA-failover_email:

done: 1 relayed to: 1 relayed from: 1

last trigger:Thu May 24 11:35:22 2018

last relay:Thu May 24 11:35:22 2018

Example output

# diagnose test application autod 2

csf: enabled root:yes

total stitches activated: 2

stitch: Compromised-IP-Banned

destinations: all

trigger: Compromised-IP-Banned

actions:

Compromised-IP-Banned_ban-ip type:ban-ip interval:0

stitch: HA-failover

destinations: HA-failover_ha-cluster_25;

trigger: HA-failover

actions:

HA-failover_email type:email interval:0

subject: HA Failover

mailto:admin@example.com;

Display history for every automation stitch

To display the history for all your automation stitches, use the diagnose test application autod 3 command.

Example output

# diagnose test application autod 3

stitch: Compromised-IP-Banned

local hit: 0 relayed to: 0 relayed from: 0

last trigger:Wed Dec 31 20:00:00 1969

last relay:Wed Dec 31 20:00:00 1969

actions:

Compromised-IP-Banned_ban-ip:

done: 0 relayed to: 0 relayed from: 0

last trigger:Wed Dec 31 20:00:00 1969

last relay:Wed Dec 31 20:00:00 1969

stitch: HA-failover

local hit: 1 relayed to: 1 relayed from: 1

last trigger:Thu May 24 11:35:22 2018

last relay:Thu May 24 11:35:22 2018

actions:

HA-failover_email:

done: 1 relayed to: 1 relayed from: 1

last trigger:Thu May 24 11:35:22 2018

last relay:Thu May 24 11:35:22 2018