Lucent Technologies CentreVu Call Management System Release 3 Version 8 Guide

							  Troubleshooting  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Boot problems85
Boot problems4
Generally speaking, most boot problems are the result of one of two 
problems: either you are trying to boot from the wrong device or the 
primary boot device is not available. This section suggests remedies for 
those situations.
Trying to boot from 
the wrong device
4
If you are trying to boot from the wrong device, you must change the boot 
device. Here is a quick way to do that:
1. Reboot:# /usr/sbin/shutdown -y -g0 -i0
2. From the ok
 prompt enter:ok> printenv boot-device
The system responds:boot-device

where  is either the word disk, 
indicating the primary 
boot device, or the word bootdevice2, 
indicating the alternate 
boot device. (This may be followed by additional device names.) 
To change the boot device, enter the following command:
You should have set up 
bootdevice2 as the alternate boot device 
when you installed disk mirroring.
Primary boot 
device is not 
available
4
If the primary boot device is not available, you must change to the 
secondary boot device. 
Changing to the secondary boot device is a matter of entering, from the 
ok
 prompt, the following command:
ok> setenv boot-device bootdevice2
You should have set up 
bootdevice2 as the alternate boot device when 
you installed mirroring. ok setenv boot-device bootdevice2
- or -
ok setenv boot-device disk 
						

							  Troubleshooting  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Boot problems86
Excessive reboot 
time
4
Problem: The system takes a long time to come back up after a reboot 
and seems to stop at the 
configuring multicast point.
Possible workaround: The 
Enterprise 3000, by default, tries to configure 
itself as a router/gateway. To avoid that problem, execute the following 
command before rebooting:
touch /etc/notrouter
That command tells the startup scripts that this system should not be 
configured as a router. 
						

							  Troubleshooting  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Log files87
Log files4
A disk-mirrored system contains the following system log files:
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:
If the file is not found, load the CMS CD into the CD-ROM drive and enter 
the following commands:
To test chkDisks, simply execute it by entering the following command: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.
# ls /olds/chkDisks
# cp /cms/rdonly/olds_install/chkDisks /olds
# chmod +x /olds/chkDisks
# /olds/chkDisks 
						

							  Troubleshooting  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Error messages88
Error messages4
The table that follows lists and explains error messages you can receive 
related to 
Solstice DiskSuite and disk mirroring. The messages are 
presented in alphabetical order, ignoring special characters and 
replacement strings. (For example, you would find the message 
“
filename restored”
 in alphabetical order by the word restored.)
Error Messages
Message:All data on cms filesystems will be removed 
and filesystems will be unmirrored, are 
you sure?
Explanation:Standard warning message for olds -mirrored 
-cleanup
 command.
Response:Always use an olds -mirrored -cleanup
 with 
caution, keeping in mind that a backup will be needed to 
recover any CMS data in the 
/cms filesystem. Use the 
command only to set up your system from scratch.
Message:Attempt an operation on a submirror that 
has erred components.
Explanation:Component needs maintenance before the operation can 
be carried out.
Response:1. Execute a metastat
 command. 
2. Examine the output for the 
Invoke line and execute 
the command named in that line. For example:
# metareplace -e d13 c0t0d0s0
3. Reboot system.
Message:CDROM must not be present, remove CD
Explanation:In order for the command to execute, the CDROM drive 
must be empty.
Response:1. Enter the command:eject cdrom
2. Remove the CD from the drive tray.
3. Close the drive tray. 
						

							  Troubleshooting  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Error messages89
