Lucent Technologies CentreVu Release 3 Version 8 High... User manual

585-210-931
Comcode 108502204
Issue 1
June 2000
CentreVu
Call Management System
Release 3 Version 8
High Availability User Guide

Copyright© 2000 Lucent Technologies
All Rights Reserved
Printed in U.S.A.
Notice
Every effort was made to ensure that the information in this document was
complete and accurate at the time of printing. However, information is
subject to change.
Your Responsibility for Your System’s Security
Toll fraud is the unauthorized use of your telecommunications system by
an unauthorized party, for example, persons other than your company’s
employees, agents, subcontractors, or persons working on your
company’s behalf. Note that there may be a risk of toll fraud associated
with your telecommunications system and, if toll fraud occurs, it can result
in substantial additional charges for your telecommunications services.
You and your system manager are responsible for the security of your
system, such as programming and configuring your equipment to prevent
unauthorized use. The system manager is also responsible for reading all
installation, instruction, and system administration documents provided
with this product in order to fully understand the features that can
introduce risk of toll fraud and the steps that can be taken to reduce that
risk. Lucent Technologies does not warrant that this product is immune
from or will prevent unauthorized use of common-carrier
telecommunication services or facilities accessed through or connected to
it. Lucent Technologies will not be responsible for any charges that result
from such unauthorized use.
Lucent Technologies Fraud Intervention
If you
suspect that you are being victimized by toll fraud and you need
technical support or assistance, call Technical Service Center Toll Fraud
Intervention Hotline at 1-800-643-2353.
Canadian Department of Communications (DOC)
Interference Information
This digital apparatus does not exceed the Class A limits for radio noise
emissions set out in the radio interference regulations of the Canadian
Department of Communications.
Le Présent Appareil Nomérique n’émet pas de bruits radioélectriques
dépassant les limites applicables aux appareils numériques de la class A
préscrites dans le reglement sur le brouillage radioélectrique édicté par le
ministére des Communications du Canada.
Trademarks
CentreVu and DEFINITY are registered trademarks of Lucent
Technologies.
Sun, Sun Microsystems, SunOS, the Sun logo, Solaris, Solstice, Solstice
DiskSuite
, Enterprise, and Ultra are trademarks or registered trademarks
of Sun Microsystems, Inc.
Exatape is a trademark of Exabyte Corporation.
INFORMIX is a registered trademark of Informix Software, Inc.
All other product names mentioned herein are the trademarks of their
respective owners.
Ordering Information
Call: Lucent Technologies Publications Center
Voice: 1-800-457-1235
International Voice: [phone]
Fax: [phone]
International Fax: [phone]
Write: Lucent Technologies Publications Center
P.O. Box 4100
Crawfordsville, IN 47933
U.S.A.
Order: CentreVu CMS R3V8 High Availability Connectivity, Upgrade and
Administration
Document No. 585-210-931
Comcode 108502204
Issue 1, June 2000
For additional documents, refer to the section entitled “Related
Documents” in the Preface.
You can be placed on a Standing Order list for this and other documents
you may need. Standing Order will enable you to automatically receive
updated versions of individual documents or document sets, billed to
account information that you provide. For more information on Standing
Orders, or to be put on a list to receive future issues of this document,
please contact the Lucent Technologies Publications Center.
Lucent Technologies National Customer Care Center
Lucent Technologies provides a telephone number for you to use to report
problems or to ask questions about your call center. The support
telephone number is 1-800-242-2121.
Document Support Telephone Number
Lucent Technologies provides telephone numbers for you to use to report
errors or to ask questions about the information in this document. The
support telephone numbers are:
Voice: 1-888-584-6366 and
International Voice: [phone].
European Union Declaration of Conformity
Lucent Technologies Business Communications Systems declares that
the equipment specified in this document conforms to the referenced
European Union (EU) Directives and Harmonized Standards listed below:
EMC Directive 89/336/EEC
Low Voltage Directive 73/23/EEC
The “CE” mark affixed to the equipment means that
it conforms to the above Directives.
Heritage Statement
Lucent Technologies—formed as a result of AT&T’s planned
restructuring—designs, builds, and delivers a wide range of public and
private networks, communication systems and software, consumer and
business telephone systems, and microelectronics components. The
world-renowned Bell Laboratories is the research and development arm
for the company.
Comments
To comment on this document, return the comment card at the front of the
document.
Acknowledgment
This document was developed by the Lucent Technologies Information
Development Organization for Global Learning Solutions.

Table of Contents
CentreVu® Call Management System
Release 3 Version 8
High Availability Connectivity, Upgrade and Administration
CentreVu CMS R3V8 High Availability User Guide
iii
Preface . . . . . . . . . . . . . . . . . . . . . . . . P-1
Overview . . . . . . . . . . . . . . . . . . . . . P-1
Scope . . . . . . . . . . . . . . . . . . . . P-1
Organization . . . . . . . . . . . . . . . . . P-1
Conventions . . . . . . . . . . . . . . . . . P-2
Related Documents . . . . . . . . . . . . . . P-2
If you have a problem . . . . . . . . . . . . . . P-2
Provide information . . . . . . . . . . . . . . P-3
1: Introduction . . . . . . . . . . . . . . . . . . . . . . . 1-1
Overview . . . . . . . . . . . . . . . . . . . . . 1-1
HA Server Switch-over After a Failure Event. . . . . . . . 1-1
Dual ACD Links . . . . . . . . . . . . . . . . . 1-3
Hardware Platforms . . . . . . . . . . . . . . . . 1-4
R3V8 Feature Enhancements . . . . . . . . . . . . . 1-4
Increased Data Availability . . . . . . . . . . . . . 1-5
2: Primary and Secondary CMS Servers . . . . . . . . . . . . . . . 2-1
Primary versus Secondary CMS servers . . . . . . . . . . 2-1
CMS HA Server Maintenance . . . . . . . . . . . . . 2-2
CMS Recovery Kit . . . . . . . . . . . . . . . . 2-3
Purpose . . . . . . . . . . . . . . . . . . 2-3
Recovery kit contents . . . . . . . . . . . . . . 2-3
Recovery kit software components . . . . . . . . . 2-3
Connectivity Considerations for CMS Server Switch-Overs. . . 2-4
Admin operations that are auto-synchronized by the switch . . 2-5
Admin operations that require manual synchronization . . . . 2-5
Admin operations synchronized by backups and restores. . 2-7
Operations that require data collection to be turned off . . . . 2-8

CentreVu CMS R3V8 High Availability User Guide
iv
3: User Scenarios . . . . . . . . . . . . . . . . . . . . . . 3-1
Agent Trace - Modification . . . . . . . . . . . . . 3-1
Base Load Upgrades with High Availability . . . . . . . . 3-1
Call Work Codes . . . . . . . . . . . . . . . . . 3-2
Change Agent Skills . . . . . . . . . . . . . . . . 3-2
Custom Reports . . . . . . . . . . . . . . . . . 3-2
Designer Reports. . . . . . . . . . . . . . . . . 3-3
Dictionary Changes . . . . . . . . . . . . . . . . 3-4
Exceptions . . . . . . . . . . . . . . . . . . . 3-7
External Call History - Turning on and off. . . . . . . . . 3-8
Forecast Data Storage Allocation Administration . . . . . . 3-9
Forecasting Report Data, Administration . . . . . . . . . 3-9
Main Menu Additions . . . . . . . . . . . . . . . 3-10
Printers . . . . . . . . . . . . . . . . . . . . 3-10
Scripting . . . . . . . . . . . . . . . . . . . 3-10
Shortcuts . . . . . . . . . . . . . . . . . . . 3-10
Split/Skill Call Profile Setup . . . . . . . . . . . . . 3-11
Synchronizing the CMS servers after turning
Data Collection On/Off . . . . . . . . . . . . . . . 3-12
Timetables – Running only on the Primary server . . . . . . 3-16
Timetables – Running on both Primary and Secondary servers . 3-17
Timetables – Global edits to change server ownership . . . . 3-18
Users - Adding or modifying . . . . . . . . . . . . . 3-20
Users - Removing . . . . . . . . . . . . . . . . 3-20
Users - Setting User Passwords. . . . . . . . . . . . 3-21
VDN Call Profile Administration . . . . . . . . . . . . 3-21
Visual Vectors - Vector Changes. . . . . . . . . . . . 3-22
4: High Availability Backup & Restore Strategy. . . . . . . . . . . . . 4-1
High Availability Backup Strategy. . . . . . . . . . . . . 4-1
Synchronizing after an unscheduled outage of the
Primary CMS server . . . . . . . . . . . . . . . . 4-1
Synchronizing after an unscheduled outage of the
Secondary CMS server . . . . . . . . . . . . . . . 4-2

