Lucent Technologies 585-210-940 User Manual
CentreVu
Call Management System
Release 3 Version 8
Disk-Mirrored Systems
®
585-210-940
Comcode 1085023 52
Issue 1
December, 1999
Copyright 1999 Lucent Technologies
All Rights Reserved
Printed in U.S.A.
Disclaimer
Intellectual property rel a te d to t his product (including trad emarks)
and registered to AT&T Corporation has been transferred to Lu cent
Technologies Incorporated.
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 ot her 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 associated with your telecommunications system and, if toll fraud occurs, it
can result in s u bstantial ad ditional charges f or your telecommunications services.
You and your system manager are responsible for the security of your
system, such as programming and configuring your equipm ent to prevent unauthorized use. The system m anager is also responsible for
reading all installation, instruction, and system administr ation documents provided with this product in order to fully understand the features that ca n introduce risk of toll fraud and the steps th at can be
taken to reduce that risk. Lucent Technologies does not warrant that
this product is immune from or will prevent unauthorized use of common-carrier telecommunication services or facilities accessed through
or connected to it. Lucent Technologies will not be responsible for any
charges that resul t from such unautho rized 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 Hotlin e at 1-800-643-2353.
Any references within this te xt to A merican 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 Statem en t
Lucent Technologies—formed as a result of AT&T’s planned restructuring—designs, builds, a nd de li ve rs a w id e ra nge of public and private 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 develop ed by the Lucent Technologies Product
Publications group of the Global Le arning Solutions organization.
Trademarks
CentreVu is a regist ered trademark of Lucent Technologies.
AnswerBook, Enterprise, Sol aris, SunLink, and Solstice DiskSuite are
trademarks of Sun Microsystem s, Inc.
Sun and Sun Microsystems are registered trademarks of Sun Microsystems, Inc.
INFORMIX is a registered tradem ar k of Informix Software, Inc.
Ordering Information
Call: Lucent Technologies Publications Center
Voice: 1-800-457-1235
International Voice: 317-322-6416
Fax: 1-800-457-1764
International Fax: 317-322-6699
Write: Lucent Technologi es BCS Publications Center
2855 N. Franklin Road
Indianapolis, IN 46219
Order: Document No. 585-210-94 0
Comcode 108502352
Issue 1, December 19 99
You can be placed on a Standi ng Order list for this and other documents you may need. Standing Order will enable you to automatically
receive updated versions of individual documen ts or doc um e nt sets,
billed to account inform ation that you provide. For mor e in formation
on Standing Orders, or to be put on a list to receive future issues of this
document, contact th e L ucent Technologies Publications Center.
CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
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
i
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
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
ii
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 fi le (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
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
iii
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
provides you with a completely redundant set of data, helping
to ensure data sec urity. T o use disk mirrorin g, you must have a
*
Sun
Enterprise* 3000 or Sun Enterprise 3500 platfor m running
CMS r3v8.
Call Management System (CMS) that
Disk mirroring defined 1
*
software package. They
Solstice
Metadevices 1
“Mirrors” are a feature of th e
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 syste ms must be
backed up just as often as unmirrored systems.
The
Solstice DiskSuite
be logically combined to create a single large p artition. Using the
DiskSuite
grow quite large.
package allows CMS databases to span mul tiple disk s, and so
software package allows multiple disk partitions to
Solstice DiskSuite
*
Sun, Enterprise
, and
Solstice DiskSuite
Solstice DiskSuite
associated data. In
metadevice. To a software application, a metadevice is identical to a
physical disk driv e.
a metadevice, converting them into I/O request s for the under ly ing disks.
Solstice DiskSuite
system controlled by
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.
are trademarks or registered trademarks of Sun Microsystems, Inc.
uses virtual disks to manage physical disks and their
Solstice DiskSuite
Solstice DiskSuite
metadevices are built from slices (disk partitions). A
Solstice DiskSuite
, a virtual disk is called a
handles all I/O requests directed at
may contain any number of
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.
Physical Disks A & B Metadevice d0
c0t0d0s2
c0t0d0s2
c1t0d0s2
c1t0d0s2
Concatenated metadevice s 1
A metadevice can be configured as any one of three basic types :
concatenated,
or
concatenated stripes
. The type used by CMS systems
striped,
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 concat enated met adevi ce with t hr ee slic es (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.
Physical Disk A
Chunk 1
Chunk 2
Chunk 3
Chunk 4
Physical Disk B
Chunk 5
Chunk 6
Chunk 7
Chunk 8
Physical Disk C
Chunk 9
Chunk 10
Chunk 11
Chunk 12
Solstice DiskSuite
Metadevice d1
Chunk 1
Chunk 2
. . .
. . .
. . .
Chunk 12
Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Disk mirroring defined 3
The total capacit y 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.
The
St ate databases 1
Solstice DiskSuite
which metadevices with a state database. A state database stores
information on disk about the state of your
configuration.
The state database consist s of multiple copies of the basic dat abase. 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 databas e trac ks the
location and status of all state database replicas.
cannot operate until you hav e created the st ate dat abase and it s replicas:
the software must have an operating state database.
software tracks which disk partitions belong to
Solstice DiskSuite
Solstice DiskSuite
Mirrors 1
A 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 physi cal di sk. The mir ror acc ept s I/ O reque st s 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 submi rrors. 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
Metadevice d19
Chunk 1
Chunk 2
Chunk 3
Chunk 4
Solstice DiskSuite
Chunk 1
Chunk 2
Chunk 3
Chunk 4
Metadevice d21
Chunk 1
Chunk 2
Chunk 3
Chunk 4
Metadevice d20
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:
/cms
d19
c0t0d0s3
c0t1d0s1
. . .
(disk n)
To implement disk mirroring, a metadevice d20 is created as a duplicate
of d19, and the two met adevices are configured as submirrors of d21, as
shown in the following example:
/cms
d19
. . .
d21
d20
c0t0d0s3
c0t1d0s3
c0t2d0s1
c0t3d0s1
(disk n)
. . .
(disk n)
Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring 6
/cms
In a CMS computer system with
mirrored,
root
is also mirrored. The
root mirror is d13; its submirrors are d11 and d12. For example:
/
(root)
d11
c0t0d0s0
d13
d12
c0t1d0s0
If your computer system is running CMS r3v8, your swap partition i s also
mirrored. The swap mirror is d17; its submirrors are d15 and d16. For
example:
swap
d15
c0t0d0s4
d17
d16
c1t4d0s4
Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring 7
Mirror layout s 1
Mirror layout on a
Enterprise
3000
computer 1
No.
Disks
2 c0t0d0s0 c0t1d0s0 c0t0d0s3 c0t1d0s3 c0t0d0s4 c0t1d0s4
4
6
submirror
Sun
mirror d13
(/
(root)
d11
c0t0d0s0 c0t1d0s0
c0t0d0s0 c0t1d0s0
Mirror layouts on a factory-installed mirrored system diff er depending
upon the platform. When a system is upgraded to mirroring in the field,
mirror layouts are essenti ally unpredictable, and depend on how many
disk drives are already installed, and what their target numbers are.
On a
Sun Enterprise
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.
filesystem)
submirror
d12
submirror
c0t10d0s1
3000 platform with factory-installed mirroring, the
mirror d21
(
/cms
d19
c0t0d0s3
c0t2d0s1
c0t0d0s3
c0t2d0s1
filesystem)
submirror
d20
c0t1d0s3
c0t3d0s1
c0t1d0s3
c0t3d0s1
c0t11d0s1
submirror
c0t0d0s4 c0t1d0s4
c0t0d0s4 c0t1d0s4
mirror d17
(swap partition)
(CMS r3v8)
d15
submirror
d16
8
10
c0t0d0s0 c0t1d0s0
c0t0d0s0 c0t1d0s0
c0t0d0s3
c0t2d0s1
c0t10d0s1
c0t12d0s1
c0t0d0s3
c0t2d0s1
c0t10d0s1
c0t12d0s1
c0t14d0s1
c0t1d0s3
c0t3d0s1
c0t11d0s1
c0t13d0s1
c0t1d0s3
c0t3d0s1
c0t11d0s1
c0t13d0s1
c0t15d0s1
c0t0d0s4 c0t1d0s4
c0t0d0s4 c0t1d0s4
Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring 8
On a
Mirror layout on a
Enterprise
3500
Sun
computer 1
Sun Enterprise
based upon the bays in which the disks are installed. Submirrors 11, 15,
and 19 are the disks in the lower bay (target s 0 through 3 on controll er 0);
3500 platform, the mirror layout must always be
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.
mirror d17
swap partition
(CMS r3v8)
submirror
d15
d16
No.
Disks
mirror d13
(root)
/
submirror
d11
filesystem
submirror
d12
mirror d21
/cms
submirror
d19
filesystem
submirror
d20
submirror
2 c0t0d0s0 c1t4d0s0 c0t0d0s3 c1t4d0s3 c0t0d0s4 c1t4d0s4
4 c0t0d0s0 c1t4d0s0
6 c0t0d0s0 c1t4d0s0
8 c0t0d0s0 c1t4d0s0
c0t0d0s3
c0t1d0s1
c0t0d0s3
c0t1d0s1
c0t2d0s1
c0t0d0s3
c0t1d0s1
c0t2d0s1
c0t3d0s1
c1t4d0s3
c1t5d0s1
c1t4d0s3
c1t5d0s1
c1t6d0s1
c1t4d0s3
c1t5d0s1
c1t6d0s1
c1t7d0s1
c0t0d0s4 c1t4d0s4
c0t0d0s4 c1t4d0s4
c0t0d0s4 c1t4d0s4
Required hardware 1
In 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 inst alled 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.
Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How CMS implements disk mirroring 9
Required software 1
Additional references
In order for your CMS system to be mirrored, it must be running the
following software:
CMS R3V8
Solaris
Solstice DiskSuite
7 dated 3/99
4.2
any CMS r3v8 load
For a list of other software required for your system, see the Lucent
Technologies Software Installation manual for your version of CMS.
Sun Microsystems*
maintenance and configuration includes:
1
documentation rel a ted to
Solstice DiskSuite
Solstice DiskSuite 4.2 Administration Guide
Solstice DiskSuite Tool 4.2 User‘s Guide
and disk
*
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 procedur es for upgrading existing
computer
mirrored system under factory conditions.
systems to use disk mirroring and for installing a
How to upgrade an
This section tells how to upgrade
(CMS) on a
system to a mirrored system.
Disk drive slots 2
Before you begin, you must understand the drive slot arrangement in
your system.
In an
disks for each mirror. Each slot is labeled with a number 0 th rough 3 or 1 0
through 15; there are no slots numbered 4 through 9. All the drive slots
are on controller 0.
In an
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, f or exampl e, has the devi ce name
The drive in slot 0 is always the primary boot disk.
Enterprise
Sun Enterpr is e
Enterprise
Enterprise
3000 computer, there are 10 slots, allowing up to five
3500 computer, there are eight disk drive slots, four in
platform to disk mirroring 2
CentreVu
3000 or 3500 computer from a nonmirrored
Call Management System
c0t1d0
.
Enterprise
In an
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
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.
3000 mirrored system, mirror disks are normally installed
3500 mirrored system, however, mirror disks always go in the
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
Step 1: Identify mirror devices
If you intend to increase your system capacity as well as mirror your
system, first install the new disks needed to increase capacity. For
2
instructions, see the documentation that came with the new drives or the
appropriate Lucent Technologies installati on 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.
1. Check the number of new disks to be installed as the mirror.
2
There should be as many new disks to be installed as there are old
disks already on your system. That keeps the same system cap acity
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
already been identified and recorded for you in the
3500 system, the device names have
Enterprise
table. Here’s how you identify the device names for an
Enterprise
3000 system:
3500
Identify the secondary boot disk and record the device
a.
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 di sk 1 of submirror 20.
●
If your system is running load r3v6aj.c or late r 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
boot disk (2):
Submirror d16 Device
(r3v6aj.c or later)
swap c0t2d0s4
c0t2d0s0 CMS disk 1: c0t2d0s3
. . .
Submirror d20
Device Names
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 di sk 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
CMS disk 1: c0t0d0s3
CMS disk 2:
CMS disk 3: CMS disk 3:
CMS disk 4: CMS Disk 4:
CMS disk 5: CMS disk 5:
Device/Metadevice Names for an
Submirror d1 1
Device Name
boot disk 1: c0t0d0s0 boot disk 2: s0 CMS disk 1: c0t0d0s3 CMS disk 1: s3
Submirror d15
Device Name
(r3v6aj.c and later)
Submirror d12
Device Name
Submirror d16
Device Name
(r3v6aj.c and later)
c0t1d0s1
Enterprise
Submirror d19
Device Names
CMS disk 2: s1 CMS disk 2: s1
CMS disk 3: s1 CMS disk 3: s1
CMS disk 4: s1 CMS Disk 4: s1
Submirror d20
Device Names
CMS disk 1: c0t2d0s3
CMS disk 2:
c0t3d0s1
3000 system
Submiror d20
Device Names
swap, disk 1: c0t0d0s4 swap, disk 2 s4 CMS disk 5: s1 CMS disk 5: s1
Submirror d1 1
Device Name
boot disk 1:
c0t0d0s0
Submirror d15
Device Name
(r3v6aj.c and later)
swap, disk 1:
c0t0d0s4
Device/Metadevice Names for an
Submirror d12
Device Name
boot disk 2:
c1t4d0s0
Submirror d16
Device Name
(r3v6aj.c and later)
swap, disk 2
c1t4d0s4
Enterprise
Submirror d19
Device Names
CMS disk 1:
CMS disk 2:
CMS disk 3:
CMS disk 4:
3500 system
c0t0d0s3
c0t1d0s1
c0t2d0s1
c0t3d0s1
Submiror d20
Device Names
CMS disk 1:
CMS disk 3:
CMS Disk 4:
CMS disk 5:
c1t4d0s3
c1t5d0s1
c1t6d0s1
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
Do this step only if you have an
It is likely that your
Enterprise
Enterprise
3500 system.
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
2
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 betwee n the two newly installed GBICs.
The illustration below shows where the GBICs are installed. For
more detailed informat ion, see
System (connectivity diagram)
CentreVu CMS Sun Enterprise 3500
(585-215-877), which was packed
with your system.
Installing Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring 15
3. Install the new disk drives in the upper drive bay. The illustration
below shows where to install the new drives.
Installing Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring 16
4. From the ok prompt, do a reconfigure boot by enteri ng the fo llowing
command:
______________________________________________________
ok boot -r
______________________________________________________
Step 3: Install the
mirror disks on an
Enterprise
3000
system
5. Log in as
6. Enter the following command:
______________________________________________________
#
______________________________________________________
The system should respond with a line similar to the following:
______________________________________________________
lrwxrwxrwx 1 roor roor 50 Nov 16 08:58
/dev/dsk/c2t6d0s0 -> ../../devices/sbus@3,0
/SUNW,fas@3,8800000/sd@6,0:a
______________________________________________________
Notice that c2t6d0s0 is pointing to sd@6,0:a, indicating that the CD-
ROM drive is now on controller 2.
Do this step only if you have an
Install the new disk drives, which will f orm the mirror , into the empty slots
reserved in step 1. Follow the procedure in the “Add a Disk Drive”
subsection in the Lucent Technologies hardware installation or hardware
2
maintenance manual for your version of CMS. DO NOT PARTITION THE
DISKS JUST YET; that happens next.
root.
ls -l /dev/dsk/c2t6d0s0
Enterprise
3000 system.
Step 4: Partition the mirror disks
Partition the newly installed disks using the
have an
2
using “c1,” as c1t4d0 or c1t5d0.
The procedure is as follows:
1. Enter: #
2. Enter the menu number of the new disk to be partitioned.
3. Enter:
Enterprise
A menu of disks displays. You are asked to select one.
format>
The
partition>
The
3500, make certain that the new drives are named
format
prompt displays.
format> partition
prompt displays.
format
command. If you
Installing Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring 17
4. Enter:
partition> print
The partition table displays and the
Compare the display to the
Partitioning
you need to re-partition the disk. You probably will need to repartition.
5. Enter the number of the partition to be reconfigured.
The system begins a series of prompts for partitioning information.
Answer according to the CMS version and disk type you are
partitioning (see the
Partitioning
Repeat this task for each partition on the disk.
Partitioning (Note: Never change the default size of the
CMS R3V8
4.2-GB Disk
Disk
Type
Part Tag Flag
Size
(cyl.)
Starting
Cylinder
partition>
table below to see whether
table below).
overlap
CMS R3V8
9.1-GB Disk SCSI
(E3000) and FC-AL
(E 3500)
Size
(cyl.)
prompt returns.
slice!)
Starting
Cylinder
Boot 0
Nonboot 0 unassigned wm 2 0 2 0
boot disk 1:
boot disk 2:
1 unassigned wm 7 1023 7 616
2overlap
3 unassigned wm 1879 1030 3716 623
4 swap wm 971 2109 585 4339
5-7 unassigned wm 0 0 0 0
1 unassigned wm 3878 2 4922 2
2overlap
3-7 unassigned wm 0 0 0 0
/ or root
unassigned
or
backup wm 3880 0 4924 0
or
backup wm 3880 0 4924 0
6. Enter:
The partition table displays and the
Compare the display to the
wm 1023 0 616 0
partition> print
partition>
Partitioning
table to make certain you
prompt returns.
have repartitioned the disk properly. If not, repeat step 5.
7. Enter:
partition> label
The system responds
Ready to label disk, continue?
Installing Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring 18
Step 5: Create the state database replicas
8. Enter:
The
9. Enter:
The
10. To select the next disk to be partitioned, enter:
y
partition>
partition> q
format>
prompt returns.
prompt returns.
format> disk
and return to item 2.
If you have finished partitioni ng all the new dis ks, ent er:
and continue with the next step.
1. Alter your path by entering the foll owing commands:
# export PATH=$PATH:/usr/opt/SUNWmd/sbin:/olds
2
2. Create two state database replicas on slice 1 of boot disk 2:
# metadb -a -c3 -f /dev/rdsk/
(where
<device>
is the target number of boot disk 2)
<device>
format> q
Step 6: Create the
md.tab
table entrie s2
3. Verify that the replicas were created by entering the following
command:
metadb -i
#
The system lists the stat e database replicas currently on the system.
The following sample output shows two replicas on c0t2:
flags first blk block count
a u 16 1034 /dev/dsk/c0t2d0s1
a pc luo 16 1034 /dev/dsk/c0t2d0s1
Make sure the list includes the two replicas you just created.
1. Make copies of essential system files by entering these commands:
# cp /etc/opt/SUNWmd/md.tab /etc/opt/SUNWmd/md.tab.orig
# cp /etc/vfstab /etc/vfstab.orig
# cp /etc/system /etc/system.orig
2. Edit
/etc/opt/SUNWmd/md.tab
/cms
metadevices. If your system is running CMS load r3v6aj.c or
later, you must also create a section for the
and insert entries for the
swap
metadevice.
root
and
Installing Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring 19
The root metadevice definiti ons go into the #metaroot section,
which you must create for the occasion; d20 goes into the #/cms
section, which already exists in the file. The swap metadevice
definitions go into the #swap section which, li ke #metaroot, must
be created for the occasion.
The lines you add must be in the following general format:
x> <y>
d<
d
<x>
is the metadevice name.
<y>
denotes the total number of disks named in the line.
1
<device>
indicates one disk with the device name
should have recorded the device names on page 13
The pattern 1 (space)
1
<device>
<device>
<device>.
.
repeats until all disks in the
You
metadevice have been named. The d12 entry must specify one disk;
the d20 entry must specify the same number of disks as the existing
d19 entry. If your system has two disks in slots 0 and 1 and you are
adding a two-disk mirror in slots 2 and 3, for example, you would
add the
-------- /etc/opt/SUNWmd/md.tab - EXAMPLE ONLY --------------
#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
.
.
.
md.tab
lines shown in boldface in the following sample:
#metaswap (for load r3v6aj.c or later)
d15 1 1 c0t0d0s4
d16 1 1 c0t2d0s4
d17 -m d15
-------------------------------------------------------------
3. Save the
/etc/opt/SUNWmd/md.tab
file and quit the editor.
Installing Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring 20
Step 7: Set up the
mirrors for the
root
file system 2
Set up the mirrors for the
1. Activate metadevice d11:
# metainit -f d11
d11: Concat/stripe is set up
#
2. Activate metadevice d13:
# metainit -f d13
d13: Concat/stripe is set up
#
3. Activate metadevice d12:
# metainit -f d12
d12: Concat/stripe is set up
#
4. Attach d12 to d13:
# metattach d13 d12
d13: submirror d12 is attached
#
root
file system with the following steps:
5. Verify that root is set up and resynching:
# metastat d13
d13: Mirror
Submirror 0: d11
State: Okay
Submirror 1: d12
State: Resyncing
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 2209680 blocks
.
.
.
Check the
Okay
indicate any other status, somethin g has gone wrong with the setup:
discontinue the upgrade and telephone the Lucent National
Customer Care Center (1.800.242.2121) or contact your Lucent
representative or distributor.
State:
Resyncing
or
lines in the output list. They should read either
. If they do, then everything is fine. If they
Installing Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring 21
6. Set up d13 as the root mirror:
# metaroot d13
#
7. Reboot the system and log in as the root user:
# /usr/sbin/shutdown -i6 -g0 -y
...
<hostname>
Password:
login: root
<password>
#
Installing Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring 22
Step 8: Set up the mirrors for the swap space
Set up the mirrors for the swap space with the following steps:
1. Activate metadevice d15:
2
# metainit -f d15
d15: Concat/stripe is set up
#
2. Activate metadevice d17:
# metainit d17
d17: Concat/stripe is set up
#
3. Activate metadevice d16:
# metainit d16
d16: Concat/stripe is set up
#
4. Attach d16 to d17:
# metattach d17 d16
d17: submirror d16 is attached
#
5. Ver ify that swap is set up and resynching:
# metastat d17
d17: Mirror
Submirror 0: d15
State: Okay
Submirror 1: d16
State: Resyncing
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 2209680 blocks
.
.
.
Check the
Okay
State:
Resyncing
or
lines in the output list. They should read either
. If they do, then everything is fine. If they
indicate any other status, somethin g has gone wrong with the setup:
discontinue the upgrade and telephone the Lucent National
Customer Care Center (1.800.242.2121) or contact your Lucent
representative or distributor.
Installing Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring 23
6. Edit
/etc/vfstab.
The relevant portion of the file looks like this:
----------------- /etc/vfstab ----------------
...
/dev/dsk/c0t0d0s4 - swap - no /dev/dsk/c0t2d0s4 - swap - no -
--------------------------------------------------
Do the following steps to modify the file:
a. Copy the
c0t0d0s4
entry and insert the copy on the succeeding
line.
b. Comment out the original entry by inserting a pound sign at the
beginning of the line.
c. Alter the copy by:
1. replacing
2. adding
md/
c0t0d0s4
after the
with
dev/
d17
d. Immediately after the line just added should be a li ne naming
the secondary boot disk. Comment out that line by inserting a
pound sign at the beginning of the line.
When you have finished
a
through
d,
the relevant lines of the
file might look something like this:
----------------- /etc/vfstab ---------------...
#/dev/dsk/c0t0d0s4 - swap - no /dev/md/dsk/d17 - swap - no #/dev/dsk/c0t2d0s4 - swap - no -
----------------------------------------------
e. Save the file and quit the editor.
7. Set up the swap space by entering the following command:
# swap -a /dev/md/dsk/d17
#
Installing Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
How to upgrade an Enterprise platform to disk mirroring 24
Step 9: Set up the
/cms
mirror 2
1. Edit
/etc/vfstab.
Copy the d19 entry to the succeeding line. Then
comment out the original and change “d19” to “d21”. For example:
---------------- /etc/vfstab - EXAMPLE ONLY ----------------...
#/dev/md/dsk/d19 /dev/md/rdsk/d19 /cms ufs 2 yes -
/dev/md/dsk/d21 /dev/md/rdsk/d21 /cms ufs 2 yes
-------------------------------------------------------------
2. Save the
/etc/vfstab
file and exit the editor.
3. Alter your path:
# export PATH=$PATH:/usr/opt/SUNWmd/sbin:/olds
4. Activate the new metadevice (d20):
# metainit d20
d20: Concat/stripe is set up
#
5. Verify that d20 is active:
# metastat d20
d20: Concat/Stripe
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
#
6. Initialize the newly created mirror (d21):
# metainit -f d21
d21: Concat/stripe is set up
#
7. Attach the new metadevice (d20) to the newly created mirror (d21):
# metattach d21 d20
d21: submirror d20 is attached
#
8. Reboot the system by entering the following command:
# /usr/sbin/shutdown -y -i6 -g0
Loading...