Fortinet black logo

Upgrade Requirements

Upgrade Requirements

Ticket #

Description

FortiNAC License Key

Upgrading to this release requires the FortiNAC License. It is possible, however unlikely, older appliances may not have this specific type of license key installed. In such cases, an error will display during the upgrade. For additional details, see KB article https://community.fortinet.com/t5/FortiNAC/Troubleshooting-Tip-Upgrade-fails-with-license-requirement-error/ta-p/246324

Upgrade Path Requirements

Systems on version 9.1.6 must upgrade to either:

  • Higher version of 9.1 (e.g. 9.1.7)

  • 9.2.4 or higher

Systems on versions 8.2 or lower must upgrade to 8.3 before upgrading to 8.4 or higher.

892856

High Availibility and FortiNAC Manager Environments: The following are required as of 7.2.2:

Key files containing certificates are installed in all FortiNAC servers. License keys with certificates were introduced on January 1st 2020. Appliances registered after January 1st should have certificates. To confirm, login to the UI of each appliance and review the System Summary Dashboard widget (Certificates = Yes). If there are no certificates, see Importing License Key Certificates in the applicable FortiNAC Manager Guide.

Allowed serial numbers: Due to enhancements in communication between FortiNAC servers, a list of allowed FortiNAC appliance serial numbers must be set. This can be configured prior to upgrade to avoid communication interruption. For instructions, see What's New.

834826

As of FortiNAC versions 9.4.2 & vF7.x, Persistent Agent communication using UDP 4567 is no longer supported.

It is recommended the following be checked prior to upgrade to avoid agent communication disruptions:

  • SSL certificates are installed for the Persistent Agent target

  • Persistent Agents are running a minimum version of 5.3

For additional details see KB article 251359.

https://community.fortinet.com/t5/FortiNAC/Technical-Note-Agent-communication-using-UDP-4567-no-longer/ta-p/251359

885056 All devices managed by FortiNAC must have a unique IP address. This includes FortiSwitches in Link Mode: Managed FortiSwitch interface IP addresses must be unique. Otherwise, they will not be properly managed by FortiNAC and inconsistencies may occur. This is also noted in the FortiSwitch Integration reference manual.

829805

FortiNAC supports REST API V2. For a list of supported v2 calls see

https://docs.fortinet.com/document/fortinac/9.2.0/rest-api-v2?preview_token=fc0e8d44856a1745b0f6

As of FortiNAC version 7.2, all v1 calls have been deprecated except for the following:

  • FortinetFabricIntegrationService

  • ServerInformationService

  • ServiceDocumentService

  • ControlService

Upgrade Requirements

Ticket #

Description

FortiNAC License Key

Upgrading to this release requires the FortiNAC License. It is possible, however unlikely, older appliances may not have this specific type of license key installed. In such cases, an error will display during the upgrade. For additional details, see KB article https://community.fortinet.com/t5/FortiNAC/Troubleshooting-Tip-Upgrade-fails-with-license-requirement-error/ta-p/246324

Upgrade Path Requirements

Systems on version 9.1.6 must upgrade to either:

  • Higher version of 9.1 (e.g. 9.1.7)

  • 9.2.4 or higher

Systems on versions 8.2 or lower must upgrade to 8.3 before upgrading to 8.4 or higher.

892856

High Availibility and FortiNAC Manager Environments: The following are required as of 7.2.2:

Key files containing certificates are installed in all FortiNAC servers. License keys with certificates were introduced on January 1st 2020. Appliances registered after January 1st should have certificates. To confirm, login to the UI of each appliance and review the System Summary Dashboard widget (Certificates = Yes). If there are no certificates, see Importing License Key Certificates in the applicable FortiNAC Manager Guide.

Allowed serial numbers: Due to enhancements in communication between FortiNAC servers, a list of allowed FortiNAC appliance serial numbers must be set. This can be configured prior to upgrade to avoid communication interruption. For instructions, see What's New.

834826

As of FortiNAC versions 9.4.2 & vF7.x, Persistent Agent communication using UDP 4567 is no longer supported.

It is recommended the following be checked prior to upgrade to avoid agent communication disruptions:

  • SSL certificates are installed for the Persistent Agent target

  • Persistent Agents are running a minimum version of 5.3

For additional details see KB article 251359.

https://community.fortinet.com/t5/FortiNAC/Technical-Note-Agent-communication-using-UDP-4567-no-longer/ta-p/251359

885056 All devices managed by FortiNAC must have a unique IP address. This includes FortiSwitches in Link Mode: Managed FortiSwitch interface IP addresses must be unique. Otherwise, they will not be properly managed by FortiNAC and inconsistencies may occur. This is also noted in the FortiSwitch Integration reference manual.

829805

FortiNAC supports REST API V2. For a list of supported v2 calls see

https://docs.fortinet.com/document/fortinac/9.2.0/rest-api-v2?preview_token=fc0e8d44856a1745b0f6

As of FortiNAC version 7.2, all v1 calls have been deprecated except for the following:

  • FortinetFabricIntegrationService

  • ServerInformationService

  • ServiceDocumentService

  • ControlService