Lucent Technologies CentreVu Call Management System Release 3 Version 8 Guide

							  Introduction to Disk Mirroring  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring5
How CMS implements disk mirroring1
A nonmirrored, CMS system with Solstice DiskSuite uses it to create a 
single metadevice, named d19, containing all the disk partitions used to 
store CMS data. For example: 
To implement disk mirroring, a metadevice d20 is created as a duplicate 
of d19, and the two metadevices are configured as submirrors of d21, as 
shown in the following example: 
d19
/cms
. . .
c0t0d0s3c0t1d0s1(disk n)
d19
/cms
. . .
c0t0d0s3c0t2d0s1(disk n)
d20
d21
c0t1d0s3c0t3d0s1(disk n)
. . . 
						

							  Introduction to Disk Mirroring  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring6
In a CMS computer system with 
/cms mirrored, root is also mirrored. The 
root mirror is d13; its submirrors are d11 and d12. For example:
If your computer system is running CMS r3v8, your swap partition is also 
mirrored. The swap mirror is d17; its submirrors are d15 and d16. For 
example:
d11
/ (root)
c0t0d0s0
d12
d13
c0t1d0s0
d15
swap
c0t0d0s4
d16
d17
c1t4d0s4 
						

							  Introduction to Disk Mirroring  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring7
Mirror layouts1Mirror layouts on a factory-installed mirrored system differ depending 
upon the platform. When a system is upgraded to mirroring in the field, 
mirror layouts are essentially unpredictable, and depend on how many 
disk drives are already installed, and what their target numbers are.
Mirror layout on a Sun 
Enterprise 
3000 
computer
1
On a Sun Enterprise 3000 platform with factory-installed mirroring, the 
mirror layout is the simple odd/even arrangement shown in the table 
below. A system upgraded to mirroring in the field probably has a 
different mirror layout.
mirror d13
(/ 
(root) filesystem)mirror d21
(/cms filesystem)mirror d17
(swap partition)
(CMS r3v8)
No. 
Diskssubmirror 
d11submirror
d12submirror
d19submirror
d20submirror
d15submirror
d16
2 c0t0d0s0 c0t1d0s0 c0t0d0s3 c0t1d0s3 c0t0d0s4 c0t1d0s4
4
c0t0d0s0  c0t1d0s0c0t0d0s3
c0t2d0s1c0t1d0s3
c0t3d0s1c0t0d0s4  c0t1d0s4
6
c0t0d0s0 c0t1d0s0c0t0d0s3
c0t2d0s1
c0t10d0s1c0t1d0s3
c0t3d0s1
c0t11d0s1c0t0d0s4 c0t1d0s4
8
c0t0d0s0 c0t1d0s0c0t0d0s3
c0t2d0s1
c0t10d0s1
c0t12d0s1c0t1d0s3
c0t3d0s1
c0t11d0s1
c0t13d0s1c0t0d0s4 c0t1d0s4
10
c0t0d0s0 c0t1d0s0c0t0d0s3
c0t2d0s1
c0t10d0s1
c0t12d0s1
c0t14d0s1c0t1d0s3
c0t3d0s1
c0t11d0s1
c0t13d0s1
c0t15d0s1c0t0d0s4 c0t1d0s4 
						

							  Introduction to Disk Mirroring  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring8
Mirror layout on a Sun 
Enterprise 
3500 
computer
1
On a Sun Enterprise 3500 platform, the mirror layout must always be 
based upon the bays in which the disks are installed. Submirrors 11, 15, 
and 19 are the disks in the lower bay (targets 0 through 3 on controller 0); 
submirrors 12,16, and 20 are the disks in the upper bay (targets 4 
through 7 on controller 1). The table below shows the mirror layout.
Required hardware1In order for your CMS system to be mirrored, it must have the following 
hardware installed in addition to the hardware already installed:
lFor a Sun Enterprise 3500 system, two GigaByte Interface 
Converter (GBIC) modules. One will be installed into the UA slot on 
the FC-AL Interface board, and the other will be installed into GBIC 
Port 1 on the Sbus I/O board (see the illustration on page 15).
lFor a Sun Enterprise 3500 system, a fiber cable to connect the UA 
port GBIC to GBIC Port 1 on the I/O board.
lTwice the number of disk drives needed for an unmirrored system. 
All the disks must be the same size. mirror d13
/ 
(root) filesystemmirror d21/cms filesystemmirror d17
swap partition
(CMS r3v8)
No. 
Diskssubmirror
d11submirror
d12submirror
d19submirror
d20submirror
d15submirror
d16
2 c0t0d0s0 c1t4d0s0 c0t0d0s3 c1t4d0s3 c0t0d0s4 c1t4d0s4
4 c0t0d0s0 c1t4d0s0c0t0d0s3
c0t1d0s1c1t4d0s3
c1t5d0s1c0t0d0s4 c1t4d0s4
6 c0t0d0s0 c1t4d0s0c0t0d0s3
c0t1d0s1
c0t2d0s1c1t4d0s3
c1t5d0s1
c1t6d0s1c0t0d0s4 c1t4d0s4
8 c0t0d0s0 c1t4d0s0c0t0d0s3
c0t1d0s1
c0t2d0s1
c0t3d0s1c1t4d0s3
c1t5d0s1
c1t6d0s1
c1t7d0s1c0t0d0s4 c1t4d0s4 
						

							  Introduction to Disk Mirroring  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring9
