Nec Expresscluster X R3 Lan & Wan With Microsoft SQL Server Installation Guide

7.
6
NEC ExpressCluster X R3 LAN
& WAN with Microsoft SQL
Server Installation Guide
Lenel® OnGuard® 7.6 NEC ExpressCluster X R3 LAN & WAN with Microsoft SQL Server Installation
Guide. This guide is item number DOC-955, revision 10.008, July 2019.
© 2019 United Technologies Corporation. All rights reserved.
Lenel®, OnGuard®, Prism®, BlueDiamond™, and UltraView® are registered trademarks or trademarks of
UTC Fire & Security Americas Corporation, Inc. LenelS2 is a part of Carrier.
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 prior
express written permission of UTC Fire & Security Americas Corporation, Inc., which such permission may
have been granted in a separate agreement (i.e., end user license agreement or software license agreement for
the particular application).
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 Business Objects, S.A.
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.
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 International Corporation.
Other product names mentioned may be trademarks or registered trademarks of their respective companies
and are hereby acknowledged.
Product Disclaimers and Warnings
THESE PRODUCTS ARE INTENDED FOR SALE TO, AND INSTALLATION BY, AN EXPERIENCED
SECURITY PROFESSIONAL. LENELS2 CANNOT PROVIDE ANY ASSURANCE THAT ANY PERSON
OR ENTITY BUYING ITS PRODUCTS, INCLUDING ANY "AUTHORIZED DEALER", IS PROPERLY
TRAINED OR EXPERIENCED TO CORRECTLY INSTALL SECURITY RELATED PRODUCTS.
LENELS2 DOES NOT REPRESENT THAT SOFTWARE, HARDWARE OR RELATED SERVICES MAY
NOT BE HACKED, COMPROMISED AND/OR CIRCUMVENTED. LENELS2 DOES NOT WARRANT
THAT SOFTWARE, HARDWARE OR RELATED SERVICES WILL WORK PROPERLY IN ALL
ENVIRONMENTS AND APPLICATIONS AND DOES NOT WARRANT ANY SOFTWARE,
HARDWARE OR RELATED SERVICES AGAINST HARMFUL ELECTROMAGNETIC
INTERFERENCE INDUCTION OR RADIATION (EMI, RFI, ETC.) EMITTED FROM EXTERNAL
SOURCES. THE ABILITY OF SOFTWARE, HARDWARE AND RELATED SERVICES TO WORK
PROPERLY DEPENDS ON A NUMBER OF PRODUCTS AND SERVICES MADE AVAILABLE BY
THIRD PARTIES OVER WHICH LENELS2 HAS NO CONTROL INCLUDING, BUT NOT LIMITED TO,
INTERNET, CELLULAR AND LANDLINE CONNECTIVITY; MOBILE DEVICE AND RELATED
OPERATING SYSTEM COMPATABILITY; OR PROPER INSTALLATION, CONFIGURATION AND
MAINTENANCE OF AUTHORIZED HARDWARE AND OTHER SOFTWARE.
LENELS2 MAY MAKE CERTAIN BIOMETRIC CAPABILITIES (E.G., FINGERPRINT, VOICE PRINT,
FACIAL RECOGNITION, ETC.), DATA RECORDING CAPABILITIES (E.G., VOICE RECORDING),
AND/OR DATA/INFORMATION RECOGNITION AND TRANSLATION CAPABILITIES AVAILABLE
IN PRODUCTS LENELS2 MANUFACTURES AND/OR RESELLS. LENELS2 DOES NOT CONTROL
THE CONDITIONS AND METHODS OF USE OF PRODUCTS IT MANUFACTURES AND/OR
RESELLS. THE END-USER AND/OR INSTALLER AND/OR RESELLER/DISTRIBUTOR ACT AS
CONTROLLER OF THE DATA RESULTING FROM USE OF THESE PRODUCTS, INCLUDING ANY
RESULTING PERSONALLY IDENTIFIABLE INFORMATION OR PRIVATE DATA, AND ARE SOLELY
RESPONSIBLE TO ENSURE THAT ANY PARTICULAR INSTALLATION AND USE OF PRODUCTS
COMPLY WITH ALL APPLICABLE PRIVACY AND OTHER LAWS, INCLUDING ANY
REQUIREMENT TO OBTAIN CONSENT. THE CAPABILITY OR USE OF ANY PRODUCTS
MANUFACTURED OR SOLD BY LENELS2 TO RECORD CONSENT SHALL NOT BE SUBSTITUTED
FOR THE CONTROLLER'S OBLIGATION TO INDEPENDENTLY DETERMINE WHETHER CONSENT
IS REQUIRED, NOR SHALL SUCH CAPABILITY OR USE SHIFT ANY OBLIGATION TO OBTAIN
ANY REQUIRED CONSENT TO LENELS2.
For more information on warranty disclaimers and product safety information, please check https://
firesecurityproducts.com/en/policy/product-warning or scan the following code:
Table of Contents
CHAPTER 1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Conventions Used in this Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Other Referenced User Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
LAN Initial Setup Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
WAN Deployment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Network Pre-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Network Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Starting Cluster Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Rebooting 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Running the Lenel Utility for ExpressCluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Running the Utility at Different Points of the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
CHAPTER 4 Cluster Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Cluster Manager Setup (Install the JRE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
NEC ExpressCluster X R3 LAN & WAN with Microsoft SQL Server Installation Guide 5
Table of Contents
Install ExpressCluster X R3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Configure the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
CHAPTER 5 Install Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Set Up the OnGuard Environment on the Primary Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Set Up the OnGuard Environment on the Secondary Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Configure SQL Server on the Primary Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Create the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Create a Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Obtain the SID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Run a New Query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Set Memory Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Truncate the Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Create an Archival Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Configure SQL Server on the Secondary Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Attach the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Attach the Archival Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Set Memory Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Truncate the Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
CHAPTER 6 Install OnGuard on the NEC Server . . . . . . . . . . . . . . . . . . . . . . . . . 89

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Install OnGuard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Configure the Archival Database in OnGuard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Manually Issue an SSL Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
CHAPTER 7 Configure the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Configure Host Header Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
For IIS and Sites Served without SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
For IIS and Sites Served with SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
CHAPTER 8 Script Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Stop the Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Stop the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Add a Script Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
CHAPTER 9 WAN Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
CHAPTER 10 Upgrading OnGuard on NEC Systems . . . . . . . . . . . . . . . . . . . . . . 111
Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6 NEC ExpressCluster X R3 LAN & WAN with Microsoft SQL Server Installation Guide
Table of Contents
APPENDIX A Ping Resource Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
APPENDIX B WAN Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Implications and Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124
Requirement 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Requirement 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Requirement 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Requirement 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Requirement 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Table of Contents
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].
• Where actual values are substituted for items in the Network Configuration Checklist, the name
of the item is written in italics within angle brackets. For example, <Virtual Computer Name>.
For more information, refer to Network Configuration Checklist on page 17.
• Where actual values are substituted for items in the Lenel Utility for ExpressCluster user
interface, the name of the item is written in italics within square brackets. For example, [Private
NIC GUID]. For more information, refer to Running the Lenel Utility for ExpressCluster on
page 35.
Other Referenced User Guides

