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, minimizing downtime. The ECSAs will be upgraded at restart.
There are certain 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 data loss
of data, unless the traffic is redirected first.
If you are running any configuration
that containscontaining agents or services such as Aggregation, Inter Workflow, Usage Management, PCRF, or Routing Control, you MUST check
onthe 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 an internal storage model change, you must
shutdownshut down 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
shutdownshut down 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
rollbackroll back to the old version.
Notewarning |
---|
Caution! |
Scroll ignore | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
Scroll pagebreak |
---|