Lucent Technologies 585-210-940 manual Rebuilding /cms

Page 52

Maintaining Mirrored Systems

CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems

Repairing or rebuilding the /cms file system

46

 

 

Rebuilding /cms

The system prompt should return without error, as shown above. (Of course, file and block counts in the last line will vary.) In that case, continue with the next step.

If you get an error message, however, repeat the fsck command. If the command still returns errors after 10 repetitions, stop this procedure and skip ahead to “Rebuilding /cms,” below.

Continue with step 6 only if you entered the fsck command and it returned the system prompt without error messages.

5.This step remounts /cms and reallocates the swap file. How that is done depends upon whether you altered the vfstab file earlier in this procedure.

If you altered the vfstab file earlier (step 4), do the following:

a.Load the /etc/vfstab file into your editor.

b.Find the #/cms line. Uncomment the line. (To uncomment a line, delete the initial pound sign.)

c.Save the file and exit the editor.

d.Reboot by entering the following command:

# /usr/sbin/shutdown -i6 -g0 -y

If you did NOT alter the vfstab file, do the following:

a.Remount /cms:

# mount /cms

6.Turn on CMS:

a.Enter a cmsadm or cmssvc command.

b.Select the run_cms option.

c.Select the Turn on CMS option.

The file system has now been repaired and should be operating normally.

If this procedure completed successfully, do NOT do the “Rebuild /cms” procedure.

Do this procedure only if you have tried the fsck command at least ten times and it is still returning errors.

If you are running a Sun Enterprise 3500 platform, do not begin this procedure until you have checked the /kernel/drv/st.conf file to make sure the 3500’s 8mm tape drive is properly defined. See “Restoring from a CMSADM Backup” on page 43 for details.

To complete this procedure, you need the latest CMSADM backup. Also, /cms should still be unmounted at this point. If anything has been done to alter that, repeat steps 2 through 4 of the “Repairing /cms” procedure.

Image 52
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 Metadevices Disk mirroring definedBacked up just as often as unmirrored systems Concatenated Mirrors State databasesSolstice DiskSuite D19 How CMS implements disk mirroringD21 D20 D11 D13 D12D15 D17 D16Mirror layouts Mirror d13 Mirror d21 Mirror d17Root filesystem Cms filesystem 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 d16Do 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 Ok boot -r # ls -l /dev/dsk/c2t6d0s0Do this step only if you have an Enterprise 3000 system Enter format partition3500 Disk PartFlag StartingEnter partition q # export PATH=$PATH/usr/opt/SUNWmd/sbin/olds# metadb -a -c3 -f /dev/rdsk/device # metadbDx y 1 device 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 # metainit -f d12 D12 Concat/stripe is set up# metaroot d13 Password password# /usr/sbin/shutdown -i6 -g0 -y 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 # 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/newbootdevOk nvalias bootdevice2 device Ok boot bootdevice2# /usr/sbin/shutdown -y -i0 -g0 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 password14171072 14205776 1430988814376992 14446400 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=diskCanceling chkDisks Maintaining the chkDisks crontabActivating chkDisks Verifying chkDisks # crontab -lDoing a Cmsadm backup on a mirrored system Run the backupPrint the vfstab file # lp /etc/vfstabLabel and store the tapes Restoring from a Cmsadm Backup # cpio -icmudv -C 10240 -I deviceRestoring 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 d19 D19 Concat/Stripe is set up # metainit d21 mirror 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 Restoring a mirrored system from a Cmsadm backup Power off the systemTask Action Result Ok boot cdromSelect Language Identify the system ContinueConfirm Information Click ContinueSet the Name Service options 255.255.255.0 isInstallation Initial Set the date and timeGeographic Region RegionInstallation screen is Services? screen isAllocate Client Select LanguagesSelect the hard disks GB Disk Slice NameClick Reboot Click Begin Installation Reboot/No RebootClick Continue Mount Remote File Complete the OS installation # /olds/olds -cleanup Reestablish the disk mirrors# 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 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 # metastatIdentify the faulty disk Replacing a faulty disk# ls -l /dev/dsk/c Lrwxrwxrwx 1 root Root Identify the submirrors Size 14960160 blocks Stripe DeviceDbase State Hot Spare C0t2d0s1 Okay 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 Reboot the system boot disks only You may delay this step until a more convenient time# metainit d20 # metattach d21 d20Setting up replicas Replacing replicas State Database 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 How to tell whether your mirrored system is standard Root Metadevice Device NamesExamples of valid system files Valid vfstab 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 Fixing needs maintenance messages C0t0d0s0 OkayPrimary boot device is not available Boot problemsOk setenv boot-device bootdevice2 Excessive reboot time Touch /etc/notrouterLog files File Name Description# ls /olds/chkDisks # /olds/chkDisksError messages Error Messages Explanation ResponseMessage Explanation Response # metareplace -e d13 c0t0d0s0Device devicename cannot be setup or does Not exist Disk diskname already setup, exitingDevice devicename will not be used Message ExplanationMessage Response No disks found! Internal error Command not foundMetadb hostname cxtyd0sz has a Metadevice database replica Metadetach systemname d21 resync ProgressMessage Error Messages Response DiskSuite Software must be installed To run this script File filename could not be restoredDisk 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 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.