Upgrade Asset Manager Enterprise Edition

An Asset Manager upgrade package upgrades the Asset Manager Enterprise Command Center, Enterprise Scout, and Portal. Upgrade packages do not upgrade Cloud Scouts. 

Upgrades preserve your current configuration for users, roles, organizations, zones, collectors, Enterprise Scouts, and system connections. The FIPS state (i.e., enabled or disabled) any any changes you've made to the Martian packet logging in vi /etc/sysctl.conf file are maintained during the upgrade. Orphaned attributes (i.e., those not associated with any device) and all certificates are cleaned off of the Asset Manager database upon upgrade. 

Upgrade packages are available for download in the FireMon User Center, on the Downloads page.The upgrade procedure follows.

Get Ready

1. Check Prerequisites

2. Review Release Notes

3. Backup Your System

   1. Export Configuration

   2. Export Custom Dashboards & Reports

   3. Export Custom Device Profile Patterns 

Upgrade

1. Ensure that the upgrade package you need has been downloaded to your local system from the FireMon User Center > Downloads page.

2. On the main menu of your Asset Manager Command Center, browse to Settings > Asset Manager Systems.

3. In the Available Systems pane, select the Command Center whose connected Scouts you want to upgrade.

4. In the same pane, click Upgrade Connected Scouts.

5. Select the upgradefile you saved locally and then click Asset Manager Upgrade.

   • The distributed upgrade runs in the background.You can monitor its progress by browsing to the All Notifications report (Reports > Browse Real-Time > All Notifications).
   • The Scouts reboot when the upgrade is complete.
   • All Enterprise Scouts connected to the Command Center upgrade.
6. Spot-check to validate that the Scouts upgraded by browsing to their IP addresses and making sure their version number is up-ticked as expected. 

Upgrade the Command Center from the GUI

Launch the Asset Manager Cloud Scout AMI

1. If you have not done so already, download the upgrade package you need from the FireMon User Center > Downloads page to your local system.

2. On the main menu of your Asset Manager Command Center, browse to Settings > Asset Manager Systems.

3. In the Available Systems pane, select the Command Center you want to upgrade.

4. In the System Information pane, click Upgrade.

5. Select the upgrade file you saved locally and then click Asset Manager Upgrade.
   The Command Center upgrades.

Upgrade the optional Portal from the CLI

To  upgrade from the Command-Line Interface (CLI) of the Portal or any Enterprise Asset Manager component––Command Center, Portal, or Enterprise Scout:

1. Log in to the CLI of a Command Center, Scout, or Portal.

2. Use this syntax to upgrade:
   system upgrade <path to the upgrade file>

   1. If the upgrade file resides on an SSH server, then the path takes the form user@host:/path/to/file
   2. Otherwise, use an SSH client like WinSCP or FileZilla to copy the file to the Asset Manager system. In this case, the path takes the form /path/to/file.
      Whichever Asset Manager component you are logged into, upgrades.

3. Wait for the system to reboot.
   

• Replace your optional Cloud Scout on Azure
  
• Replace your optional Cloud Scout on AWS
  

Step 1: Select Instance Type & Details

1. 1. 1. In a web browser, navigate to the AWS Login page for your preferred region and sign in.
      1. • US East (Northern Virginia) https://console.aws.amazon.com/ec2/v2/home?region=us-east-1 - Images:visibility=public-images;search=Asset Manager,Cloud;sort=name
         • US West (Northern California) https://console.aws.amazon.com/ec2/v2/home?region=us-west-1#Images:visibility=public-images;search=Asset Manager,Cloud;sort=name
         • EU (London) https://console.aws.amazon.com/ec2/v2/home?region=eu-west-2#Images:visibility=public-images;search=Asset Manager,Cloud;sort=name
         • Canada (Central) https://console.aws.amazon.com/ec2/v2/home?region=ca-central-1#Images:visibility=public-images;search=Asset Manager,Cloud;sort=name
         • Asia Pacific (Tokyo) https://console.aws.amazon.com/ec2/v2/home?region=ap-northeast-1#Images:visibility=public-images;search=Asset Manager,Cloud;sort=name
      2. Select the Asset Manager Cloud Scout AMI, and then click Launch.

Step 2: Select Instance Type & Details

1. 1. 1. Select the instance type t2.2xlarge.
      2. Click Next: Configure Instance Details and set the details per your organization’s preferences, which may be to accept all of the defaults. Suggestions follow in bold.
         1. Number of Instances: 1
         2. Purchasing Option: Do not request
         3. Network: Acceptdefault (e.g., Asset ManagerVPC)
         4. Subnet: No preference
         5. Auto-assign Public IP: Use subnet setting
         6. Placement Group: Do not request
         7. Capacity Reservation: Open
         8. IAM Role: None
         9. Shutdown Behavior: Stop
         10. Enable Termination Protection: Do not request
         11. Monitoring: Do not request
         12. Tenancy: Shared – Run a shared hardware instance
         13. Elastic Inference: Do not request
         14. T2/T3 Unlimited: Do not request
         15. Advanced Details: Do not request
   3. Click Next: Add Storage.

Step 3: Add Storage

1. 1. 1. Accept the default values.
      2. Click Next: Add Tag.
         Tags are optional. Use them to label, identify, or keep an inventory of instances.
      3. Click Next: Configure Security Group

Step 4: Configure Security Groups

1. 1. 1. Create a new security group and configure these inbound security rules:

         Type	Protocol	Port Range
         SSH	TCP	22
         HTTPS	TCP	443

      2. Click Review and Launch.
      3. Click Launch.

Step 5: Create a Private Key

1. 1. 1. Select or create a private key pair.
      2. Download the private key pair and store it in a safe and accessible location.
         The private key pair is required on your first login to the Asset Manager Cloud Scout. Thereafter, you’ll log in as the user adminwith the password you set during the software’s initial configuration.

Step 6: Launch Instance

1. 1. 1. Click Launch Instances.
         The system begins its Initializing Instance Launch process.
      2. Navigate to your EC2 dashboard.
      3. Click Running Instances to watch your Asset Manager Cloud Scout initialize.
      4. To name the instance, click the Pencil icon.
      5. Note the IPv4 Public IP address. You will need this to configure your virtual machine.

Step 7: Initialize the System

1. 1. 1. From a terminal window such as PuTTY or Terminal, log in to your Cloud Scout system as the user admin, authenticating with your private key file.
         
         1. Input the IPv4 Public IP address as the Host Name.
         2. Import your private key file. If you are using PuTTY, use PuTTYgen to convert the pem format to ppk format. Use the ppk-formatted key when you connect using PuTTY.
            The FireMon Cloud SDK Initial Configuration screen displays.
         3. Press Enter to continue.
      2. Accept the default values by pressing Enter in response to these prompts:
         
         1. New host name or <Enter> to keep the old one?
         2. How would you like to configure the network? (dhcp|manual) [dhcp]
         3. How would you like to configure DNS? (dhcp|manual) [dhcp]
         4. How would you like to configure NTP? (dhcp|manual) [dhcp]
      3. Enter a new admin password containing 8 characters. Use at least one uppercase letter, one lowercase letter, one number, and one special character.
      4. Confirm the password and press Enter. Your initial system configuration is complete.
         Congratulations! Your Asset Manager Cloud Scout is deployed.
         

   Validate the Upgrade

   • Check Version & Configuration

   • Enable Collectors