1. User Guide for the Enterprise Edge and Core Plug-in
  2. Configure and Apply Software and Bootloader Upgrades to Devices
  3. Work Flow Processing Scenarios for an Upgrade Work Order

Work Flow Processing Scenarios for an Upgrade Work Order

An upgrade work order contains a predefined work flow that lists the execution procedure sequentially in a step-by-step process. As the upgrade work order is executed, each procedural step is tracked in the Device tasks table, under the Progress column. The following sections outline the different upgrade work-order scenarios:

Upgrade for a Standalone Device

  1. The available space is checked for the device.
  2. The current device software and/or bootloader image is archived.
  3. The running configuration data file is retrieved for backup.
  4. The software and/or bootloader image is pushed to the device.
  5. Call shedding is performed.
  6. The configuration file is converted to ACP XML format if necessary.
  7. The image name in the boot parameters for the device is edited.
  8. The device is re-booted.
  9. The Oracle Communications Session Element Manager plugin updates the device information in the Oracle Communications Session Delivery Manager server.

Upgrade for a High Availability Device Pair

  1. The available space is checked for both devices.
  2. The status and health is checked for both devices.
  3. The current device software and/or bootloader image is archived.
  4. The running configuration data file is retrieved for backup.
  5. The software and/or bootloader image is pushed to both devices.
  6. The configuration file is converted to ACP XML format if necessary.
  7. The image name in the boot parameters for the standby device is edited.
  8. The standby device is re-booted.
  9. The health of the standby device is checked.
  10. A fail-over is forced and the standby device becomes the active device.
  11. The image name in the boot parameters for the new standby device is edited.
  12. The new standby device is re-booted.
  13. The Oracle Communications Session Element Manager plugin updates the device information in the Oracle Communications Session Delivery Manager server.

Rollback for a Standalone Device

Note:

The rollback steps below are for a successfully-executed device task and may vary if the rollback process is initiated when a work order fails or is aborted during the execution process.
  1. The files are pushed to the standalone device.
  2. Call shedding is performed.
  3. The image name in the boot parameters is edited.
  4. The device is re-booted.
  5. The device information in Oracle Communications Session Delivery Manager is updated.

Rollback for an HA Pair

Note:

The rollback steps below are for a successfully-executed device task and may vary if the rollback process is initiated when a work order fails or is aborted during the execution process.
  1. Files are pushed to both devices.
  2. The status and health score are retrieved from both devices.
  3. The image name in the boot parameters from the standby device is edited.
  4. The standby device re-boots.
  5. There is a switch-over to a standby device.
  6. The image name in the boot parameters is edited from the standby device.
  7. The new standby device is re-booted.
  8. The device information in Oracle Communications Session Delivery Manager is updated.