Technical Tip: Resolving an installation failure from FortiManager to FortiGate v7.4.10+/v7.6.3+ for limit on shaping-entries under shaping-profile
Description | This article describes an installation failure that occurs when pushing device configurations from FortiManager to FortiGate after upgrading the FortiGate to v7.4.10/v7.6.3 or higher. The issue arises when the FortiManager attempts to apply a limit on the shaping entries, which does not exist in the policing type profile. |
Scope | FortiManager, FortiGate v7.4.10/v7.6.3 or higher. |
Solution | After an upgrade of FortiOS to v7.4.10/v7.6.3 or higher, installation issues can be observed from FortiManager in the format as follows:   This happens when FortiGates are set up with a shaping profile with type set to policing. When the FortiGate does not have a shaping profile configured, or its type is set to queueing, this article does not apply.  This is because the default value of the limit was changed in FortiOS for the shaping-entries, as shown below:  In these versions, the previous default value is set to 1000. The value 1000 is also the value that FortiManager utilizes by default, and thus it worked fine on earlier versions because, by default, it does not push the value. However, as the default changed on FortiOS, it does push the value, but the limit parameter is only applicable to shaping profiles of the queueing type.  There are a couple of other settings for which the default value changed, as indicated in the document FortiManager 7.6.6 and FortiOS 7.4.10 & 7.4.11 compatibility issues on the compatibility between FortiManager v7.6.6 and FortiGate v7.4.10 and v7.4.11. Note that it is also relevant for FortiManager 7.4 versions because it is just a change on the FortiGate, actually.  To resolve the installation failure from FortiManager to FortiGate, follow these steps:
|
