Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies CentreVu Call Management System Release 3 Version 8 Guide
Lucent Technologies CentreVu Call Management System Release 3 Version 8 Guide
Have a look at the manual Lucent Technologies CentreVu Call Management System Release 3 Version 8 Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
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. Tr a d e m a r k s 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: 1-800-457-1764 International Fax: 317-322-6699 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 defined1 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 defined1 “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. Metadevices1The 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 defined2 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 CMetadevice d1
Introduction to Disk Mirroring CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems Disk mirroring defined3 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 databases1The 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. Mirrors1A 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 defined4 Chunk 3 Chunk 4 Chunk 2 Chunk 1 Chunk 3 Chunk 4 Chunk 2 Chunk 1 Solstice DiskSuite Metadevice d19 Metadevice d20Metadevice d21 Chunk 3 Chunk 4 Chunk 2 Chunk 1