Compatibility with FortiOS Versions
This section highlights compatibility issues that administrators should be aware of in 5.6.11.
Compatibility issues with FortiOS 5.6.6
The following table lists interoperability issues that have been identified with FortiManager version 5.6.5 and FortiOS 5.6.6.
| Bug ID | Description |
|---|---|
| 513066 |
FortiManager 5.6.5 does not support the following new value in FortiOS 5.6.6: |
|
513069 |
FortiManager 5.6.5 does not support the following new value in FortiOS 5.6.6: |
Compatibility issues with FortiOS 5.6.5
The following table lists known interoperability issues that have been identified with FortiManager version 5.6.4 and FortiOS version 5.6.5.
| Bug ID | Description |
|---|---|
| 496117 | Install fails for purging dnsfilter profile. |
Compatibility issues with FortiOS 5.6.3
The following table lists interoperability issues that have been identified with FortiManager version 5.6.1 and FortiOS 5.6.3.
| Bug ID | Description |
|---|---|
| 469993 | FortiManager has a different default value for switch-controller-dhcp-snooping from that on FortiGate. |
Compatibility issues with FortiOS 5.6.0 and 5.6.1
The following table lists interoperability issues that have been identified with FortiManager version 5.6.0 and FortiOS 5.6.0 and 5.6.1.
| Bug ID | Description |
|---|---|
| 451036 | FortiManager may return verification error on proxy enable when installing a policy package. |
|
460639 |
FortiManager may return verification error on |
Compatibility issues with FortiOS 5.4.10
The following table lists interoperability issues that have been identified with FortiManager version 5.4.5 and FortiOS 5.4.10.
| Bug ID | Description |
|---|---|
| 508337 |
FortiManager cannot edit the following configurations for replacement message: system replacemsg mail "email-decompress-limit" system replacemsg mail "smtp-decompress-limit" system replacemsg nntp "email-decompress-limit" |
Compatibility issues with FortiOS 5.4.9
The following table lists interoperability issues that have been identified with FortiManager version 5.6.3 and FortiOS 5.4.9.
| Bug ID | Description |
|---|---|
| 486592 |
FortiManager may report verification failure on the following attributes for RADIUS users: rsso-endpoint-attribute rsso-endpoint-block-attribute sso-attribute |
Compatibility issues with FortiOS 5.4.8
The following table lists interoperability issues that have been identified with FortiManager version 5.4.4 and FortiOS 5.4.8.
| Bug ID | Description |
|---|---|
| 469700 | FortiManager is missing three wtp-profiles: FAP221E, FAP222E, and FAP223E. |
Compatibility issues with FortiOS 5.2.10
The following table lists interoperability issues that have been identified with FortiManager version 5.4.1 and FortiOS 5.2.10.
| Bug ID | Description |
|---|---|
| 397220 | FortiOS 5.2.10 increased the maximum number of the firewall schedule objects for 1U and 2U+ appliances. As a result, a retrieve may fail if more than the maximum objects are configured. |
Compatibility issues with FortiOS 5.2.7
The following table lists interoperability issues that have been identified with FortiManager version 5.2.6 and FortiOS 5.2.7.
| Bug ID | Description |
|---|---|
| 365757 | Retrieve may fail on LDAP User Group if object filter has more than 511 characters. |
| 365766 | Retrieve may fail when there are more than 50 portals within a VDOM. |
| 365782 | Install may fail on system global optimize or system fips-cc entropy-token. |
Compatibility issues with FortiOS 5.2.6
The following table lists interoperability issues that have been identified with FortiManager version 5.2.4 and FortiOS 5.2.6.
| Bug ID | Description |
|---|---|
| 308294 | 1) New default wtp-profile settings on FOS 5.2.6 cause verification errors during installation. 2) FortiManager only supports 10,000 firewall addresses while FortiOS 5.2.6 supports 20,000 firewall addresses. |
Compatibility issues with FortiOS 5.2.1
The following table lists interoperability issues that have been identified with FortiManager version 5.2.1 and FortiOS version 5.2.1.
| Bug ID | Description |
|---|---|
| 262584 | When creating a VDOM for the first time it fails. |
| 263896 | If it contains the certificate: Fortinet_CA_SSLProxy or Fortinet_SSLProxy, retrieve may not work as expected. |
Compatibility issues with FortiOS 5.2.0
The following table lists known interoperability issues that have been identified with FortiManager version 5.2.1 and FortiOS version 5.2.0.
| Bug ID | Description |
|---|---|
| 262584 | When creating a VDOM for the first time it fails. |
| 263949 | Installing a VIP with port forwarding and ICMP to a 5.2.0 FortiGate fails. |
| Bug ID | Description |
|---|---|
| 230199 | FortiManager allows the creation of a new FAP-320C WTP profile on a FortiOS 5.0.5 device causing the install to fail. FAP-320C is new for FortiOS 5.0.6. |
| Bug ID | Description |
|---|---|
| 226064 | Attempting to install time zones 79 and 80 fails. These time zones were added in FortiOS 5.0.5. |
| 226078 | When the password length is increased to 128 characters, the installation fails. |
| 226098 | When installing a new endpoint-control profile, installation verification fails due to default value changes in FortiOS 5.0.5. |
| 226102 | If DHCP server is disabled, installation fails due to syntax changes in FortiOS 5.0.5. |
| 226203 | Installation of address groups to some FortiGate models may fail due to table size changes. The address group table size was increased in FortiOS 5.0.5. |
| 226236 | The set dedicated-management-cpu enable and set user-anonymize enable CLI commands fail on device install. These commands were added in FortiOS 5.0.5. |
| 230199 | FortiManager allows the creation of a new FAP-320C WTP profile on a FortiOS 5.0.4 device causing the install to fail. FAP-320C is new for FortiOS 5.0.6. |