Experion PKS R500 Migration Planning Guide

Transcription

1 Experion PKS R500 Migration Planning Guie EPDOC-XX70-en-500E May 2018 Release 500

2 Document Release Issue Date EPDOC-XX70- en-500e May 2018 Disclaimer This ocument contains Honeywell proprietary information. Information containe herein is to be use solely for the purpose submitte, an no part of this ocument or its contents shall be reprouce, publishe, or isclose to a thir party without the express permission of Honeywell International Sàrl. While this information is presente in goo faith an believe to be accurate, Honeywell isclaims the implie warranties of merchantability an fitness for a purpose an makes no express warranties except as may be state in its written agreement with an for its customer. In no event is Honeywell liable to anyone for any irect, special, or consequential amages. The information an specifications in this ocument are subject to change without notice. Copyright Honeywell International Sàrl 2

3 Contents 1 About this guie Relate ocuments Special terms Before you begin Experion migration concepts Migration license requirements About the migration tools Overview of Upgrae Tool Migration Reainess tool ERDB Consistency Checker BOOTP Checker Install Sequencer Controller Migration wizar Dual primary state History collection uring ual primary state About OPC Integrator, script engines, an SCADA channels Migrating custom isplays Migrating Display Builer isplays Migrating HMIWeb isplays Upating the HMIWeb solutions pack Migrating trens Excel ata exchange System interoperability concepts Interoperability Server interoperability eserver interoperability Domain controller interoperability BOOTP server interoperability DSA an OPC interoperability Controller interoperability Controller CDA/exchange peer-to-peer connections Configuration Stuio interoperability Using Configuration Stuio uring server migration (ual primary state)

4 CONTENTS Using Configuration Stuio uring multi-cluster migration Saving an rebuiling checkpoints Using the Search utility Using Display Builer an HMIWeb Display Builer Station interoperability Displays Network Detail isplays Enterprise Moel Database (EMDB) interoperability Inter an intra cluster interoperability Planning migrations Develop a migration plan Consierations while migrating non-reunant Experion systems an control components Consierations for migrating network-api base customer applications Migration Planning Checklist Develop a migration strategy System migration planning Cluster migration planning State of the process Network topology consierations Develop a migration timetable Migration time estimates Review software requirements Migrating other Honeywell proucts an applications Migrating non-experion thir-party applications Review harware requirements Choose whether to use Experion Software Installation Server (ESIS) About Experion Migration Storage Noe (EMSN) Ientify a location for the EMSN Consierations for using EMSN hoste in a omain Consierations for planning network topology changes Review migration consierations Consierations for migrating integrate Experion-TPS noes Consierations for migrating DSA-connecte Experion/TPN systems Consierations for migrating secure Experion noes Consierations for multi-cluster migrations Consierations for partitioning har rives using Experion PKS System Initialization meia About pre-installe SQL scenario Planning time synchronization uring migration NTP servers (time source for Series C control harware) Time check on system before you start migration

5 CONTENTS 4.11 Ientify security policy changes Installing the omain controller package Workstation package Cancelling a migration On-process migration of servers/clients Off-process migration of servers/clients On-process migration of controllers Off-process migration of controllers Starting migration Selecting a migration path On-process migration of servers/clients On-process migration of controllers Migration scenarios Server/client migration scenarios Controller migration scenarios R400.x, R410.x, R430.x, R431.x, an R432.xmigration Using tools to verify upgrae reainess Main winow File menu Reainess Check menu Reainess checks for migrating servers Reainess checks for migrating controllers Reainess checks for migrating ACE, SCE, EHG or SIMIOLIM noes Generating reports Saving reports Printing reports Reviewing reports Reviewing faile items R510.x migration reference Qualifie migration paths R510.x server/client migration paths R510.x controller migration paths R510.x system interoperability Interoperability summary Software requirements Software meia requirements Microsoft an other Experion upates Reapplying software patches on servers Total Plant Network (TPN) software Honeywell Experion PKS Localization Meia SCADA system communication protocols

6 CONTENTS 7.4 Harware requirements Experion installation space requirements Experion migration space requirements Experion Migration Storage Noe (EMSN) space requirements Multi-cluster migration scenarios R400.x, R410.x, R430.x, R431.X, R432.x an R510.x systems Experion High Security Policy changes Migration Planning Checklist Collection System questions Checklist 1 - Experion an Winows Software Checklist 2 - Other Honeywell software Checklist 3 - Thir Party software Checklist 4 - System architecture guielines Checklist 5 - Cluster an noe sequence questions Checklist 6 - Server specification sheet Checklist 7 - Station specification sheet Checklist 8 - Domain Controller specification sheet Checklist 9 - Controller Notices

7 1 About this guie The Experion Migration Planning Guie assists you in unerstaning an planning the migration of your Experion system. Specifically, this guie provies information an guiance for migrating Experion systems from R400.x (with or without patches), R410.x (with or without patches), R430.x (with or without patches), R431.x (with or without patches) an R432.x (with or without patches) system software to Experion release R510.x software. For exact migration paths supporte to target point release, refer to the latest target point release Software Change Notice (SCN). For example, refer to the latest target release SCN. Attention Migration from R3xx to R500.x requires multiple hops. However, DSA interoperability between R3xx an R500.x is supporte. Refer to Enterprise Moel Database (EMDB) interoperability section for more information. Revision history Version Date Description A November 2016 Initial release of the ocument. B February 2017 Upate section 7, R500.x migration reference. C August 2017 Upate the ocument to inclue the information regaring DSA interoperability between R3xx an R500.x is supporte. 7

8 1 ABOUT THIS GUIDE Version Date Description D January 2018 Upate PAR #1-5FYESNX information in the ocument. E May 2018 Ae a note in Qualifie migration paths section. Prerequisite skills It is assume that you are familiar with the operation of Experion system software an the plant processes which Experion controls, Microsoft Winows operating systems, an network aministration tasks. Intene auience This guie is intene for people who are responsible for planning, aministering, an operating the Experion system an the process which it controls. These people may inclue Plant Managers, Process Engineers, an System Aministrators. How to use this guie? This guie is organize into the following sections. Topic Experion migration concepts on page 15 System interoperability concepts on page 29 Planning migrations on page 43 Starting migration on page 75 Description Defines Experion migration, server migration, controller migration, qualifie migration paths an the applications, an tools evelope to automate various tasks for migration. Introuces the concept of interoperability within the Experion system. Specific rules for release interoperability an the restrictions of interoperability between system functions are escribe. Contains important planning information an topics that require consieration by users while planning to conuct on-process or off-process migrations. Provies information about the starting point for conucting a migration an presents typical migration scenarios. 8

9 1 ABOUT THIS GUIDE Topic Using tools to verify upgrae reainess on page 81 Description Defines the Migration Reainess tool an Upgrae tool. In aition, the reports generate using the Migration Reainess tool an Upgrae tool. R510.x migration reference on page 105 Provies release specific reference content for planning migration. Migration Planning Checklist Collection on page 139 Contains all the checklists that may be require while performing migration. 9

