Page tree
Skip to end of metadata
Go to start of metadata

The upgrade process for this release is to boot a Lumeta system from a Lumeta-provided ISO in VMware. This method upgrades the Lumeta operating system from CentOS 6.7 to CentOS 7.7 and also installs the Lumeta software.

This special 4.0 upgrade process is for Lumeta Command Centers and Lumeta Enterprise Scouts only. The standard upgrade process applies to CloudVisibility Cloud Scouts. You may opt to reinstall Scouts rather than using this upgrade process for them. If you do, just be aware that Scouts do contain a modest amount of data such as interface packet rates, remote connections, and licensing that will need to be manually reconfigured.

Although this process is different from our typical upgrade, it does provide advantages:

  • Same Virtual Machine before and after upgrade, which means the upgrade does not double the amount of VMware resources used
  • Same UUID before and after upgrade, enabling you to complete an upgrade without having to procure a new license for each Lumeta instance
  • Same interface configuration before and after upgrade, making it unnecessary for you to allocate new IPs or re-provision new virtual machines

To facilitate the upgrade, Lumeta developed a data retention utility that backs up data from the 3.3.x platform. The utility generates a backup file that is kept in a secure location until after the software upgrade has completed. Afterward, another utility restores the data from the backup to the 4.0 platform. This upgrade process does not affect the Lumeta system proper; the Lumeta 4.0 system is functionally equivalent to its predecessor.

Pre-Upgrade - In the pre-upgrade process, you create a snapshot of your virtual machine. This backup can be used to restore the pre-upgrade state of the Lumeta system in the unlikely event there is a failure during upgrade. Next, you install Interim Release 3.3.6, a pre-upgrade package that upgrades only the packages necessary for Lumeta to generate the backup file. Once this process has completed, the newly installed backup utility will be used to generate a backup file used later for restoration.

Upgrade - The upgrade of Lumeta from 3.3.6 to 4.0 involves mounting the provided ISO in VSphere data store and installing the Lumeta system as new. This will give you a new Lumeta 4.0 system.

Post-Upgrade - Once the Lumeta 4.0 software has completed installation, the Restore utility brings your system to the same functional state as before the upgrade.

Files You'll Need

Available now on the Downloads page of  FireMon User Center

  • Interim release 3.3.6 tgz upgrade file
  • Lumeta 4.0 ISO file


System Requirements & Specifications

System Requirements & Specifications (+ special builds)

Process Checklist

The process is as follows:

  • 1. Take a snapshot of your Lumeta Enterprise Command Center
  • 2. Upgrade to interim release 3.3.6
  • 3. Back up 3.3.6 and save the backup to an off-box location
  • 4. Upload the Lumeta-install-4.0.iso file

  • 5. ISO-boot Lumeta 4.0
  • 6. Do a post-install restore (which is the post-install wizard plus the option to restore)

Upgrade Process

  1. Take a snapshot of your Lumeta Enterprise Command Center

    The process applies to Lumeta Command Centers only. It does not apply to Lumeta Enterprise Scouts, Cloud Scouts, Portals, or Lumeta Community Edition.

  2. Upgrade to interim release 3.3.6.


    The 3.3.6 upgrade is intended for the sole purpose of providing you with a backup of your system. It is not intended to be and should not be used as a regular upgrade or software release. The 3.3.6 release is an unsupported waypoint; Lumeta 4.0 is the destination. During this upgrade, you will not get any user feedback. You may want to track the upgrade in PuTTY so you can see its progress. Instructions to do this are included in the procedure that follows.

    1. Log in to your Lumeta Command Center 3.3.5.x via Command Line Interface (CLI).

    2. Enter an upgrade command.

      1. CLI: "system upgrade /tmp/esi_update-

    3. The Command Center begins its upgrade process, which takes a while. Ultimately, your box will reboot to interim release 3.3.6.

    4. Log in to admin CLI user after the system reboots, and then issue the following command to track the progress of the upgrade:

      You will see the system's progress. Ultimately, the message “Successfully upgraded from 3.3.x to” will display.

  3. Log in to the admin CLI user repeatedly, until the welcome banner stops reporting that the system is in “maintenance mode” and instead shows “Lumeta Spectre system [name] is a Command

    Center.” The system will exit maintenance mode when all of the changes have been completed.

  4. Back up 3.3.6 and save it off box

    The next step is to make the actual backup and save it off-box as a  zipped tar file (.tgz). You may choose where you want to store your backup file. Just make sure it's a location to which you can SCP. In the example below, we show creating the backup and saving it off to another server in one step. You may, however, prefer to first save the backup using "system backup create /tmp/"file-name". Then copy this file off the Command Center onto your local workstation using winscp, terminal or a similar utility. Two things to bear in mind: Any files not contained in the 3.3.6 backup will be deleted. The backup file may be very large, so make sure you have sufficient resources to store it in your preferred location. 

    1. From your Command Center CLI, log in and enter the command "system backup create <user@host:path/tp/file> " for example  system backup create prael@hector:/home/DEV/backup

      If you input the command "system backup create /var/tmp/" on a freshly netbooted system and do not follow the command with <user@host:path/tp/file>, you may see this erroneous error message:
      cp: ‘/var/tmp/ESI-’ and ‘/var/tmp/ESI-’ are the same file

      You may safely ignore this message! The backup file has been created successfully.

    2. Restart system services by entering the CLI command support service dataserver restart.
    3. Open an SSH CLI session using admin login.
    4. When the message "Backup to [filename] complete" appears, execute the following command to track the progress of the backup script:

      tail -f /var/log/backup_restore.log

    5. In response to the system prompt, enter a password to enable SCP.
      Ultimately, a backup of 3.3.6 is saved to your designated location.

      You can see the backup file that 3.3.6 generates in your preferred backup location.

       If you didn’t use a networked file location to download the file, use your SCP client software to store the file on your local workstation.

  5. Upload the Lumeta-4.0.iso file to the vmware server from which you want to boot.
    1. Fetch the Lumeta 4.O ISO file from the FireMon User Center > Downloads page.

  6. Upload this 2GB file to the datastore of the VMware host from which you want to boot.
    Note: This step only needs to be done only once for all the VMs in your organization.
    1. In the vmware Navigator > Files tab, click the Upload icon to bring in the 4.0 ISO file.

  1. ISO-boot Lumeta 4.0

    1. Return to your Lumeta 3.3.6 Command Center on vmware.

    2.  Navigate to the Summary tab > VM Hardware > CD/DVD drive 1.

    3. Click the Connect to CD/DVD Image option

    4. Select the the Lumeta-4.0.iso file from your datastore and click OK.

      The Lumeta-4.0.iso image is now connected your Command Center.

  2. Start booting up your Lumeta 3.3.6 Command Center, but press ESC to interrupt the boot at this point and display the Boot Menu.

    Note: If for any reason pressing ESC doesn't interrupt the boot process (as illustrated above), an alternate method is to go into the VM's Settings > Advanced Options pane and there configure it to enter BIOS setup. Change the boot sequence and then restart the VM.

  3. Select option 4: CD-ROM Drive.

  4. Select Install Lumeta 4.0.
    The Install Lumeta 4.0 menu has a timer that counts down from 10 and will begin the install at 0 even if no user input is given.
    Note: The small system option is expected to be removed from the GUI. Select the full-sized option.

    Installation begins.

  5. After the ISO-boot has completed, give the box another 6-8 minutes to allow the system to initialize. This part of the process takes about a half hour. Also, do not push the F1, F2, or F3 keys while the ISO is booting. Let the process run to completion. Wait until the CentOS login prompt is followed by the Lumeta Spectre prompt; this may take up to three minutes and displays without you having to touch any keys on your keyboard:

  6. Do a post-install restore

    1. The next step is to restore the backup you saved as a  zipped tar file (.tgz). In the example below, we show copying and restoring the backup in one step. 

    2. If you don't have SSH access, you can opt to do the restore later on, after the Command Center has been initialized. You may choose to first copy the backup file to the /tmp directory of the Command Center using winscp, terminal, or another utility. Then from your Command Center CLI, restore the backup with system backup restore [/tmp/'file-name']
    3. Return to the vmware Lumeta 4.0 console and log in. At this point, you won't be using your 3.3.x password. Use the default system password here. See Default UID and PW.
      The Initial Configuration screen with Restore capability displays.

    4. Press Enter to select DHCP. Nevertheless, the server will always get a static IP.

    5. When you specify the restore server later in the process, you will want to be able to say the name of the server (e.g., Hector), rather than providing its IP address, so press Enter to choose DHCP.

    6. You will see the prompt "Do you want to restore your backup now?" and the prompt for a Yes/No response. If you respond "Yes", the system will prompt you to enter the location of your backup file. You may opt to copy it to your local system in perhaps a /tmp directory.

      If you opt to restore your backup file later, expect the system to initially go into maintenance mode. Give it some time for the services to come up in the background. Without any intervention from you, the system will reboot itself. Again, wait a little while for the system to finish its processing and come out of maintenance mode.

    7. The system will then prompt you to enter the SCP password. You get three attempts at the password.

      Your original backup starts to restore. You can see the items that are restored in your console.

    8. The system reboots to Lumeta 4.0.

      Congratulations! You have successfully upgraded your system to Lumeta 4.0! You may now log in from your browser.

      Your new system will be significantly faster. So much so, that you may see a "System still in maintenance mode" or "License not activated" message. If so, be patient and give all the threads of activity a chance to run to completion. The problem should resolve itself.

  7. Disconnect the CD-ROM drive if you have not done so already.

  8. If for any reason you have not yet restored your backup, you may do so now by entering the command:
    system backup restore [/tmp/'file-name']

    1. Your original license and passwords will be activated and the system will once again reboot as part of the restore process.


