After the upgrade/migration

You have just finished upgrading and migrating your system to A32.00 with CentOS 7. Follow the steps in this topic before running your ASMS system.

Check Single Sign On (SSO)

If your system machine has changed its IP, configure the new IP for Single Sign On (SSO). See Configure user authentication.

Check upgrade/migration success

To make sure that the upgrade to A32.00 with migration to CentOS 7 was successful, perform system sanity checks. See System sanity checks

Check backup settings

The backup configuration to the external backup server may need to be reconfigured after the migration to CentOS 7.

On system machine, verify path, IP, hostname and Password definitions in the backup configuration. See Define backup options.

Custom scripts

If you moved customizations from other folders to /usr/share/fireflow/local/etc/site/lib/, after the migration, you can return them to their previous locations.

Also move the scheduler back. (To move back, go to the CRON tab of the scheduler).

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.

Set global parameter RISK_CHECK_API_RISK_PROFILE in AppViz

(optional) In A32.00, AppViz uses an improved method for finding risks for traffic flows. In order to determine the risk profile used by this new method, you need to define the global parameter RISK_CHECK_API_RISK_PROFILE.

Otherwise, if not set, the risk profile that was used in the last completed report is selected for the AppViz risk calculation. If there was no last completed report, by default the Standard risk profile is used.

Do the following:

Define a value for the RISK_CHECK_API_RISK_PROFILE parameter as explained in Advanced Configuration. See RISK_CHECK_API_RISK_PROFILE.

Reconfigure monitoring agents after CentOS 7 migration

If you use third party monitoring agents, remember to:

Reconfigure SNMP monitoring for use with the new ASMS machine IP. See this AlgoPedia article.
Set up syslog forwarding. See AFA Syslog messages.

Reinstall AlgoBot

If you use AlgoBot: AlgoBot is not part of the upgrade package. The new AlgoBot version for A32.00 needs to be reinstalled on the A32.00 System. The configuration on chat platforms is still valid, so requires no update.