System 800xA. Installation, Update and Upgrade Getting Started. Power and productivity for a better world. System Version 6.0

Transcription

1 System 800xA Installation, Update and Upgrade Getting Started System Version 6.0 Power and productivity for a better world

2

3 System 800xA Installation, Update and Upgrade Getting Started System Version 6.0

4 NOTICE This document contains information about one or more ABB products and may include a description of or a reference to one or more standards that may be generally relevant to the ABB products. The presence of any such description of a standard or reference to a standard is not a representation that all of the ABB products referenced in this document support all of the features of the described or referenced standard. In order to determine the specific features supported by a particular ABB product, the reader should consult the product specifications for the particular ABB product. ABB may have one or more patents or pending patent applications protecting the intellectual property in the ABB products described in this document. The information in this document is subject to change without notice and should not be construed as a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document. Products described or referenced in this document are designed to be connected, and to communicate information and data via a secure network. It is the sole responsibility of the system/product owner to provide and continuously ensure a secure connection between the product and the system network and/or any other networks that may be connected. The system/product owners must establish and maintain appropriate measures, including, but not limited to, the installation of firewalls, application of authentication measures, encryption of data, installation of antivirus programs, and so on, to protect the system, its products and networks, against security breaches, unauthorized access, interference, intrusion, leakage, and/or theft of data or information. ABB verifies the function of released products and updates. However system/product owners are ultimately responsible to ensure that any system update (including but not limited to code changes, configuration file changes, third-party software updates or patches, hardware change out, and so on) is compatible with the security measures implemented. The system/product owners must verify that the system and associated products function as expected in the environment they are deployed. In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, nor shall ABB be liable for incidental or consequential damages arising from use of any software or hardware described in this document. This document and parts thereof must not be reproduced or copied without written permission from ABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. This product meets the requirements specified in EMC Directive 2004/108/EC and in Low Voltage Directive 2006/95/EC. TRADEMARKS Copyright by ABB. All rights reserved. Release: Document number: January PAA F

5 Table of Contents About this User Manual User Manual Conventions...9 Warning, Caution, Information, and Tip Icons...9 Terminology...11 Section 1 - Introduction System Security...13 System 800xA media for Software Distribution...14 Accessing the System 800xA software on a virtual machine...14 Mapping the System 800xA media using a network share...15 System 800xA Installation Workflow...16 Prepare...16 Setup...17 Configure...18 System 800xA Update Workflow...18 System 800xA Upgrade Workflow...19 Section 2 - System 800xA Installation Overview...21 System Functions and Node Types...21 Node Preparation Tool...22 System Configuration Console...22 Installation Process...23 Preparing the node...25 Creating a system...27 Selecting System Functions PAA F 5

6 Table of Contents Adding Nodes to the System...28 Allocating Functions to Nodes...29 Making Nodes Redundant...30 Deploying the System...31 Installing the.net hotfix...31 Maintenance...31 Expanding the System...31 Repairing the Local Media Repository (LMR)...33 Excluding a node...33 Replacing a node...34 Removing Nodes from the System...35 Renaming a node...35 Section 3 - System 800xA Update Section 4 - System 800xA Upgrade Appendix A - Prerequisites Windows Operating System...41 Selecting the Windows Operating System...41 Considerations for Disks and File System...42 Windows Installation Guidelines...44 Windows Operating System Updates...45 Configuring Network Adapters...45 Configuring Domain Controller and DNS Server...48 Adding Nodes to a Domain...54 Configuring Users and Groups...55 New Organizational Unit...59 Groups...59 Users, Groups, and Rights Assignments xA Service User...64 User Account for Installation...66 Other Users PAA F

7 Table of Contents Adding 800xA Domain Users to the Local Administrator Group...67 Operating System Setup Use with 800xA System...68 Regional and Language Options...69 Enable Write Caching on Hard Disks...70 Internet Explorer Enhanced Security...71 Internet Security Settings for Digital Signature Validation...71 Disable Web Browser Popup Blocker...72 Disable Show Window Contents While Dragging...72 Energy Saver and Screen Saver Configuration...72 Virus Scanning Configuration During Installation and Post Installation...73 Windows Update Configuration...73 Enable the Change Sharing Options for Different Network Profiles...73 Disable Server Manager Startup...74 Hot fix for redundancy with IPSec enabled...74 Set Date and Time for Batch Servers...74 Disable ISATAP Setting...75 Group Policy Management...75 Adding Privileges to the 800xA Service User...79 Remote (Thin) Client for the Server Operating System...79 Other Third Party Software...80 Microsoft Office Professional...80 Microsoft Word...81 Microsoft Excel...82 Crystal Reports...83 Autocad Integration...84 McAfee Integration...84 Symantec...85 Bulk SPL Template...85 Process Engineering Tool Integration Specific Requirements...86 Backup Software...86 Appendix B - Installation and Configuration Parameters Acquiring Installation and Configuration Parameters PAA F 7

8 Table of Contents Appendix C - Related Documentation Revision History Index 8 2PAA F

