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 the NTS3-61
The program responds:
5. Enter 1 to erase EEPROM. The program responds:
6. Enter y. The program responds:
7. Repeat Steps 4
 through 6, but select 2 (FLASH) to erase the 
FLASH information.
8. After you have completed the erase command, enter addr. The 
program responds:
9. Enter the IP address for this NTS. The program responds:
Erase
1) EEPROM (i.e., Configuration Information)
2) FLASH (i.e., Self Boot Image)
Enter 1 or 2:: 
Erase all non-volatile EEPROM memory? (y/n) [n]::
Erasing xxxx bytes of non-volatile memory. Please wait....
...............................
Erased xxxx bytes of non-volatile memory complete.
Monitor::
Enter Internet address []::
Internet address : xxx.xxx.xxx.xxx
Enter Subnet mask [255.255.255.0]:: 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up the NTS3-62
10. Enter the appropriate Subnet mask, or press Enter to accept the 
default. The program responds:
11. Enter the IP address of the CMS computer. The program responds:
12. Press Enter to accept the default broadcast message address. The 
program responds:
13. Enter the IP address of the CMS computer. The program responds:
14. Press Enter to accept the default IP packet encapsulation. The 
program returns to the monitor:: prompt if you have a 64-port 
NTS. Continue with Step16
.
The program responds with the following question if you have an 8- 
or 16-port NTS:
15. Enter N. The program returns to the monitor:: prompt.
Subnet mask: xxx.xxx.xxx.xxx
Enter preferred load host Internet address []::
Preferred load host address xxx.xxx.xxx.xxx
Enter Broadcast address [0.0.0.0]::
Enter Preferred dump address [0.0.0.0]::)
Preferred dump address: xxx.xxx.xxx.xxx
Select type of IP packet encapsulation (ieee802/ethernet) 
[] ::
Type of IP packet encapsulation: 
Load Broadcast Y/N [Y]:: 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Setting Up the NTS3-63
16. Enter the boot command at the monitor prompt to reinitialize the 
NTS with the new parameters. The program responds:
The boot file name differs depending on the type of NTS. For 
the 8- and 16-port NTS, the boot file name is:
[(ip) “oper.52.enet”,(mop)“OPER_52_ENET.SYS”]
For the 64- port NTS, the boot file name is:
oper.42.enet
17. Press Enter to accept the default boot file name. The program 
responds:
The periods (dots) continue to appear as the NTS is initialized and 
set up.
If the program displays “SELF” instead of the IP address 
(192.168.2.1 is the factory default; your IP address may be 
different), it means that you did not erase EEPROM. Go back to 
Step 4
 to erase EEPROM.
When the initialization finishes, the program responds:
18. Disconnect the dumb terminal from the NTS.
The NTS has been administered.
Enter boot file name [oper.42.enet]::
NOTE:
Requesting boot file “oper.42.enet”.
Unanswered requests shown as ‘?’,
transmission errors as ‘*’.
Booting file: oper.42.enet from 192.168.2.1
Loading image from 192.168.2.1
....................
NOTE:
annex:: 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Creating an Alternate Boot Device for Mirrored Systems3-64
Creating an Alternate Boot Device for Mirrored Systems3
This procedure creates an alternate boot device. This procedure is 
required only for Enterprise 3000 or Enterprise 3500 platforms configured 
as  mirrored systems. 
For a description of the procedure used to create the alternate boot 
device, see “Creating an Alternate Boot Device for Mirrored Systems” in 
Chapter 2 of  “CentreVu Call Management System R3V8 Software 
Installation and Setup” (585-210-941).
Migrating CMS System Administration Data to the New 
Server
3
This procedure uses the maintenance backup tape (“Performing a 
Maintenance Backup (Administration Data Only)” on Page 3-12),  which 
was created on the original server, to migrate administration data onto 
the new HA server.
Since the immediate objective is to bring  the new HA server to an 
operational state as quickly as possible, CMS Historical data is not 
migrated onto the new HA server until later in the upgrade process.
Caution! 
Do not use the Full Maintenance backup tape created in “
Performing a 
Full Maintenance Backup” on Page 3-11 for this migration.
Procedure3For all versions of CMS Release 3, the system administration data is 
migrated via the R3 Migrate Data window.
Attempting to migrate system administration data more than once may 
cause catastrophic errors from which recovery is difficult. Before a re-
migration of system administration data can be performed,  CMS must be  
turned off and a second setup of the CMS software must be performed.
1.  Log in to CMS.
The CMS main menu is displayed.
2. Select System Setup - CMS State from the CMS main menu 
and select the Single User Mode option
3. Insert the backup tape that contains the latest version of the admin 
data into the tape drive on the new HA server.
4. Select the System Setup -> R3 Migrate Data option from the 
CMS main menu.
The System Setup: R3 Migrate Data  window is displayed.
!WARNING: 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Migrating CMS System Administration Data to the New Server3-65
5.  Specify System Administration data as the the migration 
data types, and specify All ACDs  for migration, as shown in the 
following example:
6. Press Enter to access the action list in the top right corner of the 
window.
7. 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.
8. Repeat the procedure, this time selecting  Agent/Call Center 
Admin data as the data type to be migrated. 
Again, the Status: field reports the progress of the migration. 
When the migration ends, Status: indicates the success or failure 
of the run.
9. To print out the customer migration log, enter:
lp /cms/migrate/r3mig.log
Note:
Printer administration must be done on the new HA server  
before this step can be performed.
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 in /cms/maint/r3mig/mig.log.
x
xx
x
x 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Checking the Archive Interval3-66
Checking the Archive Interval3
When you are ready to upgrade the CMS software on the original server, 
wait for the current archive interval to complete before busying out the 
link. This avoids unnecessary loss of call data. 
To check the archive interval status:
1. Log in as a CMS user and select the Maintenance option from the 
CMS Main Menu.
The Maintenance options window is displayed.
2. Cursor down to the Archiving Status option and press Enter.
The Maintenance: Archiving Status window is displayed.
3. Cursor down to the Archiving type list and use the spacebar to 
deselect the Daily, Weekly and Monthly options.
4. Press enter to move the active cursor to the action box in the top 
right corner of the window; press enter again to select the List 
all option. 
The Maintenance: Archiving Status: List all window is 
displayed. 
5. Note the figures in the Time column. If the elapsed time since the 
last archive completion is not more than a few minutes, proceed with 
the link busy out. Alternately, if more than a few minutes has 
elapsed since the last archive completion, wait for the next archive 
interval to complete before busying out the link. 
acd1
acd28:05
8:05a.m
a.m 1/12/00
1/12/00Interval
IntervalFinished
Finished8:30a.m
8:30a.m 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Administering the Switch3-67
Administering the Switch3
After links to the original server are busied out at the Definity switch, the 
switch is re-administered for R3V8 and the HA dual C-LAN option. 
For details of switch admininistration for HA systems, see “
Administering 
the Switch for CMS High Availability Systems” on Page 4-1. 
After the switch is re-administered, bring up the links and start data 
collection on the new HA server. At this point in the HA upgrade process, 
both CMS systems are offline and call data is not collected. Therefore,  
administration of the switch for R3V8 and HA dual links and startup of 
data collection on the new HA server should be completed as quickly as 
possible.
Note:
Be sure to verify that data collection is active on all ACD links 
before proceeding to the next procedure.
The services migration log is in /cms/maint/r3mig/mig.log. The log may contain information inappropriate for the customer.
Performing an Incremental Maintenance Backup3
Perform an incremental maintenance backup (historical data only) on the 
original server. Begin the server upgrade immediately after the backup 
completes. 
Procedure31. From the CMS main menu, select the Maintenance - Back Up 
Data option.
The Back Up Data window is displayed. Only select the 
Historical data - incremental data type to be copied onto 
the backup. 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Upgrade the Original CMS Server3-68
 The correct backup option selections are shown in the following 
