Lucent Technologies CentreVu Release 3 Version 8 Disk-Mirrored... User manual

CentreVu
®Call Management System
Release 3 Version 8
Disk-Mirrored Systems
585-210-940
Comcode 108502352
Issue 1
December, 1999

Copyright 1999 Lucent Technologies
All Rights Reserved
Printed in U.S.A.
Notice
Every effort was made to ensure that the information in this book was
complete and accurate at the time of printing. However, information is
subject to change.
Your Responsibility for Your System’s Security
Toll fraud is the unauthorized use of your telecommunications system
by an unauthorized party, for example, persons other than your com-
pany’s employees, agents, subcontractors, or persons working on your
company’s behalf. Note that there may be a risk of toll fraud associ-
ated with your telecommunications system and, if toll fraud occurs, it
can result in substantial additional charges for your telecommunica-
tions services.
You and your system manager are responsible for the security of your
system, such as programming and configuring your equipment to pre-
vent unauthorized use. The system manager is also responsible for
reading all installation, instruction, and system administration docu-
ments provided with this product in order to fully understand the fea-
tures that can introduce risk of toll fraud and the steps that can be
taken to reduce that risk. Lucent Technologies does not warrant that
this product is immune from or will prevent unauthorized use of com-
mon-carrier telecommunication services or facilities accessed through
or connected to it. Lucent Technologies will not be responsible for any
charges that result from such unauthorized use.
Lucent Technologies Fraud Intervention
If you suspect that you are being victimized by toll fraud and you need
technical support or assistance, call Technical Service Center Toll
Fraud Intervention Hotline at 1-800-643-2353.
Trademarks
CentreVu is a registered trademark of Lucent Technologies.
AnswerBook, Enterprise, Solaris, SunLink, and Solstice DiskSuite are
trademarks of Sun Microsystems, Inc.
Sun and Sun Microsystems are registered trademarks of Sun Microsys-
tems, Inc.
INFORMIX is a registered trademark of Informix Software, Inc.
Ordering Information
Call: Lucent Technologies Publications Center
Voice: 1-800-457-1235
International Voice: 317-322-6416
Fax: [phone]
International Fax: [phone]
Write: Lucent Technologies BCS Publications Center
2855 N. Franklin Road
Indianapolis, IN 46219
Order: Document No. 585-210-940
Comcode 108502352
Issue 1, December 1999
You can be placed on a Standing Order list for this and other docu-
ments you may need. Standing Order will enable you to automatically
receive updated versions of individual documents or document sets,
billed to account information that you provide. For more information
on Standing Orders, or to be put on a list to receive future issues of this
document, contact the Lucent Technologies Publications Center.
Disclaimer
Intellectual property related to this product (including trademarks)
and registered to AT&T Corporation has been transferred to Lucent
Technologies Incorporated.
Any references within this text to American Telephone and Telegraph
Corporation or AT&T should be interpreted as references to Lucent
Technologies Incorporated. The exception is cross references to books
published prior to December 31, 1996, which retain their original
AT&T titles.
Heritage Statement
Lucent Technologies—formed as a result of AT&T’s planned restruc-
turing—designs, builds, and delivers a wide range of public and pri-
vate networks, communication systems and software, consumer and
business telephone systems, and microelectronics components. The
world-renowned Bell Laboratories is the research and development
arm for the company.
Comments
To comment on this document, return the comment card at the front of
the document.
Acknowledgment
This document was developed by the Lucent Technologies Product
Publications group of the Global Learning Solutions organization.

CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
i
Table of Contents
Chapter 1: Introduction to Disk Mirroring
Disk mirroring defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Metadevices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Concatenated metadevices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
State databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Mirrors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
How CMS implements disk mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Mirror layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Mirror layout on a Sun Enterprise 3000 computer. . . . . . . . . . . . . . . . . 7
Mirror layout on a Sun Enterprise 3500 computer. . . . . . . . . . . . . . . . . 8
Required hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Required software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Additional references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 2: Installing Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring. . . . . . . . . . . . . . . . . . 11
Disk drive slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Increasing system capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Step 1: Identify mirror devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Step 2: Install the mirror disks on an Enterprise 3500 system . . . . . . . . . . . 14
Step 3: Install the mirror disks on an Enterprise 3000 system . . . . . . . . . . . 16
Step 4: Partition the mirror disks . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Step 5: Create the state database replicas . . . . . . . . . . . . . . . . . . . . . . 18
Step 6: Create the md.tab table entries . . . . . . . . . . . . . . . . . . . . . . . . 18
Step 7: Set up the mirrors for the root file system . . . . . . . . . . . . . . . . . . 20
Step 8: Set up the mirrors for the swap space . . . . . . . . . . . . . . . . . . . . 22
Step 9: Set up the /cms mirror. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Step 10: Verify disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Step 11: Create an alternate boot device . . . . . . . . . . . . . . . . . . . . . . . 26
Factory installation procedures for disk mirroring . . . . . . . . . . . . . . . . . . . . . 28
Step 1: Install the hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Step 2: Install the operating system. . . . . . . . . . . . . . . . . . . . . . . . . . 28
Step 3: Install the application software . . . . . . . . . . . . . . . . . . . . . . . . 29
Step 4: Check the disk.type file . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Step 5: Set up the disk subsystem for Solstice DiskSuite. . . . . . . . . . . . . . 30
Step 6: Run the setup scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Step 7: Verify disk space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Step 8: Install the CMS software. . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Step 9: Create an alternate boot device. . . . . . . . . . . . . . . . . . . . . . . . 35

CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
ii
Chapter 3: Maintaining Mirrored Systems
Using the alternate boot device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Maintaining the chkDisks crontab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Activating chkDisks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Verifying chkDisks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Changing the scheduled run time . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Canceling chkDisks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Doing a CMSADM backup on a mirrored system . . . . . . . . . . . . . . . . . . . . . . . 41
Step 1: Print the vfstab file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Step 2: Run the backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Step 3: Label and store the tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Restoring from a CMSADM Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Repairing or rebuilding the /cms file system . . . . . . . . . . . . . . . . . . . . . . . . . 45
Repairing /cms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Rebuilding /cms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Restoring a mirrored system from a CMSADM backup. . . . . . . . . . . . . . . . . . . . 49
Step 1: Power off the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Step 2: Install the new drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Step 3: Boot the system from the compact disk . . . . . . . . . . . . . . . . . . . 50
Step 4: Identify the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Step 5: Set the Name Service options . . . . . . . . . . . . . . . . . . . . . . . . . 52
Step 6: Set the date and time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Step 7: Select the operating system files to be installed . . . . . . . . . . . . . . . 54
Step 8: Select the hard disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Step 9: Set up the disk partitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Step 10: Install the operating system . . . . . . . . . . . . . . . . . . . . . . . . . 57
Step 11: Complete the OS installation . . . . . . . . . . . . . . . . . . . . . . . . . 58
Step 12: Alter the tape configuration file (Enterprise 3500 only). . . . . . . . . . . 58
Step 13: Restore the backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Step 14: Reestablish the disk mirrors . . . . . . . . . . . . . . . . . . . . . . . . . 59
Restoring specific files from a CMSADM backup . . . . . . . . . . . . . . . . . . . . . . . 62
Adding new disks to a standard mirrored system . . . . . . . . . . . . . . . . . . . . . . 63
Adding new disks to a nonstandard mirrored system . . . . . . . . . . . . . . . . . . . . 66
Replacing a faulty disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Step 1: Identify the faulty disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Step 2: Identify the submirrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Step 3: Detach the submirrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Step 4: Remove state database replicas (boot disks only) . . . . . . . . . . . . . . 72
Step 5: Replace the faulty disk drive . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Step 6: Recreate the state database replicas . . . . . . . . . . . . . . . . . . . . . 73
Step 7: Reattach the submirrors . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Step 8: Reboot the system (boot disks only) . . . . . . . . . . . . . . . . . . . . . 74
State Database Replicas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Setting up replicas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Replacing replicas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
iii
Partitioning disks with the format command . . . . . . . . . . . . . . . . . . . . . . . . . 76
How to tell whether your mirrored system is standard . . . . . . . . . . . . . . . . . . . . 78
Examples of valid system files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Valid vfstab files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Valid md.tab files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Chapter 4: Troubleshooting
Solstice DiskSuite problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
The root filesystem runs out of space during a system install. . . . . . . . . . . . 81
Excessively long resync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
The system fails to recognize all disk drives . . . . . . . . . . . . . . . . . . . . . . . . . 82
Fixing “needs maintenance” messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Boot problems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Trying to boot from the wrong device . . . . . . . . . . . . . . . . . . . . . . . . . 85
Primary boot device is not available . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Excessive reboot time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
iv

Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Disk mirroring defined 1
1
Introduction to Disk Mirroring1
This chapter introduces you to “disk mirroring,” an optional
feature of CentreVu