9 About this User Manual User Manual Conventions About this User Manual Any security measures described in this user manual, for example, for user access, password security, network security, firewalls, virus protection, and so on, represent possible steps that a user of an 800xA System may want to consider based on a risk assessment for a particular application and installation. This risk assessment, as well as the proper implementation, configuration, installation, operation, administration, and maintenance of all relevant security related equipment, software, and procedures, are the responsibility of the user of the 800xA System. This user manual is intended to guide a user to install, update or upgrade System 800xA.The main purpose of this manual is to guide the user with the workflow for the different phases in installation, update and upgrade of System 800xA. Unless otherwise noted, the versions of all 800xA Base System and Functional Area software described in this user manual are the latest release of 800xA 6.0. Refer Appendix C, Related Documentation for information on site planning, engineering planning, software configuration, network design, security measures, tools, maintenance, and so on that can be found in other 800xA User Manuals. User Manual Conventions Microsoft Windows conventions as defined in the Microsoft Manual of Style are normally used for the standard presentation of material when entering text, key sequences, prompts, messages, menu items, screen elements, and so on. Warning, Caution, Information, and Tip Icons This user manual includes Warning, Caution, and Information where appropriate to point out safety related or other important information. It also includes Tip to 2PAA F 9

10 Warning, Caution, Information, and Tip Icons About this User Manual point out useful hints to the reader. The corresponding symbols should be interpreted as follows: Electrical warning icon indicates the presence of a hazard which could result in electrical shock. Warning icon indicates the presence of a hazard which could result in personal injury. Caution icon indicates important information or warning related to the concept discussed in the text. It might indicate the presence of a hazard which could result in corruption of software or damage to equipment/property. Information icon alerts the reader to pertinent facts and conditions. Tip icon indicates advice on, for example, how to design your project or how to use a certain function. Although Warning hazards are related to personal injury, and Caution hazards are associated with equipment or property damage, it should be understood that operation of damaged equipment could, under certain operational conditions, result in degraded process performance leading to personal injury or death. Therefore, fully comply with all Warning and Caution notices. 10 2PAA F

11 About this User Manual Terminology Terminology A complete and comprehensive list of terms is included in System 800xA System Guide Functional Description (3BSE038018*). The listing includes terms and definitions that apply to the 800xA System where the usage is different from commonly accepted industry standard definitions and definitions given in standard dictionaries such as Webster s Dictionary of Computer Terms. Media Term/Acronym Node Preparation Tool (NPT) System System Functions Node Functions System Installer Agent (Agent) Installation Configuration Deploy Description The source containing the complete set of 800xA installation files. A tool used to prepare a computer before it can be configured to be a node in an 800xA system. It checks system requirements and places the installation media files on a local disk. It also installs and starts the System Installer Agent on the computer. System is defined as a collection of one or more system functions. System functions define the capability of the system. Node functions determine the functions that will installed on the nodes in the System. A local service on a computer that installs and configures software from the installation file copied to the local drive by given commands. Installation of core packages copied to the local drive. A package is still not active, after installation; it requires configuration before use. Configuration of installed core products and of on demand products from the installation files copied to the local drive. A product is activated and is ready for use after configuration. A function to deploy the system or node functions to the nodes using the agent in each node. 2PAA F 11

12 Terminology About this User Manual 12 2PAA F

13 Section 1 Introduction System Security Section 1 Introduction The latest version of this manual is available in ABBSolutions Bank. Use This document reflects 800xA System and Functional Area software at the time of release. All 800xA System and Functional Area Release Notes must be read and understood before performing any installation, update and upgrade procedures. The Release Notes contain any last minute changes that have to be performed when installing or upgrading the 800xA System. All Release Notes can be found on the System 800xA Media System Version 6.0 Released Documents. The System 800xA Installation, Update and Upgrade Getting Started manual provides information and instructions about: Phases and workflows associated with the installation, update and upgrade processes for System 800xA Prerequisites for an installation Use the System 800xA 6.0 System Planning (3BSE041389*) document to help plan the requirements, both hardware and software, for the 800xA System. For information on planning for Node and System Function refer the System 800xA 6.0 System Guide Technical Data and Configuration (3BSE041434*) and System 800xA System Guide Functional Description (3BSE038018*). System Security It is very important to have a corporate security policy that is revised on a regular basis. This is the responsibility of the user of the 800xA System. Refer the System 800xA Administration and Security (3BSE037410*), System 800xA Network Configuration (3BSE034463*), and System 800xA System Planning 2PAA F 13

