Lucent Technologies 585-210-940 manual Log files, File Name Description, # ls /olds/chkDisks

Page 93

Troubleshooting

CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems

Log files

87

 

 

Log files

A disk-mirrored system contains the following system log files:

File Name

Description

 

 

 

 

/var/adm/messages

Contains all console error messages, including

 

hardware messages. (For an example of how

 

to use this log to detect a bad disk drive, see

 

Replacing Faulty Disks” in Chapter 3.)

 

 

/olds/elog

Contains olds error messages. Most messages

 

are logged when setting up the system or when

 

making changes to the disk setup.

 

 

If a log seems to indicate a problem, it may take an experienced troubleshooter to determine the nature of the problem.

The logs are checked each night by the chkDisks crontab, which is able to determine whether any potential or actual drive problems have been logged. The results of the determination are logged to /olds/elog and mailed to the root user.

If chkDisks is not running each night, verify that it is available in the /olds directory by entering the following command:

#ls /olds/chkDisks

If the file is not found, load the CMS CD into the CD-ROM drive and enter the following commands:

#cp /cms/rdonly/olds_install/chkDisks /olds

#chmod +x /olds/chkDisks

To test chkDisks, simply execute it by entering the following command:

#/olds/chkDisks

Image 93
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 Disk mirroring defined MetadevicesBacked up just as often as unmirrored systems Concatenated State databases MirrorsSolstice DiskSuite How CMS implements disk mirroring D19D21 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 NamesSystem Do this step only if you have an Enterprise 3500 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 upPassword password # metaroot d13# /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 or rebuilding the /cms file system Repairing /cms# umount /cms Rebuilding /cms If you altered the vfstab file earlier , do the followingIf 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 cleared# newfs Dev/md/rdsk/d21 14585216 1465462414724032 14793440 Power off the system Restoring a mirrored system from a Cmsadm backupOk boot cdrom Task Action ResultSelect 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 Begin Installation Reboot/No Reboot Click RebootClick Continue Mount Remote File Complete the OS installation Reestablish the disk mirrors # /olds/olds -cleanup# PATH=$PATH/usr/opt/SUNWmd/sbin/olds # export Path # olds mirrored -mkfiles Success, creating md.tab.new# 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/d21Replacing a faulty disk Identify the 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/c0t0d0s1Partitioning disks with the format command Enter # formatFC-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 files Valid md.tab file for a 3 disk non mirrored R3V8 CMS systemValid md.tab file for a 4 disk mirrored R3V8 CMS system Excessively long resync Unmount /cms umount /cmsEnter mount /cms Remounts /cms If you receive a This command may hang the system Enter setenv auto-boot? falseSystem fails to recognize all disk drives Ok setenv auto-boot? true Ok boot -r Console login root PasswordToshiba XMS5701TASUN12XCD099704/09/97 C0t0d0s0 Okay Fixing needs maintenance messagesBoot problems Primary boot device is not availableOk 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 mountedEnter reset-all Unbalanced configurations not supportedTouch /cms/db/unixstart cannot create Configuration, configure manually You must be root in order to run this commandUsage 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.