EP03-300-200
December,
2003
Release 200
Version 1.0
Experion PKS CEE-based Controller Specifications and Models
14
An on-process migration is performed through a migration wizard, which will perform the following high-
level actions:
1. The migration wizard first focuses on the secondary chassis.
2. The secondary chassis is interrogated to determine the module types and versions. All
modules that require firmware updates will be updated automatically during the migration
process.
3. The static database is loaded after the new controller firmware is loaded.
4. Next, the dynamic information is synchronized between the primary (executing the old
software) and the secondary (executing the new software). During this limited period, the
control is frozen (several seconds). When the transfer of all dynamic data is complete, a
failover occurs (identical to a normal failover between redundant controllers) and the
secondary chassis using the new software will assume the role of primary controller.
5. Finally, the ‘old’ primary chassis is migrated and will then synchronize with the primary
controller after which a normal redundant controller pair exists.
In addition, the Experion PKS system supports release interoperability, which provides the flexibility to
leave controllers on an older release while they remain interoperable with the new server and
controllers in the system. Each Software Change Notice describes in detail which releases are
interoperable.
