FireMon Asset Manager
Page tree

Asset Manager 5.0 introduces upgrading the Operating System from Centos 7 to Rocky Linux 9.

Due to the OS change, your Asset Manager system does not support typical upgrades. Below are high-level steps, followed by detailed steps for multiple upgrade options.

High-Level Steps

  1. Create a backup file of the old system configuration

  2. Install 5.0 on either a new virtual machine or the existing virtual machine

  3. License the 5.0 system with a new Asset Manager license

  4. Restoring data from the backup file

Detailed steps when using the same virtual machine

  1. Upgrade the old system to Asset Manager 4.11.0.0 first and then to 4.11.0.2.  Review Upgrading FireMon Asset Manager

  2. Login to the CLI as an administrator / superuser

  3. Run system backup create <location>
    • The <location> can be a local file or directory or an SCP path such as user@example.com:/tmp/filename.tgz
    • If it’s a local file, then that file should be copied off the machine

  4. Power down the virtual machine

  5. Mount the Asset Manager 5.0 DVD ISO on the virtual machine

  6. Boot from the DVD

  7. Select Install Asset Manager 5.0 . The system will reboot when finished

  8. When the installation is finished, log in to the CLI as admin and complete the post-install configuration. Review Initial Configuration 

  9. License the new system with a new Asset Manager license. Review Activate Your License 

  10. If the original system had a custom CA or server certificate, then those should be installed now, Review About Certificates

  11. Optionally, copy the saved backup file to the new system

  12. Run system backup restore <location> to re-create the original system’s configurations

    1. The <location> can be the path to the local file you already transferred in step 11, or an SCP path such as user@example.com:/tmp/filename.tg

Detailed steps when using a new virtual machine

  1. Upgrade the old system to Asset Manager 4.11.0.0 first and then to 4.11.0.2. Review Upgrading FireMon Asset Manager

  2. Login to the CLI as an administrator / superuser

  3. Run system backup create <location>
    • The <location> can be a local file or directory or an SCP path such as user@example.com:/tmp
    • If it’s a local file, then that file should be copied off the machine

  4. Create a new virtual machine from an Asset Manager 5.0 OVA (VMware), VHD (Azure/Hyper-v) or AMI (AWS)

  5. Login to the CLI as admin and complete the post-install configuration. Review Initial Configuration 

  6. License the new system with a new Asset Manager license. Review Activate Your License  

  7. If the original system had a custom CA or server certificate, those should be installed now. Review About Certificates 

  8. Optionally, copy the saved backup file to the new system

  9. Run system backup restore <location> to re-create the original system’s configurations

    1. The <location> can be the path to the local file you already transferred in step 8, or an SCP path such as user@example.com:/tmp/filename.tgz

Deploying Scouts

You should disconnect the scouts from your Command Center and proceed with either option above. After the Scouts have been deployed at 5.0, reconnect to your Command Center.


  • No labels