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
Setting Up CMS on an HA Server3-21
Setting Up Data 
Storage 
Parameters
3
Overview3TSC personnel modify specific data storage parameters on the CMS 
computer so that the CMS application can operate properly. The 
storage.def file contains these data storage parameters, which are 
installed with a set of standard default values. 
Review the default data storage values for each authorized ACD. The 
default values are found on the line immediately below each storage 
parameter, and many of them can be can be edited to meet the needs of 
individual customers.  Use the values determined by the Account 
Executive, System Consultant, and Design Center based on the 
customer configuration. For a new HA system being added to an existing 
CMS installation, these values should be identical to the values installed 
on the original server at the customer site. 
Procedure31. To change to the CMS installation directory, enter:
cd /cms/install/cms_install
2. Enter:
vi storage.def
If you delete or damage the storage.def file, you can find a 
copy of this file (storage.skl) in the same directory.
3. The default storage parameters are listed (immediately below each 
of the defined storage paremeters) in the order in which they appear 
in the storage.def file.  
•# Intrahour interval (15, 30, 60 minutes):
30
•# Week start day (Sunday, Monday, Tuesday, Wednesday, 
Thursday, Friday, Saturday):
Sunday
•# Week end day (Sunday, Monday, Tuesday, Wednesday, 
Thursday, Friday, Saturday):
Saturday
NOTE: 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up CMS on an HA Server3-22
•# Daily start time (regular time):
12:00 AM
•# Daily stop time (data will be collected for seconds of last 
minute):
11:59 PM
•# Number of agent login/logout records (0-999999):
10000
•# Number of agent trace records:
10000
•# Number of call records (0-5000 internal or 0-99999 external):
 0
•# Number of exceptions records (1-2000):
250
•# Days of intrahour for splits (1-62):
31
•# Days of daily splits (1-1825):
387
•# Weeks of weekly splits (1-520):
53
•# Months of monthly splits (1-120):
13
•# Days of intrahour for agents (1-62):
31
•# Days of daily agents (1-1825):
387
•# Weeks of weekly agents (1-520):
53
•# Months of monthly agents (1-120):
13
•# Days of intrahour for trunk groups (1-62):
31
•# Days of daily trunk groups (1-1825):
387 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up CMS on an HA Server3-23
•# Weeks of weekly trunk groups (1-520):
53
•# Months of monthly trunk groups (1-120):
13
•# Days of intrahour for trunks (1-62):
31
•# Days of daily trunks (1-1825):
387
•# Weeks of weekly trunks (1-520):
0
•# Months of monthly trunks (1-120):
53
•# Days of intrahour for call work codes (1-62):
0
•# Days of daily call work codes (1-1825):
0
•# Weeks of weekly call work codes (1-520):
0
•# Months of monthly call work codes (1-120):
0
•# Days of intrahour for vectors (1-62):
31
•# Days of daily vectors (1-1825):
387
•# Weeks of weekly vectors (1-520):
53
•# Months of monthly vectors (1-120):
13
•# Days of intrahour for VDNs (1-62):
31 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up CMS on an HA Server3-24
•# Days of daily VDNs (1-1825):
387
•# Weeks of weekly VDNs (1-520):
53
•# Months of monthly VDNs (1-120):
13
4. After entering the appropriate values, enter:
 :wq
After the CMS application is running, the system administrator can 
change the data storage parameters using the Data Storage Allocation 
window and the Storage Intervals window in the CMS System Setup 
menu. For more information about changing ACD data storage 
parameters, see the CMS System Setup chapter in 
CentreVu® CMS 
R3V8 Administration
 (585-210-910).
Setting Up a LAN 
for Switch 
Connections
3
Overview3This section contains information about setting up a LAN connection 
between the CMS computer and one or more HA-enabled 
Definity 
switches. This type of connection is used only with 
Definity ECS Release 
8.1 or later. The LAN connections described herein are based on the 
configuration recommended for HA systems, which includes two ethernet 
ports for each server and which also assumes that private LAN subnets 
are used for the switch-to-server connections.
To set up a LAN connection to an HA-enabled switch, you must 
coordinate the administration done on the CMS computer with the 
administration done on the switch and, if required, within the customer’s 
own data network.
Prerequisites3•Verify that you are logged in as root.
•CMS must be turned off.
•All file systems must be mounted. 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up CMS on an HA Server3-25
Procedures3To set up a network connection to an HA-enabled switch and other CMS 
computer peripherals, the following steps are performed:
•Edit the /etc/hosts file.
•Set up a second network interface.
•Edit the /etc/defaultrouter file.
Editing the 
/etc/hosts File
3
1. To save a backup copy of the file, enter:
cp /etc/hosts /etc/hosts.old
2. To edit the /etc/hosts file, enter:
vi /etc/hosts
3. Add a new line in this file for each ACD/switch that will connect to 
this computer using TCP/IP. Lines must also be added for any NTS 
devices installed on the system.
This example shows the recommended default IP addressing 
scheme for the two ethernet ports installed on the server. The 
hostname “cms_1”  represents the second network interface, which 
is on the same private subnet carrying the link to the switches. This 
example also shows the first ethernet port conncecting to two NTS 
servers (cmsterm1 and cmsterm2).
4. Press the Esc key to leave the edit mode.
5. Enter :wq to save and quit the existing file.
6. To edit the hostname files associated with the second network 
hostname created in /etc/hosts, enter one of the following:
•On an 
Enterprise 3000 or Enterprise 3500 with a second FSBE 
card, enter the following:
vi /etc/hostname.le0
•On an 
Enterprise 3000, Enterprise 3500, or Ultra 5 with a 
second 
SunSwift card, enter the following:
vi /etc/hostname.hme1
192.168.2.1      cms
192.168.2.101    cmsterm1
192.168.2.102    cmsterm2
192.168.1.2      cms_1
192.168.1.11     switch1
192.168.1.12     switch2 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up CMS on an HA Server3-26
7. Add a line to this new file with the host name you added to the 
/etc/hosts file. For example:
8. Press the Esc key to leave the edit mode.
9. Enter :wq to write and quit editing the file.
Editing the 
/etc/defaultrouter 
File
3
If the connection between the first network interface on the CMS 
computer connects through a customer network, you will have to set up a 
default network router.
1. To create a default router file, enter:
vi /etc/defaultrouter
2. Add a line to this new file with the IP address for the default system 
router on the customer’s network. This address must be obtained 
from the customer. For example:
3. Press the Esc key to leave the edit mode.
4. Enter :wq to write and quit editing the file
Turn Off IP Forwarding3To eliminate a potential security risk associated with the IP Forwarding 
function, enter: 
 
