Lucent Technologies Centrevu Release 3 Version 8 High Availability Connectivity, Upgrade And Administration Manual

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Migrating Administration Data Back Onto the Original Server3-71
3. Select the System Setup -> R3 Migrate Data option from the 
CMS main menu.
The System Setup: R3 Migrate Data  window is displayed. 
Select CMS administration data and Agent/Call center 
admin data  as data types and specify All ACDs for migration, as 
shown in the following example:
4. After you verify that the correct options are selected, press enter to 
access the action list in the top right corner of the window.
5. Select the Run option and press Enter.  The Status: field reports 
the progress of the migration. When the migration ends, Status: 
indicates the success or failure of the run.
6. Select System Setup - CMS State from the CMS main menu 
and select the Multi User Mode option.
7. Verify that data collection is on for all ACD links.
8. To print out the customer migration log, enter:
lp /cms/migrate/r3mig.log
For help interpreting the log and its messages, U.S. customers can 
telephone the Lucent National Customer Care Center at 
1-800-242-2121; international customers should contact their 
Lucent distributors or customer representatives.
The services migration log is stored in /cms/maint/r3mig/mig.log.
x
x
x 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Performing a New Full Maintenance Backup and Restore3-72
Performing a New Full Maintenance Backup and Restore3
These procedures create a full maintenance backup on the new HA 
server. The backup is then used to restore CMS historical data back onto 
the original server.
Performing the  
Full Maintenance 
backup on the 
new HA server
3
The required full maintenance backup copies all system data to tape. For 
details, see “Performing a Full Maintenance Backup” on Page 3-11
.
Note:
Assuming that the new HA server is used as the HA primary server, 
this backup represents the first tape to be archived for the new HA 
system. The other backup tapes used during the provisioning 
process may now be reused for nightly maintenance backups. 
Restoring 
historical data to  
the original 
server
3
This procedure copies historical data from the Full Maintenance backup 
created in the preceeding procedure.
 Procedure31. Insert the Full Maintenance Backup created on the new HA server 
into the tape drive on the original server.
2. Log in as a CMS user.
The CMS Main Menu is displayed. 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Performing a New Full Maintenance Backup and Restore3-73
3. From the main menu, select Maintenance > Restore Data 
The Maintenance: Restore Data window is displayed. In the 
Data to Restore fields, select the  Historical data and Non-
CMS data options, as illustrated in the following figure:  
4. After you verify that the correct restore options are selected, press 
enter to move the active cursor to the action box in the top right 
corner of the window, select the Run option and press enter.
Note:
If the customer does not have any Custom Report Tables set up by the 
PSO, the Maintenance: Restore Data window will display the following 
message when the restore is run:
Errors: Initialization errors. See Error Log. 
To view the Error Log, select Maintenance > Error Log from the 
CMS menu. The relevant log message should read as follows:
Restore process startup failed. Cannot restore non-CMS 
data because there are not tables in the database for 
that group.
These error messages can be ignored. 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Performing CMSADM Backups on the HA Servers3-74
Performing CMSADM Backups on the HA Servers3
Once both servers are fully operative, CMSADM backups must be 
performed on each server as soon as possible. The CMSADM file system 
backup saves all system files (excluding CMS call data). These backups 
must be stored in a safe place so they can be used to restore the system 
after a major system failure.
For a description of the CMSADM backup procedure, see “
Performing a 
CMSADM Backup” on Page 3-7. 
						

							  Administering the Switch for CMS High Availability Systems CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Overview4-1
Administering the Switch for CMS High Availability 
Systems4  
Overview4
Before a CentreVu® Call Management System (CMS) high availability (HA) 
system can collect and process Automatic Call Distribution (ACD) data from 
the 
DEFINITY® switch, a special hardware interface on the switch must be 
properly administered. Each switch can use a number of different interfaces 
to communicate to a CMS computer. 
The switch administration procedures described in this chapter apply to the 
following 
DEFINITY switches:
•Generic 3si (G3si) 
•Generic 3r (G3r) 
•Generic 3csi (G3csi) 
For additional information about switch administration, refer to the 
appropriate switch administration documents. 
Multiple ACDs 
(Switches) on 
HA Systems
4
If the customer has purchased the High Availability option, you must connect 
a link from one C-LAN circuit pack to one CMS computer, and a second link 
from a different C-LAN circuit pack to another CMS computer. 
In addition to having the correct CMS R3V8 load, the 
Definity switch must be 
optioned with a switch version of V8, Call Center Release of 8.1, and Adjunct 
CMS Release of R3V8, as specified below in “Determining Switch/CMS 
Compatibility” on Page 4-2.
The two CMS computers used in a dual server HA system can collect 
identical data from up to eight switches. From the perspective of the CMS 
computer, each switch represents one ACD. For HA systems, all switches 
connect to the servers via TCP/IP. The switch administration procedures 
shown in this chapter are applicable whether you are setting up one switch or 
eight switches; each switch requires a link to the CMS computer.
Setting Up Version and Release Values4
This section contains switch administration activities that must be done for all 
G3 switches (si, r, and csi) before you administer the switch-to-CMS 
computer link.  
						

							  Administering the Switch for CMS High Availability Systems CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up Version and Release Values4-2
