Picture Perfect 4.6 Redundant Edition User Manualpartner.lenel.com/file/casi/pp/460134011A.pdf · System Status Information ... Port configuration for dial-up micros ... Since Picture

Picture Perfect 4.6 Redundant Edition

User Manual

P/N 460134011A • 1 November 2011

Copyright © 2011 UTC Fire & Security. All rights reserved.

This document may not be copied in whole or in part or otherwise reproduced without prior written consent from UTC Fire & Security, except where specifically permitted under US and international copyright law.

Disclaimer The information in this document is subject to change without notice. UTC Fire & Security assumes no responsibility for inaccuracies or omissions and specifically disclaims any liabilities, losses, or risks, personal or otherwise, incurred as a consequence, directly or indirectly, of the use or application of any of the contents of this document. For the latest documentation, contact your local supplier or visit us online at www.utcfireandsecurity.com.

This publication may contain examples of screen captures and reports used in daily opera-tions. Examples may include fictitious names of individuals and companies. Any similarity to names and addresses of actual businesses or persons is entirely coincidental.

Trademarks and patents Picture Perfect is a trademark of UTC Fire & Security.

Other trade names used in this document may be trademarks or registered trademarks of the manufacturers or vendors of the respective products.

Intended use Use this product only for the purpose it was designed for; refer to the data sheet and user documentation for details. For the latest product information, contact your local supplier or visit us online at www.utcfireandsecurity.com.

Software license agreement

The EULA is included on the product DVD.

FCC compliance This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reason-able protection against harmful interference when the equipment is operated in a commer-cial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.

You are cautioned that any changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.

Certification and compliance

2002/96/EC (WEEE directive): Products marked with this symbol cannot be disposed of as unsorted municipal waste in the European Union. For proper recycling, return this product to your local supplier upon the purchase of equivalent new equipment, or dispose of it at designated collection points. For more information see: www.recyclethis.info.

Manufacturer UTC Fire & Security

HQ and regulatory responsibility:

UTC Fire & Security, 9 Farm Springs Road, Farmington, CT 06034-4065, USA

Contact information For contact information see our Web site: www.utcfireandsecurity.com

iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Conventions used in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Safety terms and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Chapter 1. System Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Database Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Alarm Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