If you log in to the CLI after restoring from backup, you may see this error message:
"(in cleanup) Can't open /home/admin/.esicookies.txt: Permission denied at /usr/share/perl5/vendor_perl/HTTP/ line 415."
If this happens, you will need to start a bash session with the support bash command and become root (su) to delete the (rm /home/admin/.esicookies.txt). This should resolve the problem.


  1. If I have modified files outside of what Lumeta has explicitly defined to be backed up, would it be restored on the new system?
    1. No. The list that Lumeta has provided are the ONLY functional files that will be backed up and restored. The term functional files means that Lumeta will share with users which features will be functionally equivalent from the restore, but not the files that are being backed up. The reason for this is some files will be backed up and restored, some will be merged, and some will have new configurations generated with old parameters.
  2. How much space will I need for backup storage?
    1. The main factor in how much space will be needed for backup storage is how large the databases are. If either the X15 or Postgres databases are large, a large amount of disk space will need to be free to support this backup.
  3. What if my system is low on space?
    1. Space will need to be created before the backup can proceed.
  4. Do all Lumeta system types need to be backed up, or can I just re-install system types such as Scouts?
    1. Likely the most important system type is the command center. We recommend this always be backed up. Scouts could skipped as they are lighter to reinstall, yet they do still contain some data, such as interface packet rates, remote connections, and licensing. If Scouts are skipped, they will need to be manually reconfigured.
  5. Do we support backing up events?
    1. Yes, events can be backed up, but they generate a very large database backup and take a long duration of time, which is why they are skipped by default.
  6. Do we backup spool files?
    1. Yes, we backup spool files.
  7. Do we restore logs?
    1. Logs are not restored. This is due to many log files changing format and their large size. While logs will not be restored, they will be included as part of the back up file so that users can manually reference them if needed.

  • No labels

1 Comment

  1. Anonymous - cialis 5 mg Jttjad Brand Name Propecia Male Pattern Hair Loss Yvxlog Cialis Yypdpq Vrftsb - generic cialis 20mg Aivxcz cialis farmacias benavides