Message:component is attached
metattach: 
hostname: d21: growing of 
metadevice delayed
Explanation:Submirrors are out of sync.
Response:Enter the command:metasync d21
This command effectively resyncs submirrors. 
Message:device: 
devicenamecannot be setup or does 
not exist
Explanation:The device named is a CD-ROM drive or is not available 
and will not be used in the 
Solstice DiskSuite setup.
Response:Verify that the device should not be used. 
Message:device: 
devicenamewill not be used
Explanation:The device named is a CD-ROM drive or is not available 
and will not be used in the 
Solstice DiskSuite setup.
Response:If the device is c0t6d0, it is a CD-ROM drive and no 
further action is required. If the device is a disk, verify the 
sanity of the message: check device availability, for 
example, or use a format
 command to view partition 
sizes, etc. 
Message:disk 
diskname already setup, exiting...
Explanation:You are trying to attach a disk that is already attached or 
is part of the base configuration. No response is 
necessary.
Message:disk: 
diskname slice 1 is not partitioned 
correctly
Explanation:Disk is partitioned incorrectly, or the 
olds script was run 
without the 
-mirrored option.
Response:Try rerunning the command with the -mirrored option. If 
that doesn’t work, repartition the disk.
If 
diskname is the primary boot disk, you must reload 
Solaris, repartitioning the disk correctly in the process. If 
diskname is not the primary boot disk, you can repartition 
it with the 
Solaris format
 command. Error Messages (Continued) 
						

							  Troubleshooting  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Error messages90
Message:/etc/system has been updated since the 
last reboot. CMS cannot run without an up-
to-date /etc/system file.
Explanation:/etc/system can change when a particular Solaris patch is 
applied to the system or when state database replicas are 
removed and re-added during a boot disk replacement.
Response:Reboot the system.
Message:Failed activating new replicas, replicas 
already active, or a second disk does not 
exist
Explanation:The system does not have all the replicas it needs to be 
functional (it needs at least three), or the replicas you 
attempted to create already exist.
Response:Use metadb -i 
to verify that at least three replicas are 
active. If not, add replicas (see Chapter 3).
Message:Failed: disk c
xtyd0 or cx’ty’d0 already 
setup, exiting ...
Explanation:You are trying to set up a disk that is already a part of the 
configuration. You probably mistyped the name.
Response:Set up the disk with the appropriate device name.
Message:Illegal Request, cannot setup
Response:Check your hardware configuration and your usage of the 
olds
 command.
Message:in order to attach disk, /cms must already 
be mounted, exiting...
Response:Mount cms with this command:mount /cms
Message:ksh: 
command: not found
Explanation:Command does not exist or is not in the execution path. 
Response:Use the entire path—as 
pathname/command—or add it 
to the execution path with the following command:
# export PATH=$PATH:
pathname
The path of the metastat, metadb, metattach
, and 
metadetach 
commands 
is 
/usr/opt/SUNWmd/sbin; the 
path of the olds command is
 /olds
Error Messages (Continued) 
						

							  Troubleshooting  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Error messages91
Message:metadb: 
hostname: cxtyd0sz has a 
metadevice database replica
Explanation:The slice named in the message already has a replica.
Response:If you really need to add another replica, choose a 
different slice.
Message:metadetach: 
systemname: d21: resync in 
progress
Explanation:You cannot detach a metadevice while a resync is in 
progress.
Response:Try again later. To find out how far along the resync has 
progressed, enter a metastat
 command.
Message:must have at least 2 databases
Response:Add a state database replica and retry the command.
Message:No disks found! Internal error.
Response:Add the state database replicas and retry the command. 
If the message persists, telephone the National Customer 
Care Center (1-800-242-2121) or contact your Lucent 
distributor or customer representative.
Message:No more space on device
Explanation:Occurs during a restore cpio command:
cpio -icmudf -C10240 -I input-device -M 
Enter tape..  ../cms*.. 
The “/cms” entry has probably been mistyped.
Response:Remove the /cms directory and all files and try again.
Message:
command: not found
Explanation:Command does not exist or is not in the execution path. 
Response:Use the entire path—as pathname/command
—or add it 
to the execution path with the following command:
# export PATH=$PATH:
pathname
The path of the metastat, metadb, metattach
, and 
metadetach 
commands 
is 
/usr/opt/SUNWmd/sbin; the 
path of the olds command is
 /olds