10 1 ABOUT THIS GUIDE 1.1 Relate ocuments The following ocuments an sources contain aitional information relate to installation, upgrae, an migration of Experion system software an firmware. It is recommene to have these ocuments reaily available for reference. Software Change Notices (SCN): The Software Change Notice provies information about new features, problems resolve, known issues, software component versions, an firmware revisions for a release/point release. In aition, the ocument also contains important changes from previous release, special consierations in installation or migration, an any last-minute ocumentation upates. Although the SCN is provie in printe form, you must always ownloa the latest version of the SCN from the Honeywell Process Solutions website ( The following are the three types of SCNs. Experion General Release Software Change Notice Experion Support Software - Software Change Notice Experion Point Release Software Change Notice Site-specific migration guies (R400.x, R410.x, R430.x, R431.x, R432.x an R500.x to R510.x): For migrations from R400.x onwars, you can generate a site-specific migration guie using the Upgrae Tool. As per the site configuration, the Upgrae Tool combines the migration guies available on the Experion PKS Upgrae Tool components meia for the noes/moules in the Experion cluster. This ocument is automatically generate by the Upgrae Tool. Starting from R431.2, the latest point release Experion PKS Upgrae Tool components meia(upgrae_tool_components_meia.iso) is available as an ISO image on Honeywell Process Solutions website ( support). Extract this ISO image using ISO extraction software to create a DVD or copy the extracte files to local system an install the latest Experion PKS Upgrae Tool components meia. For example, you can use Virtual Clone Drive software for extracting the contents to a meia. If you are migrating to any point releases, refer to the applicable point release SCN. Experion Upgrae Tool User's Guie: This guie escribes the proceures to install an configure the Upgrae Tool. Experion Upgrae Tool Component meia Software Change Notice: This Software Change Notice contains information about Experion PKS Upgrae Tool Components meia. Getting Starte with Experion Software Guie: This ocument etails the prerequisites an specific tasks require to set up the Experion system. You can also use the ocument as a reference when you a new components to your system. 10

11 1 ABOUT THIS GUIDE Experion Software Installation User's Guie (SIUG): This ocument guies you through the stanar Experion software installation. The SIUG is available in the Experion PDF Collection meia. Experion Supplementary Installation Tasks Guie (SITG): This ocument escribes the aitional tasks to be performe once you have complete an initial installation or upgrae of Experion. This ocument is available in the Experion PDF Collection meia. Control Harware an I/O Moule Firmware Upgrae Guie Integrate Experion-TPS Noes (ES-T, ESVT, & ACE-T) User's Guie: This ocument escribes supplementary installation tasks that must be one before you use T-Noes on an Experion system. In aition, it escribes configuration tasks necessary for T-Noes. This ocument is available in the Experion PDF Collection meia. OneWireless Guies: For more information on OneWireless integration with Experion, refer to the Experion PKS OneWireless Migration User's Guie an Experion PKS OneWireless Integration User s Guie available in the HPS Support website. PDF Collection In the PDF Collection, you can search an view the Experion ocumentation in PDF format. The PDF Collection contains all Experion ocuments, incluing installation, migration, an SCN ocuments. Aitional information about the Experion system can be foun in the HPS Support website. 11

12 1 ABOUT THIS GUIDE 1.2 Special terms The following terms efine here are unique to the subject presente in this guie. Unless specifically note, the term Migration pertains to both on-process migration an off-process migration. Base release Controller Migration wizar Dual Primary Server state Engineering Repository Database (ERDB) Enterprise Moel Enterprise Moel Database (EMDB) ERDB Consistency Checker Experion Control Cluster (Cluster) Installation Application Mismatche component Install Sequencer The release version of Experion that is currently in use before the start of a migration. A software application which migrates process controllers an associate control harware to the newer release firmware with minimal user action. A state uring on-process migration where each server of a reunant pair operates as a primary server. Dual primary state allows the checkout an verification of the process using the new release software. The atabase or set of atabases which support the control system evelopment. A hierarchical representation of the Experion system components, the plant's assets an the alarm groups erive from the assets, an alarm groups efine in the EMDB. A atabase that contains the source escriptions of the plant's assets an alarm groups use in the Enterprise Moel. Engineering Repository Database Consistency Checker. A tool to valiate the internal consistency of the ERDB. An operational unit of an Experion control system consisting of Experion server or reunant server pair, associate clients (Flex Stations, Consoles, an Extene Stations), controllers, an optional other noes, such as ACE, EHG, PHD, terminal server, an eserver. A software application that installs the Experion system software with minimal user action. Any component that is installe with or is running at a release other than the target system release. A software wizar which migrates Experion system components to the newer release system software. 12

13 1 ABOUT THIS GUIDE Experion Migration Storage Noe (EMSN) Migration Reainess Tool (MRT) Off-Process Migration On-Process Migration (OPM) Reunant Chassis Pair (RCP) Release interoperability Supervisory Control An Data Acquisition (SCADA) Server A an Server B System migration Target release A location use for storing ata (atabases, system configuration, operating system preferences, an so on) when migrating an Experion platform. An software wizar that performs checks on servers, controllers, an other system components to verify if they are reay for migration. Migration of an Experion control system or migration of an Experion system component while it is not controlling the process an there is no view of the process. NOTE: Integrate Experion-TPS noes can maintain view to the process through TPN while the Experion off-process migration is in progress. Migration of an Experion control system or migration of an Experion system component while maintaining view an control of the process. This is achieve by utilizing reunant system components. A pair of moules, such as two FIMs, IOLIMs or other chassis I/O moules that support reunancy, each installe in reunant chassis (Primary an Seconary). The ability of system components to interact in a stable manner when operating with ifferent releases. SCADA is an Experion application for process control. It is esigne to interface with serial evices such as PLCs an Honeywell TPS. The stanarize names of the reunant servers. Server A operates as primary before the start of on-process migration, an Server B operates as the backup. The migration of Experion control system from one release to a newer release. The release version of the system software or firmware after migration is complete. 13

14 1 ABOUT THIS GUIDE 1.3 Before you begin Experion contains substantial infrastructure that supports the migration from one release to another, while still maintaining process control. However, on-process introuces complexity along with beneficial flexibility. HPS Migration Center of Excellence/Technical Assistance Center The HPS Migration Center of Excellence (COE) or your local Honeywell Technical Assistance Center (TAC) is set up to hanle your questions an requests when planning an Experion system migration. Contact the HPS Migration Center of Excellence through at or call the Honeywell Technical Assistance Center at , an request assistance when planning to perform on-process migration of Experion software. The COE helps in planning the activities an provies expert guiance. Arrangements can also be mae to have Honeywell personnel at your site to assist you with migration. The COE provies a site survey to be complete along of migration software tools that can be run on the system to help evaluate the system reainess for migration. You must forwar the complete site survey along with the log files generate as a result of running the migration tools to the COE for evaluation by the Honeywell engineers. Honeywell can then provie further guiance on the subsequent actions to be taken in preparing the system for migration. 14

15 2 Experion migration concepts Experion system migration is efine as the upgrae of Experion system components, such as SERVERS, CLIENTS, ESERVERS, ACE, SCE, an SIMIOLIM noes to the new release system software. The firmware for I/O control harware an Experion controller is also upgrae as part of system migration. Migration can either be performe on-process, where Experion components are upgrae while maintaining a view an control of process operations; or off-process, where Experion system components are taken off-line before they are upgrae to the new software release. On-process migration can be performe only on reunant Experion components, specifically reunant servers, controllers, an reunant control moules. System migration is performe in two major stages. Server/client migration (Software migration of Experion servers an clients). Controller migration (Firmware migration of Experion process controllers an I/O harware components). Server/client migration Server migration is the upgrae of Experion servers, client noes, an their loae software. Migration can inclue upgraes of the computer's operating system or computer harware - such as aing more memory to a server, or even upgraing to a newer computer (platform harware). Experion server an client noes are migrate first, before other Experion noes, such as eservers, ACE noes, an controllers. The Experion Install Sequencer is use for upgraing the Experion servers an clients. During on-process migration, the migrate servers an clients operate at the target release while the controllers an other control harware operate at the base release. This is because the server migration must be complete before the associate controllers' migration. Interoperability is necessary between the servers an controllers to maintain system operations. In systems that contain multiple Experion clusters, interoperability is necessary because clusters may be migrate iniviually. During on-process migration it is likely that some clusters operate at a newer release, while other clusters continue to operate at the oler 15

16 2 EXPERION MIGRATION CONCEPTS release. Interoperability between these clusters is maintaine through DSA communications uring migration. Controller migration Controller migration is the upgrae of firmware installe in Experion control harware. Only control harware that is reunant can be migrate on-process. Non-reunant control harware can only be migrate off-process. The Controller Migration wizar application is use for performing controller migration. The following is a summary of the Experion control harware that supports migration. Controllers: C200/C200e 1 (CPM), Experion Control Harware C300 (CC-PCNT01/CC-PCNT02) C300 with EHB personality configure Note: Other controllers (such as, TPN controllers) can be upgrae inepenently of Experion migration. They are upgrae using the existing proceures escribe in TPN ocumentation an are not covere in this ocument. EHPM can be migrate using Controller Migration Wizar. Interface Moules: RM, IOLIM, FIM, FTEB, CNI, LIOM, Series C FIM4, FIM8 an PGM. I/O Moules: Series C IOMs Series A IOMs, Series H IOMs (nonreunant) Comment C200 Controller inclues a Reunancy Moule (RM) an may contain any of the following interface moules: IOLIM, FIM, FTEB, CNI, LIOM. These moules support reunancy an can be migrate on-process. These moules support reunancy an can be migrate on-process. Non-reunant moules support only offprocess migration. The Controller Migration wizar is use for migrating process controller firmware an control harware firmware. This wizar automates many of the tasks performe uring controller migration an is use for both on-process an off-process migration. It can be accesse from the Controller menu in Control Builer. The Controller Migration wizar allows you to select reunant pairs of components for on-process migration. For example, when a Reunant Chassis Pair is selecte for 1 Reunant C200/C200e Controllers, which comprise a Reunant Chassis Pair (RCP), contain ientical chassis moules. 16

17 2 EXPERION MIGRATION CONCEPTS migration, all moules installe in the primary an seconary chassis are migrate. When a single pair of FIMs installe in a reunant chassis are selecte for migration, both moules are migrate. Non-reunant I/O components associate with the controllers are migrate off-process; after the controller an/or after the I/O interface moules are migrate. Extene on-process migration support Prior to R400.1, the on-process migration was supporte from an N-1 to N (for example, from R30x to R31x) releases. With R400.1, OPM is supporte from both N-1 an N-2 releases to N (for example, from R30x to R400.1). This reuces the nee for an intermeiate upate uring migration from an N-2 release to N release.. From R430.1, OPM is supporte from N-1, N-2, an N-3 release to N (for example, from R400.x to R500.x). In R500.x, DSA interoperability is supporte from R3xx. Direct migration to point releases You can migrate your PC noes from Experion R410.x,R430.x, R431.x, R432.x, R500.x, an R501.x to 510.x without stopping at the base release (Experion R510.1). For example, you can migrate irectly from Experion R410.x to Experion R510.2 (instea of migrating to R510.1 first an then upgraing to R510.2). With earlier releases, you were require to migrate the system to the base release (Experion R400.1) an then upgrae to the require point release Experion R For more etails on server migration paths, refer to the server migration paths section in the SCN. For more etails about migration, refer to the site-specific migration guies. Attention 1. This feature is qualifie only for R400.1, R410.1, R430.1, or with point releases on them. For example, R400.1, R400.2, R400.3, R410.1, R410.2, R410.3, R430.1, R430.2, R430.3, an so on. 2. This feature is qualifie if iniviual server patches or TPN server patches are installe on the point releases. 3. This feature is not qualifie if there are Controlle Patch Controlle Release or Hotfixes installe on the system. These patches or hotfixes have to be uninstalle from the PC noes (excluing the controllers/ios), an the cluster (incluing controller/ios) have to be upgrae to the qualifie point release before using this feature. For more information, contact HPS Migration Center of Excellence (COE). 4. This new feature oes not impact the earlier rule of irect controllers/ios migrations from any point release or patch to any target release as mentione in the site-specific migration guie an scenario-specific migration guie. For qualifie controller migration paths, refer to the Controller Migration Paths section in the SCN. 17

18 2 EXPERION MIGRATION CONCEPTS Direct migration support from Controlle Patch Control Release or hotfix to point release For R500.1, you can irectly migrate from CPCR or hotfix to appropriate target point release without uninstalling or upgraing the patch on the base release. You can irectly migrate from R400.x (with or without hotfixes), R410.x (with or without hotfixes), R430.x (with or without hotfixes) onwars to R431.4, R432.1, an subsequent releases. For example, you can migrate from R431.2 CPCR2 to R For more information, refer to the respective latest SCN. Spare IO moule migration With R400.1, the spare parts connecte to the local chassis an remote chassis for the C200/C200E controllers can be migrate separately from the Controller Migration wizar. A new option, off process migration of spare parts in CPM chassis is ae to the Controller Migration wizar. This enables migration of the I/O moules that are connecte to a local or remote chassis an are not configure in the Control Builer (CB). The option can be selecte from the available migration options ialog box in the Controller Migration wizar. This option is enable for the following types of configuration. Reunant C200/C200E controller with spare parts connecte in remote chassis. In the remote chassis, at least one IO moule must be configure in the CB to etect the spare parts. Non-reunant C200/C200E controller with spare parts connecte to local chassis. Non-reunant C200/C200E controller with spare parts connecte to remote chassis. In the remote chassis, at least one IO moule must be configure in the CB to etect the spare parts. Non-reunant C200/C200E controller with spare parts connecte to the local chassis an remote chassis. In the remote chassis, at least one IO moule must be connecte. 18

19 2 EXPERION MIGRATION CONCEPTS 2.1 Migration license requirements Starting with Experion R301.3, the OPM license is combine with the Server Reunancy purchasable option. When the reunancy option is purchase, both the reunancy an OPM license information are enable. Controller reunancy is a seconary requirement which must be satisfie; otherwise, the OPM option for controller migration is not enable on the Controller Migration wizar. Before starting the migration, license key is require. 19

20 2 EXPERION MIGRATION CONCEPTS 2.2 About the migration tools Various software applications an utilities have been evelope specifically to help streamline the system migration process by: Detecting system conitions prior to a migration that may cause problems or faults after a migration begins. Detecting inconsistencies in system atabases an system components that may cause errors uring migration. Automating many of the tasks that are performe uring a migration Overview of Upgrae Tool The Upgrae Tool checks the upgrae reainess of the noes an its subsystems in an Experion system. The Upgrae Tool is installe as a part of the Engineering tools installation. If you have reunant servers, Upgrae Tool is installe on Server B. In case of non-reunant server, Upgrae Tool is installe on the only server. The Upgrae Tool oes not epen on any specific Experion topology. In case of a reunant Experion configuration, the Upgrae Tool is run only on the Server B. In case of a nonreunant Experion server configuration, the Upgrae Tool is run on the single Experion server noe. The Upgrae Tool ensures that it oes not overloa the Experion server. Before starting an Experion upgrae, you have to verify the upgrae reainess of the Experion system an prepare it for the upgrae. The Upgrae Tool automates the manual process of preparing the Experion system for the upgrae. After the upgrae is complete, you can run the Upgrae Tool to perform a post-upgrae analysis. Upgrae Tool makes the upgrae reainess process effortless, easy, an error-free. It reuces the manual information gathering time an minimizes the possibility of errors Migration Reainess tool The Migration Reainess Tool (MRT) is a software application that performs prerequisite checks on the system an its components which are necessary to ensure that an Experion system is reay for migration. The MRT is run to check the migration reainess of servers, controllers, I/O chassis an remote chassis moules, an control network platforms prior to starting a migration. After the MRT is run, a report is generate to inicate the reainess of the system an its components for migration. You can ownloa the latest version of the MRT ata files from the Honeywell Process Solutions website at MRT is only use for R31x.x an R400.x Experion releases. 20

21 2 EXPERION MIGRATION CONCEPTS Attention The MRT is not use for SCADA systems ERDB Consistency Checker The ERDB Consistency Checker utility performs checks on the Engineering Repository Database for inconsistencies that may cause problems uring a migration or cause a migration to fail. This utility also etects patches that have to be remove before starting the migration. Run this utility before you start a server migration in orer to etect an eliminate problems which might appear uring or perhaps even after the migration. In aition, run this utility before you begin on-process migration of the controllers. You can ownloa the latest version of this utility from the Honeywell Process Solutions website at Tip The ERDB Consistency Checker is not use for SCADA systems. Prior to R430.1, you nee run ECC as batch file. Starting from R430.1, ECC is integrate in Configuration Stuio. ECC must be starte from Configuration Stuio.From R500.x, ECC also provies an option to repair the inconsistencies if one or more repair scripts are available an installe for a faile check.for more information about the integration of ECC in Configuration Stuio, see the Upgrae Tool User's Guie BOOTP Checker The BOOTP Checker utility is use for etecting the BOOTP server on the FTE an ControlNet (through Ethernet) communications network in a process system. This tool also queries the local atabase to verify whether the NTP servers are configure on the local server. Use this tool before a migration, to check whether there are multiple BOOTP servers configure on the network. There must be only one BOOTP server running on the control network. If multiple BOOTP servers are running, BOOTP Checker verifies that they are proviing the ientical information. You must run the BOOTP checker after migrating one server an before migrating any controllers. You can ownloa the latest version of this utility from the Honeywell Process Solutions website at Tip The BOOTP Checker is not use for SCADA systems. 21

22 2 EXPERION MIGRATION CONCEPTS Install Sequencer The Install Sequencer is a software application that coorinates the migration of system software to the target release for servers an clients. The Install Sequencer automates many of the migration tasks that were performe manually in the previous releases. The application is run on a server/client to be migrate an it safely hanles system atabase an configuration information so that it can be reloae to the server after the new release system software is installe. It also allows for harware an operating system upgraes uring the migration process Controller Migration wizar The Controller Migration wizar migrates (upgraes) the firmware in Experion control harware to a newer release. Experion control harware inclues process controllers, I/O interface components, an associate I/O moules. The Controller Migration wizar can be accesse from the Control Builer. 22

23 2 EXPERION MIGRATION CONCEPTS 2.3 Dual primary state At one point uring server migration, reunant servers which are migrating achieve a ual primary state, where Server B has been migrate an is operating with the new release, an Server A is operating with the base release. This state allows each server to operate as a primary an provie a view of the process. You can perform testing on station an consoles that have been migrate to the new release, to verify the control an view of the process on the new release History collection uring ual primary state During ual primary state, the servers are at ifferent releases an are not synchronize. History is collecte by both servers to ensure that there is minimal loss of history ata after migration. Also, the ual primary state allows a user to check the operation of the migrate server on the target release against the base release primary server before committing to complete the migration. Therefore, ual primary state is an important conition of on-process migration, which is present for some uration of time an can be use for verifying the operations of the migrate server. However, the history collecte by both servers may create an increase loa on controllers which are being polle twice as often for the operating ata. This coul cause an overloa on the controllers if the base loa is alreay near the specification limit. There is also an increase in the network traffic while in the ual primary state because of the controllers polling twice for the same history ata. 23

24 2 EXPERION MIGRATION CONCEPTS 2.4 About OPC Integrator, script engines, an SCADA channels Experion OPC Integrator normally runs on reunant servers. During on-process migration when Server B is stoppe an is being migrate, OPC Integrator operates on Server A. After Server B is migrate an is operating with Server A in ual primary state, all groups as well as script engines an SCADA channels are loae to Server B, but are isable. OPC Integrator on Server A continues to operate. When Server A is stoppe to be migrate, the OPC Integrator groups, script engines, an SCADA channels on Server B must be enable manually to continue the ata transfer, as it oes not happen automatically. 24

25 2 EXPERION MIGRATION CONCEPTS 2.5 Migrating custom isplays Attention Systems that use customize (user-efine) isplays create in Display Builer (.sp files) an/or HMIWeb Display Builer (.htm files) must follow the important consierations explaine in this section. Not following these recommenations may result in the loss of customize isplay files. Generally, you must back up any file that contains user-efine information, (such as customize isplays) before starting migration. These files may not be migrate forwar as part of the migration process an may nee to be reinstalle after migration. Any custom isplay files must be manually save before migration an then restore after migration because these files may be store in a user-efine location an may not be migrate forwar. For example, you must back up an save the following files before starting migration. Point etail isplays such as DI, Numeric, flag, an fielbus. Faceplates such as DI, Numeric, flag, an fielbus. Custom Station setup an menu configurations (*.stn an *.stb files). *.css files *.htm files Migrating Display Builer isplays Custom Displays built using Display Builer (.sp files) can be available on an upgrae Experion Station provie that: The isplays are custom isplays (system isplay interoperability is not supporte). The references to server ata in the custom isplays are limite to point parameters an the ata in user tables. In Display Builer when you save a isplay (.sp file), you can specify the isplay release for the file. This allows you to save the isplay in an ol format which allows you to use the isplay file with an oler release of Station. After a isplay file is upate or save for a newer release, it cannot be isplaye on a Station operating on an oler release Migrating HMIWeb isplays You must use either HMIWeb Display Builer or the Bulk Display Migration tool to migrate all custom HMIWeb isplays (.htm files) to the current Experion release. 25

26 2 EXPERION MIGRATION CONCEPTS After you migrate a noe to the target release you must use either HMIWeb Display Builer or the Bulk Display Migration tool to migrate the isplay files before you can isplay the custom or user-efine HMIWeb isplays (.htm files) in Station. For example, when a isplay file (create in an oler release) is opene using a new release of HMIWeb Display Builer, the file is automatically converte to the new isplay format by saving the file in the new format. If you want to upate the HMIWeb isplays in bulk, you can use the Bulk Display Migration tool (bulkisplaymigrator.exe) Upating the HMIWeb solutions pack HMIWeb Solution Pack (HMIWeb SP) is a comprehensive avance shapes library esigne to allow customers to implement custom Experion isplays consistent with the Abnormal Situation Management (ASM) Consortium s isplay guielines an the sitespecific requirements. The HMIWeb SP an HMIWeb SP-base graphics can be migrate accoring the HMIWeb SP migration instructions. However, the migrate HMIWeb SP shapes are not the same as the R500.1 HMIWeb SP shapes. Any new functionality introuce with the R500.1 HMIWeb SP is not present in the migrate isplays. Any new functionality available with R500.1 HMIWeb SP can be obtaine by replacing the previous shapes with the R500.1 HMIWeb SP shapes. The HMIWeb SP migration instructions, installation guielines, an the R500.1 HMIWeb SP is part of Experion R500.1 software meia kit. Honeywell personnel can ownloa the stanar R500.1 HMIWeb Solution Pack available at teams.honeywell.com/sites/techopskx/gfo/eex/hmi/solution%20libraries/forms/ Solution_Library_view.aspx. Starting from R440, HMIWeb Solution Pack installation is integrate with Experion installation. If the feature is alreay installe your system, then software is upgrae to a new version as part of Experion installation Migrating trens Tren object plot numbers in custom isplays may not work as expecte after migrating the isplays, if you are migrating from a release prior to R300. Prior to R300, tren objects assigne plot IDs, starting from the number 2. However, after R300 tren objects assign plot IDs from the number 1. If your isplay scripts a a plot an then reference the plot using the return plot ID, or if you use the GetPlotIDFromPlotNumber metho on the trendata object, there is no issue with your custom isplays. However, if your scripts irectly access a plot, using the plot ID number, you may experience the issue of the script setting the range of the 2n plot in the tren instea of the first plot. 26

27 2 EXPERION MIGRATION CONCEPTS Here is an example of a script that irectly accesses a plot. im xlow, xhigh, ylow, yhigh chart001.getplotvisiblerange 2, ylow, yhigh, xlow, xhigh chart001.setplotvisiblerange 2, 0, 20, xlow, xhigh This script sets the range of the 2n plot in the tren (if it exists), rather than the first plot in the tren, which was the intention of this script when use in systems prior to R

28 2 EXPERION MIGRATION CONCEPTS 2.6 Excel ata exchange If Microsoft Excel is installe, the MS Excel ata exchange can be restore to an Experion noe either uring or after migration of the noe. Restoring the MS Excel ata exchange uring migration requires that you install MS Excel an set up ata exchange on the noe after the installation or reinstallation of the operating system, an before the upgrae/installation of the new release of Experion is starte. MS Excel can be installe after migration of the Experion noe, but you may encounter errors uring the migration; (just click OK to continue an complete migration). See the section Setting up Microsoft Excel reports in the Supplementary Installation Tasks Guie for the proceure to restore MS Excel ata exchange on an Experion noe. 28

29 3 System interoperability concepts Relate topics Interoperability on page 30 Server interoperability on page 32 eserver interoperability on page 33 Domain controller interoperability on page 34 BOOTP server interoperability on page 35 DSA an OPC interoperability on page 36 Controller interoperability on page 37 Configuration Stuio interoperability on page 38 Station interoperability on page 40 Enterprise Moel Database (EMDB) interoperability on page 41 Inter an intra cluster interoperability on page 42 Server interoperability on page 32 Controller interoperability on page 37 Domain controller interoperability on page 34 eserver interoperability on page 33 Enterprise Moel Database (EMDB) interoperability on page 41 Controller CDA/exchange peer-to-peer connections on page 37 Interoperability summary on page

30 3 SYSTEM INTEROPERABILITY CONCEPTS 3.1 Interoperability Interoperability is efine as the ability of system components that are loae an operating at ifferent releases of software to be compatible an interact in a stable manner. For example, a server which is loae an operating with Experion R500.x software is able to communicate with a process controller that is operating with Experion R400.x firmware. Release interoperability When you perform on-process migration, reunant servers are migrate to the target release first. Reunant controllers can be migrate later to the target release. There is a perio of time when servers are migrate an are operating with the target release software, an the controllers, which are not migrate, are operating at the original release (not even the base release from which the servers migrate). Interoperability is also among controllers an in general between any moules that are operating on ifferent releases. Release interoperability may not be necessary when you migrate a system off-process; that is if all system components are off-line or are migrate before restarting the process. Till R310 release, Experion was supporting only two-way interoperability. Starting from R400.x, Experion supports three-way interoperability. For example, R500.1 release can communicate with R400.x, R410.x, R430.x, R431.x, an R432.x at the same time. Interoperability rules Release interoperability within Experion systems are governe by a set of rules an restrictions. Connection between servers an clients, such as stations, operating at ifferent Experion releases is not supporte. Servers an clients must be operating with the same release to communicate an operate together. On-process migration begins when you migrate Server B of a reunant server pair to a new release. Next you must migrate a client to the new release an then connect it to Server B so that you have a view of the process on Server B which is operating on the new release. Servers must be migrate to the new release before all other moules. Servers operating at a newer release can interoperate with other moules running at an oler release; with the exception of stations. For interoperability, the stations have to be on the same release as the server. When the other moules excluing stations are upgrae, the upgrae moules can interoperate with the server which must alreay be on the target release. The upgrae moules can also inepenently interoperate with the rest of the moules which may be operating on the original release or on the target release. 30

31 3 SYSTEM INTEROPERABILITY CONCEPTS With R400, Experion supports three way interoperability feature. For example, interoperability is supporte if there are servers operating at R510.x, the associate ACE noe is operating at R400.3, an controllers operating at R410.x. 31

32 3 SYSTEM INTEROPERABILITY CONCEPTS 3.2 Server interoperability Server interoperability with server Interoperability between servers in ifferent control clusters operating on ifferent release software is supporte. This interoperability is supporte through DSA an OPC communications. For example, a DSA Server on Release R431.x, (such as an Experion Server or eserver on R431.1 or R431.2) can communicate with other DSA Servers or clients operating on Release R400.x, R410.x, an R430.x, R431.x an R432.x. Server interoperability with client Interoperability is not supporte between servers an clients (Flex an Console Station) operating with ifferent release software. Clients an servers must be operating with the same release software to support full interoperability. For example, an R500.x server cannot connect to an operate with a client operating with 400 software. Server interoperability with controller Interoperability between servers an controllers operating with ifferent release firmware is supporte. For example, an R500.x server interoperates with controllers operating with R400.x, R410.x, R430.x, R431.x, R432.x an R510.x firmware. In aition, there can be patches loae on the controllers on top of these releases. For example, 400.4, 400.5,410.4, 430.2, The R500.x server interoperates with the controllers loae with any of these patches. All release firmwares that are supporte for controller migrations to the target release are also supporte for interoperability with the target release. For the exact releases/point releases/patches from where a migration is supporte to the target release/point release are available in the respective latest General release SCN or the specific point release SCN. Here the server release represents all the applications running in a server (such as Control Builer an real time ata cache) that interact with applications running in a controller, (such as CEEs). Relate topics Interoperability summary on page 110 System interoperability concepts on page

33 3 SYSTEM INTEROPERABILITY CONCEPTS 3.3 eserver interoperability R510.x eserver supports interoperability with R400.x, R410.x, R430.x, R431.x, an R432.x Experion releases. Relate topics Interoperability summary on page 110 System interoperability concepts on page 29 33

34 3 SYSTEM INTEROPERABILITY CONCEPTS 3.4 Domain controller interoperability A omain controller (server) use in an Experion system operates as an inepenent noe an is migrate separately. The interoperability of a omain controller with the Experion server epens on the operating system of the omain controller. Relate topics Interoperability summary on page 110 System interoperability concepts on page

35 3 SYSTEM INTEROPERABILITY CONCEPTS 3.5 BOOTP server interoperability The BOOTP server must be running on the latest release server of the cluster. You must run the BOOTP checker before migrating or rebooting any controllers. 35

36 3 SYSTEM INTEROPERABILITY CONCEPTS 3.6 DSA an OPC interoperability DSA is use for communication between servers. The communication using DSA epens on the interoperability of the servers on ifferent releases. OPC is use to access the controller ata between clusters. The OPC Integrator running in a cluster can access controller ata in the other clusters through the OPC server in the Experion server. These OPC connections also epen on the interoperability of the servers on ifferent releases. The OPC Integrator running in a station, console or Experion server can communicate with internal an external OPC DA servers using OPC DA versions 1.0a, 2.00, an 2.05a. OPC Integrator supports interoperability with all OPC servers. 36

37 3 SYSTEM INTEROPERABILITY CONCEPTS 3.7 Controller interoperability The controllers, communication moules, an simulators can be upgrae in any orer. This is supporte by the R510.x interoperability between ifferent releases of the following Experion moules. C200 C200E C300 (CC-PCNT01/CC-PCNT02) C300 with EHB personality configure FIM FIM4 FIM8 IOLIM LIOM ACE SIM-C200 SIM-C200E SIM-C300 SIM-IOLIM PGM an C ms(turbo Machinery) EHPM EIP EHB Relate topics Interoperability summary on page 110 System interoperability concepts on page Controller CDA/exchange peer-to-peer connections Peer-to-peer controller CDA/exchange between a C200 controller an a later release of a C300 controller works only if the connection is efine (initiate) in the C300 controller. Relate topics Interoperability summary on page 110 System interoperability concepts on page 29 37

38 3 SYSTEM INTEROPERABILITY CONCEPTS 3.8 Configuration Stuio interoperability Interoperability between a client an server operating on ifferent releases is supporte. Using the Configuration Stuio on the client noe, you can connect to a server when both server an client are operating on ifferent releases. However, in such a situation not all tasks are available. For example, an R500.x client can connect to an R310.3 server, but tasks that o not support interoperability are not available. Starting the Configuration Stuio to connect to a system provies only view of the noes that are operating with the same release. Choosing the task Configure Process Control Strategies connects to an ERDB server which is at the same release as the client you are currently using. Refer to the Enterprise Moel Database (EMDB) interoperability section for illustrations on Control Builer interoperability Using Configuration Stuio uring server migration (ual primary state) You can open an use Configuration Stuio (CS) uring an on-process migration, although there are some limitations on the tasks that are available to use. These limitations epen on the following: The noe you are using (Server B or Server A). The release currently operating on the noe. The Connect ialog box that appears, when you start the Configuration Stuio, isplays all the etecte servers, regarless of their release an upate levels. When selecting a task from the list in Configuration Explorer using Server B (which has been migrate to the target release) uring ual primary state, you may receive some error an/or warning messages inicating that the task is not permitte uring OPM. Some tasks in the Configuration Explorer winow are unavailable. You can open an use the Control Builer, the Enterprise Moel Builer, an other engineering tools to verify that the system configuration was migrate successfully an to perform compatibility tests. However, the atabases in the system are rea-only. You cannot make any configuration changes or perform any engineering tasks to the ERDB or EMDB uring the on-process migration. When using CS on Server A (which is operating with the base release) in ual primary state, warning messages appear. For example, atabase is not writeable at this time. Although, you can open an use Control Builer, Enterprise Moel Builer an other engineering tools, messages such as Function not allowe when connecte to seconary atabase' appear. The rea-only restriction applies also to the system atabases. When various applications in CS are open, they inicate that the system is in an OPM status (OPM appears in yellow on the status line below the application winow). 38

39 3 SYSTEM INTEROPERABILITY CONCEPTS When opening CS an the engineering applications from clients (Console Stations, Flex, an so on.), the behavior is ifferent. You must connect irectly to a server that is on the same release as the client (an o not connect to the system). A Console Station that is migrate an is now operating on the target release is similar in behavior to Server B as previously escribe. Similarly, a Console Station which is operating on the base release is similar in behavior to Server A as previously escribe Using Configuration Stuio uring multi-cluster migration Connection to systems an server on ifferent releases is supporte. The Connect ialog box that appears when you open Configuration Stuio isplays all the etecte servers regarless of their release an upate levels. However, if the client (which is use for connecting to the server) an the server are operating on ifferent releases, not all tasks are available Saving an rebuiling checkpoints The checkpoint rebuil an manual checkpoint save operations are performe for the various controller noes uring server ual primary state in OPM. The format of checkpoint files in a given release of Experion is unique, so that the checkpoint files of one release are not compatible with other Experion releases. For example, R400.3 checkpoint files are not compatible with Experion Release R500.x an vice versa Using the Search utility Starting the Search utility in Configuration Stuio (Determine where an object is use in the system (Where Use)) searches only the ERDBs an/or EMDBs which are at the same release an upate level Using Display Builer an HMIWeb Display Builer If a user moifies isplays on the base release in Server A, the changes are lost once the server migration is complete. When the Server A is upgrae an synchronize with Server B, the moifie isplays are overwritten with the original isplays in Server B. 39

40 3 SYSTEM INTEROPERABILITY CONCEPTS 3.9 Station interoperability Displays The isplays in R510.x cluster can access controller ata at any release level in any cluster in the system. The intercluster communication is through DSA. During the ual primary state, some clients (Flex stations, console stations, an console extensions) are on target release an connecte to Server B, an some clients which are still on the base release are connecte to Server A. After ual primary an before Server A migration all the clients must be migrate to the target release Network Detail isplays Network Detail isplays an faceplates accesse in Station provie information gathere from computers, switches, FTE evices, an Control Firewalls through the System Performance Server (SPS) on the monitoring server. The monitoring server association is efine using the Configuration Stuio Network Tree - Assign Monitoring Server task. For interoperability between the R510.x network isplays (non-existent in R210 an earlier releases) must be on R400.x, R410.x, R430.x, R431.x, an R432.x noes, common component maintenance releases must be installe on the R400.x, R410.x, R430.x, R431.x, an R432.x noes. 40

41 3 SYSTEM INTEROPERABILITY CONCEPTS 3.10 Enterprise Moel Database (EMDB) interoperability Starting Configuration Stuio to connect to the system provies view of the noes which are at the same release. Choosing the task Configure Assets or Alarm Groups for this system starts the Enterprise Moel Builer (EMB) application an connects to the EMDB server which is at the same release an upate level as the client you are currently using. Some functions are isable uring migration. For example, the EMDB (an ERDB) are locke to prevent any changes until migration is complete. Aitionally, features which are available in newer releases are not available on noes operating at earlier releases until they are migrate to the new release. Relate topics Interoperability summary on page 110 System interoperability concepts on page 29 41

42 3 SYSTEM INTEROPERABILITY CONCEPTS 3.11 Inter an intra cluster interoperability Configuration an valiation interoperability Intercluster peer-to-peer function enables communication between batch layers istribute in two or more Experion clusters. This function allows a parent recipe in one cluster to control its chil recipes in another cluster. The clusters participating in intercluster peer-to-peer communication may be in the same or ifferent FTE communities. Inter-cluster interoperability Runtime interoperability Inter-cluster interoperability The following table shows interoperability between Security Manager an Security Manager Proxies with all other noes that participate in Secure Communications. C300s, Console Stations, Flex Stations, Console Extension Stations, an Servers not in the role of Security Manager or Security Manager Proxy. 42

43 4 Planning migrations Preparation for system migration requires careful planning an must begin well in avance of the ay that you plan to start a migration. To execute a migration successfully requires the coorination of many things along with the cooperation of various plant personnel. Develop a comprehensive migration plan that aresses the consierations escribe in the following sections. Also a plan helps to alert responsible plant personnel on what to expect before, uring, an after the migration. This section covers topics that escribe preliminary planning, consierations, an tasks which are essential for conucting a successful system migration while on-process. Relate topics Develop a migration plan on page 44 Develop a migration strategy on page 48 Develop a migration timetable on page 51 Review software requirements on page 53 Review harware requirements on page 56 Choose whether to use Experion Software Installation Server (ESIS) on page 57 About Experion Migration Storage Noe (EMSN) on page 59 Consierations for planning network topology changes on page 61 Review migration consierations on page 62 Planning time synchronization uring migration on page 67 Ientify security policy changes on page 69 Cancelling a migration on page 72 43

44 4 PLANNING MIGRATIONS 4.1 Develop a migration plan It is essential that you evelop a migration plan for your control system to minimize any problems which may occur uring a migration an ensure that the migration is successful. In eveloping a migration plan, you must take into account the structure an size of the control system as well as the process which the Experion system controls. A system may contain one Experion cluster, or in a larger system, a number of Experion clusters. An Experion cluster may consist of computers that host reunant servers, clients which may consist of one or more Console Stations, Flex Stations associate with the servers, an controllers associate with the cluster. Larger Experion clusters may consist of computers that host reunant servers; clients (both Flex an Console Stations) associate with the servers, an ACE noe, an a set of controller components. Large plants may contain a number of control systems that have many Experion clusters populate throughout the plant. You may ecie to migrate the Server/Client noes of one cluster an then migrate all, none, or a portion of the controller components of that cluster. The servers in all the Experion clusters of a control system may be selecte for migration now, an the controller migration coul be scheule for a later time. Interoperability of system components is possible with some restrictions. For example, you coul migrate an operate servers an clients on the new release software, an operate controllers an other system noes running at the base release until migration is scheule for those components. In any case, server migration (which inclues clients) is always performe before the migration of ACE noes an controllers within a single cluster. A well-planne migration plan must be evelope beforehan to ensure success. A control system must be partitione in such a way that migration of Experion clusters is accomplishe with minimal upset to the process. You may want to create a system rawing showing the system structure to ai you in migration planning. Also, consier any harware upgraes that may be necessary or esire. Servers may require a newer harware platform (computer system) in orer to operate an run new release system software. See Harware requirements on page 126 for more information. Contact the HPS Migration Center of Excellence at LSS.Migration.coe@honeywell.com to let them know that you are planning to perform a migration of your system. The HPS Migration Center of Excellence, working with TAC, can offer invaluable information an guiance in planning an executing a system migration. 44

45 4 PLANNING MIGRATIONS Consierations while migrating non-reunant Experion systems an control components Non-reunant Experion system an control components must be migrate off-process. If a migration is planne uring a scheule plant maintenance shutown, a migration plan must be evelope to make sure that people an resources are available for the migration Consierations for migrating network-api base customer applications Network-API base customer applications must be migrate off-process. For more information, refer to the Application Development Guie Migration Planning Checklist The Migration planning checklist provies a high-level list of tasks to be performe while planning a system migration. Many of these tasks refer to sections in this ocument for further information or proceures to complete the task. You can use a more comprehensive set of checklists available in the Migration Planning Checklist Collection chapter. Table 1: Migration Planning Checklist Step Task Done? 1 Inform the HPS Migration Center of Excellence (COE) that you are preparing to migrate your system. You can contact the COE at LSS.Migration.coe@honeywell.com. 2 Review the latest SCN to fin any information that pertains to the migration you are going to perform. Review the general specifications an requirements for the new release in Appenix A of the SCN. See the Experion SCN for this information. 3 Check the Honeywell Process Solutions website an refer to the spreasheet available at the following link support/software-ownloas/experion/experion-upate-matrix.zip for any information on upates for latest Experion patches, software upates, an so on to review whether or not these items apply to the system installation for migration. 45

46 4 PLANNING MIGRATIONS Step Task Done? 5 Use a software application (such as Intergraph, Auto-Ca, or Visio) to plan your implementation or system esign. Create a rawing that shows the system architecture, (clusters, servers, clients, an controllers) that coul ai you to implement your migration. 6 Ientify the cluster an noe migration sequence. See Multi-cluster migration scenarios on page 134. This is a very important consieration an you must consier the process being viewe. During migration, a station cannot view the process for a few hours while the connecte server is upate. Thus while the station is being upate, alternate security level or asset assignments may nee to be performe on the stations that are not being migrate at that time. 7 Ientify the backup imaging sequence for Experion noes incluing the locations of images. Experion Backup an Recovery application can be use for this operation. See Experion Backup an Restore User s Guie for information an proceures. 8 Make sure that a time topology for the system is in place that provies time synchronization to all the noes throughout migration. See Planning time synchronization uring migration on page Ientify the location of the BOOTP server. Refer the section BOOTP service in the Scenario specific migration guies. 10 Ientify all other Honeywell Applications in the system an consier any interoperability an migration requirements. Define a migration plan for these applications. See Migrating other Honeywell proucts an applications on page Ientify all thir party applications in the system, an efine a migration plan. See Migrating non-experion thir-party applications on page Rea through the appropriate Scenario specific migration guies to become familiar with the migration process, an be aware of other tasks to perform in preparation for migration. Take notes. 13 Review computer harware requirements for the target release, an review against your computer harware propose for use on the new release. See the section Software/Harware/Firmware Compatibility in the Experion SCN for more information. 14 Verify that DVD rives are available to the PCs ientifie for migration. This can inclue local rives or remote rives that may be use to rea the Experion meia. 15 If planning to use an Experion Software Installation Server (ESIS) uring migration, ientify a noe in the system to be use as an ESIS. See Choose whether to use Experion Software Installation Server (ESIS) on page

47 4 PLANNING MIGRATIONS Step Task Done? 16 Review Supplementary Installation Tasks Guie for information an tasks that may be necessary uring migration (such as time synchronization an aing computer back into a omain). 17 Ientify the FTE rivers an switches an\or the switch configuration files that nee to be upate. 18 Review the latest Fault Tolerant Ethernet Overview an Implementation Guie for possible improvements. 19 Use ERDB Consistency Checker on Process systems to ientify the following: Valiate the content of the Engineering Repository Database (ERDB). Ientify an correct inconsistencies in the ERDBs before starting migration. Custom CCLs that have to be upate. Control strategies that have to be upate after the migration. 20 Ientify any customize system isplays that have to be re-create after migration. 21 Plan any conversions that are to be one after the migration, such as CNI replacement with FTEB an C200 replacement with C Estimate the time require to migrate the system components an evelop a timetable for the migration process (planning, system reainess or premigration tasks, migration of servers/clients an controllers to the target release, post-migration tasks.) See Develop a migration timetable on page

48 4 PLANNING MIGRATIONS 4.2 Develop a migration strategy Ientify the scope of migration. On what release of Experion software is your system currently operating (the base release)? What release of Experion software o you want to migrate to (the target release)? Which part(s) of the system are to be migrate at this time? What parts of the system are ientifie for subsequent migrations? Is a prouct change planne for the system noes? How o the migrate system noes interoperate with the noes that remain on the base release? If Secure communications is enable, ientify the noe performing the Security Manager role an what is its migration requirement for Experion cluster(s) in the Security Area? If your system comprises one Experion cluster or a number of clusters, all the server noes in the clusters are migrate to the target release now? Do server noes share atabases between clusters? For example, the Enterprise Moel Database (EMDB) may exist on a eicate noe which is share between servers in ifferent clusters. How oes this impacts migration? How oes this impacts the system operation an interoperability if one Experion cluster is migrate to the target release an another cluster is left at the base release? When migrating from R400.xor later, the cluster orer is not restricte - the cluster with EMDB Server can be migrate first, last, or mile.if you are migrating from R400.x) to R500.1, you must ensure both EMDB an non- EMDB servers are migrate to R500.1 before using Upgrae Tool. For larger systems that inclue multiple clusters, a migration strategy must contain two scenarios. 1. How is the system migrate? 2. How is each Experion cluster migrate? System migration planning Depening upon how your system topology is arrange, etermine the orer of migration for the noes an clusters that comprise your system. 48

