Lucent Technologies CentreVu Call Management System Release 3 Version 8 Guide

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring25
Step 10: Verify disk 
space
2
1. Display available disk space by entering a df -k
 command. The 
system responds with a file system table. For example:
The figures on the 
/dev/md/dsk/d21 line are critical. You will use 
them to determine whether 
Solstice DiskSuite* is administering all 
your disks.
2. Complete the table below by filling in (1a) and (1b) as instructed.
3. Compare the figures in (1a) and (1b) of the table. They should be 
approximately equal. The two will not correspond exactly, but they 
should be within about 10% of the /cms size figure. A major 
discrepancy between the disk space you should have and the space 
recognized by your 
Solstice DiskSuite software usually indicates a 
connectivity problem. You can check connectivity by checking the 
output of a metastat
 command to see that all the disks are 
recognized. For example:
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d13 1039555 355366 580239 38% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
swap 1305272 344 1304928 1% /tmp
/dev/md/dsk/d21 31956788 849300 31107488 3% /cms
*Solstice DiskSuite is a trademark of Sun Microsystems, Inc.
Disk Space Verification
To ta l  N o .
of Disks/cms size in MB
(4-GB disks)/cms size in MB
(9-GB disks) Calculations:
2 3104 6208 (1a) Enter /cms 
line’s ‘kbytes’ figure 
divided by 1000 
(move decimal 
three places left): (1a) 4 7137  14274
6 11170  22340
8 15203  30406
10 19236   (1b) Enter “/cms 
Size” (above left) 
corresponding to 
the number of hard 
disks and disk size: (1b) 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring26
If the stripes of d19 and d20 do not account for all the disk drives on your 
system, check your disk drive connections. If discrepancies persist, 
telephone the Lucent National Customer Care Center at 1.800.242.2121, 
or contact your Lucent representative or distributor.
Step 11: Create an 
alternate boot 
device
2
Set up an alternate boot device by doing the following procedure:
1. Enter the following command:
where 
newbootdev is the device name of the disk chosen as boot 
disk 2 (recorded as the d12 metadevice on page 13
). 
If your boot disk 2 were c0t2d0s0, for example, the system would 
respond with something like this:
2. Record the part of the line immediately following /devices
 and 
preceding :a.
 For the example above, you would record the part of 
the line beginning /sbus@3,0 
and ending sd@2,0
.
# metastat
...
d21: Mirror
    Submirror 0: d19
      State: Okay         
    Submirror 1: d20
      State: Okay
...
d19: Submirror of d21
    State: Okay         
    Size: 14398560 blocks
    Stripe 0:
        Device Start Block Dbase State        Hot Spare
        c0t0d0s3 0 No Okay 
    Stripe 1:
        Device  Start Block  Dbase State        Hot Spare
        c0t2d0s1 0 No Okay 
d20: Submirror of d21
    State: Okay         
    Size: 14398560 blocks
    Stripe 0:
        Device  Start Block  Dbase State        Hot Spare
        c0t1d0s3                   0     No    Okay         
    Stripe 1:
        Device  Start Block  Dbase State        Hot Spare
        c0t3d0s1                   0     No    Okay 
# ls -l /dev/rdsk/
lrwxrwxrwx 1 root root 83 Jun 18 15:23 /dev/rdsk/c0t2d0s0 -> 
../../devices/sbus@3,0/SUNW,fas@3,8800000 /sd@2,0:a,raw 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring27
3. Reboot the system with the following command:
The system displays the ok 
prompt.
4. Create a device alias for the new boot device by entering the 
following command (for example):
Replace 
 with what you recorded in item 2. For the 
example shown, you would replace 
 with the following:
/sbus@3,0/SUNW,fas@3,8800000/sd@2,0
5. Test the alternate boot device name by entering the following 
command:
6. Reboot the system as usual and verify that everything is normal. 
Ignore any warnings you may get about a “forceload” failing.
7. Enter the following command:
The system starts the editor and loads the cron
 file. 
8. Find the line for 
/olds/chkDisks and take one of the following actions:
If the line is commented out, uncomment it by deleting the pound 
sign at the beginning of the line.
If there is no line for 
/olds/chkDisks, add the following line to 
the end of the file:
15 0 * * * /olds/chkDisks > /dev/null 2>&1
 
9. Save the file and exit the editor.
10. Enter the following command:# /usr/sbin/shutdown -y -i0 -g0
ok nvalias bootdevice2

ok boot bootdevice2
# crontab -e
# chmod +x /olds/chkDisks 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Factory installation procedures for disk mirroring28
Factory installation procedures for disk mirroring2
This section describes how a mirrored system is installed on a new Sun 
Enterprise
 3xxx computer in the factory. You may use these instructions 
in the field to bring an existing system up to factory specifications. 
Step 1: Install the 
hardware
2
Install hardware components as required. For details and instructions, 
see the appropriate Lucent hardware installation document and the 
Sun 
Microsystems
 documents shipped with your machine.
Step 2: Install the 
operating system
2
Install the Solaris operating system. Partitioning the disks will be part of 
that process.
To install the 
Solaris operating system, follow the instructions in the 
CentreVu CMS R3V8 Software Installation and Setup (585-210-941) 
document, with the following exception:
lUse the Disks and Partitioning tables below to determine disk 
partitioning details. 
Disks shows which disks are boot disks and 
which are not; 
Partitioning shows partitioning details.
Disks
Disk
Enterprise 3000
Device NamesEnterprise 3500
Device Names
 boot disk 1  c0t0d0 c0t0d0
 boot disk 2  c0t1d0
a
aTrue for factory-installed disk mirroring. Unlikely to be true 
for systems upgraded to disk mirroring in the field. 
c1t4d0
 other disks  c0t2d0
c0t3d0
c0t10d0
c0t11d0
c0t12d0
c0t13d0
c0t14d0
c0t15d0c0t1d0
c0t2d0
c0t3d0
c1t5d0
c1t6d0
c1d7d0 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Factory installation procedures for disk mirroring29
.
Step 3: Install the 
application 
software
2
Install application software as instructed in the CentreVu CMS R3V8 
Software Installation and Setup 
(585-210-941) document. That will mean 
installing the following packages in order:
lCommon Desktop Environment (CDE)
lSunLink* HSI/S drivers (if using HSI/S ports)
lNTS drivers (if using NTS ports)
lX.25 (if using X.25 switch links)
lINFORMIX† SQL (optional)
lINFORMIX SE 
lINFORMIX ESQL
lINFORMIX ILS
lSolstice DiskSuite 
lSun Solaris patches Partitioning (Note: Never change the default size of the 
overlap slice!)
CMS R3V8
4.2-GB DiskCMS R3V8
9.1-GB Disk SCSI 
(E3000) and FC-AL 
(E 3500)
Disk 
TypePart Tag FlagSize
(cyl.)Starting
CylinderSize
(cyl.)Starting 
Cylinder
Boot 0boot disk 1: / or root
boot disk 2: unassignedwm 1023 0 616 0
1 unassigned wm 7 1023 7 616
2overlap 
or backup wm 3880 0 4924 0
3 unassigned wm 1879 1030 3716 623
4 swap wm 971 2109 585 4339
5-7 unassigned wm 0 0 0 0
Nonboot 0 unassigned wm 2 0 2 0
1 unassigned wm 3878 2 4922 2
2overlap 
or backup wm 3880 0 4924 0
3-7 unassigned wm 0 0 0 0
*SunLink is a trademark of Sun Microsystems, Inc.
†
INFORMIX is a registered trademark of Informix Software, Inc. 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Factory installation procedures for disk mirroring30
Step 4: Check the 
disk.type file2
The olds
 commands, which you will be using to configure the Solstice 
DiskSuite 
software, obtain information about your disk configuration from 
the 
/olds/disk.type file. If your boot disks are not as specified in the Disks 
table in Step 2, check the 
disk.type file to verify that it names the proper 
boot disks for your system. 
The relevant portion of the 
disk.type file looks like this:
The 
bootdisk1 column designates the first boot disk; the disk2 column 
designates the second boot disk in a mirrored configuration. In order for 
the 
olds commands to work, the disks.type file must match your physical 
configuration: you must have disks in the locations specified in the file.
Step 5: Set up the 
disk subsystem for 
Solstice DiskSuite2
1. Set the environment to the Korn Shell by entering these commands:
(where 
 indicates you should press and hold the Control key 
as you press the H key).
The 
stty command sets up your backspace key as an actual 
backspace. If you do not enter this command, you will have to use 
the Delete key as a backspace.
2. Make sure the CMS CD is loaded in the CD-ROM drive. 
3. Copy the 
Solstice DiskSuite setup scripts from the CD to the boot 
disk by entering the following commands:
4. Alter your path:
#arch config bootdsk1 disk2 scsi control
 
#Enterprise 3000
sun4u notmirrored c0t0d0 c0t1d0 dontcare
sun4u mirrored c0t0d0 c0t1d0 controllers=0
# stty erase
# ksh -o vi
# mkdir /olds
# cp /cdrom/cdrom0/cms/reloc/rdonly/olds_install/* /olds
# cd /olds
# chmod +x /olds/olds
# export PATH=$PATH:/usr/opt/SUNWmd/sbin:/olds
# 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Factory installation procedures for disk mirroring31
5. Check the disks:
6. Create system files for the 
Solstice DiskSuite software:
7. Make sure all the disk drives on your system have been recognized. 
To do that, read the file 
/olds/md.tab.new into an editor and locate 
the 
#/cms section. It should reflect the precise number of disk drives 
on your system. The following example shows a total of four disk 
drives on the system, two in d19 and two in d20:
If there is a discrepancy between what the system should have 
recognized and what it 
did recognize, complete the procedure in 
“The system fails to recognize all disk drives” on page 82, and then 
return to item 5.# olds -mirrored -check_disks
number of external scsi controllers with disks  
is = 0
number of disks is = 4 
...
disk:c0t0d0 is partitioned ok                                                   
disk:c0t1d0 is partitioned ok                                                   
disk:c0t2d0 is partitioned ok                                                   
disk:c0t3d0 is partitioned ok                                                   
Success, checking disks for mirroring.                                          
#
# olds -mirrored -mk_files
#
.
.
.
#metaroot
d11 1 1 c0t0d0s0
d12 1 1 c0t2d0s0
d13 -m d11
#/cms
d19 2 1 /dev/rdsk/c0t0d0s3 1 /dev/rdsk/c0t1d0s1
d20 2 1 /dev/rdsk/c0t2d0s3 1 /dev/rdsk/c0t3d0s1
d21 -m d19
#metaswap
d15 1 1 c0t0d0s4
d16 1 1 c0t2d0s4
d17 -m d15 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Factory installation procedures for disk mirroring32
Step 6: Run the 
setup scripts
2
1. Create the state database replicas by entering the following 
command:
2. Mirror the root file system by entering the following command:
3.Check disks with “metastat
” and wait until all disks are synched.
Ignore any FSCK error messages which may be 
generated.
4. Reboot and log in as the root user (boot -r)
: # olds -mirrored -metadbs
.
.
.
Success, setting up metadb replicas
# olds -mirrored -setroot
.
.
.
Success, root mirrored successfully.
# /usr/sbin/shutdown -y -g0 -i0
.
.
.
ok
ok boot -r
.
.
.
 console login: root
Password:

#
NOTE: 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Factory installation procedures for disk mirroring33
5. Setup the /cms metadevices by entering the following commands:
6. Create and mount the 
/cms file system by entering the following 
commands:
Step 7: Verify disk 
space
2
1. Display available disk space by entering a df -k
 command. The 
system responds with a file system table. For example:
The figures on the 
/dev/md/dsk/d21 line are critical. You will use 
them to determine whether 
DiskSuite is administering all your disks. # ksh -o vi
# export PATH=$PATH:/olds
# olds -mirrored -setup
.
.
.
3962848, 13997552, 14032256, 14066960, 14101664, 
14136368, 14171072,
 14205776, 14240480, 14275184, 14309888, 
14344592, 14376992, 14411696,
 14446400, 14481104, 14515808, 14550512, 
14585216, 14619920, 14654624,
 14689328, 14724032, 14758736, 14793440, 
14828144, 14862848, 14897552,
 14929952,
ufs fsck: sanity check: /dev/md/rdsk/d21 okay
Success, /cms mirrored  successfully
#
# mkdir /cms
# mount /cms
#df-k
Filesystem kbytes used avail capacity Mounted on
/dev/md/dsk/d13 772327 236870 458227 35% /
/proc 0 0 0 0% /proc
fd 0 0 0 0% /dev/fd
/dev/md/dsk/d21 xxxxxxxx 562168 14346985 0% /cms 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Factory installation procedures for disk mirroring34
2. Complete the table below by filling in (1a) and (1b) as instructed.
3. Compare the figures in (1a) and (1b). They should be 
approximately 
equal. The two will not correspond exactly, but they should be within 
about 10% of the /cms size figure. A major discrepancy between the 
disk space you should have and the space recognized by the 
software usually indicates a connectivity problem. You can check 
connectivity by checking the output of a metastat
 command to see 
that all the disks are recognized. For example:
If the stripes of d19 and d20 do not account for all the disk drives on your 
system, check your disk drive connections. If discrepancies persist, 
telephone the Lucent National Customer Care Center at 1.800.242.2121, 
or contact your Lucent representative or distributor.Disk Space Verification
To ta l  N o .
of Disks/cms size in MB
(4-GB disks)/cms size in MB
(9-GB disks) Calculations:
2 3104 6208 (1a) Enter /cms 
line’s ‘kbytes’ figure 
divided by 1000 
(move decimal 
three places left): (1a) 4 7137  14274
6 11170  22340
8 15203  30406
10 19236   (1b) Enter “/cms 
Size” (above left) 
corresponding to 
the number of hard 
disks and disk size: (1b)
# metastat
...
d21: Mirror
    Submirror 0: d19
      State: Okay         
    Submirror 1: d20
      State: Okay
...
d19: Submirror of d21
    State: Okay         
    Size: 14398560 blocks
    Stripe 0:
        Device Start Block Dbase State        Hot Spare
        c0t0d0s3 0 No Okay 
    Stripe 1:
        Device  Start Block  Dbase State        Hot Spare
        c0t2d0s1 0 No Okay 
d20: Submirror of d21
    State: Okay         
    Size: 14398560 blocks
    Stripe 0:
        Device  Start Block  Dbase State        Hot Spare
        c0t1d0s3                   0     No    Okay         
    Stripe 1:
        Device  Start Block  Dbase State        Hot Spare
        c0t3d0s1                   0     No    Okay