In addition to this user guide, the following guides provide instructions for installing OnGuard and
SQL Server. These guides are included on the OnGuard installation media:
Installation Guide. A comprehensive guide that includes instructions for installing the OnGuard
software. This guide also includes information on all supported SQL Server database systems and the
browser-based client applications.
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 Chapter 7: Configure the Application Server on page 93.
Prerequisites
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 Chapter 7: Configure the Application Server on page 93.
In addition to this user guide, the following guides provide advanced installation and configuration
information for your NEC ExpressCluster X R3 system. These guides are included 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 install
A 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 considered a clean install.
Client
Refers to the computer(s) that connect to the server.
Cluster
A logical collection of servers that have clustering software installed. Clustered servers share a
virtual identity.
Cluster partition
A small (non-user) partition used by ExpressCluster to store metadata that keeps track of the
mirror disk status.
Data partition
Disk partition used to store regular user/application data.
Database system
Refers to the database program that you are using. This document assumes that you are using
Microsoft SQL Server as your database system.
Disk resource
A shared disk volume used to resolve Network Partition situations.
ExpressCluster Builder
The software component used to build, configure, and modify NEC clusters.
ExpressCluster Manager
The software component that is used to monitor and manipulate the cluster.
Failover
The 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 address
The most common type of shared IP address for a cluster group. Floating IP addresses can
only be on the same sub-net as the cluster servers, as opposed to Virtual IP Addresses.
Group
A logical collection of shared resources between clustered servers. Group resources often
include Virtual Computer Name, Mirror disk, Floating/Virtual IP Address, etc.
Group resource
Any item in a cluster group (Virtual Computer Name, Mirror/Switch Disk, Floating/Virtual IP
Address, etc.).
GUID
Refers 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 Key
Commonly referred to as a “dongle.” It is used on the server as part of the OnGuard license.
Alternatively, you may have a software license. For more information, refer to Software
license on page 13.
Heartbeat
A periodic transmission sent between clustered servers. The heartbeat signal is used to inform
partner servers of system status.
High Availability
High-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.
Prerequisites
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,
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 network
Also referred to as the “Private” network. 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 uses both for heartbeat
communication.
Java Policy file

A 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.
LAN
Refers to Local Area Network. A logical network that does not contain segments separated by
routers. LANs typically span small regions.
Management IP address
An IP address 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.
Metadata
Data written to the Cluster Partition of mirrored/switch disks - used by ExpressCluster to
maintain these resources.
Mirror disk
A 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.
Node
A member server of a cluster. Also refers to any addressable endpoint on a network (server,
router, etc.).
OnGuard services
OnGuard services include all those services with names beginning with “LS”, “Lps”, and
“Lnr.”
Ping resource
A 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 Server
The server that a cluster group starts up on, by default.
Secondary Server
The 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.
Servers
The 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 Release
Service 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 license
OnGuard 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.bat
An NEC 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.bat
An NEC ExpressCluster script that is run when a group stops. The Stop.bat file contains
instructions for stopping applications and services controlled by ExpressCluster.
URI
Refers 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 Name

