Description
This article describes some useful commands to troubleshoot common issues with the FortiGate Transaction Mode or before raising a ticket with the Fortinet Technical Support.
Scope
FortiGate.
Solution
When using the Workspace Mode in FortiGate, multiple admin users will be able to make changes at the same time and then commit the changes once done. If more than one admin user tries to change the same part of the config, i.e. 'config router static', an error message will be displayed:
Can not config the object since either the object or the referenced objects are being configured by other transactions. Command fail. Return code 14
Any transaction has an idle timeout of 5 minutes. After, it expires and the changes are aborted if not committed.
The following outputs can be collected to troubleshoot the problem or before raising a new ticket with the Fortinet Technical Support if further assistance is needed:
diagnose sys config-transaction status
The output will show the status of the current Workspace mode transaction. No output will be shown if the command is being run outside of transaction mode.
diagnose sys config-transaction show txn-info
The output will show the current transactions, the user making the changes, and the transaction time left. It is useful to collect this output 3 or 4 times to see if the timer is currently decreasing.
diagnose sys config-transaction show txn-lock
The output shows the transaction lock status and its process ID.
diagnose sys config-transaction show entity-by-txn
The output shows the config sections involved in each transaction.
diagnose sys config-transaction show txn-entity
The output shows the config sections involved in each transaction (more details than previous command).
diagnose sys config-transaction show txn-cli-commands <txn-ID>
The output shows the CLI commands related to the specific transaction ID.
diagnose sys config-transaction show mctx
The output shows statistics related to the transactions pages and page size.
diagnose debug config-error-log read
The output shows if there is any config import error generated during the last config restore (if not cleared).
Related article:
