After upgrading your system

After upgrading your system to A32.20, follow the steps in this topic before running your ASMS system.

Check upgrade success

To make sure that the upgrade to A32.20 was successful, perform system sanity checks.

Do the following:

  1. In the algosec_conf main menu, select 17 System health.

  2. Select 1: Check services status to check that basic ASMS processes are running on your machines.

  3. Select 2: Check system health and run a Full check.

Run all firewalls

Run a manual analysis to create an unscheduled report on all on individual devices, groups, and matrices defined in AFA. See Run a manual AFA analysis.

SSO integration (if applicable)

If you used custom UID parsers (in pre-existing SSO environments), you may need additional adjustments to your local code. See Configure a customized UID parser​.

Existing open Change Requests for Panorama devices

If you did not close Change Requests for panorama devices before the upgrade (see Close any open Change Requests for Panorama devices ), note the following:

  • For each Change Request in the Implement stage: Recalculate the work order.

  • For Change Requests in the Validate stage: Since the Change Request from before the upgrade doesn't have a URL Category field but the matched rule does, if you recalculate the validation after the upgrade, the recommended compatibility check will incorrectly show a failure in the Destination/URL Category column.