CentreVu CMS R3V8 High Availability User Guide
v
A: Backup & Restore Procedures . . . . . . . . . . . . . . . . . A-1
CMS Backup Strategy. . . . . . . . . . . . . . . . . A-1
Labeling the backup volume . . . . . . . . . . . . . A-1
Backup information format . . . . . . . . . . . . A-2
How to interpret backup information . . . . . . . . . A-2
B: Items excluded from a CMSADM backup . . . . . . . . . . . . . . B-1
C: Items backed up during a Full Maintenance backup . . . . . . . . . . C-1
D: Restore Characteristics of Different Data Types . . . . . . . . . . . D-1
E: What to do if a CMS Server Fails. . . . . . . . . . . . . . . . . E-1
F: Frequently Asked Questions . . . . . . . . . . . . . . . . . . F-1
G: CMS Base Load Upgrade Procedure for High Availability Systems . . . . . G-1
Index . . . . . . . . . . . . . . . . . . . . . . . . IN-1

CentreVu CMS R3V8 High Availability User Guide
vi

Preface CentreVu CMS R3V8 High Availability User Guide
Overview P-1
Preface
Overview 0
This document is written for customers who purchase the High
Availability feature of the CentreVu® Call Management System(CMS).
Scope 0This document contains a variety of procedures to help you maintain your
CMS High Availability system. It assumes a minimum level of technical
knowledge on the part of its readers to complete the procedures. It
assumes, for example, that the reader knows how to perform backup and
restore procedures for the CMS system. Where necessary, this
document refers to other CMS documentation which describe how to
perform basic CMS procedures.
Organization 0This document includes the following topics:
●Introduction
Provides an overview of the new dual ACD links feature and R3V8
CMS High Availability
●Primary and Secondary CMS Servers
Describes the two CMS servers and how to synchronize the data
between them
●User Scenarios
Describes step by step procedures to complete the most common
High Availability scenarios you will encounter
●High Availability Backup & Restore Strategy
Explains the High Availability backup and restore strategy and lists
step by step procedures to complete backup and restore procedures
Backup & Restore Procedures
Items excluded from a CMSADM backup
Items backed up during a Full Maintenance backup
Restore Characteristics of Different Data Types
What to do if a CMS Server Fails
Frequently Asked Questions
CMS Base Load Upgrade Procedure for High Availability Systems

Preface CentreVu CMS R3V8 High Availability User Guide
Overview P-2
Conventions 0The following conventions are used in this document:
●Unless otherwise specified, all information and procedures in this
document apply to the Sun Enterprise 3000, Sun Enterprise 3500,
and Ultra5 computers. They will be referred to as the “CMS server.”
●Commands you enter from the console are shown in courier font.
Related Documents0To order any of these documents, call the Publications Center at 1-800-
457-1235, or 1-317-361-5353.
●
CentreVu CMS R3V8 Upgrades and Migrations (585-210-913)
●
CentreVu CMS R3V8 Software Installation & Setup (585-210-941)
●
CentreVu CMS R3V8 Switch Connections and Administration (585-
215-876)
●
CentreVu CMS R3V8 Change Description (585-210-925)
●
CentreVu CMS R3V8 External Call History Interface (585-210-912)
If you have a
problem 0
If you have a problem with a CentreVu® CMS High Availability
configuration, call the Lucent Technologies Customer Care Helpline at
[phone] to report the problem and obtain a case number. For
customers outside the United States and Canada, please contact your
local Lucent distributor or representative.
The Customer Care Helpline is staffed by trained CentreVu® CMS
technicians at the Technical Service Center (TSC). The technicians at
the TSC will try to fix your problem in a timely manner. If they cannot fix
it, they will escalate the problem to a higher level of customer support.