14 System 800xA media for Software Distribution Section 1 Introduction (3BSE041389*) documents for more information on system security, users, user groups, roles and permissions. System 800xA media for Software Distribution The 800xA media is distributed either on physical media, or via software download, depending on the use case. The physical media is a secure and tamper proof Solid State Drive (SSD). The SSD is a read-only device ensuring that the content is secure and tamper proof. A software download means receiving one or more zip-files which have to be un-packaged and stored locally as described in Readme file included in the media. Table 1. System 800xA media for software distribution What does it consist of... When can it be used... Where can I find it... SSD Full software package Installation Upgrade Physical, can be ordered. Update Software download Update software package Update ABB SolutionsBank Accessing the System 800xA software on a virtual machine System 800xA software can be mapped into multiple Virtual Machines on a single server. Perform the following settings to access the System 800xA software on a virtual machine: 1. Connect the Solid State Drive to the virtual machine host. 2. Open Settings on the virtual machine. 3. Add... the SCSI device. 4. Select CD/DVD SMI or CD/DVD Generic in the Connection tab of the SCSI device. 5. Click Next and then Finish to complete the mapping. 14 2PAA F

15 Section 1 Introduction Mapping the System 800xA media using a network share Mapping the System 800xA media using a network share When a new installation is carried out using the Update media, the user is prompted with the location of the media used for System 800xA 6.0.The user should not browse to the mapped drives on the local node. Instead, the user should browse to the remote node where the media share is available and copy the complete path of the shared folder. To map the media on the network share: 1. Share the location of the media on the remote node. 2. Copy and paste the complete path of the shared folder, for example \\machinename\sharedfolder, in the Node Preparation Tool (NPT). Update media is available in ABB SolutionsBank. 2PAA F 15

16 System 800xA Installation Workflow Section 1 Introduction System 800xA Installation Workflow The System 800xA installation is carried out in three phases as shown in Figure 1 : Figure 1. System 800xA Installation Workflow Prepare The main purpose of this phase is to configure a node to be a 800xA node. Use the System 800xA 6.0 System Guide Technical Data and Configuration (3BSE041434*), and System 800xA 6.0 System Planning (3BSE041389*) documents to plan the hardware and software requirements for an 800xA Node. A node must comply with the hardware and Operating System requirements to be configured as an 800xA node. The following tasks are carried out in the prepare phase: 1. Selecting, and installing the Windows Operating System 2. Configuring Network Adapters 3. Configuring Domain Controller and DNS Server 4. Configuring Users and Groups 5. Operating System Setup Use with 800xA System 6. Setting up the Other Third Party Software 16 2PAA F

17 Section 1 Introduction Setup 7. Preparing the node using the Node Preparation Tool (NPT) These procedures remain the same for any node selected to be configured as a 800xA node. Please see the Industrial IT Certification home page for a complete and up to date list of certified computers: Note that the certification itself is performed towards one or more specific versions of System 800xA. Setup This phase ensures that the nodes prepared to be 800xA nodes are configured with the correct Node Functions in System 800xA. Select from the list of System Functions applicable to the system and the Node Functions intended to run on the individual nodes to setup the system. Deploying the System installs the required 800xA software on all the nodes in a centralized approach where the overall progress is indicated on Aspect Server. The system configuration information including system functions, nodes and associated node functions, node function properties and so on are stored in the Aspect Directory. This enables and ensures smooth updates and upgrades of the installed system. Do not install System 800xA software product manually. This will cause inconsistencies in the information stored in the aspect directory which will lead to unforeseen consequences in future maintenance of the system. The following tasks are carried out in the setup phase: Creating a system Selecting System Functions Adding Nodes to the System Allocating Functions to Nodes Making Nodes Redundant 2PAA F 17

18 Configure Section 1 Introduction Configure Most of the post installation configuration of the system and node functions is done before the system is deployed. However, there are post installation configuration steps that are not automated. Refer the System 800xA 6.0 Post Installation (2PAA111693*) manual along with the product specific configuration manuals to carry out the configurations. Refer the Product Specific configuration manual for specific configurations related to specific functions and features.this phase deals with configuring the 800xA Base System and Functional Areas. The system is now ready for application engineering. System 800xA Update Workflow System 800xA updates are released either with new features or problem corrections or both. The Update function in the System configuration console shall be used to update an already installed system. The three phase for a System 800xA Update are as shown in Figure 2 Figure 2. System 800xA Update Workflow To update the System 800xA: 1. Prepare the nodes on the system to install the updates by running the Node Preparation Tool (NPT). 2. Distribute the update media using either the: a. Centralized distribution method b. Manual distribution method 18 2PAA F

19 Section 1 Introduction System 800xA Upgrade Workflow 3. Load and deploy the update using the System Configuration Console (SCC). System 800xA Upgrade Workflow An upgrade to System 800xA 6.0 can be executed by using the System Installer function in System 800xA 6.0. Figure 3 shows the Overview of the Upgrade. Figure 3. Upgrading System 800xA - Overview To upgrade to System 800xA 6.0: 1. Plan the system upgrade taking into consideration the: PC Hardware Compatibility Third party software requirements Decide if the upgrade is to be done Online or Offline Ensure time synchronization for all the nodes on the system Plan to migrate the Visual Basic Process Graphics (VBPG) to Process Graphics (PG2) 2. Prepare the system being upgraded to include: Migrate all VBPG to PG2 Carry out product wise pre-upgrade procedures Identify the Node and System Functions Complete the 800xA Maintenance backup 2PAA F 19

20 System 800xA Upgrade Workflow Section 1 Introduction Move the files to a safe location 3. Prepare and deploy the software based on the upgrade strategy (Online/Offline) selected. 4. Configure the system and node functions based on product- wise post-upgrade procedures Please refer the Considerations and Upgrade Flow included in the System 800xA 5.1 to 6.0. Upgrade (2PAA111694*) and System 800xA 5.0 SP2 to 6.0 Upgrade (2PAA111695*) manuals for more information. 20 2PAA F

21 Section 2 System 800xA Installation Overview Section 2 System 800xA Installation Before proceeding with this chapter, make sure that all prerequisites required to configure an 800xA System are completed, refer Appendix A, Prerequisites. Overview System 800xA installation includes the following: System planning Centralized and automated software installation and configuration System deployment The System 800xA 6.0 is installed with minimal user interaction. It automates the installation and configuration (adding of Nodes, adding of System Functions and allocating functions to nodes) of an existing 800xA System. The configuration of all nodes in the system can be done from one place, except for the preparation of nodes which is done at each node. System Functions and Node Types System Functions define the capability of the System. Functions allocated to the nodes describe the intended functional behavior and use of a node. The selection of the System Functions determines the functions available for allocation and deploy of the nodes. The Node Types determine the main use of an 800xA system node as a: Server Client Combined client and server node System 800xA supports optional redundant server configurations to increase the uptime and eliminate loss of data. The switchover functionality is one of the key 2PAA F 21

22 Node Preparation Tool Section 2 System 800xA Installation features of redundancy and parallel servers. If the service with which a client application is communicating fails, or if the whole server node where the service is running fails, the client node will connect to a redundant service on the redundant server node. For more on node redundancy refer System 800xA 6.0 System Guide Technical Data and Configuration (3BSE041434*). Node Preparation Tool The Node Preparation Tool (NPT) copies the installation files to the local drive on the computer and installs the 800xA Base Software. Thus preparing the node for deployment of an 800xA System. System Configuration Console The System Configuration Console (SCC) helps the user create and deploy a System or expand an existing System 800xA 6.0 by using the following tasks: Create a System task: creates a System on the Primary Aspect Server node and making the node ready for a System deploy. Configure System task: helps with the configuration and installation of the system functions and the functions allocated to the nodes by: Allocating the functions to the System and the nodes and clicking Apply to save the configuration Deploying individual or all nodes in a system via the Deploy or the Deploy System button respectively Expanding an existing System Excluding a node Replacing a node Adding and/or removing a node Importing and exporting of configurations. This saves information about nodes, configured functions and so on to a text file that can be used for configuring other systems Updating the system 22 2PAA F

23 Section 2 System 800xA Installation Installation Process Viewing the task logs and collecting diagnostics data from all system nodes using the View task log and Diagnostics buttons respectively The Configure System task creates and configures aspects and objects in the system. Modifying these aspects and objects manually is not allowed and might cause inconsistencies in the system. Launch the SCC as the 800xA Installing User from the: ABB Start Menu >ABB IndustrialIT > System. Installation Process The process to be followed for installation of System 800xA is: 1. Preparing the node on page Creating a system on page Selecting System Functions on page Adding Nodes to the System on page 28 2PAA F 23

24 Installation Process Section 2 System 800xA Installation 5. Allocating Functions to Nodes on page Making Nodes Redundant on page Deploying the System on page PAA F

25 Section 2 System 800xA Installation Preparing the node Preparing the node Prerequisites to launch the NPT tool The node is prepared and configured as per the information provided in Appendix A, Prerequisites. To prepare the node with NPT: Launch the preparation tool by starting the 'Setup.exe' from the root level of the installation media. Click on the Install Adobe Reader in NPT to install the Adobe PDF reader. 2PAA F 25

26 Preparing the node Section 2 System 800xA Installation Figure 4. Node Preparation Tool (NPT) Follow the instructions provided in the tool to complete the node preparation process. The system reboots when the 800xA Base System installation is complete. Wait until all the core products are installed before proceeding with any additional installations. 26 2PAA F

27 Section 2 System 800xA Installation Creating a system Creating a system The purpose of creating a system is to create a framework where functions can be allocated to the System and the nodes. It allows to plan, deploy and configure a system. A system is created using the System Configuration Console (SCC) on the Primary Aspect Server. Refer the System 800xA System Guide Functional Description (3BSE038018*) to understand the node and/or system functions to be combined in a system. To know more about the licensing information associated with the System refer the System 800xA 6.0 Licensing Information (2PAA111691*). Selecting System Functions Select the System functions that will be a part of the System using the Configure System task in the SCC as shown in Figure 5. These System Functions will determine the functionality in the system, the functions allocated to the nodes and available for the configuration. System Functions cannot be removed once they are deployed. 2PAA F 27

