Ericsson LBI-39169 Troubleshooting, CD-ROM does not Work, 15.2 MSM/SM does not Show PI Traffic

LBI-39169 TROUBLESHOOTING

15. TROUBLESHOOTING

This section presents various methods for solving technical difficulties with the Network Manager.

15.1 CD-ROM DOES NOT WORK

Problem: /etc/update exits with error that all devices are not mounted.

Solution:

The /etc/checklist file should have only list the hard drives. The Tape Drive and CD-ROM drive should not be listed in it. If peripherals are listed in this file, then updates will not work.

Procedure to access CD-ROM:

The CD-ROM is mounted when there is a disk in it using the mount /dev/dsk/c201d2s0 /cdrom command. Once mounted, the /cdrom directory is accessed like any other directory. The disk cannot be removed until an umount /dev/dsk/c201d2s0 command is performed.

15.2 MSM/SM DOES NOT SHOW PI TRAFFIC

Problem: MSM/SM does not show PI traffic, but shows Group and ICall traffic.

Solution:

Do traf -e-sXon the PI or stat -e-sXon the BCU/CAL where X is the PI Site_Id. If is shows that the packets the PI received were errored with Null Caller ID then check the Line database definition for the PI site in the System Manager. If the Line is enabled and the LID is 0, this is invalid and causes this problem. If there is only one PI in the Network all lines should be N. In a multinode PI configuration, the Line database must have a unique LID assigned for each PI line. See LBI 39000A.

15.3 ATTEMPT TO LOG IN FAILS

Problem:

When the disk fills up, the following situations occur:

∙All users who attempt to log in will be in the root directory (/).

∙None of the user’s initialization files will be executed, i.e., the environment variables (such as $path) may not be set correctly, and the general appearance of the screen will seem unusual.

∙Any process that tries to write to disk is likely to hang (this includes almost all processes).

∙The message “Cannot write to file: disk system full” will appear at the bottom left corner of the screen at the console. If the user is not at the console, he may not see the error message. If a remote user notices odd behavior, he should check for error messages on the screen that is connected as the console.

Solution:

Most likely, the log files have grown too large. Delete the log files in /usr/EDACS/logs/filename. DO NOT ERASE edacs.log. Also, periodically check /usr/netls/log_file and /usr/OV/log/trapd.log and delete files as necessary.

72