49 4 PLANNING MIGRATIONS Cluster migration planning Within a single cluster, on-process migration of Experion noes occur in the following orer. Server B EAS (off-process migration can be performe before or after server migration) One Flex Station One Console Station Console Extension Stations (CES) connecte to the migrate Console Station Perform compatibility an performance tests Attention Some stations an consoles can be migrate before or after Server A or Server B is migrate. Remaining Flex Stations Remaining Console Stations Remaining Console Extension Stations (CES) connecte to the Console Stations Server A Controllers ACE an SCE noes (migrate off-process) E-APP eserver Collaboration Station Other noes which may be associate with a number of servers across multiple clusters, such as eserver, are migrate off-process, inepenent of the system migration. If your system contains Series C control harware (C300 (CC-PCNT01/CC-PCNT02)/ C300 with EHB personality configure controllers, FIM4s, FIM8s, an PGM), you must upgrae the CF9 control firewall to the latest firmware before you migrate the Series C control harware State of the process Determine what state is satisfactory for the process to start an on-process migration. The process must be stable, an if possible, inactive. If the process is a batch operation, it is recommene that a batch not be in progress uring system migration. Verify that the process is appropriate for on-process migration by using normal system isplays to view an monitor the process. 49

50 4 PLANNING MIGRATIONS Network topology consierations If you are migrating a SCADA noe from R400.x, R410.x, R430.x, R431.x an R432.x to R510.x, the network topology changes epen on whether you want to use the following process control components after migration or not. Note The process control components are. C200 an/or C300 /C300 with EHB personality configure controllers ACE, SCE, or EHG noes Fielbus Interface Moule or FTE Brige Moule If the SCADA noe is configure with FTE topology, then FTE gets installe uring migration. If the SCADA noe is configure with Ethernet topology, then the same configuration is retaine after migration. For etails on the network topology changes, refer to the corresponing SCADA migration guie. You can refer Relate ocuments on page 10 for the list of migration guies. 50

51 4 PLANNING MIGRATIONS 4.3 Develop a migration timetable Develop a timetable for conucting the migration. Consier the timing of the various migration tasks that nee to be performe an the orer of such tasks. Estimate the time require for completing each task. For example, estimate the time for: Obtaining new harware, if require. Completing pre-migration tasks. Performing server migration of one reunant noe. Performing migration of associate client noes. Completing compatibility an performance tests on migrate noes. Completing the migration of the remaining client noes. Performing server migration of secon reunant noe. Completing server post-migration tasks. Reinstallation of other Honeywell applications. Reinstallation of thir-party applications. Migration of other Experion noes, ACE, SCE, EHG, an so on. Performing controller migration. Completing controller post-migration tasks Migration time estimates Use the following information as a guie for estimating the time to perform an onprocess migration from R400.x, R410.x, R430.x, R431.x an R432.x to R510.x, or an off-process migration from R400.x, R410.x, R430.x, R431.x an R432.x to R510.x. The estimates are base on a cluster with 5-10 stations, reunant servers, 1 ACE noe, 3-10 controllers, an a number of LCN connections. These times can vary significantly base on user experience, atabase size, an the current conition of the system. On-process migration to R510.x Overall planning. Migration Task Fixing of all issues that may prevent migration, an getting an approval from COE for migration Preparation an backups. Server B migration together with some stations or consoles. Estimate Time 2 5 ays 2 4 ays 2 5 ays 3 4 ays 51

