A Firmware Upgrade Activity defines which devices should be upgraded, to which versions, the pre/post actions and the error policy to use.
To add a new firmware upgrade activity, navigate to Mange→ Maintenance→ Firmware Upgrade, select the plan to add an activity to and click "Add Activity" from the Firmware Upgrade Plan Details Page.
The system will display "Add Firmware Upgrade Activity" page. Consult the screenshot and the table below in order to create a new activity in the system.
Uploading Firmware Image File to DPOD
Before DPOD can use a firmware image, it needs to be uploaded into the DPOD's path that was defined in the system parameter "Firmware Upgrade - Repository Path".
You can use SCP/WinSCP or any other file transfer program to upload the file.
Add Activity Page
Attribute | Is Mandatory? | Description |
|---|---|---|
| Device (or Pattern) | Yes | The Device(s) to upgrade, enter a specific device, pattern with asterisk or a list of devices or patterns See Using Patterns for Device and Domain Names in the Maintenance Concepts page |
| Allow Major Release Downgrade | No | Can the device be downgraded within the same major release? For example, 7.5.1.5 to 7.5.1.3 Other types of downgrade are not supported or trying to upgrade to the same firmware level are not supported. |
| Allow Features Incompatibility | No | Allows to upload a firmware image file that is missing features that are found on the device (Tibco-EMS and DCO-Oracle) Uploading an image that contains features that are not found in the device is not supported. |
| Pre-Action Script | No | A user defined script to run before the task is executed. See user defined scripts for more information |
| Pre-Action Quiesce | No | Should the device(s) be quiesced before it is restarted. The device(s) will be always quiesced before the upgrade is executed, whether or not you checked this option This option only controls the quiesce that happens before the optional restart. |
| Pre-Action Restart | No | Should the device(s) be restarted before the upgrade starts. Restarting the device before firmware upgrade is recommended |
| Seconds to wait after restart | Yes (if restart requested) | How long (in seconds) to wait after restart and before issuing the quiesce request and upgrading the firmware. This parameter is used for situations where the monitored device does not enter "ready" state immediately after device restate. |
| Pre-Action Quiesce | Yes | Always checked, this option cannot be changed. The device will be quiesced before the upgrade starts. The timeout value that is passed to the quiesce SOMA is controlled by a system parameter (see maintenance configurable parametersfor more information) |
| Image File | Yes | The firmware image file, only scrypt3, scrypt4 and tar.gz types are supported Click the Three dots button to open the file selection window, the window will show all image files that were found in the Repository path (see "Firmware Upgrade - Repository Path") If a new file was just uploaded, close and re-open the window to refresh the list. |
| Upgrade timeout in seconds | Yes | How long to wait before DPOD will mark the upgrade execution as failed. For example, if DPOD did not receive any response from the upgraded device after 30 minutes, it will mark the execution as failed, so a syslog/email will be sent. |
| Post-Action Unquiesce | No | Always checked, this option cannot be changed. |
| Post-Action Script | No | A user defined script to run after the task is executed. |
| Error Policy | Yes | Select how this activity handles errors. |
| Accept License Chechbox | Yes | Accept IBM's license is needed before firmware upgrade |
Edit, Delete or Reorder Activities
The Firmware Upgrade Plan Details Page allows the user to edit, delete or reorder activities.
