FireMon Asset Manager
Page tree

FireMon provides full-installation Asset Manager VM images on our SFTP site. To download yours, request Support indicating the release you need. Support will set up an account folder for you and let you know when the image file, along with any license key files you may need (e.g., Command Center, Scouts, Cloud Scouts, integrations), is in the folder. They will also provide you with the login credentials to your account folder.

The same OVA image file is capable of deploying Command Centers and Scouts.

To pick up the installation image . . .

  1. Browse to: https://sftp.firemon.com.



  2. Enter your credentials and then click Login.
    Contact us if you need this information or other login assistance.

  3. Browse the Files folder for items you need and save them to your local system.

     

Contact Support if you have any trouble.

One OVA for Both Command Center & Scouts

Asset Manager Scouts are deployed by users in the same manner as Command Centers. The license keys, which Asset Manager creates using a component's UUID, determine whether the virtual machine OVA template will unpack to a Scout or to a Command Center.  

See Full Deployment for the complete installation procedure.  See Upgrade Process to upgrade an existing Asset Manager Command Center or Scout.

The OVA intended for use in deploying Scouts allocates fewer system resources because Scouts are small. The one intended for use in deploying Command Centers is relatively large.  It is configured to allocate an appropriate level of resources to discover and index your organization's network.

You may install an unlimited number of virtual Scouts by reusing the OVA template and you may connect however many Scouts you need to your Command Center. You will need to input a unique license key from Asset Manager, however, for each Scout you install. This is because the UUID changes every time the OVA is applied to a different virtual machine.

Each Command Center deploys with its own onboard Scout that cannot be disabled or deleted. This onboard Scout is referred to as "local" or "onboard" on the Asset Manager GUI and in this documentation.

Once deployed, Scouts are smaller, have a minimal GUI, and require fewer system resources.  When you browse to a Scout's IP address, you'll see three tabs of device identifiers about it.  For more on these identifiers, plus the procedure to add, remove, and upgrade Scouts, see Managing Asset Manager Systems.

The next step is to allocate space for your Asset Manager system.


  • No labels