NIO CommKit Host Interface Installation and System Administration Manual

B-3

Troubleshooting Guide

Troubleshooting Checklist

If you encounter a problem with product operation, here is a checklist to

help troubleshoot the problem. Some items on the list may "overlap"; for

example, if there is a hardware problem, then the dkserver process cannot

execute properly.

• Start (or attempt to start) the dkdaemon process if not already started.

• Start (or attempt to start) the dkserver process if not already started.

• Verify that the LEDs on the Host Interface board are blinking at about a 4 second

interval.

If not, check that the Host Interface board(s) are well-seated. Check that the

ﬁber optic cables are attached correctly. Check that the Transmit and Receive

cables are not reversed. When a red LED is lit at the CPM-HS side of the cable,

it is one indication of a problem.

• Check that the host kernel contains CommKit components by executing

% what /stand/vmunix

If not, install/re-install Commkit.

• Check that the Host Interface boards have been recognized by the system. A

"dmesg" command should show a "dknio0" for each board installed. If not,

check that the Host Interface board(s) are well-seated.

• Check the dkdaemonlog and the dkserver log for errors. Error message

descriptions are listed in the next section of this chapter.

• Check that the VCS is configured correctly. Verify that the server and listener

names are properly defined by using the VCS verify commands. Verify that the

cpm's service state is "in".

An "Unable to create server" error may mean there is a mismatch between the

name speciﬁed for dkserver on the host and the group name on the VCS.

• Check that the server control table (srvtab/dksrvtab file(s)) are configured

correctly. An "Access Denied" error indicates a problem with a server control

table. Possible problems include:

- the service does not exist.

- the user is excluded because the UID is not valid or the user is not