Call Management System (CMS) that
provides you with a completely redundant set of data, helping
to ensure data security. To use disk mirroring, you must have a
Sun
*
Enterprise
*
3000 or Sun Enterprise 3500 platform running
CMS r3v8.
Disk mirroring defined 1
“Mirrors” are a feature of the Solstice DiskSuite
*software package. They
allow you to build a hard disk system containing two—or even three—
complete sets of data. Having such data redundancy greatly reduces the
risk of data loss should a hard disk drive fail or your system crash. While
mirrors greatly reduce the risk of losing data, however, they are not
meant to be a substitute for regular backups. Mirrored systems must be
backed up just as often as unmirrored systems.
Metadevices 1The
Solstice DiskSuite software package allows multiple disk partitions to
be logically combined to create a single large partition. Using the
Solstice
DiskSuite
package allows CMS databases to span multiple disks, and so
grow quite large.
Solstice DiskSuite uses virtual disks to manage physical disks and their
associated data. In
Solstice DiskSuite , a virtual disk is called a
metadevice. To a software application, a metadevice is identical to a
physical disk drive.
Solstice DiskSuite handles all I/O requests directed at
a metadevice, converting them into I/O requests for the underlying disks.
Solstice DiskSuite metadevices are built from slices (disk partitions). A
system controlled by
Solstice DiskSuite may contain any number of
metadevices, each of which may comprise any combination of disk
partitions.
Once a metadevice has been set up, the underlying disk partitions
can be accessed only through the metadevice.
* Sun , Enterprise , and Solstice DiskSuite are trademarks or registered trademarks of Sun Microsystems, Inc.

Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Disk mirroring defined 2
The illustration below shows a simple, two-slice metadevice.
Concatenated
metadevices 1
A metadevice can be configured as any one of three basic types: striped,
concatenated,
or concatenated stripes . The type used by CMS systems
is the concatenated metadevice. In a concatenated metadevice, data
blocks, or
chunks , are written sequentially across the slices, beginning
with the first disk.
Consider, for example, a concatenated metadevice with three slices (see
the illustration below.) In that scenario, disk A can be envisioned as
containing logical chunks 1 through 4, disk B as containing logical
chunks 5 through 8, and disk C as containing chunks 9 through 12.
c0t0d0s2
c1t0d0s2
c0t0d0s2
Physical Disks A & B Metadevice d0
c1t0d0s2
Chunk 3
Chunk 4
Chunk 2
Chunk 1
Chunk 7
Chunk 8
Chunk 6
Chunk 5
Chunk 11
Chunk 12
Chunk 10
Chunk 9
Solstice DiskSuite
. . .
Chunk 2
Chunk 1
Chunk 12
. . .
. . .
Physical Disk A
Physical Disk B
Physical Disk C
Metadevice d1

Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Disk mirroring defined 3
The total capacity of this concatenated metadevice is the combined
capacities of the three drives. If each drive is 4 gigabytes, for example,
the metadevice has an overall capacity of 12 gigabytes.
State databases 1The
Solstice DiskSuite software tracks which disk partitions belong to
which metadevices with a state database. A state database stores
information on disk about the state of your
Solstice DiskSuite
configuration.
The state database consists of multiple copies of the basic database. The
copies, referred to as state database replicas, ensure that the data in
the database is always valid. Having multiple copies protects against
data loss from single points-of-failure. The state database tracks the
location and status of all state database replicas.
Solstice DiskSuite
cannot operate until you have created the state database and its replicas:
the software must have an operating state database.
Mirrors 1A mirror is a metadevice that can copy data from one metadevice to
another. The metadevices containing the data are called submirrors.
The process of copying the data between submirrors is called mirroring.
Mirroring provides redundant copies of data. To a software application, a
mirror looks just like a physical disk. The mirror accepts I/O requests and
converts them into I/O requests for the submirrors. The submirrors in
turn—being metadevices themselves—convert I/O requests from the
mirror into I/O requests for the underlying physical disks.
A mirror can be two-way or three-way. A two-way mirror is a mirror with
two submirrors; a three-way mirror has three submirrors. CMS supports
only two-way mirrors. The illustration below shows a typical two-way
mirror, d21, consisting of the submirrors d19 and d20.

Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Disk mirroring defined 4
Chunk 3
Chunk 4
Chunk 2
Chunk 1
Chunk 3
Chunk 4
Chunk 2
Chunk 1
Solstice DiskSuite
Metadevice d19
Metadevice d20
Metadevice d21
Chunk 3
Chunk 4
Chunk 2
Chunk 1

Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring 5
How CMS implements disk mirroring 1
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
. . .
c0t0d0s3 c0t1d0s1 (disk n)
d19
/cms
. . .
c0t0d0s3 c0t2d0s1 (disk n)
d20
d21
c0t1d0s3 c0t3d0s1
(disk n)
. . .

Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring 6
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 mirroring 7
Mirror layouts 1Mirror 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.
Disks submirror d11 submirror d12 submirror d19 submirror d20 submirror d15 submirror d16
2 c0t0d0s0 c0t1d0s0 c0t0d0s3 c0t1d0s3 c0t0d0s4 c0t1d0s4
4c0t0d0s0 c0t1d0s0 c0t0d0s3
c0t2d0s1 c0t1d0s3 c0t3d0s1 c0t0d0s4 c0t1d0s4
6c0t0d0s0 c0t1d0s0 c0t0d0s3
c0t2d0s1
c0t10d0s1
c0t1d0s3
c0t3d0s1
c0t11d0s1 c0t0d0s4 c0t1d0s4
8
c0t0d0s0 c0t1d0s0
c0t0d0s3
c0t2d0s1
c0t10d0s1
c0t12d0s1
c0t1d0s3
c0t3d0s1
c0t11d0s1
c0t13d0s1
c0t0d0s4 c0t1d0s4
10
c0t0d0s0 c0t1d0s0
c0t0d0s3
c0t2d0s1
c0t10d0s1
c0t12d0s1
c0t14d0s1
c0t1d0s3
c0t3d0s1
c0t11d0s1
c0t13d0s1
c0t15d0s1
c0t0d0s4 c0t1d0s4

Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring 8
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 hardware 1In order for your CMS system to be mirrored, it must have the following
hardware installed in addition to the hardware already installed:
●For 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).
●For a
Sun Enterprise 3500 system, a fiber cable to connect the UA
port GBIC to GBIC Port 1 on the I/O board.
●Twice the number of disk drives needed for an unmirrored system.
All the disks must be the same size.
mirror d13
/
(root) filesystem mirror d21 /cms filesystem
mirror d17
swap partition
(CMS r3v8)
No.
Disks submirror d11 submirror d12 submirror d19 submirror d20 submirror d15 submirror d16
2 c0t0d0s0 c1t4d0s0 c0t0d0s3 c1t4d0s3 c0t0d0s4 c1t4d0s4
4 c0t0d0s0 c1t4d0s0 c0t0d0s3
c0t1d0s1 c1t4d0s3 c1t5d0s1 c0t0d0s4 c1t4d0s4
6 c0t0d0s0 c1t4d0s0 c0t0d0s3 c0t1d0s1
c0t2d0s1
c1t4d0s3
c1t5d0s1
c1t6d0s1 c0t0d0s4 c1t4d0s4
8 c0t0d0s0 c1t4d0s0
c0t0d0s3
c0t1d0s1
c0t2d0s1
c0t3d0s1
c1t4d0s3
c1t5d0s1
c1t6d0s1
c1t7d0s1
c0t0d0s4 c1t4d0s4

Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring 9
Required software 1In 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 mirroring 10