28 Adding Nodes to the System Section 2 System 800xA Installation Figure 5. Selecting the System Functions Adding Nodes to the System Adding a node to the system makes it possible to allocate functions to the node and deploy. Use System nodes tab of the Configure System task in the SCC to add a 28 2PAA F

29 Section 2 System 800xA Installation Allocating Functions to Nodes node and allocate the functions to the node. To deploy a node ensure that the status of the node is shown as Connected in the System nodes tab. Allocating Functions to Nodes Before deploying nodes to a System they should be allocated with the required functions that define the role they play in a System. Figure 6. Allocating functions to the node To allocate functions to nodes: Select the node in the System nodes tab and click Allocate functions to select and allocate the node functions. Provide any additional node level information needed 2PAA F 29

30 Making Nodes Redundant Section 2 System 800xA Installation for the specific function and click Apply to save the system configuration as shown in Figure 6. A function allocated to a node cannot be removed once the node is deployed. Refer the System 800xA 6.0 System Guide Technical Data and Configuration (3BSE041434*) to know and plan the number of nodes and the functions that can be deployed. Making Nodes Redundant To make a node redundant, first select the node to be made redundant. Then use the Make Redundant function and select the functions that should be made redundant. If new functions are allocated to any of the nodes that have been made redundant. Ensure that the new functions are made redundant as well, to achieve complete node redundancy. Figure 7. Making a node redundant 30 2PAA F

31 Section 2 System 800xA Installation Deploying the System Deploying the System Deploying a System involves deploying of allocated System functions and functions to nodes which makes the System ready for Engineering and Configuration. Refer System 800xA 6.0 Post Installation (2PAA111693*) to carry out any further configuration of the system. During deploy to minimize the licensing related warnings the Central Licensing System function should be deployed first, followed by loading of the available 800xA license files. The node where the SCC is run might be rebooted during deployment. Ensure to login again with the same user credentials and accept the UAC prompt to continue the deployment. If the UAC prompt is not acknowledged on time the pop up will disappear and SCC will not be launched. In such cases, launch the SCC from the ABB Start menu to continue the deploy. Installing the.net hotfix Maintenance The Configure System task supports exclusion of nodes at the time of deploy. The workplace process will leak one handle each time a Graphic Display is closed in the Operator Workplace. This handle leak is caused due a Microsoft process and can be resolved by installing the Microsoft.NET hotfix. To install the.net4.5.2 hotfix: 1. Go to 3rd_Party_SW\Microsoft\Hotfix for.net Framework in the 800xA Media. 2. Double click _intl_x64_zip.exe file and extract to a shared location. 3. Run the NDP452-KB x86-x64-AllOSENU.exe on all nodes to install the hotfix. Expanding the System Expansion of a System is supported both at the node level and the System Function Level. This means an expansion based on System Size and/or functions. 2PAA F 31

32 Expanding the System Section 2 System 800xA Installation f Expansion based on Nodes can be done using the System nodes tab of the Configure System task. To expand a system by adding new nodes: 1. Prepare and configure the node according to the instructions in Appendix A, Prerequisites. 1. Launch the preparation tool by starting the 'Setup.exe' from the root level of the installation media. 2. Go to Configure System > System nodes and click Add node Enter the node name and select the node type. 4. Go to System functions tab, click Edit functions and add the required system functions. 5. In the System nodes tab, click Allocate functions to select and allocate the application and service functions to the node. 6. Click Apply to save the configuration or go to Node actions... and click Deploy. Deploying the system might cause the nodes to be rebooted based on the functions selected. Expansion based on the 800xA products can be done by allocating new functions to the System and the nodes. To expand the nodes by adding new system functions to the existing nodes: 1. Go to System functions tab, click Edit functions and add the required system functions. 2. In the System nodes tab, click Allocate functions to select and allocate the application and service functions to the node. 3. Click Apply to save the configuration or go to Node actions... and click Deploy. Deploying the system might cause the nodes to be rebooted based on the functions selected. Ensure that there are no reserved entities in a system before deploying the system with new System functions. Use the Find Tool to identify the reserved entities and release them. Refer System 800xA Operations 6.0 Operator Workplace Configuration (3BSE030322*) manual for more information. 32 2PAA F

33 Section 2 System 800xA Installation Repairing the Local Media Repository (LMR) Repairing the Local Media Repository (LMR) System 800xA allows the user to repair the LMR to include other installation types by: 1. Navigate to...\tools\system Installer\Node Preparation Tool and open the command prompt. 2. Enter the command " ABB Node Preparation Tool.exe /Repair" in the prompt and press Enter 3. Select any new options for extending the node or just start the node preparation for repairing the LMR without modifying the installation types. While repairing the LMR all the previously selected options will be deselected in the NPT. Ensure to reselect any previously selected options and/or select the new options. 4. The content applicable for the selected Installation Type option will be copied to LMR. Excluding a node It might be needed to exclude a node or nodes from being deployed either because: it is disconnected from the system is in an error state the user does not want to deploy on a particular node. It is possible to exclude the erroneous node and continue the system deploy process. A node can be excluded only if it is not already deployed. It is highly recommended to include all the nodes for a system to be fully deployed. Excluding a node before deploy To exclude a node before initiating the deploy phase: 1. Go to the Node functions tab in the SCC. 2PAA F 33

34 Replacing a node Section 2 System 800xA Installation 2. Select the node to be excluded and click on Exclusions... in the Node actions... button. 3. Follow the screen prompts to complete the node exclusion. Once the excluded node is available, it can be deployed at a later stage by the user. Replacing a node Excluding a node during deploy A node might have to be excluded during the deploy phase if the node has failed. To exclude a node during the deploy phase: 1. Abort the deploy. 2. Go to the Node functions tab in the SCC. 3. Select the node to be excluded and click on Exclusions... in the Node actions... button. 4. Follow the screen prompts to complete the node exclusion Once the erroneous node has been excluded and the deploy process is complete on the other nodes in the system. Follow the procedure as documented in the section Replacing a node to make an excluded node operable again. A node can be replaced by using the Replace node button. It can be used to redeploy nodes that for example: have become corrupt have hardware issues. Replacing a node will reset the node's installation status but it will retain its configuration (the configured Node Functions and their property values). Once the replace node process has been initiated, the node status will change to Needs Redeploy. When a node is replaced, the replacement node needs to have the same computer name and network configuration. To replace a node: 34 2PAA F

35 Section 2 System 800xA Installation Removing Nodes from the System 1. Restore the faulty node to a clean Windows installation. Prepare it according to the instructions in Appendix A, Prerequisites. 2. Ensure that it has the same computer name and network configuration as earlier. 3. Run the Node Preparation Tool on it. 4. Go to the node where the deploy was initiated and from the System nodes tab of the Configure System task, and click on Replace node command on the node. Once completed, the node's status will be 'Needs Redeploy' 5. Click the Deploy command to install the configuration on the node once again. 6. The node will have the same configuration installed as previously. Removing Nodes from the System A node may be removed when reducing the system footprint. Use the Remove node function from the System nodes tab of the Configure System task to remove a node and deploy for the change to take effect. Removing the node from the system causes all the configuration data on the node to be removed as well. Once removed the node can no longer connect to the system. To reconnect the node to the system the node must be prepared, added and the functions allocated to the node. Renaming a node A node maybe renamed when restoring a backup from a development or an engineering system into a production system or due to some other reason. To rename the node and reconnect it to the system: the node must be prepared, added and the functions allocated to the node. 2PAA F 35

36 Renaming a node Section 2 System 800xA Installation 36 2PAA F

37 Section 3 System 800xA Update Section 3 System 800xA Update Updates can be executed using the System Installer as described in the System 800xA 6.0 Update Manual (2PAA114580*). 2PAA F 37

38 Section 3 System 800xA Update 38 2PAA F

39 Section 4 System 800xA Upgrade Section 4 System 800xA Upgrade Upgrades can be executed using the System Installer as described in following upgrade manuals. Choose the user manual that applies to the system being upgraded. System 800xA 5.1 to 6.0 Upgrade (2PAA111694*) System 800xA 5.0 SP2 to 6.0 Upgrade (2PAA111695*) System 800xA 4.1 to 5.0 SP2 Upgrade (2PAA113553*) System 800xA 3.1 SP2 to 5.0 SP2 Upgrade (2PAA113440*) A direct upgrade from System Version 3.1 Service Pack 3 to System Version 6.0 is not supported. The System Version 3.1 Service Pack 3 800xA System must be upgraded to 800xA 5.0 SP2 and then to 800xA 6.0. A direct upgrade from System Version 4.1 to System Version 6.0 is not supported. The System Version xA System must be upgraded to 800xA 5.0 SP2 and then to 800xA 6.0. VB based Process Graphics are not supported in System 800xA 6.0. The VB editor is not supported and VBPG graphics can no longer be edited in 800xA 6.0. It is mandatory to migrate all VB process graphics to PG2 graphics before upgrading to System 800xA 6.0. The upgrade instruction contains procedures for upgrade preparation and post upgrade. Upgrading most Base System and Functional Area software requires referring back to the installation instruction Creating a system to install that software. This does not include information on site planning, engineering planning, software configuration, network design, security measures, tools, maintenance, and so on that can be found in other 800xA User Manuals. 2PAA F 39

40 Section 4 System 800xA Upgrade 40 2PAA F

41 Appendix A Prerequisites Windows Operating System Appendix A Prerequisites The user performing the procedures in this section must be proficient in the use of Windows Operating Systems. This section may not include detailed procedures on how to perform the described settings. There may be differences in accessing the Microsoft Operating System settings described in this section depending on the selected operating system. It is the responsibility of the user to consult Microsoft documentation and online help to accurately make the settings. Use the System 800xA 6.0 System Planning (3BSE041389*) document to help plan the requirements, both hardware and software, for the 800xA System. This section lists the prerequisites required to configure a node for an 800xA System. It is recommended to make a full backup of all disks. With such a backup all work will be saved in the event of a disk crash or other serious malfunction. Make sure to place proper identification on the backup media or backup files. Install optional hardware drivers if not supplied by the Windows Operating System (video card, network adapter, sound card, etc.). Windows Operating System This section describes: Selecting the Windows Operating System. Considerations for Disks and File System. Windows Installation Guidelines. Windows Operating System Updates. Selecting the Windows Operating System System 800xA 6.0 version runs only on 64-bit (x64) operating systems. 2PAA F 41

42 Considerations for Disks and File System Appendix A Prerequisites The supported operating systems, service packs, and hot fixes are listed in System 800xA 6.0, 5.1, 5.0, 4.x, 3.1 Third Party Software (3BUA000500). For security updates refer System 800xA - Third Party Security Updates Validation Status (3BSE041902). These documents can be found in ABB SolutionsBank. The US English version of the operating system is required even if a translation NLS package for System 800xA is used. The following conditions affect the decision on which operating system to use: Server roles can be allocated to nodes running either a workstation or server operating system of Windows. Using workstation operating system helps in keeping the cost down for smaller installations. Refer to the System 800xA 6.0 System Guide Technical Data and Configuration (3BSE041434*) for rules that apply in selecting the type of Operating System. There are limitations on number of nodes used in the system when using the Workstation Operating System for Server nodes. These limitations depend on Microsoft licensing rules for the Workstation Operating System. Refer to System 800xA System Guide Technical Data and Configuration (3BSE041434*) for the details on the limitations. The Windows Operating System may be purchased from any Microsoft reseller. The nodes with pre-installed operating system shall be checked and configured as per the system 800xA specifications. Considerations for Disks and File System There are several factors that may have an impact on 800xA System performance, for example: where the software is installed, the tendency toward fragmentation. The following are some recommendations regarding these factors: Multiple Disks and Partitions Some types of 800xA servers can use significant disk I/O. Creating partitions that are hosted by different disks or disk arrays can improve performance for these servers. Aspect Servers, Connectivity Servers, Information Management Servers and Batch Servers can benefit from additional partitions when configuration data is distributed over multiple partitions that are hosted by separate disks or disk arrays. 42 2PAA F

43 Appendix A Prerequisites Considerations for Disks and File System At least two of these partitions are recommended for Information Management Servers. See the System 800xA System Guide Technical Data and Configuration (3BSE041434*) for specific details for Information Management and other server types. Installation Directory It is generally recommended to use the Windows default location, the program files directory on the boot disk, for installation. A faster disk subsystem will improve performance. Defragmenting Disks The file system must be in a consistent state at all times. Size disks so they will be 25 percent empty for defragmentation purposes. Defragment disks on a regular basis using the defragmentation software provided with the operating system. Check the system for fragmented files and defragment them as required: On all nodes where trend and history logs reside. History Server disks and disks on the Connectivity Servers where trend or history logs reside as History configuration impacts not only the History Server disks. Extensive use of the Bulk Configuration tool may cause associated disks to become fragmented. Configuration procedures that involve creating, deleting, and then recreating of a large quantity of objects may cause associated disks to become fragmented. Deleting and then creating the Aspect System may cause associated disks to become fragmented. 2PAA F 43

44 Windows Installation Guidelines Appendix A Prerequisites Windows Installation Guidelines Make a fresh installation of the Windows Operating System. Before adding applicable service packs, it is important that all the latest device drivers are installed to match the hardware. This is especially important for elite server hardware with special RAID hard drives and server specific hardware that requires the latest drivers or drivers not included in the operating system media. Follow the installation procedure as described in the documentation provided by Microsoft. Table 2 indicates the settings specifically required for the 800xA System installation. Table 2. Windows Installation Requirements Step Choosing a partition for installing the operating system. Selecting Regional Settings Time Zone Description It is recommended that all server nodes (Aspect Directory, Connectivity Servers, Applications Servers, etc.) use at least one additional partition for the operateitdata and operateittemp folders. For best performance, the additional partition should be on a separate disk or disk array from the operating system. There may be additional disk requirements for Applications Servers. If installing the Information Management Server function on this node, at least one additional NTFS partition is needed for storing historical data. This partition can be the same as the operateitdata and operateittemp partition or be a separate partition. The amount of disks, disk space, and disk I/O needed for the Information Management node are dependent on the final configuration for the node. To maximize the performance for any server, any additional partitions should be a separate disk or disk array from the root partition. Refer to Regional and Language Options on page 69. Make sure the Automatically adjust clock for daylight saving changes check box is enabled (if daylight saving time is used). 44 2PAA F

45 Appendix A Prerequisites Windows Operating System Updates Windows Operating System Updates Install Windows hot fixes, and Security Updates approved by ABB (refer to Third Party Software System 800xA (3BUA000500) and System 800xA Third Party Security Validation Status (3BSE041902) after installing other third party software. ABB System 800xA Qualified Security Updates (9ARD183777*) can be used to install the latest qualified security updates. The tool and the document are accessible from ABB SolutionBank. The Windows Operating System Updates (Service Packs, Feature Packs) must be installed immediately after installing the operating system, and before performing any other procedures in this instruction. Configuring Network Adapters If the Network Adapter supports Receive Side Scaling this feature must be disabled. Refer to the Network Adapter documentation for information on how to disable the feature. Network adapters must be installed and configured to support communication on the client/server network. This is required on the Domain Server node, and all 800xA System nodes. Typically one network adapter will be provided with the server or workstation hardware. It may be necessary to install a second network adapter for redundancy. All network adapters may be installed and configured at the same time during system installation; however, the network will not run with redundancy until Redundant Network Routing Protocol (RNRP) is installed (refer to Product Installation section for a separate Domain Server node). If the network adapters are not plug-and-play devices, the installation must be done manually. If the Windows installation does not include the drivers for the network adapters the driver software must be installed before the network adapters can be configured. The 800xA System relies on TCP/IP as its transport protocol. It is strongly recommended that TCP/IP is the only protocol in use. If other protocols need to be installed, make sure that TCP/IP is configured as the primary protocol. 2PAA F 45

46 Configuring Network Adapters Appendix A Prerequisites Refer to Windows Help > Networking for more information on how to install and configure TCP/IP network adapters. Refer to System 800xA Network Configuration (3BSE034463*) for configuration of DNS. The following procedure applies to the Workstation Operating System nodes. The procedure for the Server Operating System nodes may vary from the one shown here. To configure the network adapters: 1. Open Windows Control Panel. 2. Double-click Network and Sharing Center to open the Network and Sharing Center. 3. Click Change Adapter Settings. 4. Right-click on the network adapter and select Properties from the context menu to open the Connection Properties dialog box. 5. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties to open the Internet Protocol (TCP/IP) Properties dialog box. 6. Select Use the following IP address. 7. Enter the IP address in the IP address and the subnet mask in the Subnet fields according to the planning done in Installation and Configuration Parameter Worksheet. 8. Enter the IP address of the default gateway in the Default gateway field (if required by topology). 9. Enter the IP address of the Primary Domain Server in the Preferred DNS server field. 10. Enter the IP address of the Secondary Domain Server in the Alternate DNS server field. Always specify the Domain Servers with their primary client/server network addresses. This is true for all network adapters, including the ones for secondary client/server networks. 46 2PAA F

47 Appendix A Prerequisites Configuring Network Adapters 11. Repeat for all network adapters in the servers and workstations. Use the same DNS settings for all network adapters. 12. For all interfaces on separate Control Networks three configuration changes (compared to the default settings) must be done to reduce the amount of traffic on the Control Network. a. Disable IPv6 by clearing the check box Internet Protocol Version 6 (TCP/IPv6). b. Click Properties in the Internet Protocol (TCP/IP) Properties dialog to open the Advanced TCP/IP settings dialog. c. Click the DNS tab. d. Clear the check box Register this connection's addresses in DNS. e. Click the WINS tab. f. Select Disable NetBIOS over TCP/IP. 13. Click OK as necessary to save the newly configured values, and then click Close to close the Connection Properties dialog box. 14. Connect the Ethernet cables. Match each of the icons with its corresponding Ethernet connector on the server or workstation. 15. Use ping -a from a Windows command prompt to verify the server or workstation has contact with the Domain Controller: C:\>ping -a Pinging MM-DC1 [ ] with 32 bytes of data: Reply from : bytes=32 time<1ms TTL=128 Reply from : bytes=32 time<1ms TTL=128 Reply from : bytes=32 time<1ms TTL=128 Reply from : bytes=32 time<1ms TTL=128 Ping statistics for : Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: 2PAA F 47

48 Configuring Domain Controller and DNS Server Appendix A Prerequisites Minimum = 0ms, Maximum = 0ms, Average = 0ms The connection may not work through more than one network adapter before RNRP is installed. Verify the port speed and duplex configuration on both ends (Network Adapter and network switch). Refer to System 800xA Network Configuration (3BSE034463*). 16. Verify the primary Client Server network is bound first for RNRP configurations. From the Change Adapter Settings: a. Use the Alt key to expose the Advanced Settings menu. b. Select Advanced Settings. c. Verify the Primary Client Server Network is bound first and the Redundant Client Server Network is second. d. Make corrections as needed. 17. Disable all unused NIC cards. The primary NIC card can only have one TCP/IP address. If the card consists more than one TCP/IP address, RNRP will not function correctly. Configuring Domain Controller and DNS Server If the Domain Controller uses any network interface in addition to the ones for the client/server network, the DNS Server need to be configured to only listen to DNS requests on the client/server network. Perform the following for all Domain Controllers. Open the Interfaces tab under Properties for the DNS Server. Make sure that only the IP addresses for the client/server network are selected. The below 800xA software must be installed on the standalone domain controllers manually browsing the media for: 48 2PAA F