52 4 PLANNING MIGRATIONS Migration Task Estimate Time Migrate remaining stations an consoles. Each Flex Station 3 4 hours Each Console Station 3 4 hours Verification of proper Server functionality (Compatibility Testing). 1 2 ays Server A migration 1 2 ays Controller migration 1 2 hours per controller Perform off-process ACE noe migration 3 5 hours TPS functionality 1 2 ays Migration verification 1 2 ays Off-process migration to R510.x Overall planning. Migration Task Fixing of all issues that may prevent migration, an getting an approval from COE for migration. Preparation an backups. Server A an B migration. Migrate the stations an consoles: 1 2 ays 2 4 ays 1 3 ays 2 3 ays Each Flex Station 3 4 hours Each Console Station 3 4 hours Controller migration ACE noe, SCE TPS functionality Migration verification Estimate Time 1 2 hours per controller 3 5 hours 1 2 ays 1 2 ays 52

53 4 PLANNING MIGRATIONS 4.4 Review software requirements Review an aress the software requirements for the migration. Some consierations that must be reviewe are: What is the base release (or current release) of the system components ientifie for migration? What is the target release for the system components? Will the system be taken to the latest target point release? Is the release at the correct service pack level or release level to perform the planne migration? Does the planne migration path for the system create any special requirements that must be met? For example, if all the system components are not currently operating at the base release, then must components at oler releases be migrate to the base release before migration to the target release? Attention Before starting the migration from base release to the target release, ensure all the require optional features are installe using the installation meia of the base release. The qualifie on-process server migration paths for Experion Release R510.x are: Experion R400.x (with or without patches) to Experion R510.x Experion R410.x (with or without patches) to Experion R510.x Experion R430.x (with or without patches) to Experion R510.x Experion R431.x (with or without patches) to Experion R510.x Experion R432.x (with or without patches) to Experion R510.x Attention For exact supporte migration paths, refer to the latest target release SCN. Relate topics Software requirements on page Migrating other Honeywell proucts an applications Some of the Honeywell applications installe on Experion noes may not be migrate as part of the Experion system migration. During migration you may get a message that informs you of software applications (both Honeywell an thir-party applications) that cannot be migrate forwar. Refer to the associate prouct ocumentation an take 53

54 4 PLANNING MIGRATIONS appropriate actions to preserve these applications an user settings so that they can be restore after migration. Alarm Pager - If you are using Alarm Pager option, you must reconfigure the alarm paging after migration. This requires that you check to make sure that the moem (if one is use) is connecte to the system an configure properly. Refer to Experion Server an Client Configuration Guie. Control Component Libraries (CCLs) - The system stanar CCLs supplie with Experion are migrate forwar to the new release. Special consieration is require for customer specific CCLs. Customize system components an isplay files must be manually save because they are not migrate an then restore in the target release. For example: Point etail isplays such as DI, Numeric, flag, an fielbus. Faceplates such as DI, Numeric, flag, an fielbus. Custom Station menu configurations (*.stb files) *.css files Safety Manager - For Experion systems that have Safety Manager installe, refer to the Safety Manager ocumentation for migration. The following are some of the other Honeywell applications that may be installe on Experion noes an not migrate as part of Experion system migration. Fiel Device Manager (FDM) Asset Manager Da Vinci Server, Quality Server, MxProLine Server BMA Process History Database (PHD) Process Performance Profit Suite Simulation TPB User Alert Uniformance For information about Applications Interoperability Matrix, refer to the teams.honeywell.com/sites/ait/hpsaitinteroperabilitymatrix/share%20documents/ HPS-Applications%20Interoperability%20Matrix.aspx link Migrating non-experion thir-party applications Most non-experion applications are not migrate as part of Experion migration. If your control system inclues non-experion (thir party) applications, consier a strategy for 54

55 4 PLANNING MIGRATIONS saving the ata an configuration files for the application so that the ata an user settings can be restore with the application after Experion migration is complete. Take appropriate steps to save these files an applications. During server migration you may get a message that informs you of software applications that are not be migrate forwar an elete from the noe. Aitional consierations must be mae such as: Are the thir-party applications currently operating with the Experion system compatible with the new release operating system requirements? Are the thir-party applications interoperable with the new Experion platform software release? Are there upgraes available for the thir-party software? Is compatibility testing performe off-line to ensure that the applications operates properly in a stable manner? Attention Experion R510.x operates with Winows Firewall enable. You must verify that thir-party applications are set to operate in a firewall environment. Here are some examples of thir-party software applications. Virus protection services applications are not migrate forwar as part of Experion migration. 55

56 4 PLANNING MIGRATIONS 4.5 Review harware requirements Migrating an existing Experion system to new system software may require that the harware platform (computer system) which supports software operation is also upgrae. Harware platforms may be configure as Experion Servers, Flex Stations, Consoles, ACE or SCE noes, or other client noes. A new computer system may be neee to meet the performance requirements for Experion software operation. Typical upgraes may inclue aing memory cars, installing aitional isk rives an upgraing to newer interface cars. Any thir-party harware interfaces, if installe, nee to be transferre to the new harware platforms. Verify if the interface harware is compatible an can be installe in the new platform's car slots, an if the interface harware nee to be replace. Make sure that any replacement harware is equivalent in function of the harware that it replaces. Estimate the time require to obtain any new harware. 56

