Lucent Technologies CentreVu Call Management System Release 3 Version 8 Software Installation And Setup Manual

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Setting Up the NTS2-173
6. Connect the power cord to the NTS (see the following figure). 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Setting Up the NTS2-174
7. Connect the 10-T transceiver to the Network Transceiver Port on the 
back panel of the NTS.
8. Connect the network hub unit to the NTS (10-T transceiver) using a 
UTP network cable.
9. Connect a dumb terminal to the Console Port on the rear of the NTS 
using the console cable and adapter that came with the NTS. On 
the 8- and 16-port NTSs, the Console Port is port #1.
You will need the following for the 8- and 16-port units:
lConsole Cable
lAdapter - comcode 407361823
lNull Modem - comcode 407122043.
You will need the following for the 64-port unit:
lConsole Cable
lAdapter - part number 06-988-260-20.
The terminal options should be set to 9600 bps, 8 bits, no parity or 
space parity, and a stop bit.
10. Turn on the NTS, and within 15 seconds push the Test Switch on the 
front of the NTS (see the following figure).
11. The NTS goes through its hardware diagnostics, and the following 
prompt should appear:
NOTE:
Monitor:: 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Setting Up the NTS2-175
12. Enter the erase command.
There are two types of information that can be erased:
lEEPROM (configuration information)
lFLASH (self-boot image).
If only one type of information is present, the program begins to 
erase it. If there are two types of information, the program 
prompts you to select the information you want to erase. Erase 
both the EEPROM and the FLASH information.
The program responds:
13. Enter 1 to erase EEPROM. The program responds:
14. Enter y. The program responds:
15. Repeat Steps 12
 through 14, but select 2 (FLASH) to erase the 
FLASH information.
16. After you have completed the erase command, enter addr. The 
program responds:
NOTE:
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 []:: 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Setting Up the NTS2-176
17. Enter the IP address for this NTS. This should follow the IP address 
structure outlined earlier in the Prerequisites
 on Page 2-172. The 
program responds:
18. Enter the appropriate Subnet mask, or press Enter to accept the 
default. The program responds:
19. Enter the IP address of the CMS computer. The program responds:
20. Press Enter to accept the default broadcast message address. The 
program responds:
21. Enter the IP address of the CMS computer. The program responds:
Internet address : xxx.xxx.xxx.xxx
Enter Subnet mask [255.255.255.0]::
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) 
[] :: 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Setting Up the NTS2-177
22. 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 Step24
.
The program responds with the following question if you have an 8- 
or 16-port NTS:
23. Enter N. The program returns to the monitor: prompt.
24. 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
Type of IP packet encapsulation: 
Load Broadcast Y/N [Y]::
Enter boot file name [oper.42.enet]::
NOTE: 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Setting Up the NTS2-178
25. 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 12
 to erase EEPROM.
When the initialization finishes, the program responds:
26. Disconnect the dumb terminal from the NTS.
The NTS has been administered.
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:: 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Creating an Alternate Boot Device2-179
Creating an Alternate Boot Device2
This procedure creates an alternate boot device. This procedure is 
required only for mirrored systems.
1. Log in as root and Enter:
ls -l/dev/rdsk/
where  is the device to be used as the alternate boot 
disk. This disk should already be partitioned as an alternate boot 
device, according to the partitioning instructions provided in 
“Partitioning the Hard Disks” on Page 2-18.
The system responds (for example):
2. Identify and record the device definition from the output generated 
in Step 1. The device definition is the character sequence that starts 
after /devices and ends before :a,raw. In the example provided 
above, the device definition is:
sbus@3,0/SUNW,fas@3,8800000/sd@1,0
3. Enter:
/usr/sbin/shutdown -y -g0 -i0
The system displays the ok prompt.
4. To create a device alias for the alternate boot device, enter:
nvalias bootdevice2 
where  is the character sequence 
recorded in Step 2.
5.At the ok prompt, enter:
devalias
The output should include a line that is similar to the following 
example:
Bootdevice2/sbus@3,0/SUNW,fas@3,8800000/sd@1,0
6. To test the alternate boot device, enter:
bootdevice2
When the computer restarts, login as root at the console login. lrwxrwxrwx  1 root   root  54 Nov 9 /dev/redsk/c0t1d0s0 -> 
../../devices/sbus@3,0/SUNW,fas@3,8800000/sd@1,0:a,raw 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Creating an Alternate Boot Device2-180
7. Reboot once again to return system control to the regular boot disk:
/usr/sbin/shutdown -y -g0 -i6
8. To set up a cron job for chkDisk, enter:
crontab -e
The cron file is displayed in editor mode.
9.Add the following line to the end of the cron file:
15   0  *  *  *  /olds/chkDisks>/dev/null 2>&1
10. To save and quit the file, enter:
 :wq