Preface CentreVu CMS R3V8 High Availability User Guide
Overview P-3
Provideinformation0When you call the Helpline, be sure to identify yourself as a CentreVu®
CMS High Availability customer and be prepared to give the following
information:
●Your full name, your organization, and a phone number where a
Lucent Technologies representative can contact you about the
problem
●The installation location (IL) number
The IL number is a 10-digit number from a Lucent Technologies
database that helps identify the details of your CentreVu® CMS
High Availability installation and environment .
●Your ACD and CMS release information
●Whether the problem is with the Primary CMS server or the
Secondary CMS server
●CPU type and speed
●Microsoft Windows operating system version (if using CentreVu
Supervisor)
●A description of the problem
●The type of service contract your organization has with Lucent
Technologies, if any.
●Whether you have a Professional Services contract related to the
High Availability option.
If your system is not covered by warranty or a service contract, you
will be invoiced for the Helpline troubleshooting. A service contract
may provide coverage for business hours only or for 24-hours a day,
7 days a week. Alternatively, the contract may provide you with a
technician dedicated to your installation. If you are uncertain about
the details or expiration date of your service contract, contact you
Lucent Technologies representative.

Preface CentreVu CMS R3V8 High Availability User Guide
Overview P-4

Introduction CentreVu CMS R3V8 High Availability User Guide
Overview 1-1
Chapter 1: Introduction
Overview 1
The primary purpose of the CMS High Availability offer is to ensure an
uninterrupted data stream between the DEFINITY ECS and the CMS
system, which is achieved by connecting two CMS servers at one site to
one DEFINITY® system, thereby eliminating the traditional single point of
failure between the CMS and the DEFINITY system.
Both CMS servers collect data from the DEFINITY®, but they operate
completely independently and are not even aware of each other. With
few exceptions (which will be discussed indetail later), both CMS servers
provide full CMS capabilities. Should either server fail, lose connection to
the DEFINITY®, or need to be brought down for maintenance, the
alternate server can carry the entire CMS activity load. Note that both
CMS servers have to be administered with identical CMS Setup (number
of ACDs in the configuration, data storage allocation, users, features,
etc.).
The High Availability offer relies heavily on manual data synchronization
between the two CMS servers as well as manual administration
synchronization. Therefore, this document will discuss in detail
procedures you will follow to maintain synchronization between the two
CMS servers.
HA Server
Switch-overAfter
a Failure Event 1
For customers who require continuous access to their CMS data, HA
systems allow for the redirection of LAN traffic related to CMS clients and
peripheral devices from the primary server to the secondary server.
Switch-over from the primary server to the backup server can be
performed when the primary server experiences a major failure event.
However, an HA switch-over should be performed only when the
anticipated down time for the primary server is expected to be significant.
Also, since each call center network is configured according to its own
unique specifications, each HA customer must develop their own
customized plans to define their own criteria and requirements for
switch-over events.

Introduction CentreVu CMS R3V8 High Availability User Guide
Overview 1-2
The CMS HA option allows the following server switch-over options:
1. No switch-over
If you do not require continuous access to your CMS data, you can
elect not to switch-over to the secondary server after the primary
server experiences a major failure event. When the primary server
goes down, uninterrupted collection of call data will continue on the
secondary server, but you may not be able to access that data until
the primary server is restored.
2. Customized software switch-over
If the HA primary and secondary servers connect to CMS clients
and other peripherals, such as NTS servers, printers, etc. over the
same network subnet, LAN traffic on this “user” network can be
automatically redirected from the primary to the secondary server by
means of customized scripting tools set up by the Lucent
Professional Services Organization (PSO). The scripts create an
alias for the IP address of the primary server on the secondary
server.
3. Manual server switch-overs
If your HA servers do not connect to your user network over the
same subnet, the custom software switch-over solution offered by
the PSO can not be implemented. If you still require uninterrupted
access to CMS data, the server switch-over must be performed
manually.
At a minimum, manual switch-over entails the individual editing of
host configuration files on the secondary server and re-
administration of CMS supervisor clients by their individual users in
order to redirect them from the primary to secondary server. Also, if
the primary server is connected to one or more NTS servers,
significant effort may be required to manually switch the NTS
devices over to the secondary server. For more information about
manual server switch-overs, see “What to do if a CMS Server
Fails”.

Introduction CentreVu CMS R3V8 High Availability User Guide
Overview 1-3
Dual ACD Links 1Duplicate hardware is a key component of the High Availability system.
The function of the duplicate hardware is to eliminate a single point of
failure in order to prevent data loss due to hardware failures. The dual
ACD link feature addresses ACD link failures and builds on the increased
ACD link reliability provided by TCP/IP. The C-LAN card provides TCP/IP
connectivity between the DEFINITY® and the CMS server. Each ACD
link requires a separate C-LAN card and supports different network
routes to eliminate as many single points of failure as possible.
The ACD Call Processing software will send duplicate data to both CMS
servers simultaneously. Thus, both CMS servers will collect identical real-
time, historical, and call record data. Furthermore, both CMS servers will
be able to perform call center and agent administration, and the results
will be communicated from the DEFINITY® switch back to both CMS
servers. However, as we discuss in detail later, we strongly recommend
performing administrative functions from only the Primary CMS server.
An idealized schematic of the network links between each of the dual
ACD CLAN cards on a Definity ECS and their respective CMS HA
servers is shown in the following figure.
to customer
network
CMS Secondary
CMS Primary

Introduction CentreVu CMS R3V8 High Availability User Guide
Overview 1-4
Hardware
Platforms 1
CMS HA is supported on the following platform combinations:
●
Sun Ultra
*5 -
Ultra 5
●
Sun Enterprise
†
3000 - Enterprise 3000
●
Sun Enterprise 3500 - Enterprise 3000
●
Sun Enterprise 3500 - Enterprise 3500
Note:
●For HA systems in which
Enterprise 3000 and 3500 servers are
combined, the 3500 server should be designated as the primary HA
server
●for HA systems in which Ultra 5 and Ultra 5 Einstein servers are
combined, the Einstein server should be designated as the primary
server
R3V8 Feature
Enhancements 1
The following improvements have been madeto the standard R3V8 CMS
offer and apply to all standard R3V8 CMS platforms supported (i.e., not
just High Availability platforms). These new features were designed to
prevent data loss and improve system availability.
1. Non-disruptive cmsadm backup: Non-disruptive cmsadm
backup is the ability to perform a cmsadm backup with data
collection turned on during the entire cmsadm backup process.
Note that non-disruptive cmsadm
restores are not technically
feasible and will occur with data collection turned off and CMS
turned off. A CMSADM backup copies nearly all system directories
and files. For a list of those items excluded from a CMSADM
backup, see “Items excluded from a CMSADM backup”.
2. Manually synchronize the two CMS systems: The following
capabilities were incorporated into CMS to allow you to manually
synchronize two independent R3V8 CMS servers in a High
Availability configuration:
a. non-disruptive maintenance restores - non-disruptive
maintenance restores is the ability to perform any of the
maintenance restores (except for local system administration)
with data collection turned on during the entire maintenance
restore process.
* Ultra is a trademark of Sun Microsystems, Inc.
†
Enterprise is a trademark of Sun Microsystems, Inc.

Introduction CentreVu CMS R3V8 High Availability User Guide
Overview 1-5
b. non-disruptive R3 migration -non-disruptive R3 migration is the
ability to perform any of the R3 migrations with data collection
turned on during the entire migration process. R3 migration is
critical to synchronizing data during the upgrade process (e.g.,
R3V6 to R3V8 or R3V8.1 to R3V8.2 when database schema
changes are required).
3. Capability to turn External Call History (ECH) on and off: The
ECH feature can be independently started and stopped on the two
HA servers. How ECH is managed depends on your particular CMS
configuration:
●if you do not use any customized CMS reporting solutions
(developed by the PSO), ECH data should be active only on
the primary server under normal operating conditions. If the
primary server fails, ECH can be started on the other CMS
server.
●if you do use customized CMS reporting solutions developed
by the PSO, ECH data should be active on both CMS servers.
Consult with your PSO representative for details.
Increased Data
Availability 1
The R3V8 CMS High Availability offer builds on the availability and
serviceability improvements implemented in the standard R3V8 CMS
offer described above. Below is a summary of how the R3V8 CMS High
Availability offer increases the availability of your CMS data.
1. ACD link failures: In the recommended HA configuration, ACD
data is transmitted across different C-LAN cards within the
DEFINITY® and across different network subnets, thereby reducing
the number of potential single points of failure. If one ACD link fails,
data collection continues on the second R3V8 CMS server. You will
use the maintenance backup and restore process to recover the
missing data onto the R3V8 CMS server that was connected to the
down ACD link.
2. CMS hardware failures: The R3V8 CMS server is duplicated. If a
hardware failure occurs on one R3V8 CMS server, data collection
continues on the second R3V8 CMS server. You will use the
maintenance backup and restore process to recover the missing
data onto the R3V8 CMS server that failed. If the R3V8 CMS
system fails, you may need to restore the cmsadm backup. Since
the cmsadm backup can now be performed with data collection on,
it is more likely that you will have a good cmsadm backup and the
system can be recovered more quickly.

Introduction CentreVu CMS R3V8 High Availability User Guide
Overview 1-6
3. Power failures: The Primary and Secondary servers should be
separately connected to individual Uninterruptible Power Supplies
(UPS) on separate protected power circuits. This configuration
ensures that both servers will not be simultaneously disabled due to
a localized power failure. However, in the event of an extended
power outage, impacted servers should be powered down in order
to prevent UPS failure and consequent possible data corruption on
the server.
4. CMS software failures: The R3V8 CMS application is duplicated. If
the CMS application fails or a CMS data collection process fails on
one R3V8 CMS server, data collection continues on the second
R3V8 CMS server. You will use the maintenance backup and
restore process to recover the missing data onto the R3V8 CMS
server with the software problems.
5. CMS maintenance: You will not lose data during either a cmsadm
backup or a maintenance backup. You will not lose data when
restoring a maintenance backup as long as you are not restoring
Local System Admin data.
6. CMS full version upgrades: In a High Availability configuration,
one CMS server continues to collect data while the other CMS
server is being upgraded to the new CMS version. After the first
CMS server is upgraded, data collection is turned on for the
upgraded CMS server. The second CMS server is then upgraded
while the upgraded CMS server continues with data collection
turned on. After the second CMS server is upgraded, data
collection is turned on for the second CMS server and the data is
restored between the two CMS servers. Note that if you upgrade
the DEFINITY® with a new release, the interval of data loss is
limited to the amount of time it takes to administer the latest Call
Center Release on the DEFINITY® and pump-up the ACD link. (See
the “Base Load Upgrades with High Availability”section later in this
document.)

Primary and Secondary CMS Servers CentreVu CMS R3V8 High Availability User Guide
Primary versus Secondary CMS servers 2-1
Chapter 2: Primary and Secondary CMS Servers
Primary versus Secondary CMS servers 2
When the CMS High Availability offer is installed at your location, you
designate one CMS server to be the “Primary” and the other as the
“Secondary”. It is highly recommended that you perform
administration only on the Primary CMS Server, and administer
from the Secondary CMS server only when the Primary is down. In
order to avoid possible confusion, the two servers should be clearly
labeled to indicate which is the primary and secondary.
The Primary and Secondary servers are essentially identical, except for
the following differences.
Both CMS servers collect data from the DEFINITY®, but they operate
completely independently and are not even aware of each other. Both
CMS servers provide full CMS capabilities except for the differences
listed above. Should either server fail, lose connection to the
DEFINITY®, or need to be brought down for maintenance, the alternate
server can carry the entire CMS activity load.
It is strongly recommended that you always perform administration
functions on one CMS server (designated the “Primary” CMS server) and
use the “Secondary” CMS server as a backup. Performing administration
on both servers could lead to synchronization problems and loss of
historical and/or admin data.
Primary CMS Server Secondary CMS Server
May have Internet Call
Center loaded Does not have Internet Call Center loaded
May have External Call
History turned on Does not have External Call History turned on
Has timetables turned on Timetables turned off, except for
incremental and full backup
timetables and any others you want
to run on both CMS servers. (See
the “Timetables – Running only on
the Primary server”section in this
guide for more details.)
Caution

Primary and Secondary CMS Servers CentreVu CMS R3V8 High Availability User Guide
Primary versus Secondary CMS servers 2-2
It is strongly recommended that no users are logged into the Secondary
CMS server while the Primary CMS server is operational. If the Primary
CMS server experiences a failure event, your ability to switch CMS users
over to the Secondary server will depend on your site-specific specific
switch-over strategy, as discussed in “HA Server Switch-over After a
Failure Event” on page 1.
The benefit to creating and following a routine where you always perform
administration on the Primary CMS server and transfer (synchronize) the
data to the Secondary CMS server is that you will be more likely to
synchronize your data correctly.
CMS HA Server
Maintenance 2
To assure that both CMS servers are healthy and able to accept and
process data from the DEFINITY ECS, it is strongly recommended that
the administrator, on a daily basis, perform the following functions on
both CMS servers:
1. Verify that all links to both CMS servers are up.
2. Verify that archiving is occurring on both CMS servers. To do this,
select Maintenance > Archiving Status from the CMS
menu; press Enter to access the action list in the top right corner of
the Maintenance: Archiving Status window, then press
Enter again to view archive status information for all ACDs.
3. To verify that daily backups have run, select Maintenance >
Backup Data from the CMS menu; at the top of the
Maintenance: Backup Data window, output similar to the
following example is displayed:
Backups completed today: 1
Status: Last backup finished at 05/02/00 00:23:41
4. Check the customer error log on both CMS servers for unusual
errors.
Note that these maintenance procedures are not new or in any way
unique to the CMS High Availability offer. You are probably already
accustomed to performing these maintenance procedures on your
existing CMS server.
Failure to adhere to the maintenance practices listed above may
result in unnecessary loss of CMS data and/or incur additional
administrative charges associated with Lucent Technical Support.
Caution
!WARNING:

Primary and Secondary CMS Servers CentreVu CMS R3V8 High Availability User Guide
Primary versus Secondary CMS servers 2-3
CMS Recovery
Kit 2
Purpose 2The recovery kit consists of the backup media and original software that
the Lucent Service organization needs to restore service to your system
when problems occur. Store this kit in a secure location to minimize the
time your system is out of service.
Recovery kit
contents 2
Your CMS recovery kit should include the following contents:
●the latest cmsadm file system backup tapes
●latest full maintenance backup tapes
●patching CDs and tapes
Recovery kit
software
components 2
A number of software packages are shipped with your CentreVu® CMS.
It is recommended that you store this software with the recovery kit.
The following table lists the required and optional software components
used in CMS R3V8, along with the HA server platforms to which they
apply (E3000, E3500, and
Ultra
*5).
* Ultra is a trademark of Sun Microsystems, Inc.
Software Component HAServer
Platform Required/ Optional
Sun Solaris 7 operating system (3/99 version) All Required
Sun Online Validation Test Suite (VTS) 3.1 All Required
Bay Networks Annex R10.0B drivers All Optional
INFORMIX
*Structured Query Language (SQL) Version 7.20
INFORMIX
†Standard Engine (SE) Version 7.22
INFORMIX
‡
Runtime Enhanced SQL (ESQL) Version 9.14
INFORMIX
§International Language Supplement (ILS)
All
All
All
All
Optional
Required
Required
Required
Solstice DiskSuite 4.2 software (found on the “ Solaris Easy Access
Server” CD). All Required
CMS Supplemental Services software All Required
CMS application software All Required

Primary and Secondary CMS Servers CentreVu CMS R3V8 High Availability User Guide
Primary versus Secondary CMS servers 2-4
Connectivity
Considerations
for CMS Server
Switch-Overs 2
For customers who require continuous access to their CMS data, HA
systems allow for the re-direction of LAN traffic related to CMS clients
and other peripheral devices. Switch-over from the primary server to the
backup server can be performed when the primary server experiences a
major failure event and the anticipated down time is expected to be
significant.
The time and effort required to accomplish an HA server switch-over
depends on your particular network configuration:
●if the primary and secondary server are linked to your user network
via a shared network subnet, the switch-over process can be
accomplished by use of customized scripts developed by the Lucent
Professional Services Organization (PSO). The custom scripts use
the IP alias address for the primary server and temporarily assign it
to the secondary server. This “software switchover” method enables
switch-overs to be accomplished in a manner that is both fast and
reliably error free. Co-location of the HA primary and secondary
servers on the same customer network is highly recommended
so that the switch-over scripts can be set up for use in server
switch-overs.
●if the primary and secondary server are linked to your user network
via different network subnets, the automated scripting method
(described above) can not be used for HA server switch-overs. In
this case, the switch from primary to secondary server must be done
manually. The amount of effort required for a manual CMS server
switch-over will depend on the nature of your network configuration
and the type and number of CMS client and peripheral devices to be
re-directed to the secondary server.
For issues and procedures associated with the switch-over from the
primary to the secondary HA server, see “What to do if a CMS Server
Fails” .
Open Database Connectivity (ODBC) software All Optional
Visual Vectors server software All Optional
* Informix is a registered trademark of Informix Software, Inc.
†
Informix is a registered trademark of Informix Software, Inc.
‡
Informix is a registered trademark of Informix Software, Inc.
§
Informix is a registered trademark of Informix Software, Inc.
Software Component HAServer
Platform Required/ Optional