Installing Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring 11
2
Installing Mirrored Systems 2
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 mirroring 2
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 slots 2Before 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 arenormally 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 mirroring 12
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 yoursystem. 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
Enterprise 3000 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:
●Record the slice 0 device name as submirror 12.
●Record the slice 3 device name as disk 1 of submirror 20.
●If 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): c0t2d0s0 CMS disk 1: c0t2d0s3
Submirror d16 Device
(r3v6aj.c or later)
swap c0t2d0s4

Installing Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring 13
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 Names Submirror d20 Device Names
CMS disk 1: c0t0d0s3 CMS disk 1: c0t2d0s3
CMS disk 2: c0t1d0s1 CMS 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 Name Submirror d12 Device Name Submirror d19 Device Names Submiror d20 Device Names
boot disk 1: c0t0d0s0 boot disk 2: s0 CMS disk 1: c0t0d0s3 CMS disk 1: s3
CMS disk 2: s1 CMS disk 2: s1
Submirror d15
Device Name
(r3v6aj.c and later)
Submirror d16
Device Name
(r3v6aj.c and later)
CMS disk 3: s1 CMS disk 3: s1
CMS disk 4: s1 CMS Disk 4: s1
swap, disk 1: c0t0d0s4 swap, disk 2 s4 CMS disk 5: s1 CMS disk 5: s1
Device/Metadevice Names for an Enterprise 3500 system
Submirror d11
Device Name Submirror d12 Device Name Submirror d19 Device Names Submiror d20 Device Names
boot disk 1: c0t0d0s0 boot disk 2: c1t4d0s0 CMS disk 1: c0t0d0s3 CMS disk 1: c1t4d0s3
Submirror d15
Device Name
(r3v6aj.c and later)
Submirror d16
Device Name
(r3v6aj.c and later)
CMS disk 2: c0t1d0s1 CMS disk 3: c1t5d0s1
CMS disk 3: c0t2d0s1 CMS Disk 4: c1t6d0s1
swap, disk 1: c0t0d0s4 swap, disk 2 c1t4d0s4 CMS disk 4: c0t3d0s1 CMS disk 5: c1t7d0s1

Installing Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring 14
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:
●Install a GigaByte Interface Converter (GBIC) into slot UA on
the Interface board.
●Install another GBIC into port 1 on the SBus I/O board.
●Install 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.