PPRS Command Utility (pprscmd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

System Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Failover Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Takeover Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Disable-Failover Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Hardware Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Micro controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Signal splitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Modems and cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2. Installing PPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Installation Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

TCP/IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

How to configure TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Network Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Pre-Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Primary Host installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Backup Host installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Installation of Optional Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Micro Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Port configuration for dial-up micros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Network Micros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 3. Configuration and Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Picture Perfect 4.6 Redundant EditionUser Manual

iv

PPRS Command Line Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Database Synchronization and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Database synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

PPRS database synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Database recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Chapter 4. Failover and Takeover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Failover Event Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Takeover Event Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Disable Failover Event Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Error Conditions and Responses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Dual Primary Host and Dual Backup Host Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Recognizing a Failover/Takeover Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Operator Action for Failover/Takeover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Possible Events on the Primary Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

Possible Events on the Backup Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

Chapter 5. Verifying the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

chkredundant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Verifying Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Verifying Picture Perfect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54

Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Verifying Network Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

File setup of /etc/hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

File Check of .netrc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Verifying Static Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61

Verifying Remote Database Access Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Verifying Table IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62

Verification of Hosts Time Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

chkdbsync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Chapter 6. Removing PPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Removing PPRS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Chapter 7. Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67

General Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

Default onconfig file parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68

PPRS commands to determine the database state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

Monitor the logical log archive process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Complete database recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Failure to recover database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

Cleaning the online.log after pprs is removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

v

PrefaceThis document provides instructions for the software installation, configuration, and operation of the Picture Perfect Redundant System (PPRS) software.

The material in this manual has been prepared for persons responsible for and familiar with the security needs of the customer facility. It is intended for use by system administrators and system operators.

System administrators (responsible for planning system design and implementation) setup, configure, and manage the Picture Perfect Redundant System. Redundant system configuration utilities are accessible only to the Picture Perfect System Administrator (ppadmin user).

System operators perform routine system operation duties in an established Redundant system, after system setup is complete. The Redundant system utility (pprscmd) is used for alarm monitoring and for taking appropriate action when failover occurs.

Read these instructions and all ancillary documentation entirely before installing or operating this product. The most current versions of this and related documentation may be found on our Web site.

Note: A qualified service person, complying with all applicable codes, should perform all required hardware installation.

Conventions used in this document

The following conventions are used in this document:

Safety terms and symbols

These terms may appear in this manual:

Bold Menu items and buttons.

Italic Emphasis of an instruction or point; special terms.

File names, path names, windows, panes, tabs, fields, variables, and other GUI elements.

Titles of books and various documents.

Blue italic Hyperlinks to cross-references, related topics, and URL addresses.

Monospace Text that displays on the computer screen.

Programming or coding sequences.

CAUTION: Cautions identify conditions or practices that may result in damage to the equipment or other property.

WARNING: Warnings identify conditions or practices that could result in equipment damage or serious personal injury.


vi

Related documentation• Picture Perfect 4.6 User Manual• Picture Perfect 4.6 Release Notes • Picture Perfect 4.6 Installation Manual • Picture Perfect 4.6 External Interface User Manual • Picture Perfect 4.6 Interface User Manual • Picture Perfect 4.6 Tables and Fields • Picture Perfect 4.6 Import/Export User Manual • Picture Perfect 4.6 Guard Tours User Manual • Picture Perfect 4.6 Redundant Edition User Manual • Picture Perfect 4.6 Imaging Installation Manual • Universal Badge Format (UBF) for Picture Perfect • Graphics Monitoring and Control User Manual • Credential Designer User Manual • Card Access Report Management Application for Picture Perfect (CARMA)

This chapter provides an overview of a typical redundant system including its operation and configuration.

In this chapter:

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Database Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Alarm Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3PPRS Command Utility (pprscmd) . . . . . . . . . . . . . . . . . . . . . . . . 3System Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Failover Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Takeover Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Disable-Failover Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 1 System Overview


2

IntroductionThe Picture Perfect Redundant System (PPRS) provides a reliable and stable Picture Perfect environment by providing server redundancy. A combination of both software and hardware redundancy detects faults and automatically transfers control to the Backup Host. In the event of failure on the Primary Host, the Backup Host continues the alarm monitoring and access control functions. The transfer of control from the Primary Host to the Backup Host occurs rapidly to ensure that there is almost no loss of data or alarms.

By default, SSH (secure shell) is used for the authentication of information between the two hosts.

Note: Before installing PPRS, ensure the backup directory (file system) is created and is at least 35 GB.

Hardware Requirements• Two identical servers running the same operating system in the same time zone• Two network interface cards for each server• PPRS requires a minimum of 10 MB free space to install the redundant package• One signal splitter for every serially connected micro

HostsA redundant system consists of two servers, each running Picture Perfect and PPRS. The two servers communicate constantly with each other over dual networks. One server is designated as the Primary Host and the second server is designated as the Backup Host.

Note: The two networks must be independent of each other. Contact your network administrator to verify that you have two independent networks between the servers. The networks cannot have a common point of failure, such as sharing a common router.

The Primary Host runs Picture Perfect in an active mode, whereas the Backup Host runs Picture Perfect in a standby mode. In standby mode, Picture Perfect is up and running, but the user interface cannot write to the database nor send data to the microcontrollers. Similarly, Picture Perfect running on the Backup Host does not process data received from the microcontrollers.

Note: Any data entered into the backup Picture Perfect database will be lost! Picture Perfect on the Backup Host can only display database information. Any changes made on the Backup Host will not be saved.

Database SynchronizationIBM’s Informix Dynamic Server provides an enterprise solution called High Availability Data Replication (HDR). This feature is designed to ensure database application availability in the event of either planned downtime or unplanned outages. High Availability Data Replication replicates data changes from a source, or primary database, to a secondary database, thereby maintaining a fault-tolerant replica.

Informix HDR uses storage space and logical logs to ensure the Primary and Backup database servers are synchronized. Logical logs are tables within Informix. Informix's logical log is similar to the transaction logs of other redundant database management systems. The logical log is used to redo, or roll forward, transactions in case of recovery, or an explicit rollback work statement. It also

Chapter 1System Overview

3

stores the before-images of the records that each transaction will change, so it can be used to roll back any transactions that have not committed. It is called a logical log because it contains a log of how the database was changed logically. That is, it contains a record of which rows were changed and how, rather than which physical pages contained those rows. The logical log is composed of three logical log buffers (in shared memory) and several logical logs (on disk).

How HDR works in Picture Perfect 4.6 PPRS

Information that is already committed in the Primary Server or in between cycles is stored in Logical Log buffers that are sent to the Backup database server. Since Picture Perfect performs an auto-commit transaction for every SQL event in the database (Insert, Update or Delete), any modification to records in the Primary Server is sent almost instantaneously to the Backup Server.

Although, in our Picture Perfect environment transactions gets auto-committed, logical logs are also copied to the Backup Server based on a parameter in the database configuration file (default is every 30 seconds).

Alarm MonitorsThe information displayed on the Alarm Monitors of the Primary and Backup Hosts is identical (assuming you selected the same facility sets when logging on). If the Primary Host fails, communication is lost and the session ends; however, the Alarm Monitor on the Backup Host (now the new Primary Host) continues to function and displays current information and incoming alarms. To ensure continuous monitoring of alarms, the operator logs off of the inactive session, and then logs back in to the Backup Host.

PPRS Command Utility (pprscmd)The PPRS Command Utility (pprscmd) is used by the System Administrator to:

• Configure PPRS• Control PPRS• Display the status of PPRS for the primary and Backup Hosts

System Status InformationThe primary and Backup Hosts exchange status information at a user defined interval known as the heartbeat. PPRS on each host generates a status and sends it to the other host. PPRS on each host then examines the status received from the other host. The status information includes:

• The state of the two networks.• The state of critical processes that are essential for the proper operation of Picture Perfect

and PPRS.• The state of Picture Perfect software parameters that indicate the “health” of the internal

operation.


4

Failover OperationFailover occurs when the Primary Host initiates the transfer of control to the Backup Host. If the Primary Host determines that its operating status is faulty, it sends a failover message to the Backup Host, then immediately shuts itself down. When this occurs, a failover alarm appears on the Alarm Monitor. The Backup Host then implements its takeover operation and becomes the Primary Host.

Takeover OperationIf the Backup Host receives a failover message from the Primary Host or if the Primary Host is not responding, the Backup Host initiates the takeover procedure and takes control of PPRS by becoming the Primary Host. During the takeover process, the Picture Perfect application, including the database, is stopped and then restarted. During this time:

• Clients logged into the Backup Host receive a popup message stating that the session has timed out and to retry or log out. You should log out and wait a few minutes before trying to log back in.

• Successful logons are not possible until the application has fully started. When this occurs, a takeover alarm appears on the Alarm Monitor.

• When the application and database are being restarted, no alarms are processed by the application.

• After the application is restarted, allow a few minutes for the controllers to re-establish communication.

Disable-Failover OperationWhen the Primary Host detects a loss of communication with the Backup Host (over both networks), it executes the disable failover procedure which inhibits failover until the communication with the Backup Host is re-established. During this communication outage, the Backup Host takes over and becomes the Primary Host, leaving the system in a dual-primary state. When communication is re-established, the host that became the primary most recently is stopped. Therefore, that server must be manually started as the Backup Host. When this occurs, a disable failover alarm appears on the Alarm Monitor.

If the Backup Host itself is not functioning correctly, the Backup Host disables its takeover capability and sends a status message to notify the Primary Host of the action. Upon receiving the disable failover message, the Primary Host disables its failover option and sends a disable-failover alarm to the Alarm Monitor.

Chapter 1System Overview

5

Hardware OverviewPPRS consists of two hosts (Host1 and Host2) connected by redundant networks. One computer is designated as the Primary Host and the other as the Backup Host. Both the primary and Backup Hosts have a copy of the database. See Figure 1, PPRS Architecture (without Modems) on page 6 and Figure 2, PPRS Architecture (with Modems) on page 6.

Networks

The two networks provide a redundant link between the two hosts. Each network connects to both hosts. Network micros may be connected to either network (See Network Micros on page 27). The networks are used to exchange status information and data between the primary and Backup Hosts.

Workstations

The workstations provide the Picture Perfect Redundant System (PPRS) user interface.

Micro controller

Each micro controller must be configured with the IP addresses of the Primary and Backup Servers. Configure the IP addresses in the parameter control block for PXN controllers and use the Integrated Configuration Tool for PXNPlus and DirecDoor controllers.

Signal splitter

One signal splitter is required for each serially connected micro. The signal splitter provides a communications link to and from a micro to both hosts. The Backup Host ignores the signals until a failover occurs. After failover, when the backup becomes the new Primary Host, the communications link is already in place and host-to-micro communication is undisturbed.

Modems and cables

Short-haul modems are required between the signal splitter and the micro if the distance between those two points is greater than 100 feet.

Check with your UTC Fire & Security sales representative to be sure you are using the proper types for your setup.


6

Figure 1. PPRS Architecture (without Modems)

Figure 2. PPRS Architecture (with Modems)

Signal Splitter

Host1 Host2Micro/5

Network 1

Network 2

Micro/5 PXN

Micro/5 PXN

WorkstationWorkstation

(10.41.200.100)(ws1) (ws2)

(10.41.222.100)

(primary) (backup)

(10.41.222.57)

(10.41.200.58)(10.41.200.57) (eth0)

(eth1) (10.41.222.58)

Modem(if required by distance)

Micro/5 PXN

Host1

(primary)

Workstation

(10.41.200.100)(ws1)

Workstation(ws2)

(10.41.222.100)

Network 1

Network 2

(eth0)

(eth1)

Signal Splitter

Micro/5

Host2(backup)

(10.41.200.58)

(10.41.222.58)(10.41.222.57)

(10.41.200.57)

Micro/5 PXN

This chapter includes information needed to successfully install the Picture Perfect PPRS package.

In this chapter:

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Installation Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8TCP/IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Network Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Pre-Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . .11Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Installation of Optional Packages . . . . . . . . . . . . . . . . . . . . . . . . 24Micro Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 2 Installing PPRS


8

OverviewThis chapter provides the system administrator with installation instructions for the Picture Perfect Redundant System software.

You can install the PPRS package as an add-on package to an existing installation, or you can install PPRS on a new (or upgraded) installation.

ConventionsThe operating system assigns a name to each network interface. Two Ethernet interfaces are assigned, for example, eth0 and eth1.

Installation TerminologyHost

One of the two hosts or servers used in the redundant environment.

Host Name

The first of two names assigned to each host, such as bctottawa and bctwunan. The second name is associated with the second network adapter (two per host, one for each network), such as bctottawa2 and bctwunan2.

Notes:

• Use lowercase a through z, and/or numerics 0 through 9.

• Use the simple machine name such as pphost1, not the fully qualified name.

• The host name may not be more than 16 characters in length.

• Do not use host names containing the dash character (-). This is not a valid character in the Informix Dynamic Server and prevents the database from starting.

• Do not use host names containing the underscore character (_). This is not a valid character in the web server running on the Picture Perfect host.

Primary Host

The host which runs the active version of Picture Perfect and through which all updates are made.

Backup Host

The host which runs a duplicate version of Picture Perfect and becomes active only if the Primary Host fails.

Local Host

The host on which you are currently working. It can be either the Primary Host or the Backup Host, depending on your location.

Remote Host

The host on which you are not working, but which is connected to the local host through the network. It can be either the Primary Host or the Backup Host, depending on your current location.

IP Address

The multi-digit number, such as 10.41.200.57, which defines a unique location within a network. Each host needs an IP address for both of its host names.

Chapter 2Installing PPRS

9

TCP/IP ConfigurationSee your network administrator for IP addresses for the following items on both networks:

• Primary Host (two IP addresses)• Backup Host (two IP addresses)

Before you configure TCP/IP, map out the IP addresses for each network.

How to configure TCP/IP• First configure TCP/IP on the Primary Host. • Then repeat the process on the Backup Host.

AIX

To configure TCP/IP on an AIX host, use the SMIT TCP/IP menu:

Note: To move your cursor to the next data entry field on a form, press an up/down arrow key.

1. Type the following command at the system prompt in an AIX window: smit tcpip

2. The TCP/IP menu opens. Select Minimum Configuration & Startup and press .

The Available Network Interfaces window displays.

3. Select the network interface card, for example en0 or en1, and press .

The Minimum Configuration & Startup menu displays.

4. Type the host name. (The host name is the same for en0 and en1.)

5. Type the IP address. Provide IP addresses for the network interfaces used for PPRS, for example:

10.41.200.57 for en010.41.222.57 for en1

6. To start the selected network driver (en0 or en1), set the Start Now field on the Minimum Configuration & Startup screen to yes (type yes or press , then press .

7. Repeat steps 3 through 6 to configure each network driver.

8. Because both hosts are configured with the same name, as indicated in step 4, you need to edit the /etc/hosts file to change the host name for the second network card’s IP address. For example, if the host name for 10.41.200.57 and 10.41.222.57 is bctottawa, change the host name for 10.41.222.57 to bctottawa2.

Table 1. Network map

Network Interface Host1 DomainIP Address Host2 Domain IP Address

Network 1 eth0 10.41.200.57 10.41.200.58

Network 2 eth1 10.41.222.57 10.41.222.58

Enter

Enter

Enter

Tab Enter


10

Linux

To configure TCP/IP on a Linux host:

Note: The following steps edit the contents of the /etc/hosts file. We recommend that you make a backup copy of the file before performing these steps.

1. Log on to the system as the root user.

2. Click System, Administration, and then Network.

The Network Configuration window displays.

3. Select a network device, for example eth0 or eth1, then click Edit.

The Ethernet Device window displays.

4. Check Activate device when computer starts.

5. It is recommended that DHCP be disabled and a static IP address used. You need to supply the static IP address, Subnet mask, and Default Gateway address.

Note: If you intend to enable DHCP, make sure the host IP address remains static and is tied to the MAC address of the network card. Check with your IT department for DHCP configuration information.

6. When you have completed these changes, click Ok.

You are returned to the Network Configuration window.

7. Click Activate.

8. When prompted to save your changes, click Yes.

9. When your changes have been saved, click Ok to close this window.

a. Once the device is activated, you are returned to the Network Configuration window.

b. Repeat step 3 through step 9 for each network device.

10. Close the window.

Network CablingBefore you connect the network cable to a network interface, you need to determine the network board that is configured to each specific network interface (eth0 or eth1).


11

Pre-Installation RequirementsBefore you begin the installation of PPRS, make sure both hosts meet the following requirements:

• Both hosts in a redundant system must have identical operating system settings (files system sizes/names, and packages).

• The database backup directory selected during base package installation (default /ppbackup) should be sized large enough to accommodate your database backups and database log files. The recommended minimum size is 35 GB.

• The database sizes selected during the base installation on both hosts must match. If the database sizes do not match, the PPRS installation will fail.

The following software package is installed on both hosts:

• Picture Perfect base package

Notes: The settings selected at installation for the Primary Server are used for both hosts. Both servers must be configured for the same time zone. Two network adaptors are installed on each host.

• Each host has a hostname and an IP address for each of its two network adaptors, and they can ping each other by hostname and IP address.

• Port numbers are selected that are greater than 9000 and not already in use (check the /etc/services file for port numbers already in use).

Note: Make sure the primary port numbers and the backup port numbers on both hosts match, otherwise there is no communication between the two hosts.

Optional packages, such as image, graph, and tours, can be installed on a redundant system after the pprs package has been installed. See Installation of Optional Packages on page 24.

Installation ProceduresPrimary Host installation

Decide which host will be the Primary Host. Follow these steps to install PPRS on the Primary Host. To perform the installation for the Backup Host, refer to Backup Host installation on page 17.

PPRS requires two (2) network interface cards to be installed on each host and configured; that is, they have been defined and configured with the network IP addresses that will be used for the redundant system.

If this is not done:

• The Informix database will be unable to start. • After PPRS is installed, it will be impossible to install any other packages, or to start PPRS.

To install the software:

1. Log on as ppadmin and open a terminal window.

2. Type the following to shut down Picture Perfect:

. /cas/bin/profile rc.pperf -k

Enter

Enter


12

3. Switch users to root by typing the following command.

su -

Enter your root password, and then press .

4. Insert the Picture Perfect v4.6 Installation DVD into your server. Wait for the DVD ROM LED to stop blinking before proceeding.

Linux

Unmount the DVD by typing the following command:

umount /media/pp46

Mount the DVD by typing the following command:

mount /dev/dvd /media

AIX


mount -v cdrfs -r /dev/cd0 /mnt

5. Change to the root directory by typing cd / .

6. To display a list of installation options, type:

Linux

/media/Linux/INSTALL -o

AIX

/mnt/AIX/INSTALL -o

Messages similar to those shown below display, followed by a list of packages:

-------------------------------------------------------------------- Picture Perfect CD-ROM Installation - 4.6 04/10/11 Copyright (C) 2011 UTC Fire & Security Americas Corporation, Inc.--------------------------------------------------------------------The following BASE OPTIONS product(s) are available:Prod# Name and Descriptions----- ---------------------0 base Picture Perfect Base package1 graph Picture Perfect Graphics Monitoring and Control package2 image Picture Perfect Imaging package3 impexp Picture Perfect Import/Export package4 netlan Picture Perfect Network System - Host package5 pprs Picture Perfect Redundant System package6 subhost Picture Perfect Network System - Subhost package7 tours Picture Perfect Guard Tours packageEnter product number(s), separated by ',' to select, 'q' to quit:

7. Type the corresponding product number, for example 5, to install the Picture Perfect Redundant System (pprs) package, and then press .

Enter

Enter

Enter

Enter

Enter

Enter

Enter

Enter

Enter


13

Your package selection is now displayed, and you are asked to confirm it:

You have selected the following product(s):5 pprs Picture Perfect Redundant System packageIs this correct (y/n)? [y]

8. To make a different selection, type n, and you are returned to step 7 where you are prompted again for your selection.

To continue the installation, type y

The installation begins and messages similar to the following display:

Installing pprs...Picture Perfect Multi-package Installation - 4.6 04/10/11Copyright (C) 2011 UTC Fire & Security Americas Corporation, Inc.Installing from image in /media/Linux/pp...Do you want to install the Picture Perfect PPRS Package (y/n)? [y]

9. To confirm, type y

Messages similar to the following display:

Picture Perfect NLS Text Save - 4.6 04/10/11Copyright (C) 2011 UTC Fire & Security Americas Corporation, Inc.Mon Mar 09 10:54:40 EDT 2011This package has no nls or help files to save...Picture Perfect PPRS Installation - Version 4.6 04/10/11Copyright (C) 2011 UTC Fire & Security Americas Corporation, Inc.Loading Picture Perfect Redundant System Package...Extracting files from media...The files have been read from the media.Redundant Picture Perfect remote connectivity configurationWill [bctottawa] be the Primary Machine (y/n)?..... [y]

10. Make sure to type y , as this server will be the Primary Host.

You are asked to confirm your answer.

Are You Sure (y/n)? [y]

11. Type y if the previous response is correct.

You are prompted for the name of the second interface to be used by Picture Perfect redundancy.

Please enter Second PRIMARY (LOCAL) System Name:

CAUTION: Only one host should be designated as the Primary Host.

Enter

Enter

Enter

Enter


14

12. Enter the second name of the Primary Host (for example, bctottawa2), and press .

You are asked for the IP address of the second network interface.

Enter its IP Address: [10.41.222.57]

13. If the IP address displayed is the correct IP address for the second network interface, accept it by pressing , or enter the IP address of the second network interface, and press .


Name of Second PRIMARY (LOCAL) host is ......: bctottawa2IP address of Second PRIMARY (LOCAL) host is ...: 10.41.222.57Is the name and IP address correct (y/n)? [y]

14. If the name and IP address are correct, type y

You are prompted for the name of the Backup Host.

Please enter First BACKUP (REMOTE) System Name:

To enter the name of the Backup Host:

1. Type the name of the Backup Host (such as bctwunan), and press .

You are prompted for the IP address of the Backup Host.


2. If the IP address displayed is the correct IP address for the backup, accept it by pressing , or enter the IP address of the Backup Host, and press .


Name of first BACKUP (REMOTE) host is ......: bctwunanIP address of first BACKUP (REMOTE) host is ...: 10.41.200.58Is the name and IP address correct (y/n)? [y]


An entry is added to your /etc/services file for the port used by Informix to communicate with the database of the Backup Host. You are prompted for the second name of the Backup Host.

Adding the following entry to /etc/services: bctwunan_star 9088/tcp #Informix REMOTEDB Portbctwunan_e_star 9089/tcp #Informix REMOTEDB Encrypted PortPlease enter Second BACKUP (REMOTE) System Name:

4. Enter the second name of the Backup Host (such as bctwunan2), and press .

You are prompted for the IP address of the second network interface of the Backup Host.

Enter its IP address: [10.41.222.58]

Enter

Enter Enter

Enter

Enter

Enter Enter

Enter

Enter


15

5. If the IP address displayed is the correct IP address for the second network interface of the Backup Host, accept it by pressing , or enter the IP address of the second network

interface of the Backup Host, and press .


Name of Second BACKUP (REMOTE) host is ......: bctwunan2IP address of Second BACKUP (REMOTE) host is ...: 10.41.222.58Is the name and IP address correct (y/n)? [y]


Messages are displayed indicating the Informix sqlhosts and onconfig files are being updated with the information provided, as well as the Picture Perfect system configuration table.

Ensuring Primary and Backup in the same timezone...Starting the Informix database..DoneUpdating /cas/db/etc/sqlhosts file.. REMOTE DB PORT IS bctwunan_starUpdating /cas/db/etc/onconfig file.. Create archive and Logical log file...

If your /ppbackup disk space is too small, the following messages display:

Available Disk Space at /ppbackup is too small (5952 M)UTC Fire & Security recommend that you have at least 15G Free Space!Please increase available disk space so that database replication will run properly!Are You going to increase the size later (y/n)? .......: [y]

Press to increase the backup disk space later.

7. You are then prompted for the port numbers used by Picture Perfect on the Primary Host to communicate with Picture Perfect on the Backup Host. Each port number must be four or more digits long, greater than 9000, and not already in use (the installation script checks the/etc/services file to ensure that existing port numbers are not used).


Enter PRIMARY [bctottawa] Local PORT Number (i.e. 9003): [9003]Enter BACKUP [bctwunan] Remote PORT Number (i.e. 9004): [9004]

To check if the specified ports are correct:

1. Press to accept the displayed port, or type the port of your choice, and press .


PRIMARY [bctottawa] Local PORT Number: [9003] BACKUP [bctwunan] Remote PORT Number: [9004] Are these ports correct (y/n)? [y]

Enter

Enter

Enter

Enter

Enter Enter


16

2. If the ports are correct, type y

An entry is added to your /etc/services file for the ports and other updates performed to the Picture Perfect database.

Setting Ports...Please WaitBuilding .mwmrc and dtwmrc resource files..Adding alternate-servers in /usr/lib/X11/fs/config...Adding FPP Alarms/Input_groups to SystemDeleting pre-existing FPP input_groups and alarms - if any!!Creating PPRS Sweeper Failure alarm record.Creating PPRS Sweeper Failure input group record.Creating PPRS FAILOVER alarm record.Creating PPRS FAILOVER input group record.Creating PPRS TAKEOVER alarm record.Creating PPRS TAKEOVER input group record.Creating PPRS DISABLE FAILOVER alarm record.Creating PPRS DISABLE FAILOVER input group record.Loading DB Task....[Done.]Perform Informix archive...[OK]Change database to PRIMARY mode...[OK]Setting up ntp Server to keep the hosts time in sync..

3. The installation is now complete. Messages similar to the following display.

Note: If you did not have a successful PPRS installation, do not press . Instead contact your UTC Fire &

Security Technical Support representative for additional instructions.

The ‘PPRS.INST’ installation has completed successfully.**********************************************************************************NOTE******************************************************************************************* ****** Redundant Picture Perfect does NOT start ****** automatically when the system is rebooted!! ****** ************************************************************************************END NOTE*************************************************************************************Checking if need to update nls files...Picture Perfect NLS Check - 4.6 01/16/11Copyright (C) 2011 UTC Fire & Security Americas Corporation, Inc.Mon Mar 09 13:40:45 EDT 2011No nls files for pprs packageRunning /cas/bin/fixperm on /tmp/pprs.perm file...No errors detected/cas/bin/fixperm finished.Installing desire BASE_OPTIONS product(s) was successful.INFO: Updating Red Hat patches was successful!The INSTALLation has completed.The system needs to be rebooted for the changes to take effect.Reboot the system (y/n)? [y]

4. Press (defaults to y) to reboot the system. Remember to remove the installation DVD after the reboot is complete.

Enter

Enter

Enter


17

Backup Host installation

Decide which host will be the Backup Host. Follow these steps to install PPRS on the Backup Host. To perform the installation for the Primary Host, refer to Primary Host installation on page 11.

PPRS requires two (2) network interface cards to be installed on each host and configured; that is, they have been defined and configured with the network IP addresses that will be used for the redundant system.

If this is not done:

• The Informix database will be unable to start. • After PPRS is installed, it will be impossible to install any other packages, or to start PPRS.

To install the software:

Prerequisite: The Primary Host must already have the PPRS package installed and the system reboot completed.

1. Log on as ppadmin and open a terminal window.

2. Type the following to shut down Picture Perfect:

. /cas/bin/profile rc.pperf -k


su -


4. Insert the Picture Perfect 4.6 Installation DVD into your server. Wait for the DVD ROM LED to stop blinking before proceeding.

Linux

Unmount the DVD by typing the following command:

umount /media/pp46


mount /dev/dvd /media

AIX


mount -v cdrfs -r /dev/cd0 /mnt

5. Change to the root directory by typing cd / .

6. To display a list of installation options, type:

Linux

/media/Linux/INSTALL -o

AIX

/mnt/AIX/INSTALL -o

Enter

Enter

Enter

Enter

Enter

Enter

Enter

Enter

Enter

Enter


18

Messages similar to those shown below display, followed by a list of packages:

------------------------------------------------------------------- Picture Perfect CD-ROM Installation - 4.6 04/10/11 Copyright (C) 2011 UTC Fire & Security Americas Corporation, Inc.--------------------------------------------------------------------The following BASE OPTIONS product(s) are available:Prod# Name and Descriptions----- ---------------------0 base Picture Perfect Base package1 graph Picture Perfect Graphics Monitoring and Control package2 image Picture Perfect Imaging package3 impexp Picture Perfect Import/Export package4 netlan Picture Perfect Network System - Host package5 pprs Picture Perfect Redundant System package6 subhost Picture Perfect Network System - Subhost package7 tours Picture Perfect Guard Tours packageEnter product number(s), separated by ',' to select, 'q' to quit: 5

7. Type the corresponding product number, for example 5, to install the Picture Perfect Redundant System (pprs) package and press .

Your package selection is now displayed, and you are asked to confirm it:

You have selected the following product(s):5 pprs Picture Perfect Redundant System packageIs this correct (y/n)? [y]

8. To make a different selection, type n, and you are returned to step 7 where you are prompted for your selection. To continue the installation, type y

The installation begins, and messages similar to the following display:

Installing pprs...Picture Perfect Multi-package Installation - 4.6 04/10/11Copyright (C) 2011 UTC Fire & Security Americas Corporation, Inc.Installing from image in /media/Linux/pp ...Do you want to install the Picture Perfect PPRS Package (y/n)? [y]

9. To confirm, type y


Picture Perfect NLS Text Save - 4.6 01/16/11Copyright (C) 2011 UTC Fire & Security Americas Corporation, Inc.Wed Aug 12 14:25:45 EDT 2011This package has no nls or help files to save...-------------------------------------------------------------------- Picture Perfect PPRS Installation - Version 4.6 04/10/11 Copyright (C) 2011 UTC Fire & Security Americas Corporation, Inc.--------------------------------------------------------------------Loading Picture Perfect Redundant System Package...

Enter

Enter

Enter


19

Extracting files from media...The files have been read from the media.Redundant Picture Perfect remote connectivity configuration...Will [bctwunan] be the Primary Machine (y/n)? ........: [y]

10. Make sure to type n, and press , as this host will be the Backup Host.


Are You Sure (y/n)? [y]

11. If the previous response is correct, type y

You are prompted for the name of the second interface to be used by Picture Perfect redundancy.

Please enter Second BACKUP (LOCAL) System Name:

12. Enter the second name of the Backup Host (such as bctwunan2), and press .

You are prompted for the IP address of the second network interface.


13. If the IP address displayed is the correct IP address for the second network interface, accept it by pressing , or enter the IP address of the second network interface, and press .


Name of Second BACKUP (LOCAL) host is ......: bctwunan2IP address of Second BACKUP (LOCAL) host is ...: 10.41.222.58Is the name and IP address correct (y/n)? [y]


You are prompted for the name of the Primary Host.

Please enter First PRIMARY (REMOTE) System Name:

To enter the name of the Primary Host:

1. Type the name of the Primary Host (such as bctottawa), and then press .

You are prompted for the IP address of the Primary Host.


CAUTION: Only one host should be designated as the Primary Host.

Enter

Enter

Enter

Enter Enter

Enter

Enter


20

2. If the IP address displayed is the correct IP address for the Primary Host, accept it by pressing , or enter the IP address of the Primary Host and press .


Name of first PRIMARY (REMOTE) host is ......: bctottawaIP address of first PRIMARY (REMOTE) host is ...: 10.41.200.57Is the name and IP address correct (y/n)? [y]


The SSH for the Remote Server is set up and a message similar to the following displays:

Setting SSH for Remote Server...NOTE: Secure Shell functionality can be enabled by executing the \)confgi_ssh <remote_server>' script on backup server then run: \)touch /cas/.ssh_configured'on backup server.Starting Secure Shell (SSH) configuration...Generating RSA key, Enter 'y' for any overwrite prompts:Please keep the default file location when asked:Generating public/private rsa key pair.Your identification has been saved in /root/.ssh/id_rsa.Your public key has been saved in /root/.ssh/id_rsa.pub.The key fingerprint is:62:b3:6e:c6:50:0e:1c:cd:c5:44:07:75:6c:1d:f9:fe root@bctwunanTransferring public key to remote host bctottawaKey in 'yes' for 'continue connecting' promptsEnter root password for bctottawa, when asked for it.The authenticity of host 'bctottawa (10.41.200.57)' can't be established.RSA key fingerprint is 59:12:c9:57:88:1a:13:6c:8e:a5:7f:4b:8b:0b:79:95.Are you sure you want to continue connecting (yes/no)?

4. You are asked if you want to continue connecting. Type yes, and then press .

root@bctottawa's password:

You are prompted for the Primary Server root password. Type the password, and then press .

Enabling public key on remote host bctottawaEnter root password for bctottawa, when asked for it.root@bctottawa's password:

5. You are prompted for the Primary Server root password again. Type the password, and then press .

Secure Shell (SSH) has been configured successfullyNOTE: Please run ". /cas/bin/profile" after installation has completed. Make sure you do this before running any commands.Press enter to continue...

Enter Enter

Enter

Enter

Enter

Enter


21

6. Press to continue. A message similar to the following displays:

An entry is added to your /etc/services file for the port used by Informix to communicate with the database of the Primary Host, and you are prompted for the second name of the Primary Host.

We are trying to copy .netrc file to primaryscp /tmp/netrc bctottawa:/root/.netrcscp /tmp/netrc bctottawa:/cas/db/.netrcscp /tmp/netrc bctottawa:/cas/.netrcAdding Remote Server to Services file to [PRIMARY]...Informix ports for remote host 'bctottawa', are [9088] and [9089]Adding the following entries to /etc/services: bctottawa_star 9088/tcp #Informix REMOTEDB Port bctottawa_e_star 9089/tcp #Informix REMOTEDB Encrypted PortPlease enter second PRIMARY (REMOTE) System Name .....:

7. Enter the second name of the Primary Host (such as bctottawa2), and press .

You are prompted for the IP address of the second network interface of the Primary Host.

Enter its IP address: [10.41.222.57]

8. If the IP address displayed is the correct IP address for the second network interface of the Primary Host, accept it by pressing , or enter the IP address of the second network

interface of the Primary Host and press .


Name of Second PRIMARY (REMOTE) host is ......: bctottawa2IP address of Second PRIMARY (REMOTE) host is ...: 10.41.222.57Is the name and IP address correct (y/n)? [y]


Messages are displayed indicating the Informix sqlhosts and onconfig files are updated with the information provided, as well as the Picture Perfect system configuration table.

Is the name and address correct (y/n)? ...............: [y]Ensuring Primary and Backup in the same timezone...Primary machine's timezone is [EDT]Backup machine's timezone is [EDT]Backup machine has same timezone as Primary. Proceeding...shared memory not initialized for INFORMIXSERVER 'bctwunan'Checking whether the primary database is running...Starting the Informix database.. DoneUpdating /cas/db/etc/sqlhosts file...REMOTE DB PORT IS bctottawa_starUpdating /cas/db/etc/onconfig file...

Enter

Enter

Enter

Enter

Enter


22

Create archive and Logical log file...

If your /ppbackup disk space is too small, the following messages display:

Available Disk Space at /ppbackup is too small (7750 M)UTC Fire & Security recommend that you have at least 15G Free Space!Please increase available disk space so that database replication will run properly!Are You going to increase the size later(y/n)? .......: [y]

Press to increase the backup disk space later.

10. You are then be prompted for the port numbers used by Picture Perfect on the Backup Host to communicate with Picture Perfect on the Primary Host. Each port number MUST be four or more digits long, greater than 9000, and not already in use (the installation script checks the /etc/services file to ensure that existing port numbers are not used).


Enter BACKUP [bctwunan] Local PORT Number(i.e. 9004) ..........................................: [9004]Enter PRIMARY [bctottawa] Remote PORT Number(i.e. 9003) ..........................................: [9003]

To check if specified ports are correct:

1. Press to accept it, or type the port of your choice, and press .


BACKUP [bctwunan] Local PORT Number ..................: 9004PRIMARY [bctottawa] Remote PORT Number ...............: 9003Are these ports correct (y/n)? .......................: [y]

2. If the ports are correct, type y

An entry is added to your /etc/services file for the ports and other updates performed to the Picture Perfect database.

Setting Ports...Please WaitBuilding .mwmrc and dtwmrc resource files...Adding alternate-servers in /usr/lib/X11/fs/config...Adding FPP Alarms/Input_groups to SystemDeleting pre-existing FPP input_groups and alarms - if any!!Creating PPRS Sweeper Failure alarm record.Creating PPRS Sweeper Failure input group record.Creating PPRS FAILOVER alarm record.Creating PPRS FAILOVER input group record.Creating PPRS TAKEOVER alarm record.Creating PPRS TAKEOVER input group record.Creating PPRS DISABLE FAILOVER alarm record.Creating PPRS DISABLE FAILOVER input group record.Loading DB Task... [Done.]Checking PRIMARY and SECONDARY database sizes...The PRIMARY and SECONDARY database sizes match.Performing archive on the PRIMARY server...

Enter

Enter Enter

Enter


23

Please mount tape 1 on /ppbackup/db/ifxDBArch and press Return to continue ... 100 percent done.Please label this tape as number 1 in the arc tape sequence.This tape contains the following logical logs: 20Program over.[OK]Transferring archive file from remote server...ifxDBArch 100% 33MB 16.4MB/s 00:02[OK]Restoring archive file... [OK]Changing database to SECONDARY mode of [bctottawa]... [OK]Checking database synchronization.............[OK]Stopping[OK]Setting up ntp client to keep the hosts time in sync...The 'PPRS.INST' installation has completed successfully.***************************************************************************** N O T E ********************************************************************************* ****** Redundant Picture Perfect does NOT start ****** automatically when the system is rebooted!! ****** **************************************************************************** E N D N O T E *************************************************************************Checking if need to update nls files...Picture Perfect NLS Check - 4.6 01/16/11Copyright (C) 2011 UTC Fire & Security Americas Corporation, Inc.Wed Aug 12 14:18:45 EDT 2011No nls files for pprs packageRunning /cas/bin/fixperm on /tmp/pprs.perm file...No errors detected/cas/bin/fixperm finished.Installing desired BASE_OPTIONS product(s) was successful.

Note: If you did not have a successful PPRS installation, do not press . Instead, contact your UTC Fire &

Security Customer Support representative for additional instructions.

The INSTALLation has completed.The system needs to be rebooted for the changes to take effect.Reboot the system (y/n)? [y]

3. Press (defaults to y) to reboot the system. Remember to remove the installation DVD after the reboot is complete.

Note: In a redundant system, interface (Alarm, CCTV, Firepanel, and Intercom) packages are installed onto the Primary Host and then copied automatically from the primary to the Backup Host. Therefore, before installing these packages, both hosts must be a fully operational redundant system and a recovery must be performed to synchronize the two databases.

4. To verify your configuration, if problems are encountered, please refer to Chapter 5 Verifying the Configuration for troubleshooting details.

Enter

Enter


24

5. After installation has completed, run the following command before running any other commands.

. /cas/bin/profile

Note: The database recovery process updates all Picture Perfect database tables.

Installation of Optional PackagesPicture Perfect optional packages, such as image, graph, and tours, can be installed on a redundant system after the pprs package has been installed.

To install other optional packages after installing pprs:

1. Stop PPRS on the backup host and then on the primary host.

2. Install the optional package(s) on the primary host.

Refer to the Picture Perfect Installation Manual, section “Installing optional packages and interfaces”, for detailed instructions.

3. When prompted, reboot the primary host.

4. After the primary host has started, install the same optional package(s) on the backup host.

5. When prompted, reboot the backup host.

6. Start PPRS on the primary host and then on the backup host.

Micro Configuration

Port configuration for dial-up micros

In a PPRS environment, dial-up micros can be configured in one of two ways. The configuration used depends upon the location of the primary and secondary hosts.

• If the distance between the hosts is relatively short, then a single modem can be connected to a signal splitter. See Figure 3 below.

• If the distance between the hosts is too great to use a signal splitter, then two modems need to be used with one modem directly connected to each host. See Figure 4 on the following page.


25

Figure 3. Single Modem Configuration

Figure 4. Double Modem Configuration

The double modem configuration also requires a unique setup, both from a physical connection and a software standpoint, because the database is replicated on both hosts. The port table, which is one of the tables replicated, contains the fields which define a tty line, phone number, and type of modem connected. As you can see from Figure 4, the two modems connected to the hosts require two different phone numbers. This requires the Ports form to configure two sets of phone numbers. One number is for the Primary Host and the second phone number is for the Backup Host. See Figure 5 for an example of a Linux host double modem configuration.

Host2Host1

Micro

Network I

Network II

Splitter

Modem

Modem

Micro

Host2Host1

Network I

Network II

Modem Modem

Modem


26

Figure 5. Double Modem Host Configuration

In addition, three new fields appear on the Ports form: Double Modem, Primary Phone, and Backup Phone (Figure 6 shows these fields and their descriptions follow.)

Figure 6. Ports Form

Table 2. Double Modem Host Configuration

Field Description

Double Modem (Redundant Only)

This toggle button is visible only in a Picture Perfect Redundant System. It should be set only if the primary and Backup Hosts are separated by distances which require a different phone number for the modem connected to the TTY. This toggle button should not be set if your modem is connected to a splitter.

If this toggle button is set, then the Phone field is disabled. If this toggle button is not set, then the Primary Phone and Backup Phone fields are disabled.


27

Network Micros

When using a network micro in a redundant environment, although the host is connected to two network lines, a micro must be connected to only one of the network lines, not both. Refer to the figure below where Host 1 and Host 2 are both connected to Network I and Network II. Micro 1 is connected only to Network I and Micro 2 is connected only to Network II.

Figure 7. Network Micro Configuration

Primary Phone (Redundant Only)

With dial-up micros in a double modem configuration on a Redundant System, this is the dial-in line phone number for the TTY on the host which was installed as Primary. This field can be accessed only if the Double Modem toggle is set.

Backup Phone (Redundant Only)

With dial-up micros in a double modem configuration on a Redundant System, this is the dial-in line phone number for the TTY on the host which was installed as Backup. This field can be accessed only if the Double Modem toggle is set.

Table 2. Double Modem Host Configuration

Field Description


28

This chapter describes how to begin using your redundant system.

In this chapter:

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Initial Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30PPRS Command Line Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Database Synchronization and Recovery. . . . . . . . . . . . . . . . . . 39

Chapter 3 Configuration and Operation


30

OverviewA Picture Perfect redundant system consists of two hosts with PPRS configured and invoked on both hosts.

It is recommended that a Manual Failover test be performed once or twice a year to ensure that the Backup Server is operational and that all micros are properly configured to communicate to the Backup Server. See Manual failover control on page 35 for an detailed explanation of Manual Failover.

This chapter discusses:

• Initial setup• The PPRS command line utility• Database synchronization and recovery• Micro configuration

Initial SetupPPRS consists of two hosts with PPRS configured and invoked on both hosts.

Note: If SSH authentication is desired, it must be selected during the installation of PPRS.

There is a specific order in which the primary and Backup Hosts must be configured and started. Follow the sequence below to set up your redundant Picture Perfect system.

To perform the initial setup of your redundant system:

1. Complete Picture Perfect and PPRS installation on both hosts.

Refer to the Picture Perfect 4.6 Installation Manual to install the base Picture Perfect package on both hosts.

Refer to Chapter 2 Installing PPRS, of this manual, to install the pprs package on both hosts.

2. Configure PPRS on the Primary Host as follows:

a. From the console, log on to the Primary Host as ppadmin.

b. Open a terminal window, and then type the following commands:

. /cas/bin/profile

dbmode -iv

c. Make sure that the Replication Mode displays as Primary.

3. Start PPRS on the Primary Host by typing the following command at the ppadmin prompt:

pprscmd start primary

The following displays to indicate that PPRS is started on the Primary Host.

Starting PPRS as Primary server...... ....Done

Note: The first time this command is run after installation, you are prompted to authenticate the remote host. At the prompt, type Yes, and then press Enter.

Enter

Enter

Chapter 3Configuration and Operation

31

4. Resave any existing operators on the Primary Host.

This is necessary to correctly set up your operator's environments. You need to resave only the Primary Host operator records. Perform these steps from a client workstation connected to the Primary Host.

a. From the Picture Perfect primary navigation menu, select Control, and then Operators.

b. Click Find to view all operator records.

c. Review each one and set their passwords.

d. Click Save.

5. Configure PPRS on the Backup Host as follows:

a. From the console, log on to the Backup Host as ppadmin.

b. Open a terminal window, and then type the following commands:

. /cas/bin/profile

dbmode -iv

c. Make sure that the Replication Mode displays as Backup.

6. During startup of the Backup Host, if the Backup Host database does not synchronize with the Primary Host database, the following message displays and requests that a database recovery is required.

Starting PPRS as Backup server.Errors checking for if Recovery is needed; Stop Picture if running, do a Recover and then try starting Picture again

If required, synchronize the databases by performing a database recovery procedure from the Primary Host to the Backup Host. See Database recovery on page 39.

7. Start PPRS on the Backup Host by typing the following command at the ppadmin prompt:

pprscmd start backup

The following displays to indicate that PPRS is started on the Backup Host.

Starting PPRS as Backup server...... ....Done

8. Open the PPRS monitor by typing the following command at the ppadmin prompt:

pprscmd monitor

The system status temporarily displays Invalid, and then displays Starting Communication. After a few minutes, the system status fields on both hosts display OK. The system is now running in a redundant state.

Enter

Enter


32

PPRS Command Line UtilityThe pprscmd utility allows the ppadmin user to:

• Configure PPRS options using the configuration utility• Start/Stop PPRS• Monitor PPRS• Recover the database• Manual failover control• Enable/disable failover• Enable/disable override communication• Enable/disable warning messages

Configuration utility (pprscmd config)

The configuration utility is used to set values for the following parameters for each host (Refer to Table 3, Configuration options on page 33.):

• Polling Frequency (sec)• Min Free Shared Mem ()• Max Allowable Xoff Time (sec)• Failover Threshold

Note: Configuration changes are not synchronized, so make sure changes are made on both hosts.

To view or modify the configuration utility options:

1. Log on as ppadmin.

2. From the command line, type the following command

pprscmd config


bctsunrise> # pprscmd config Polling Frequency (sec) [10] : Min Free Shared Mem (%) [8] : Max Allowable Xoff Time (sec) [900] : Failover Threshold [1] :You have entered : Polling Frequency (sec) : 10 Min Free Shared Mem (%) : 8 Max Allowable Xoff Time (sec) : 900 Failover Threshold : 1Are these values correct (y/n) [y] :

3. Modify the parameter values as required, and then press .

Note: If Picture Perfect is running, you must restart the application for changes to take effect.

Enter

Enter


33

Note:

Start/Stop PPRS

The Primary Host must be started before starting the Backup Host.

When Picture Perfect is not running on both hosts, always start the server as primary that was last running as primary. If both databases are in primary mode because of a failover, start the one that was running last in primary mode as the Primary Server. If the modes of the hosts are reversed, then a full database recovery is required.

If you are not sure of the last database mode of the host, use the command dbmode -iv. (Refer to Chapter 7 Troubleshooting for detailed information on the dbmode command.)

To start the PPRS application in primary mode:

1. Log on as ppadmin, and then open a terminal window.

2. From the command line, type the following command to start PPRS in primary mode:

pprscmd start primary

If the remote server is already running as Primary, messages similar to the following display:

Starting PPRS as Primary server.Invalid Startup ModeStartup Mode..:[Primary]Remote DB mode:[Primary]Remote DB Stat:[Online]Exiting.

The following displays to indicate that PPRS is started on the Primary Host.

Starting PPRS as Primary server...... ....Done

Table 3. Configuration options

Menu Item Description

Polling Frequency (sec) Enter the frequency (in seconds) at which status messages are sent from the local host to the remote host. Tune this heartbeat (polling frequency) to meet the requirements of each installation. Default is 10 seconds.

Min Free Shared Mem (%) Enter the minimum allowable percentage of free shared memory in Picture Perfect.

If Failover/Takeover is enabled and the percentage of free memory falls below this value, a host in primary mode executes failover; a host in backup mode executes the disable failover procedure.

When the percentage of free shared memory is equal to 1.5 times the user-defined value, a warning pop-up window appears (if warning messages are enabled). Default value is 8 percent. The warning message says: Free shared memory approaching minimum limit.

Max Allowable Xoff Time (sec)

Enter the maximum allowable Xoff time (in seconds) for asynchronous communications to remain suspended when the host has not received a message from a micro.

If Failover/Takeover is enabled and Xoff remains set past the maximum allowable time, a host in primary mode executes failover; a host in backup mode executes the disable failover procedure. Default value is 150 seconds.

Failover Threshold Enter the number of retries before a failover occurs.

Enter


34

To start the PPRS application in backup mode:


2. From the command line, type the following command to start PPRS in backup mode:


Picture Perfect - starting database... [OK].

If a database recovery is needed, messages similar to the following display:

Picture Perfect - synchronizing database... [Failed].Errors checking for if Recovery is needed; Stop Picture if running, do a Recover and then try starting Picture again

If the primary is not running, messages similar to the following display:

Starting PPRS as Backup server.Invalid Startup ModeStartup Mode..:[Backup]Remote DB mode:[Primary]Remote DB Stat:[Offline]Exiting.

Note: The first time PPRS application is started, you may be prompted as follows:

The authenticity of host 'pphost (192.168.1.1)' can't be established.RSA key fingerprint is 00:01:d7:aa…Are you sure you want to continue connecting (yes/no)?

To continue, you must type yes, and then press .

The following displays to indicate that PPRS is started on the Backup Host.

Starting PPRS as Backup server....Picture Perfect - starting database... [OK].Picture Perfect - synchronizing database... [OK].Picture Perfect - starting application... .........Done$ The system is ready.

To stop the PPRS application in primary or backup mode:

Note: Unless you want the Backup to takeover as Primary, you should not stop the Primary while the Backup is running and Failover is enabled (by default Failover is enabled).To stop the PPRS application, Picture Perfect must be running.


2. From the command line, type the following command to stop PPRS:

pprscmd stop

The following displays to indicate that PPRS is stopped on the Backup Host.

Stopping PPRS ............ ....Done

Enter

Enter

Enter


35

Recover the database

For detailed information about the database recovery process, refer to Database Synchronization and Recovery on page 39.

To perform a database recovery on the Backup Server:Note: pprscmd recover runs even when Picture Perfect is down on both hosts.

1. At the ppadmin command prompt, type the following:

pprscmd recover


Recover PPRS executed from command lineUsing bctberlin1a for database recoveryStarting database recovery...Check Local database state [Done]Using Server [bctberlin] for recoveryCheck Local Server Last Database type [Done]Checking if Remote Database Server is running [Done]Check Database Space Sizes [Done]RECOVERY PROCESS================This task can take several minutesPlease Do Not StopPerforming Remote Database Server BackupGet Logical Log Archive file ID informationFirst Logical log in Archive Log fileLast Logical log in Archive Log file[Done]Recovering entire database. This will take a while.Do you want to continue <y/n>: [y] yRetrieving database backup fileifxDBArch[Done]Recovering database backup fileRecovering from Total Archive [Done]Setting Local database server in Secondary mode......[Done]Databases getting in sync, please wait [Done]Stopping datagase...[Done]Finished database recovery...

2. Your Backup Server database recovery is complete.

Manual failover control

The pprscmd failover command causes a manual failover to the Backup Host. This command can be used for testing the PPRS application and for maintenance purposes.

To manually failover to the Backup Host:


2. From the command line, type the following command:

pprscmd failover

Enter


36

Enable/disable failover

The pprscmd failover disable command allows you to enable or disable failover. This command enables the local host to failover (if it is the Primary Host) or takeover (if it is the Backup Host), when required.

Note: If failover has been disabled from one server, it needs to be enabled from the same server. When failover is enabled on both hosts, it can be disabled from either host.

To enable or disable failover:


2. From the command line, type the following command to enable failover:

pprscmd failover enable

3. From the command line, type the following command to disable failover:

pprscmd failover disable

Enable/disable override communication

The command allows you to enable or disable the override communication status option.

On startup of Picture Perfect Redundant system, if the override communication status is disabled (default setting), and one of the networks is not communicating, the Backup system shuts down after detecting that both networks are not operational.

On startup of Picture Perfect Redundant system, if the override communication status is enabled, and one of the networks is not communicating, the system continues to operate in redundant mode with one network.

While Picture Perfect is running on both the Primary and Backup Hosts and override communication status is disabled, if one of the networks loses communication, then a HOST to HOST Comm Failure alarm is triggered continuously until communication is reestablished. To stop the alarm from being triggered continuously, enable override communication status on the Primary and Backup Hosts to keep them in same state.

Note: To enable or disable override communication status, use the 'pprscmd override enable' or 'pprscmd override disable' commands on both servers. While system is running, the setting on the server running as Primary is what takes effect, but it is recommended to keep the same setting (enabled or disabled) on both servers. Even if you have communication override enabled during which no alarm should be triggered, if you have the HOST TO HOST COMM FAILURE alarm configured on the host records, then the alarm for when the primary network loses comm. is still triggered.

To enable or disable override communication:


2. From the command line, type the following command to enable override communication:

pprscmd override enable


Override Communication Enabled [1]

Enter


37

3. From the command line, type the following command to disable override communication:

pprscmd override disable


Override Communication Disabled [0]

Note: The value is stored in the file /cas/db/text/pprs/fppcfgfile as the parameter comm_override. The value 0 (default) indicates disabled and value 1 indicates enabled.

Enable/disable warning message

This command allows you to enables warning messages to pop-up when Picture Perfect reaches critical limits or disable the warning message pop-ups.

To enable or disable warning message:


2. From the command line, type the following command to enable warning messages:

pprscmd warning msg enable


3. From the command line, type the following command to disable warning messages:

pprscmd warning msg disable


The PPRS monitor

The PPRS monitor displays the status of the two hosts in the PPRS environment. It displays the status of the communication links between the two hosts.

Note: If a failover occurs while running the PPRS monitor on the Backup Host, the PPRS monitor automatically closes and you must restart the PPRS monitor manually.

To view the PPRS monitor:


2. From the command line, type the following command

pprscmd monitor


PPRS Monitor [ Mon Jul 13 11:35:52 2009 ]SYSTEM STATUS System Name : bctsunrise bctmitu System Mode : PRIMARY BACKUP System Status : OK OK Warning Messages : ENABLED Failover Status : ENABLED Override Comm Status : ENABLED

Enter

Enter

Enter

Enter


38

NETWORK STATUS Network I : OK OK Network II : OK OK

3. Refer to Table 4, PPRS status descriptions on page 38 for detailed description of the status variables.

Table 4. PPRS status descriptions

Field Description

System Status The System Status section indicates the current statuses of both hosts.

System NameDisplays the name of each host (from the /etc/hosts file).

System ModeDisplays the mode of each host: Primary, Backup, or Invalid.

System StatusDisplays the status of each host: Enabled, Failover, Disable, Takeover, or Starting Comm.

Warning MessagesDisplays the current status of the warning messages parameter (ENABLED or DISABLED).

Failover StatusDisplays the present Failover mode of the local host: Enabled or Disabled.

Override Comm StatusDisplays the present status of the Communications Override feature of the local host: Enabled or Disabled (default). If the Override Communication Status displays Enabled, the PPRS system is capable of functioning with only one network instead of two.

Network Status The Network Status section indicates the communication statuses of both networks (Network I and Network II) as perceived by the local host: OK or No Communication (No Comm).


39

Database Synchronization and RecoveryWhen a host that was removed from the redundant environment becomes operational again, the databases of the two hosts must be synchronized. Depending on the system activity level during one host’s absence from the redundant environment, that host may also require a database recovery.

Database synchronization

When a failed Backup Host or a failed Primary Host recovers, the Backup Host requires deletions and/or insertions to its database in order to match (synchronize with) the database of the Primary Host.

During Backup server start up, if the databases cannot synchronize naturally (database to database connection), the Picture Perfect application displays a message advising you to perform a database recovery. In this case, use the Database Recovery function to synchronize the two databases, otherwise the databases will not be matched and the Backup Server will not be able to start up.

Database Recovery updates records which have been modified on the Primary Host databases, inserts missing data into the Backup Host database (from the Primary Host database), and deletes records on the Primary Host database.

PPRS database synchronization

If the Backup Server has not been down for a long time, which also depends on database activity, the Backup Server can be recovered automatically by restarting Picture Perfect on the Backup Server. If database synchronization fails, the system displays a message that a database recovery is required.

Use the Database Recovery function pprscmd recover to synchronize the databases of the two hosts. When the database recovery process is complete, start Picture Perfect on the repaired host.

Database recovery

A database recovery is only allowed in the Backup Server. The following are examples of when an operator will receive a warning message that a database recovery from the Backup Server is required.

• The Backup Server has been down for a period of time, in which the Logical Logs are reused in total. When this occurs, the database has no way to recover the latest updates after connecting to the Primary Server.

• Both servers are in found in Primary mode (dual Primary). In this case, the server that has been up and running longer remains up and a database recovery is required in the paired machine.

• A Failover/Takeover event occurs, during which the operator stops the new Primary Server, and then starts up the old Primary Server in primary mode again. In this case, the server that took over (now stopped) requires a database recovery since the Logical Logs are not synchronized.

Note: To ensure secure transmission of the authentication information between the two hosts, SSH should be enabled.


40

Before you start:

1. Use the Backup Host as the recovery server.

2. Picture Perfect must not be running on the recovery server.

3. The Primary Host must be accessible via the network before the actual recovery process.

To perform the database recovery:

1. Log on to the Backup Host as ppadmin, and then open a terminal window.

2. From the command line, type the following command.

pprscmd recover


Checking Local database state [Done]Checking Remote Server [bctdavie] [Done]Using Server [bctdavie] for recoveryChecking Local Server Last Database type [Done]Checking if Remote Database Server is running [Done]Checking Database Space Sizes [Done]RECOVERY PROCESS================This task can take several minutesPlease Do Not StopPerforming Remote Database Server Backup [Done]Recovering entire database. This will take a while.Do you want to continue (y/n)?: [y]

3. Type y to continue the database recovery.

Retrieving database backup fileifxDBArch 100% 52MB 13.1MB/s 00:04 [Done]Recovering database backup fileRecovering from Total Archive [Done]Setting Local database server in Secondary mode...... [Done]Databases getting in sync, please wait [Done]Stopping database... [Done]

4. When the recovery is complete, start Picture Perfect application on the Backup Server by typing the following command:


Note: The database recovery process updates all Picture Perfect database tables.

Enter

Enter

This chapter describes the failover and takeover sequence of events.

In this chapter:

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Failover Event Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Takeover Event Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Disable Failover Event Sequence . . . . . . . . . . . . . . . . . . . . . . . 43Error Conditions and Responses . . . . . . . . . . . . . . . . . . . . . . . . 44Dual Primary Host and Dual Backup Host Errors . . . . . . . . . . . . 45Recognizing a Failover/Takeover Condition . . . . . . . . . . . . . . . . 45Operator Action for Failover/Takeover . . . . . . . . . . . . . . . . . . . . 45Possible Events on the Primary Host . . . . . . . . . . . . . . . . . . . . . 46Possible Events on the Backup Host . . . . . . . . . . . . . . . . . . . . . 47

Chapter 4 Failover and Takeover


42

OverviewIf the Primary Host detects certain undesirable conditions in itself, it executes the failover event sequence which instructs the Backup Host to take over system operation. For example, failover can occur when any critical process running on the Primary Host fails. When failover is initiated by the Primary Host, the Backup Host responds with the takeover event sequence, which puts it in control of the system.

The two hosts continually monitor each other through heartbeat messages. The Backup Host can initiate the takeover event sequence (without receiving a failover message) if it does not detect the Primary Host’s heartbeat after a certain length of time. Loss of the heartbeat message could be caused by network failure (on both networks), an operating system crash, or power outage on the Primary Host. It is the loss of communication which causes the Backup Host to initiate the takeover.

PPRS does not allow failover/takeover to occur unless the Backup Host is operational. If either host detects an error condition on the Backup Host, a disable-failover sequence is initiated to inhibit the failover mechanism. The non-operational Backup Host is then prevented from executing a takeover.

This chapter details the event sequences of failover and takeover operations. It describes the events that cause disable failover to occur, and lists common error conditions and their corresponding PPRS responses.

Failover Event SequenceOnly the Primary Host executes the failover procedure. Failover is initiated when any of the following conditions occur:

• Due to an unrecoverable error, PPRS terminates and cannot be re-invoked.• Due to an unrecoverable error, Informix terminates and cannot be re-invoked.• The amount of available shared memory in PPRS is less than the user-defined percentage of

total shared memory.• The micro controller communication Xoff status remains Xoff for longer than the user-defined

number of minutes.• All communication processes terminate and cannot be re-established.• The system administrator initiates a manual failover.• TPS processes respawn repeatedly.

Table 5. Failover event sequence

Primary Host (Initiates) Backup Host (Responds)

Sends a failover message. Receives a failover message.

Prints a failover message. Executes the takeover procedure.

Sends a Picture Perfect failover alarm. Sends a Picture Perfect takeover alarm.

Shuts down the PPRS application. Displays a takeover message. Takes control of PPRS.

Chapter 4Failover and Takeover

43

Takeover Event SequenceOnly the Backup Host executes the takeover procedure. For takeover to occur, the failover function must be enabled.

Takeover is initiated when either of the following conditions occur:

• The Backup Host receives a failover message from the Primary Host.• The Backup Host loses communication with the Primary Host over both networks.

Disable Failover Event SequenceEither host can initiate the disable-failover procedure.

Disable failover is initiated by the Backup Host when any of the following conditions occur:

• Picture Perfect processes terminate on the Backup Host and cannot be re-invoked.• Informix processes terminate on the Backup Host and cannot be re-invoked.

If the Primary Host receives the disable_failover status message, the Primary Host disables failover until it receives an OK status message from the Backup Host. A warning message advises that redundancy is no longer in effect. When this occurs, a disable-failover alarm appears on the Alarm Monitor.

The Primary Host disables failover if either of the following conditions occur:

• The operator manually executes a Disable Failover/Takeover. • Both of the communication links to the Backup Host are interrupted.

Table 6. Takeover event sequence (no heartbeat)

Primary Host Backup Host

Fails (no heartbeat) Executes the takeover procedure.

Sends a Picture Perfect takeover alarm.

Displays a takeover message.

Takes control of PPRS.


44

Error Conditions and ResponsesThe following tables list some of the error conditions that can occur and how PPRS responds to them.

* An illegal condition called a dual-primary-host error exists if communication over both networks fails simultaneously and the Back-up Host becomes a Primary Host without the true Primary Host relinquishing control. When communication is re-established and both hosts detect that there are two Primary Hosts running, the original Primary Host remains running and the other host auto-matically shuts down.

* An illegal condition called a dual-primary-host error exists if communication over both networks fails simultaneously and the Back-up Host becomes a Primary Host without the true Primary Host relinquishing control. When communication is re-established and both hosts detect that there are two Primary Hosts running, the original Primary Host remains running and the other host auto-matically shuts down.

Table 7. Primary Host error conditions

Error condition Primary Host response Backup Host response

Critical process dies. Executes failover sequence. Receives failover message.

Executes takeover sequence.

Operating-system crash/power outage.

Undetermined. Communication times out.


Time-out on one network.

Sends message to backup.

Checks status of other client/server.

Displays warning message.

Automatically switches to next available network.

Receives communication time-out message.

Displays warning message.

Automatically switches to next available network.

Time-out on both networks.*

Displays error message.

Executes disable-failover sequence.


Table 8. Backup Host error conditions

Error condition Backup Host response Primary Host response

Critical process dies. Executes disable-failover sequence. Receives disable-failover message.


Operating system crash/power outage.

Undetermined. Communication times out.


Database synchronization process dies.

Executes disable-failover sequence. Receives disable-failover message.


Time-out on one network.

Sends time-out message.

Checks status of second network and switches to functional network, if required.


Receives time-out message.


Checks status of second network and switches to functional network, if required.

Time-out on both networks.*

Executes takeover sequence. Displays error message.



45

Dual Primary Host and Dual Backup Host ErrorsA dual-primary-host error is an illegal condition which occurs when both hosts are running in primary mode due to a simultaneous communications failure on both networks. The error can also occur if you accidentally start both hosts as primary (if hosts are not communicating through the network). If both hosts are primary, they will send messages to the micros at the same time, causing the micros to go into a null state. Once communication is re-established, this condition is resolved as follows:

• The host running in primary mode for a longer period of time will remain in primary mode.• The host running in primary mode for a shorter period of time will shut down.

A dual-backup-host error is an illegal condition which occurs when both hosts are started up in backup mode, due to an oversight in configuration. Both hosts automatically shut down when this condition occurs.

Recognizing a Failover/Takeover ConditionYou can recognize a failover condition when a Failover message appears on the Alarm Monitor in the current Primary Host. This is a primary-initiated failover. When this occurs, the operator receives the Connection Lost pop-up dialog stating “Your connection has been lost. Do you want to reconnect now?.” Click Retry or Logout.

Note: During a takeover in a Redundant configuration, the Picture Perfect application is automatically restarted. Successful logons are not possible until the application has fully started.

Operator Action for Failover/TakeoverIt should also be noted that functionality of a window can be determined by the following procedure.

• Click Retry on the Connection Lost pop-up dialog. • If the pop-up dialog does not reappear after clicking Retry, open one of the forms and attempt

retrieving records. If no data is retrieved, it is considered locked up or non-functional.

For each of the following events, the system administrator should be notified immediately. In addition, the result and action of an event also depends on the Terminal.


46

Possible Events on the Primary HostTable 9. Takeover event sequence (no heartbeat) on the Primary Host

Primary event #1 The operator is logged into the Primary Host when the operating system on the Primary Host crashes.

PC-Client Station The connection between PC client and the Primary Host will eventually time out. When it does, the operator is prompted to retry or log out by the Connection Lost popup.

The alarms should appear on the Backup Host’s Alarm Monitor: Takeover and Disable Failover.

Once the system administrator has recovered the failed host and re-starts PPRS, the operator should log off and log in again.

Primary event #2 The operator is logged into the Primary Host when the Backup Host crashes.

PC-Client Station Three alarms should appear on the Primary Host’s Alarm Monitor:

• Host to Host COMM Failure (remote Backup Server 1)


• Disable Failover

Primary event #3 The operator is logged into the Primary Host when the system administrator shuts down PPRS on the Primary Host.

PC-Client Station The connection between PC client and the Primary Host will eventually time out. When it does, the operator is prompted to retry or log out by the Connection Lost popup. The Operator must select Logout.

Once the system administrator has recovered the failed host, it must then be restarted in backup mode. The operator should log off and log in again.

Primary event #4 The operator is logged into the Primary Host system administrator shuts down PPRS on the Backup Host.

PC-Client Station Three alarms should appear on the Primary Host’s Alarm Monitor:



• Disable Failover

Primary event #5 The operator is logged into the Primary Host when the network connection goes down between the PC-Client and the Primary Host.

PC-Client Station The connection between PC client and the Primary Host will eventually time out. When it does, the operator is prompted to retry or log out by the Connection Lost popup.

Once the communication has been reestablished, click Retry. Your session will continue functioning.

Primary event #6 The operator is logged into the Primary Host when the network connection goes down between the PC-Client and both hosts (primary and backup).

PC-Client Station The connection between PC client and the Primary Host/Backup Host will eventually time out. When it does, the operator is prompted to retry or log out by the Connection Lost popup.



47

Possible Events on the Backup HostTable 10. Takeover event sequence (no heartbeat) on the Backup Host

Backup event #1 The operator is logged into the Backup Host when the operating system on the Backup Host crashes.

PC-Client Station The connection between PC client and the Backup Host will eventually time out. When it does, the operator is prompted to retry or log out by the Connection Lost popup.

Once the system administrator has recovered the failed host, the operator should click Retry. Your session will continue functioning.

Backup event #2 The operator is logged into the Backup Host when the Primary Host crashes.

PC-Client Station The Operator will receive an Invalid Session popup. The Operator must select Logout, and then log back into the Backup Server. If the Operator selects Retry, a System Notification popup displays. Click OK and the Operator will be returned to the Picture Perfect Login window. Once the Operator has logged in, a notice that the server has now switched to Primary mode displays and two alarms display: HOST TO HOST COMM FAILURE and Takeover Event.

Backup event #3 The operator is logged into the Backup Host when the system administrator shuts down PPRS on the Backup Host.


Once the system administrator has recovered the failed host, the operator should click Retry. Your session will continue functioning.

Backup event #4 The operator is logged into the Backup Host when the system administrator shuts down PPRS on the Primary Host.

PC-Client Station The Operator will receive an Invalid Session popup. The Operator must select Logout, and then log back into the Backup Server. If the Operator selects Retry, a System Notification popup displays. Click OK and the Operator will be returned to the Picture Perfect Login window. Once the Operator has logged in, a notice that the server has now switched to Primary mode displays and two alarms display: HOST TO HOST COMM FAILURE and Takeover Event.

Backup event #5 The operator is logged into the Backup Host when the network connection goes down between the PC-Client and the Backup Host.



Backup event #6 The operator is logged into the Backup Host when the network connection goes down between the PC-Client and both hosts (primary and backup)

PC-Client Station The connection between PC client and the Backup Host/Primary Host will eventually time out. When it does, the operator is prompted to retry or log out by the Connection Lost popup.



48

This chapter includes information needed to verify that your redundant system is configured properly.

In this chapter:

chkredundant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Verifying Network Connections. . . . . . . . . . . . . . . . . . . . . . . . . . 54Verifying Picture Perfect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Verifying Network Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57File Check of .netrc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Verifying Static Routing Table . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Verifying Remote Database Access Configuration . . . . . . . . . . . 62Verifying Table IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Verification of Hosts Time Synchronization . . . . . . . . . . . . . . . . 63chkdbsync. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 5 Verifying the Configuration


50

chkredundantTo verify that the Redundant System is configured properly, the chkredundant utility is executed on either the primary or Backup Host while the database is running on both hosts.

Note: If Picture Perfect is running, the database is running. It is not necessary to start it.

To verify the configuration:

Note: The root user runs all checks, while the ppadmin user only runs limited checks.

1. On both hosts, log on as root, and then open a terminal window.

A command prompt is displayed.

2. If Picture Perfect is not running, manually start the database on each host by typing:

su - ppadmin -c oninit

You are returned to the command prompt.

3. At the command prompt on the primary or Backup Host, type chkredundant


Redundant Host Local [bctottawa]: Verifying Operating System Type... [ Linux ] Verifying TPS is running... [ OK ] Verifying Informix is running... [ OK ] Verifying drarchlog is running... [ OK ] Verifying ontape is running... [ OK ] Verifying /etc/hosts... bctottawa [ OK ] bctottawa2 [ OK ] bctwunan [ OK ] bctwunan2 [ OK ] Verifying physical devices... /dev/rrootdbs [ OK ] /dev/rbasedbs [ OK ] /dev/rtempdbs [ OK ] /dev/rllogdbs [ OK ] /dev/rplogdbs [ OK ] Verifying .netrc for informix user... File /cas/db/.netrc exists [ OK ] Owned by ìnformix` user [ OK ] Owned by ìnformix` group [ OK ] Contents of /cas/db/.netrc are valid [ OK ] Verifying .netrc for root user... File /root/.netrc exists [ OK ] Owned by `root` user [ OK ] Owned by `root` group [ OK ] Contents of /root/.netrc are valid [ OK ] Verifying .netrc for ppadmin user... File /cas/.netrc exists [ OK ] Owned by `ppadmin` user [ OK ] Owned by `pperf` group [ OK ] Contents of /cas/.netrc are valid [ OK ] Verifying packages... [ OK ] Verifying system_config count... [ OK ] Verifying host table against /etc/hosts... SERVER_HOST = bctottawa [ OK ] REMOTE_CLIENT = bctwunan [ OK ] HOST bctottawa IP = 3.137.174.215 [ OK ] HOST bctottawa ALT IP = 192.100.100.1 [ OK ]

Enter

Enter

Chapter 5Verifying the Configuration

51

HOST bctwunan IP = 3.137.174.214 [ OK ] HOST bctwunan ALT IP = 192.100.100.2 [ OK ] Verifying /etc/hosts Pri & Sec Consistency... PRI SERVER_HOST = SEC REMOTE_SERVER [ OK ] PRI CLIENT_HOST = SEC REMOTE_CLIENT [ OK ] PRI REMOTE_CLIENT = SEC CLIENT_HOST [ OK ] PRI REMOTE_SERVER = SEC SERVER_HOST [ OK ] Verifying Seed Counter Settings... [ DISABLED ] Verifying DB Spaces... [ OK ] Verifying Picture Perfect Modes... bctottawa: Picture Perfect (TPS) mode [ PRIMARY ] bctottawa: Informix HDR (replication) mode [ HDR-PRIMARY ] bctottawa: Informix HDR mode matches TPS mode [ OK ] bctwunan: Picture Perfect (TPS) mode [ BACKUP ] bctwunan: Informix HDR (replication) mode [ HDR-SECONDARY] bctwunan: Informix HDR mode matches TPS mode [ OK ] Verifying /cas/db/log/online.log... Owned by `ppadmin` user [ OK ] Owned by `pperf` group [ OK ] Log file contains HDR errors [ OK ] Verifying Informix Settings... Onconfig AUTO_AIOVPS option [ OK ] Onconfig AUTO_CKPTS option [ OK ] Onconfig BUFFERPOOL option [ OK ] Onconfig DBSPACETEMP option [ OK ] Onconfig DEF_TABLE_LOCKMODE option [ OK ] Onconfig DIRECT_IO option [ OK ] Onconfig DRINTERVAL option [ OK ] Onconfig DRTIMEOUT option [ OK ] Onconfig IFX_FOLDVIEW option [ OK ] Onconfig LTAPEBLK option [ OK ] Onconfig LTAPEDEV option [ OK ] Onconfig LTAPESIZE option [ OK ] Onconfig MAX_INCOMPLETE_CONNECTIONS option [ OK ] Onconfig MAXPDQPRIORITY option [ OK ] Onconfig NUMAIOVPS option [ OK ] Onconfig OPT_GOAL option [ OK ] Onconfig STMT_CACHE option [ OK ] Onconfig STMT_CACHE_HITS option [ OK ] Onconfig STMT_CACHE_NOLIMIT option [ OK ] Onconfig TAPEBLK option [ OK ] Onconfig TAPEDEV option [ OK ] Onconfig TAPESIZE option [ OK ] Onconfig TEMPTAB_NOLOG option [ OK ] Onconfig UPDATABLE_SECONDARY option [ OK ] Onconfig VP_MEMORY_CACHE_KP option [ OK ] Verifying /etc/services... bctottawa [ OK ] bctwunan [ OK ]Redundant Host Remote [bctwunan]: Verifying Network Connection [bctwunan]... [ OK ] Verifying Network Connection [bctwunan2]... [ OK ] Verifying Remote Connectivity via ssh... [ OK ] Verifying Operating System Type... [ Linux ] Verifying TPS is running... [ OK ] Verifying Informix is running... [ OK ] Verifying Remote Database Connectivity... [ OK ] Verifying /etc/hosts... bctwunan2 [ OK ] bctwunan [ OK ] bctottawa2 [ OK ] bctottawa [ OK ]


52

Verifying physical devices... /dev/rrootdbs [ OK ] /dev/rbasedbs [ OK ] /dev/rtempdbs [ OK ] /dev/rllogdbs [ OK ] /dev/rplogdbs [ OK ] Verifying .netrc for informix user... File /cas/db/.netrc exists [ OK ] Owned by ìnformix` user [ OK ] Owned by ìnformix` group [ OK ] Contents of /cas/db/.netrc are valid [ OK ] Verifying .netrc for root user... File /root/.netrc exists [ OK ] Owned by `root` user [ OK ] Owned by `root` group [ OK ] Contents of /root/.netrc are valid [ OK ] Verifying .netrc for ppadmin user... File /cas/.netrc exists [ OK ] Owned by `ppadmin` user [ OK ] Owned by `pperf` group [ OK ] Contents of /cas/.netrc are valid [ OK ] Verifying packages... [ OK ] Verifying system_config count... [ OK ] Verifying host table against /etc/hosts... REMOTE_SERVER = bctottawa [ OK ] CLIENT_HOST = bctwunan [ OK ] HOST bctottawa IP = 3.137.174.215 [ OK ] HOST bctottawa ALT IP = 192.100.100.1 [ OK ] HOST bctwunan IP = 3.137.174.214 [ OK ] HOST bctwunan ALT IP = 192.100.100.2 [ OK ] Verifying /etc/hosts Pri & Sec Consistency... PRI SERVER_HOST = SEC REMOTE_SERVER [ OK ] PRI CLIENT_HOST = SEC REMOTE_CLIENT [ OK ] PRI REMOTE_CLIENT = SEC CLIENT_HOST [ OK ] PRI REMOTE_SERVER = SEC SERVER_HOST [ OK ] Verifying Seed Counter Settings... [ DISABLED ] Verifying DB Spaces... [ OK ] Verifying Picture Perfect Modes... bctottawa: Picture Perfect (TPS) mode [ PRIMARY ] bctottawa: Informix HDR (replication) mode [ HDR-PRIMARY ] bctottawa: Informix HDR mode matches TPS mode [ OK ] bctwunan: Picture Perfect (TPS) mode [ BACKUP ] bctwunan: Informix HDR (replication) mode [ HDR-SECONDARY] bctwunan: Informix HDR mode matches TPS mode [ OK ] Verifying /cas/db/log/online.log... Owned by `ppadmin` user [ OK ] Owned by `pperf` group [ OK ] Log file contains HDR errors [ OK ] Verifying Informix Settings... Onconfig AUTO_AIOVPS option [ OK ] Onconfig AUTO_CKPTS option [ OK ] Onconfig BUFFERPOOL option [ OK ] Onconfig DBSPACETEMP option [ OK ] Onconfig DEF_TABLE_LOCKMODE option [ OK ] Onconfig DIRECT_IO option [ OK ] Onconfig DRINTERVAL option [ OK ] Onconfig DRTIMEOUT option [ OK ] Onconfig IFX_FOLDVIEW option [ OK ] Onconfig LTAPEBLK option [ OK ] Onconfig LTAPEDEV option [ OK ] Onconfig LTAPESIZE option [ OK ] Onconfig MAX_INCOMPLETE_CONNECTIONS option [ OK ] Onconfig MAXPDQPRIORITY option [ OK ]


53

Onconfig NUMAIOVPS option [ OK ] Onconfig OPT_GOAL option [ OK ] Onconfig STMT_CACHE option [ OK ] Onconfig STMT_CACHE_HITS option [ OK ] Onconfig STMT_CACHE_NOLIMIT option [ OK ] Onconfig TAPEBLK option [ OK ] Onconfig TAPEDEV option [ OK ] Onconfig TAPESIZE option [ OK ] Onconfig TEMPTAB_NOLOG option [ OK ] Onconfig UPDATABLE_SECONDARY option [ OK ] Onconfig VP_MEMORY_CACHE_KP option [ OK ] Verifying /etc/services... bctottawa [ OK ] bctwunan [ OK ]Results: Passed [ 154 ], Failed [ 0 ], Blocked [ 0 ]root@bctottawa#

4. Note the Results line listed at the end of the output. If the Failed column lists a number greater than 0, then there are problems in your configuration. Please see the sections that follow for troubleshooting details for each test. If the Failed column lists 0, then the installation is successful.

5. When satisfied with the results, if you manually started the database, stop it on both hosts, by typing: su - ppadmin ‘onmode -ky’

Table 11.

Test Description

Verifying Network Connection This test will fail if a remote host cannot be reached using the ping command. If this test fails, then there is either a networking configuration problem on the local host or on the target remote host or both. See Verifying Network Connections on page 54.

Verifying Remote Connectivity via SSH

This test will fail if a remote host cannot be reached by SSH. SSH is required for chkredundant to verify conditions on a remote host. Please enable SSH access to the remote host and try again.

Verifying Operating System Type

This test can fail only if chkredundant is being executed on a system that is neither Linux nor AIX. Currently, PPRS is supported only on Linux and AIX operating systems.

Verifying TPS is running See Verifying Picture Perfect on page 54.

Verifying Informix is running See Verifying Picture Perfect on page 54.

Verifying Remote Database Connectivity

This test can fail only if either the /cas/db/etc/sqlhosts file or the /etc/services file is configured incorrectly. Failure indicates that the local host cannot remotely access the remote host database.

See Verifying Remote Database Access Configuration on page 62.

Verifying Seed Counter Settings This test determines whether or not Seed Counter is enabled or disabled. Both hosts in a redundant system must have the same Seed Counter settings. If a setting mismatch is detected, then a warning is displayed indicating that both hosts in the redundant system must have identical Seed Counter settings in order for the system to function normally. To correct this problem, it is necessary to reinstall the mismatched host.

Enter


54

Verifying Network ConnectionsUse the ping command from each host to check all network connections of the remote host.

ping remote_hostname

For example: ping andromeda

You should see output similar to the following:

PING bctwunan (3.137.000.214) 56(84) bytes of data.64 bytes from bctwunan (3.137.000.214): icmp_seq=1 ttl=64 time=0.141 ms64 bytes from bctwunan (3.137.000.214): icmp_seq=2 ttl=64 time=0.319 ms64 bytes from bctwunan (3.137.000.214): icmp_seq=3 ttl=64 time=0.223 ms64 bytes from bctwunan (3.137.000.214): icmp_seq=4 ttl=64 time=0.236 ms

Press C to stop the ping command and display the ping statistics:

--- bctwunan ping statistics ---4 packets transmitted, 4 received, 0% packet loss, time 3001msrtt min/avg/max/mdev = 0.141/0.229/0.319/0.065 msroot@bctottawa#

You should see 0% packet loss. If packet loss is higher than this, troubleshoot your network. You may have to switch the network cable connections to the other network adapter.

Verifying Picture Perfect

AIX

Verify that Picture Perfect is running on the primary and the Backup Hosts by using the ipcs command. This command verifies that Informix and TPS are running (attached to shared memory).

Verifying /etc/hosts See File setup of /etc/hosts on page 58.

Verifying system_config count See Verifying Table IDs on page 62

Verifying host table against /etc/hosts

This test can fail only if there is an inconsistency in the host names stored in the host table relative to the host names stored in the /etc/hosts file for the primary and Backup Servers. Either one or both, the host table and the /etc/hosts file, must be corrected. See File setup of /etc/hosts on page 58.

Verifying /etc/hosts Pri & Sec Consistency

See File setup of /etc/hosts on page 58.

Verifying /etc/services See Verifying Remote Database Access Configuration on page 62.

Verifying host times See Verification of Hosts Time Synchronization on page 63.

Table 11.

Test Description

Enter

Ctrl.


55

To verify Picture Perfect:


2. Type the following command:

ipcs

3. If Informix and TPS are running, output similar to the following displays:

Note: TPS is recognized by the KEY ending in 400 for shared memory and 401 for semaphore. For example: 0x00000400 and 0x00000401

------ Shared Memory Segments --------key shmid owner perms bytes nattch status0x00000000 753664 ppadmin 600 393216 2 dest0x52564801 1245186 root 660 464982016 60x00000000 786435 ppadmin 600 393216 2 dest0x00000000 819204 ppadmin 600 393216 2 dest0x00000000 851973 ppadmin 600 393216 2 dest0x00000000 884742 ppadmin 600 393216 2 dest0x00000000 917511 ppadmin 600 393216 2 dest0x00000000 1048584 ppadmin 600 393216 2 dest0x00001770 1212425 ppadmin 666 193 50x52564802 1277962 root 660 134217728 60x00000400 1310731 ppadmin 666 18288652 270x00000000 1409038 ppadmin 600 393216 2 dest------ Semaphore Arrays --------key semid owner perms nsems0x00000000 688136 root 660 70x00001388 655369 ppadmin 666 10x00000401 720906 ppadmin 666 20------ Message Queues --------key msqid owner perms used-bytes messages0x00000401 0 ppadmin 666 0 00x00000402 32769 ppadmin 666 0 00x00000403 65538 ppadmin 666 0 00x00000404 98307 ppadmin 666 0 00x00000405 131076 ppadmin 666 0 00x00000406 163845 ppadmin 666 0 00x00000407 196614 ppadmin 666 0 00x0000040a 229383 ppadmin 666 0 00x0000040b 262152 ppadmin 666 0 00x0000040c 294921 ppadmin 666 0 00x0000040d 327690 ppadmin 666 0 00x0000040e 360459 ppadmin 666 0 00x0000040f 393228 ppadmin 666 0 00x00000410 425997 ppadmin 666 0 00x00000411 458766 ppadmin 666 0 00x00000412 491535 ppadmin 666 0 00x00000413 524304 ppadmin 666 0 00x00000414 557073 ppadmin 666 0 00x00000415 589842 ppadmin 666 0 00x00000416 622611 ppadmin 666 0 00x00000417 655380 ppadmin 666 0 0[ppadmin@bctottawa ~]$

When Picture Perfect is not running, there should be no Message Queues, Shared Memory, and Semaphores for TPS or Informix. If there are entries, then Shared Memory is corrupted.

Enter


56

Linux

Verify that Picture Perfect is running on the primary and the Backup Hosts by verifying that TPS and Informix are running (attached to shared memory.)

To verify that TPS is running:

Note: In Linux, there are two steps to verify TPS.


2. Type the following command to check if the TPS processes are running:

ps -e | grep tps

The output should appear similar to the following:

[ppadmin@bctottawa ~]$ ps -e | grep tps 1180 ? 00:00:00 tps 1191 ? 00:00:00 tps 1192 ? 00:00:01 tps 1195 ? 00:00:00 tps 1196 ? 00:00:00 tps 1197 ? 00:00:00 tps 1198 ? 00:00:00 tps 1199 ? 00:00:00 tps 1200 ? 00:00:00 tps 1201 ? 00:00:00 tps 1202 ? 00:00:00 tps 1203 ? 00:00:00 tps 1204 ? 00:00:00 tps 1207 ? 00:00:00 tps 1208 ? 00:00:00 tps 1209 ? 00:00:00 tps 4327 ? 00:00:01 tps 4328 ? 00:00:00 tps 4334 ? 00:00:01 tps

If no results are shown, TPS is not running.

3. Next, type the following command to check if TPS is attached to shared memory:

ipcs | grep 0x000004


0x00000400 1310731 ppadmin 666 18288652 270x00000401 720906 ppadmin 666 200x00000401 0 ppadmin 666 0 00x00000402 32769 ppadmin 666 0 00x00000403 65538 ppadmin 666 0 00x00000404 98307 ppadmin 666 0 00x00000405 131076 ppadmin 666 0 00x00000406 163845 ppadmin 666 0 00x00000407 196614 ppadmin 666 0 00x0000040a 229383 ppadmin 666 0 00x0000040b 262152 ppadmin 666 0 00x0000040c 294921 ppadmin 666 0 00x0000040d 327690 ppadmin 666 0 00x0000040e 360459 ppadmin 666 0 00x0000040f 393228 ppadmin 666 0 0

Enter

Enter


57

0x00000410 425997 ppadmin 666 0 00x00000411 458766 ppadmin 666 0 00x00000412 491535 ppadmin 666 0 00x00000413 524304 ppadmin 666 0 00x00000414 557073 ppadmin 666 0 00x00000415 589842 ppadmin 666 0 00x00000416 622611 ppadmin 666 0 00x00000417 655380 ppadmin 666 0 0

If no results are shown, TPS is NOT running.

To verify that Informix is running:

Note: In Linux, there are two steps to verify Informix is running.

1. Type the following command to check if the Informix processes are running:

ps -e | grep oninit


942 ? 00:02:07 oninit950 ? 00:00:00 oninit951 ? 00:00:00 oninit952 ? 00:00:00 oninit953 ? 00:00:00 oninit954 ? 00:00:06 oninit

If no results are shown, Informix is NOT running.

2. Next, type the following command to check if Informix is attached to shared memory:

ipcs -c | grep informix


1245186 660 root informix root informix1277962 660 root informix root informix688136 660 root informix root informix

If no results are shown, Informix is NOT running.

Verifying Network SetupThe PPRS environment software must be installed in a dual-network configuration. This configuration requires some or all of the following verification procedures and modification of the /etc/hosts and the .netrc. The following sections provide file setup information for these files along with an example site.

Enter

Enter


58

File setup of /etc/hosts

Host Names

In a dual network configuration, each server requires two host names (such as bctottawa and bctottawa2, bctwunan and bctwunan2).

Descriptions

The descriptions are required in order to configure the communication between the two hosts. Without these descriptions, the communication subhosts do not know the IP addresses of the other end of the communication.

The SERVER_HOST in the bctottawa host receives messages from the REMOTE_CLIENT in the bctwunan host, and the CLIENT_HOST in the bctottawa2 host sends messages to the REMOTE_SERVER IP address in the bctwunan2 host.

The file setup of /etc/hosts is done automatically during the installation (which is illustrated in the next section). The following two tables show the required entries in the /etc/hosts file for the Host1 (bctwunan) and Host2 (bctwunan) servers. Each line requires an entry for IP address, host name, and descriptions.

Table 12. Host1 Host Names

Host1 Name Network Host2 Name Network

bctottawa 1 bctwunan 1

bctottawa2 2 bctwunan2 2

Table 13. Host1 /etc/hosts File

IP Address Host Name Description

10.41.200.57 bctottawa # SERVER_HOST

10.41.222.57 bctottawa2 # CLIENT_HOST

10.41.200.58 bctwunan # REMOTE_CLIENT

10.41.222.58 bctwunan2 # REMOTE_SERVER

Table 14. Host2 /etc/hosts File

IP Address Host Name Description

10.41.200.58 bctwunan # CLIENT_HOST

10.41.222.58 bctwunan2 # SERVER_HOST

10.41.200.57 bctottawa # REMOTE_SERVER

10.41.222.57 bctottawa2 # REMOTE_CLIENT


59

Notice that bctottawa and bctwunan have the same subdomain IP address (200) on the first network, and bctottawa2 and bctwunan2 have the same subdomain IP address (222) on the second network.

Note: The commented information following the # sign in the descriptions (for example, # CLIENT_HOST), is used by the primary and backup Picture Perfect servers and should not be altered.

File Check of .netrcThe .netrc is a file used to configure secured database communication between remote servers. Perform the following checks to ensure your configuration is properly setup.

Note: The /cas/db/.netrc, /cas/.netrc, and .netrc files must be same. If they are not the same, edit the files using an editor such as vi.

To verify the informix .netrc file:

1. Log on to the primary and Backup Hosts as root, and then open a terminal window.

2. Type the following command on the Primary Host:

cat /cas/db/.netrc

Output similar to the following displays:

machine bctwunanlogin ppadminpassword ppadminmachine bctwunan2login ppadminpassword ppadminroot@bctottawa#

3. Type the following command on the Backup Host:

cat /cas/db/.netrc


machine bctottawalogin ppadminpassword ppadminmachine bctottawa2login ppadminpassword ppadminroot@bctwunan#

To verify the ppadmin .netrc file:


cat /cas/.netrc

2. Output similar to the following displays:

machine bctwunanlogin ppadminpassword ppadminmachine bctwunan2login ppadminpassword ppadmin

Enter

Enter

Enter


60


cat /cas/.netrc

4. Output similar to the following displays:


To verify the root .netrc file:


Linux

cat /root/.netrc



AIX

cat /.netrc




Linux

cat /root/.netrc



Enter

Enter

Enter

Enter


61

AIX

cat /.netrc



Verifying Static Routing TableVerify that the Static Routing Table is configured properly. This is one way to check that you have configured the /etc/hosts files correctly.

To verify that the Static Routing Table is configured properly:

1. Log on to the primary and Backup Hosts as root, and then open a terminal window.

2. Use the following command on each host to view the Static Routing Table:

netstat -r

3. If the data in the Static Routing Table does not match the following example (such as missing data in a field, extra entries, or duplicate entries), contact Technical Support for further instructions. There must be a unique entry for each destination, gateway, and interface.

Kernel IP routing tableDestination Gateway Genmask Flags MSS Window irtt Iface192.100.100.0 * 255.255.255.0 U 0 0 0 eth13.137.174.0 * 255.255.255.0 U 0 0 0 eth0169.254.0.0 * 255.255.0.0 U 0 0 0 eth1default 3.137.174.1 0.0.0.0 UG 0 0 0 eth0

Destination: The IP address includes destination addresses up to the subdomain level.

Gateway: The gateway host name must reflect the corresponding host name from the /etc/hosts file.

Flags: The Flags field must be set to U (up) for every table entry

Interface: The Interface field shows the corresponding network driver interface. Make sure that this interface assignment agrees with your TCP/IP setup.

Note: The interface name varies depending on the operating system and adapter that you are using.

Enter

Enter


62

Verifying Remote Database Access ConfigurationTo synchronize the data from the primary to the Backup Host, the database must be configured correctly. Check the following files on both hosts to verify the configurations.

Make sure that the following entry appears in the etc/services file for each host. (If the entry is missing, type it in manually by using a text editor.)

Verifying Table IDsMake sure the database is running before checking these tables.

To verify the database table IDs:

1. Log on to the primary and Backup Hosts as ppadmin, and then open a terminal window.

2. Type the following command to start the database:

oninit

3. Type the following commands consecutively on the Primary Host, and then on the Backup Host:

query system_config query host

There should be one row in the system_config table and two rows in the query host table as shown in Figure 8, Verifying table IDs.

Figure 8. Verifying table IDs

4. Type the following command to stop the database:

onmode -ky

Table 15. Required File Entries for Remote Database Access

Service Name Port Number/Protocol Name Aliases Comments

<local_host>_star 9088/tcp star1 star2 # local_host Informix istar Port

<remote_host>_star 9088/tcp # Informix remote DB Port

Enter

Enter

Enter

1 NODE 1 0 65535 5250 6000 16000 805306368 805343248 256 100000 100000 200 50000 1000 50000 2 1 2 2 2 2 0 2 3 0 1 00000 59 -99 25 50 eirs2cr -t0 -c180 -k Y Y Y Y Y Y Y 500 6 64 96 1 500 1 40 <bid>,<last_name>,<first_name> 0 0 0 96 32 1 1 /ppbackup 60 /cas/flash/eflash 6 1 1 0 0 0 1 1 1 1 1 1 /ppbackup 0 0 1 0 20081114 120000

[ppadmin@bctottawa ~]$ query host

1 9003 bctottawa 3.137.174.215 192.100.100.1 0 5 5 30 29 30 Y -1 20090812 134807

2 9004 bctwunan 3.137.174.214 192.100.100.2 1 5 5 30 29 30 Y -1 20090812 134807

Enter


63

Verification of Hosts Time SynchronizationPicture Perfect uses Network Time Protocol (NTP) to synchronize computer clock times in a network of computers. NTP services are configured during the installation of the pprs package. NTP services are started when the operating system boots up. The Picture Perfect Primary Server is designated as the master time-keeper and runs the NTP service as Server.

Note: The NTP service cannot synchronize server times if the server times are more than 1000 seconds apart.

chkdbsyncThis utility lists the tables on the primary and Backup Hosts that are refreshed by the system. For each table, it lists the record count (COUNT) and the maximum value in the id field (MAXID). The respective numbers should be the same for the Primary Host and the Backup Host. For example, if the COUNT is 35 on the Primary Host, it should be 35 on the Backup Host. If there is a discrepancy, then that table is not in sync.

To run the chkdbsync utility:

1. Log onto the Primary Host as root, and then open a terminal window.

2. At the command prompt, type:

. /cas/bin/profile chkdbsync


TABLE COUNT MAXID--------------------------------------------------------------------Number of alarm on bctottawa [Primary] 23 22Number of alarm on bctwunan [Backup] 23 22--------------------------------------------------------------------Number of alarm_history on bctottawa [Primary] 3 3Number of alarm_history on bctwunan [Backup] 3 3--------------------------------------------------------------------Number of notes on bctottawa [Primary] 0 0Number of notes on bctwunan [Backup] 0 0--------------------------------------------------------------------Number of time_zone on bctottawa [Primary] 498 1096Number of time_zone on bctwunan [Backup] 498 1096--------------------------------------------------------------------

Enter

Enter


64

This chapter includes the information needed to remove the Picture Perfect Redundant System (PPRS) package.

Chapter 6 Removing PPRS


66

Removing PPRSIf you intend to remove PPRS permanently (you do not intend to reinstall it), remove only the PPRS package. If, however, you intend to reinstall PPRS, you must remove any other packages installed on the system (with the exception of the base Picture Perfect package), then PPRS. Packages must be removed from the Primary Host before removing them from the Backup Host.

To remove PPRS:


2. Stop PPRS by typing the following command:

pprscmd stop


su -


4. Start the removal program by typing:ppr

Output similar to the following displays:Picture Perfect Package Removal - /custom_pp/bin/ppr 4.6 04/10/11Copyright (C) 2011 UTC Fire & Security Americas Corporation, Inc.WARNING: THIS PROGRAM WILL COMPLETELY REMOVE PICTURE PERFECT PACKAGESAND ANY DATABASES USED BY THE PACKAGE.SELECTING 'base' OR 'all' WILL REMOVE PICTURE PERFECT ENTIRELY.ARE YOU SURE YOU WANT TO PROCEED?

5. To continue, type yes If you entered yes, a list of the Picture Perfect packages currently installed is displayed. You are then asked which package you want to delete.

The following Picture Perfect packages are currently installed:basepprsEnter the name of the package to remove:

Type: pprs

Output similar to the following displays:Enter the name of the package to remove: pprsRemoving the pprs package.-------------------------------------------------------------------- Picture Perfect PPRS Package Removal - Version 4.6.0 05/20/11 Copyright (C) 2011 UTC Fire & Security Americas Corporation, Inc.--------------------------------------------------------------------Checking for Local database parameters [Done]Checking for Remote server connectivityStarting Local database [Done]Deleting pre-existing FPP input groups and alarms.Stopping the Informix database...Picture Perfect Redundant System package Removal completed successfullyThe removal process has completed. Program Exiting.The system needs to be rebooted for the changes to take affect.Reboot the system (y/n)? [y]

6. Press to reboot the system.

Following the reboot, Picture Perfect starts automatically as a standalone configuration. See Cleaning the online.log after pprs is removed on page 73.

Enter

Enter

Enter

Enter

Enter

Enter

Enter

This chapter includes information helpful in troubleshooting your redundant system and offers technical support contacts in case you need assistance.

In this chapter:

General Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Default onconfig file parameters . . . . . . . . . . . . . . . . . . . . . . 68PPRS commands to determine the database state . . . . . . . 69Monitor the logical log archive process. . . . . . . . . . . . . . . . . 72Complete database recovery . . . . . . . . . . . . . . . . . . . . . . . . 72Failure to recover database . . . . . . . . . . . . . . . . . . . . . . . . . 72Cleaning the online.log after pprs is removed . . . . . . . . . . . 73

Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Chapter 7 Troubleshooting


68

General TroubleshootingTo troubleshoot your Picture Perfect Redundant configuration, it is recommended that you verify your configuration first. Refer toChapter 5, Verifying the Configuration on page 49.

Default onconfig file parameters

To configure High Availability Data Replication (HDR) properly, the onconfig file should contain the following parameters.

Table 16. Onconfig file parameters

Parameter Value Description

TAPEDEV /ppbackup/db/ifxDBArch Informix database archive file

TAPESIZE 40960000 Kbytes Maximum space allowed for the database archive file

LTAPEDEV /ppbackup/db/ifxDBLogs Informix database logical log archive file

LTAPESIZE 10240000 Maximum space allowed for the database logical log archive file

DRINTERVAL 30 Poll time interval that Informix uses to move information from the Primary to the Backup Server (in sec.)

DRTIMEOUT 5 Default time delay before an alarm is initiated after a network interruption is detected (in sec.)

DRLOSTFOUND /cas/db/etc/dr.lostfound Directory that lost files are stored

DRAUTO 0 Default value that allows Picture Perfect application to manage failover by not allowing Informix to automatically failover in the event of a Primary Server crash

UPDATABLE_SECONDARY 4 Allows customer to write to the Backup Server database

Chapter 7Troubleshooting

69

PPRS commands to determine the database state

The following commands assist in determining the state of the database in your redundant system.

dbmode

This shell script was written specifically for redundant systems. It can display the current or previous mode of the local database, start the database in certain modes, or stop the database.

Sample usage of dbmode (See Table 17, dbmode variables.):

dbmode -m <primary|secondary|standard> [-h hostname]dbmode <-i|-k|-s|-v>dbmode <-?>

onstat

This Informix command provides specific information of the database such as: database type, mode and state for HDR, SQL commands being executed, sessions running, and DB Space data.

Sample usage 1

Type the following command:

onstat -g dri

This command provides the current redundant configuration of the server as shown below.

IBM Informix Dynamic Server Version 11.50.UC3 -- On-Line (Pri) -- Up 02:14:58 -- 759532 KbytesData Replication: Type State Paired server Last DR CKPT (id/pg) Supports Proxy Writes primary on bctorlando 25 / 3404 N/A DRINTERVAL 30 DRTIMEOUT 5 DRAUTO 0 DRLOSTFOUND /cas/db/etc/dr.lostfound DRIDXAUTO 0 ENCRYPT_HDR 0

Table 17. dbmode variables

Variable Description

-h <hostname> Specifies the remote hostname.

-i Displays information about the Informix database.

-k Stops the Informix database if it is running.

-m <mode> Places the Informix database into an HDR replication mode (primary, backup, or standard).

-s Starts the Informix Database if it is not running

-v Display verbose information.

-? Displays this help screen.


70

Note the following column heading definitions:

Type: Lists how the Informix database was configured for startup (primary, backup, or standard).

Database state: The database can only be in one of two states once it is started, as shown in Table 18

Paired server: Lists the name of the remote database server.

Database mode: Depending on how the database is started or the process that it is executing, Table 19 provides a list of different states you can find the database in.

Sample usage 2

Type the following command:

onstat -g iof

This command provides disk activity information during a recovery process as shown below.

IBM Informix Dynamic Server Version 11.50.UC3 -- On-Line (CKPT INP) -- Up 02 :07:46 -- 759532 KbytesAIO global files:gfd pathname bytes read page reads bytes write page writes io/s3 /dev/rrootdbs 1323008 646 18432 9 558.4 op type count avg. time seeks 0 N/A reads 0 N/A writes 0 N/A kaio_reads 503 0.0017 kaio_writes 8 0.0053

Table 18.Database states

State Description

Off Describes a communication state with the paired server, usually found in Standard mode (no pair) or when Primary/Backup do not communicate.

On Describes a proper communication status between Primary and Backup servers.

Table 19.Database modes

Mode Description

On-Line Describes a Read/Write database, usually found in Standard and Primary Servers.

Read-Only Describes a server that has been set up as Backup Server.

Updatable Describes a server defined as Secondary that accepts update events to the database.

Fast Recovery State in which the database is recovering last Logical Logs for synchronization, usually found in Backup Servers or during start up process for few seconds.

Quiescent Single user mode, usually set manually or found temporarily during the process of switching modes.


71

Sample usage 3

The onstat -l command provides vital information about the Logical Log archiving process.

This command returns a report, among others, of the current flags for every Logical Log in the database. For every Logical log listed in the report, except the currently one used, marked as "U---C--" or "U---C--", the flags must show a B in the third flag reported as "U-B----" or "U-B---L", where U = used, B = Backed up, C = Current, and L = Check point.

Type the following command to monitor the Logical Log Archive process in Primary database server:

onstat -l

This command shows the logical log configuration of the database as shown below.

IBM Informix Dynamic Server Version 11.50.UC3 -- Updatable (Sec) -- Up 2 days 20:55:20 -- 157504 KbytesPhysical LoggingBuffer bufused bufsize numpages numwrits pages/io P-1 2 32 54957 1841 29.85 phybegin physize phypos phyused %used 1:263 16000 9456 2 0.01Logical LoggingBuffer bufused bufsize numrecs numpages numwrits recs/pages pages/io L-1 0 32 0 0 0 0.0 0.0 Subsystem numrecs Log Space usedaddress number flags uniqid begin size used %used368e9fd0 17 U-B---- 185 4:53 10240 10240 100.00367b0b80 18 U-B---- 186 4:10293 10240 10240 100.00367b0bc8 19 U-B---- 187 4:20533 10240 10240 100.00367b0c10 1 U-B---- 188 4:30773 10240 10240 100.00367b0c58 2 U-B---- 189 4:41013 10240 10240 100.00367b0ca0 3 U-B---- 190 4:51253 10240 10240 100.00367b0ce8 4 U-B---- 191 4:61493 10240 10240 100.00367b0d30 5 U-B---- 192 4:71733 10240 10240 100.00367b0d78 6 U-B---- 193 4:81973 10240 10240 100.00367b0dc0 7 U-B---- 194 4:92213 10240 10240 100.00367b0e08 8 U-B---- 195 4:102453 10240 10240 100.00367b0e50 9 U-B---- 196 4:112693 10240 10240 100.00367b0e98 10 U-B---- 197 4:122933 10240 10240 100.00367b0ee0 11 U-B---- 198 4:133173 10240 10240 100.00367b0f28 12 U-B---- 199 4:143413 10240 10240 100.00367b0f70 13 U-B---- 200 4:153653 10240 10240 100.00367b0fb8 14 U-B---- 201 4:163893 10240 10240 100.00372f9018 15 U-B---- 202 4:174133 10240 10240 100.00372f9060 16 U-B---- 203 4:184373 10240 10240 100.00372f90a8 20 U-B---- 204 4:194613 10240 9902 96.70372f90f0 21 U---C-L 205 4:204853 10240 95 0.93372f9138 22 U-B---- 182 4:215093 10240 10240 100.00372f9180 23 U-B---- 183 4:225333 10240 10240 100.00372f91c8 24 U-B---- 184 4:235573 10240 10240 100.00 24 active, 24 total


72

Note the following column heading definitions:

flags: F = free, U = used, B = backed up, C = check point, L = current

size: Allocated size for the logical log in Informix Page units. Linux = 2048 bytes, AIX = 4096 bytes

used: Space used by logical logs in Informix Page units.

%used: Percentage of the space used by logical logs in Informix Page units.

Monitor the logical log archive process

Logical Log archiving is automatically performed by the Picture Perfect system. The drarchlog command allows you to make sure that the logical logs that are storing database activity are properly archived.

Run the command ps -e | grep drarchlog. Text similar to the following displays.

$ ps -ef | grep drarchlogppadmin 532674 475196 0 09:37:55 pts/0 0:00 /bin/ksh /cas/bin/drarchlog -s$ ps -ef | grep drarchlogppadmin 610546 475196 8 09:41:15 pts/0 0:00 /bin/ksh /cas/bin/drarchlog -a

Complete database recovery

If your normal database recovery process (pprscmd recover) fails to run, use the following command to force a complete recovery of the database.

pprecover -L 0 (the number zero)

Failure to recover database

Check the size of your database backup directory (default /ppbackup) using the following command:

df -k

If the backup directory is at 100% usage, increase the size of the file system.

root@bctottawa# df -kFilesystem 1K-blocks Used Available Use% Mounted on/dev/mapper/rootvg-LogVol00 4951688 338448 4357652 8% //dev/mapper/rootvg-LogVol05 7935392 149196 7376596 2% /ppbackup/dev/mapper/rootvg-LogVol03 6919612 1545028 5017416 24% /usr/dev/mapper/rootvg-LogVol04 4761160 226944 4288456 6% /var/dev/mapper/rootvg-LogVol01 571320 16856 524976 4% /home


73

Cleaning the online.log after pprs is removed

After removing the PPRS packages from the Primary and Backup hosts (see Removing PPRS on page 66), the hosts still try to communicate and connect as Primary and Backup servers. These communication attempts do not impact the performance, i.e., the Primary will work as a Standalone server for the database as long as the Backup server is removed. However, the online.log will show repeated error messages, such as Trying to connect to secondary server = bctpantera and Cannot connect to secondary server. To remove these error messages, follow the steps below after the pprs package is removed from the Primary and Backup servers:

1. On the Primary server, open a terminal session and log in as root or Informix (if super user access is not available).

2. To verify that the pprs package is indeed removed, type the following command:

plevel

3. View the /cas/db/log/online.log Informix log file and search for messages indicating that the Primary server is still trying to connect to the old Backup server.

4. If messages related to Primary server connection attempts are found in the Informix log file, type the following command from the command line:

onmode -d standard

5. Check the Informix log file again and verify that messages related to Primary server connection attempts do not occur anymore.

6. To make sure the database is set back to Standard (Standalone), type the following command:

onmode -g dri

Check the resulting output for Type to be standard and State to be off as shown below.

==========================================================================================IBM Informix Dynamic Server Version 11.50.UC8X4GE -- On-Line-- Up 00:00:10 -- 759924 Kbytes Data Replication at 0x37087018: Type State Paired server Last DR CKPT (id/pg) Supports Proxy Writes standard off -1 / -1 NA DRINTERVAL 30 DRTIMEOUT 30 DRAUTO 0 DRLOSTFOUND /cas/db/etc/dr.lostfound DRIDXAUTO 0 ENCRYPT_HDR 0 Backlog 0==========================================================================================


74

Contacting Technical SupportFor assistance installing, operating, maintaining, and troubleshooting this product, refer to this document and any other documentation provided. If you still have questions, you may contact technical support during normal business hours (Monday through Friday, excluding holidays, between 8 a.m. and 7 p.m. Eastern Time).

North America

T 888 437 3287

F 561 998 6224

Asia

T 65 639 19314

F 65 639 19306

Australia

T 61 3 9239 1200

F 61 3 9239 1299

Canada

T 800 267 6317

F 613 737 5517

EMEA

T 48 58 326 22 40

F 48 58 326 22 41

Latin America

T 503 691 7294

F 561 994 6572

Email: [email protected]

Web site: www.utcfireandsecurity.com

75

Index

A

Alarm Monitors........................................................................................3

B

Backup .............................................................................................11, 14

Backup Host ...2, 4, 5, 8, 9, 11, 14, 17, 19, 22, 23, 25, 26, 30, 33, 39, 50, 54, ......................................................56, 62, 63

Backup Phone ................................................................................26, 27

C

chkdbsync..............................................................................................63

chkredundant ..................................................................................50, 53

command line utility .............................................................................32

configuration utility ...............................................................................32

conventions .............................................................................................v

D

Database Recovery .......................................................................39, 40

Database Synchronization ..............................................................2, 39

dbmode ..................................................................................................69

Disable Failover ....................................................................................43

Disable-Failover......................................................................................4

Double Modem .....................................................................................26

Double Modem Configuration ............................................................25

dual-network configuration..................................................................57

E

Ethernet .............................................................................................8, 10

F

Failover ..............................................................................4, 5, 30, 33, 38

Failover Event Sequence ....................................................................42

Failover Operation..................................................................................4

H

Hardware Requirements .......................................................................2

HDR ..........................................................................................................3

Heartbeat .................................................................................................3

heartbeat................................................................................................33

High Availability Data Replication (HDR) .........................................68

I

Informix ............................................11, 14, 15, 17, 21, 54, 55, 56, 57, 62

L

Local Host....................................................................................8, 33, 53

logical log archive.................................................................................72

M

Manual Failover ....................................................................................30

Max Allowable Xoff Time ....................................................................33

Min Free Shared Mem.........................................................................33

Modem Configuration ..........................................................................25

N

Network Micro Configuration ..............................................................27

Network Status .....................................................................................38

O

Onconfig ................................................................................................68

onstat......................................................................................................69

P

Polling Frequency ................................................................................33

Port Configuration ................................................................................24

ppadmin .................................................................................................11

PPRS......................................................................................................30

PPRS Command Utility (pprscmd) ......................................................3

PPRS monitor .......................................................................................37

pprscmd config .....................................................................................32

pprscmd config (configuration utility) ................................................32

pprscmd recover...................................................................................35

pprscmd utility .......................................................................................32

preface .....................................................................................................v

Primary Host .............3, 5, 8, 9, 11, 13, 15, 19, 21, 22, 23, 25, 39, 40, 63

Primary Phone ................................................................................26, 27

R

Remote Host .........................................................................8, 33, 53, 54

Rolled History Table ............................................................................24


76

S

safety terms and symbols .....................................................................v

Seed Counter........................................................................................53

Signal Splitter..........................................................................................5

start/stop PPRS ....................................................................................33

Static Routing Table ............................................................................61

System Mode ........................................................................................38

System Status...................................................................................3, 38

T

Takeover ......................................................................................4, 33, 38

Takeover event sequence ..................................................................43

Takeover Operation ...............................................................................4

TCP/IP..........................................................................................9, 10, 61

technical support ..................................................................................74

TPS.......................................................................................54, 55, 56, 57

V

Verifying host table against /etc/hosts ..............................................54

Verifying host times..............................................................................54

Verifying Informix is running ...............................................................53

Verifying Network Connection............................................................53

Verifying Network Connections..........................................................54

Verifying Operating System Type......................................................53

Verifying Picture Perfect......................................................................54

Verifying Remote Connectivity ...........................................................53

Verifying Remote Database Connectivity.........................................53

Verifying Seed Counter Settings .......................................................53

Verifying system_config count ...........................................................54

Verifying TPS is running......................................................................53

Verifying /etc/hosts...............................................................................54

Verifying /etc/hosts Pri & Sec Consistency ......................................54

Verifying /etc/services..........................................................................54

Symbols

.netrc ......................................................................................................59

Documents

Picture Perfect 4.6 Redundant Edition User Manualpartner.lenel.com/file/casi/pp/460134011A.pdf · System Status Information ... Port configuration for dial-up micros ... Since Picture