Error Messages (Continued) 
						

							  Troubleshooting  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Error messages92
Message:panic: vfs_mountroot: cannot mount root
rebooting...
resetting....
Explanation:The system is misconfigured. 
Response:There are two possible causes:
1.
You attempted to boot from a nonbootable device. 
Check the device name and try again. The alternate 
boot device may be set up incorrectly.
2.
You failed to reboot after mirroring root 
(olds -mirrored -setroot
), leaving the system 
unstable. In that case, do the following:
a. Boot from the CD.
b. Mount 
/dev/dsk/c0t0d0s0 /a (or whatever 
partition is your root partition).
c. Remove 
Solstice DiskSuite entries from 
/a/etc/system (i.e. everything between tags 
mddb ...)
d. Remove 
/a/etc/opt/SUNWmd/md* files, i.e.:
rm /a/etc/opt/SUNWmd/md*
e. Replace 
/dev/md/rdsk/d21 entries with 
/dev/rdsk/c0t3d0s0 (or whatever your boot 
device name is).
f. Boot: /usr/sbin/shutdown -y -g0 -i6
g. If the system still refuses to reboot, reload 
Solaris.
Message:
filename restored from filebackup
Explanation:The action failed, and the md.tab file was restored from 
the previous version. Consequently, the configuration files 
reflect the previous system setup.
Response:Determine the cause of the problem and try again.
Message:resync in progress
Response:The command entered cannot be executed because the 
mirrors are currently being resynched. Try again later. 
You can tell whether a resync is in progress by entering a 
metastat
 command. Error Messages (Continued) 
						

							  Troubleshooting  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Error messages93
Message:stale databases
Response:The state database contains old information. Recreate 
(see “
Recreating the Replicas and Reattaching the 
Disk” in Chapter 3).
Message:state database information not found, 
DiskSuite must not be installed
Response:Install and set up 
Solstice DiskSuite before doing this 
task.
Message:Submirror too small to attach
Explanation:The submirrors d11 and d12 (or d19 and d20) do not 
match. You have forgotten to label one or more disks, or 
you have partitioned one or more disks incorrectly.
Response:1. Determine the specific cause of the message by 
examining, via the 
format and partition 
commands, the disks involved. 
2. If the message was a response to a metattach 
d13 d12
 command, enter the following commands:
# metaclear d12
# metadb -d -f /dev/dsk/c0td0s1
(where  is the second boot disk)
3. If the message was a response to a metattach 
d21 d20
 command, enter the following command:
# metaclear d20
4. Label or repartition the disks in error, as needed.
5. Restart the mirror upgrade process. Note that you 
need not recreate the md.tab entries the second 
time through the procedure.
Message:syntax error
Response:Check the syntax and usage of the command. Reenter 
the command, correcting syntax errors you have made.Error Messages (Continued) 
						

							  Troubleshooting  CentreVu CMS Release 3 Version 8 Disk-Mirrored Systems
Error messages94
Message:The disk is not recognized by cms.
Explanation:The disk is either not a standard Sun disk drive, or is 
larger than 4.2 gigabytes.
Response:Replace the disk with a standard Sun disk drive of not 
more than 4.2 gigabytes capacity.
Message:The DiskSuite Software must be installed 
to run this script.
Response:Install 
Solstice DiskSuite software before attempting to 
run this script.
Message:The file 
filename could not be restored.
Explanation:The previous action failed, and the md.tab 
or vfstab
 
file could not be copied back. The existing files may not 
accurately reflect the system environment.
Response:Check the file and repair it if necessary. See “How to Set 
Up State Database Replicas” in Chapter 3.
Message:The /cms filesystem needs to be mounted
Explanation:
/cms must be mounted for the command to work.
Response:Mount 
/cms with the command:mount /cms Error Messages (Continued)