NEC ExpressCluster X R3 LAN & WAN with Oracle Installation ...partner.lenel.com/.../7.2/userguides/NECExpressCluster_Oracle.pdf · Oracle 11g R2 ... LAN & WAN with Oracle Installation

7.2

NEC ExpressCluster X R3 LAN & WAN with Oracle Installation Guide

Lenel® OnGuard® 7.2 NEC ExpressCluster X R3 LAN & WAN with Oracle Installation GuideThis guide is item number DOC-904, revision 6.009, December 2015.© 2015 United Technologies Corporation. All rights reserved.

Lenel® and OnGuard® (Registered trademarks of UTC Fire & Security Americas Corporation, Inc.) Lenel is a part of UTC Building & Industrial Systems, a unit of United Technologies Corporation.

All trademarks are the property of their respective owners.

Information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of UTC Fire & Security Americas Corporation, Inc.

Non-English versions of Lenel documents are offered as a service to our global audiences. We have attempted to provide an accurate translation of the text, but the official text is the English text, and any differences in the translation are not binding and have no legal effect.

The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that agreement.

Crystal Reports for Windows is a trademark of Crystal Computer Services, Inc.

OnGuard includes ImageStream® Graphic Filters. © 2002 eBT International, Inc. (f/k/a Inso Corporation). All rights reserved. ImageStream Graphic Filters and ImageStream are registered trademarks of eBT International, Inc. (f/k/a Inso Corporation).

Integral and FlashPoint are trademarks of Integral Technologies, Inc.

Portions of this product were created using LEADTOOLS ©1991-2011, LEAD Technologies, Inc. ALL RIGHTS RESERVED. Portions of this product are licensed under US patent 5,327,254 and foreign counterparts.

Active Directory, Microsoft, SQL Server, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

NEC, ExpressCluster and ExpressCluster X are registered trademarks or trademarks of NEC Corporation in the United States and other countries.

Oracle is a registered trademark of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Other product names mentioned may be trademarks or registered trademarks of their respective companies and are hereby acknowledged.

Table of Contents

CHAPTER 1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Conventions Used in this Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Other Referenced User Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Network Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Initial LAN Setup Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Oracle 12c R1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Oracle 11g R2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

WAN Deployment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Starting Cluster Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Starting the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Firewall Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

CHAPTER 2 Pre-Installation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Disk Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Network Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

CHAPTER 3 Configure Windows Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Miscellaneous Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Running the Lenel Utility for ExpressCluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Running the Utility at Different Points of the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

NEC ExpressCluster X R3 LAN & WAN with Oracle Installation Guide 3

Table of Contents