11 . E n t e r :
chmod  +x  /olds/chkDisks
The alternate boot disk is now set up. 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Performing a CMSADM Backup2-181
Performing a CMSADM BackupB
The CMSADM file system backup saves all of the file systems on the 
computer onto a tape. 
OverviewBThe CMSADM file system backup includes the following:
lSolaris 7 system files and programs
lCMS programs and data
lNon-CMS customer data placed on the computer (in addition to the 
CMS data).
The CMSADM file system backup should be done at the following times:
lAfter the system has been set up in the factory
This backup contains the default factory configuration. These tapes 
should be saved if the system must be reinstalled in the field.
lAfter the CMS is provisioned
This backup contains the 
Solaris system files and programs and 
CMS configuration data placed on the computer by TSC 
provisioning personnel. These tapes should also be saved and not 
reused.
In addition, field technicians should perform a CMS full maintenance 
backup before they turn a new system over to the customer. See 
CentreVu® CMS R3V8 Administration (585-210-910) for more 
information.
lBefore and after the CMS software is upgraded (usually done by a 
field technician)
lOnce a month (performed by the customer).
The customer must use a new set of backup tapes for this 
CMSADM File System backup. The customer must NOT use the 
original set of factory or provisioning backup tapes.
The number of cartridge tapes required to complete a CMSADM file 
system backup depends on the amount of data on the system and the 
capacity of the backup tape. The program estimates the number of tapes 
required and informs the user.
!CAUTION: 
						

							  Installing Software and Setting Up CMS CentreVu®  CMS R3V8 Software Installation and Setup
Performing a CMSADM Backup2-182
Platform 
Considerations
B
lAll platforms.
PrerequisitesBlBefore starting the backup procedures described in this section, log 
in as 
root, and enter lp /etc/vfstab. The output from the printer 
is necessary when doing a system restore. Bundle the printout of 
the /etc/vfstab file with the system backup tape(s) for future 
reference.
lVerify that the computer is in a Solaris multi-user state (2 or 3). To 
check if you are in the multi-user state, enter who -r.
Verify that you are using the correct tape for the tape drive on your 
system. Many of the tape cartridges look alike, and using the wrong 
tape can damage the tape drive mechanism and tape heads. The 
following table lists the different model of tape drives, the 
accompanying tape cartridge model identification, and the CMS 
computers that use the tape drives.
Tape Drive Tape Cartridge CMS Computers
20/40-GB 8mm
Exatape* 170m AME
*Exatape is a trademark of Exabyte Corporation.
Enterprise 3500
SLR5 4/8-GB QIC
Sony† SLR
†Sony is a registered trademark of Sony Corporation.
Ultra 5
14-GB 8mm
Exatape 160mm 
AMEEnterprise 3000
5-GB 8mm
Exatape 112mm 
AMEEnterprise 3000
2.5-GB QIC
3M‡
‡3M is a registered trademark of Minnesota Mining and Manufacturing.
SPARCserver
150 MBMaxell§ DC6320
§Maxell is a registered trademark of Maxell, Inc.
SPARCserver
!CAUTION: