Lucent Technologies 585-210-940 manual Enterprise

Page 14

Introduction to Disk Mirroring

CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems

How CMS implements disk mirroring

8

 

 

Mirror layout on a Sun On a Sun Enterprise 3500 platform, the mirror layout must always be

Enterprise 3500

based upon the bays in which the disks are installed. Submirrors 11, 15,

computer

 

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.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

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

c1t4d0s0

 

c0t0d0s3

c1t4d0s3

 

c0t0d0s4

c1t4d0s4

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

4

 

c0t0d0s0

c1t4d0s0

 

c0t0d0s3

c1t4d0s3

 

c0t0d0s4

c1t4d0s4

 

 

 

 

 

c0t1d0s1

c1t5d0s1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

c0t0d0s3

c1t4d0s3

 

 

 

 

 

 

6

 

c0t0d0s0

c1t4d0s0

 

c0t1d0s1

c1t5d0s1

 

c0t0d0s4

c1t4d0s4

 

 

 

 

 

 

 

 

c0t2d0s1

c1t6d0s1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

c0t0d0s3

c1t4d0s3

 

 

 

 

 

 

8

 

c0t0d0s0

c1t4d0s0

 

c0t1d0s1

c1t5d0s1

 

c0t0d0s4

c1t4d0s4

 

 

 

 

 

c0t2d0s1

c1t6d0s1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

c0t3d0s1

c1t7d0s1

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Required hardware 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 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.

Page 13 Page 15
Image 14
Page 13 Page 15
Contents CentreVu Call Management System Comments Table of Contents CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems Index CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems IiiCentreVu CMS Release 3 Version 8 Disk-Mirrored Systems Backed up just as often as unmirrored systems Disk mirroring definedMetadevices Concatenated Mirrors State databasesSolstice DiskSuite D21 D20 How CMS implements disk mirroringD19 D15 D11D13 D12 D17 D16Root filesystem Cms filesystem Mirror layoutsMirror d13 Mirror d21 Mirror d17 Submirror DisksEnterprise Required software Additional referencesHow CMS implements disk mirroring How to upgrade an Enterprise platform to disk mirroring Disk drive slotsIncreasing system capacity Identify mirror devicesDevice Names Submirror d15 Submirror d16# ls -l /dev/dsk/c1t6d0s0 SystemDo this step only if you have an Enterprise 3500 system How to upgrade an Enterprise platform to disk mirroring Do this step only if you have an Enterprise 3000 system Ok boot -r# ls -l /dev/dsk/c2t6d0s0 Enter format partitionFlag 3500Disk Part Starting# metadb -a -c3 -f /dev/rdsk/device Enter partition q# export PATH=$PATH/usr/opt/SUNWmd/sbin/olds # metadbDx y 1 device # metainit -f d13 D13 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 d12 D12 Concat/stripe is set up# /usr/sbin/shutdown -i6 -g0 -y Password password# metaroot d13 # metainit d17 D17 Concat/stripe is set up Set up the mirrors for the swap space# metainit -f d15 D15 Concat/stripe is set up # metainit d16 D16 Concat/stripe is set up# swap -a /dev/md/dsk/d17 Set up the /cms mirror Verify disk space Disk Space VerificationCreate an alternate boot device # ls -l /dev/rdsk/newbootdev# /usr/sbin/shutdown -y -i0 -g0 Ok nvalias bootdevice2 deviceOk boot bootdevice2 Sbus@3,0/SUNW,fas@3,8800000/sd@2,0Factory installation procedures for disk mirroring Install the hardwareInstall the application software 3500 Disk PartCheck the disk.type file # stty erase Ctrl-H # ksh -o# olds -mirrored -mkfiles Run the setup scripts Ok boot -r Hostname console login root Password password14376992 14446400 14171072 1420577614309888 14550512Disk Space Verification Install the CMS software Enter the following command ok devalias # chmod +x /olds/chkDisks Factory installation procedures for disk mirroring Using the alternate boot device Ok setenv boot-device disk # eeprom boot-device=diskActivating chkDisks Verifying chkDisks Canceling chkDisksMaintaining the chkDisks crontab # crontab -lPrint the vfstab file Doing a Cmsadm backup on a mirrored systemRun the backup # lp /etc/vfstabLabel and store the tapes Restoring from a Cmsadm Backup # cpio -icmudv -C 10240 -I deviceRestoring from a Cmsadm Backup # umount /cms Repairing or rebuilding the /cms file systemRepairing /cms If you did not alter the vfstab file, do the following Rebuilding /cmsIf you altered the vfstab file earlier , do the following # metadetach d21 d20 D21 submirror d20 is detached # metainit d19 D19 Concat/Stripe is set up# metainit d21 mirror is set up # metaclear d20 D20 Concat/Stripe is cleared14724032 14793440 # newfs Dev/md/rdsk/d2114585216 14654624 Restoring a mirrored system from a Cmsadm backup Power off the systemSelect Language Ok boot cdromTask Action Result Confirm Information Identify the systemContinue Click ContinueSet the Name Service options 255.255.255.0 isGeographic Region Installation InitialSet the date and time RegionAllocate Client Installation screen isServices? screen is Select LanguagesSelect the hard disks GB Disk Slice NameClick Continue Mount Remote File Click Begin Installation Reboot/No RebootClick Reboot Complete the OS installation # /olds/olds -cleanup Reestablish the disk mirrors# olds -mirrored -checkdisk Success, checking md.tab.new # PATH=$PATH/usr/opt/SUNWmd/sbin/olds # export Path# olds mirrored -mkfiles Success, creating md.tab.new Hostname login root Password root password Restoring specific files from a Cmsadm backup Adding new disks to a standard mirrored system # /usr/opt/SUNWmd/sbin/metastat# olds -mirrored -mkfiles c0t10d0 c0t11d0 # olds -mirrored -setup newdisk1 newdisk2 Adding new disks to a nonstandard mirrored system # df -k /cms# metattach d19 newdisk1 # metattach d20 newdisk2 # metattach d19 c0t10d0s1 # metattach d20 c0t11d0s1# growfs -M /cms /dev/md/rdsk/d21 # metastat# ls -l /dev/dsk/c Lrwxrwxrwx 1 root Root Replacing a faulty diskIdentify the faulty disk Dbase State Hot Spare C0t2d0s1 Okay Stripe Device Identify the submirrorsSize 14960160 blocks Stripe Device Dbase State Hot Spare C0t4d0s3 OkayDetach the submirrors Metadetach metamirror submirrorRemove state database replicas boot disks only Replace the faulty disk driveRecreate the state database replicas # metainit d20 Reboot the system boot disks onlyYou may delay this step until a more convenient time # metattach d21 d20# metadb -d -f /dev/dsk/c0t0d0s1 Setting up replicas Replacing replicasState Database Replicas # metadb -d -c4 -f /dev/dsk/c0t0d0s1FC-AL E Partitioning disks with the format commandEnter # format Enter partition q How to tell whether your mirrored system is standard Root Metadevice Device NamesValid vfstab file for a non mirrored R3V8 CMS system Examples of valid system filesValid vfstab files Valid vstab file for an R3V8 CMS system with mirrored disksValid md.tab file for a 4 disk mirrored R3V8 CMS system Valid md.tab filesValid md.tab file for a 3 disk non mirrored R3V8 CMS system Enter mount /cms Remounts /cms Excessively long resyncUnmount /cms umount /cms System fails to recognize all disk drives If you receive a This command may hang the systemEnter setenv auto-boot? false Toshiba XMS5701TASUN12XCD099704/09/97 Ok setenv auto-boot? trueOk boot -r Console login root Password Fixing needs maintenance messages C0t0d0s0 OkayOk setenv boot-device bootdevice2 Boot problemsPrimary boot device is not available Excessive reboot time Touch /etc/notrouter# ls /olds/chkDisks Log filesFile Name Description # /olds/chkDisksMessage Explanation Response Error messagesError Messages Explanation Response # metareplace -e d13 c0t0d0s0Device devicename will not be used Device devicename cannot be setup or does Not existDisk diskname already setup, exiting Message ExplanationMessage Response Metadb hostname cxtyd0sz has a Metadevice database replica No disks found! Internal errorCommand not found Metadetach systemname d21 resync ProgressMessage Error Messages Response Disk is not recognized by cms DiskSuite Software must be installed To run this scriptFile filename could not be restored /cms filesystem needs to be mountedTouch /cms/db/unixstart cannot create Enter reset-allUnbalanced configurations not supported Usage olds -mirrored -checkdisks Configuration, configure manuallyYou must be root in order to run this command Symbols IndexNeeds 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