Fortinet black logo
9.4.0

Preparation Checklist

Preparation Checklist

Task

Description

Timeline

README and NOTES Files

Check for the existence of README or NOTES files in the CentOS appliance. Log in to the CentOS appliance CLI as root and type:

cd bsc/campusMgrUpdates/

ls | grep –i readme

ls | grep -i notes

If either a README or NOTES file exists:

  1. Run the following commands and copy output to a text file (match case with filename if different than below)

    cat README

    cat NOTES

  2. Open a support ticket. Attach the text file to verify what actions will be necessary (if any) post migration.

Any time prior to upgrading software.

Software Upgrade

Upgrade all CentOS appliances to the required version (see Requirements). For instructions, refer to the OS and Software Upgrade Cookbook.

Several days prior to starting the migration.

Product Registration

(Step 1) /Endpoint License Entitlements

Transfer (Step 2)

New products must be registered prior to requesting entitlements transfer.

These steps do not affect current functionality.

Two weeks prior to the maintenance window.

Maintenance Window Planning

If FortiNAC is already managing network access, a maintenance window is required to perform the last two migration steps (Collect & Transfer CentOS Migration Data and Cutover).

During this time:

  • VLANs will not be switched

  • RADIUS requests sent to FortiNAC will not be answered

  • Hosts will not be registered

Recommend at least a 4 hour maintenance window to complete the data migration and validation of the following functions:

  • Administrative access

  • Network Inventory

  • Endpoint Visibility

  • Network access scenarios

    • Wired

    • Wireless

    • Remote (VPN)

  • Security Policies

    • Network Access

    • Endpoint Compliance

  • The amount of time required for the migration to complete is dependent upon the deployment size. It has been observed it can take as long as 30 minutes once the data transfer has started to the time the new appliance is running.

  • If unexpected behavior occurs, the customer can revert to the original appliance.

Recommend at least a 4 hour maintenance window

Preparation Checklist

Task

Description

Timeline

README and NOTES Files

Check for the existence of README or NOTES files in the CentOS appliance. Log in to the CentOS appliance CLI as root and type:

cd bsc/campusMgrUpdates/

ls | grep –i readme

ls | grep -i notes

If either a README or NOTES file exists:

  1. Run the following commands and copy output to a text file (match case with filename if different than below)

    cat README

    cat NOTES

  2. Open a support ticket. Attach the text file to verify what actions will be necessary (if any) post migration.

Any time prior to upgrading software.

Software Upgrade

Upgrade all CentOS appliances to the required version (see Requirements). For instructions, refer to the OS and Software Upgrade Cookbook.

Several days prior to starting the migration.

Product Registration

(Step 1) /Endpoint License Entitlements

Transfer (Step 2)

New products must be registered prior to requesting entitlements transfer.

These steps do not affect current functionality.

Two weeks prior to the maintenance window.

Maintenance Window Planning

If FortiNAC is already managing network access, a maintenance window is required to perform the last two migration steps (Collect & Transfer CentOS Migration Data and Cutover).

During this time:

  • VLANs will not be switched

  • RADIUS requests sent to FortiNAC will not be answered

  • Hosts will not be registered

Recommend at least a 4 hour maintenance window to complete the data migration and validation of the following functions:

  • Administrative access

  • Network Inventory

  • Endpoint Visibility

  • Network access scenarios

    • Wired

    • Wireless

    • Remote (VPN)

  • Security Policies

    • Network Access

    • Endpoint Compliance

  • The amount of time required for the migration to complete is dependent upon the deployment size. It has been observed it can take as long as 30 minutes once the data transfer has started to the time the new appliance is running.

  • If unexpected behavior occurs, the customer can revert to the original appliance.

Recommend at least a 4 hour maintenance window