57 4 PLANNING MIGRATIONS 4.6 Choose whether to use Experion Software Installation Server (ESIS) Starting R310, Experion Software Installation Server (ESIS) can be set up only on a local har rive, a portable USB har rive, or a removable USB rive. Setting up ESIS inclues installing all the Experion software on a share foler (the share foler is create on local har rive or USB rive) which can be accesse over a network to perform Experion installation an migration on one or more systems. ESIS provies a single repository for all Experion software an can be use for installing an migrating Experion software on multiple systems simultaneously. ESIS can be upate for any meia upates or new meia releases. An ESIS repository consists of a copy of the following: Experion PKS System Initialization meia(optional) Experion PKS System Initialization Upates meia(optional) Experion PKS Installation meia 1 Experion PKS Installation meia 2 The latest point release Experion Support Software is available as an ISO image on Honeywell Process Solutions website ( Use the ISO image content to create a DVD/meia for installing the latest Experion point release. For extracting contents to a meia, use ISO extraction software. For example, you can use Virtual Clone Drive software for extracting the contents to a meia. Microsoft Visual Stuio for CAB Developer meia. (optional, require only if CAB is selecte). Experion Support an Maintenance meia Microsoft SQL Server 2014 SP2 Experion PKS with PMD controller meia (optional) For operating system, the following meia are require. Winows Server 2016 HPS OS reinstallation meia Winows 10 (64-bit) HPS OS reinstallation meia You can create an ESIS repository on a local har isk that can be accesse using a network share, USB rive, or a removable har rive. Tip For setting up an ESIS repository, the minimum space require on the ESIS server is 33 GB. 57

58 4 PLANNING MIGRATIONS Attention 1. DO NOT install/setup ESIS on Experion noes. 2. Although ESIS allows migration of multiple Experion noes, there are some limitations that must be note. In on-process migration scenarios, o not migrate more than two noes simultaneously. When the Plant processes are running, the control system must have the necessary banwith for network communications to ensure process control. In off-process migration scenarios, it is assume that other control evices are on the network (thir party evices). Therefore, o not migrate more than four noes simultaneously. 58

59 4 PLANNING MIGRATIONS 4.7 About Experion Migration Storage Noe (EMSN) The Experion Migration Storage Noe (EMSN) is a temporary storage area use for storing migration-relate information, which is use after installing Experion. Relate topics Ientify a location for the EMSN on page 59 Consierations for using EMSN hoste in a omain on page Ientify a location for the EMSN The EMSN is a share foler which is use for storing an retrieving the atabase an configuration information containe on an Experion noe ientifie for migration. The EMSN must be set up an locate on a noe ifferent from the noe to be migrate, but within the same control network or Experion cluster. EMSN is compatible with USB har rive or removable USB rive. The EMSN must have sufficient isk storage so that the information can be copie to the EMSN from the server or client noe to be migrate. You can ientify a noe an create a space for the EMSN before you begin migration. You are prompte to create a share foler for the EMSN uring migration. A minimum of 32 GB isk space is require for creating EMSN. During phase I of migration, if you o not select Operating System Re-installation option, then Local EMSN an the Remote host EMSN options are available. If local EMSN is not require to be store after migration, then you can select Select this to elete EMSN once Migration Complete (this helps to manage the isk space) check box. Attention The Operating System Re-installation option is applicable from R410.x, R430.x, R431.x, an R432.x to R510.x migration path Consierations for using EMSN hoste in a omain When the computer on which EMSN is hoste an the Experion noe to be migrate are members of a omain, they can either be on the same or ifferent network. You may not be able to resolve the Universal Naming Convention (UNC) path to EMSN an the creential information when the following are performe uring migration. A harware change An operating system installation (cannot be avoie for the migration paths where operating system change is a must) 59

60 4 PLANNING MIGRATIONS To avoi path resolution problems, perform one of the following base on the location of the EMSN an the noe to be migrate. 1. If the EMSN an the noe to migrate are connecte over the same network. a. Use normal UNC. b. For security (account an passwor), create a local account (an passwor) on the omain system that matches the account being use for performing the migration on the noe being migrate. A this account to the Share an File Permissions on EMSN. The account entere must be the Account Name an associate passwor. Or, you can specify an account on the EMSN by entering EMSNHostName \Account. Enter the passwor. 2. If the computer is not local to the system, (computers must communicate across a router): a. Define the Server UNC path in the following format: \\EMSN Host IP Aress \<<EMSN ShareName>> For example: \\ \EMSN b. For Security (account an passwor), create a local account (an passwor) on the omain system that matches the account being use for performing the migration on the noe being migrate. A this account to the Share an File Permissions on EMSN. Type the account name as <<EMSN Host IP Aress>>\Account. For example: \MigAccount Type the passwor. 60

61 4 PLANNING MIGRATIONS 4.8 Consierations for planning network topology changes Attention Any changes to the control or supervisory communications topology in the system must be mae, either before migration is starte or after migration is complete. Ientify any changes to the system or network topology that are planne an which can be mae before the migration. For example, if you are planning a prouct change (changing a SCADA system type to Process system) or conversion of single/ual Ethernet or ControlNet to FTE; a FTE supervisory network must be installe in the system before migration starts. For more information an the tasks for installing an FTE network in a system, see Converting a single or ual Ethernet supervisory network to an FTE network in the Fault Tolerant Ethernet Installation an Service Guie. Create a plan to complete the changes. Ientify any changes to the system communications network that you want to make after migration. For example, you may want to a CISCO switches, upate the CISCO switch firmware, an then upate the CISCO switch configuration, an a a control firewall. Also, you may want to install C300/C300 with EHB personality configure controllers an Series C I/O moules, a Stations, a controllers, an/or upate the control firewall. You must also etermine a plan for performing these changes that affect the network topology. 61

62 4 PLANNING MIGRATIONS 4.9 Review migration consierations Attention The following sections contain important information that you must consier before you begin a migration. The information is arrange by system function or feature an escribes conitions where ata may be lost through the migration process, if precautions are not taken or proceures are not followe. Where possible, workarouns are provie to help safeguar an restore ata. Therefore, if your Experion system contains certain configurations of system components or uses these features, you must rea the relate topics of interest to etermine if the information is relevant to your system or situation. If so, take precautions to back up your ata files an follow any require workarouns Consierations for migrating integrate Experion-TPS noes TPS components continue to be on-process uring the migration of Experion system components, an ES-Ts continues to have view an control capabilities to the TPS system uring the migration process. When an ES-T noe is selecte for migration, it loses view an control capabilities. After the noe is migrate an is operational on the new release, view an control are restore. Consierations must be mae to maintain at least one operational noe that can provie view of the TPN Consierations for migrating DSA-connecte Experion/TPN systems The ESVTs an ESTs in Experion clusters that are connecte to TPN can be migrate without affecting TPN operations. The version of TPN require for the integrate Experion-TPS noes in R510.x has not change since R210 so there is no requirement to upgrae it. Attention DSA interoperability between R3xx an R500.x is supporte Consierations for migrating secure Experion noes The following consierations must be note for secure Experion noes before migrating from R430.x/R431.x/R432.x to R500.x. 1. It is recommene to avoi secure communication configuration changes uring Experion migration. Any changes must be performe before or after the migration. 62

63 4 PLANNING MIGRATIONS 2. R430.x/R431.x/R432.x Security Manager interoperates with other Experion noes which are alreay migrate to R500.x. If you want to get R500.x Secure Communication features, then migrate the Security Manager to R500.x. When the Security Manager role is performe by an Experion Server noe in a Level 2 cluster, the Server must be migrate as part of the existing rules for migration of an Experion cluster (no special consierations). When the Security Manager role is performe by an Experion Server or Experion Application Server (EAS) noe at Level 3, the orer of migration of Experion Server or EAS noe versus multiple Experion cluster migration is not important in the same Security Area Consierations for multi-cluster migrations The following important consierations must be rea to etermine if any apply to your system in a migration scenario. The table Multi-cluster migration scenarios an EMDB interoperability escribes migration scenarios for two clusters. The same scenarios are vali for all clusters within a system. In all migration scenarios, DSA an OPC ata interoperability is available throughout the migration process. Server noes connecte through DSA must maintain communication with other DSA servers an clients before, uring, an after an on-process migration, (except for the noe that is currently being upate). OPC ata exchange between servers an clients an thir-party OPC is also maintaine uring migration, except when the OPC noe is being migrate. Interoperability is supporte only between clusters (servers) operating on two ifferent releases an only between releases in which migration is supporte. Interoperability between clusters (servers) operating on more than two ifferent releases is not supporte. Do not make any engineering changes until all clusters within a system are migrate. Do not make any engineering changes until all systems are migrate. Do not ownloa or uploa EMDB ata when either the EMDB hosting Experion server or the target Experion server is in ual primary state. Minimize the amount of time that clusters are running on ifferent releases. Although OPM of multi-cluster systems allows for interoperability between clusters operating on ifferent releases, you must minimize the time that clusters on ifferent releases in a system are allowe to co-exist. All noes within the FTE communities use by any of the migrating clusters must be upate to the latest version of Common Components before starting a migration. All FTE system preferences an FTE river configurations must be the same for all clusters in the FTE community. 63

64 4 PLANNING MIGRATIONS The BOOTP server must be running on the latest release server of the cluster. You must run the BOOTP checker before migrating or rebooting any controllers Consierations for partitioning har rives using Experion PKS System Initialization meia Experion PKS System Initialization meia fails to partition har rives before starting the operating system installation if aitional internal rives or RAID arrays are connecte to the system. Attention Experion PKS System Initialization meia is teste an qualifie only on Honeywell recommene harware configuration an only supports those configuration. Honeywell recommene harware configurations o not inclue more than one har rive on non- RAID platforms. Previously use EXPPlus meia (R3xx.x) was unintentionally supporting such nonstanar har rive configuration. Therefore, any customer using such configuration an migrating to may come across this issue. This issue is not applicable to external USB har rives attache to the platforms. Before starting the operating system installation, Experion PKS System Initialization meia fails to perform the requeste partition of the har rive on workstations with more than one internal har rive or servers with more than one RAID array. Har rive partition on these servers/workstations fails with the error message Faile to configure harisk. Click Yes to retry or No to exit. Experion PKS System Initialization meia eletes an re-creates partitions in the aitional har rive or the RAID array. Attention This is not applicable to USB har rives attache to the platforms. This issue occurs when customers are using Experion PKS System Initialization meia to perform har rive partition prior to operating system installation on any Dell platform having non-stanar Honeywell configuration or any server or workstation. The non-stanar Honeywell configuration can be (but not limite to) workstation having more than one internal har rive, an any server/workstation having more than one RAID array. 64

65 4 PLANNING MIGRATIONS Attention Review the harware platform configuration to ensure that the platform oes not inclue more than one internal har rive on non-raid platforms an more than one RAID array on RAID platforms. You must perform this harware platform verification before booting the system with Experion PKS System Initialization meia to start operating system installation. If you have not performe, the Experion PKS System Initialization process may elete an re-create partitions in the aitional har rive or RAID array. This results in ata loss in the aitional har rive or the RAID array. To isable aitional har rives in BIOS before starting operating system installation 1 Press F2 to enter BIOS Setup while the workstation is booting. 2 On the left pane, navigate to Drives, an press right arrow or Enter to expan Drives. Attention Before isabling/enabling the SATA ports that have aitional har rives, you must verify the Drive Details section on the right pane. 3 For Dell Precision Workstations R5500, T5500 an T3500: a b c Select Drives. Clear the respective check boxes for each SATA port (For example, SATA-1 check box). Hence, all SATA ports to which aitional har rives are connecte are isable. Click Apply to save the changes. Click Exit to close the BIOS setup winow. 4 For Dell Precision Workstations T5400, T3400, an P490: a b c On the left pane, navigate to each SATA port option using the arrow keys. Press Enter to moify the SATA port option. Select Off to isable all SATA ports to which aitional har rives are connecte. Press Esc, an then select Accept to save the changes. 5 Restart the workstations/servers. To enable the har rives 1 Once the installation completes, perform step 1 through step 2 from the To isable aitional har rives in BIOS before starting OS installation proceure. 2 For Dell Precision Workstations T5500 an T3500: a Select Drives. 65

66 4 PLANNING MIGRATIONS b c Select the respective check boxes for each SATA port (For example, SATA-1 check box). Hence, all SATA ports to which aitional har rives are connecte are enable. Click Apply to save the changes. Click Exit to close the BIOS setup winow. 3 For Dell Precision Workstations T5400, T3400, an P490: a b c On the left pane, navigate to each SATA port option using the arrow keys. Press Enter to moify the SATA port option. Select On to enable all SATA ports to which aitional har rives are connecte. Press Esc, an then select Accept to save the changes. 4 For Servers: a b Do not use Experion PKS System Initialization meia for operating system installation if the server has more than one set of RAID arrays configure. Perform manual operating system installation, an then use Experion PKS System Initialization meia to perform system configuration. For more information on this issue, contact Honeywell TAC About pre-installe SQL scenario In R500.1, the pre-installe SQL scenario is supporte to install Experion on a system where Microsoft SQL Server 2014 Stanar Eition Service Pack1 (SP1) is alreay installe. SQL installation prior to Experion installation is only require on all the server noes. For migrating on all the server noes from R400.x, R410.x, R430.x, R431.x to R510.x, you must manually install SQL on the server noe an then configure SQL prior to Experion migration. For migrating the server noes from R400.x, R410.x, R430.x, R431.x to R510.x, this scenario is applicable only for operating system re-installation migration. This scenario is also applicable for eserver an EAS noe. For configuring SQL, refer to the Configuring pre-installe SQL Server 2012 proceure in the Software Installation User's Guie. 66

67 4 PLANNING MIGRATIONS 4.10 Planning time synchronization uring migration Maintaining the correct time synchronization throughout migration is critical. If you have a time topology for your system, you must consier whether the current time topology is comprehensive enough to istribute time to all system noes uring a migration. Otherwise, you must establish a time topology that provies reliable time istribution to all noes in the system. Keep in min that uring a migration, some noes operate at the new release (such as servers an clients that are migrate), while other noes (such as controllers) continue to operate at the base release. Experion noes in a system that are not synchronize to the same time source may rift through time an cause control an/or migration problems. For example - at one point uring server migration, a reunant server pair is operating in a ual primary state, (Server B has been migrate an is operating at the new release an Server A is operating at the base release). Each server may be istributing time to the controllers associate with these servers. If time is not synchronize between the servers, the controllers may execute control strategies incorrectly ue to the inconsistent time receive from the servers. The system time source must erive its time from a reliable external time source NTP servers (time source for Series C control harware) In Experion R301.3 an later releases, Network Time Protocol (NTP) is use for furnishing system time to all Experion noes. Series C control harware (C300/C300 with EHB personality configure controllers, FIM4, FIM8, PGM EHPM, an IEC61850M), uses time istribute from an NTP server, so if your system contains any Series C control harware, you must setup an NTP server. Preferably the NTP server must be setup on a Winows 2008 or a Winows 2003 noe which erives its time from a reliable external time source. After server migration the exisitng NTP configuration settings can be restore using NTPConfig utility. For more information, refer to the Scenario-specific migration guie an Site-specific migration guie. For information about upgraing firmware using the Series C Firmware Loa Tool, refer to the latest Control Harware an I/O Moules Firmware Upgrae Guie. For information about setting up the system time, refer to the following guies. Time Synchronization topic in Server an Client Planning Guie. Setting up Time Synchronization in the Supplementary Installation Tasks Guie. 67

68 4 PLANNING MIGRATIONS Time check on system before you start migration Server time an time zone settings must remain consistent uring migration. Before starting migration on a reunant server pair, check to make sure the time an time zone settings are the same on both Server A an Server B, as well as the client noes (Console Stations, Flex Stations, ACE noe, so on.). Change if necessary. After migration, check the time zone settings on the server an client noes to ensure they are the same. Change if necessary. Do not change time zone settings uring a migration. Aitionally, check the time zone setting on other servers in the system, (any servers that are connecte to the migrate servers by DSA), an make any changes so that all noes are set to the same time. Support for the latest Daylight Savings Time fixes are inclue with the Experion Software. However, ue to the recent global time zone ajustments, it may be necessary to reset the time zone settings uring some migration scenarios. You must verify the time zone an set the time (if necessary) after the software upgrae but before the server synchronization for ual primary state, an reestablishing of server reunancy an all other noes. 68

69 4 PLANNING MIGRATIONS 4.11 Ientify security policy changes Experion systems that use the Experion High Security Policy in a omain or workgroup environment require that you upate the security policy files to the most recent version when migrating your system. Note that you can upate your security policy files manually without using the installation packages, although it is not recommene. The Experion High Security Policy consists of the following two installation packages: A omain controller package which is installe on the omain controller. For more information, refer to the Installing the omain controller package proceure. A Workstation package which is automatically installe on all noes as part of the Experion software loa. You might be prompte to save the checkpoint when preparing to start migration. It oes not require a separate installation Installing the omain controller package A omain controller use in an Experion system operates as an inepenent noe with either Microsoft Winows Server 2003 (32-bit), Microsoft Winows Server 2008 Stanar or, Microsoft Winows Server 2008 R2 Stanar, or, Microsoft Winows Server 2012 operating system installe. If you are using Microsoft Winows Server 2003 (32-bit) currently as the omain controller s operating system, an o not upgrae the operating system, you must install the R510.x Experion High Security Policy on the omain controller before you start migration. If you are using Microsoft Winows Server 2003 (32-bit) as the omain controller operating system an choose to upgrae to Microsoft Winows Server 2008 Stanar or, Microsoft Winows Server 2008 R2 Stanar, or, Microsoft Winows Server 2012 upgrae the omain controller after completing migration of all noes in the omain. Use the Microsoft recommene proceures to perform the operating system upgrae (at: After the operating system upgrae is complete, install the R510.x Experion Security Policy again on the omain controller. Attention When you remove R31x version of the omain controller package, it oes not change any user group settings or isassociate any user/group settings, an oes not elete any of the security objects, (such as accounts, groups, or group policy objects). In aition, any Experion R31x noes that are members of the omain continue to operate when the new omain controller package is installe. 69

70 4 PLANNING MIGRATIONS To install the omain controller package 1 Insert Experion PKS Installation meia 1. 2 Browse to the removable rive location. 3 Right-click an choose Open. 4 Browse to <Packages\DCSecurity>. 5 Right-click Honeywell security moel - omain controller an click Install. 6 If security warning ialog box is isplaye, click Run. 7 In the Welcome to the Honeywell Experion PKS R510.x Installation Setup Wizar, click Next. 8 If prompte, type the user name an the passwor of the omain aministrator account, an then click OK. 9 Rea the License Agreement, click I accept the terms in the license agreement an click Next. 10 Select Install policies at Domain Level an click Next. 11 Click Install. 12 Click Finish. To remove the omain controller package 1 Click Start > Winows System > Control Panel. The Control Panel ialog box is isplaye. 2 Select Programs an Features. 3 Select the Honeywell Security Moel-Domain Controller program. 4 Click Uninstall. Attention Honeywell-provie Group Policy Objects (GPOs) are over-written when the new omain controller security package is installe. Therefore, any customizations mae to the GPOs must be recreate after the new omain security package is installe. Users must create their own GPOs for settings they want to customize, rather than moifying the Honeywell-provie GPOs. You must return to the Run Link Domain Groups task in the migration metho chapter that brought you to this chapter an continue with the remaining tasks. For more information on omain controller package, refer to latest Winows Domain an Workgroup Implementation Guie. For planning information, refer to Winows Domain an Workgroup Planning Guie. For operation system migration information, refer the appropriate operating system-specific implementation guie Winows Domain Implementation Guie for Winows Server 2016/Winows Domain Implementation Guie for Winows Server

71 4 PLANNING MIGRATIONS Workstation package The workstation package is installe on all noes as part of Experion software installation uring migration. The package inclues the Link Domain Groups which is execute manually after the workstation is mae a member of a omain on which the omain security package is installe. The application links the global group members with the local groups for computers participating in a omain. In other wors, after migrating a system with omain security, you must run Link Domain Groups on all Experion noes in the omain. Note that if omain security is not use, an the user login is base on workgroup security, then the application is not require on any of the Experion noes. If errors occur when running the Link Domain Groups comman, make sure that: The new omain controller package is installe The workstation is mae a member of the omain Both the omain controller an the workstation are on-line on the network For more information on Experion High Security Policy, refer to the Server an Client Configuration Guie. 71

72 4 PLANNING MIGRATIONS 4.12 Cancelling a migration You can cancel on-process migration an go back an restore the control system to operate with the base release software, epening upon which stage of the migration your system is at On-process migration of servers/clients You can start on-process migration of reunant server by clicking Start Migration on the On-process Migration page in Station. A number of restrictions take effect at this point. You cannot make changes to the Engineering Repository or Enterprise Moel Databases. ERDB an EMDB replication remains isable until Server A migration is complete. You cannot initiate a manual failover or atabase synchronization while the onprocess migration is active. To cancel migration, click the Cancel Migration button on the On-Process Migration page. Then, restore the server to the state it was before starting migration an start the migration again. After migration is cancelle, you cannot re-enter migration from the point at which migration was cancelle. You can cancel on-process migration (without a loss of control or view) up until the point where you begin migration of Server A, (Section Migrating Server A in the Onprocess migration (OPM) checklist). After performing Run Compatibility Tests in the OPM checklist, run the system for 2-3 ays to allow the control system to remain stable. You must be satisfie with the control system performance before you continue migration of Server A. While Server A is being migrate, Server B must remain at system running status an as the primary server. If you change the status of Server B, you invaliate the on-process migration an the base release of Experion must be restore or reinstalle on both Server A an Server B. If you cancel on-process migration before you begin Server A migration, then you must restore Server B with the save isk image or reinstall the base release of Experion on Server B (an associate clients) to return the system to a reunant server state. If you restore Server A or Server B from a isk image an Server A an Server B are part of a omain, you must remove the computer from the Winows omain an then: 1. A again each to the workgroup. 2. Re-boot each. 3. A again each to the omain. 72

73 4 PLANNING MIGRATIONS If you cancel on-process migration while Server A is shutown, then you must restore the save isk image containing the base release of Experion to Server A. You lose all runtime ata uring the perio that Server A is own. After Server A is restore an is running, you must restore the isk image or reinstall the base release of Experion on Server B to return the system to a reunant server state Off-process migration of servers/clients There are no critical points when to cancel off-process migration, as the control system oes not operate. All migrate noes can be restore to the base release, if necessary. If you nee to restore any server or client noe to the base release, you can use a isk image, (save prior to migration) to restore the noe to the base release. First you must cancel or exit any applications that are running; then loa the isk image to the noe On-process migration of controllers Generally, after the migration of reunant controllers an I/O control harware is starte, you must allow the migration to complete. When migrating reunant Series C control harware, the Controller Migration Wizar gives you an option either to continue with the migration of the reunant partner, or choose Back to Ile. If Back to Ile is selecte, ue to switchover, the controller running on the base firmware becomes the primary controller. The controller on the new release firmware runs the base release firmware. After migration is complete, you can restore reunant controllers to the base release firmware, but it must be performe off-process Off-process migration of controllers There are no critical points for off-process migration of controllers, except that after a migration is starte it must be allowe to complete. If controller migration is interrupte, the controller may have to be returne to the factory for reprogramming. 73

74 4 PLANNING MIGRATIONS 74

75 5 Starting migration Before starting migration, perform the following: Select a migration path. Select the server/client migration scenario. Select the controller migration scenario. The following sections elaborate the criterion for these selections. Relate topics Selecting a migration path on page 76 Migration scenarios on page 77 75

76 5 STARTING MIGRATION 5.1 Selecting a migration path The starting point for Experion system migration is the selection of a migration path. A migration path efines the system migration from the base release to the target release. There are minimum requirements for a migration path. Systems must be operating with a software release an upate level that supports on-process migration. Attention Rea the section Planning for Migration. It contains pertinent information which is essential to perform a successful migration On-process migration of servers/clients On-process migration is supporte using the proceures containe in the Scenario specific migration guies. *For exact migration paths supporte to target point release, refer to the latest target point release Software Change Notice (SCN). For example, refer to the latest target release SCN On-process migration of controllers On-process migration is supporte using the proceures containe in the scenario specific migration guie an site-specific migration guie. For more information, refer to the latest Experion PKS General Release Software Change Notice an Experion PKS Support Software Software Change Notice. 76

77 5 STARTING MIGRATION 5.2 Migration scenarios Server/client migration scenarios The following table shows the server/client migration an installation scenarios which are supporte for Experion Release R510.x. Experion PKS Installation meia contains the Install Sequencer which executes the migration. The table also shows the Winows operating systems that are supporte for the ifferent Experion noe types an the behavior of the Install Sequencer when it is run on the system. Some migration scenarios may require a harware upgrae. Reinstallation of the operating system is manatory for all the migration scenarios. Table 2: Experion Server/Client migration scenarios an Install Sequencer behavior Operating System Installe Microsoft Winows Server 2016 Microsoft Winows 10 (64-bit) Winows Server 2008 R2 (64 bit) Winows 7 Professional (64 bit) Winows Server 2008 (32 bit) Winows 7 Professional (32 bit) Experion Release Installe None None 41X.x an 43X.x 41X.x an 43X.x Experion R400.x Experion R400.x Install Sequencer Behavior Performs a clean installation on Experion R Performs a clean installation on Experion R Detects the previous version of Experion on the computer. Starts the Install Sequencer to perform migration to Experion R500.1 with an operating system change. Detects the previous version of Experion on the computer. Starts the Install Sequencer to perform migration to Experion R500.1 with an operating system change. Detects the previous version of Experion on the computer. Starts the Install Sequencer to perform migration to Experion R500.1 with an operating system change. Detects the previous version of Experion on the computer. Starts the Install Sequencer to perform migration to Experion R500.1 with an operating system change. Tip Refer to the Software Installation User's Guie for clean installation. 77

78 5 STARTING MIGRATION Controller migration scenarios The migration of controllers an control harware can be performe in a number of ways, epening upon the system topology an the compliment of the installe I/O. Typical scenarios are escribe in the following table. Note that controller migration is performe, after server/client migration is complete. Table 3: Controller migration scenarios Controller Migration scenario On-Process Migration scenarios On-Process migration, Reunant C200 Controller Chassis which inclues reunant controller moules, such as CPM, RM, CNI, IOLIM, FTEB, an FIM. The controller may resie either on the Supervisory Network or on a I/O Network (currently not supporte for the CPM an IOLIM moules). On-Process migration, Reunant C300 Controllers On-Process Migration, Reunant FIM4/ FIM8/PGM On-Process Migration, Reunant EHPM On-Process migration, Reunant IEC61850M Off-process Migration scenarios Off-process Migration, Reunant Chassis Off-process Migration, Non-Reunant Chassis Off-process Migration, Reunant C300 Controllers Off-process Migration, Non-reunant C300 Controllers Use the Controller Migration wizar an Select reunant C200 controller chassis (primary an seconary chassis) at one time for on-process migration. All reunant components in the controller chassis are migrate at once. Also, iniviual controller interface components in an RCP that are reunant can be selecte for migration, such as FIMs an IOLIMs. Select reunant controller moules for migration. Select reunant Fielbus Interface Moules (FIM4/FIM8/PGM) for migration. Select reunant EHPM for migration. Select reunant IEC61850M for migration. Perform migration of reunant controller chassis off-process. All reunant components in the controller chassis are migrate at once. Select a non-reunant controller chassis for offprocess migration. All components in the controller chassis (except I/O) are migrate at once. Select reunant controller moules for migration. Select iniviual controller moules for migration. 78

79 5 STARTING MIGRATION Controller Migration scenario Off-process Migration, Non-reunant controller moules, (CPM, CNI, IOLIM, FIM, FTEB an LIOM) Off-process Migration, Reunant FIM4/ FIM8/PGM Off-process Migration, Non-reunant FIM4/ FIM8/PGM Off-process Migration, Associate I/O moules Off-process Migration, ACE/ SCE-ACE an SIM-C200 Off-process Migration, Reunant EHPM Off-process Migration, Non-reunant EHPM Off-process Migration, Reunant IEC61850M Off-process Migration, Non-reunant IEC61850M Use the Controller Migration wizar an Select iniviual controller moules for offprocess migration. Select reunant Fielbus Interface moulesan PGM for migration. Select iniviual Fielbus Interface moules an PGM for migration. Select Iniviual I/O moules for off-process migration. Select iniviual ACE/SIM-ACE or SIM-C200 control noes for off-process migration. Select reunant EHPM for migration. Select iniviual EHPM for migration. Select reunant IEC61850M for migration. Select iniviual IEC61850M for migration R400.x, R410.x, R430.x, R431.x, an R432.xmigration Site-specific migration guies (R400.x, R410.x, R430.x, R431.x, R432.x an R500.x to R510.x): For migrations from R400.x onwars, you can generate a site-specific migration guie using the Upgrae Tool. As per the site configuration, the Upgrae Tool combines the migration guies available on the Experion PKS Upgrae Tool components meia for the noes/moules in the Experion cluster. This ocument is automatically generate by the Upgrae Tool. 79

80 5 STARTING MIGRATION 80

81 6 Using tools to verify upgrae reainess The following tools can be use for performing upgrae reainess checks. Migration Reainess Tool (MRT) Upgrae Tool (UT) Attention For migrations where the base release is R400.x the upgrae reainess tools must be use as follows: MRT must be use for performing server reainess checks. MRT must be use for performing controller reainess checks, before the start of server migration. UT must be use for performing controller reainess checks, after the server migration. For migration where the base release is R410.x, R430.x, R431.x an R432.x, the UT must be use for any reainess checks for servers an controllers. Migration Reainess Tool (MRT) The MRT is intene to be use only on process servers an controllers that can be configure only with a process server. You must install the MRT on Server A, Server B, an all Console Stations where the MRT is run on the base release R400.x. The Migration Reainess Tool (MRT) is a software utility that automatically performs the prerequisite checks necessary to ensure that an Experion system is reay for migration. After the MRT is run, a report is generate inicating the reainess status of the system an its components, which inclue servers, controllers, I/O chassis an remote chassis moules, an control network platforms. In all migration scenarios, the MRT is run multiple times. For example, the MRT must be run before you begin an on-process migration Run the server reainess check on Server B an Server A, an then run the controller reainess check on all associate controllers. During an on-process migration, run the MRT on Server B after it is migrate to the new release, but before Server A is migrate, (uring the ual primary state). 81

82 6 USING TOOLS TO VERIFY UPGRADE READINESS After the servers an clients are migrate, run the controller reainess check before you migrate any controller. Referhttp:// for accessing the latest version of the MRT ata files an installing them on the server, before starting MRT. For more information, refer the section Obtaining the latest Migration Reainess Tool (MRT) ata files in the Scenario specific migration guies. Upgrae Tool (UT) The Upgrae Tool checks the upgrae reainess of the noes an its subsystems in an Experion system. The Upgrae Tool is installe as a part of the Engineering tools installation. If you have reunant servers, Upgrae Tool is installe on Server B. In case of non-reunant server, Upgrae Tool is installe on the only server. The Upgrae Tool oes not epen on any specific Experion topology. In case of a reunant Experion configuration, the Upgrae Tool is run only on the Server B. In case of a nonreunant Experion server configuration, the Upgrae Tool is run on the single Experion server noe. The Upgrae Tool ensures that it oes not overloa the Experion server. Before starting an Experion upgrae, you have to verify the upgrae reainess of the Experion system an prepare it for the upgrae. The Upgrae Tool automates the manual process of preparing the Experion system for the upgrae. After the upgrae is complete, you can run the Upgrae Tool to perform a post-upgrae analysis. Upgrae Tool makes the upgrae reainess process effortless, easy, an error-free. It reuces the manual information gathering time an minimizes the possibility of errors. For more etails, refer the Experion Upgrae Tool Users Guie. 82

83 6 USING TOOLS TO VERIFY UPGRADE READINESS 6.1 Main winow The MRT main winow, as shown in the following figure, contains three menu heaings File, Reainess Check, an Help that give you access to the utility's functions. Within the winow, there are instructions you must follow on when to perform reainess tests for servers an controller components. Figure 1: MRT Main Screen 83

84 6 USING TOOLS TO VERIFY UPGRADE READINESS 6.2 File menu The file menu allows you to choose the following functions. File Menu Item Open Save as CSV Save as HTML Print Exit Function Opens a previously save reainess report. Saves a report in CSV format as an.xls file or.txt file. Selection is enable after a report is generate. Saves a report in HTML format. Selection is enable after a report is generate. Prints a generate report. Selection is enable after a report is generate. Closes the winow an exits the application. 84

85 6 USING TOOLS TO VERIFY UPGRADE READINESS 6.3 Reainess Check menu The Reainess Check menu allows you to select the type of check that you want to perform. Reainess Check menu Item Server Migration Controller Migration Function Checks for the reainess of the server(s) for migration. This check covers the following components: Reunant or Non-reunant Experion server(s). Checks for the reainess of the controller(s) for migration. This checks for the reainess of control moules resiing on: Reunant/Non-reunant Controller Chassis. Reunant/Non-reunant Remote Chassis. Checks also for compatibility of the following noes with the current an target version of Experion release. ACE, SIM-C200 (SCE), SIMIOLIM Reainess checks for migrating servers If you select Server Migration from the Reainess Check menu, the following ialog box is isplaye. It provies a list an brief escription of all checks performe uring a server migration reainess check. Note Only checks that are applicable to the selecte server(s) are performe. For example, some checks are performe only if servers are reunant. 85

86 6 USING TOOLS TO VERIFY UPGRADE READINESS Table 4: Server Migration Reainess Check escription Check Is system license for OPM? Is system license for reunancy? Is the system configure for reunancy? Is OPM not alreay running? Description This check verifies that an OPM license is enable. An OPM license must be purchase an enable to perform an on-process migration. This check verifies that a reunancy license is enable. The reunancy license must be purchase an enable to perform an on-process migration. This check verifies that the system is configure for reunancy. On-process migration can only be performe on systems that are reunant. This check verifies if OPM has been starte on the servers. 86

87 6 USING TOOLS TO VERIFY UPGRADE READINESS Check Is Server A primary? Is Server B running? Are servers synchronize? Is the EMS Database synchronize? Are there active locks? Are there checke out elements? Is the HART Multiplexer Service running? Is ERDB Language other than English? Manually verify the mngr passwor on both ServerA an ServerB are same. Description This check is performe if servers are reunant to verify that the primary server is esignate as Server A. In orer to begin an on-process migration, the primary server must be esignate as Server A an the seconary esignate as Server B. This check verifies that Server B is up an running. Server B must be running to begin an on-process migration. This check is performe if servers are reunant. This check verifies that the seconary server is synchronize with the primary server. The servers must be synchronize in orer to start an on-process migration. This check is performe if servers are reunant. For servers to be synchronize, the EMS atabase must be in sync an there must be no Event Database Replication Faile alarm liste in the alarm summary. This check ientifies whether there are any active locks currently on atabase objects. There must be no active locks on atabase objects in the ERDB when performing system migration. This check ientifies whether there are any elements currently checke out from the QVCS. It is not necessary that the elements are checke in before starting migration, but the migration may take longer to complete when elements are checke out. This check etects whether HART Multiplexer Service is running on the server/s. HART Multiplexer Service application must be stoppe before starting migration. This check ientifies if the ERDB language is other than English. This is just a warning to users that the ERDB language may be change to English uring the migration process. This check is performe if servers are reunant an verifies the equality of passwors on both Server A an Server B. Both Server A an Server B must be logge in using the same account, an the passwor of the account must be same on both servers uring migration. 87

88 6 USING TOOLS TO VERIFY UPGRADE READINESS Check Manually verify Network Configuration Information. Is the Primary an Seconary servers time synchronize? Is NTP server(s) configure? Description For FTE systems, manually verify the network configuration. For more information, refer to FTE Installation an Service Guie. This check compares the ate an time of primary an seconary servers an reports the ifference. This check verifies that the Experion servers have at least one NTP server configure. Migration may fail to complete if no NTP servers are configure Reainess checks for migrating controllers If you select Controller Migration from the Reainess Check menu, the following ialog box is isplaye. A list an brief escription of all checks performe uring a controller migration reainess check are isplaye. Attention The checks that are performe (an presente on the screen) are etermine by the controller (control harware) selecte in the MRT. Therefore, the checks that are performe are applicable only to the controller or control harware selecte, (in this case, a C300 controller). 88

89 6 USING TOOLS TO VERIFY UPGRADE READINESS Figure 2: Controller Migration Reainess Check ialog box Table 5: Controller Migration Reainess checks Check Are the RM Synchronize? Description This check is performe only if the selecte controller an its associate components are installe in a Reunant Chassis Pair (RCP). This check verifies that the Reunancy Moules (RMs) in the primary an seconary chassis are synchronize. The RMs in the primary an seconary chassis must be synchronize before you begin an on-process migration. If check fails with a Status of Check Aborte. Synchronization check failures (controller reainess check) 89

90 6 USING TOOLS TO VERIFY UPGRADE READINESS Check Is Auto Synchronization State Conitional? Are the Controllers Synchronize? Is there enough free CPU an Memory available in the controller? Is Base Execution Perio not set to Default? Is OPM license enable? Are there any Legacy CNI Moules? Description This check is performe only if the selecte controller an its associate components are installe in a Reunant Chassis Pair (RCP). This check verifies that the Auto Synchronization State of the Reunancy Moule is set to Conitional. This conition must be true before you begin an on-process migration. If check fails with a Status of Check Aborte. Synchronization check failures (controller reainess check). This check is performe only when C300 reunant controllers are selecte. This check verifies that the primary an seconary C300 controllers are synchronize. This check verifies that the total time-average free CPU available in the controller is maintaine above 40%. It also verifies that at least 20% of the memory is available. Both conitions must be true before you begin an on-process migration. This check is performe only if a CPM or LIOM moule is present. This check verifies that the CEE Base Execution Perio is not set to the efault value. This check verifies that an OPM license is enable. An OPM license must be purchase an enable to perform an on-process migration. This check is performe only if the controller an its associate components are installe in a Reunant Chassis Pair (RCP). This check etects the presence of any legacy Control Net Interface (CNI) moules in the selecte RCP. The RCP must not contain any legacy Control Net Interface moules (TC-CCN012 or TC-CCR012 or lower) to perform an on-process migration. Peer references to seconary blocks (controller reainess check). 90

91 6 USING TOOLS TO VERIFY UPGRADE READINESS Check Are there any Unassigne Channels, Moules an Unconnecte Pins? Checks are performe to etect: Description IOCHANNELS that are not assigne to any of the IOMoules. IO Moules that are not being use by any of the IO Channels. Block Pins that are left unconnecte. Note that it is not manatory to fix all these for starting onprocess migration. Unassigne channels, moules an unconnecte pins (controller reainess check). Are there any Peer References to Seconary Blocks? Are there any unsupporte Moules/Firmware? Are there any Unientifie/ Incompatible Firmware? Are there any unsupporte Moules/Firmware on Remote Chassis? Checks for any peer references to seconary chassis moules. Peer references to seconary moules must be remove to perform an on-process migration. Peer references to seconary blocks (controller reainess check). This check etects the presence of any unsupporte moules an firmware versions installe in the controller chassis. Moules an firmware versions that are not liste in the ver_rev.txt file are ientifie as unsupporte. Before starting an on-process migration, all unsupporte moules must be replace with moule types that are supporte. Aitionally, moules must be loae with a supporte firmware version for on-process migration to succee. Moule information (controller reainess check). This check is performe only for the FIM controller. It etects any unientifie/incompatible firmware version installe in FIM controller. Moules an firmware versions that are not liste in the ver_rev.txt file are ientifie as unientifie. Before starting an on-process migration, all unientifie moules must be replace with moule types that are supporte. Aitionally, moules must be loae with a supporte firmware version for on-process migration to succee. Moule information (controller reainess check). This check is performe for all the remote chassis associate with the selecte controller chassis. This check etects the presence of any unsupporte moules an firmware versions installe in all non-reunant remote chassis associate with the controller chassis. Malfunctioning peer references (controller reainess check). 91

92 6 USING TOOLS TO VERIFY UPGRADE READINESS Check Are there any Malfunctioning Peer References? Is HART Multiplexer Service running? Are there more than one CPM or two LIOMs in a chassis? Are there Active Locks? Are there any Dangling Peer Connections? Are there any Dangling Control Connections? Description This check verifies that all peer references in the CPM are performing properly. This conition must be true before you begin an on-process migration. Peer references that o not work usually inicate a configuration mismatch between the ERDB an the controller. Such a mismatch can result when the peer efinition block is reconfigure an reloae, but the block containing the peer reference is not subsequently reloae. See on page Malfunctioning peer references (controller reainess check). This check etects whether HART Multiplexer service is running on the server/s. HART Multiplexer service application must be stoppe on the associate servers before beginning a migration. Checks whether more than one CPM moule or two LIOMs are present in a chassis. A single chassis containing more than one CPM moule is not a vali configuration for performing a migration. A single chassis containing two LIOMs is not a vali configuration for performing a migration. This check ientifies whether there are any active locks currently on atabase objects. All the active locks in the ERDB must be cleare before starting a migration. ERDB active locks (server reainess check). This check etects the presence of any angling control peer reference connections in the CPM control strategy. There must not be any angling control peer reference connections in the CPM to begin an on-process migration. This check etects the presence of any angling control connections in the CPM control strategy. There must not be any angling control connections in the CPM to begin an on-process migration. Dangling control connections (controller reainess check). 92

93 6 USING TOOLS TO VERIFY UPGRADE READINESS Check Are there any Ghost/ Inconsistent Moules in the Controller? This check etects: Description Ghost moules in the controller moules or function blocks, which are present in the controller, but not in the ERDB. Inconsistent moules or blocks between the controller an the ERDB. These errors must be resolve before starting migration. See on page Ghost or inconsistent moules in the controller (controller reainess check). Is the IOLINK partner not visible or mismatche? This check is performe on reunant C300 controllers that have either Series C IO or PMIO moules connecte to them through IO Link cables. The check verifies the proper communication an IOLink cabling between the primary an seconary C300 controllers. Failures might occur if: The primary controller oes not have visibility to the seconary controller across the IO link communication path. This is because the seconary IO link cables not connecte to the primary IO link, or a harware fault to both IO link Channel A an Channel B. The primary controller is communicating with a seconary controller which is not the correct reunant partner. This is because the seconary controller's IO link cables are connecte to the primary IO link, or the correct seconary controller is connecte but primary Link1 is communicating with seconary Link 2 (IO Link cables are crosse between Link1 an Link 2 on the controllers). Controller OPM fails if any one of the above conitions is true. Are there any mismatche controller moules in Checkpoint? This check etects the following conition. After server migration an before controller migration, aing a new parameter to the controller atabase (CDB) block results in a mismatch of the CDB block between the ERDB an controller. During controller migration, rebuil of the checkpoint file creates a mismatche checkpoint file. Restoring this file to the seconary controller uring OPM, results in incomplete restore, an cause OPM to fail Reainess checks for migrating ACE, SCE, EHG or SIMIOLIM noes When an ACE, SCE, EHG or SIMIOLIM noe is selecte for a reainess check, a screen appears similar to the Controller Migration reainess check screen. The screen 93

94 6 USING TOOLS TO VERIFY UPGRADE READINESS lists the checks performe uring a controller migration check an are escribe in the following table. Check Check for compatibility of ACE/SCE/EHG/SIMIOLIM noes with current an target Experion release? Description Checks performe to verify compatibility of all the configure an liste noes with the current an target release of Experion server. 94

95 6 USING TOOLS TO VERIFY UPGRADE READINESS 6.4 Generating reports After the reainess checks are complete, a report is generate. The report can be viewe, save as a CSV file format or HTML file format, an can be printe for evaluation an reference Saving reports The report containing the results an etails of the reainess checks can be save as a file for reference. To save a report in CSV or HTML format 1 From the bottom of the Report page, select the file format to which you want to save the report ata, CSV or HTML. 2 Click the Save button. Or 3 Perform one of the following: Choose File > Save as CSV, if you want to save the report as an.xls file (for use in Excel) or a.txt file. Or Choose File > Save as HTML, if you want to save the report as an.htm file (for isplay in a browser application) Printing reports To print a report 1 Click the Print button at the bottom of the Report page to print a report. Or Choose File >Print. The results of the reainess checks an all etails are consoliate onto an HTML page. 2 Click the Print icon on the browser page. 95

96 6 USING TOOLS TO VERIFY UPGRADE READINESS 6.5 Reviewing reports The top portion of the report screen provies information relevant to the checks performe, such as the ate an time of the report, the server name, the current system release version an target release, network topology, types of migration supporte, an reainess for on-process migration. Reports for the Controller reainess checks are similar in format, but provie the results of the checks relevant to controller migration. The top portion of the report contains information relevant to the controller reainess checks, such as: Date an Time of the report Controller Name Topology Target Release Chassis Type Types of Migration Reainess to start On-process Migration 96

97 6 USING TOOLS TO VERIFY UPGRADE READINESS When running reainess checks on ACE, SCE, EHG or SIMIOLIM noes, the report contains information relevant for migration of those noes, such as: The block name Type of noe: ACE, SCE, EHG or SIMIOLIM The software version Compatibility with current Experion release version Compatibility with target Experion release version The lower portion of the report lists the checks that were performe on the system components with the Pass/Fail results an etails. Color an Status column The status of each check performe in the Check column is inicate as Pass, Fail, or Check Aborte an also is enote with a color. A status of Check Aborte inicates that the MRT faile to perform the check an that errors are liste in the error log file. The legen for the check status is shown near the bottom of the screen. Comment column The Comment column contains aitional information on the status as a result of the reainess checks. If a check status is inicate in Blue or Re as Fail ue to a system conition, the Comment column may provie recommene actions to correct system conition before attempting a system migration. Clicking Details in the Comment column, when it appears, opens a ialog box that shows the atabase object or list of objects which were ientifie uring a check as being locke or checke out. Color an Status Green: OK Re: Must be fixe Blue: Might be fixe Comment The result of the check is OK (Pass) an no action is require. The current system conition may cause the migration process to fail or abort. The conition must be correcte before attempting a migration. You may want to correct the conition, an then run the reainess check again. The current system conition is not correct an oes not cause a migration to fail. The conition can be fixe if necessary Reviewing faile items When the results of a reainess check show a Status of Fail, a Details link may exist in the Comment column of the report. Clicking the link opens a ialog box that provies more information about the components or atabase objects that cause the check to fail. 97

98 6 USING TOOLS TO VERIFY UPGRADE READINESS You may nee to correct these conitions that cause the check failure before you procee with a system migration. Some conitions prevent a successful system migration, while others may cause the migration process to take longer to complete. The following paragraphs escribe the pop up screens that appear when the Details link for a particular reainess check is clicke an provie further information on the causes for the reainess check failure. Suggeste corrective actions may also be given to remey failure conitions. ERDB active locks (server reainess check) When status for the check Are there Active Locks? is Fail or is re, you can click on the Details link to isplay a list of the atabase objects which are ientifie as being locke. The table ientifies the Object Name, the Object Type an the User's login Name that is currently using the object. You must clear these locks using DbAmin tool, before starting migration. 1. Ensure that you are logge on to the server using an account that is part of Prouct Aministrator's group. 2. Launch Configuration Stuio an connect to the server where you are planning to install the point release. Launch the bamin tool by selecting the Aminister the Control strategy Datbase in Control Strategy section. 3. In the bamin tool, browse to Console Root / DbAmin / ERDB Active Locks. 4. Active locks will be liste on the right pane. Select Clear All Locks uner Action in the menu bar to clear the locks. Checke out elements (server reainess check) In systems that have Qualification an Versioning Control (QVCS), you can view the list of checke out elements by clicking the Details link, when it appears across from Are there Checke Out Elements?. A ialog box opens that ientifies the Object Name, the Version of the object, an the User's login name that has the object checke out. 98

99 6 USING TOOLS TO VERIFY UPGRADE READINESS Figure 3: Details log of Checke Out Elements It is not necessary that these elements be checke in before starting the migration process, but checking in the elements may help to minimize any failures uring migration. Synchronization check failures (controller reainess check) Failures of the checks Are the RM Synchronize? an Is Auto Synchronization State Conitional? with a Status of Check Aborte may occur when you run the Controller Reainess check on C200 controller. The controller may have IO moules loae to the monitoring atabase which are non-existent or switche off. If this conition occurs, perform the following steps: 1. Delete any non-existent IOMs from the Monitoring view. Delete any IOM instances for harware that is switche off. Delete any IOM instance where the loa has faile, (appears as re) in Monitoring view. 2. Run the Controller reainess check again on the controller. 99

100 6 USING TOOLS TO VERIFY UPGRADE READINESS 3. If the error persists, check the values of Synchronization Status an Auto Synchronization State parameters in the RM function block. Vali values for migration must be: Synchronization Status = Synchronize Auto Synchronization State = Conitional Legacy CNI moules (controller reainess check) Clicking the Details link, when it appears, across from Are there any Legacy CNI Moules? opens a ialog box that shows the Block Name an Moel Number of the CNI moules present on the reunant chassis pair (TC-CCN012 or TC-CCR012). You must replace these ControlNet moules with TC-CCN013/TC-CCR013 or TC- CCN014/TC-CCR014 before performing an on-process migration. Also in the ialog box, the table shows the slot number of the CNI moule an the MACID of the CNI moule. See the topic Common Experion Process Controller tasks in the Control Harware an I/O Moules Firmware Upgrae Guie for more information an proceures to replace CNI moules in reunant C200 controllers an non-reunant chassis. Unassigne channels, moules an unconnecte pins (controller reainess check) Clicking the Details link, when it appears across from Are there any Unassigne Channels, Moules an Unconnecte pins?, opens a ialog box that shows information regaring: IOCHANNELS that are not assigne to any IO Moules. IOMODULES that are not use by any of the IO Channels. Block pins that are not connecte. It is not necessary to correct all items ientifie by this check, but correcting them helps to minimize any failures uring migration. Peer references to seconary blocks (controller reainess check) Clicking the Details link, when it appears across from Are there any Peer References to Seconary Blocks?, opens a ialog box that shows information regaring peer references to seconary block moules. In the ialog box, a table lists the following information about the peer references to seconary blocks. Strategy Name, which contains the peer reference to the seconary block. Parameter name referring to the seconary block. It is necessary to remove these references to seconary blocks before starting on-process migration

101 6 USING TOOLS TO VERIFY UPGRADE READINESS Moule information (controller reainess check) Information on the moules iscovere in selecte reunant or non-reunant chassis uring the controller reainess checks can be isplaye by clicking on the Details link. The following moules may be liste in the Moule Information ialog box. Supervisory CNI or FTEB moules. CPM, RM, FIM, IOLIM, an I/O in the primary chassis lists. Downlink CNI moules. Reunant moules installe in the seconary chassis. The following information about the moules is liste in the ialog box. Primary component (moule) name an moule firmware version. Seconary component (moule) name an moule firmware version. Moule moel number, Slot number, an Firmware status. Figure 4: Moule Information Details log The moule information is presente in color, which further enotes the firmware status. 101

102 6 USING TOOLS TO VERIFY UPGRADE READINESS Green: Latest Color an Status Blue: Firmware Mismatch Re: Unientifie Firmware Orange: Unsupporte /Unconfigure Moule Purple: Incompatible Firmware Description Moules loae with firmware versions same as the target release. Moules loae with firmware versions that are ifferent from the target release. The firmware loae in the moule is not recognize. The moule ientifie is not supporte for system migration, or the moule in the chassis is not configure. This status appears only when the user chooses to migrate to a service pack. This conition inicates that the firmware version is incompatible because of one of the following reasons. 1. Base release of the moule firmware version is ifferent from the base release of the target service pack release. 2. The moule firmware version is same as the target service pack release, that is the moule is alreay migrate to the service pack version. Remote chassis moule information (controller reainess check) Information on the moules iscovere in a non-reunant remote chassis uring the controller reainess checks can be isplaye by clicking the Details link. CNI, IOLIM, an I/O moules may be ientifie an liste in the Remote Chassis Moule Information ialog box. The following information about the moules is liste in the ialog box. Block Name Moule Firmware Version Moule Moel Number Slot Number Status of the firmware version A color legen is use for ientifying the firmware status currently loae in the moule. It is ientical to the colors use in the Moule Information box. For more etails, see Moule information (controller reainess check). Malfunctioning peer references (controller reainess check) Clicking the Details link, when it appears across from Are there any Malfunctioning Peer References?, opens a ialog box that shows information regaring the peer references ientifie uring the reainess check that might not be functioning properly

103 6 USING TOOLS TO VERIFY UPGRADE READINESS You must work to remey these references before starting on-process migration. In the ialog box, a table lists the following information about the peer references. Strategy Name on Peer 1 an the Parameter Name containing the reference. Strategy Name on Peer 2 an the Parameter Name containing the reference. Comment proviing aitional etails. Dangling control connections (controller reainess check) During the controller reainess check for Are there any Dangling Control Connections?, if any angling control connections are etecte in the CPM control strategy, you can view them by clicking the Details link in the report. A ialog box opens with a table ientifying the: Strategy Name in which the control connection is missing. Parameter Name containing the name of the control connection. Error Description of the improper control connection. You must resolve any angling control connections before starting on-process migration. Ghost or inconsistent moules in the controller (controller reainess check) Resolve any ghost moules or blocks ientifie by the MRT. Go to Control Builer an choose Ientify ERDB/Controller Inconsistencies to correct these errors. Resolve any inconsistent moules or block in the controller by reloaing these moules to the controller. 103

104 6 USING TOOLS TO VERIFY UPGRADE READINESS 104

105 7 R510.x migration reference Starting from R431.2, irect migration to point releases are supporte. For more information refer to Experion migration concepts on page 15 section. Relate topics Qualifie migration paths on page 106 R510.x system interoperability on page 109 Software requirements on page 121 Harware requirements on page 126 Experion installation space requirements on page 127 Experion migration space requirements on page 130 Experion Migration Storage Noe (EMSN) space requirements on page 133 Multi-cluster migration scenarios on page 134 Experion High Security Policy changes on page

106 7 R510.X MIGRATION REFERENCE 7.1 Qualifie migration paths R510.x server/client migration paths Migration paths illustrate the path for an Experion system migration from the base release (or current release) to the target release (new release). A migration path may also inclue intermeiate steps. For more information, contact the HPS Migration Center of Excellence. Note that migration paths apply to servers an clients. Table 6 lists the migration paths that are supporte in Experion R510.x for Experion Servers, Console, an Flex Stations. Refer to the Software Change Notice (SCN) available on the Honeywell Process Solutions website (Honeywell Process Solutions website) for the most up-to-ate migration paths. Attention The following on-process an off-process migration paths are supporte for physical to virtual an virtual to virtual migrations: Experion R400.x (with or without patches ) to Experion R510.x Experion R410.x (with or without patches ) to Experion R510.x Experion R430.x (with or without patches ) to Experion R510.x Experion R431.x (with or without patches ) to Experion R510.x Experion R432.x (with or without patches ) to Experion R510.x Note R400 Server Patch 4 is a manatory for migration from R400.1 / R400.2 an R400.3 (with or without patches)

107 7 R510.X MIGRATION REFERENCE Table 6: Server/client migration paths supporte Migration Path to R510.x R400.x, R410.x, R430.x, R431.x, an R432.x for On-process Migration Off-process Migration Documentation References X X Site-specific migration guies (R400.x, R410.x, R430.x, R431.x, R432.x an R500.x to R510.x): For migrations from R400.x onwars, you can generate a site-specific migration guie using the Upgrae Tool. As per the site configuration, the Upgrae Tool combines the migration guies available on the Experion PKS Upgrae Tool components meia for the noes/moules in the Experion cluster. This ocument is automatically generate by the Upgrae Tool. For exact migration paths supporte to target point release, refer to the latest target point release Software Change Notice (SCN). For example, refer to the latest target release SCN R510.x controller migration paths You can migrate the server from R400.x to R510.x when some of the controllers are still on R400.x You can migrate the server from R410.x to R510.x when some of the controllers are still on R400.x. You can migrate the server from R430.x to R510.x when some of the controllers are still on R410.x. You can migrate the server from R431.x to R510.x when some of the controllers are still on R430.x. You can migrate the server from R432.x to R510.x when some of the controllers are still on R431.x. The qualifie migration paths for migrating controllers, interface moules, an I/O moule firmware to Experion R510.x are etermine using the Migration Reainess Tool/Upgrae Tool. Only vali firmware release versions are liste in the Select Target Release box of the Controller Migration ialog box. Refer the target point release Software Change Notice (SCN) ocument supplie with your software for the most upto-ate migration paths. In the following table, on-process migration applies only to reunant controller an I/O moule components. 107

108 7 R510.X MIGRATION REFERENCE Experion Control Harware Controllers: C200 (CPM), C200E, an C300 EHPM an IEC61850M can be migrate using Controller Migration Wizar. Interface Moules: RM, IOLIM, FIM, FIM4, FIM8, PGM, FTEB, CNI, LIOM I/O Moules: Table 7: Controller noes supporte for migration On-process migration (Only if reunant) X X Off-process Series C IOMs X X Series A IOMs, Series H IOMs (non-reunant) Application Environments: ACE, SCE, SIMLIOM EHG X X X X X 108

109 7 R510.X MIGRATION REFERENCE 7.2 R510.x system interoperability Experion R510.x allows greater interoperability between noes operating on ifferent releases. You can use applications for engineering work an configuration an then ownloa the changes to noes operating on ifferent releases. However, there are restrictions to the engineering work an operations uring the migration. There are lesser restrictions after the servers are migrate, an controllers are operating on an oler release. Interoperability rules in Experion are such that you can continue the engineering work an operations in a multi-release environment in the same way as was one in the past in a single release environment. The general restrictions in interoperability are as follows: Before migration: There are no restrictions if all connecte clusters are at the same release an upate level. During migration while servers are in Dual Primary state: Configuration changes are restricte to ensure system integrity. A server an its associate client must be at the same release an upate level in orer to connect. Clients can only connect to a server operating on the same release as the client. No engineering changes must be mae to a cluster until all noes within that cluster are migrate to the same release an upate level. Alarms an point ata are typically accessible through DSA between clusters of ifferent releases an upate levels both uring an after migration. Refer to EMDB Interoperability table in Enterprise Moel Database (EMDB) interoperability section to see the release interoperability of servers for DSA. After migration: In some cases, configurations from previous releases must be upate to the latest version before changes can be mae. For example after migration, user-efine custom isplay an shape files nee to be upate to the current release so that they can be use in Station. Only a subset of engineering tasks may be available. For example, two clusters operating at ifferent releases; some engineering tasks which are available when working within a cluster operating with the same release, may not be available when working on the cluster operating with the ifferent release. 109

110 7 R510.X MIGRATION REFERENCE Interoperability summary Server interoperability with controllers This section summarizes the release interoperability support between server an the various controller type noes. In the table, Server Release represents all applications running in a server (such as Control Builer an real time ata cache) that interact with applications running in a controller, (such as CEEs). The table inicates that R510.x Server interoperates with controllers operating with R400.x, R410.x, R430.x, R431.x, an R432.xan R510.xfirmware. R500.x Control Builer allows you to loa an uploa controllers operating with R400.xor later firmware. You can eit, loa, an uploa controllers operating with, R400.x (R400.1, R400.2, an R400.3), R410.x (R410.1 an R410.2),, R430.1 R431.x R432.x firmware with the exception being that new features available in R500.x are not applicable in controllers running with the oler release firmware. Serve r Relea se R510.x Experion Controllers (C200, FIM, C300, FIM4, IOLIM, LIOM, ACE an SIM-C200) R210 R301.x R310.x R311.x R400.x R410.x R430. x Not Not Support e Not Not Support e Supp orte R431.x Supp orte R4 32. x Su pp ort e R51 0.x Sup port e eserver interoperability R510.x eserver supports interoperability with previous Experion releases, R400.x, R410.x,R430.x, R431.x, an R432.x. Interoperability is not supporte with Experion R Domain controller interoperability A omain controller (server) use in an Experion system operates as an inepenent noe an is migrate separately. This section summarizes the interoperability of a omain controller in an Experion system

111 7 R510.X MIGRATION REFERENCE Domain Controller Operating System Microsoft Winows Server 2012 Microsoft Winows Server 2016 Experion Server Releases R301.x R310.x R311.x R400.x R410.x R43X.x R510.x Not supporte Not supporte Not supporte Not supporte Not supporte Not supporte Not supporte Not supporte Not supporte Not supporte Suppor te Not suppor te Sup port e Sup port e C200 an C300 controller interoperability Release interoperability for C200 an C300 controllers with other controller type noes is summarize in the following tables. C200 Controller Release R2xx.x R301.3 R31x.x R400.x R410.x R43X.x R x R210 Not R301.3 Not Not Not Not N ot S u p p or te N ot S u p p or te 111

112 7 R510.X MIGRATION REFERENCE C200 Controller Release R2xx.x R301.3 R31x.x R400.x R410.x R43X.x R x R310.3 R311.2 R311.3 R400.x R410.x Not Not Not N ot S u p p or te N ot S u p p or te N ot S u p p or te S u p p or te S u p p or te 112

113 7 R510.X MIGRATION REFERENCE C200 Controller Release R43X.x R510.x R2xx.x R301.3 R31x.x R400.x R410.x R43X.x R x Not Not Not Not Not S u p p or te S u p p or te C200 Controller Release R2xx.x R301.3 R31x.x R400.x R410.x R43X.x R x R210 Not R301.3 Not Not Not Not N ot S u p p or te N ot S u p p or te 113

114 7 R510.X MIGRATION REFERENCE C200 Controller Release R2xx.x R301.3 R31x.x R400.x R410.x R43X.x R x R310.3 R311.2 R311.3 R400.x R410.x Not Not Not N ot S u p p or te N ot S u p p or te N ot S u p p or te S u p p or te S u p p or te 114

115 7 R510.X MIGRATION REFERENCE C200 Controller Release R43X.x R510.x R2xx.x R301.3 R31x.x R400.x R410.x R43X.x R x Not Not Not Not Not S u p p or te S u p p or te Controller CDA/Exchanges peer to peer connections The following table lists the restrictions when setting up peer-to-peer connections between controller type noes operating on ifferent releases. C300 Controller (Initiator) R2xx Experion Controllers (C200, C300, FIM4, IOLIM, LIOM, an ACE) (Target/Responer) R2xx.x R301.x R31x.x R400.x R410.x R43X.x R510.x R301.3 R310.3 R31x.x R400.x Not Not Not Not Not Not Not Not Not Not 115

116 7 R510.X MIGRATION REFERENCE C300 Controller (Initiator) R410.x R43X.x R510.x Experion Controllers (C200, C300, FIM4, IOLIM, LIOM, an ACE) (Target/Responer) R2xx.x R301.x R31x.x R400.x R410.x R43X.x R510.x Not Not Not Not Not Not Not As the previous table inicates, controller CDA/Exchange peer-to-peer from a C200 controller on R210 to a C300 controller on R3xx works only when the connection is efine (initiate) in the C300 controller. Experion Controllers (C200, C300, FIM4, IOLIM, LIOM, ACE) (Initiator) R2xx Experion Controller C300, FIM4 (Target/Responer) R2xx.x R301.x R31x.x R400.x R410.x R43X.x R510.x R301.3 R310.3 R311.x R400.x R410.x Not Not Not Not Not Not Not Not Not Not Not Not 116

117 7 R510.X MIGRATION REFERENCE Experion Controllers (C200, C300, FIM4, IOLIM, LIOM, ACE) (Initiator) R43X.x R510.x Experion Controller C300, FIM4 (Target/Responer) R2xx.x R301.x R31x.x R400.x R410.x R43X.x R510.x Not Not Not Not As the previous table inicates, controller CDA/Exchange peer-to-peer from a C200 controller on R210 to a C300 controller on R3xx works only when the connection is efine (initiate) in the C300 controller. Checkpoint file interoperability The format of checkpoint files in a given release of Experion is unique so that the checkpoint files of one release are not compatible with other Experion releases. For example, R400.x Checkpoint files are not compatible with Experion Release R500.x. Similarly, R500.x checkpoint files are not compatible with Experion Release R400.x. Therefore, you must execute Checkpoint Rebuil uring migration, so that the checkpoint file format conforms to the new server release. For example, a reunant R400.x server pair is being migrate to R500.x - after Server B is migrate to R500.x Enterprise Moel Database (EMDB) interoperability While migrating the EMDB, some functions are isable. For example, the EMDB (an ERDB) are locke to prevent any changes until migration is complete. Aitionally, features which are available in newer releases are not available on noes operating at earlier releases until they are migrate to the new release. For example, an EMDB server an a client that are migrate to R500.x can take avantage of the features available with the new release, (for example, the Network Tree). The client (operating with R500.x ) can loa EMDB changes to a server operating at the oler release R4xx, but the network tree is not available to use on the R4xx server. After the server is migrate to R500.x, the network tree is visible an available on the server. The following figure illustrates the interoperability of the EMDB in multi-cluster, where one cluster is operating with R400.1 an a secon cluster has been migrate to R500.x. The Network Tree is not present in R400.1, although the system efinitions, assets, an alarm groups in the EMDB atabase can be ownloae an uploae from the R500.x cluster, where the system EMDB is locate. 117

118 7 R510.X MIGRATION REFERENCE Tip Server Runtime inclues the EMDB that is loae to the server. The otte line between Server Runtime an CB represents the synchronization of changes one in EM assets an use by the Control Builer. The following table shows the interoperability of EMDB across Experion releases. The same interoperability rules applies for DSA communication. Experio n Release Experio n R500x Experio n R43x Experio n R410.x Experio n R400.x Experio n R31x Experio n R30x Experio n R21x Can interoperate with Experion R500 EMDB Can interoperate with Experion R43X EMDB Can interoperate with Experion R410.x EMDB Can interoperate with Experion R400.x EMDB Can interoperate with Experion R31x EMDB Can interoperate with Experion R30x EMDB Can interoperate with Experion R21x EMDB Yes No No No No No No Yes Yes No No No No No Yes Yes Yes No No No No Yes Yes Yes Yes No No No Yes Yes Yes Yes Yes No No Yes No No Yes Yes Yes No No No No No Yes Yes Yes 118

119 7 R510.X MIGRATION REFERENCE Note The interoperability efine here is limite to efining the Experion system as part of the EMDB server (eg: for DSA) an configuration loa in EMDB for Assets Alarmgroups etc. onto all the configure servers. R311.2 Server Patch243 for PAR1-J43NXT patch is manatory on R311 system to ensure interoperability. R310 Server Patch680 for PAR1-K7N7TZ patch is manatory on R310 system to ensure interoperability. R301.3 Server Patch093 for PAR1-WKEFV9 patch is manatory on R301 system to ensure interoperability. Refer to respective patch SCNs for more etails. The following figure shows two clusters, one operating with R4xx an the other that has been migrate to R500.x. EMDB interoperability is fully supporte between the clusters. Note that interoperability is supporte also when the EMDB is locate in the R4xxcluster. In other wors, the EMDB can be locate in either cluster an still support full interoperability. Figure 5: EMDB Interoperability between R400.x an R500.x CAB interoperability CAB types existing within the ERDB on R400.x, R410.x, R430.X, R431.x, an R432.x servers, which are then migrate to R500.x an left unchange, can be loae to an R400.x, R410.x, R430.X, R431.x, an R432.xservers, which are then migrate to ACE noes. 119

120 7 R510.X MIGRATION REFERENCE Attention After a CAB type is opene an eite by the R510.x buil-time, it can no longer be loae to an R400.x ACE noe. A CAB type, that is built or eite on an R510.x system, can be loae only to an ACE noe operating with R510.x. CAB Target R301.3 R310.3 R311.x R400.x R410.x R43X.x R510.x Create or eite with control builer release See Note 1. R301.3 R310.3 R311.x R400.x R410.x R43X.x R510.x Not Not Not Not Not Not Not Not Relate topics Server interoperability on page 32 Controller interoperability on page 37 Domain controller interoperability on page 34 eserver interoperability on page 33 Enterprise Moel Database (EMDB) interoperability on page 41 Controller CDA/exchange peer-to-peer connections on page 37 System interoperability concepts on page

121 7 R510.X MIGRATION REFERENCE 7.3 Software requirements Relate topics Software meia requirements on page 121 Microsoft an other Experion upates on page 122 Reapplying software patches on servers on page 122 Total Plant Network (TPN) software on page 123 Honeywell Experion PKS Localization Meia on page 125 SCADA system communication protocols on page 125 Review software requirements on page Software meia requirements Whether you are migrating to or installing Experion R510.x, you require the following software meia for upgraing either Experion Server or Station. Honeywell Experion meia: Experion PKS System Initialization meia Experion PKS System Initialization Upates meia Experion PKS Installation meia 1 Experion PKS Installation meia 2. The latest point release Experion Support Software is available as an ISO image on Honeywell Process Solutions website ( Use the ISO image content to create a DVD/meia for installing the latest Experion point release. For extracting contents to a meia, use ISO extraction software. For example, you can use Virtual Clone Drive software for extracting the contents to a meia. Microsoft Visual Stuio for CAB Developer meia. (optional, require only if CAB is selecte). Experion Support an Maintenance meia Microsoft SQL Server 2014 SP2 Experion PKS with PMD controller meia (optional) For operating system, the following meia are require. Winows Server 2016 HPS OS reinstallation meia Winows 10 (64-bit) HPS OS reinstallation meia 121

122 7 R510.X MIGRATION REFERENCE Microsoft an other Experion upates There are two types of upates or patches as follows: 1. Patches or upates that must be installe immeiately after upgraing an before using the server. In case of reunant servers, the patches must be installe immeiately after upgraing each server. Most of such upates are from thir parties like Microsoft. 2. Patches or upates that nee not be installe immeiately after upgraing an before using the server. You can use the server after the upgrae without installing the patch. In case of reunant servers, such patches can be installe even after both the servers are upgrae. Most of such upates are from Honeywell Reapplying software patches on servers You may have installe patches for specific server issues. Some of these patches may not be inclue in R500.x Use the following list to etermine if you nee to reapply any of the upates that are not inclue in R500.x. If you have applie a patch with a patch number equal or greater than the number liste in the following table, you may nee to obtain an reapply a newer version of the patch that is compatible with Experion Server/Client R500.x release. From Release Patch Number (nee to reapply after migration) R400.1 R400.2 R400 SP2 208, 209 R400.3 R410.1 R410.2 R410.3 P003 Attention The base releases (for example, R311.2, R311.2 Server Patch 1) are all inclue in the R400.1 General Release. However, if you have installe a patch with a patch number greater than the patch numbers mentione in the table that you may nee to reapply a newer patch. About the patch number 122

123 7 R510.X MIGRATION REFERENCE The patch number is embee in the name of the patch file. Experion.RRelease.Subsystem.PatchNumber.PARNumber.zip Release= The release of the prouct PatchNumber= The patch number PARNumber=PAR number of the issue reporte For example: ExperionPKS.R310.2.Server.Patch016.PAR1-APQ57X.zip Release = R310.2 PatchNumber = 016 PAR Number = 1-APQ57X Refer to the patch install log, for the history of patches applie on the noe. The efault location of this log file is as follows: For Server/ESVT/Console Station: C:\Program Files\Honeywell\Experion PKS \Server\Setup\Software Upate log.txt. For Flex Station/EST: C:\Program Files\Honeywell\Experion PKS\Client\Setup \Software Upate log.txt Patch log files You may also refer to the Patch log for the history of patches applie on the noe. The efault location of this log file is: For Server/ESVT/Console Station - C:\Program Files\Honeywell\Experion PKS\Server \Setup\Software Upate log.txt. For Flex Station/EST - C:\Program Files\Honeywell\Experion PKS\Client\Setup \Software Upate log.txt Total Plant Network (TPN) software The minimum release level of TPN software that is fully compatible with Experion release software is shown in the following table. Compatibility for ES-T an ESVT integration with any Experion release. ACE-T integration with any Experion release. R652.1 or later R652.1 or later LCN Software Release 123

124 7 R510.X MIGRATION REFERENCE Experion Release Series R201, R21x, R301.x TPN R641.2 R400.x, R410.x, R430.xR431.x, R432.x, an R510.x Minimum TPN System Software TPN R535.1 or later R5xx releases in this series. TPN R652.1 or later R6xx releases in this series. For more information about TPN software compatibility, refer to the latest Experion General Release Software Change Notice. Attention TPN R683.2 or later an Experion R410.x is require for: New TPS Console/System alarm integration Fully functioning integration for HMI Web TPS Detail Displays Ensure that you are using the Utilities an Loa Moule (ULM) meia that correspons to the Experion release for the proper version of the Z12 an Z14 emulate. In Experion R310 release, the following are the functionalites that require LCN R680. Uncertain quality for TPS points OPC applications, currently has access to the existing value quality fiel for the PV parameter fetch. However, this is not currently fille in from the PV parameter fetch quality base on the PVSTS LCN parameter. This functionality provies the ability to return the UNCERTN quality of PV in TPN server. This functionality is optional for the users an if not selecte, there is no change in the existing functionality. Disable alarm inication TPN server functionality is unaffecte irrespective of optional activation of the isable alarm inication. TPN server must be able to ignore the new bit in the event recor if the option is activate. This is applicable to TPN server of both TPS an Experion. The ESVT can use the flag in the event recor an TPN server to store the isable events in Experion journal when the new bit of information is set, irrespective of the NCF option selecte. The functionality is leverage to ESVT to ientify alarms as isable in its propagation to the Experion alarm system. ESVT is use to supply operational alarm information, yet it is esigne to be an event logger. The use of the isable inication allows TPN server not to propagate isable alarms to operational clients. For example, an alarm summary on flex station. TPN server must be able to use the new bit in the event recor to ientify isable alarms. With LCN R681, the selective cutout feature allows the alarms of a point to pass through the seconary point in the cutout state. The NIM, flag, numeric, regulatory control, regulatory PV, igital input, analog input, igital composite, an evice control points can be configure with the new parameters to enable selective cutout. Selective cutout operates in combination with the contact cutout feature. This feature is supporte from R311 onwars

125 7 R510.X MIGRATION REFERENCE Note that the latest versions of the EST an ESVT loa moules must be use, which are: EST 68.1 an ESVT The loa moule software is locate on the Utilities an Loa Moule CD, which can be orere through the Honeywell Process Solutions (HPS) Online Support web site Honeywell Experion PKS Localization Meia If the Experion system to be migrate is a localize system, the following aitional software is neee. Experion PKS R500.1 EUI pack - For the language of the base system. For Microsoft Winows Server 2008 Stanar anmicrosoft Winows Server 2008 R2 Stanar: Microsoft Winows Server 2008 Stanar anmicrosoft Winows Server 2008 R2 Stanar MUI pack CD for require language. Microsoft Office 2007 MUI pack CD For Microsoft Winows 7 (64-bit): Experion PKS R500.1 EUI pack CD (this pack contains the Language Pack Installer (LPI) which is use for installing the language pack) Microsoft Office 2007 MUI pack CD SCADA system communication protocols Experion SCADA Server communicates with a variety of SCADA evices using ifferent protocols (such as, Mobus, Allen-Braley, so on). Most of these protocols are not uner control of Honeywell, but the majority of these protocols have not change. Unless there is a protocol change, it can be assume that the new releases of Experion Server continue to be compatible with the existing SCADA evices. 125

126 7 R510.X MIGRATION REFERENCE 7.4 Harware requirements For list of supporte platforms, refer to the latest Experion PKS System Initialization meia Software Change Notice. For information about software/harware/firmware compatibility refer to the latest Experion Software Change Notice. If you are migrating a system which is not a supporte platform for R510.x, you must perform a platform harware change uring the migration to R510.x. Attention You cannot change the operating system type uring a migration. For example, you cannot change the server operating system to a workstation operating system uring migration

127 7 R510.X MIGRATION REFERENCE 7.5 Experion installation space requirements Experion installation using Experion PKS System Initialization meia The Experion system must have minimum of 60 GB har isk space in C rive for the Experion PKS System Initialization meia to install the following: Operating system Operating system upates Drivers Using the following metho, calculate the minimum free har isk space require for the operating system installation: 55 GB (operating system + base Experion) + GB RAM size x 1.5 (page file) + GB RAM size x 1.5 (ump file). If the calculate value is greater than 60 GB, then 60 GB is the minimum free har isk space require. For example, in a system with 4 GB RAM, the minimum free har isk space require for the operating system installation is 67GB (55 + 4* *1.5). Hence, 67 GB is the minimum free har isk space require for operating system installation. If the calculate value is lesser than 60 GB, then the calculate value is the minimum free har isk space require. Hence, 60 GB is the minimum free har isk space require for operating system installation. Attention If you are installing Experion in custom installation path, refer to Custom installation path section, for the isk space require for each of the custom install paths. The minimum space require in C rive (60 GB) is inepenent of efault or custom installation paths. The Experion PKS System Initialization meia isplays a warning if the recommene isk space is not available, an oes not allow you to install on C: rive. Experion installation without using Experion PKS System Initialization meia The har isk space requirement to install Experion without using Experion PKS System Initialization meia is as follows. Default path: If you are planning to install Experion in the efault path, each noe must meet minimum space requirements in C rive as follows. Noe Server (ESV) Server TPN Connecte (ESVT) eserver Minimum space 32 GB 32 GB 32 GB 127

128 7 R510.X MIGRATION REFERENCE Noe Application Server (EAS) Application Control Environment (ACE) Application Control Environment TPN Connecte (ACE-T) Simulation environments Experion Hiway Gateway (EHG) App Noe (E-APP) PC Universal Station(PCUS) Console Station (ES-C) Console Station TPN connecte (ES-T) Console Extension Station (ES-CE) Flex Station (ES-F) Collaboration Station Optional Components Minimum space 32 GB 14.5 GB 14.5 GB 14.5 GB 14.5 GB 14.5 GB 14.5 GB 28.5 GB 28.5 GB 28.5 GB 28.5 GB 28.5 GB 4 GB Custom install path: If you are planning to install Experion in the custom installation path, the path you select for each component must meet the minimum space requirements. Noe Thir party application (Default rive: C rive) Experion Software path Experion Runtime Data path Server (ESV) 17.5 GB 8.5 GB 5 GB 1 GB Server TPN Connecte (ESVT) 15 GB 8.5 GB 5 GB 1 GB eserver 13.5 GB 5 GB 5 GB 1 GB Application Server (EAS) 15.5 GB 7 GB 5 GB 1 GB Application Control Environment (ACE) Application Control Environment TPN Connecte (ACE-T) 9.5 GB 2 GB 2 GB 1 GB 9.5 GB 1.5 GB 2 GB 1 GB Simulation environments 8 GB 1.5 GB 2 GB 1 GB Experion Hiway Gateway (EHG) 7 GB 1 GB 2 GB 1 GB App Noe (E-APP) GB 2 GB 1 GB Experion SQL Logs path 128

129 7 R510.X MIGRATION REFERENCE Noe Thir party application (Default rive: C rive) Experion Software path Experion Runtime Data path Console Station (ES-C) 17.5 GB 9 GB 2 GB NA Console Station TPN connecte (ES-T) Console Extension Station (ES- CE) 16 GB 8.5 GB 2 GB NA 16 GB 8 2 GB NA Flex Station (ES-F) 16.5 GB 8 GB 2 GB NA Collaboration Station 16.5 GB 8 GB 2 GB NA PC Universal Station (PCUS) 3.5 GB GB NA Experion SQL Logs path 129

130 7 R510.X MIGRATION REFERENCE 7.6 Experion migration space requirements Experion migration with operating system change Migration with operating system change uses the same space numbers that have been calculate for the Experion installation without using Experion PKS System Initialization meia (refer to the table in the above section) along with the ata present in the system. For example, size of the SQL atabase in the system. Attention If you are planning for migration with operating system change, then approximately 12 GB of har isk space is require on C: rive for operating system installation. Experion migration without operating system change Migration without operating system change uses the same space numbers that have been calculate in the below table with the ata present in the system. For example, size of the SQL atabase in the system. Attention If you are planning to use the local noe (unergoing migration) as EMSN repository, then EMSN space is ae to the space calculate for software path. The har isk space requirement for migration without operating system change is as follows. Default Path: If you are planning for migration without operating system change in the efault path, each noe must meet minimum space requirements along with the ata present in the system. Noe name Server (ESV) Server TPN Connecte (ESVT) eserver Application Server (EAS) Application Control Environment (ACE) Application Control Environment TPN Connecte (ACE-T) Simulation Environments Experion Hiway Gateway (EHG) App Noe (E-APP) Minimum space 29.5 GB 29.5 GB 29.5 GB 29.5 GB 10 GB 10 GB 10 GB 10 GB 10 GB 130

131 7 R510.X MIGRATION REFERENCE Noe name PC Universal Station (PCUS) Console Station (ES-C) Console Station TPN Connecte (ES-T) Flex Station (ES-F) Collaboration Station Console Extension Station (ES-CE) Minimum space 10 GB 19 GB 19 GB 19 GB 19 GB 19 GB Custom install path: If you are planning for migration without operating system change in the custom installation path, the path you select for each component must meet the minimum space requirements along with the ata present in the system. Noe name OS path Software path Runtime path SQL Logs path Server (ESV) 15.5 GB 9 GB 4 GB 1 GB Server TPN Connecte (ESVT) 15.5 GB 9 GB 4 GB 1 GB eserver 15.5 GB 9 GB 4 GB 1 GB Application Server (EAS) Application Control Environment (ACE) Application Control Environment TPN Connecte (ACE-T) Simulation Environments Experion Hiway Gateway (EHG) 15.5 GB 9 GB 4 GB 1 GB 3 GB 4 GB 2 GB 1 GB 3 GB 4 GB 2 GB 1 GB 3 GB 4 GB 2 GB 1 GB 3 GB 4 GB 2 GB 1 GB App Noe (E-APP) 3 GB 4 GB 2 GB 1 GB PC Universal Station (PCUS) Console Station (ES-C) Console Station TPN Connecte (ES-T) 3 GB 4 GB 2 GB 1 GB 10.5 GB 6.5 GB 2 GB NA 10.5 GB 6.5 GB 2 GB NA Flex Station (ES-F) 10.5 GB 6.5 GB 2 GB NA 131

132 7 R510.X MIGRATION REFERENCE Noe name OS path Software path Runtime path SQL Logs path Collaboration Station Console Extension Station (ES-CE) 10.5 GB 6.5 GB 2 GB NA 10.5 GB 6.5 GB 2 GB NA 132

133 7 R510.X MIGRATION REFERENCE 7.7 Experion Migration Storage Noe (EMSN) space requirements You can use the following as a guiance to calculate the EMSN space requirements. To etermine Total space (T), right-click Drive C: an click Properties. The use space is isplaye in the ialog box that appears. The Base size in is the estimate for the Experion software installe in the server/client noe, minus Experion ata an atabase files store on the noe. Options inclue optional Experion software files (CAB) an other thir-party applications, although the applications are not save or migrate forwar uring migration. If you plan to use the same EMSN as storage for other noe migrations, you must consier the aitional isk space neee. Space on the EMSN that was use for prior system migrations can be recovere. Ientify a system (computer name) in the EMSN file structure that has complete migration an elete all folers an ata locate uner the system name to free up space on the EMSN for future migrations. Noe Type Release 3xx.x Table 8: Experion Migration Storage Noe estimate space Total space (T) Base size (B) Options (O) (Eg, CAB) Process Server 8 GB + Options 8.7 SCADA Server, eserver 8.7 GB + Options 8.7 Process Flex Station, Console Extension Station 9.6 GB 3 GB 12.6 Collaboration Station 9.6 GB NA 9.6 SCADA Flex Station, Console Extension Station 9.6 GB + Options 12.6 Console Station 11 GB 3 GB 14 ACE, SCE 5 GB 1 GB 6 Formula: Total Space - (Base size + Options) = Estimate EMSN space Options inclue CAB software, Thir Party software an applications installe on the noe, so on. Estimate EMSN Space neee T - (B +O) = EMSN 133

134 7 R510.X MIGRATION REFERENCE 7.8 Multi-cluster migration scenarios Migration of systems that contain multiple clusters requires aitional planning an consierations with regar to preserving an upating the Enterprise Moel (EM) an the Enterprise Moel Database (EMDB) R400.x, R410.x, R430.x, R431.X, R432.x an R510.x systems Attention Migration from R3xx to R500.x requires multiple hops. However, DSA interoperability between 3xx an 500.x are supporte for letting one cluster complete multiple hops to R500.x uring a migration scenario. R311.2 Server Patch243 for PAR1-J43NXT patch is manatory on R311 system to ensure interoperability. R310 Server Patch680 for PAR1-K7N7TZ patch is manatory on R310 system to ensure interoperability. R301.3 Server Patch093 for PAR1-WKEFV9 patch is manatory on R301 system to ensure interoperability. Refer to respective patch SCNs for more etails. For R400.x, R410.x, R430.x, R431.x, R432.x an R510.x systems, you can migrate the servers in any orer. For example in the following figure, if both Cluster X an Cluster Y are running R400.x, R410.x, R430.x, R431.x, R432.x an R510.x systems, either cluster can be migrate first. The following figure shows the case where the EMDB server is still running with R400.x, R410.x, R430.x, R431.x an R432.x in Cluster X while Cluster Y has been migrate to R510.x. In the case of a system with a EAS or nonreunant Experion Server (EMDB Sever), there is no restriction on what server is migrate first. If you are migrating from R400.x) to R500.1, you must ensure both EMDB an non-emdb servers are migrate to R500.1 before using Upgrae Tool

135 7 R510.X MIGRATION REFERENCE The following table presents migration scenarios for multi-cluster systems an also gives an inication of the interoperability restrictions for the EMDB. Interoperability for the EM has been enhance in R400.x, R410.x, R430.x, R431.x, R432.x an R510.xsystems. See Enterprise Moel Database (EMDB) Interoperability for more etails. 135