CHAPTER 4 Cluster Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Cluster Manager Setup (Install the JRE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Install ExpressCluster X R3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Configure the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

CHAPTER 5 Install Oracle Server Software on an NEC Server . . . . . . . . . . . . . . 83

Reconfigure the Oracle Database Listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

CHAPTER 6 Install Oracle Client Software on an NEC Server . . . . . . . . . . . . . . 87

CHAPTER 7 Create Lenel Live Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

CHAPTER 8 Install OnGuard on an NEC Server . . . . . . . . . . . . . . . . . . . . . . . . . 91

Installing OnGuard on an NEC Server Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Install the OnGuard Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Set Services to Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Manually Issue an SSL Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

CHAPTER 9 Script Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Stop the Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Stop the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Add a Script Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

CHAPTER 10 Configure the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Configure Host Header Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

CHAPTER 11 WAN Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

CHAPTER 12 Upgrade OnGuard on NEC Systems . . . . . . . . . . . . . . . . . . . . . . . 113

Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

4 NEC ExpressCluster X R3 LAN & WAN with Oracle Installation Guide

Table of Contents

APPENDIX A Ping Resource Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

APPENDIX B WAN Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Implications and Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126Requirement 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Requirement 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Requirement 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Requirement 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Requirement 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131


Table of Contents

6 NEC ExpressCluster X R3 LAN & WAN with Oracle Installation Guide

CHAPTER 1 Prerequisites

Conventions Used in this Documentation

• Where a term is defined, the word is represented in italics.

• Field names and file names are shown in bold.

• Menus and menu choices are shown in bold italics.

• Keyboard keys are represented in angle brackets. For example: <Tab>, <Ctrl>.

• Keyboard key combinations are written in two ways:

– <Ctrl> + <Z> means hold down the first key, then press the second

– <Alt>, <C> means press the first key, then press the second

• Window buttons on the screen are represented in square brackets. For example: [OK], [Cancel].

Other Referenced User Guides

In addition to this user guide, the following guides provide instructions for installing OnGuard, and Oracle 12c and Oracle 11g Server and Client software. These guides are included on the OnGuard installation disc:

Installation Guide. A comprehensive guide that includes instructions for installing the OnGuard software. This guide also includes information on the browser-based client applications.

Advanced Installation Guide. A guide that encompasses a variety of advanced topics including Oracle installation and configuration.

Visitor Administration User Guide. When installing or upgrading OnGuard, if you install the Application Server to use browser-based applications, refer to this document to Update the URL. For more information, refer to Configure the Application Server on page 107.

Visitor Management Host User Guide. When installing or upgrading OnGuard, if you install the Application Server to use browser-based applications, refer to this document to Update the URL. For more information, refer to Configure the Application Server on page 107.


Prerequisites

8

This installation guide walks you through the installation and configuration of your NEC ExpressCluster X R3 system with Oracle 12 c and 11g as well as the installation and configuration of the OnGuard software. In addition to this user guide, the following user guides are provided on the NEC ExpressCluster X R3 installation disc:

ExpressCluster X R3 for Windows Getting Started Guide. This guide is intended for all users. The guide covers topics such as product overview, system requirements, and known problems.

ExpressCluster X R3 WAN Edition for Windows Installation and Configuration Guide. This guide is intended for system engineers and administrators who want to build, operate, and maintain a cluster system. Instructions for designing, installing, and configuring a cluster system with ExpressCluster are covered in this guide.

ExpressCluster X R3 for Windows Reference Guide. This guide is intended for system administrators. The guide covers topics such as how to operate ExpressCluster, function of each module, maintenance-related information, and troubleshooting. The guide is supplement to the Installation and Configuration Guide.

The vocabulary used:

Clean installA completely new installation of an operating system or application on a computer. In a clean install of an operating system, the hard disk is formatted and completely erased. In a clean install of an application, the older version is uninstalled first. Installing an operating system on a new computer, or installing an application for the first time, is automatically a clean install.

ClientRefers to the computer or computers that connect to the server.

ClusterA logical collection of servers that have clustering software installed. Clustered servers share a virtual identity.

Cluster partitionA small (non-user) partition used by ExpressCluster to store metadata that keeps track of the mirror disk status.

Data partitionDisk partition used to store regular user/application data.

Database systemRefers to the database program that you are using. This document assumes that you are using Oracle as your database system.

Disk resourceA shared disk volume used to resolve Network Partition situations.

ExpressCluster BuilderThe software component used to build, configure, and modify NEC clusters.

ExpressCluster ManagerThe software component that is used to monitor and manipulate the cluster.



FailoverThe planned or unplanned movement of a cluster group from one server to another. A failover can occur if a failure threshold has been exceeded (unplanned).

Floating IP addressThe most common type of shared IP address for a cluster group. Floating IP addresses can only be on the same subnet as the cluster servers, as opposed to Virtual IP Addresses.

GroupA logical collection of shared resources between clustered servers. Group resources often include Virtual Computer Name, Mirror disk, Floating/Virtual IP Address, etc.

Group resourceAny item in a cluster group (Virtual Computer Name, Mirror/Switch Disk, Floating/Virtual IP Address, etc.).

GUIDRefers to Globally Unique Identifier. A unique 128-bit number produced by the Windows operating system or by some Windows applications to identify a particular component, application, file, database entry, or user. GUIDs can be created in a number of ways, but usually they are a combination of a few unique settings based on a specific point in time (e.g. an IP address, network MAC address, and clock date/time.).

Hardware KeyCommonly referred to as a “dongle.” It is used on the servers as part of the license. Alternatively, you may have a software license. For more information, refer to Software license on page 11.

HeartbeatA periodic transmission sent between clustered servers. The heartbeat signal is used to inform partner servers of system status.

High AvailabilityHigh-availability clusters (also known as HA clusters or failover clusters) are computer clusters that are implemented primarily for the purpose of providing high availability of the services which the cluster provides. They operate by having redundant computers or nodes which are then used to provide service when system components fail. Normally, if a server with a particular application crashes, the application will be unavailable until someone fixes the crashed server. HA clustering remedies this situation by detecting hardware and software faults, and immediately restarting the application on another system without requiring administrative intervention, a process known as failover. As part of this process, clustering software may configure the node before starting the application on it. For example, appropriate file systems may need to be imported and mounted, network hardware may have to be configured, and some supporting applications may need to be running as well.

HA clusters are often used for critical databases, file sharing on a network, business applications, and customer services such as electronic commerce Web sites. HA cluster implementations are intended to build redundancy into a cluster to eliminate single points of failure.

HA clusters send heartbeat traffic across the Public and Private network subnets so that the servers can maintain awareness of each other. A serious condition every clustering software system must be able to handle is “split-brain.” Split-brain occurs when the servers lose connectivity to each other on both the Public and Private network subnets. If this happens,


Prerequisites

10

each node in the cluster may mistakenly decide that every other node has gone down and attempt to start services that the other nodes are still running. Having duplicate instances of services may cause data corruption on the shared storage.

Interconnect networkAlso referred to as the “Private” network in this document. A dedicated network segment used for heartbeat signal communication and sometimes disk mirroring. Both the Private and Public network interfaces serve as “interconnects” because ExpressCluster X uses both for heartbeat communication.

Java Policy fileA file stored in the user's home directory that specifies Java security settings. This file is usually named “.java.policy” (the leading dot is intentional). Proper configuration of this file is necessary in order to access the ExpressCluster Builder.

LANRefers to Local Area Network. A logical network that does not contain segments separated by routers. LANs typically span small regions.

Management IP addressAn IP address is used to access the browser-based ExpressCluster Manager. This IP address is necessary in order to access the cluster when there are no Floating/Virtual IP addresses online.

MetadataData written to the Cluster Partition of mirrored/switch disks - used by ExpressCluster to maintain these resources.

Mirror diskA group resource that consists of two logical disk partitions on two separate servers. These logical disks will only be accessible from one server at a time.

NodeA member server of a cluster. Also refers to any addressable endpoint on a network (server, router, etc.).

OnGuard servicesOnGuard services include all those services with names beginning with “LS”, “Lps”, and “Lnr.”

Ping resourceA method of resolving the Network Partition (known as “split brain”). This method makes a determination of whether or not to shutdown a server based on if it can communicate with a pre-defined reliable remote network node (router, etc.).

Primary ServerThe server that a cluster group starts up on, by default.

Secondary ServerThe non-active server in the cluster - the server that does not currently have control of the group. Alternative terms for the Secondary Server include Standby Server and Backup Server.



ServersThe computers that run NEC ExpressCluster server services and OnGuard server services. Typically, these computers also host the database system however it is possible to utilize a separate database server that is not part of the clustered server environment.

Service ReleaseService release refers in general to updates made to OnGuard in the forms of service packs or hot fixes.

A service pack is a cumulative package with guided installation that resolves customer issues. A service pack may also include support for a technology refresh and new features.

A hot fix is a cumulative package with guided installation that resolves critical customer issues. A hot fix may contain more than one fix.

Software licenseOnGuard offers a software license that works without the need for a hardware dongle. With a software-based license you are able to use License Administration to activate, return, or repair your license.

Software licenses can only be used on a physical computer or in a VMware ESX virtual environment. In a VMware ESX virtual environment, only the License Server is supported. The License Server must be used with a software-based license and not with a dongle-based license.

Start.batAn ExpressCluster script that is run when a group starts. The Start.bat file contains instructions for starting up applications and services controlled by ExpressCluster.

Stop.batAn ExpressCluster script that is run when a group stops. The Stop.bat file contains instructions for stopping applications and services controlled by ExpressCluster.

URIRefers to Uniform Resource Identifier; a generic term for all types of names and addresses that refer to objects on the World Wide Web. A Uniform Resource Locator (URL) is one type of URI.

Virtual Computer NameA group resource that defines a computer name that is assigned to the server that is currently running the group. Applications and users should access this name rather than the actual server name.

Virtual IP AddressA type of shared IP address for a cluster group. Virtual IP addresses can be on a different subnet than the cluster servers, as opposed to Floating IP Addresses.

WANRefers to Wide Area Network. A logical network that contains segments separated by routers. WANs typically span large geographical regions.

WorkstationAny computer where OnGuard software is installed.


Prerequisites

12

Introduction

NEC offers integrated high availability and disaster recovery software solutions that provide continuous data mirroring and fast application recovery to maintain the continuity of critical systems against hardware, software, and site failures.

NEC ExpressCluster X R3 LAN with OnGuard supports Standard and Enterprise editions of common server applications and operating systems including but not limited to:

• Database Server:

– Oracle 11g R2 32-bit and 64-bit

– Oracle 12c R1 Server 64-bit (12.1.0.1) (with 32-bit Client installed if OnGuard is running on the same server as the database)

• Web Server: Microsoft Internet Information Services

• Operating System: Windows Server 2012 R2 64-bit

Note: For the latest patch sets and service packs supported, refer to the Third Party Compatibility Chart on the Lenel web site for current NEC ExpressCluster support.

In addition, NEC provides flexible data protection including full data protection across geographic locations through its real-time synchronous data mirroring technology.

From a single integrated management console administrators can easily view and monitor current application and data availability status and events, configure appropriate cluster policies, and manually activate/deactivate clustered server resources across geographic locations.

Network Requirements

This guide describes the required installation and configuration to build a disaster tolerant computing solution for OnGuard in a clustered environment. The installation and configuration procedures consist of two (2) major stages: the initial setup in a LAN environment, and the final (optional) deployment in a WAN environment.

For more information about LAN network requirements, refer to Chapter 3: Verifying Deployment Environment Requirements in the ExpressCluster X R3 for Windows Installation and Configuration Guide.

Note: For WAN network requirements, this document describes using the same subnet. If you use a different subnet, please contact PES. For more information, refer to Appendix B: WAN Network Requirements on page 125.


Network Configuration Checklist

Network Configuration Checklist

In order to set up ExpressCluster X R3 in a LAN or WAN environment, the network IP address and cluster information should be determined before completing any other steps. The following checklist is provided for you to note the information required for setup:

• Cluster Name:

• Cluster Partition:

• Data Partition (Mirror Disk):

• Lenel Database User Password:

• Primary Server Hostname:

• Primary Public IP Address:

• Primary Public Subnet Mask:

• Primary Public Default Gateway:

• Primary Private IP Address:

• Primary Private Subnet Mask:

• Secondary Server Hostname:

• Secondary Public IP Address:

• Secondary Public Subnet Mask:

• Secondary Public Default Gateway:

• Secondary Private IP Address:

• Secondary Private Subnet Mask:

• Floating IP Address (Cluster Floating IP Address):

• Management IP Address (Management Floating IP Address):


Prerequisites

14

• Mirror Drive Database Path:

• Virtual Computer Name (Virtual Hostname):

• SID Service Name (Refers to the Oracle System Identifier used to identify the database.):

• Failover Group:

• Management Group (By default, the name automatically assigned to Management Group is “ManagementGroup.”):

Initial LAN Setup Overview

Notes: Professional Engineering Services (PES) are required for NEC ExpressCluster X R3 LAN and WAN systems.

For WAN deployment, this document describes using the same subnet. If you use a different subnet, please contact PES. For more information, refer to Appendix B: WAN Network Requirements on page 125.

For Oracle 11g R2: Complete the steps in Oracle 11g R2 on page 16.

Oracle 12c R1

Complete the steps in this section.

The first stage is performed with all of the hardware components at a single site where as the WAN connection is replaced with a temporary, direct LAN connection.

The major steps in the first stage include the following:

1. Plan the system network. For more information, refer to Network Configuration Checklist on page 13.

2. (Optional) On both the <Primary Server Hostname> and <Secondary Server Hostname>, if the Windows Firewall will be enabled on any Oracle client or server, take the necessary steps to avoid firewall issues. Perform the instructions for Step 5: Prevent Firewall Issues in “Oracle 12c Release 1 Server Software Installation and Configuration” in the Advanced Installation Topic guide.

3. On the <Primary Server Hostname>, complete steps 4 - 8.

4. Configure the required disk operating system settings (including the mirrored disk set) for NEC ExpressCluster X R3. Complete the steps in Disk Setup on page 19.

5. Configure the required network settings for NEC ExpressCluster X R3. Complete the steps in Network Setup on page 26.

6. Configure Windows settings using the Lenel Utility for ExpressCluster. Follow the instructions designated for this point in the process (after network setup). For more information, refer to After Network Setup on page 38.

7. Install the JRE. For more information, refer to Cluster Manager Setup (Install the JRE) on page 41.

8. Install ExpressCluster Server. For more information, refer to Install ExpressCluster X R3 on page 43.

9. On the <Secondary Server Hostname>, repeat steps 4 - 8.

10. On the <Primary Server Hostname>, configure the cluster. For more information, refer to Configure the Cluster on page 54.



11. On the <Primary Server Hostname>, complete steps 12 - 22.

12. Run the Lenel Utility for ExpressCluster again. Follow the instructions designated for this point in the process (after cluster setup). For more information, refer to After Cluster Setup on page 39.

13. Using the Cluster Manager, move the <Failover Group> back to the <Primary Server Hostname>.

14. Install the Oracle Server software. For more information, refer to Install Oracle Server Software on an NEC Server on page 83.

15. Reconfigure the Oracle Database Listener. For more information, refer to Reconfigure the Oracle Database Listener on page 84.

16. Create the Lenel database. For more information, refer to Create Lenel Live Database on page 89.

17. Install the Oracle Client software. For more information, refer to Install Oracle Client Software on an NEC Server on page 87.

18. Perform the instructions for Step 3: Add Local Net Services Name(s) in “Oracle 12c Release 1 Client Installation and Configuration” in the Advanced Installation Topics guide.

Note: Use <Virtual Computer Name> for the Live database Host Name.

19. Perform the instructions for Step 9: Prepare the User Scripts in “Oracle 12c Release 1 Server Software Installation and Configuration” in the Advanced Installation Topics guide.

When you prepare the user scripts for an Oracle ExpressCluster configuration, Lenel strongly recommends the following actions:

• Restrict the Lenel user.

• Configure a Windows Authenticated user for application.config.

Note: The Windows Authenticated user you specify in this file is the one Setup Assistant will use later (after OnGuard is installed) to connect to the Oracle database.

20. Perform the instructions for Step 10: Create the Live Database Oracle Users in “Oracle 12c Release 1 Server Software Installation and Configuration” in the Advanced Installation Topics guide.

Notes: When you Create the Lenel User, log on to SQLPlus using the SYSTEM account and the <SID Service Name> as the Service. You must be logged in as SYSTEM to run the scripts.

21. Install the latest approved patch sets. The list of approved patch sets can be found on the Lenel Web site at: https://partner.lenel.com/downloads/onguard/compatibility-charts.

Note: When accessing the Downloads section at https://partner.lenel.com, make sure to select the version of OnGuard that is currently installed.

22. Stop the Oracle services on the <Primary Server Hostname>.

23. On the <Secondary Server Hostname>, failover to the <Secondary Server Hostname>, and then repeat steps 14 - 22 after moving the application folder from <Mirror Drive Database Path>\<SID Service Name> to <Mirror Drive Database Path>\<SID Service Name>\backup.

24. Complete the steps to Set Services to Manual on the <Secondary Server Hostname>, and then create the scripts to handle starting or stopping the system. For more information, refer to Set Services to Manual on page 92 and Script Setup on page 95.

25. Install the OnGuard software. For more information, refer to Install OnGuard on an NEC Server on page 91.


https://partner.lenel.com/downloads/onguard/compatibility-charts

https://partner.lenel.com

Prerequisites

16

26. Run the Lenel Utility for ExpressCluster again. Follow the instructions designated for this point in the process (after OnGuard setup). For more information, refer to After OnGuard Setup on page 39.

27. If you plan to run the browser-based applications, configure the Application Server. For more information, refer to Configure the Application Server on page 107.

Oracle 11g R2

The first stage is performed with all of the hardware components at a single site where as the WAN connection is replaced with a temporary, direct LAN connection.

The major steps in the first stage include the following:

1. Plan the system network. For more information, refer to Network Configuration Checklist on page 13.

2. On the <Primary Server Hostname>, complete steps 4- 8.

3. Configure the required disk operating system settings (including the mirrored disk set) for NEC ExpressCluster X R3. Complete the steps in Disk Setup on page 19.

4. Configure the required network settings for NEC ExpressCluster X R3. Complete the steps in Network Setup on page 26.

5. Configure the Windows settings using the Lenel Utility for ExpressCluster. Follow the instructions designated for this point in the process. For more information, refer to After Network Setup on page 38.

6. Configure the required firewall exceptions. For more information, refer to Firewall Settings on page 18.

7. Install the JRE. For more information, refer to Cluster Manager Setup (Install the JRE) on page 41.

8. Install ExpressCluster Server. For more information, refer to Install ExpressCluster X R3 on page 43.

9. On the <Secondary Server Hostname>, repeat steps 4- 8.

10. On the <Primary Server Hostname>, configure the cluster. For more information, refer to Configure the Cluster on page 54.

11. On the <Primary Server Hostname>, complete steps 12- 20.

12. Run the Lenel Utility for ExpressCluster again. Follow the instructions designated for this point in the process. For more information, refer to After Cluster Setup on page 39.

13. Using the Cluster Manager, move the <Failover Group> back to the current server.

14. Install the Oracle Server software. For more information, refer to Install Oracle Server Software on an NEC Server on page 83.

15. Install the Oracle Client software. For more information, refer to Install Oracle Client Software on an NEC Server on page 87.

16. Install the latest approved patch sets. The list of approved patch sets can be found on the Lenel Web site at: https://partner.lenel.com/downloads/onguard/compatibility-charts.

Notes: If you are installing Oracle Client as part of the Oracle Server installation, make sure you apply the latest approved patch sets to both.

When accessing the Downloads section at https://partner.lenel.com, make sure to select the version of OnGuard that is currently installed.


https://partner.lenel.com/downloads/onguard/compatibility-charts

https://partner.lenel.com


17. Perform the instructions for Step 3 Create the Lenel Database in “Oracle 11g Server Software Installation and Configuration” in the Advanced Installation Topics guide. Use the <SID Service Name> instead of “LENEL” for the Global Database Name.

IMPORTANT: Do NOT accept the default location for the database file. Instead, change the Database Files location to the <Mirror Drive Database path>.

18. Perform the instructions for Step 2 Run the Net Configuration Assistant in “Oracle 11g Server Software Installation and Configuration” in the Advanced Installation Topics guide.

Note: When you Run the Net Configuration Assistant and Verify the System is Working, replace “LENEL” with the <SID Service Name>. Also use the <Virtual Computer Name> for Host name.

19. Reconfigure the Oracle Database Listener on page 84. Perform the instructions for Step 2 Add Local Net Services Name in “Oracle 11g Client Installation and Configuration” in Advanced Installation Topics.

20. Stop the Oracle services on the <Primary Server Hostname>.

21. On the <Secondary Server Hostname>, failover to the <Secondary Server Hostname> and repeat steps 12 - 20 after moving the files found at <Mirror Drive Database Path>\<SID Service Name> to <Mirror Drive Database Path>\<SID Service Name>\backup.

22. On the <Secondary Server Hostname>, perform the instructions for Step 5 Create the Lenel User in “Oracle 11g Server Software Installation and Configuration” in Advanced Installation Topics.

Note: When you Create the Lenel User, log onto SQLPlus using the SYSTEM account and the <SID Service Name> as the Service. You must be logged in as SYSTEM to run the script.

23. On the <Secondary Server Hostname>, complete steps 24 - 28.

Notes: After rebooting the servers or failing them over, from this point on, until the scripts are setup, you must restart the Oracle listener service, and then restart the Oracle database service, to restore connectivity.

In order to reboot a server, you must be in Operation Mode. Right-click on one of the servers, and then select Reboot.

24. Install the OnGuard software. For more information, refer to Install OnGuard on an NEC Server on page 91.

25. Configure Authentication. Complete the steps in Database Authentication for Web Applications in the Installation Guide.

26. Run the Lenel Utility for ExpressCluster one more time. Follow the instructions designated for this point in the process. For more information, refer to After OnGuard Setup on page 39.

27. Complete the steps to Configure the OnGuard Logs Folder in the Installation Guide.

28. Complete the steps to Install Your OnGuard License in the Installation Guide.

29. Repeat steps 24 - 28 on the <Primary Server Hostname> after you Set Services to Manual on page 92 on the <Secondary Server Hostname>.

30. On the <Primary Server Hostname>, Run Database Setup.

31. Complete the steps in Set Services to Manual on page 92 on the <Primary Server Hostname>, and then create the scripts to handle starting or stopping the system. For more information, refer to Script Setup on page 95.


Prerequisites

18

WAN Deployment Overview


For WAN deployment, this document describes using the same subnet. If you use a different subnet, please contact PES.

For WAN customers, only: The second stage (WAN deployment) is performed last to deploy a previously built cluster to two geographically dispersed locations. For more information, refer to WAN Deployment on page 111 and WAN Network Requirements on page 125.

Starting Cluster Manager

Where the document specifies starting Cluster Manager, you need to determine if the cluster is stopped or started. If the cluster is stopped, you must use one of the following URLs to start Cluster Manager:

• The only time the cluster should ever be stopped (as far as this document is concerned) is during the initial configuration. In this case, start Cluster Manager using http://localhost:29003. In addition, use localhost to start Cluster Manager when the cluster is already stopped.

• After the cluster is configured, and subsequently started, you should always start Cluster Manager using http://<Management IP Address>:29003.

Starting the Cluster

IMPORTANT: If prompted, do NOT restart your computer. Instead, reboot the cluster using Cluster Manager. Right-click on the <Cluster Name> in the left pane, then select Reboot. If necessary, start the cluster before rebooting it.

Firewall Settings

ExpressCluster X R3 uses several port numbers. If your Windows firewall is on, you will need to configure your firewall to enable access to the ExpressCluster X R3 port numbers. A list of the port numbers used by default in ExpressCluster X R3 is provided in the ExpressCluster X R3 for Windows Getting Started Guide. Refer to section Before installing ExpressCluster > Communication port number.

Note: You will need Adobe Reader to view the PDF guides. It can be installed from the Supplemental Materials Disc - Prerequisite Software section.


CHAPTER 2 Pre-Installation Setup

Disk Setup

The following procedure must be performed to set up the cluster partition and the data partition (mirror disk).

Instructions are provided for a Windows Server 2012 R2 64-bit system.

On the Primary Server, complete the following steps:

1. Start the Windows Computer Management Utility using one of the following methods.

• Press the Windows key + <R>, type diskmgmt.msc in the Run dialog, and then click [OK].

• Press the Windows key + <X> to bring up the advanced context menu, and then select Disk Management.

• On Windows Server 2012 R2 systems, hover the mouse over the lower left corner of the Desktop to activate the Start screen icon. Right-click on the icon to bring up the advanced context menu, and then select Disk Management.


Pre-Installation Setup

20

2. There will be two disks displayed in the Disk Management tool. The second disk should contain no partitions. Right-click on the second disk, and then select New Simple Volume.

3. The New Simple Volume Wizard is opened. Click [Next].

4. A default volume/partition size is automatically set up; this is, by default, the remaining unallocated space on the disk. The size of the mirror disk can be set to any size based on the


Disk Setup

overall disk size and user preference, but the size of the mirror disk MUST match on both the Primary and Secondary Servers.

Specify a volume size of 50 MB, and then click [Next].

5. Assign a drive letter to the drive. We will use “X.” It is not recommended to assign drive “Y” because it will be used for the data partition. (This is also the drive assignment we use on a non-clustered system). Click [Next].



22

6. Format the partition:

a. Select Format this partition with the following settings.

b. Format this partition as “NTFS.”

c. We used “Cluster” as the Volume label.

d. Deselect the Perform a quick format check box, if selected.

e. Click [Next].

7. Click [Finish].


Disk Setup

8. After clicking [Finish] you will be returned to the Disk Management tool. The cluster partition of 50 MB is now present. Click on the remaining unallocated space, and then create another New Simple Volume. This will be the data (mirror) partition.

9. Click [Next].

10. A default partition size is automatically set up; this is, by default, the remaining unallocated space on the disk. The size of the mirror disk can be set to any size based on the overall disk size



24

and user preference, but the size of the mirror disk MUST match on both the Primary and Secondary Servers. Click [Next].

11. Assign a drive letter. Click [Next]. We used “Y.”

Note: If you use a drive letter other than “Y”, then you may need to modify the start.bat script if utilizing the ShareDrive example for a shared folder on the mirror drive for archiving or other purposes.


Disk Setup

12. From the Format Partition window:

a. Select the Format this partition with the following settings radio button with the following settings:

• File System: “NTFS”

• Allocation unit size: “Default”

• Volume label: “Data” (This can be set to anything the user wants.)

• Deselect the Perform a quick format check box, if selected.

b. Click [Next].

13. Click [Finish].



26

Formatted Cluster and Data Partitions

14. Repeat steps 1 - 13 on the Secondary Server.

IMPORTANT: You must assign the same drive letters on the Secondary Server as were assigned on the Primary Server.

Network Setup

On the Primary Server:

1. Open Network Connections.

For Windows Server 2012 R2, press the Windows key + <R>, type ncpa.cpl in the Run dialog, and then click [OK].

2. Depending on your server configuration, you may see different connections. To set up a cluster, there must be a minimum of two (2) connections. One connection is referred to as Public the other connection is referred to as Private.


Network Setup

3. Rename the connections to be used to “Public” and “Private.”

4. The Public connection must be configured with a static IP address:

a. Right-click on the Public connection, and then select Properties. The Public Properties window is displayed.

b. Select your Internet Protocol Version (TCP/IP), and then click [Properties].



28

c. For this configuration, the IP information is configured as follows:

• IP address: <Primary Public IP Address>

• Subnet mask: <Primary Public Subnet Mask>

• Default gateway: <Primary Public Default Gateway>

• Preferred DNS server: For the Public connection, enter the IP address for the preferred DNS server. For example, 10.112.10.1. Although not necessary, it is also recommended that you enter an IP address for the Alternate DNS server as well.

Note: These settings may be different based on your network configuration.

d. Click [OK] when finished.

5. The Private connection must be configured with a static IP address set:

a. Right-click on the Private connection, and then select Properties. The Private Properties window is displayed.


Network Setup

b. Deselect all connections except for Internet Protocol Version (TCP/IP), and then click [Properties].

c. For this configuration, set the IP information as follows:

• IP address: <Primary Private IP Address>

• Subnet mask: <Primary Private Subnet Mask>

Note: These settings may be different based on your network configuration.

d. Click [OK] when finished.

6. In the Network Connections window, from the Advanced menu, select Advanced Settings. Alternatively, press <Alt> to access the Advanced menu.



30

7. Examine the list to ensure that “Public” is at the top of the list and “Private” follows it directly. Re-order the connections if necessary.

8. With Windows Server 2012 R2, non-domain-based, network connections, there is a Location type option for Public or Private. This should not be confused with the names used in this document for the network connections “Public” and “Private” (interconnect). The Location type for the interconnect network must be set to “Private.” With WAN configurations, the Private network is typically a domain type, and therefore cannot be modified.

a. For Windows Server 2012 R2, open the Start screen, and then click the Administrative Tools icon. In the Administration Tools folder, double-click Local Security Policy.

b. Select Network List Manager Policies, and then double-click the Unidentified Networks policy in the right panel.

c. Ensure the Location type is Private, and then click [OK].

9. If the Private network is set to the Private Location type AND Inbound connections that do not match a rule are blocked by default, then set an Inbound Rule to allow connections from the Remote IP addresses within the Local Subnet. This applies to both servers in the cluster.

10. Repeat steps 1- 9 on the Secondary Server.

IMPORTANT: The network connections must have a different IP address set or else the cluster will not work. Use the Secondary Public IP Address and the Secondary Private IP Address, and so on. For more information, refer to Network Configuration Checklist on page 13.


CHAPTER 3 Configure Windows Settings

• WARNING! • Modifying the registry may cause irreversible damage to your Windows operating system; make sure to back up the registry before making any changes. Follow the instructions located at: http://support.microsoft.com/kb/322756.

Run the Lenel Utility for Express Cluster to automatically configure the Windows settings. The Lenel Utility for ExpressCluster.exe file is available on the Supplemental Materials disc. For more information, refer to Running the Lenel Utility for ExpressCluster on page 35.

Prerequisite: You must install .NET Framework 3.5 (includes .NET 2.0 and 3.0) before running the Lenel Utility for Express Cluster.

In order for the utility to execute specific registry or file modifications (actions), the application must have knowledge of key pieces of information. This is why some actions are disabled until you use the application to detect the required information from the system. For more information, refer to Dependencies: Information Required to Enable an Action on page 32.

Miscellaneous Information

• If you have multiple versions of the Java Runtime installed, you will be prompted to select the appropriate one.

• If you have detected the Java Runtime Version, and you instruct the application to modify the Java Policy, you will be prompted to specify which Java Policy File to modify (either the one for your current Windows login, or the global policy for the Java Runtime Version specified).

• The application will prompt you for the network adapter in your system which is the Private NIC. This is the one where you would modify the TcpAckFrequency.

• Private NIC GUID refers to the Interconnect. GUID is the same connection setup as the Interconnect. When using the utility, <Primary Private IP Address> and <Secondary Private IP Address> are the values that allow you to determine which of the GUIDs are presented when the Private NIC GUID is detected by matching the IP address listed in the Multiple Resources window


http://support.microsoft.com/kb/322756

http://support.microsoft.com/kb/322756

Configure Windows Settings

32

.

Dependencies: Information Required to Enable an Action

Type Action Dependencies

Registry LSA BackConnectionHostName Virtual Computer Name

Registry LSA DisableLoopbackCheck No dependencies.

Registry LanMan DisableStrictNameChecking No dependencies.

Registry TcpAckFrequency Private network adapter GUID

Registry Login Driver Locations • ODBC name

• Floating IP Address

Registry Vinca • Virtual Computer Name


ACS.INI file File License Server Virtual Computer Name

application.config file

Database Connection • WARNING! •

Do NOT execute this action. Installations with Oracle database do not support this action.


App Server URI Virtual Computer Name


License Client Host Virtual Computer Name

java.policy file Policy for ExpressCluster Builder With only the Management Port Number detected, entries can be made to the policy files for “localhost.” However, if the Management IP Address is also detected, an additional entry will be made to the policy files for it as well. This is the recommended course of action.

If you have the Java Runtime Version detected, you can either modify the user's java.policy file or the global java.policy file.

Browser Favorite file

Shortcut to ExpressCluster Manager Management Port and Management IP Address



Registry Modifications

Action What is modified

Disable Loopback Check

• Type: DWORD

• Location: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa

• Value Name: DisableLoopbackCheck

• Value: 1

Back Connection Host Names

• Type: MULTI-STRING

• Location: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\MSV1_0

• Value Name: BackConnectionHostNames

• Value: [Virtual Computer Name] (Plus any pre-existing previous values)

Disable Strict Name Checking

• Type: DWORD

• Location: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters

• Value Name: DisableStrictNameChecking

• Value: 1

TCP Acknowledgement Frequency

• Type: DWORD

• Location: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TcpIP\Parameters\Interfaces\[Private NIC GUID]

• Value Name: TcpAckFrequency

• Value: 1

Vinca Setting (used by Linkage Server)

• Type: String

• Location: HKEY_LOCAL_MACHINE\Software\Vinca\CoStandby\ClusterItems\CLU_IPADDRS\[Floating IP Address]

• Value Name: NtsCluGroupRef

• Value: [Virtual Computer Name]

Note: This modification applies a registry fix to the Primary Server or Secondary Server in the cluster allowing the OnGuard services such as LS Linkage Server, LS Communications Server, LS Global Output Server, and LS Replicator Service to start under the <Virtual Computer Name>. If this is not applied to both servers in the cluster, the services will not be able to start on the virtual computer.

Login Driver Location 1

• Type: String

• Location: HKEY_CURRENT_USER\Software\Lenel

• Value Name: LoginDrvLoc_[ODBC name]

• Value: [Floating IP Address]



34


• Type: String

• Location (64-bit): HKEY_LOCAL_MACHINE\Software\Wow6432Node\Lenel

• Location (32-bit): HKEY_LOCAL_MACHINE\Software\Lenel




• Type: String

• Location: HKEY_USERS\.DEFAULT\Software\Lenel



File Modifications


License Server • File: %WinDir%\ACS.INI

• Section: [LicenseServerHost]

• Value Name: Host


Note: It may not be necessary to execute this action because the ACS.INI file should be properly created when you install OnGuard and specify the[Virtual Computer Name] for the License Server.

Database Connection • WARNING! • Do NOT execute this action. Installations with Oracle database do not support this action unless you temporarily modify the Virtual Computer Name to the <SID Service Name>. For instructions, refer to step 6 in Running the Lenel Utility for ExpressCluster on page 35.

• File (64-bit): %AllUsersProfile%\Lnl\application.config

• File (32-bit): %AllUsersProfile%\Application Data\Lnl\application.config

• Section: [appSettings]

• Key: ConnectionString

• Value Portion: [TNS Service Name]

App Server URI • File (64-bit): %AllUsersProfile%\Lnl\application.config



• Key: ApplicationServerUri

• Value Portion: [Host Name]


Registry Modifications (Continued)




Running the Lenel Utility for ExpressCluster

1. Run the utility:

a. Insert the Supplemental Materials disc into the disc drive and navigate to the High Availability\NEC\ExpressCluster Tools folder.

b. Save the file Lenel Utility for ExpressCluster.exe to the Desktop, and then run it.

2. When the Lenel Utility for ExpressCluster window is opened, examine the available actions to determine which of these needs to be executed.

License Client Host • File (64-bit): %AllUsersProfile%\Lnl\application.config



• Key: Lnl.LicenseSystem.Client.Host


Java.Policy File: %UserProfile%\.Java.Policy or %ProgramFiles%\Java\[JRE Version]\Lib\Security\Java.Policy or %ProgramFiles(x86)%\Java\[JRE Version]\Lib\Security\Java.Policy

You can choose which file to create or modify. The settings will either effect the current Windows user, or all Java users on this system.

Examples:

• grant codeBase "http://localhost:29003/clptrek.jar" { permission java.security.AllPermission;};

• grant codeBase "http://localhost:29003/webmanager.jar" { permission java.security.AllPermission;};

• grant codeBase "http://127.0.0.1:29003/clptrek.jar" { permission java.security.AllPermission;};

• grant codeBase "http://127.0.0.1:29003/webmanager.jar" { permission java.security.AllPermission;};

• grant codeBase "http://192.168.1.1:29003/clptrek.jar" { permission java.security.AllPermission;};

• grant codeBase "http://192.168.1.1:29003/webmanager.jar" { permission java.security.AllPermission;};

ExpressCluster Manager Internet Favorite (Bookmark)

File: %UserProfile%\Favorites\ExpressCluster Manager.url

File Modifications (Continued)




36

3. Detect the key information for these actions.

a. If you Detect Private NIC, the system prompts you to select the Private Network Interface:

b. If you Detect Java Runtime Version, the system prompts you to select the Java Runtime Version in order to modify the global Java policy file:



The following example shows all options detected:

4. Execute the actions.

5. In the Config File Settings section, if you execute Java Policy File, and if you have multiple versions of the Java Runtime installed, the system will prompt you to select the appropriate Java Policy file (the user’s java.policy file or the global java.policy file):

IMPORTANT: For the Java Policy to take effect, all open instances of your browser must be closed.

6. (Optional) Rather than executing each action individually, use either or both of the following options:

a. Click [Do All Registry Changes] to execute all registry actions currently enabled.

b. Click [Do All File Changes] to execute all file updates currently enabled. The utility uses the INCORRECT setting for DB Connection (the application.config file); you need to specify the .

– Temporarily overwrite the value in Virtual Computer Name. Double-click on [Virtual Computer Name] to open the Manual Entry dialog.

– Type your <SID Service Name>, and then click [OK].

– Click on [DB Connection].

– Click [Detect Virtual Computer Name] to reset the Virtual Computer Name value for any further Windows configuration changes.

Note: Most registry modifications (except Login Driver Location Settings and Vinca Setting), require a cluster reboot to make the registry settings take effect.



38

7. Reboot the cluster. From the Cluster Manager, right-click on <Cluster Name> in the tree view, and then select Reboot. If necessary, start the cluster before rebooting it.

8. Click [OK] when prompted to confirm the reboot operation.

Running the Utility at Different Points of the Installation

The Lenel Utility for ExpressCluster is run at three different points of the installation process on both the Primary Server and Secondary Server:

• After Network Setup on page 38

• After Cluster Setup on page 39

• After OnGuard Setup on page 39

After Network Setup

1. Run the utility by completing the following steps:

a. Detect Private NIC. Select the network interface resource specified in the checklist as the Primary Private IP Address or Secondary Private IP Address based on which server you are on. For more information, refer to Network Configuration Checklist on page 13.

b. Run TcpAckFrequency Setting. Running this setting now allows the cluster initial mirror build to run much more quickly.

c. Close the utility.



After Cluster Setup

1. Run the utility by completing the following steps:

a. Detect Virtual Computer Name.

b. Detect Floating IP Address.

c. Execute the following actions:

• LSA BackConnectionHostNames Setting

• LSA DisableLoopbackCheck Setting

• LanMan DisableStrictNameChecking Setting

• Vinca Setting

d. Click [OK] to confirm each action.

Note: Executing these actions now allows you to log into SQL via the <Virtual Computer Name> using Windows Authentication. This is important for the OnGuard configuration.

e. (Optional) Detect Management Port Number, Detect Management IP Address, and Detect Java Runtime Version. Execute Java Policy File, and ExpressCluster Manager Internet Favorite.

Notes: The Java Policy File may have been manually configured by the user at this point, since minimal configuration would have been required to build the cluster.

ExpressCluster Manager Internet Favorite is not required and is included for convenience only.

f. Close the utility.

After OnGuard Setup

1. Run the utility, and then complete the following steps:

a. Detect Floating IP Address.

b. Detect ODBC.

c. Run Login Driver Location Settings.

d. Close the utility.

Note: If this is a fresh installation, and everything was done properly, modifying the ACS.INI and application.config files should not be necessary. These functions are provided primarily for upgrade scenarios and for situations where the user may not have provided the correct values for the License Server and Database Server locations when installing the OnGuard software.



40

CHAPTER 4 Cluster Setup

Cluster Manager Setup (Install the JRE)

The computers used to administrate the cluster must have the JRE (Java Runtime Environment) installed. The JRE can be installed by running the installation program found under the jre folder on the NEC ExpressCluster X R3 disc. Typically, both servers in the cluster are set up to be able to manage the cluster as well as a potential non-cluster server.

1. Run the executable file located in the jre folder.

2. If prompted to confirm, click [Run].


Cluster Setup

42

3. On the welcome window, click [View License Agreement] to read the agreement, and then click [Install] to accept the agreement and continue installing the JRE.

4. The JRE will run the install process.


Install ExpressCluster X R3

5. When the installation is complete, click [Close].


1. Starting on the Primary Server, insert the ExpressCluster X R3 installation disc into the disc drive to start the installation procedure. Click [Next].


Cluster Setup

44

2. Type the User Name and Company Name. Click [Next].

3. Select the Server check box. Click [Next].

4. If prompted, click [Yes] to confirm.



5. Click [Next].

6. Select the I accept the terms of the license agreement radio button, and then click [Next].


Cluster Setup

46

7. The default installation folder for NEC ExpressCluster is C:\Program Files\NEC\ExpressCluster X LAN. If you need to change the location of the installation folder, do so now, otherwise click [Next].

IMPORTANT: Do NOT install NEC ExpressCluster X on the cluster or mirror partition.

8. Click [Next].



9. The installation progress is displayed.

10. When installation of the Server component is completed, click [Finish].


Cluster Setup

48

11. The system must be restarted to become functional. Select the Restart System check box, and then click [Finish].

12. After the installation, open the License Manager to register the licenses.

a. Start License Manager. For more information, refer to “Locating Operating System Applications in Windows” in the OnGuard Installation Guide.

b. Click [Register] to register the EXPRESSCLUSTER X 3.1 for Windows license.



13. Click [Register with License Information] and then enter the information for the license you are registering as prompted. This information is included with your installation package.

14. Select the product of the license you are registering:

a. Select “Windows” from the OS information drop-down.

b. Select “Product version” from the Product/Trial drop-down.

c. Select “EXPRESSCLUSTER X 3.1 for Windows” in the Product information listing window, and then click [Next].


Cluster Setup

50

15. Select the license units:

a. Select the CPU Unit radio button.

b. The Number of CPU Licenses should be two (2).

c. Click [Next].

16. Enter the Serial No. and License Key information as provided on the NEC license sheets, and then click [Next].



17. The License Registration Confirmation window is displayed. Click [Next].

18. Click [OK] to confirm the license registration.

19. Click [Register] to register the Replicator license.


Cluster Setup

52

20. Click [Register with License Information], and then enter the information for the license you are registering as prompted. This information is included with your installation package.

21. Select “EXPRESSCLUSTER X Replicator 3.1” from the Product information list, and then click [Next].



22. Enter the Serial No. and License Key information as provided on the NEC license sheets, and then click [Next].

23. The License Registration Confirmation window is displayed. Click [Next].

24. Click [OK] to confirm the license registration.


Cluster Setup

54

25. Click [Finish].

26. Repeat the installation and license registration instructions on the Secondary Server.

Configure the Cluster

Note: Complete the following steps on the Primary Server, only.

1. After NEC ExpressCluster X R3 is installed, start the Cluster Manager Web application. From a Web browser, navigate to http://localhost:29003.

IMPORTANT: After the cluster is configured (and subsequently started), the cluster is accessed using http://<Management IP Address>:29003.

2. The Confirm dialog is opened. Click [Close].



3. You will be prompted to edit the Java security file. Select the code provided in the lower section of the window, and the press <Ctrl> + <C> to copy the code.

4. Navigate to C:\Program Files (x86)\Java\jre6\lib\security\java.policy.


Cluster Setup

56

5. Open the file using the WordPad text editor.

6. Paste the copied code into the java.policy file, and then save the file. Close the text editor.

7. (Optional) You can also add code to the Java security file for each of the following items:

• If the java.policy file is on the clustered server:

– - localhost by IP address (127.0.0.1)

– - localhost by name

• Primary Server Hostname

• Secondary Server Hostname

• Management IP Address (This is the most important item in addition to the localhost!)




• Virtual Computer Name

IMPORTANT: step 4 - step 6 describe how to modify the global Java policy file which affects all users that log into the server. Although this is the recommended method, it may be considered a security risk. This is why NEC ExpressCluster X instructs you to modify the user’s Java policy file. Use the method that best suits your requirements.

8. Close all open browser windows. Start your browser again, and then navigate to http://localhost:29003.

9. The Confirm dialog is opened. Click [Start cluster generation wizard]. Alternatively, you can perform this operation from the File menu by selecting Cluster Generation Wizard.

10. Start the Cluster Generation Wizard for the standard edition.


Cluster Setup

58

11. The Cluster Generation Wizard is opened. It is now time to build your cluster.

12. In the Cluster Name field, type the <Cluster Name>. In the Management IP Address field, type the <Management IP Address>. Once assigned, the cluster name cannot be changed. Click [Next].



13. The Server Definition List is automatically populated with the <Primary Server Hostname>. In this example, the hostname used for our Primary Server is “qa-nec1.”

From here, other servers are added to the cluster. Click [Add].

Note: Before performing step 14, make sure the NEC ExpressCluster firewall ports are open.

14. When the Add Server dialog is opened, type the <Secondary Server Hostname> in the Server Name or IP Address field, and then click [OK].


Cluster Setup

60

15. Configure the Interconnect for the servers in the cluster. Click [Next].

16. The <Primary Private IP Address>, <Primary Public IP Address>, <Secondary Private IP Address>, and <Secondary Public IP Address> are automatically added.

Note: <Primary Private IP Address> is the Primary Interconnect and <Primary Public IP Address> is the Secondary Interconnect. The Private IP Address is used for disk mirroring.



17. Select the mirror disk connect (MDC column) name to be allocated to the data communication route, and move “mdc1” [Up] to configure it as Priority “1”. Click [Next].

18. The NP Resolution window is opened. Click [Next].


Cluster Setup

62

19. The Management Group window is opened. Click [Add].

20. The Group Definition window is opened. Ensure that “failover” is the group Type, and then enter the failover group Name. “OnGuard” is used for our system. Click [Next].



21. In the this window, because Failover is possible on all servers is enabled, it is not necessary to select the group that can run the group or configure the priority of the servers. Click [Next].

22. The Group Attribute Settings window is opened. Click [Next].


Cluster Setup

64

23. The Group Resource window is opened. Click [Add].

24. The Group Resource Definitions window is opened. Select “floating ip resource” as the Type. Click [Next].



25. Click [Next].

26. Click [Next].


Cluster Setup

66

27. Type the <Floating IP Address> in the IP Address field. This value will be used for any programs, services, etc. that need to access the cluster. Click [Finish].

28. The floating IP address resource is set up. Click [Add] to add another resource.



29. From the Type drop-down, select “mirror disk resource” and enter the Name of this resource. Click [Next].

30. Click [Next].


Cluster Setup

68

31. Click [Next].

32. On the next window, click [<Add] with the Primary Server selected.



33. The Selection of partition window is opened. Click [Connect].

34. The connection information is displayed for the Primary Server partitions.

a. Data Partition: Select <Data Partition (Mirror Disk)> volume Y:\.

b. Cluster Partition: Select <Cluster Partition> volume X:\.

c. Click [OK].


Cluster Setup

70

35. Click [<Add] for the Secondary Server.



36. The Selection of partition window is opened. Click [Connect] for the Secondary Server.

37. The connection information is displayed for the Secondary Server partitions.

a. Data Partition: Select <Data Partition (Mirror Disk)> volume Y:\.

b. Cluster Partition: Select <Cluster Partition> volume X:\.

c. Click [OK].


Cluster Setup

72

38. The data and cluster partitions are now configured for both servers that will run the group. Click [Finish].



39. Configuration of the mirror disk resource is complete. Click [Add] to add another resource.

40. From the Type drop-down, select “virtual computer name resource” and enter the Name of this resource. Click [Next].


Cluster Setup

74

41. Click [Next].

42. Click [Next].



43. In the Virtual Computer Name field, enter the <Virtual Computer Name>, and then select the Target FIP Resource Name. Click [OK].

44. That completes configuring the virtual computer name resource. Click [Finish].


Cluster Setup

76

45. Click [Next].

46. Click [Finish].

47. If prompted, click [Yes] to enable the recovery action.



48. The cluster configuration is completed.

49. From the File menu, select Apply the Configuration File.


Cluster Setup

78

50. You will be prompted to confirm the configuration change operations. If you want to use an IP address other than the one currently being connected to, click [Select IP]. Otherwise, click [OK] to continue.

51. After the configuration is successfully applied, another prompt is displayed to confirm restarting the WebManager. Click [OK] to restart the manager service. WebManager refers to the NEC ExpressCluster X web management console. You may also know it as the “Cluster Manager.”

52. Change from the Config Mode to Operation Mode.



53. Start the cluster. From the Service menu, select Start Cluster.

54. Click [OK] to confirm the operation.


Cluster Setup

80

55. The cluster is started.



56. Before moving the Failover Group, verify that the Failover Group (OnGuard) can be moved between the two servers by completing the following steps:

a. Make sure the mirror disk is synchronized. Expand the Failover Group, and then right-click on the “md” resource, and then select Details.

b. The Mirror Disk Help(md) dialog is opened. The status text “Mirror disk is in the normal status now” is displayed when the mirror disk is synchronized.

c. Click [Close].

57. Move the Failover Group.

a. Right-click on the Failover Group, and then select Move.

b. When the Select Server (Move Group) dialog opens, select the Secondary Server, and then click [OK].


Cluster Setup

82

Failed Over to the Secondary Server

• WARNING! • After verifying the failover group can be moved successfully to the Secondary Server, be sure to failover over to the Primary Server before continuing.


CHAPTER 5 Install Oracle Server Software on an NEC Server

To install the Oracle Server software, complete the steps required for your version of the server software and operation system.

• For Oracle 12c Release 1, perform the instructions for the following steps in “Installing and Configuring Oracle 12c Release 1 Server Software” in the Advanced Installation Topics guide.

– Step 1: Pre-Installation Planning

– Step 2: Install Oracle Database 12c Server Software

IMPORTANT: Be sure to log into Windows as a local Administrator, and then install the Oracle Database Management System (DBMS) on both the primary and secondary server via the Use Windows Built-in Account option when you select the Oracle Home User.

Note: When the Specify Installation Location window opens, either leave the fields at their default values, or modify the field values as required.


Install Oracle Server Software on an NEC Server

84

– Step 3: Configure the Live Database Home Net Configuration (This step configures the database server Listener and Naming Methods by running the Net Configuration Assistant from the database's Oracle Home.)

• For Oracle 11g, perform the following step in “Installing and Configuring Oracle 11g Release 2 Server Software” in the Advanced Installation Topics guide.

– Step 1: Install Oracle 11g Server Software

IMPORTANT: If the Oracle server sub-steps specify to install the Oracle Client, or the latest patch set, then skip those sub-steps for now as the overview in this document will indicate when you need to apply those changes. For more information, refer to Oracle 12c R1 on page 14.

Notes: If you plan to archive to an Archival database, then create the Archival database after the Live database is created. For instructions, refer to “Create the Archival Database” in the Oracle 12c Release 1 Server Software Installation and Configuration section of the Advanced Installation Topics guide.

For Oracle 11g, refer to “Determine the Database Archive Plan” in the Oracle 11g Server Software Installation and Configuration section of the Advanced Installation Topics guide.

For detailed information about the Live and Archival databases, refer to the Archives Folder chapter in the System Administration User Guide.

Reconfigure the Oracle Database Listener

Prerequisites:

• Ensure the <Failover Group> is active on the current server. If it is not, move the <Failover Group> to the current server.

• Ensure that you can ping the <Virtual Computer Name> from the current server and Test Client (Computer 3).

Complete the following steps on the active server:

1. In Windows, start the Oracle Net Manager.


Reconfigure the Oracle Database Listener

2. In Oracle Net Manager, expand the tree view on the left, and then modify the Listener Host name to the <Virtual Computer Name>. In this example: “YNEC” on the Address1 tab.

3. In Oracle Net Manager, save the configuration. From the File menu, select Save Network Configuration, and then close the application.


Install Oracle Server Software on an NEC Server

86

CHAPTER 6 Install Oracle Client Software on an NEC Server

IMPORTANT: Install the Oracle Client on both the Primary Server and the Secondary Server.

• Before installing the Oracle Client software, reboot the cluster servers.

• Make sure the Oracle services are running. First start the Listener service (OracleOraDB12Home1TNSListener), and then restart the Oracle database (OracleService<SID Service Name>).

• Complete the instructions for “Installing and Configuring Oracle 12c Release 1 Client Software” or “Configuring Oracle 11g Release 2 Client Software” in the Advanced Installation Topics guide based on the version of software you are installing.

– Oracle 12c: Perform Step 1 and Step 2, only.

– Oracle 11g: Perform Step 1, only.

• Make sure to specify a separate Oracle Client home from that of the Oracle Server although the Oracle Client should still reside on the C:/ drive.


Install Oracle Client Software on an NEC Server

88

CHAPTER 7 Create Lenel Live Database

For Oracle 12c: Perform the instructions for Step 4: Create the Live Database in “Oracle 12c Release 1 Server Software Installation and Configuration” in the Advanced Installation Topic guide.

IMPORTANT: On the Storage Locations step, change the Database Files location to the <Mirror Drive Database Path>.

• Select Use Common Location for All Database Files as the Storage Type, and then change the default location from C:\ to the <Mirror Drive Database Path>, for example, Y:\app\oradata.


Create Lenel Live Database

90

• If you want to use Specify Fast Recovery Area option, change the path for it to a location also on your mirrored partition. For example, specify the “fast recovery area” location as Y:\app\fast_recovery_area.


CHAPTER 8 Install OnGuard on an NEC Server

Read the sections that follow, and then install and configure the OnGuard environment using the standard OnGuard installation procedure. For instructions, refer to Installing OnGuard on a Server in the OnGuard Installation Guide unless the NEC server is part of an Enterprise system, then refer to Install the OnGuard 7.2 Enterprise Software in the Enterprise Setup & Configuration User Guide.

Installing OnGuard on an NEC Server Overview

• After you install the prerequisites from the Supplemental Materials disc, use Cluster Manager to reboot the server. Make sure to make the current server the active server after any reboot.

• Before installing OnGuard, make sure you log on as the user specified in the WindowsUser_Authentication.ora file. This is the user account Setup Assistant should use.

• After OnGuard is installed, depending on the components that you chose to install, you may need to reboot the server. If you are prompted to do so, use Cluster Manager to reboot the server. Make sure to make the current server the active server after any reboot.


Install OnGuard on an NEC Server

92

Install the OnGuard Software

• In the System Location Information window:

– Do NOT accept the default location of your License Server. Instead, click [Browse] and then specify the <Virtual Computer Name>. If a mistake occurs and you accept a different location for your License Server than you meant to, then you must use the Configuration Editor to adjust this in the ACS.INI file and application.config file. For more information, refer to the Configuration Editor appendix in the OnGuard Installation Guide.

– Do NOT accept the default location for your Oracle database. Instead, specify the location of the <SID Service Name> which was established when you created the Lenel database.

Note: If you chose to custom install the Application Server, additional prompts will be displayed. Follow the on-screen instructions and provide the web address of the <Virtual Computer Name>, user name, and password.

• Do NOT reboot the computer after OnGuard is installed. This operation must be performed in Cluster Manager.

Note: After OnGuard is installed, it is helpful to have the OnGuard license file on the local computer prior to rebooting the first time. After the reboot, when you log on to Windows, Setup Assistant will run immediately and require you to specify the path to install your license file.

Set Services to Manual

After Oracle and OnGuard are installed, you need to stop their related services, and then set them to “Manual.”

Note: The names of the Oracle services are similar to the examples listed here but may not match exactly.

• OracleOraDB12Home1TNSListener

• OracleService<SID Service Name>

• OracleDBConsole<SID Service Name>

• OracleOraDb11g_home1ClrAgent


Install the OnGuard Software

• OracleOraDb11g_home1TNSListener

Note: OnGuard service names begin with “LS”, “Lps”, or “Lnr.”

Manually Issue an SSL Certificate

If this is an Enterprise configuration or OnGuard is integrated with OpenAccess, the MessageBroker.config file needs to be modified on all servers in the cluster with the <Virtual Cluster Name> in order to use the Message Broker with SSL. Otherwise, you may experience issues where replication fails or OpenAccess cannot connect with the Message Broker.

Note: This is not required if you will be using your own self-signed certificates.

1. In the command prompt, execute the following command:

lnl_app_server_certificate_installer.exe -key=DRIVE:\\PATH\\TO\\nginxConfFile\\og_cert_key.pem -cert=DRIVE:\\PATH\\TO\\nginxConfFile\\og_cert.pem -store="LS Certificate Store" -cn=<virtual computer name>

Note: The default file location of the .exe file is C:\program files (x86)\OnGuard\Certificates\ and the default location of the nginx.conf file is C:\ProgramData\Lnl\nginx\conf\.

2. Navigate to and open the MessageBroker.config file which is located by default at C:\ProgramData\Lnl\.

3. Edit the following line to use the Virtual Computer Name and uncomment the line by removing the "#" character from the beginning.

ssl-cert-name=<virtual computer name>

4. Save the file, and then restart the services.


Install OnGuard on an NEC Server

94

CHAPTER 9 Script Setup

Stop the Services

Stop the Cluster

1. Before adding the script resource, you must stop the cluster. Use localhost to access the Cluster Manager, and then right-click on <Cluster Name> in the tree view, and select Service > Stop Cluster.


Script Setup

96

2. When prompted, click [OK] to confirm stopping the cluster.


Add a Script Resource


1. Ensure the cluster is stopped.

2. Change to Config Mode.

3. Right-click on the Failover Group, and then select Add Resource.


Script Setup

98

4. Select “script resource” as the group resource Type.

5. Enter a name for the script resource. Click [Next].



6. Click [Next].

7. Click [Next].


Script Setup

100

8. From the Scripts list, select “Start script” and then click [Replace].

9. Navigate to the scripts folder and select start.bat, then click [Open]. This file is located on the Supplemental Materials disc in: High Availability\NEC\ExpressClusterScripts\.

10. If you are prompted to overwrite the file, click [Yes].

11. Verify that the Listener service name specified (by default, OracleOraDb11g_home1TNSListener) matches the actual Listener service name. (Browse to the service name by running services.msc.)

12. To enable the services to start up, complete the following steps:

a. In the Oracle Database Services section, change the SID Service Name references to the actual service name used. For example, modify OracleServiceLENEL by replacing LENEL with the <SID Service Name>.

b. Click [Edit] to modify start.bat:

c.

d. Close the text editor and make sure to save the file.



13. From the Scripts list, select “Stop script” and then click [Replace].

14. Navigate to the scripts folder and select the stop.bat file, and then click [Open]. This file is located on the Supplemental Materials disc in: High Availability\NEC\ExpressClusterScripts\.

15. If you are prompted to overwrite the file, click [Yes].

16. To enable the services to stop, complete the following steps:

a. Click [Edit] to modify stop.bat:

b.

c. Close the text editor and be sure to save the file.

17. Click [Finish].


Script Setup

102

18. From the File menu, select Apply the Configuration File.

19. Click [Yes] when prompted to confirm applying changes.



20. Click [OK].

21. Change to Operation Mode.

22. From the Service menu, select Restart Manager.

23. Click [OK] to confirm restarting the manager service.


Script Setup

104

24. After the cluster finishes refreshing, start the cluster. From the Service menu, select Start Cluster.

25. Click [OK] to confirm starting the cluster.

26. After the cluster starts, the group script should be green indicating that it is started and running correctly.



27. Move the Failover Group to the other server to verify the services start successfully there as well.


Script Setup

106

CHAPTER 10 Configure the Application Server

Complete the steps for Configuring the Application Server in the Installation Guide except for the following:

• Wherever the physical server name <server name> is referenced, use the <Virtual Computer Name> instead. However, in Database Authentication for Web Applications (Add the Windows user to Oracle Server) it specifies to add the server-name\username login to Oracle Server. In this case, use either the actual server name or a domain name.

• For the Area Access Manager and VideoViewer browser-based applications:

Use the <Virtual Computer Name> as the URL rather than the name of the physical server which is the default setting. Modify the C:\inetpub\wwwroot\lnl.og.web\Preferences.js g_lnl_pfx_webservice_serverAddress to use <Virtual Computer Name>.

• In the Web Visitor Management AdminApp for the clustered servers, you will need to change the default physical server name in the SilverlightApplicationConfiguration.xml file to the fully qualified <Virtual Computer Name>. For more information, refer to Update the URL in the Visitor Administration User Guide.

• If the Visitor Management Host is being served, you will need to change the default physical server name in the FlexApplicationConfiguration.xml file to the fully qualified <Virtual Computer Name>. For more information, refer to Update the URL in the Visitor Management Host User Guide.

• If the Visitor Management - Front Desk is being served, you will need to change the default physical server name in the serviceModelClient.config.deploy file to the fully qualified <Virtual Computer Name> twice. For more information, refer to Server Name in the Visitor Management Front Desk User Guide.

Configure Host Header Value

For OnGuard clients to successfully host the OnGuard web applications using the fully qualified <Virtual Computer Name> (the logical name of the cluster), you must configure the Host header value for the Default Web Site via IIS on both clustered servers.


Configure the Application Server

108

For IIS and Sites Served without SSL

1. Start up the Internet Information Services (IIS) Manager.

a. For Windows 7:

• Click the Windows Start button, then select Control Panel.

• Click System and Security, and then Administrative Tools.

• In the Administration Tools window, double-click Internet Information Services (IIS) Manager.

b. For Windows 8, Windows 8.1, or Windows Server 2012 R2:

• Press the Windows Key.

• Start typing Internet Information Services. Select “Internet Information Services Manager” from the list of icons in the result set.

2. In the Connections pane, expand the Sites node, and then right-click on Default Web Site, and then select Edit Bindings.

3. In the Site Bindings dialog, click [Edit] after selecting the “http” Type entry.

4. Type the fully qualified <Virtual Computer Name> in the Host name field, and then click [OK].

5. In the Site Bindings dialog, click [Close].

6. Restart IIS.

For IIS and Sites Served with SSL

Note: In an NEC cluster environment, because <Virtual Computer Name> is used as the host name, IIS version 7.0 does not allow the host name to be set for HTTPS bindings by default. To workaround this, you need to set a “friendly name” for the SSL certificate that begins with an asterisk “*” such as “*ynec2.qalab.lenel.com.”

Set the friendly name for the SSL certificate:

1. Start Microsoft Management Console by typing mmc at the command line or in the Run dialog.

2. Add the Certificates snap-in for the computer account and the local computer.

a. From the File menu, select Add/Remove Snap-in.

b. On the Standalone tab, click [Add]. The Add Standalone Snap-in window is opened.

c. Select “Certificates” from the available snap-ins, and then click [Add].

d. Select the Computer account radio button, and then click [Next].

e. Select the Local computer radio button, click [Finish], and then [Close].

3. In the tree, expand Certificates, and then select Personal > Certificates.

4. Right-click on the SSL certificate, and then select Properties.

5. Add a “*” to the beginning of the Friendly name, and then click [OK].

Configure the host header value:

1. Start up the Internet Information Services (IIS) Manager.

a. For Windows 7:

• Click the Windows Start button, then select Control Panel.

• Click System and Security, and then Administration Tools.

• In the Administration Tools window, double-click Internet Information Services (IIS) Manager.

b. For Windows 8, Windows 8.1, or Windows Server 2012 R2:

• Press the Windows Key.


Configure Host Header Value

• Start typing Internet Information Services. Select “Internet Information Services Manager” from the list of icons in the result set.

2. In the Connections pane, expand the Sites node, right-click on Default Web Site, and then select Edit Bindings.

3. In the Site Bindings dialog, click [Add]

4. Modify Type to “https.”

5. Leave the IP address set to “All unassigned.”

6. Verify Port is set to 443, select the appropriate SSL certificate, and then click [OK].

7. Restart IIS.


Configure the Application Server

110

CHAPTER 11 WAN Deployment


For WAN deployment, this document describes using the same subnet. If you use a different subnet, please contact PES. For more information, refer to Appendix B: WAN Network Requirements on page 125.

After a cluster has been properly installed and configured in the LAN environment, then the following steps are performed to prepare the cluster for deployment in the WAN environment:

1. From the Cluster Manager, stop the cluster from Cluster Manager:

a. Right-click on <Virtual Computer Name> in the tree view, and then select Service > Stop Cluster.

b. Click [Yes] when prompted to confirm.


WAN Deployment

112

2. Ship the Secondary Server and the other Secondary system elements, including the storage and WAN routers, to the final Secondary site.

3. (Optional) The Primary Server can be shut down from Cluster Manager and shipped along with the other Primary system elements to the final Primary site. Then it can be restarted.

4. If the Primary Server is fully operational at the final Primary site, and the Secondary Server has arrived at the final Secondary site, then the Secondary Server can be restarted from NEC ExpressCluster.

5. Return the Secondary Server to the cluster from the Cluster Manager. Data differences between the Primary Server and Secondary Server will be resolved and synchronized in this process. Assuming little or no data differences exist between the servers, the process should only take a few minutes. When the process completes, the cluster will be in a fully functional state.


CHAPTER 12 Upgrade OnGuard on NEC Systems

This section provides instructions for upgrading OnGuard software only when the NEC ExpressCluster edition, the operating system, and the database version remain constant. For any other upgrade scenario, we recommend a database backup, the cleansing of both servers in the cluster, clean installs, database restoration, and then database setup. There may be operating system and database system upgrade scenarios where very knowledgeable administrators could avoid erasing the entire configuration, but we cannot guarantee their support.

Only individuals who are highly knowledgeable about NEC ExpressCluster X R3 systems should perform the upgrade procedures:

Upgrading OnGuard consists of upgrading the software, the licenses (if a major upgrade), and potentially the NEC start and stop scripts.

For more information, refer to the Introduction in the OnGuard Upgrade Guide for a list of processes that must be completed before upgrading the OnGuard software.

IMPORTANT: Make sure to backup the OnGuard database. It is CRITICAL you have an up-to-date backup of the database before beginning the upgrade or service release process.

Prerequisites:

• OnGuard no longer supports Apollo hardware. Therefore, you must decommission any Apollo hardware in the field and delete them from System Administration before upgrading or else the upgrade will not work.

• If you are using any custom .dll files, you must back these up prior to upgrading the OnGuard software.

• Before installing a service release:

– Make sure you can open the OnGuard applications on the Secondary Server without any problems while the primary server is active.

– Verify the prerequisites found in the Upgrading OnGuard chapter in the Upgrade Guide have been met. If this is part of an Enterprise configuration, verify the prerequisites found in the Upgrading to OnGuard 7.2 Enterprise chapter of the Enterprise Setup & Configuration User Guide have been met.

1. Start Cluster Manager.


Upgrade OnGuard on NEC Systems

114

2. Verify the <Failover Group> is located on the Primary Server and both nodes are ONLINE (green).

3. A new license must be installed on the Primary Server and Secondary Server. Install the new licenses by completing the following steps:

a. On the Primary Server, start and log onto the OnGuard License Administration application.

b. Install the new license for the Primary server. After you have added this license, the old license and the new license will both be listed in the Installed Licenses drop-down. Leave the old license installed and log out of License Administration.

c. Move the <Failover Group> to the Secondary Server. The Secondary Server becomes active.

d. Repeat steps a and b on the Secondary Server to install the new Secondary Server license.

e. Move the <Failover Group> back to the Primary Server.

4. On the Secondary Server:

a. In Cluster Manager, right-click on the Secondary Server, and then select Service > Stop.

b. Verify all OnGuard services are stopped.

c. Install the upgrade or service release. The system may prompt you to install applications required for this version of the OnGuard software. After each application is installed, a reboot will be required causing the Secondary Server to automatically rejoin the cluster. Each time the Secondary Server rejoins the cluster, stop it before continuing.

d. Verify the Secondary Server has returned to the cluster. If it has not started, from Cluster Manager, right-click on the Secondary Server, and then select Service > Start.

e. Use the Configuration Editor to verify the ConnectionString setting in the application.config file specifies the <SID Service Name> rather than the <Secondary Server Hostname> for the Data Source. For more information, refer to the Configuration Editor appendix in the OnGuard Installation Guide.

f. If using Windows authentication, reconfigure the method used for authenticating with the database. Examine the authentication settings for Oracle to reconcile any differences from earlier versions to the current software. For more information, refer to Database Authentication for Web Applications in the OnGuard Installation Guide.

g. If this is part of an Enterprise configuration or you are using OpenAccess, update the MessageBroker.config file to use the <Virtual Computer Name> for SSL. For more information, refer to Manually Issue an SSL Certificate on page 93.

h. When the upgrade or service release is completed, because the upgrade or service release may start the OnGuard services, ensure the OnGuard services are set to “Manual” and stopped.

i. Run Database Setup from the Secondary Server while the Primary Server is still active.

5. Stop the Primary Server. Right-click on the Primary Server, and then select Service > Stop. This action should have the additional affect of moving the <Failover Group> and <Management Group> to the Secondary Server.

6. On the Primary Server:

a. Verify all OnGuard and Oracle services are stopped.

b. Install the upgrade or the service release. The system may prompt you to install applications required for this version of the OnGuard software. After each application is installed, a reboot may be required causing the Primary Server to automatically rejoin the cluster. Each time the Primary Server rejoins the cluster, stop it before continuing.

c. Use the Configuration Editor to verify the ConnectionString setting in the application.config file specifies the <SID Service Name> rather than the <Primary Server


Hostname> for the Data Source. For more information, refer to the Configuration Editor appendix in the OnGuard Installation Guide.

d. If using Windows authentication, reconfigure the method used for authenticating with the database. Examine the authentication settings for Oracle to reconcile any differences from earlier versions to the current software.

e. If this is part of an Enterprise configuration or you are using OpenAccess, update the MessageBroker.config file to use the <Virtual Computer Name> for SSL. For more information, refer to Manually Issue an SSL Certificate on page 93.

f. When the upgrade or service release is completed, because the upgrade or service release may start some of the OnGuard services, ensure all OnGuard services are set to “Manual” startup and stopped.

7. Reboot the Primary Server. This action will also rejoin the Primary Server to the cluster.

8. On the Secondary Server:

a. At this point, you should note any NEC start and stop script customizations you may have.

b. From Cluster Builder, replace the existing start and start scripts with the latest version from the Supplemental Materials disc and re-incorporate the customizations. This is also where you should be cognizant of potential service name changes such as changing “LS OpenIT” to “LS DataConduIT.”

c. Upload the Configuration File.

d. Restart the Cluster Manager. Wait approximately 15 seconds until it refreshes.

e. From the Service menu, select Stop Cluster.

f. From the Service menu, select Start Cluster. Specify the Secondary Server if given a choice to do so.

g. Verify that you can successfully log onto OnGuard applications on the Secondary Server.

h. Failover to the Primary Server:

• Right-click on the Cluster Group, and then select Move.

• In the Move window, select the Primary Server.

9. On the Primary Server, verify you can successfully log onto OnGuard applications on the Primary Server.


Upgrade OnGuard on NEC Systems

116

Appendices

APPENDIX A Ping Resource Configuration

ExpressCluster X R3 has an additional resource available that helps to prevent a split-brain scenario where both servers in a cluster start their services because they lose communication with each other. This resource works by pinging a shared resource to determine whether there has been a site or network outage and determines whether or not the other server should start based on it's ping results.

Note: It is recommended that you set up a ping resource.

1. From Cluster Manager, change to Operation Mode, and then suspend the cluster. From the Service menu, select Suspend Cluster.


120

2. Click [OK] to confirm.


3. Change to Config Mode, and then open the cluster properties. Right-click on the Cluster Name cluster, and then select Properties.


122

4. After the properties open for the cluster, select the NP Resolution tab, and then add the ping resource as follows:

a. Select “Ping” as the Type.

b. Enter an IP address for the Ping Target. This IP address should be an address that can be seen from both systems and is always up. A good example of an address to use is that of a router.

c. Specify which of the servers will monitor the ping resource by selecting “Use” for that server, and then click [OK].

5. When you are returned to Cluster Manager, from the File menu, select Apply the Configuration File.

6. When you are prompted to confirm the operation, click [Yes] to continue.

7. When the configuration file is successfully applied, click [OK] to confirm.


8. Click [Yes] to enable the recovery action.

9. Change to the Operation Mode to start the stopped services.

10. From the Service menu, select Resume Cluster.

11. When prompted to confirm the operation, click [OK].


124

APPENDIX B WAN Network Requirements

Note: Professional Engineering Services (PES) are required for NEC ExpressCluster X R3 LAN and WAN systems.

NEC ExpressCluster X R3 WAN has the following basic network requirements for each cluster of two (2) servers (Primary and Secondary) that must be met in order to enable full DR (disaster recovery) functionality and ensure the proper operation of the NEC ExpressCluster X R3 WAN system:

• Requirement 1 on page 126

A logical IP protocol network that spans two sites (Primary and Secondary) must be available to be used as the Public network to enable transparent migration of virtual server identity between the Primary and Secondary systems.


Proper IP protocol network routing between the client systems and the Public network must be configured to enable network communications between client and server systems.


Proper IP protocol network routing between the server systems and the Private (Interconnect) network must be configured to enable cluster specific network communication between the Primary and Secondary Servers.


For synchronous data mirroring: Private network round trip time (RTT) for 1500-byte PING packets must be 70 milliseconds or less to ensure proper operation of ExpressCluster X WAN and the target application. For asynchronous data mirroring: Private network RTT for 1500-byte PING packets should be low enough to meet sustained target application transaction performance requirements to minimize risk of excessive data loss in case of system failure.


For synchronous data mirroring: Private network bandwidth must be 1.5 Mbps or greater to meet sustained target application transaction performance requirements. For asynchronous data mirroring: Private network bandwidth must be high enough to meet sustained target application transaction performance requirements to minimize the risk of excessive data loss in case of system failure.


126

Implications and Recommendations

In general, if a customer network infrastructure does not meet the network requirements, then professional network consulting services would be required to analyze the existing network infrastructure, design the necessary network infrastructure changes, and implement the designed network changes using specific network equipment.

The following sections provide some of the implications and recommended methods to meet the network requirements in a generic context that may or may not be appropriate for a specific deployment.

Requirement 1

Figure 1 on page 126 shows a basic LAN configuration within the same data center that meets this requirement. Figure 2 on page 126 shows an example of a basic WAN configuration that also meets this requirement. In a typical WAN environment, this requirement usually means that a dedicated virtual network (for example, VLAN or VPN) has to be in place between the Primary and Secondary sites. Generally, dedicated routers or switches are required to implement the virtual network using layer 2 or layer 3 network protocols.

FIGURE 1. NEC ExpressCluster X R3 LAN network configuration within the same data center

FIGURE 2. NEC ExpressCluster X R3 WAN network configuration for sites sharing common subnets



Examples of commercial routers that could be used to implement the virtual network include Cisco routers running Cisco IOS v12.0 and later (for example, Cisco 1711) which can support layer 3 VPN (for example, IPSec) or layer 2 VPN (for example, L2TPv3). A more advanced configuration example using VPN routers is shown in Figure 3 on page 127.

FIGURE 3. Recommended NEC ExpressCluster X R3 WAN network configuration for sites with separate local subnets

In general, customer organizations may have multiple groups managing the IT infrastructure so approval to implement virtual networks using specific network equipment and protocols may require explicit authorization from multiple groups besides the group purchasing ExpressCluster X WAN. Understanding and coordination of customer organization groups and processes is critical to successful deployment.

Requirement 2

This requirement is meant to ensure proper network communication can occur between client systems residing on separate logical networks from the logical networks of the servers. It is a general requirement and fundamental to all IP network communication as well as being a technically simple


128

objective to accomplish. However, depending on the customer organization, approval from multiple groups may be required to implement changes to customer network routers to enable the necessary network communication.

If for some reason the necessary routing is not obtainable then a possible workaround is to connect all relevant client systems directly to the same logical network as the servers and assign the addresses to the client systems from the same logical network as the servers. An example is shown in Figure 4 on page 128.

FIGURE 4. Workaround for NEC ExpressCluster X R3 WAN network configuration for sites with separate local subnets

Requirement 3

This requirement is intended to ensure that proper network communication can occur between the Primary and Secondary Server for the cluster health check and data mirroring. It is a general requirement and fundamental to all IP network communication as well as being a technically simple objective to accomplish. However, depending on the customer organization, approval from multiple groups may be required to implement changes to customer network routers to enable the necessary network communication.

Requirement 4

For synchronous data mirroring usage, ExpressCluster X WAN requires the Private (Interconnect) network round trip latency (RTT) to be 70 ms or less for reliable operation. Furthermore, lower RTT may be required in order to meet target applications transaction performance requirement.

For asynchronous data mirroring usage, ExpressCluster X WAN does not have a strict Private network RTT requirement, but significant data loss risk will increase if the RTT becomes much larger than the typical target application transaction time as more data will be queued on the local server.



Requirement 5

For synchronous mirroring usage, ExpressCluster X WAN requires an available Private network bandwidth of 1.5 Mbps or greater. Furthermore, higher available network bandwidth may be required to meet the target application transaction performance requirement.

For asynchronous data mirroring usage, ExpressCluster X WAN does not have a strict Private network available bandwidth requirement, but significant data loss risk will increase if the available network bandwidth becomes much lower than the typical target application transaction data rate as more data will be queued on the local server.

A general rule of thumb for available network bandwidth is that the raw available network bandwidth should be at least three (3) times the required average application data rates. For example, if target application expects to process 10 2 KBytes transactions per second, then the required network bandwidth would be 40 KBytes (-2*10*2KBytes) per second which in turn means (assuming a 10x conversion from raw data bytes to network packet bits) 400 KBits per second of available network bandwidth would be required.


130

Index

AAdd a script resource ..................................... 97Application Server ........................................ 107

CClean installs ................................................. 113Configure

Application Server .............................. 107host header value ................................. 107Lenel Utility for ExpressCluster ......... 31Windows settings .................................. 31

Create the Lenel live database ...................... 89

DDisk setup ........................................................ 19

FFirewall Settings ............................................. 18

IInitial LAN setup overview

Oracle 11g .............................................. 16Oracle 12c .............................................. 14

InstallOnGuard on an NEC server ......... 91, 92Oracle Client .......................................... 87Oracle Server ......................................... 83

Install a service release on NEC systems . 113Introduction ..................................................... 12

LLenel Utility for ExpressCluster .................. 31

NNetwork Configuration Checklist ................ 13Network requirements .......................... 12, 125Network setup ................................................. 26

OOnGuard installation on an NEC server ..... 91Oracle Server software .................................. 83Other referenced user guides .......................... 7

PPrerequisites ...................................................... 7

SScript setup

add a script resource ............................. 97stop the group ........................................ 95stop the services .................................... 95

Set services ...................................................... 92SSL certificates ............................................... 93

UUpgrade OnGuard on NEC systems ......... 113

WWAN deployment overview ......................... 18WAN network requirements ....................... 125Windows settings ............................................ 31

Lenel Utility for ExpressCluster ........ 31


UTC Fire & Security Americas Corporation, Inc.1212 Pittsford-Victor RoadPittsford, New York 14534 USATel 866.788.5095 Fax [email protected]

NEC ExpressCluster X R3 LAN & WAN with Oracle Installation ...partner.lenel.com/.../7.2/userguides/NECExpressCluster_Oracle.pdf · Oracle 11g R2 ... LAN & WAN with Oracle Installation

Documents