Error Messages

Lucent Technologies Data Switch Server Log File

The log file, dksrvlog, is written to by LCS60 interface software and contains information about incoming call requests. The default log file name is /var/opt/dk/log/dksrvlog.network_security_group_name. There will be as many dksrvlog files as there are multiple subnetworks configured. For the example in Figure 3-1, the three dksrvlog files are: dksrvlog.morse, dksrvlog.Library, and dksrvlog.Techs.

The dksrvlog file name may be changed with the -loption of the dkserver com- mand. The -voption specifies the amount of information that will be written to the file (i.e., log level). Its contents can be displayed by use of the pg command as shown in the following example.

Each entry in the dksrvlog file begins with a time stamp. The first message logged after the dkserver starts with a log level of n is always of the form shown in the example above: where morse is the name of the data switch interface server started, srvtab is the name of the data switch interface server table, dkuidtab is the name of the data switch interface dkuidtab, and n (6 in the example) is the level at which the server activity is logged.

#pg /var/opt/dk/log/dksrvlog.morse

Jun 27 09:50:43 (274) [0.000]

SERVER morse is INITING files=(/etc/opt/dk \

/srvtab /etc/opt/dk/dkuidtab) loglvl=6

Jun 27 09:50:53 (274) [0.000]

ERROR dkmgr: Can't open /dev/dk/dial0

Jun 27

09:50:53 (274) [0.000]

dkmgr : SERVER morse is ACTIVE and SERVING

Jun 27

09:51:11 (274)

[0.139]

REQUEST s=pupu, u=45003=lcsadm, r=earth/ \

mlkway/brown

 

 

Jun 27

09:51:11 (315)

[0.139]

Send ioctl init = 3

Jun 27

09:51:11 (315)

[0.139]

ORIGIN h=TOOLBOX.52.3, c=/opt/dk/bin/pupu

 

 

 

 

 

 

Administration

Note: morse is the network security group name.

More information is given depending on the following log levels:

Log Level 1 Each incoming call is logged with the service requested, the user id, and the dial string of the remote system from which the call ori- ginated. The entry will also show whether the call was accepted with the token REQUEST or rejected with the token DENIED.

Issue 3

8-45