Fortinet Document Library

Version:

6.2.0
FortiGate / FortiOS FortiAnalyzer FortiManager FortiWeb FortiAuthenticator FortiSandbox FortiWeb Manager

Table of Contents

Azure Cookbook

Resources

Upgrade Path Tool
Home Azure/Azure Stack FortiGate / FortiOS
6.2 6.0 5.6

Azure Cookbook

6.2.0
6.2.0
Download PDF
Copy Link

Troubleshooting

The following provides a list of CLI commands for troubleshooting the FortiGate-VM active-passive HA deployment.

Usage

Command

Validate HA configuration sync.

diagnose sys ha checksum show

Invoke debug output for Azure components in FortiOS.

diagnose debug application azd -99

Display diagnose commands.

SDN api test allows you to see whether your SDN connector configuration can successfully authenticate and issue commands to Azure management.

Running HA api test on production environments is not recommended. This may lead your cluster to a mixed state. Use it only to see whether the azd daemon successfully sends failover commands to Azure management.

diagnose test application azd -1

1. show HA stats

2. SDN api test

3. HA api test

4. filter list test

99. restart

Verify that the following diagnose command works for the azd daemon.

Primary FortiGate-VM:

diag test application azd 1

azd stats:

master: 1

Secondary FortiGate-VM:

diag test application azd 1

azd stats:

master: 0

Restart your Azure daemon after modifying the CLI configuration.

diag test application azd 99

azd start

Disable synchronization.

config system ha

set sync-config disable

end

Resources

Upgrade Path Tool

Troubleshooting

The following provides a list of CLI commands for troubleshooting the FortiGate-VM active-passive HA deployment.

Usage

Command

Validate HA configuration sync.

diagnose sys ha checksum show

Invoke debug output for Azure components in FortiOS.

diagnose debug application azd -99

Display diagnose commands.

SDN api test allows you to see whether your SDN connector configuration can successfully authenticate and issue commands to Azure management.

Running HA api test on production environments is not recommended. This may lead your cluster to a mixed state. Use it only to see whether the azd daemon successfully sends failover commands to Azure management.

diagnose test application azd -1

1. show HA stats

2. SDN api test

3. HA api test

4. filter list test

99. restart

Verify that the following diagnose command works for the azd daemon.

Primary FortiGate-VM:

diag test application azd 1

azd stats:

master: 1

Secondary FortiGate-VM:

diag test application azd 1

azd stats:

master: 0

Restart your Azure daemon after modifying the CLI configuration.

diag test application azd 99

azd start

Disable synchronization.

config system ha

set sync-config disable

end