Lucent Technologies 585-210-940 Mirror layouts, Mirror d13 Mirror d21 Mirror d17, Submirror Disks

Page 13

Introduction to Disk Mirroring

CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems

How CMS implements disk mirroring

7

 

 

Mirror layouts

Mirror 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 On a Sun Enterprise 3000 platform with factory-installed mirroring, the

Enterprise 3000

mirror layout is the simple odd/even arrangement shown in the table

computer

 

below. A system upgraded to mirroring in the field probably has a

 

 

 

 

 

different mirror layout.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

mirror d13

 

mirror d21

 

mirror d17

 

 

 

 

 

 

 

(swap partition)

 

 

 

 

 

(/ (root) filesystem)

 

(/cms filesystem)

 

 

 

 

 

 

 

 

(CMS r3v8)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

No.

submirror

submirror

 

submirror

submirror

 

submirror

submirror

 

 

 

Disks

d11

d12

 

d19

d20

 

d15

d16

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2

 

c0t0d0s0

c0t1d0s0

 

c0t0d0s3

c0t1d0s3

 

c0t0d0s4

c0t1d0s4

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

4

 

c0t0d0s0

c0t1d0s0

 

c0t0d0s3

c0t1d0s3

 

c0t0d0s4

c0t1d0s4

 

 

 

 

 

 

c0t2d0s1

c0t3d0s1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

6

 

 

 

 

c0t0d0s3

c0t1d0s3

 

 

 

 

 

 

 

 

c0t0d0s0

c0t1d0s0

 

c0t2d0s1

c0t3d0s1

 

c0t0d0s4

c0t1d0s4

 

 

 

 

 

 

 

 

c0t10d0s1

c0t11d0s1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

8

 

 

 

 

c0t0d0s3

c0t1d0s3

 

 

 

 

 

 

 

 

c0t0d0s0

c0t1d0s0

 

c0t2d0s1

c0t3d0s1

 

c0t0d0s4

c0t1d0s4

 

 

 

 

 

 

c0t10d0s1

c0t11d0s1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

c0t12d0s1

c0t13d0s1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

10

 

 

 

 

c0t0d0s3

c0t1d0s3

 

 

 

 

 

 

 

 

 

 

 

c0t2d0s1

c0t3d0s1

 

 

 

 

 

 

 

 

c0t0d0s0

c0t1d0s0

 

c0t10d0s1

c0t11d0s1

 

c0t0d0s4

c0t1d0s4

 

 

 

 

 

 

 

 

c0t12d0s1

c0t13d0s1

 

 

 

 

 

 

 

 

 

 

 

c0t14d0s1

c0t15d0s1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Page 12 Page 14
Image 13
Page 12 Page 14
Contents CentreVu Call Management System Comments Table of Contents CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems Iii IndexCentreVu CMS Release 3 Version 8 Disk-Mirrored Systems Metadevices Disk mirroring definedBacked up just as often as unmirrored systems Concatenated State databases MirrorsSolstice DiskSuite D19 How CMS implements disk mirroringD21 D20 D13 D12 D11D15 D17 D16Mirror d13 Mirror d21 Mirror d17 Mirror layoutsRoot filesystem Cms filesystem Submirror DisksEnterprise Additional references Required softwareHow CMS implements disk mirroring Disk drive slots How to upgrade an Enterprise platform to disk mirroringIdentify mirror devices Increasing system capacitySubmirror d15 Submirror d16 Device NamesDo this step only if you have an Enterprise 3500 system System# ls -l /dev/dsk/c1t6d0s0 How to upgrade an Enterprise platform to disk mirroring # ls -l /dev/dsk/c2t6d0s0 Ok boot -rDo this step only if you have an Enterprise 3000 system Enter format partitionDisk Part 3500Flag Starting# export PATH=$PATH/usr/opt/SUNWmd/sbin/olds Enter partition q# metadb -a -c3 -f /dev/rdsk/device # metadbDx y 1 device # metainit -f d11 D11 Concat/stripe is set up Set up the mirrors for the root file system# metainit -f d13 D13 Concat/stripe is set up # metainit -f d12 D12 Concat/stripe is set up# metaroot d13 Password password# /usr/sbin/shutdown -i6 -g0 -y # metainit -f d15 D15 Concat/stripe is set up Set up the mirrors for the swap space# metainit d17 D17 Concat/stripe is set up # metainit d16 D16 Concat/stripe is set up# swap -a /dev/md/dsk/d17 Set up the /cms mirror Disk Space Verification Verify disk space# ls -l /dev/rdsk/newbootdev Create an alternate boot deviceOk boot bootdevice2 Ok nvalias bootdevice2 device# /usr/sbin/shutdown -y -i0 -g0 Sbus@3,0/SUNW,fas@3,8800000/sd@2,0Install the hardware Factory installation procedures for disk mirroring3500 Disk Part Install the application software# stty erase Ctrl-H # ksh -o Check the disk.type file# olds -mirrored -mkfiles Ok boot -r Hostname console login root Password password Run the setup scripts14309888 14171072 1420577614376992 14446400 14550512Disk Space Verification Install the CMS software Enter the following command ok devalias # chmod +x /olds/chkDisks Factory installation procedures for disk mirroring Ok setenv boot-device disk # eeprom boot-device=disk Using the alternate boot deviceMaintaining the chkDisks crontab Canceling chkDisksActivating chkDisks Verifying chkDisks # crontab -lRun the backup Doing a Cmsadm backup on a mirrored systemPrint the vfstab file # lp /etc/vfstabLabel and store the tapes # cpio -icmudv -C 10240 -I device Restoring from a Cmsadm BackupRestoring from a Cmsadm Backup Repairing /cms Repairing or rebuilding the /cms file system# umount /cms If you altered the vfstab file earlier , do the following Rebuilding /cmsIf you did not alter the vfstab file, do the following # metainit d21 mirror is set up # metainit d19 D19 Concat/Stripe is set up# metadetach d21 d20 D21 submirror d20 is detached # metaclear d20 D20 Concat/Stripe is cleared14585216 14654624 # newfs Dev/md/rdsk/d2114724032 14793440 Power off the system Restoring a mirrored system from a Cmsadm backupTask Action Result Ok boot cdromSelect Language Continue Identify the systemConfirm Information Click Continue255.255.255.0 is Set the Name Service optionsSet the date and time Installation InitialGeographic Region RegionServices? screen is Installation screen isAllocate Client Select LanguagesSelect the hard disks Slice Name GB DiskClick Reboot Click Begin Installation Reboot/No RebootClick Continue Mount Remote File Complete the OS installation Reestablish the disk mirrors # /olds/olds -cleanup# olds mirrored -mkfiles Success, creating md.tab.new # PATH=$PATH/usr/opt/SUNWmd/sbin/olds # export Path# olds -mirrored -checkdisk Success, checking md.tab.new Hostname login root Password root password Restoring specific files from a Cmsadm backup # /usr/opt/SUNWmd/sbin/metastat Adding new disks to a standard mirrored system# olds -mirrored -mkfiles c0t10d0 c0t11d0 # olds -mirrored -setup newdisk1 newdisk2 # df -k /cms Adding new disks to a nonstandard mirrored system# metattach d19 c0t10d0s1 # metattach d20 c0t11d0s1 # metattach d19 newdisk1 # metattach d20 newdisk2# metastat # growfs -M /cms /dev/md/rdsk/d21Identify the faulty disk Replacing a faulty disk# ls -l /dev/dsk/c Lrwxrwxrwx 1 root Root Size 14960160 blocks Stripe Device Identify the submirrorsDbase State Hot Spare C0t2d0s1 Okay Stripe Device Dbase State Hot Spare C0t4d0s3 OkayMetadetach metamirror submirror Detach the submirrorsReplace the faulty disk drive Remove state database replicas boot disks onlyRecreate the state database replicas You may delay this step until a more convenient time Reboot the system boot disks only# metainit d20 # metattach d21 d20State Database Replicas Setting up replicas Replacing replicas# metadb -d -f /dev/dsk/c0t0d0s1 # metadb -d -c4 -f /dev/dsk/c0t0d0s1Enter # format Partitioning disks with the format commandFC-AL E Enter partition q Root Metadevice Device Names How to tell whether your mirrored system is standardValid vfstab files Examples of valid system filesValid vfstab file for a non mirrored R3V8 CMS system Valid vstab file for an R3V8 CMS system with mirrored disksValid md.tab file for a 3 disk non mirrored R3V8 CMS system Valid md.tab filesValid md.tab file for a 4 disk mirrored R3V8 CMS system Unmount /cms umount /cms Excessively long resyncEnter mount /cms Remounts /cms Enter setenv auto-boot? false If you receive a This command may hang the systemSystem fails to recognize all disk drives Ok boot -r Console login root Password Ok setenv auto-boot? trueToshiba XMS5701TASUN12XCD099704/09/97 C0t0d0s0 Okay Fixing needs maintenance messagesPrimary boot device is not available Boot problemsOk setenv boot-device bootdevice2 Touch /etc/notrouter Excessive reboot timeFile Name Description Log files# ls /olds/chkDisks # /olds/chkDisksError Messages Explanation Response Error messagesMessage Explanation Response # metareplace -e d13 c0t0d0s0Disk diskname already setup, exiting Device devicename cannot be setup or does Not existDevice devicename will not be used Message ExplanationMessage Response Command not found No disks found! Internal errorMetadb hostname cxtyd0sz has a Metadevice database replica Metadetach systemname d21 resync ProgressMessage Error Messages Response File filename could not be restored DiskSuite Software must be installed To run this scriptDisk is not recognized by cms /cms filesystem needs to be mountedUnbalanced configurations not supported Enter reset-allTouch /cms/db/unixstart cannot create You must be root in order to run this command Configuration, configure manuallyUsage olds -mirrored -checkdisks Index SymbolsNeeds maintenance messages How Are We Doing?