Overview4Administrative procedures related setting up version and release values 
include: 
•setting the G3 Version on the System Parameters Customer 
Options form
•setting the Call Center Release on the System Parameters 
Customer Options form
•setting up the Adjunct CMS Release on the System Parameters 
Features form.
In addition, some basic CMS link administration is described in this 
section.
Determining 
Switch/CMS 
Compatibility
4
The following table reflects how you should set the G3 Version, Call 
Center Release, Adjunct CMS Release, and CMS Setup switch type 
based on the release of the switch. You can set the G3 Version, Call 
Center Release, or Adjunct CMS Release to an earlier version, but you 
will not have access to all of the features of the most recent release.
Switch ReleaseDEFINITY Switch AdministrationCMS 
Administration
G3 Version Call Center 
ReleaseAdjunct CMS 
ReleaseCMS Setup 
Switch Model
R8.x V8 8.1 R3V8 Definity-R8 
						

							  Administering the Switch for CMS High Availability Systems CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up Version and Release Values4-3
Setting the 
Switch Version
4
Use Page 1 of the System Parameters Customer Options form to set the 
switch version.
change system-parameters customer-options Page  1 of  X
OPTIONAL FEATURES
G3 Version: V8  Maximum Ports: 300
Location: 1  Maximum XMOBILE Stations: 0
Maximum H.323 Trunks: 0
Maximum H.323 Stations: 0
Maximum IPSoftPhones: 0
(NOTE: You must logoff & login to effect the permission changes.)
Field Definition
G3 Version To enable the HA option, enter V8 or later,
 
depending on the software release of the 
switch. If you set this field to an earlier 
release number, you will not have access to 
the latest switch features. 
						

							  Administering the Switch for CMS High Availability Systems CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up Version and Release Values4-4
Setting the Call 
Center Release
4
Use Page 4 of the System Parameters Customer Options form to set the 
Call Center Release. This is a new field introduced with R8.
change system-parameters customer-options Page  4 of  X
CALL CENTER OPTIONAL FEATURES
Call Center Release: 8.1
ACD? y  Reason Codes? y
BCMS (Basic)? y
BCMS/VuStats LoginIDs? y  Service Observing (Basic)? y
BCMS/VuStats Service Level? n  Service Observing (Remote/By FAC)? n
Call Work Codes? y  Service Observing (VDNs)? y
CentreVu Advocate? y  Timed ACW? y
DTMF Feedback Signals For VRU? y  Vectoring (Basic)? y
Expert Agent Selection (EAS)? y  Vectoring (Prompting)? y
EAS-PHD? y  Vectoring (G3V4 Enhanced)? y
Forced ACD Calls? n  Vectoring (ANI/II-Digits Routing)? y
Lookahead Interflow (LAI)? y  Vectoring (G3V4 Advanced Routing)? y
Multiple Call Handling (On Request)? y  Vectoring (CINFO)? y
Multiple Call Handling (Forced)? y  Vectoring (Best Service Routing)? y
PASTE (Display PBX Data on Phone)? n
(NOTE: You must logoff & login to effect the permission changes.)
Field Definition
Call  Center  Release The Call Center Release must be set  to 8.1 
(or later)
 to use the High Availability option. 
						

							  Administering the Switch for CMS High Availability Systems CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up Version and Release Values4-5
Setting the 
Adjunct CMS 
Release
4
Use the System Parameters Features form to set the Adjunct CMS 
Release. Depending on switch release, this field can be found on 
different pages.
change system-parameters features Page  X of Y
CALL CENTER SYSTEM PARAMETERS
AGENT AND CALL SELECTION
MIA Across Splits or Skills? n
ACW Agents Considered Idle? y
Call Selection Measurement: current-wait-time
REASON CODES
Aux Work Reason Code Type: none
Logout Reason Code Type: none
CALL MANAGEMENT SYSTEM
Adjunct CMS Release: R3V8
ACD Login Identification Length: 0
BCMS/VuStats Measurement Interval: hour
BCMS/VuStats Abandon Call Timer (seconds):
Validate BCMS/VuStats Login IDs? n
Clear VuStats Shift Data: on-login
Field Definition
Adjunct CMS Release The Adjunct CMS Release must be set to 
R3V8 or later to use the High Availability 
option. 
						

							  Administering the Switch for CMS High Availability Systems CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Administering the Definity Switch4-6
Setting Up the 
Link on the CMS 
Computer
4
The following information must be obtained to set up the CMS link:
•switch name
•switch model (release)
•is Vectoring enabled on the switch (if authorized)?
•is Expert Agent Selection (EAS) enabled on the switch (if 
authorized)?
•does the Central Office have disconnect supervision?
•local and remote port 
The local and remote port assignments must be symmetrical 
between the switch and the CMS. For example, if the CMS local port 
is 1 and the remote port is 10, the switch local port must be 10 and 
the remote port must be 1.
• the hostname or IP address, and TCP port
Note:
In addition to the switch administration presented in this 
chapter, you must also set up the switch link on the CMS 
computer using the setup or swsetup options of the 
cmssvc command. This procedure is documented in 
CentreVu® CMS Software Installation and Setup (585-210-
941)
.
Administering the Definity Switch4
Overview4This section contains the procedures required to establish a 
communications link between the CMS computer and the switch. 
Administering 
the LAN 
Connection
4
Use the procedures in this section to administer  the LAN connection to 
the switch. This section contains examples of the switch administration