A 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 Address
A type of shared IP address for a cluster group. Virtual IP addresses can be on a different sub-
net than the cluster servers, as opposed to Floating IP Addresses.
WAN
Refers to Wide Area Network. A logical network that contains segments separated by routers.
WANs typically span large geographical regions.
Prerequisites
Workstation
Any computer where OnGuard software is installed.
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. OnGuard supports
• High Availability Systems support includes:
– NEC ExpressCluster X R3 32-bit LAN
– NEC ExpressCluster X R3 32-bit WAN
– NEC ExpressCluster X R3 64-bit LAN
– NEC ExpressCluster X R3 64-bit WAN
Note: For the latest patch sets and service packs supported, refer to the Third Party
Compatibility Chart on the LenelS2 web site for current NEC ExpressCluster support.
Note: Instructions are provided for upgrading the OnGuard software only when the NEC
ExpressCluster X version, operating system, and database version remain constant. For
any other upgrade scenario, a database backup, the cleansing of both servers in the
cluster, clean installs, database restoration, and then database setup are recommended.
There might be operating system and database system upgrade scenarios where very
knowledgeable administrators could avoid erasing the entire configuration, but support
cannot be guaranteed.
NEC ExpressCluster X R3 with OnGuard supports Standard and Enterprise editions of common
database server applications and the following operating systems:
• Database Server: SQL Server. For versions supported with NEC ExpressCluster X and OnGuard,
refer to the Third Party Application Compatibility Chart.
• Web Server: Microsoft Internet Information Services
• Operating System: Windows Server 2012 R2 64-bit
Notes: For the latest patch sets and service packs supported, refer to the Third Party
Application Compatibility Chart on the LenelS2 web site at: https://partner.lenel.com/
downloads/onguard/software. Once there, select Compatibility Charts from the
Choose type of download menu.
When accessing the Downloads section at https://partner.lenel.com, make sure to select
the version of OnGuard that is currently installed.
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
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 (optional) final
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 about WAN network
requirements, refer to Appendix B: WAN Network Requirements on page 123.
LAN Initial 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 123.
The first stage is performed with all hardware components at a single site where as the WAN
connection is replaced with a temporary, direct LAN connection.
An overview of the major steps in the first stage include follows:
Prerequisites
1. Plan the system network. For more information, refer to Network Configuration Checklist on
page 17.
2. Complete steps 3 - 8 on the Primary Server and Secondary Server.
3. Configure the required disk operating system settings (including the mirrored disk set) for NEC
ExpressCluster X R3. For more information, refer to Disk Setup on page 19.
4. Configure the required network settings for NEC ExpressCluster X R3. For more information,
refer to Network Setup on page 26.
5. Configure the Windows settings using the Lenel Utility for ExpressCluster. At this point in the
process, perform the instructions in After Network Setup on page 37.
6. Configure the required firewall exceptions. For more information, refer to Firewall Settings on
page 18.
7. Install ExpressCluster Manager. For more information, refer to Cluster Manager Setup (Install
the JRE) on page 39.
8. Install ExpressCluster Server. For more information, refer to Install ExpressCluster X R3 on
page 41.
9. On the Primary Server only, configure the cluster. For more information, refer to Configure the
Cluster on page 52.
10. Run the Lenel Utility for ExpressCluster again. At this point in the process, perform the
instructions in After Cluster Setup on page 37.
11. Install and set up the OnGuard environment on both servers, beginning on the Primary Server.
a. Install Microsoft SQL Server on page 81
b. Install OnGuard on the NEC Server on page 89
12. Run the Lenel Utility for ExpressCluster again. At this point in the process, perform the
instructions in After OnGuard Setup on page 38.
13. Create the scripts to handle starting or stopping the system on both servers. For more
information, refer to Script Setup on page 97.
WAN Deployment Overview

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 Overview on page 16 and WAN Network Requirements on page 123.
Network Pre-Installation
Network Pre-Installation
Network Configuration Checklist

To set up NEC ExpressCluster X R3 in a LAN (or WAN) environment, the network IP 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):
• Database Name: ACCESSCONTROL
Note: If the Database Name is not ACCESSCONTROL, you must run the Configuration
Editor to modify the Initial Catalog entry of the ConnectionString and also modify the
default database of your ODBC. With Windows Server 2012 R2, on the Start screen,
begin typing “Configuration Editor,” and then press <Enter> when the program is
located.
• (Optional) Archival Database Name: ACCESSCONTROL_ARCHIVAL
• 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):
• Virtual Computer Name (Virtual Hostname):
• Failover Group:
• Management Group (By default, the name automatically assigned to Management Group is
“ManagementGroup.”)
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 either of the following URLs to start Cluster
Manager:
Prerequisites
• 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.
Rebooting the Cluster

IMPORTANT: If prompted, do NOT restart your computer. Instead, we recommend rebooting
the cluster via Cluster Manager. In Cluster Manager, right-click on <Cluster
Name> in the tree view, then select Reboot. If necessary, start the cluster
before rebooting it.
Firewall Settings
NEC ExpressCluster X R3 uses several TCP and UDP 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: Adobe Reader is required to view the PDF guides. It can be installed from the
Supplemental Materials media >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
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].
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
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].
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].
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.
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 15.
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 media. 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
Configure Windows Settings
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 Database Connection Virtual Computer Name

file
application.config App Server URI Virtual Computer Name

file
application.config License Client Host Virtual Computer Name

file
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 Shortcut to ExpressCluster Manager Management Port and

file Management IP Address
Registry Modifications
Action What is modified
Disable Loopback • Type: DWORD

Check • Location:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa
• Value Name: DisableLoopbackCheck
• Value: 1
Registry Modifications (Continued)
Back Connection • Type: MULTI-STRING

Host Names • Location:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\M
SV1_0
• Value Name: BackConnectionHostNames
• Value: [Virtual Computer Name] (Plus any pre-existing previous
values)
Disable Strict Name • Type: DWORD

Checking • Location:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanM
anServer\Parameters
• Value Name: DisableStrictNameChecking
• Value: 1
TCP • Type: DWORD

Acknowledgement • Location:
Frequency HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TcpIP
\Parameters\Interfaces\[Private NIC GUID]
• Value Name: TcpAckFrequency
• Value: 1
Vinca Setting (used • Type: String

by Linkage Server) • 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 • Type: String

