Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Dell Financial Services Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell EMC OpenManage Enterprise 3.9 User's Guide

PDF

Upgrade Recommendations and Prerequisites

Administrators must consider the following before updating to the latest version:

  • Take a VM snapshot of the console as a backup in case something unexpected occurs. Allocate more downtime for this if necessary.
  • Allocate at least an hour for the update process. Allocate more time if the update must be downloaded by using a slower network connection.
  • Upgrade of a 'scaled' appliance may fail due to insufficient provisioning of hard drive space required for the data backup from large number of devices and additional plugins. It is recommended to add twice the used hard drive space before initiating the upgrade using the Configure Appliance Disk Size on the Text User Interface (TUI) page. For example, consider expanding the available HD space to 1.2 TB if the initial allocation is 400 GB. For more information see, Configure OpenManage Enterprise by using Text User Interface.
  • Ensure that no device configuration, deployment, or extension (plug-in) tasks are running or are scheduled to run during the planned downtime. Any active or scheduled tasks or policies are terminated without further warning during the update.
  • Post deletion of devices, a restart of services using TUI is recommended before initiating a console upgrade. Otherwise, the upgrade may fail and the console would reboot with the previous working state of the appliance.
  • Notify other console users of the impending scheduled update.
  • If the upgrade fails, the appliance would restart. It is recommended to revert the VM snapshot and upgrade again.
NOTE
  • Only OpenManage Enterprise versions starting 3.7 and later can be directly updated to version 3.9 by the Automatic > Online method.
  • OpenManage Enterprise versions earlier than versions 3.7, for example, version 3.6 and version 3.5, must first be updated to version 3.7 before considering an upgrade to 3.9.
  • OpenManage Enterprise—Tech Release version should be first upgraded to OpenManage Enterprise either version 3.0 or 3.1.
  • When you update OpenManage Enterprise with more than 8000 discovered devices, the update task completes in two to three hours. During this time, the services might become unresponsive. It is then recommended to gracefully reboot the appliance. After the reboot, normal functionality of the appliance is restored.
  • Upgrade time for an appliance with Power Manager plugin installed, might be between 1 and 10 hours depending on the number of devices being monitored by Power Manager.
  • Adding a second network interface should be done only after the completion of the post-console upgrade tasks. Attempt to add a second NIC while the post-upgrade task is in progress would be ineffective.
  • You can log in immediately after the appliance is updated and do not have to wait until the entire inventory is discovered. Post update, the discovery task will run in the background and you can see the progress occasionally.
  • Clicking Update would initiate an Upgrade Bundle Download job. This job finishes automatically after all the update files are downloaded and cannot be terminated by the user.
  • Once the console upgrade completes, a series of mandatory tasks are undertaken as part of a system generated task named Post upgrade Task. It is recommended that this task be allowed to complete before installing or upgrading any available plugins. Additionally, do not manually disable/stop this task. This Post upgrade Task performs the following operations:
    1. Restoring upgrade console settings
    2. Restoring logging status
    3. Processing configuration task parameters
    4. Upgrading console settings if applicable to the current release.
    5. Running email tasks
    6. Sending out a reminder to disable any incompatible plugins
    7. Running catalog updates for plugins
    8. Running discovery tasks
    9. Enabling NTP services
    10. Updating the job completion status for the firmware update
    11. Updating SNMP configurations
    12. Setting FSD capability for the console

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\