585-210-940 specifications

Lucent Technologies, founded in 1996 as a spin-off from AT&T, emerged as a leader in telecommunications, contributing significantly to the advancement of network technologies. The model 585-210-940, an innovative product from Lucent, exemplifies their commitment to providing cutting-edge solutions for communication networks.

The 585-210-940 is primarily recognized as a digital cross-connect system (DCS) designed to manage and route digital voice and data traffic efficiently. This system plays a crucial role in facilitating seamless communication by allowing service providers to interconnect different digital circuits and manage bandwidth effectively. One of the main features of the 585-210-940 is its ability to support multiple protocols, which enhances interoperability among diverse communication platforms.

A standout characteristic of this system is its scalability. The 585-210-940 can adapt to growing network demands, making it suitable for both small enterprises and large service providers. This flexibility ensures that users can expand their systems without a complete overhaul, thereby reducing costs and downtime during upgrades. Additionally, the system provides fault tolerance, ensuring high availability and reliability, which are essential metrics for any critical telecommunications infrastructure.

Lucent Technologies also integrated advanced monitoring and management capabilities into the 585-210-940. This feature allows operators to track performance metrics and identify potential issues in real time. The system includes a user-friendly interface that simplifies network management tasks, making it accessible to operators with varying levels of technical expertise.

Moreover, the 585-210-940 is designed to support high capacity, handling numerous channels simultaneously without compromising performance. This capability is particularly beneficial in environments with heavy data traffic, such as urban centers or large corporate hubs.

In conclusion, Lucent Technologies' 585-210-940 serves as a robust solution for telecommunications, encapsulating many of the core innovations of the late 20th century. With its support for multiple protocols, scalability, fault tolerance, and advanced management capabilities, it stands out as an essential component for any modern communication network, reflecting Lucent's legacy in the industry.
Top Page Image Contents