example: 
2. After you have selected the appropriate options for the backup, 
press enter to access the action list in the upper right corner of the 
window, cursor to the Run option and press enter to start the 
backup. 
Upgrade the Original CMS Server3
As soon as the incremental backup (preceeding procedure) is 
successfully completed on the original server, the original server can be 
powered down, the system hard drives are swapped out with the new 
drives provided by the Speed Centre and all necessary software 
authorization, setup, and configuration steps are performed. For details, 
see “Setting Up CMS on an HA Server” on Page 3-14
.
By the time the upgrade of the original server is completed and data 
collection is turned on, the new HA server should already be fully 
operational. 
The final steps in the HA upgrade process, which includes two separate 
data migrations, a final full maintenance backup and restore, and the 
creation of CMSADM backups for each of the HA servers, are described 
in the following procedures. 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Migrating CMS Historical Data to the New HA Server3-69
Migrating CMS Historical Data to the New HA Server3
After the switch is re-administered for R3V8 and the HA dual C-LAN 
option and CMS data collection is started on the new HA server, migrate 
CMS historical data to the new HA server.
Procedure3This procedure migrates CMS historical data from the second 
incremental maintenance backup (“
Performing an Incremental 
Maintenance Backup” on Page 3-67) onto the new HA server.
Attempting to migrate CMS data more than once may cause catastrophic 
errors from which recovery is difficult. Before a re-migration of data can 
be performed,  CMS must be turned off and a second setup of the CMS 
software must be performed.
1. Install the incremental maintenance backup tape (which contains 
incremental historical data) into the tape drive on the new HA server.
2. Select the System Setup -> R3 Migrate Data option from the 
CMS main menu.
The System Setup: R3 Migrate Data  window is displayed.
3. Select Historical data as the the data type, and specify All 
ACDs for migration, as shown in the following example:
4. Press Enter to access the action list in the top right corner of the 
window.
5. Select the Run option and press Enter. 
!WARNING:
x 
						

							  Upgrading CMS to the High Availability Option CentreVu CMS R3V8 High Availability
Connectivity, Upgrade and Administration
Migrating Administration Data Back Onto the Original Server3-70
6. The Status: field reports the progress of the migration. When the 
migration ends, Status: indicates the success or failure of the run.
7. When the migration is finished, remove the incremental tape from 
the drive and insert the original full maintenance backup 
(“Performing a Full Maintenance Backup” on Page 3-11
) and repeat 
steps 2 through 6. 
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 found in /cms/maint/r3mig/mig.log.
Note:
Printer administration must be done on the new HA server  
before this step can be performed.
Migrating Administration Data Back Onto the Original 
Server
3
After the original server is upgraded to the same CMS version and base 
load as the new HA server, the original administration data, which was 
copied to tape in the first maintenance backup (“
Performing a 
Maintenance Backup (Administration Data Only)” on Page 3-12) is 
migrated back onto the system. After this procedure is performed, the two 
servers should share identical sets of administration data. 
.
Attempting to migrate CMS data more than once may cause catastrophic 
errors from which recovery is difficult. Before a re-migration of data can 
be performed,  CMS must be  turned off and a second setup of the CMS 
software must be performed.
Migrate the 
Administration 
Data
3
Insert the initial maintenance backup tape back into the tape drive of the 
original server.
1. Log in as a CMS user.
The CMS main menu is displayed.
2. Select System Setup - CMS State from the CMS main menu 
and select the Single User Mode option.
!WARNING: