Lucent Technologies 585-210-940 manual Device Names, Submirror d15 Submirror d16

Page 19

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

 

 

Submirror d20

 

Device Names

 

 

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

Submirror d12

 

 

 

Submirror d19

 

Submiror d20

 

 

 

 

Device Name

Device Name

 

 

 

Device Names

 

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

Submirror d16

 

 

 

CMS disk 3:

s1

 

CMS disk 3:

 

s1

 

 

 

Device Name

Device Name

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

(r3v6aj.c and later)

(r3v6aj.c and later)

 

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

Submirror d12

Submirror d19

Submiror d20

 

 

Device Name

Device Name

Device Names

Device Names

 

 

 

 

 

 

 

 

 

 

 

 

boot disk 1:

c0t0d0s0

boot disk 2:

c1t4d0s0

CMS disk 1:

c0t0d0s3

CMS disk 1:

c1t4d0s3

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

CMS disk 2:

c0t1d0s1

CMS disk 3:

c1t5d0s1

 

 

Submirror d15

Submirror d16

 

 

Device Name

Device Name

 

 

 

 

 

 

 

 

 

 

 

 

(r3v6aj.c and later)

(r3v6aj.c and later)

CMS disk 3:

c0t2d0s1

CMS Disk 4:

c1t6d0s1

 

 

 

 

 

 

 

 

 

 

 

 

swap, disk 1:

c0t0d0s4

swap, disk 2

c1t4d0s4

CMS disk 4:

c0t3d0s1

CMS disk 5:

c1t7d0s1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Image 19
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 D17 D16 D11D13 D12 D15Submirror Disks Mirror layoutsMirror d13 Mirror d21 Mirror d17 Root filesystem Cms filesystemEnterprise 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 Enter format partition Ok boot -r# ls -l /dev/dsk/c2t6d0s0 Do this step only if you have an Enterprise 3000 systemStarting 3500Disk Part Flag# metadb Enter partition q# export PATH=$PATH/usr/opt/SUNWmd/sbin/olds # metadb -a -c3 -f /dev/rdsk/deviceDx y 1 device # metainit -f d12 D12 Concat/stripe is set up Set up the mirrors for the root file system# metainit -f d11 D11 Concat/stripe is set up # metainit -f d13 D13 Concat/stripe is set up# metaroot d13 Password password# /usr/sbin/shutdown -i6 -g0 -y # metainit d16 D16 Concat/stripe is set up Set up the mirrors for the swap space# metainit -f d15 D15 Concat/stripe is set up # metainit d17 D17 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 deviceSbus@3,0/SUNW,fas@3,8800000/sd@2,0 Ok nvalias bootdevice2 deviceOk boot bootdevice2 # /usr/sbin/shutdown -y -i0 -g0Install 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 scripts14550512 14171072 1420577614309888 14376992 14446400Disk 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 device# crontab -l Canceling chkDisksMaintaining the chkDisks crontab Activating chkDisks Verifying chkDisks# lp /etc/vfstab Doing a Cmsadm backup on a mirrored systemRun the backup Print the vfstab fileLabel 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 # metaclear d20 D20 Concat/Stripe is cleared # metainit d19 D19 Concat/Stripe is set up# metainit d21 mirror is set up # metadetach d21 d20 D21 submirror d20 is detached14585216 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 Click Continue Identify the systemContinue Confirm Information255.255.255.0 is Set the Name Service optionsRegion Installation InitialSet the date and time Geographic RegionSelect Languages Installation screen isServices? screen is Allocate ClientSelect 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 Dbase State Hot Spare C0t4d0s3 Okay Identify the submirrorsSize 14960160 blocks Stripe Device Dbase State Hot Spare C0t2d0s1 Okay Stripe DeviceMetadetach metamirror submirror Detach the submirrorsReplace the faulty disk drive Remove state database replicas boot disks onlyRecreate the state database replicas # metattach d21 d20 Reboot the system boot disks onlyYou may delay this step until a more convenient time # metainit d20# metadb -d -c4 -f /dev/dsk/c0t0d0s1 Setting up replicas Replacing replicasState Database Replicas # metadb -d -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 vstab file for an R3V8 CMS system with mirrored disks Examples of valid system filesValid vfstab files Valid vfstab file for a non mirrored R3V8 CMS systemValid 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 time# /olds/chkDisks Log filesFile Name Description # ls /olds/chkDisks# metareplace -e d13 c0t0d0s0 Error messagesError Messages Explanation Response Message Explanation ResponseMessage Explanation Device devicename cannot be setup or does Not existDisk diskname already setup, exiting Device devicename will not be usedMessage Response Metadetach systemname d21 resync Progress No disks found! Internal errorCommand not found Metadb hostname cxtyd0sz has a Metadevice database replicaMessage Error Messages Response /cms filesystem needs to be mounted DiskSuite Software must be installed To run this scriptFile filename could not be restored Disk is not recognized by cmsUnbalanced 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.