1 • Location: HKEY_CURRENT_USER\Software\Lenel
• Value Name: LoginDrvLoc_[ODBC name]
• Value: [Floating IP Address]

2 • Location: HKEY_LOCAL_MACHINE\Software\Wow6432Node\Lenel

3 • 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 • File: %AllUsersProfile%\Lnl\application.config

• Section: [appSettings]
• Key: ConnectionString
• Value Portion: Data Source
App Server URI • File: %AllUsersProfile%\Lnl\application.config

• Key: ApplicationServerUri
• Value Portion: [Host Name]
License Client Host • File: %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
• grant codeBase "http://127.0.0.1:29003/webmanager.jar" {
• grant codeBase "http://192.168.1.1:29003/clptrek.jar" { permission
• grant codeBase "http://192.168.1.1:29003/webmanager.jar" {
ExpressCluster File: %UserProfile%\Favorites\ExpressCluster Manager.url

Manager Internet
Favorite (Bookmark)
Running the Lenel Utility for ExpressCluster

1. Run the utility:
a. Insert the Supplemental Materials media 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.
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 <Virtual Computer Name>.
Note: Most registry modifications (except Login Driver Location Settings and Vinca
Setting), require a cluster reboot to make the registry settings take effect.
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 37
• After Cluster Setup on page 37
• After OnGuard Setup on page 38
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 17.
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.
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
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
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
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
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
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
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
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. For more
information, refer to Starting Cluster Manager on page 17.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 Microsoft SQL Server
OnGuard with NEC ExpressCluster X R3 supports Microsoft SQL Server Standard and Enterprise
Editions.
This section provides instructions for installing SQL Server Standard Edition.
The latest approved SQL Server service packs should also be installed. For specific information, refer
to the Third Party Compatibility Chart on the LenelS2 Web site at: https://partner.lenel.com/
downloads/onguard/software. Once there, select Compatibility Charts from the Choose type of
download menu.
Notes: When accessing the Downloads section at https://partner.lenel.com, make sure to select
the version of OnGuard that is currently installed.
Do NOT restart your computer after the cluster is set up. Whenever prompted to restart
your computer, use the Cluster Manager to reboot the cluster instead.
SQL Server and OnGuard is installed on both servers, starting on the Primary Server.
Set Up the OnGuard Environment on the Primary Server

Prerequisites:
• Make sure the Primary Server is active. If not, failover to the Primary Server.
• Make sure the Lenel ExpressCluster Utility was run after setting up the cluster on both the
Primary and Secondary Servers. For more information, refer to Running the Utility at Different
Points of the Installation on page 37.
1. Install SQL Server:
a. Perform the steps in Installing SQL Server in the Installation Guide. After installing SQL
Server, when prompted, do NOT “Restart your computer.” Instead, reboot the cluster from
Cluster Manager.
b. Create the Database on page 82
c. Create a Login on page 83
d. Obtain the SID on page 84
e. Run a New Query on page 84
Install Microsoft SQL Server
f. Set Memory Usage on page 85

g. Truncate the Log File on page 85
h. (Optional) Create an Archival Database on page 85
2. Install OnGuard: Perform the steps in Install OnGuard on the NEC Server on page 89.
Set Up the OnGuard Environment on the Secondary Server

1. Install SQL Server:
a. Perform the steps in “Installing SQL Server in the Installation Guide. After installing SQL
Server, when prompted, do NOT “Restart your computer.” Instead, reboot the cluster from
Cluster Manager.
b. On the Primary Server, log into Windows, and then failover to the Secondary Server.
c. Configure SQL Server on the Secondary Server performing the following steps in the order
given:
• Attach the Database on page 86
• (Optional) Attach the Archival Database on page 87
• Set Memory Usage on page 87
• Truncate the Log File on page 87
2. Install OnGuard: Perform the steps in Install OnGuard on the NEC Server on page 89.
Configure SQL Server on the Primary Server
Create the Database

1. Create a directory named “MSSQL” in the Mirror Partition.
2. Create a sub-directory named “DATA” in the ‘MSSQL” directory, for example,
Y:\MSSQL\DATA.
3. Start SQL Server Management Studio.
For more information, refer to “Using OnGuard on Supported Operating Systems” in the
Installation Guide.
When the Connect to Server window is displayed:
• Enter the Virtual Computer Name for the Server name.
• Select “SQL Server Authentication” from the Authentication drop-down.
• Enter the “sa” login information, and then click [Connect].
4. In the Object Explorer pane, expand the Databases folder. Right-click on the Databases folder,
and then select New Database. The New Database window is displayed.
5. On the General page of the Login window:
a. In the Database name field, type ACCESSCONTROL. This is not case sensitive.
b. Set the Initial Size (MB) of the Data file to 50.
c. Set the Initial Size (MB) of the Log file to 10.
d. Scroll to the right in the Database files listing window, and then click the [...] button in the
Autogrowth column of the log file row.
e. Select the Unlimited radio button and then click [OK].
f. Set the Path of the Database and log files to Y:\MSSQL\DATA.
6. On the Options page of the Login window:

a. Ensure the Recovery model drop-down is set to “Full.”
b. Verify that the Compatibility level drop-down is set to the proper compatibility level for
your SQL Server version.
c. In the Other options list view, set Auto Shrink, Auto Update Statistics, Auto Create
Statistics, and Recursive Triggers Enabled to “True.”
d. Click [OK].
Create a Login
1. In the Object Explorer pane, expand the Security folder.
2. Right-click the Logins folder, then select New Login.
3. In the General page of the Login window:
a. In the Login name field, type LENEL.
b. Select the SQL Server authentication radio button.
• For Password, type the Lenel Database User Password Secur1ty# (default
password).
• For Confirm password, type the Lenel Database User Password Secur1ty#.
Note: The SQL Server password is case-sensitive.

c. Deselect the Enforce password policy, Enforce password expiration, and User must
change password at the next login check boxes.
IMPORTANT: If you select the Enforce password expiration check box, you will be
required by SQL Server to select a new login password at regular intervals.
When the login password is changed by SQL Server, it must also be updated
with the LS Login Driver. Failure to update the Login Driver will cause
OnGuard not to function properly.
4. In the Server Roles page of the Login window, we recommend that you select the following
check boxes:
• Most users should select dbcreator, serveradmin, and public.
• Advanced users should only select the public check box.
5. In the User Mapping page of the Login window:
a. Select the following databases from the Users mapped to this login list:
• master
• tempdb
b. Make sure the Database role membership for each has Public selected.
c. Click [OK].
6. (Optional) For advanced users who do not want the database owned by lenel, complete the
following steps:
a. In the Object Explorer pane of SQL Server Management Studio, right-click on the OnGuard
database you just created and select New Query. A query tab is shown.
b. In the text window, type:
• CREATE ROLE db_executor
• GRANT EXECUTE TO db_executor
c. Press <F5> to execute the command.
d. The message Command(s) completed successfully is displayed in the Messages tab.

e. Click the close (“X”) button to close the query tab, then click [No] when prompted if you
want to save the changes.
f. Select the Login - New dialog, which should already be open but might be hidden by another
window.
g. Select Server Roles from the Select a page pane, and then select (check) the following:
• public
h. Select User Mapping from the Select a page pane, and then select the ACCESSCONTROL
database.
i. Select (check) the following roles:
• public
• db_datareader
• db_datawriter
• db_ddladmin
• db_executor
j. Click [OK].
7. The new login will display in the Logins folder.
Note: At this point the lenel user provides OnGuard functionality only. Any database level
administration, such as backups and restores, must be performed by a different user with
the appropriate permissions.
Obtain the SID

To obtain the SID for the “Lenel” login, complete the following steps:
1. In the Object Explorer pane under System Databases, right-click on master, then select New
Query.
2. Type the following command in the query editor:
select sid from master.dbo.syslogins where LoginName = ‘Lenel’
3. Press <F5> to execute the command.
4. In the Results tab, right-click on the SID returned by SQL, then select Copy. (This SID will be
required on the Secondary Server to create the “Lenel” login.)
a. Open a new text file, and then paste the SID into it.
b. Save the text file on a public folder accessible from the Secondary Server.
Run a New Query

1. In the Object Explorer pane, right-click on the ACCESSCONTROL database, and then select
New Query.
a. Type the following command in the query editor:
sp_changedbowner lenel
b. Press <F5> to execute the command. “Command(s) completed successfully” should be
displayed in the Messages tab.
2. Close the query editor without saving the changes.
Set Memory Usage

1. In the Object Explorer pane, right-click on the database engine Server Name, then select
Properties.
2. On the Memory page of the Login window, set the Maximum server memory (in MB) option
to roughly one-half of your system’s actual memory. This action ensures the database does not
use your entire system’s memory which would needlessly slow down your system.
3. Click [OK].
Truncate the Log File
Note: This procedure requires that the Recovery Model is set to “Full” on the Database
Properties > Options page.
1. In the Object Explorer pane of SQL Server Management Studio, right-click on the
ACCESSCONTROL database, and then select Tasks > Shrink > Files.
2. The Shrink File window is opened.
a. In the File type drop-down, select “Log.”
b. Ensure the Release unused space radio button is selected.
c. Click [OK].
Create an Archival Database
Note: An archival database is optional.

In addition to creating the required Live database, OnGuard provides two options for archiving
Events, Events Video Location, Alarm acknowledgments, User Transactions, Visits Records, and
specific event types from the Live database tables, as a way of keeping the database from growing so
large over time that system performance is affected.
• Archive to text files
• Archive to an Archival database
The Archives Folder chapter in the System Administration User Guide describes these two options,
and how to configure each option. After reviewing the Archives Folder chapter, select and implement
an archive strategy on the databases installed on your Primary and Secondary servers.
If you decide to archive the Live database to an Archival database, then create the Archival database
by performing the following steps.
1. Perform all of the previous steps to create the Live database (ACCESSCONTROL).
2. Repeat the Create the Database on page 82 steps again to create the Archival database, changing
the Database name to ACCESSCONTROL_ARCHIVAL.
3. Repeat the Run a New Query on page 84 procedure to create a login. The Archival database is
ready to use other than configuring it in the OnGuard software.
• WARNING! • Now that SQL Server is configured on the Primary Server, make sure your
next step is to install OnGuard on the Primary Server. For more information,
refer to Install OnGuard on the NEC Server on page 89.
Configure SQL Server on the Secondary Server
Attach the Database
• WARNING! • Ensure SQL Server and OnGuard are installed and configured on the Primary
Server before completing the following steps on the Secondary Server.
1. Make sure the Secondary Server is active and the SQL Server services are started.
2. Open SQL Server Management Studio.
• For more information, refer to “Using OnGuard on Supported Operating Systems” in
the Installation Guide.
• When the Connect to Server window is displayed, enter the <Virtual Computer Name>
in the Server name field, and then click [Connect].
3. In the Object Explorer pane, right-click on the <Virtual Computer Name> server, and then select
New Query.
a. Add the “Lenel” login using the previously saved SID by typing the following commands in
the query editor:
create login Lenel with password='Secur1ty#',
check_policy=off, check_expiration=off, sid=<SID obtained
from Primary Server>;
Exec sp_addsrvrolemember 'Lenel', 'dbcreator';
Exec sp_addsrvrolemember 'Lenel', 'serveradmin';
Notes: This statement creates the user and automatically disables the “Enforce Password
Policy” and “Enforce Password Expiration” options in the properties of the newly
created SQL user. This should be done because the default Lenel user password is often
invalid on many systems that enforce more complicated password policies. In addition,
the password expiration policy is NOT enforced because OnGuard would stop working
if the password expires and no one logs into SQL to update and then re-synchronize the
Login Driver.
The default Lenel user password is “Secur1ty#”.
The SID obtained from Primary Server is the same as the SID obtained for user Lenel
on the Primary Server.
b. Press <F5> to execute the command.

c. Verify that the new login appears in the Logins folder.
4. In the Object Explorer pane, right-click on the Databases folder, and then select Attach. The
Attach Databases window is displayed.
a. Click [Add] and then navigate to Y:\MSSQL\DATA\ACCESSCONTROL.mdf.
b. Click [OK]. The database is now included in the Databases folder.
5. In the Object Explorer pane, right-click on the ACCESSCONTROL database, and then select
New Query.
b. Press <F5> to execute the command. “Command(s) completed successfully” will display in
the Messages tab.
c. Close the query editor without saving the query.
Configure SQL Server on the Secondary Server
Attach the Archival Database
Note: An archival database is optional.

If you created an archival database, complete the following steps:
1. In the Object Explorer pane, right-click on the Databases folder, and then select Attach. The
Attach Databases window is displayed.
a. Click [Add] and then navigate to
Y:\MSSQL\DATA\ACCESSCONTROL_ARCHIVAL.mdf
b. Click [OK]. The database is now included in the Databases folder.
2. In the Object Explorer pane, right-click on the ACCESSCONTROL_ARCHIVAL database, and
then select New Query.
b. Press <F5> to execute the command. “Command(s) completed successfully” will display in
the Messages tab.
c. Close the query editor without saving the query.
Set Memory Usage

1. In the Object Explorer pane, right-click on the database engine Server Name, then select
Properties.
2. On the Memory page of the Login window, set the Maximum server memory (in MB) option
to be roughly one half of your system’s actual memory. This will ensure the database does not
use your entire system’s memory which would needlessly slow down your system.
3. Repeat steps 1 and 2 for the ACCESSCONTROL_ARCHIVAL database.
Truncate the Log File
Note: This procedure requires that the Recovery Model is set to “Full” on the Database
Properties > Options page.
1. In the Object Explorer pane of SQL Server Management Studio, right-click on the
ACCESSCONTROL database, and then select Tasks > Shrink > Files.
2. The Shrink File window is displayed.
a. In the File type drop-down, select “Log.”
b. Select the Release unused space radio button.
c. Click [OK].
3. Repeat steps 1 and 2 for the ACCESSCONTROL_ARCHIVAL database.
• WARNING! • Now that SQL Server is configured on the Secondary Server, make sure your
next step is to install OnGuard on the Secondary Server. For more information,
refer to Install OnGuard on the NEC Server on page 89.
CHAPTER 6 Install OnGuard on the NEC Server
This section takes you through the installation process for the OnGuard software. Read all of the
instructions carefully, and then proceed in the order presented.
Overview
IMPORTANT: The OnGuard software and OnGuard license must be installed on the Primary
Server and Secondary Server.
To install OnGuard, perform the following instructions:
1. Before you install OnGuard, you must install the third-party requirements from the Supplemental
Materials media onto the active server. Windows service packs are also required but are not
provided on the Supplemental Materials media. Refer to the Third Party Compatibility Chart on
the LenelS2 Web site to determine which service packs are required for your operating system.
Adobe Reader is not required but highly recommended as you need it to read the OnGuard
documentation.
2. Complete steps 1 and 2 in “OnGuard 7.6 Installation Prerequisites” in the Installation Guide.
3. Complete the steps in “Configure a USB Hardware Key” in the Installation Guide but do NOT
“Restart your computer” if prompted to do so.
Install OnGuard on the NEC Server
Install OnGuard
1. Complete the steps in “Install the OnGuard 7.6 Software” in the Installation Guide.
Note: On the System Location Information window, do NOT accept the default locations for
your database and License Server. Instead, enter your <Virtual Computer Name> in the
Provide the location of your License Server and Provide the location of your
database fields.
2. After OnGuard is installed, when prompted, do NOT “Restart your computer.”
3. If Setup Assistant launches, click [Close].
4. Reboot the cluster from Cluster Manager.
5. If you installed OnGuard on the Primary Server:
a. Log into Windows. The Setup Assistant will launch automatically.
b. Cancel the Setup Assistant, and then restart the SQL Server (MSSQLSERVER) service.
c. Manually run the Setup Assistant.
6. If you installed OnGuard on the Secondary Server:
a. On the Primary Server, log into Windows, and then failover to the Secondary Server.
b. On the Secondary Server, log into Windows. The Setup Assistant will launch automatically.
c. Cancel the Setup Assistant, and then restart the SQL Server (MSSQLSERVER) service.
Click [Yes] to confirm, and then click [Close].
d. Manually run the Setup Assistant.
7. If you selected the Application Server as a custom installation, then configure its settings. For
more information, refer to Configure the Application Server on page 93. Do NOT run Form
Translator.
8. If using Integrated Security = SSPI (an application.config setting), you must complete the
“Configure Windows Authentication with SQL Server” steps in the Installation Guide.
9. Depending on the components you chose to install, you may need to restart the cluster. If you are
prompted to do so, use the Cluster Manager to reboot the cluster.
10. After SQL Server and OnGuard are installed, stop their services and set them to “Manual”
startup. SQL Server service names generally begin with “SQL Server.” OnGuard service names
begin with “LS”, “Lps”, or “Lnr.”
11. If you installed OnGuard with Enterprise, 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 91.
12. Run the Lenel Utility for ExpressCluster using the steps in After OnGuard Setup on page 38.
13. If you installed OnGuard on the Primary Server, failover to the Secondary Server, and then set up
the OnGuard environment on the Secondary Server. For more information, refer to Set Up the
OnGuard Environment on the Secondary Server on page 82.
14. (Optional) If you installed OnGuard on the Secondary Server, and chose to create an archival
database, configure the archival database. For more information, refer to Configure the Archival
Database in OnGuard on page 90.
Configure the Archival Database in OnGuard

If you opted to create an archival database, complete the following steps:
1. Run System Administration.
2. From the Administration menu, select Archives.
Install OnGuard
3. On the Archiving tab:

a. Select the Archive to database check box.
b. Type ACCESSCONTROL_ARCHIVAL.mdf in the Database name field.
c. Click [OK].
d. Click [Yes] to confirm. The Setup Assistant runs automatically and waits at the Database
Setup (Archival) step.
e. Click [Start] to run Database Setup for the Archive file.
f. When completed, click [Close].
Manually Issue an SSL Certificate

If this is an Enterprise configuration, 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.
In the command prompt, execute the following command:
lnl_app_server_certificate_installer.exe -
key=DRIVE:\\PATH\\TO\\nginxConfFile\\ls_server_cert_key.pem -
cert=DRIVE:\\PATH\\TO\\nginxConfFile\\ls_server_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\.
Install OnGuard on the NEC Server
CHAPTER 7 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 is referenced, use the <Virtual Computer Name> instead.
However, in “Database Authentication for Web Applications (Add the Windows user to SQL
Server)” it specifies to add the server-name\username login to SQL 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 the Virtual Computer Name.
• In the Web Visitor Management AdminApp for the clustered servers, modify the default physical
server name in the SilverlightApplicationConfiguration.xml file in
C:\inetpub\wwwroot\AdminApp\ 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, modify the default physical server name in the
FlexApplicationConfiguration.xml file in C:\inetpub\wwwroot\Lnl.OG.ServicesWebHost\
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, modify the default physical server name
in the serviceModelClient.config.deploy file in C:\inetpub\wwwroot\<ClickOnce
directory>\config 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

IMPORTANT: After you complete the steps in “Confirming the .NET Version with Windows
Server (If using Windows Server 2012 R2)”, configure the host header value.
For OnGuard servers 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
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 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.
• 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 prompt 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.
Configure Host Header Value
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, right-click on Default Web Site, and then select
Edit Bindings.
3. In the Site Bindings dialog, complete the following steps:
a. Click [Add].
b. Modify Type to “https.”
c. Leave IP address set to “All Unassigned.”
d. Type 443 for the Port.
e. Select the appropriate SSL certificate, and then click [OK].
4. Restart IIS.
Configure the Application Server
CHAPTER 8 Script Setup
Stop the Services

Verify the OnGuard and SQL Server services are all stopped on both the Primary and Secondary
Server.
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
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
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
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 media in: High Availability\NEC\ExpressClusterScripts\.
10. If you are prompted to overwrite the file, click [Yes].

11. To enable the services to start up, complete the following steps:
a. Click [Edit] to modify start.bat:
b. In the OnGuard and SQL Server Database Services sections, “un-comment” the lines for the
services which will be starting up on your system by deleting “rem” in each of these
statements.
c. Close the text editor and make sure to save the file.
12. From the Scripts list, select “Stop script” and then click [Replace].
13. Navigate to the scripts folder and select the stop.bat file, and then click [Open]. This file is
located on the Supplemental Materials media in:
High Availability\NEC\ExpressClusterScripts\.
14. If you are prompted to overwrite the file, click [Yes].

15. To enable the services to stop, complete the following steps:
a. Click [Edit] to modify stop.bat:
b. In the OnGuard and SQL Server Database Services sections, “un-comment” the lines for the
services which will need to be stopped on your system by deleting “rem” in each of these
statements.
c. Close the text editor and be sure to save the file.
16. Click [Finish].
Script Setup
17. From the File menu, select Apply the Configuration File.
18. Click [Yes] when prompted to confirm applying changes.
19. Click [OK].
20. Change to Operation Mode.

21. From the Service menu, select Restart Manager.
22. Click [OK] to confirm restarting the manager service.
Script Setup
23. After the cluster finishes refreshing, start the cluster. From the Service menu, select Start Cluster.
24. Click [OK] to confirm starting the cluster.
25. After the cluster starts, the group script should be green indicating that it is started and running
correctly.
26. Move the Failover Group to the other server to verify the services start successfully there as well.
Script Setup
CHAPTER 9 WAN Deployment
different subnet, please contact PES. For more information, refer to Appendix B: WAN
Network Requirements on page 123.
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
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 10 Upgrading 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.
IMPORTANT: 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 Upgrade Guide for a list of processes that must
be completed before beginning an upgrade of 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 Upgrade Guide and, if part of an Enterprise
configuration, the Upgrading to OnGuard 7.6 Enterprise chapter in the Enterprise Setup &
Configuration User Guide have been met.
1. Start Cluster Manager.
Upgrading OnGuard on NEC Systems
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 that all OnGuard services are stopped.
c. 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 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 that the ConnectionString setting in the
application.config file specifies the <Virtual Computer 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 SQL Server to reconcile any differences
from earlier versions to the current software. For more information, refer to “Database
Authentication for Web Applications” in the Installation Guide.
g. If this is part of an Enterprise configuration, 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 91.
h. When the installation of 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 SQL Server 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 that the ConnectionString setting in the
application.config file specifies the <Virtual Computer Name> rather than the <Primary
Server Hostname> for the Data Source. For more information, refer to the Configuration
Editor appendix in the Installation Guide.
d. If using Windows authentication, reconfigure the method used for authenticating with the
database. Examine the authentication settings for SQL Server to reconcile any differences
from earlier versions to the current software.
e. If this is part of an Enterprise configuration, 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 91.
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. Replace the existing start and start script files with the latest versions from the Supplemental
Materials media and re-apply 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 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 the OnGuard applications on the Secondary Server.
h. Failover to the Primary Server:
• Right-click on the <Failover Group>, and then select Move.
• In the Move window, select the Primary Server.
9. Verify you can successfully log onto the OnGuard applications on the Primary Server.
Upgrading OnGuard on NEC Systems
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.
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.
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].
APPENDIX B WAN Network Requirements
Note: Professional Engineering Services (PES) are required for NEC ExpressCluster X R3
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 124
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.
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 124 shows a basic LAN configuration within the same data center that meets this
requirement. Figure 2 on page 124 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 125.
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
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 126.
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.
Index
A N
Add a script resource ...................................... 99 Network requirements .................................. 123
Application Server Network setup ................................................. 26
configuring ............................................. 93
R
C Run database query ........................................ 84
Clean installs ................................................. 111
Configure S
Application Server ................................ 93 Script setup
host header value ................................... 93 add a script resource ............................. 99
Lenel Utility for ExpressCluster ......... 31 stop the group ........................................ 97
Windows settings .................................. 31 stop the services .................................... 97
Create a login ................................................... 83 Set memory usage .................................... 85, 87
Create the Lenel user ...................................... 83 SQL Server
attach the archival database ................. 87
D attach the OnGuard database ............... 86
Disk setup ......................................................... 19 create a login .......................................... 83
create an archival database .................. 85
I create the Lenel user ............................. 83
Install create the OnGuard database ............... 82
OnGuard on a server ............................. 89 install ....................................................... 81
overview ................................................. 89 obtain the SID ........................................ 84
SQL Server ............................................. 81 run a new query ..................................... 84
SQL Server (new installations) set database ownership ......................... 84
create a login ................................ 83 set memory usage ........................... 85, 87
run SQL queries ........................... 84 SSL certificates ............................................... 91
Install a service release on NEC systems . 111
U
L Upgrade OnGuard on NEC systems .......... 111
LAN initial setup overview ........................... 15
Lenel Utility for ExpressCluster .................. 31 W
Login for SQL Server ..................................... 83 WAN deployment overview .......................... 16
WAN network requirements ....................... 123
Windows settings ............................................ 31
Index
Lenel Utility for ExpressCluster ......... 31
Index
LenelS2
1212 Pittsford-Victor Road
Pittsford, New York 14534 USA
Tel 866.788.5095 Fax 585.248.9185
www.lenelS2.com
docfeedback@lenelS2.com

Nec Expresscluster X R3 Lan & Wan With Microsoft SQL Server Installation Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nec Expresscluster X R3 Lan & Wan With Microsoft SQL Server Installation Guide

Uploaded by

Copyright:

Available Formats

7.

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

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

CHAPTER 4 Cluster Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

CHAPTER 5 Install Microsoft SQL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

CHAPTER 6 Install OnGuard on the NEC Server . . . . . . . . . . . . . . . . . . . . . . . . . 89

CHAPTER 7 Configure the Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

CHAPTER 8 Script Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

CHAPTER 9 WAN Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

CHAPTER 10 Upgrading OnGuard on NEC Systems . . . . . . . . . . . . . . . . . . . . . . 111

APPENDIX A Ping Resource Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

APPENDIX B WAN Network Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Conventions Used in this Documentation

Other Referenced User Guides

Java Policy file

Virtual Computer Name

LAN Initial Setup Overview

WAN Deployment Overview

Network Configuration Checklist

Starting Cluster Manager

Rebooting the Cluster

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

6. Format the partition:

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

12. From the Format Partition window:

13. Click [Finish].

Formatted Cluster and Data Partitions

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

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

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

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

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

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

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

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

Registry Vinca • Virtual Computer Name

ACS.INI file File License Server Virtual Computer Name

application.config Database Connection Virtual Computer Name

application.config App Server URI Virtual Computer Name

application.config License Client Host Virtual Computer Name

Browser Favorite Shortcut to ExpressCluster Manager Management Port and

Action What is modified

Disable Loopback • Type: DWORD

Registry Modifications (Continued)

Action What is modified

Back Connection • Type: MULTI-STRING

Disable Strict Name • Type: DWORD

TCP • Type: DWORD

Vinca Setting (used • Type: String

Login Driver Location • Type: String

Login Driver Location • Type: String

Login Driver Location • Type: String

Action What is modified

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

Database Connection • File: %AllUsersProfile%\Lnl\application.config

App Server URI • File: %AllUsersProfile%\Lnl\application.config

License Client Host • File: %AllUsersProfile%\Lnl\application.config