ECSAs can be disconnected from the Platform during the upgrade of. This will allow them to continue processing on the current version throughout the upgrade and the downtime will be minimized. The ECSAs will be upgraded at restart.
There There are certain prerequisites that need to be fulfilled in order to safely complete the upgrade of:
- The traffic protocol must support failover. If not, restarting the ECSAs may cause loss of data, unless the traffic is redirected first.
- You cannot keep ECSAs running when there have been changes in the storage models for If you are running any configuration that contains agents or services such as Aggregation, Inter Workflow, Usage Management, PCRF, or Routing Control. When the platform is upgraded and the ECSAs are restarted, existing data is converted to the updated storage model. If a problem occurs at this point and a downgrade must be performed, the previous version will not be capable of handling the data generated by the new version.
For information about changes in the storage models, see the Release Notes.
...
- , you MUST check on the Release Notes for any internal storage model changes or additional migration steps. Internal storage models involve the storing of metadata and internal data used by the Platform or ECSA related to the following agents and services.
- If there is internal storage model change, you must shutdown the ECSA. Once the upgrade is done, the upgraded internal storage model will not be able to rollback to the old version.
- If there is any migration steps, you must shutdown the ECSA and perform the migration steps. Once the upgrade is done, the migrated data will be stored in the new model and will not be able to rollback to the old version.
| Warning |
|---|
It is important to go through the Release Notes under section Important Information and Known Issues to see if there are any changes related to the internal storage models or migration steps that might impact to your solution upgrade. |