Required software1In order for your CMS system to be mirrored, it must be running the 
following software:
For a list of other software required for your system, see the Lucent 
Technologies Software Installation manual for your version of CMS.
Additional 
references
1
Sun Microsystems* documentation related to Solstice DiskSuite and disk 
maintenance and configuration includes: 
Solstice DiskSuite 4.2 Administration Guide 
Solstice DiskSuite Tool 4.2 User` s Guide 
CMS R3V8
Solaris 7 dated 3/99
Solstice DiskSuite 4.2
any CMS r3v8 load
*Sun Microsystems is a registered trademark of Sun Microsystems, Inc. 
						

							  Introduction to Disk Mirroring  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring10 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring11
2
Installing Mirrored Systems2
This chapter contains procedures for upgrading existing 
computer
 systems to use disk mirroring and for installing a 
mirrored system under factory conditions.
How to upgrade an Enterprise platform to disk mirroring2
This section tells how to upgrade CentreVuâ Call Management System 
(CMS) on a 
Sun Enterprise 3000 or 3500 computer from a nonmirrored 
system to a mirrored system.
Disk drive slots2Before you begin, you must understand the drive slot arrangement in 
your system. 
In an 
Enterprise 3000 computer, there are 10 slots, allowing up to five 
disks for each mirror. Each slot is labeled with a number 0 through 3 or 10 
through 15; there are no slots numbered 4 through 9. All the drive slots 
are on controller 0. 
In an 
Enterprise 3500 computer, there are eight disk drive slots, four in 
each of two bays. The slots in the lower bay are labeled 0 through 3 and 
are on controller 0; the slots in the upper bay are numbered 4 through 7 
and are on controller 1. In a mirrored system, slots 0 through 3 are 
reserved for the original disks, and slots 4 through 7 are reserved for the 
mirror disks.
The slot number is the drive’s target number, which becomes part of the 
device name. A drive in slot 1, for example, has the device name 
c0t1d0. 
The drive in slot 0 is always the primary boot disk. 
In an 
Enterprise 3000 mirrored system, mirror disks are normally installed 
in target number order, beginning with the first empty slot. That makes it 
difficult to predict the mirror layout on an upgraded system. In an 
Enterprise 3500 mirrored system, however, mirror disks always go in the 
upper bay. If you are mirroring a two-disk system, for example, the two 
original disks would already be installed in slots 0 and 1 in the lower bay, 
and you would install the two new disks in slots 4 and 5 in the upper bay.  
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring12
Increasing system 
capacity
2
If you intend to increase your system capacity as well as mirror your 
system, first install the new disks needed to increase capacity. For 
instructions, see the documentation that came with the new drives or the 
appropriate Lucent Technologies installation documents. After the system 
capacity has been increased, and it has been verified that the system 
works correctly, you may then install disk mirroring. You must make 
certain the basic system works before you try to mirror the disks. 
Step 1: Identify 
mirror devices
2
1. Check the number of new disks to be installed as the mirror.
There should be as many new disks to be installed as there are old 
disks already on your system. That keeps the same system capacity 
and makes the two submirrors the same size. 
2. Next you must identify the device names for your mirrored system 
and record them in the 
Device/Metadevice Names table on the next 
page. 
If you have an 
Enterprise 3500 system, the device names have 
already been identified and recorded for you in the 
Enterprise 3500 
table. Here’s how you identify the device names for an 
Enterprise3000 system:
a.
Identify the secondary boot disk and record the device 
names.
 
Find the first empty slot in your system. Whatever slot you find 
will hold the secondary boot disk. Then record the following 
device names for that disk:
lRecord the slice 0 device name as submirror 12.
lRecord the slice 3 device name as disk 1 of submirror 20. 
lIf your system is running load r3v6aj.c or later of CMS—
you can find out by executing a pkginfo -x cms 
command—record the slice 4 device as submirror 16.
Example: If the first empty drive slot in your system were 
slot 2, you would record the following values in the table:
Submirror d12
Device Name. . .Submirror d20
Device Names
boot disk (2):
c0t2d0s0CMS disk 1:c0t2d0s3
Submirror d16 Device
(r3v6aj.c or later)
swapc0t2d0s4 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring13
b. Record existing nonboot disks under submirror 19, and empty 
slots for new nonboot disks under submirror 20.
Example: Imagine a system that already has two disk drives in 
slots 0 and 1. In the previous step, you would have reserved 
slot 2 for the second boot disk. The remaining new disk is a 
nonboot disk and will be installed in slot 3. So you would record 
the following values in the table:
Submirror d19
Device NamesSubmirror d20
Device Names
CMS disk 1: c0t0d0s3
CMS disk 1: c0t2d0s3
CMS disk 2:c0t1d0s1CMS disk 2:c0t3d0s1
CMS disk 3:CMS disk 3:
CMS disk 4:CMS Disk 4:
CMS disk 5:CMS disk 5:
Device/Metadevice Names for an Enterprise 3000 system
Submirror d11
Device NameSubmirror d12
Device NameSubmirror d19
Device NamesSubmiror d20
Device Names
boot disk 1:  c0t0d0s0boot disk 2: s0CMS disk 1: c0t0d0s3CMS disk 1: s3
CMS disk 2: s1CMS disk 2: s1
Submirror d15
Device Name
(r3v6aj.c and later)Submirror d16
Device Name
(r3v6aj.c and later)CMS disk 3: s1CMS disk 3: s1
CMS disk 4: s1CMS Disk 4: s1
swap, disk 1: c0t0d0s4swap, disk 2 s4CMS disk 5: s1CMS disk 5: s1
Device/Metadevice Names for an Enterprise 3500 system
Submirror d11
Device NameSubmirror d12
Device NameSubmirror d19
Device NamesSubmiror d20
Device Names
boot disk 1: c0t0d0s0boot disk 2:c1t4d0s0CMS disk 1:c0t0d0s3CMS disk 1:c1t4d0s3
Submirror d15
Device Name
(r3v6aj.c and later)Submirror d16
Device Name
(r3v6aj.c and later)CMS disk 2:c0t1d0s1CMS disk 3:c1t5d0s1
CMS disk 3:c0t2d0s1CMS Disk 4:c1t6d0s1
swap, disk 1:c0t0d0s4swap, disk 2c1t4d0s4CMS disk 4:c0t3d0s1CMS disk 5:c1t7d0s1 
						

							  Installing Mirrored Systems  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring14
Step 2: Install the 
mirror disks on an 
Enterprise 3500 
system
2
Do this step only if you have an Enterprise 3500 system.
It is likely that your 
Enterprise 3500 system is currently using controller 1 
(c1) for the internal CD-ROM drive. This step associates the CD-ROM 
drive with controller 2 (c 2) so controller 1 will be free for the new disk 
drives. In this step you also install some additional hardware for 
controlling the new disks, and install the new disks themselves. You 
should be logged in as 
root before beginning this step.
1. Enter the following command:
______________________________________________________
# ls -l /dev/dsk/c1t6d0s0
______________________________________________________
The system should respond with a line similar to the following:
______________________________________________________
lrwxrwxrwx 1 roor roor 50 Nov 16 08:58 
/dev/dsk/c1t6d0s0 -> ../../devices/sbus@3,0 
/SUNW,fas@3,8800000/sd@6,0:a
______________________________________________________
Notice that c1t6d0s0 is pointing to sd@6,0:a. That indicates that 
controller 1 is being used by the CD-ROM drive. Remove that 
association by entering the following commands:
______________________________________________________
# rm /dev/dsk/c1*
# rm /dev/rdsk/c1*
# touch /reconfigure
# /usr/sbin/shutdown -y -g0 -i0
______________________________________________________
2. Install new hardware components as follows:
lInstall a GigaByte Interface Converter (GBIC) into slot UA on 
the Interface board.
lInstall another GBIC into port 1 on the SBus I/O board.
lInstall a fiber cable between the two newly installed GBICs.
The illustration below shows where the GBICs are installed. For 
more detailed information, see 
CentreVu CMS Sun Enterprise 3500 
System (connectivity diagram) 
(585-215-877), which was packed 
with your system.