Troubleshooting Tip: Interface Pair View Mode option missing in FortiManager

[jasonhong]

Description	This article describes how Interface Pair View Mode works in FortiManager.
Scope	FortiManager.
Solution	By default, there are two View Modes (Sequence and  Interface Pair View) when viewing the firewall policy under the Policy & Objects page in FortiManager. However, in some instances, the View Mode option is missing or does not appear. This is because: When there is more than one interface in either the Source or Destination for the firewall policy, the option to view the firewall policy using the Interface Pair View is not available. As such, it will default to the By Sequence view mode. There is a problem in the Database of the FortiManager Configuration Database after creating/deleting firewall Policies inside the Policy Package. Scenario 1 - more than one interface in either the Source or Destination for the firewall policy: As in the screenshot below, the firewall policy 'test_policy' has two interfaces in the To/Destination column (internal2 and internal3) and the View Mode option will not appear. To make changes, delete one of the interfaces (internal2) and refresh. The page will be processed and the View Mode option will then re-appear. Scenario 2 - FortiManager Configuration Database Issue: When running the CDB check command in the problematic ADOM, output will be received as follows: # diagnostic cdb check policy-packages root [1/7] Checking Scope ... correct [2/7] Checking Dynamic mappings ... correct [3/7] Checking Policy package settings ... correct [4/7] Checking Cross-linked objs ... correct [5/7] Checking Object parent mismatch ... correct [6/7] Checking Undeleted objs ... firewall policy: policyid [10] is not found in node table 1 change(s) will be made [7/7] Checking Controller/Template package status ... correct Do you want to continue? (y/n) The next step is to verify if this Policy ID exists or no in the affected Policy Package under the ADOM root, as in the example. If the Policy ID x does not exist, run the aforementioned command once again and press 'y'.   After this action, the Configuration Database will be corrected and the View Mode option will then re-appear.