cms_1
192.168.1.254
touch /etc/notrouter 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up CMS on an HA Server3-27
Setting Up the 
CMS Application
3
Overview3Use the procedures in this section to set up the CMS application.
Prerequisites3•Verify that you are logged in as root.
•CMS must be turned off.
•All file systems must be mounted.
Setup Methods3You can set up the CMS feature package using one of two methods:
a.Interactively from a terminal — Using the interactive option, 
the program prompts you for the necessary information to 
set up the CMS application (for example, system type, 
number of agents, trunks, vectors, VDNs, and so on).
To set up the CMS application using this option, see “Setting Up 
CMS Interactively from a Terminal” in this chapter.
b.
UNIX* System flat file — Using the flat file option, you edit a 
UNIX System flat file containing the necessary information 
(for example, system type, number of agents, trunks, 
vectors, VDNs, and so on) to set up the CMS application. 
When you execute the program, it runs in the background 
and uses the 
UNIX System flat file data to set up the CMS 
application. To set up the CMS application using this 
option, see “Setting Up CMS Using a UNIX Flat File
” in this 
chapter.
*UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open 
Company Limited. 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up CMS on an HA Server3-28
Setting Up CMS 
Interactively from a 
Te r m i n a l
3
Overview: 
Using the interactive option, the program prompts you for the necessary 
information.
Procedure: 
1.  If you are not sure of the device path, do the following:
a. Insert a tape into the tape drive.
b. In another xterm window, enter the following commands:
•mt -f /dev/rmt/1c status
•mt -f /dev/rmt/0c status
The correct device path will show information similar to the following 
example:
2. Access the CMS Services menu by entering the following:
cmssvc
The program responds:
Mammoth EXB-8900 8mm Helical Scan tape drive:
   sense key(0x0)= No Additional Sense   residual= 0 
retries= 0
   file no= 0   block no= 0
Lucent Technologies CentreVu(R) Call Management System Services Menu
Select a command from the list below.
1) auth_display Display feature authorizations
2) auth_set Authorize capabilities/capacities
3) run_cms Turn CentreVu CMS on or off
4) setup Set up the initial configuration
5) swinfo Display switch information
6) swsetup Change switch information
7) patch_inst Install a single CMS patch from CD
8) patch_rmv Backout an installed CMS patch
9) load_all Install all CMS patches found on CD
10) back_all Backout all installed CMS patches from machine
Enter choice (1-10) or q to quit: 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up CMS on an HA Server3-29
3. Enter 4 to select the setup option.
If system setup has already been done, the program responds:
4. Enter y to continue with the setup, or enter n to exit setup. If you 
enter y, the program responds:
5. Enter the number for the language used on this system. If setup has 
been done previously, the customer CMS data is now initialized. 
When finished, the program responds:
NOTE
Warning!!! Setup has already been performed.
Running this command will remove all CMS data in the database.
Do you wish to proceed and re-configure CMS? (y/n): (default: n)
Select the language for this server:
All languages are ISO Latin except Japanese. Selection of the
server language assumes that existing customer data is 
compatible. (Upgrade from any ISO Latin language to any ISO 
Latin language or from Japanese to Japanese is supported).
1) English
2) Dutch
3) French
4) German
5) Italian
6) Portuguese
7) Spanish
8) Japanese
Enter choice (1-8): (default: 1)
Enter a name for this UNIX system (up to 256 characters): 
(default: 
XXXXXX)  
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up CMS on an HA Server3-30
6. Press enter to accept the default. 
The program responds:
7. Enter the number to specify the type of cartridge tape you are using 
as the backup device. The program responds:
Enter the default backup device path.
The correct device path will show information similar to the following 
example:
8. After you enter the correct device path, the program responds:
9. Enter the number of ACDs to be administered. This number may be 
less than the number of ACDs authorized. The program responds:
Select the type of backup device you are using
   1) SCSI QIC-150 cartridge tape - 150MB tape
2) 40.0 Gbyte 8mm tape                     
3) 14.0 Gbyte 8mm tape                     
4) 5.0 Gbyte 8mm tape                      
5) SCSI QIC-2.5 cartridge tape - 2.5GB tape
6) SCSI 4-8 SLR cartridge tape - 4GB tape (8GB compressed)
Enter choice (1-6):
Enter the default backup device path:
(default: /dev/rmt/0c)
Mammoth EXB-8900 8mm Helical Scan tape drive:
   sense key(0x0)= No Additional Sense   
residual= 0   retries= 0
   file no= 0   block no= 0
Enter number of ACDs being administered (1-8):
Information for ACD 1
Enter switch name (up to 20 characters):